tag:blogger.com,1999:blog-46324350850837800212023-11-16T08:10:15.955-08:00Educational Radio NetThis blog supports the Educational Radio Net, an amateur radio net that takes place Wednesdays at 8:00PM on the 2 meter repeater of the Puget Sound Repeater Group, 146.96MHz -600, with a tone of 103.5, located on Queen Anne Hill in Seattle.
The purpose of this net is to help our fellow amateur radio operators learn theory, gain practical knowledge, and generally benefit from the experience of the more seasoned operators.
Your hosts are Bob Helling, K9PQ, and Lee Bond, N7KC.Bob Hellinghttp://www.blogger.com/profile/02352636352618704676noreply@blogger.comBlogger95125tag:blogger.com,1999:blog-4632435085083780021.post-34586918438172958182009-10-28T20:00:00.000-07:002009-11-04T19:50:17.170-08:00The Basics for the New Ham, Bob, No. 75<div class="MsoNormal">
<span style="font-family: Calibri; font-size: x-small;"><span style="font-size: 11pt;">Here are a few questions provided by Mike, KF7DTI for the newer ham...</span></span><br />
<span style="font-family: Calibri; font-size: x-small;"><span style="font-size: 11pt;"> <br /></span></span><br />
<i><span style="font-family: Calibri; font-size: x-small;"><span style="font-size: 11pt;">What
is “Legal” (1500 watts) vs. Proper ( 5 to 20 watts) and
why…</span></span></i><br />
<span style="font-family: Calibri; font-size: x-small;"><span style="font-size: 11pt;"> First of all, let's look at what the legal limit is: 1,500 watts PEP (Peak Envelope Power) this is defined as the average power provided to the transmission line over one cycle where the envelope is at it's peak. The envelope is the carrier plus the modulation, so it is the average power of the signal at it's highest modulation. This gives a good indication of the likelihood of the signal to interfere with neighboring frequencies.</span></span><br />
<span style="font-family: Calibri; font-size: x-small;"><span style="font-size: 11pt;"><br /></span></span><br />
<span style="font-family: Calibri; font-size: x-small;"><span style="font-size: 11pt;">So now we get to the real question, what is proper. Well the regulations have something to say about that too. We are required to use the lowest amount of power to accomplish the communications we are trying to do. This is definitely a gray area and a guideline rather than a hard and fast rule. Sometimes it can be obvious, you don't need 50 watts to talk on 2 meter simplex to your neighbor a few blocks away. Sometimes it is not obvious at all, just how much power do you need to be heard by that rare DX station in a South Seas island that dozens of other hams are also trying to reach. There are endless possibilities for arguments here but this is a sort of "good faith" rule. You need to use your own best judgment to decide how much power is necessary.</span></span><br />
<span style="font-family: Calibri; font-size: x-small;"><span style="font-size: 11pt;"><br /></span></span><br />
<span style="font-family: Calibri; font-size: x-small;"><span style="font-size: 11pt;">The other reason to use less power is personal safety. I won't go into the specifics but there is good reason that your handheld doesn't put out more than about 5 watts. If you want to use your mobile rig as a portable, as many of us in emergency communications do, it is important to get the antenna away from your body and anyone elses. Just how far is another judgment call but it helps if you also have it up high so that when it is radiating primarily in the horizontal direction, it will be above your and everyone else's heads.<br /></span></span><br />
<br />
<br />
</div>
<div class="MsoNormal">
<i><span style="font-family: Calibri; font-size: x-small;"><span style="font-size: 11pt;">Proper handling of my unit .. will my Mobile work OK in
the Freezing snow?.. 110 degree Desert Sun?... pouring
Rain?</span></span></i><br />
</div>
<div class="MsoNormal">
<span style="font-family: Calibri; font-size: x-small;"><span style="font-size: 11pt;">Your mobile rig is designed to stay in a vehicle and to operate in one too. There are a handful of new weather-proof and even water-proof rigs on the market but leaving those out, you should use your rig where it will be kept dry and reasonably clean. As for cold and heat, you should check your owner's manual to be sure but generally you can do very well in the cold. When it gets hot you run the risk of overheating your rig when you run full power. Once again, this is a gray area. You can run at a pretty high ambient temperature as long as you use low power. The more power you use, the lower the ambient temperature has to be. <br /></span></span><br />
<br />
<i><span style="font-family: Calibri; font-size: x-small;"><span style="font-size: 11pt;">What
happens when my batteries get low?.. How can I
tell?</span></span></i><br />
</div>
<div class="MsoNormal">
<span style="font-size: small;"><span style="font-family: Calibri;">I assume you </span></span>mean your portable here. You should here a beep to tell you. HT's are notorious for beeping about 5 seconds before they shutdown. None of the HT's that I'm aware of have battery charge indicators. I may be wrong about this and if anyone knows of ones that do please speak up.<br />
<br />
<i><span style="font-family: Calibri; font-size: x-small;"><span style="font-size: 11pt;">Why
is my brand new Mobile that I just put in my old TRUCK so
staticy?</span></span></i><br />
<span style="font-family: Calibri; font-size: x-small;"><span style="font-size: 11pt;"><span style="font-size: small;">There are a couple of possible reasons. The most likely is the old truck itself. It is either emitting radiation from sparking or other electronics or it is causing fluctuations in the voltage where you are hooking up your radio. For this reason it is usually suggested to connect your radio directly to the battery, properly fused of course. Then all you have to worry about is the radiation caused by your truck. The only way I know to diagnose and fix it is to try putting some filters on the wires and see what happens. But this is a well known problem and there is a lot out there already to help diagnose it. One reason it happens is that mobile and HT rigs usually don't have the good filtering that base stations do. You can pay a lot for a Motorola or other rig designed for professional use in high radiation environments and do a lot better. </span> <br /></span></span><br />
<span style="font-family: Calibri; font-size: x-small;"><span style="font-size: 11pt;"><br /></span></span><br />
</div>
<div class="MsoNormal">
<span style="font-family: Calibri; font-size: x-small;"><span style="font-size: 11pt;">I can
use my old CB Radio Antenna as my Mobile antenna
right?</span></span><br />
<span style="font-family: Calibri; font-size: x-small;"><span style="font-size: 11pt;"><span style="font-size: small;">I wouldn't try it. Antennas are a huge subject that has been covered in various ERN's. You can check the blog for more info. In general, you can probably modify an old CB antenna if you know what you are doing to make it work for amateur radio, but you are almost certainly better buying an antenna build to do the job. Or you can make your own from scratch. Most people don't make their mobile anteannas though, that is better suited for base operations.</span> <br /></span></span><br />
<br />
</div>
<div class="MsoNormal">
<span style="font-family: Calibri; font-size: x-small;"><span style="font-size: 11pt;">What
is SWR and why do I care? (that is a good subject)</span></span><br />
<span style="font-family: Calibri; font-size: x-small;"><span style="font-size: 11pt;"> <span style="font-size: small;">SWR has been covered a few times and Lee has an exhaustive set of lectures on fundamental electronics leading up to impedance. In short, SWR, the Standing Wave Ratio, is a measure of how much of an electronic signal that you are transmitting, is reflected at a junction. The cause of the reflection is an impedance mismatch at the junction. For example, if you connected your transceiver that has an impediance at it's output of 50 ohms to 75 ohm cable, you will get an impedance mismatch that will cause a high SWR. Since most of us know to use 50 ohm cable the mismatch almost always comes at the connection to the antenna. The impedance at the connection to an antenna is a very complex subject and can depend on the antenna height above ground and other factors. For VHF/UHF it is simplified by the fact that the antenna is high above the ground compared to the wavelength so there is little variation. That's why you can buy an antenna with a 50 ohm connector and be pretty confident that it actually is 50 ohms.</span> <br /></span></span><br />
<br />
</div>
<div class="MsoNormal">
<i><span style="font-family: Calibri; font-size: x-small;"><span style="font-size: 11pt;">What
does QSL, QTH, QRV, 73… etc. mean?.. When is OK to use “Shorthand”
like that?</span></span></i><br />
<span style="font-family: Calibri; font-size: x-small;"><span style="font-size: 11pt;"><span style="font-size: small;">QSL, QTH, QRV and other three letter combinations starting with Q are known as Q signals. They come to us from the days of CW where it was worthwhile to have a shortcut for some commonly used phrases. Q was chosen since it is almost always followed by U so that by creating these combinations, not using U you could be assured that it was not a word. If the Q signal is followed by a question mark it means that it is a question, if no question mark then it is a positive statement.</span></span></span><br />
<br />
<span style="font-family: Calibri; font-size: x-small;"><span style="font-size: 11pt;"><span style="font-size: small;">For example, probably the most common one heard is QSL. You will hear it in place of Roger, Acknowledged, etc. It means, "I acknowledge receipt" or with a question mark, "Do you acknowledge receipt." This is also the reason for QSL cards, which are an acknowledgment of receipt of a contact form another station. These are used to prove that you made a contact with that rare DX station. By the way DX is just shorthand for distance and means a long distance, usually international.</span></span></span><br />
<br />
<span style="font-family: Calibri; font-size: x-small;"><span style="font-size: 11pt;"><span style="font-size: small;">73 goes back a long way as well and just means, "Best Wishes"</span></span></span><br />
<br />
<span style="font-family: Calibri; font-size: x-small;"><span style="font-size: 11pt;"><span style="font-size: small;">There are no hard and fast rules about using these. The most important thing to keep in mind is that you want to make yourself clearly understood. If the person or people you are communicating with understand the Q signals it is fine to use them.</span></span></span><br />
<span style="font-family: Calibri; font-size: x-small;"><span style="font-size: 11pt;"><span style="font-size: small;"> </span> <br /></span></span><br />
<br />
<br />
</div>Bob Hellinghttp://www.blogger.com/profile/02352636352618704676noreply@blogger.com2tag:blogger.com,1999:blog-4632435085083780021.post-30683962791943496202009-10-21T21:07:00.000-07:002009-10-21T21:09:50.029-07:00ASCII one oh one, Lee Bond N7KCOctober 21, 2009 Educational Radio Net, PSRG 74th Session<br /><br />Have you ever wondered about the relationship between computers and data entry? What really happens when you hit a key on your computer and the corresponding character pops up on the monitor? If you are old enough to remember the Mits Altair or IMSAI 8 bit microcomputers then you will have no problem answering these two lead in questions.<br /><br />Surely one of the oldest schemes for encoding alphabetical characters and numerals is the code developed by Samuel Morse and is known as Morse code. Early amateur radio operators had no choice but to learn the code in order to communicate with their fellow hams. The railroad telegraphers code is a variant of the Morse code and both the radio and railroad schemes were the backbone of the early communications industry.<br /><br />As telecommunications technique improved the mechanical tele-printer based on the 5 level Baudot code was introduced. Communications was much easier when typing replaced the telegraph key and the distant output was in easily read text. Since only 5 symbols were used the number of possible combinations was limited to 32. If you count all the letters of the alphabet, both lower and upper case, and the numerals 0 through 9, and various punctuation characters it is clear that even a shifted 32 will not do the job.<br /><br />During the late 50’s, when the early mainframe computers were evolving, it was obvious that something had to be done to improve the encoding of alpha-numerical character information that would be fed to the room sized digital monsters that glowed in the dark.<br /><br />Enter ASCII, pronounced ass-key, the acronym for American Standard Code for Information Interchange. ASCII is a 7 bit code hence 128 unique bit pattern combinations are possible. Enough combinations to represent all the upper and lower case alphabetical characters plus numbers plus punctuation plus special formatting characters in use at the time. The first meeting of the committee which adopted this code was in 1960. The code later became known as US ASCII since it was only good for English systems.<br /><br />During this time frame IBM developed a proprietary code known as EBCDIC which was based on all possible combinations of the 8 bits in a byte. There are 256 possible unique combinations of 8 bits so EBCDIC offered twice as many possibilities as did ASCII. EBCDIC was used in the large mainframe computers that IBM produced and ASCII became the standard coding scheme for the micro-computing industry.<br /><br />From the late 50’s until recently the use of US ASCII dominated the microcomputer industry and information exchange on the Internet. Today ASCII is taking a back seat to the Unicode in its various implementations as UTF-8, UTF-16, or UTF-32 as in Unicode Transformation Format. Using 16 bits, or a word, offers over 65 thousand unique possibilities so numerous languages can be represented in addition to English and this makes the encoding truly universal and a natural for Internet use.<br /><br />Historically ASCII is a 7 bit code. Always has been and always will be. However, that inviting 8th bit in the word could be useful and double the number of coding possibilities. Implementations of ASCII using all 8 bits became known as "extended" ASCII and found much use for formatting characters and such when word processing came to fore. Other names were "upper" level ASCII in contrast to the original "lower" level scheme.<br /><br />Let’s look at 7 bit ASCII in some detail to see how it is structured.<br /><br />Referring to the Bits, Nybles, Bytes, and Words (presentation 71) a few weeks ago we know that computers like to operate with patterns of 4 bits (a nyble), 8 bits (a byte), or 16 bits (a word). If ASCII requires 7 bits then the best choice for a pattern would be the next largest set or byte consisting of an assemblage of 8 bits. The extra 8th bit became useful as a rudimentary error detecting bit and was called the parity bit. More on this later.<br /><br />A table of the ASCII characters is generally shown as 16 rows and 8 columns. The multiple of 16x8 is 128 so this array matches all the combination possibilities of 7 bits. The first two columns from the left contain all of the, so called, formatting characters, the third column from the left is where you find the various punctuation symbols and math symbols, the fourth column from the left lists the numerical symbols, and the last four columns are the upper and lower case alphabetical symbols.<br /><br />To identify any one of 16 rows requires 4 bits and the lower 4 bits of the 7 bits is used as the row identifier where bit 1 is least significant. To identify any one of the 8 columns requires 3 bits and the bits 5, 6, and 7 (most significant) are used for this purpose. So, to recap… bits 1, 2, 3, and 4 are used to identify in which row a character is located and bits 5, 6, and 7 are used to identify in which column a character is located. Every box in the array is uniquely identified by a bit pattern. Bit 8 is always a zero unless the optional parity possibility is in play.<br /><br />The data entry and identification process goes like this. Suppose you depress the capital or upper case "H" key on your keyboard. Bit 7 is forced to a "1" and 6 and 5 remain at zero. Bit 4 is forced to a "1" and bits 3, 2, and 1 remain at zero. Finally the "H" is coded as 01001000 or 48h in shorthand hexadecimal notation. This bit pattern is sent to the computer where it is checked, pattern by pattern, against a table looking for a match. When the match is found the computer proper knows which key was pressed.<br /><br />Any error in this transmission process is serious since the computer will interpret your intended bit pattern incorrectly. The 8th bit or parity bit allows a low level error check as follows. Parity can be defined as even or odd. If you choose even then if the sum of the 7 bit 1’s is odd you just force bit 8 to a 1 and the overall number of 1 bits is even. If the sum of the 1 bits is even then leave the 8th bit at zero. This same process holds for odd parity. On the receiving end the system will check the count to determine if parity is correct. This scheme will detect all 1 bit errors or odd multiples thereof.<br /><br />In summary, bits 5, 6, and 7 determine a column and indicate if the symbol is formatting, a number, or alphabetical character. Bits 1, 2, 3, and 4 determine which character of the alphabet or which number or which formatting symbol is to be used.<br /><br />This concludes the set up discussion for ASCII one oh one. Are there any questions or comments with regard to tonight's discussion topic?<br /><br />This is N7KC for the Wednesday night Educational Radio NetAnonymousnoreply@blogger.com1tag:blogger.com,1999:blog-4632435085083780021.post-42753791767717068522009-10-20T00:49:00.000-07:002009-10-20T00:49:25.639-07:00The Future of the Educational Radio NetLee and I are considering ending our involvement with the Educational Radio Net. If we do, it will very likely end the net itself.<br />
<br />
This has been a labor of love for the two of us. It is a fair amount of work to come up with new subjects each week, research them and write the scripts for them. Getting on the air and doing the net is the payoff. What has kept us going has been the interest and participation of the hams checking in to the net. Lately that interest has fallen off somewhat. We both agree that we do not wish to continue as it is going now.<br />
<br />
We are soliciting ideas, suggestions, questions, etc. to assist us with creating future nets. We are also looking to add to our base of regular contributors.<br />
<br />
To give your suggestions, please contact Lee Bond: n7kc@comcast.net <br />
<br />
We are very grateful for the contributions from those listed below. They have helped sustain the net.<br />
John Pollock, K7MCX<br />
Jim Hadlock, K7WA<br />
Brian Daly, WB7OML<br />
Curt Black, WR5J<br />
Boone Barker, KC7RK <br />
<br />Bob Hellinghttp://www.blogger.com/profile/02352636352618704676noreply@blogger.com1tag:blogger.com,1999:blog-4632435085083780021.post-22145338381520605302009-10-14T19:23:00.000-07:002009-10-14T19:26:17.751-07:00Extra Class Exam Grab Bag, Bob, No. 73<div style="font-family: inherit;">
Tonight was supposed to be about current use of Spread Spectrum in Ham Radio but I couldn't find any information about it. If anyone on frequency knows about it or knows where to point me to look please let me know.<br />
</div>
<div style="font-family: inherit;">
<br />
</div>
<div style="font-family: inherit;">
Instead, tonight I will discuss a few test questions from the Extra Class exam. <br />
</div>
<div style="font-family: inherit;">
<br />
</div>
<span style="font-family: "Courier New",Courier,monospace;">E9B08 (C)</span><br />
<span style="font-family: "Courier New",Courier,monospace;">How does the total amount of radiation emitted by a directional (gain) antenna compare with the total amount of radiation emitted from an isotropic antenna, assuming each is driven by the same amount of power?</span><br />
<span style="font-family: "Courier New",Courier,monospace;">A. The total amount of radiation from the directional antenna is increased by the gain of the antenna</span><br />
<span style="font-family: "Courier New",Courier,monospace;">B. The total amount of radiation from the directional antenna is stronger by its front to back ratio</span><br />
<span style="font-family: "Courier New",Courier,monospace;">C. There is no difference between the two antennas</span><br />
<span style="font-family: "Courier New",Courier,monospace;">D. The radiation from the isotropic antenna is 2.15 dB stronger than that from the directional antenna</span><br />
<span style="font-family: "Courier New",Courier,monospace;"><br /></span><br />
<div style="font-family: inherit;">
The important point to take away from this is that the total radiation depends solely on the amount of power that is transferred to the antenna. What the antenna design can do is shape or focus that radiation so that more goes in the direction you want and less in the directions you don't want.<br /></div>
<span style="font-family: "Courier New",Courier,monospace;"><br /></span><br />
<span style="font-family: "Courier New",Courier,monospace;">E9D06 (C)</span><br />
<span style="font-family: "Courier New",Courier,monospace;">Why should an HF mobile antenna loading coil have a high ratio of reactance to resistance?</span><br />
<span style="font-family: "Courier New",Courier,monospace;">A. To swamp out harmonics</span><br />
<span style="font-family: "Courier New",Courier,monospace;">B. To maximize losses</span><br />
<span style="font-family: "Courier New",Courier,monospace;">C. To minimize losses</span><br />
<span style="font-family: "Courier New",Courier,monospace;">D. To minimize the Q</span><br />
<div style="font-family: inherit;">
<br /></div>
<div style="font-family: inherit;">
The reactance in the loading coil doesn't contribute to heat loss. All heat loss comes from resistance. Resistance acts directly on current, converting it to heat. Reactance, being out of phase with current, doesn't produce heat and doesn't contribute to losses.<br /></div>
<div style="font-family: inherit;">
<br /></div>
<span style="font-family: "Courier New",Courier,monospace;">E9D08 (B)</span><br />
<span style="font-family: "Courier New",Courier,monospace;">What happens to the bandwidth of an antenna as it is shortened through the use of loading coils?</span><br />
<span style="font-family: "Courier New",Courier,monospace;">A. It is increased</span><br />
<span style="font-family: "Courier New",Courier,monospace;">B. It is decreased</span><br />
<span style="font-family: "Courier New",Courier,monospace;">C. No change occurs</span><br />
<span style="font-family: "Courier New",Courier,monospace;">D. It becomes flat</span><br />
<br />
<br />
<span style="font-family: "Courier New",Courier,monospace;">E9D14(B)</span><br />
<span style="font-family: "Courier New",Courier,monospace;">Which of the following types of conductor would be best for minimizing losses in a station's RF ground system?</span><br />
<span style="font-family: "Courier New",Courier,monospace;">A. A resistive wire, such as a spark-plug wire</span><br />
<span style="font-family: "Courier New",Courier,monospace;">B. A thin, flat copper strap several inches wide</span><br />
<span style="font-family: "Courier New",Courier,monospace;">C. A cable with 6 or 7 18-gauge conductors in parallel</span><br />
<span style="font-family: "Courier New",Courier,monospace;">D. A single 12 or 10 gauge stainless steel wire<br /><br style="font-family: inherit;" /></span><br />
<div style="font-family: inherit;">
The reason for the thin, flat copper strap is that it increases the Capacitive reactance vs. the Inductive reactance making the strap less likely to become resonant. For similar reasons the RF ground strap should be as short as possible.<br /></div>
<div style="font-family: inherit;">
<br /></div>
<span style="font-family: "Courier New",Courier,monospace;">E9D15 (C)</span><br />
<span style="font-family: "Courier New",Courier,monospace;">Which of these choices would provide the best RF ground for your station?</span><br />
<span style="font-family: "Courier New",Courier,monospace;">A. A 50-ohm resistor connected to ground</span><br />
<span style="font-family: "Courier New",Courier,monospace;">B. A connection to a metal water pipe</span><br />
<span style="font-family: "Courier New",Courier,monospace;">C. A connection to 3 or 4 interconnected ground rods driven into the Earth</span><br />
<span style="font-family: "Courier New",Courier,monospace;">D. A connection to 3 or 4 interconnected ground rods via a series RF choke</span><br />
<div style="font-family: inherit;">
<br /></div>
<div style="font-family: inherit;">
We want a very low impedance path directly to earth ground. We are not trying to match impedance here, just reduce it, so no resistors or chokes. The metal water pipe might serve as a safety ground, although today, more and more pipes are PVC so don't count on that metal pipe you are connecting to, to be metal the entire length. But even so, an all metal pipe system in your house makes a pretty active antenna system in itself. This is not what you want for your RF ground. The short-run ground strap to interconnected ground rods in the Earth is the way to go.<br /></div>Bob Hellinghttp://www.blogger.com/profile/02352636352618704676noreply@blogger.com0tag:blogger.com,1999:blog-4632435085083780021.post-87723443033929237662009-10-06T16:16:00.000-07:002009-10-06T16:37:40.436-07:00Digital Summer Notes, Boone Barker, KC7RK, No. 72<h3 style="text-align: center;" align="center">
Notes from Curt Black's
“Summer of Digital Communications Fun”</h3>
<p class="Para" style="text-align: center;" align="center">
By Boone Barker, KC7RK
October 3, 2009</p>
<p class="Para">
I was a student in the ham radio class taught by Curt Black WR5J
during the summer of 2009. Included in the class were Lee N7KC, Bob K9PQ, Tammy
WA7TZ, Glen K7GLE and others. We learned about and experimented with a variety
of digital communication modes, many of which could be useful for emergency
communications. I know that everyone who participated enjoyed the challenge of
learning about digital communications. We all owe Curt a huge debt of gratitude
for his success in making this a fun experience.</p>
<p class="Para">
This paper is my effort to recap the summer sessions and some key
points that I wanted to remember. Full descriptions and more are in the
WA-DIGITAL Yahoo Group site at <a href="http://groups.yahoo.com/group/wa-digital/">http://groups.yahoo.com/group/wa‑digital/</a>
.</p>
<h3>
Overview</h3>
<p class="Para">
Students met Wednesday evenings from June 6 through August 26,
2009, on the PSRG Seattle repeater (146.960 MHz) for the Educational Radio Net
hosted by Curt Black, WR5J.</p>
<p class="Para">
All 12 sessions were written and led by Curt– Environmental
Scientist – ham for ¼ century—had a packet network then in Texas. Also a
naturalist – birds and bats and nature in general – Sound Recordist.</p>
<p class="Para">
Curt emphasized that nearly everything came from the internet
somewhere and sources were cited each time. Only of little of the information
was based on direct communication with the authors of the software—only when he
had questions on how to make something work or what was the current best
approach for achieving some objective.</p>
<p class="Para">
Training purpose: explore and experiment with a variety of
digital communication modes over radio.</p>
<p class="Para">
The WA-DIGITAL Yahoo Group established at <a href="http://groups.yahoo.com/group/wadigital/">http://groups.yahoo.com/group/wa‑digital/</a>
for this topic has extensive files and messages on this topic, including a Blog
Post script for each session. The information below is only a very brief
summary of each session; go to the corresponding Blog Post for complete
directions and information.</p>
<p class="Para">
Session scripts were also posted on the PSRG Educational Radio
Net blog at <a href="http://www.educationalradionet.blogspot.com/">http://www.educationalradionet.blogspot.com/</a>
and are still there.</p>
<p class="Para">
Participants were asked to have a computer, VHF and HF radios
and—eventually—a sound card interface, home-brew or purchased. </p>
<h3>
Session 1 - Intro to Digital Communication, Software and Modes </h3>
<p class="Para">
<b>Planned activity</b> for the summer</p>
<p class="MsoNormal" style="margin-left: 0.5in;">
Session 1 Intro to Digital
Communication, Software and Modes</p>
<p class="MsoNormal" style="margin-left: 0.5in;">
Session 2 Intro to FLDIGI –
Install, Setup and Mode Selection</p>
<p class="MsoNormal" style="margin-left: 0.5in;">
Session 3 Using FLDIGI – Starting
with PSK-31 and Transmitting a Good Signal</p>
<p class="MsoNormal" style="margin-left: 0.5in;">
Session 4 More FLDIGI – RTTY, the
WRAP Utility and RS-ID</p>
<p class="MsoNormal" style="margin-left: 0.5in;">
Session 5 WSPR – Weak Signal
Propagation Reporter</p>
<p class="MsoNormal" style="margin-left: 0.5in;">
Session 6 MMSSTV Slow Scan Image
Transmission</p>
<p class="MsoNormal" style="margin-left: 0.5in;">
Session 7 Digital SSTV EasyPAL</p>
<p class="MsoNormal" style="margin-left: 0.5in;">
Session 8 WSJT-JT65A – Terrestrial
HF</p>
<p class="MsoNormal" style="margin-left: 0.5in;">
Session 9 WSJT-HS-Meteor Scatter</p>
<p class="MsoNormal" style="margin-left: 0.5in;">
Session 10 Packet Radio Using
Flex32</p>
<p class="MsoNormal" style="margin-left: 0.5in;">
Session 11 Packet Radio Using AGW
Packet Engine</p>
<p class="MsoNormal" style="margin-left: 0.5in;">
Session 12 WINDRM – Digital Voice </p>
<p class="Para">
<b>Soundcard to radio interface options</b></p>
<ul style="margin-top: 0in;" type="disc">
<li class="MsoNormal">Acoustic coupling: microphone feeding shack audio into
your computer and the rig audio softly coming out of a speaker in the room
with you fairly close to the mic</li>
<li class="MsoNormal">Hardware: range from very simple ones for a few bucks to
$100 for a Tigertronics SignaLink USB. If you want to keep going you can
go up to a $369 US Interface Navigator - Lots of choices.</li>
</ul>
<p class="Para">
[See <a href="http://www.kc2rlm.info/soundcardpacket/1cablestart.htm">http://www.kc2rlm.info/soundcardpacket/1cablestart.htm</a>
and <a href="http://uspacket.org/network/index.php/topic,21.msg23/topicseen.html#new">http://uspacket.org/network/index.php/topic,21.msg23/topicseen.html#new</a>
for DIY soundcard interfaces.]</p>
<p class="Para">
<b>Software now available</b></p>
<ul style="margin-top: 0in;" type="disc">
<li class="MsoNormal"><u>Multifunctional</u>: Multipsk, MixW, Ham Radio Deluxe
and FLDIGI</li>
<li class="MsoNormal"><u>Specialized</u>: Digipan, MMSSTV, EasyPal, WSPR, WSJT,
Flex32</li>
<li class="MsoNormal"><u>Interface</u>: AGW Packet Engine, Packet Engine Pro</li>
<li class="MsoNormal"><u>Winlink</u>: Airmail, Paclink</li>
</ul>
<p class="Para">
<b>Assignment</b>: install FLDIGI and get ready to receive at the
next session.</p>
<h3>
Session 2 - Intro to FLDIGI – Install, Setup and Mode Selection</h3>
<p class="Para">
The group owes much of what we know about FLDIGI and the Narrow
Band Emergency Messaging System (NBEMS) to the Pennsylvania group at <a href="http://wpanbems.org/">http://wpanbems.org/</a> .</p>
<p class="Para">
<b><u>F</u>ast <u>L</u>ight <u>Dig</u>ital Modem Application
(FLDIGI) Software by W1HKJ and Friends (</b><a href="http://www.w1hkj.com/"><b>http://www.w1hkj.com/</b></a><b>
) </b></p>
<p class="Para">
<b>Modes:</b></p>
<ul style="margin-top: 0in;" type="disc">
<li class="MsoNormal">CW AFCW (A2).</li>
<li class="MsoNormal">DominoEX: (4,5,8,11,16,22)</li>
<li class="MsoNormal">Hell: Feld Hell, Slow Hell, Feld Hell 5, Feld Hell 9, FSK
Hell, FSK Hell-105, Hell 80 </li>
<li class="MsoNormal">MFSK: from 4 to 64 tones</li>
<li class="MsoNormal">MT63: 500, 1000, 2000 Hz bandwidths</li>
<li class="MsoNormal">Olivia: – several flavors from 250 to 1000Hz bandwidth and
with from 8 to 32 tones</li>
<li class="MsoNormal">PSK: BPSK-31, QPSK-31, BPSK- 63, QPSK-63, BPSK- 125, QPSK
125, BPSK-250, QPSK-250</li>
<li class="MsoNormal">RTTY: 45 baud, 50-baud, 75-baud</li>
<li class="MsoNormal">Thor: <strong>(</strong>4, 5, 8, 11, 16, 22)</li>
<li class="MsoNormal">Throb: (1, 2, 4)</li>
<li class="MsoNormal">WWV: calibration of soundcard oscillator)</li>
<li class="MsoNormal">Frequency Analysis: measure the frequency of a remote
signal that is transmitting a steady carrier.</li>
<li class="MsoNormal">Tune: generates a continuous single frequency audio signal
at the exact frequency to which the waterfall cursor has been set</li>
</ul>
<p class="Para">
<b>To Install the Software:</b></p>
<p class="Para">
See Blog Post 2 in the WA-DIGITAL group files for detailed
instructions. A summary: Go to the web site at <a href="http://www.pa-sitrep.com/NBEMS">http://www.pa-sitrep.com/NBEMS</a> . Follow
steps on the left side of the page to get the <b>FLDIGI software</b>, install, and
configure it. Calibrate your sound card offsets by downloading and running <b>CheckSR</b>
from <a href="http://www.pa-sitrep.com/NBEMS/fldigi_calibration.htm">http://www.pa-sitrep.com/NBEMS/fldigi_calibration.htm</a>
. Also download and install <b>NBEMS macros</b> from <a href="http://www.pa-sitrep.com/NBEMS/fldigi_macro.htm">http://www.pa-sitrep.com/NBEMS/fldigi_macro.htm</a>
. </p>
<p class="Para">
<b>Application Notes</b></p>
<ul style="margin-top: 0in;" type="disc">
<li class="MsoNormal">Win XP users should load FLDIGI 3.12.4. <b>Vista</b><b> OS
users</b> should install FLDIGI 3.11.4-WinV (available at <a href="http://groups.yahoo.com/group/wa-digital/">http://groups.yahoo.com/group/wa-digital/</a>
) until bugs in the later version are fixed.</li>
<li class="MsoNormal">Bookmark <b>fldigi on-line help</b> at <a href="http://www.w1hkj.com/FldigiHelp/index.html">http://www.w1hkj.com/FldigiHelp/index.html</a>
and go to it for info on various modes, and for an index of sights and
sounds of digital modes.</li>
<li class="MsoNormal">Install <b>QuickMix</b> by Product Technology Partners at <a href="http://www.msaxon.com/quickmix/">http://www.msaxon.com/quickmix/</a>
.This is a simple applet that allows you to store all or part of the
current state of your audio mixer in a settings file, and to restore the
mixer to that state whenever you want.</li>
</ul>
<p class="Para">
<b>Try out FLDIGI</b> using some of the following modes and
frequencies. </p>
<p class="Para">
<strong>PSK </strong>– narrow band low symbol rate modes using
single carrier differential Binary Phase Shift Keying, BPSK, or Quadrature
Phase Shift Keying, QPSK. This is the most popular digital mode by far. Common
PSK31 frequencies:
Daytime: 14.070 MHz/USB, 10.140 MHz/USB, 7.070 MHz/USB
Evenings/Night: 3.580 MHz/USB, 7.070 MHz/USB, 10.140 MHz/USB</p>
<p class="Para">
<b>MT63</b> employs a unique highly redundant Forward Error
Correction system which contributes to it robustness in the face of
interference and fading.</p>
<ul style="margin-top: 0in;" type="disc">
<li class="MsoNormal">MT63 <a name="mt632kl">FM 6m/2m/70cm ops (2K Long Interleave)</a></li>
<li class="MsoNormal"><a name="mt631kl">MT63 HF USB ops – (1K/Long Interleave):
NBEMS recommended USB frequencies: 3.590, 7.090, 14.109</a> MHz</li>
</ul>
<p class="Para">
<a name="oliv16_500"><b>Olivia</b> is a very robust mode with low
error rates, but can be annoyingly slow.</a></p>
<ul style="margin-top: 0in;" type="disc">
<li class="MsoNormal">HF USB ops – (500Hz/16 Tones): NBEMS recommended USB
frequencies: 3.584, 7.074, 14.074 MHz</li>
</ul>
<p class="Para">
[See <a href="http://hflink.com/olivia/">http://hflink.com/olivia/</a>
for a full list of Olivia calling frequencies.]</p>
<p class="Para">
<a name="dominoex11fec"><b>Domino</b> The mode is normally used
without Forward Error Correction, as it is very robust. The default speed (11
baud) was designed for NVIS conditions (80m at night), and other speeds suit
weak signal LF, and high speed HF use. The use of incremental keying gives the
mode complete immunity to transmitter-receiver frequency offset, drift and
excellent rejection of propagation induced Doppler. </a></p>
<ul style="margin-top: 0in;" type="disc">
<li class="MsoNormal">Default calling mode - DominoEX11. NBEMS recommended USB
frequencies: 3.583, 7.073, 14.073 MHz</li>
</ul>
<p class="Para">
<b>Feld Hell</b> frequencies 3.580, 7.037, 10.137, 14.0635, 21.063,
28.120 MHz</p>
<ul style="margin-top: 0in;" type="disc">
<li class="MsoNormal">Description of Feld Hell is at <a href="http://www.qsl.net/zl1bpu/FUZZY/Feld.htm">http://www.qsl.net/zl1bpu/FUZZY/Feld.htm</a></li>
</ul>
<h3>
Session 3 Using FLDIGI – Starting with PSK-31 and Transmitting a Good
Signal</h3>
<p class="Para">
Recommended reading: Clint Hurd KK7UK presentation at Alaska
Hamfest in 2008: go to <a href="http://kk7uq.com/html/hamfest.htm">http://kk7uq.com/html/hamfest.htm</a>
and click on <u>Digital Communication Basics</u>.</p>
<p class="Para">
<b>Hints to new PSK users</b> from that presentation:</p>
<ol style="margin-top: 0in;" start="1" type="1">
<li class="MsoNormal">Make sure you are putting out a pure signal. Don't
overdrive the rig.</li>
<li class="MsoNormal">Ask on the bands for a report from others – the software
of the person receiving your signal can report your IMD – should be less
than<b> minus 24dB</b>.</li>
<li class="MsoNormal">Don't type in all caps.</li>
<li class="MsoNormal"><span style="color: rgb(21, 34, 43);">Lower your power to a level of
50% of what your rig can produce so you don’t burn out your finals.</span></li>
<li class="MsoNormal"><span style="color: rgb(21, 34, 43);">Tune a little above the PSK
activity and call with Hell or MFSK16 or Olivia 16/500.</span></li>
</ol>
<p class="Para">
<b>All PSK31 frequencies </b></p>
<p class="MsoNormal" style="margin-left: 0.5in;">
<span style="color: rgb(21, 34, 43);">160
meters 1.838 MHz </span></p>
<p class="MsoNormal" style="margin-left: 0.5in;">
<span style="color: rgb(21, 34, 43);">80
meters 3.580 MHz </span></p>
<p class="MsoNormal" style="margin-left: 0.5in;">
<span style="color: rgb(21, 34, 43);">40
meters 7.035 MHz </span></p>
<p class="MsoNormal" style="margin-left: 0.5in;">
<span style="color: rgb(21, 34, 43);">30
meters 10.140 MHz </span></p>
<p class="MsoNormal" style="margin-left: 0.5in;">
<span style="color: rgb(21, 34, 43);">20
meters 14.070 MHz </span></p>
<p class="MsoNormal" style="margin-left: 0.5in;">
<span style="color: rgb(21, 34, 43);">17
meters 18.100 MHz </span></p>
<p class="MsoNormal" style="margin-left: 0.5in;">
<span style="color: rgb(21, 34, 43);">15
meters 21.080 MHz </span></p>
<p class="MsoNormal" style="margin-left: 0.5in;">
<span style="color: rgb(21, 34, 43);">10
meters 28.120 MHz </span></p>
<p class="MsoNormal" style="margin-left: 0.5in;">
<span style="color: rgb(21, 34, 43);">6
meters 50.290 MHz</span></p>
<p class="MsoNormal" style="margin-left: 0.5in;">
<span style="color: rgb(21, 34, 43);">2
meters 144.144 MHz</span></p>
<p class="MsoNormal" style="margin-left: 0.5in;">
<span style="color: rgb(21, 34, 43);">1.25
meters 222.07 MHz</span></p>
<p class="MsoNormal" style="margin-left: 0.5in;">
<span style="color: rgb(21, 34, 43);">70
centimeters 432.2 MHz</span></p>
<p class="MsoNormal" style="margin-left: 0.5in;">
<span style="color: rgb(21, 34, 43);">33
centimeters 909 MHz</span></p>
<p class="Para">
Note: you will frequently see the wider signals of <b>PSK63 </b>just
a little higher.</p>
<h3>
Session 4 More FLDIGI – RTTY, the WRAP Utility and RS-ID</h3>
<p class="Para">
<b>More features of FLDIGI described in Blog Post 4</b></p>
<p class="Para" style="margin-left: 0.5in;">
<b>Macros</b>: content can be edited by
right clicking on the button. Other sets can be accessed by clicking on the end
of the bar. Left or right clicking on the mode button brings up options.</p>
<p class="Para" style="margin-left: 0.5in;">
<b>Waterfall</b>: the size can be
adjusted and magnified.</p>
<p class="Para" style="margin-left: 0.5in;">
<b>2-minutes buffer</b>: constantly
saving the audio so that a new signal in a different mode can be selected for
decoding of that last 2 minutes.</p>
<p class="Para" style="margin-left: 0.5in;">
<b>Signal to noise and intermodulation
distortion</b> of a received signal are displayed on the bottom of the screen.</p>
<p class="Para">
<b>The Wrap Utility</b> (downloaded with FLDIGI)</p>
<p class="Para">
Wrap allows you to transmit a text message, image, or binary file
to either single or multiple stations and allow each receiving station to
verify that the transmission was received without error. <b>Blog Post 4</b> has
detailed instructions for configuring FLDIGI, converting and sending a
“wrapped” message, and receiving and decoding wrapped messages.</p>
<p class="Para">
<b>RS-ID</b></p>
<p class="Para">
The "RS" ("RS" for "Reed-Solomon")
identifier allows automatic identification any digital transmission done in one
of the RX/TX modes handled by FLDIGI if the sending station is using the
feature. In receive mode it can be activated by clicking on the RSID button in
upper right. </p>
<p class="Para">
<b>RTTY</b> (Radio Teletype) is the second most common digital
mode.</p>
<p class="Para">
Look to the following websites for <b>RTTY guidance</b>:</p>
<ul style="margin-top: 0in;" type="disc">
<li class="MsoNormal">Getting Started in RTTY with MMTTY at
<a href="http://www.dxzone.com/cgi-bin/dir/jump2.cgi?ID=13022">http://www.dxzone.com/cgi-bin/dir/jump2.cgi?ID=13022</a></li>
<li class="MsoNormal">An RTTY Tutorial for Beginners by Bill W7TI is at
<a href="http://www.iw5edi.com/ham-radio/26/a-rtty-tutorial-for-beginners">http://www.iw5edi.com/ham-radio/26/a-rtty-tutorial-for-beginners</a>
</li>
</ul>
<p class="Para">
<b>RTTY frequencies:</b></p>
<p class="MsoNormal" style="margin-left: 0.5in;">
80 meters: 3580 - 3650 (3520 - 3525
in Japan)</p>
<p class="MsoNormal" style="margin-left: 0.5in;">
40 meters: 7080 - 7100 in the US (see note below)</p>
<p class="MsoNormal" style="margin-left: 0.5in;">
30 meters: 10110 to top of band</p>
<p class="MsoNormal" style="margin-left: 0.5in;">
20 meters: 14080 - 14099 (avoid the
NCDXF beacons at 14100)</p>
<p class="MsoNormal" style="margin-left: 0.5in;">
15 meters: 21080 - 21100 </p>
<p class="MsoNormal" style="margin-left: 0.5in;">
10 meters: 28080 – 28100</p>
<p class="Para">
<b>Note</b>: RTTY allocations for 40 meters vary greatly all over
the world. In the US, RTTY is permitted between 7000 and 7150, although most US activity is between 7080 and 7100. DX activity is often found between 7020 and 7045. The
ARRL promotes 7040 as the RTTY DX calling frequency, but the CW QRP’ers use it
as their calling frequency too. </p>
<p class="Para">
<b>Three main digital packages</b> are: </p>
<p class="Para">
<b>FLDIGI</b> by David Freese, W1HKJ and Skip Teller, KH6TY: <a href="http://www.w1hkj.com/">http://www.w1hkj.com/</a></p>
<p class="Para">
<b>HRD/DM780</b> by Simon Brown, HB9DRV: <a href="http://www.ham-radio-deluxe.com/">http://www.ham-radio-deluxe.com/</a> </p>
<p class="Para">
<b>MULTIPSK</b> by Patrick Lindecker, F6CTE: <a href="http://f6cte.free.fr/index_anglais.htm">http://f6cte.free.fr/index_anglais.htm</a>
</p>
<p class="Para">
Patrick’s MULTIPSK is a great technical achievement. He offers
the most sensitive modems and detection routines available and many modes (such
as ALE-400) that are not available in any other software. The challenge is his
user interface is very dense and can be tough on a first-time user. His
philosophy is he wants all the controls in one place – and they are. </p>
<p class="Para">
FLDIGI is a very elegant package that is fully featured but
simple to setup and use. HRD is not so simple, but is a great package and when
used with DM780 is very fully featured. MULTIPSK offers the most sensitive
modems and detection routines available and many modes (such as ALE-400) that
are not available in any other software. The challenge is his user interface is
very dense and can be tough on a first-time user.</p>
<p class="Para">
<b>Other packages</b> of significance</p>
<p class="Para">
WINWARBLER, part of the DXLAB suite and available here: <a href="http://www.dxlabsuite.com/winwarbler/download.htm">http://www.dxlabsuite.com/winwarbler/download.htm</a>
</p>
<p class="Para">
DIGIPAN – by Skip Teller KH6 and one of the authors of FLDIGI and
a founding father of digital modes in amateur radio: <a href="http://home.comcast.net/%7Ehteller/digipan/">http://home.comcast.net/~hteller/digipan/</a></p>
<p class="Para">
MixW – updated in Jan, 2009 after a long hiatus. Payment of $50
required after a 15-day trial period. <a href="http://www.mixw.net/index.php?j=downloads">http://www.mixw.net/index.php?j=downloads</a></p>
<p class="Para">
Check out this repository of digital and other ham radio
software: <a href="http://www.g3vfp.org/download.html">http://www.g3vfp.org/download.html</a></p>
<h3>
Session 5 WSPR – Weak Signal Propagation Reporter</h3>
<p class="Para">
Joe Taylor, K1JT, of Princeton has written a series of programs
for brilliantly combining Digital Signal Processing (DSP) and ham radio to
allow us to plumb the depths of weak signal work. <b>WSPR</b> (pronounced
"whisper") stands for "Weak Signal Propagation Reporter."
This program is designed for sending and receiving low-power transmissions to
test propagation paths on the MF and HF bands. Users with internet access can
watch results in real time at <a href="http://wsprnet.org/drupal/">http://wsprnet.org/drupal/</a>.</p>
<p class="Para">
<b>Downloads</b> for Windows and documentation are at <a href="http://physics.princeton.edu/pulsar/K1JT/wspr.html">http://physics.princeton.edu/pulsar/K1JT/wspr.html</a>.
Follow the <u>Quick Start Guide</u> to install and configure.</p>
<p class="Para">
<b>Application notes</b></p>
<p class="Para">
<b>Soundcard</b>: In Configure>Options, enter the numbers from
the “Audio Device” list on the black WSPR screen that comes up at startup. Note
that power is in dBm.</p>
<p class="Para">
<b>Frequency</b> settings are automatic. Just choose the band.</p>
<p class="Para">
Install <b>Dimension 4</b> from Thinking Man Software at <a href="http://www.thinkman.com/dimension4/download.htm">http://www.thinkman.com/dimension4/download.htm</a>
to keep your computer clock accurate to within 0.01 sec.</p>
<p class="Para">
This is a <b>weak signal mode</b> – it really doesn’t need much
power – try 1 watt (30 dBm) and see who hears you and where they are. </p>
<p class="Para">
Try operating at <b>local sunrise or sunset</b> to really see
what happens as the bands change.</p>
<h3>
Session 6 MMSSTV, Slow Scan Image Transmission</h3>
<p class="Para">
<b>Download</b> MMSSTV from <a href="http://mmhamsoft.amateur-radio.ca/mmsstv/">http://mmhamsoft.amateur-radio.ca/mmsstv/</a></p>
<p class="Para">
<b>Install and configure</b> it using the Help file in the
program, or instructions in the WA-DIGITAL Yahoo Group files.</p>
<p class="Para">
Most <b>common modes</b>: Scotty 1 or Scotty 2 in US. Martin 1 or
2 for DX.</p>
<p class="Para">
Suggested <b>SSTV frequencies</b>: </p>
<p class="Para" style="margin-left: 0.5in; text-indent: -0.25in;">
<span style="font-family:Symbol;">·<span style=";font-family:";font-size:7pt;" >
</span></span><b>10 Meters:
</b>28.673
28.677
28.680=calling frequency
28.683
28.686
28.690=K3ASI repeater
28.700=ON4VRB repeater </p>
<p class="Para" style="margin-left: 0.5in; text-indent: -0.25in;">
<span style="font-family:Symbol;">·<span style=";font-family:";font-size:7pt;" >
</span></span><b>15 Meters:
</b>21.334
21.337
21.340=calling frequency
21.343
21.346
Avoid SSTV around 21.350 because there is a Phone DX Net running </p>
<p class="Para" style="margin-left: 0.5in; text-indent: -0.25in;">
<span style="font-family:Symbol;">·<span style=";font-family:";font-size:7pt;" >
</span></span><b>20 Meters:
</b>14.230=calling frequency
14.233
14.236
14.239
Avoid SSTV on 14.227 because there is a Phone DX Net running there. </p>
<p class="Para">
<b>Application Notes</b></p>
<p class="Para">
<b>Soundcard oscillator calibration</b> is critical to avoid
transmitting slanted images. See “Slant Correction” in the Help menu.</p>
<p class="Para">
To use this software, just go to the <b>SSTV watering holes</b> at
14.230 or 14.233. This is the best known and possibly the best defended
frequency in all of amateur radio. </p>
<p class="Para">
The <b>Ten Commandments</b> of Slowscan by Dave Jones - KB4YZ</p>
<ol style="margin-top: 0in;" start="1" type="1">
<li class="MsoNormal">Use voice before sending SSTV. </li>
<li class="MsoNormal">Wait for voice and SSTV traffic to finish before sending
SSTV. </li>
<li class="MsoNormal">Choose an SSTV mode that is proper for the image to be
sent, band conditions, and the receive capability of the receiving
stations. </li>
<li class="MsoNormal">Announce the SSTV mode used prior to sending. </li>
<li class="MsoNormal">Transmit on frequency as confirmed by calibration of the
VFO with WWV. </li>
<li class="MsoNormal">Send straight pictures as confirmed by calibration of the
clock timing with WWV. </li>
<li class="MsoNormal">Send quality pictures with call sign on image. </li>
<li class="MsoNormal">Send full frame. </li>
<li class="MsoNormal">Avoid sending a CW ID unless required by regulations. </li>
<li class="MsoNormal">Describe the picture only after it is confirmed that it
was properly received. </li>
</ol>
<h3>
Session 7 Digital SSTV: EasyPAL</h3>
<p class="Para">
<b>EasyPAL</b> is a piece of software by Erik VK4AES that uses
DRM encoding and allows us to send any type of file on your computer, including
images. We can request “fills” or retransmission of any blocks not received
perfectly. Or you can Reed-Solomon encode everything you send to increase the
probability your information will make it through the first time. </p>
<p class="Para">
<b>Download</b> the software from <a href="http://www.g4rob.co.uk/easypal.htm">http://www.g4rob.co.uk/easypal.htm</a>
and go to the help file on that web site for configuration instructions and
help files.</p>
<p class="Para">
<b>SSTV frequencies</b> are listed above.</p>
<p class="Para">
<b>Application notes</b></p>
<p class="Para">
<b>Soundcard volume settings are critical</b>. Too high or too
low a signal level from your Receiver via your Radio Interface to your PC
soundcard will result in Total or partial LOSS OF RECEIVE SIGNAL. EasyPal will
correctly receive and decode when ALL RECEIVE INDICATORS SHOW GREEN. Get it
right and then use QuickMix to save settings for this application.</p>
<p class="Para">
Go to Setup>Calibrate Waterfall (WWV) to use WWV signals to <b>calibrate
waterfall</b> frequency scale.</p>
<p class="Para">
[N.B. EasyPal could be a powerful tool for emcomm. It could be used
to transmit a standard ICS form along with photos from the field to the EOC.]</p>
<h3>
Session 8 WSJT-JT65A – Terrestrial HF</h3>
<p class="Para">
The <b>WJT Software </b>was also written by Joe Taylor, K1JT. It
facilitates basic digital communication using protocols explicitly optimized for
a number of different propagation modes. Specifically: </p>
<ul style="margin-top: 0in;" type="disc">
<li class="MsoNormal">FSK441 for meteor scatter </li>
<li class="MsoNormal">JT6M for ionospheric scatter </li>
<li class="MsoNormal">JT65 for EME at VHF/UHF, and for HF skywave propagation </li>
</ul>
<p class="Para">
<b>Download</b> for Windows is at <a href="http://physics.princeton.edu/pulsar/K1JT/wsjt.html">http://physics.princeton.edu/pulsar/K1JT/wsjt.html</a>
. The user’s guide is included with the download.</p>
<p class="Para">
JT65 has three sub-modes known as JT65A, B, and C. They are
identical except for the spacing between transmitted tone intervals. At the
present time JT65A is generally used on HF and 50 MHz, JT65B on 144 and 432
MHz, and JT65C on 1296 MHz. JT65 uses 60 second transmission and reception
intervals.</p>
<p class="Para">
Andy K3UK has an excellent <b>JT65A guide</b> at <a href="http://www.obriensweb.com/bozoguidejt65a.htm">http://www.obriensweb.com/bozoguidejt65a.htm</a></p>
<p class="Para">
By far the simplest method of figuring out where the action can
be found is to use your web browser and go to the <b>JT65 Terrestrial Link</b> <b>web
site</b> by N0UK at <a href="http://www.chris.org/cgibin/jt65talk">http://www.chris.org/cgi‑bin/jt65talk</a>
.</p>
<p class="Para">
The most commonly used <b>JT65A frequencies</b> are:
14.075 to 14.076
7.075
7.076 in North America
7.042 to 7.043
7.025 LSB for Europe and Oceania
3.576 (North America)
3.796 (Europe)
18.102 & 18.106
10.147
21.076
24.910
1.805 to 1.808.</p>
<p class="Para">
14.076 or 10.147 or 7.076 are the best places to start. These are
DIAL frequencies.</p>
<p class="Para">
<b>Application Notes</b></p>
<p class="Para">
<b>Important</b>: use the WSJT7 black and white DOS-like window
to check your input and output device numbers –then transfer that info to the
colorful WSJT7 by K1JT window - look under the SETUP menu - OPTIONS choice and
enter the AUDIO IN and AUDIO OUT device numbers you got from the first column
on the DOS-like black window.</p>
<p class="Para">
As before, <b>input volume level is critical</b>.</p>
<p class="Para">
<b>Soundcard oscillator calibration</b> is also important. See
the help files.</p>
<p class="Para">
<b>Operating with WSJT </b></p>
<p class="Para">
By longstanding tradition, a minimal valid QSO requires the
exchange of call signs, a signal report or some other information, and
acknowledgments. WSJT is designed to facilitate making such minimal QSOs under
difficult conditions, and the process can be made easier if you follow standard
operating practices. The <b>recommended procedure</b> is as follows: </p>
<p class="MsoNormal">
1. If you have received less than both calls from the other
station, send both calls. </p>
<p class="MsoNormal">
2. If you have received both calls, send both calls and a
signal report. </p>
<p class="MsoNormal">
3. If you have received both calls and a report, send R plus
your signal report. </p>
<p class="MsoNormal">
4. If you have received R plus signal report, send RRR. </p>
<p class="MsoNormal">
5. If you have received RRR — that is, a definite
acknowledgment of all of your information — the QSO is “officially” complete.
However, the other station may not know this, so it is conventional to send 73s
(or some other conversational information) to signify that you are done. </p>
<p class="Para">
<b>Typing the F5 key</b> will cause WSJT to pop up a screen that
reminds you of the recommended procedures.</p>
<p class="Para">
<b>Digital on Six</b> at <a href="http://www.ykc.com/wa5ufh/DOS/index.html">http://www.ykc.com/wa5ufh/DOS/index.html</a>
promotes the use of digital modes on the 6 meter band. A weekly event is the
JT65B activity on Friday evenings in 2 phases: 9:00 pm Eastern and then 8:00 pm
Pacific time. Default Mode JT65B on 50.294MHz. When the "Band Is
Open" QSY to PSK / Olivia / etc.
on that mode’s appropriate calling frequency.
50.260 WSJT Modes (Calling Frequency)
50.290 PSK31
50.2925 Olivia
50.294 JT65B & Friday Activity Period Calling Frequency
50.300 RTTY and MFSK</p>
<p class="Para">
<b>Session 9 WSJT-High Speed-Meteor Scatter</b></p>
<p class="Para">
<b>WSJT/FSK441</b> is now the <b>primary meteor scatter program</b>
and mode over nearly all the world. </p>
<p class="Para">
<b>Go to </b><a href="http://www.qsl.net/w8wn/hscw/papers/fsk-sop.html"><b>http://www.qsl.net/w8wn/hscw/papers/fsk-sop.html</b></a><b>
for Standard Operating Procedures</b> for FSK441 meteor scatter communications
within the Americas. <b>Read this!</b></p>
<p class="Para">
Go to <b>Ping Jockey Central</b> at <a href="http://www.pingjockey.net/cgi-bin/pingtalk">http://www.pingjockey.net/cgi-bin/pingtalk</a>
and click on <b>“read this!”</b> at the top of the page to see Ping Jockey Etiquette.
On that page are messages from ongoing HSMS scheds and contacts.</p>
<p class="Para">
Go to <a href="http://www.ykc.com/wa5ufh/">http://www.ykc.com/wa5ufh/</a>
for the <b>WSJT Group</b> –information and news about meteor scatter,
including Random Hour operations on Saturday and Sunday mornings. See also the <b>WSTJ
Yahoo group</b>.</p>
<p class="Para">
<b>Application Notes</b></p>
<p class="Para">
<b>Computer clock</b> must be accurate.</p>
<p class="Para">
In North America, <b>50.260 MHz and 144.140 MHz</b> are <b>calling
(CQ) frequencies—not</b> <b>operating</b> frequencies. Schedules should always
be made at least 5 kHz away from the calling (CQ) frequencies.</p>
<p class="Para">
"CQU5" means "I'm listening and will reply Up 5
kHz."
"CQD8" means "I'm listening and will reply Down 8 kHz".
The offset frequency is always relative to the CQ frequency.</p>
<p class="Para">
“CQ123” means "I'm listening and will reply on 144.123 MHz."</p>
<p class="Para">
The commonly-accepted (and expected) <b>exchange for all HSMS
operation</b> is the burst duration-signal strength report
("2-number" report).</p>
<div align="center">
<table class="MsoNormalTable" border="1" cellpadding="0">
<tbody>
<tr>
<td style="padding: 0.75pt;">
<p class="MsoNormal">
First Number: Ping Duration</p>
</td>
<td style="padding: 0.75pt;">
<p class="MsoNormal">
Second Number: Signal Strength</p>
</td>
</tr>
<tr>
<td style="padding: 0.75pt;">
<p class="MsoNormal">
1 - Ping with no info. (Not sent)</p>
</td>
<td style="padding: 0.75pt;">
<p class="MsoNormal">
</p>
</td>
</tr>
<tr>
<td style="padding: 0.75pt;">
<p class="MsoNormal">
2 - ping, up to 5 sec in length</p>
</td>
<td style="padding: 0.75pt;">
<p class="MsoNormal">
6 - up to S3 in strength</p>
</td>
</tr>
<tr>
<td style="padding: 0.75pt;">
<p class="MsoNormal">
3 - 5-15 sec in length</p>
</td>
<td style="padding: 0.75pt;">
<p class="MsoNormal">
7 - S4 to S5</p>
</td>
</tr>
<tr>
<td style="padding: 0.75pt;">
<p class="MsoNormal">
4 - 15-60 sec burst</p>
</td>
<td style="padding: 0.75pt;">
<p class="MsoNormal">
8 - S6 to S7</p>
</td>
</tr>
<tr>
<td style="padding: 0.75pt;">
<p class="MsoNormal">
5 - over 60 sec burst</p>
</td>
<td style="padding: 0.75pt;">
<p class="MsoNormal">
9 - S8 and stronger</p>
</td>
</tr>
</tbody></table>
</div>
<p class="Para">
<b>Best time</b> for MS operations is in the morning hours,
around 0600 local time, when that part of the earth is facing the same
direction as the direction of travel of the earth in its orbit around the sun.</p>
<h3>
Session 10 Packet Radio Using Flex32 and Paxon</h3>
<p class="Para">
Soundcard packet makes amateur packet radio available to any Ham
with a VHF transceiver and a soundcard-equipped computer, at little or no
expense.</p>
<p class="Para">
For the classic “Introduction to Packet Radio” by Larry Kenney,
WB9LOZ, go to <a href="http://www.choisser.com/packet/">http://www.choisser.com/packet/</a>
.</p>
<p class="Para">
<b><u>Flex32 Software</u></b> written by Gunter Jost DK7WJ</p>
<p class="Para">
<b>Go to</b> <a href="http://uspacket.org/network/index.php/topic,21.msg23/topicseen.html#new">http://uspacket.org/network/index.php/topic,21.msg23/topicseen.html#new</a>
for a tutorial by Charles Brabham N5PVL with download and installation
instructions. Two programs are downloaded:
<b>flexnet32.zip</b> this file contains the Flex32 software, some assorted
drivers, and a simple terminal program and
<b>soundmodem-flex.zip</b> this is the soundcard driver module, along with a
setup utility.</p>
<p class="Para">
<b>Installation</b>: See Blog Post 10 for details. Briefly: Unzip
into C:\FLEX32. Run soundmodem.config to configure soundcard driver. Run
Flexctl.exe to bring up the Flexnet Control Center and add “soundmodem” to the
channel parameters. Create a command-line shortcut to Tnc32.exe with parameters
“call‑sign 4 4” to bring up TNC32. Key Esc to enter command
mode and key H to list available commands. This is a simple terminal program
that may be used to connect to a packet network</p>
<p class="Para">
In Seattle, connect to SEA on 145.010 MHz.</p>
<p class="Para">
<b><u>Paxon software</u> </b>written by Ulf Haueisen DG1FAZ</p>
<p class="Para">
<b>Go to</b> <a href="http://uspacket.org/network/index.php/topic,20.0.html">http://uspacket.org/network/index.php/topic,20.0.html</a>
for another tutorial by Charles Brabham N5PVL with download and configuration <b>instructions</b>.
The web-site, help files and installation program for Paxon are all in German,
but the program comes up ready for English speaking users. However, the help
file is still in German.</p>
<p class="Para">
<b>Paxon download</b> is at <a href="http://www.paxon.de/download.html">http://www.paxon.de/download.html</a>
for download. See Blog Post 10 for details of installation and configuration.</p>
<p class="Para">
<b>First Steps</b> are listed in the Help tab</p>
<p class="MsoNormal" style="margin-left: 0.5in;">
Click on Tools, Settings.</p>
<p class="MsoNormal" style="margin-left: 0.5in;">
Select General, My Calls, Add.</p>
<p class="MsoNormal" style="margin-left: 0.5in;">
Enter your Callsign and specify the
connectable SSIDs.</p>
<p class="MsoNormal" style="margin-left: 0.5in;">
Setup your Modems and TNCs:
Devices, Device drivers, Add.</p>
<p class="MsoNormal" style="margin-left: 0.5in;">
Select Flexnet or Hostmode.</p>
<p class="MsoNormal" style="margin-left: 0.5in;">
Select your devices in the list,
and edit their Properties.</p>
<p class="MsoNormal" style="margin-left: 0.5in;">
Confirm the settings with the OK-Button.</p>
<p class="MsoNormal" style="margin-left: 0.5in;">
Click on Connect to make your first
connect with Paxon. Have Fun!</p>
<p class="Para">
Try browsing around in Paxon's "Settings" and you will
be amazed at all of the nice things this program can do. It can be used for
file transfers, remote SYSOP'ing, and as a personal terminal.</p>
<h3>
Session 11 Packet Radio Using AGW Packet Engine</h3>
<p class="Para">
<b>AGW Packet Engine</b> by George Rossopoylos SV2AGW handles all
the traffic between packet applications and the computer/radio interface—TNC or
soundcard. It is freeware from the SV2AGW web site at <a href="http://www.sv2agw.com/ham/">http://www.sv2agw.com/ham/</a> in the “<b>Downloads”</b>
section. A lengthy <b>tutorial</b> by Ralph Milnes KC2RLM for installation and
configuration is located at <a href="http://www.kc2rlm.info/soundcardpacket">http://www.kc2rlm.info/soundcardpacket</a>
. See Blog Post 11 for details.</p>
<p class="Para">
A full featured version is Packet Engine Pro, with one month free
and then $59 license fee. The SV2AGW web site also has software downloads for
AGWTerminal and AGWMonitor, both useful accompaniments to AGWPE. </p>
<p class="Para">
<b>Application Notes</b></p>
<p class="Para">
When you configure a radioport in AGWPE for SignaLink USB, select
an unused printer port (LPT3) as your PTT port. </p>
<p class="Para">
Always format packet and WL2K messages in plain text. HTML format
adds unnecessary bytes to the message.</p>
<p class="Para">
For use with Airmail software, download and install AM to PE
software by Brian Smith KG9OG from <a href="http://www.qsl.net/mararc/ampe.htm">http://www.qsl.net/mararc/ampe.htm</a>
.</p>
<h3>
Session 12 <a name="6302631280933418248"></a>WinDRM—Digital Data and Voice
Using Digital Radio Mondiale on the Ham Bands </h3>
<p class="Para">
The problem with digital voice modes is the loss of the use of a proprietary
codec. <b>Digital voice is about dead</b> and probably will remain that way
until a MELP equivalent codec is found or some new technology is found. See
Blog Post 12 for more information.</p>
<p class="Para">
If you want to try it, here is the link: <a href="http://n1su.com/windrm/download.html">http://n1su.com/windrm/download.html</a>
.14.236 MHz is the calling/net frequency for digital voice. </p>
<h3>
Postscript</h3>
<p class="Para">
At this writing, the WA-DIGITAL Yahoo Group is active—and the
group web site at <a href="http://groups.yahoo.com/group/wadigital/">http://groups.yahoo.com/group/wa‑digital/</a>
has a large collection of files and information about digital communications for
Radio Amateurs. If you are interested in this topic but not yet a member of the
group, please consider joining.</p>
<p class="Para">
October 5, 2009</p>Bob Hellinghttp://www.blogger.com/profile/02352636352618704676noreply@blogger.com1tag:blogger.com,1999:blog-4632435085083780021.post-49438596577508984982009-09-30T19:25:00.000-07:002009-09-30T19:38:14.184-07:00Bits, Nibbles, Bytes, and Words, Lee Bond N7KC<strong><span style="font-size:130%;">September 30, 2009 Educational Radio Net, PSRG 71st Session<br /></span></strong><br />The digital computer is ubiquitous. These computers are everywhere. Kids have their own and, more than likely, so do the grandparents. Most users are very proficient with the keyboard and blaze through the games, documents, spreadsheets, and whatnot without even a thought of what is going on inside that mysterious box called a computer. I am willing to bet that not one in ten users can define a "bit" and I will further wager that not one in 100 users has a good grasp of computer arithmetic or how the rational coding of bits makes their computer tick.<br /><br />My task tonight is to lead you down that magic path and explore the idea of the "bit" and how it can be used to represent numbers or events. We will then extend the bit notion into nibbles, bytes, and words. Some of the net participants tonight are likely to be expert in this bit world so, if you quality, think of ways to help me clarify the notion when I break for questions or comments.<br /><br />Let’s start with our very familiar decimal number system and dissect it in a way that I bet few of you have done. We will concern ourselves only with integers so no fractions are allowed in our discussion. Integers are the numbers 1, 2, 3, etc. that have no fractional part. You may call them whole numbers if you please. Integers can be precisely defined but that would muddy the water a bit so we will dispense with such formalism in favor of simplicity. We will start with the integers 1 through 9 and include the notion of nothingness as in zero.<br /><br />When we think of the decimal integers we must consider the ordering. For example after nothingness as in zero we think of 1, then 2, then 3, etc. in order through 9. Our standard notion of 9 is that it is ‘bigger’ than 8 and 8 is ‘bigger’ than 7 or 6 or 5, etc. In the following discussion throw ordering out the door. We will not be interested in ordering. In fact we will not even use numbers rather we will choose a collection of identical marbles and call then symbols. So, zero (or nothingness) plus 1 through 9 equals 10 symbols which we represent with 10 marbles.<br /><br />Unfortunately this forum of ours does not include a chalkboard so we must create a virtual chalkboard in your mind. If it helps then close your eyes and imagine the following: in your mind arrange 6 boxes in a 2 row x 3 column array. Each of the boxes in the top row has 10 identically sized marbles and the row of lower boxes have ‘nothing’ or zero marbles. Just so we do not get marbles in the wrong boxes lets choose black marbles for the rightmost box, brown marbles for the center box, and red marbles for the leftmost box.<br /><br />Ok, lets do something useful with this scheme. Assume that you are sitting on the back porch looking toward the Cascades and you want to tally lightning strikes. When the first strike occurs you move a black marble from the top right box into the box below. At the next strike you repeat the previous operation and move another black marble from the top right box into the box below. As you notice more and more lightning strikes you move black marbles until you have no more black marbles in the top right box. At this point you have used all of your marbles, so to speak, and you indicate this fact by moving a brown marble into the middle box below then move all of the ‘used’ black marbles back into the top right storage box.<br /><br />The lightning strikes continue and you move black marbles, one by one, into the lower box until you again run out of marbles. At this point you move a brown marble from the top box into the box below and reload the top box with the black marbles. Eventually you will run out of brown marbles in the top center box so you will move a red marble from the top left box to the box below and reload the top boxes with appropriate black and brown marbles.<br /><br />The point of this mental exercise is to illustrate that you can tally objects with symbols and that every time you exhaust, or cycle through, your symbol set you just indicate this fact by incrementing the symbol set to the left. You can choose as many symbols as you please. In this example, based on the decimal system with 10 symbols, each box to the left is weighted or "heavier" by 10 with respect to its neighbor to the right. As a result, this 10 symbol scheme goes units, tens, hundreds, thousands, etc. so is very convenient for us mortals. Once you know the weighting you can easily figure out how many lightning strikes you tallied by counting the symbols in each weighted box.<br /><br />In the interest of time let me assert that you can use a set of 12, or 9 or 8 or 7, etc. symbols and the scheme holds true. Now lets examine the case where we have reduced the set to two symbols. Thinking for a moment you realize that "bi" means two as in binary star or binocular. Could the binary number system be as simple as accounting for just two symbols? The answer is, of course, yes. The beauty of using two symbols in numerical computing is that transistors are very good switches and can be used to represent the two binary states perfectly. A SPST switch normally has two states such that it is either on or off. Open or closed. It is a trivial exercise to arrange a circuit with a mechanical switch such that one switch position results in +5 volts and the other position results in zero volts. The symbols associated with a two state switch are zero and one as in 0 or 1.<br /><br />Now, in a fashion similar to the decimal box exercise above let’s arrange 8 binary boxes side by side in a row. We know that the state of each of these "binary" boxes can be represented by either a 0 or a 1. Assume that the rightmost box is the, so called, least significant box and that all boxes are in the 0 state. Visually the boxes look like 0000 0000. Now, bump the rightmost box to the 1 state and the visual presentation goes to 0000 0001. Well, the rightmost box has now used all of its symbols so to tally the next event it must return to 0 and the box to the left is bumped from 0 to 1 as in 0000 0010. If you carry this process forward you will eventually achieve 1111 1111 and the next event will change all positions back to 0000 0000. The weighting goes by 2 rather than 10 as in the decimal case so each position to the right is ½ of its left neighbor or each position is twice its neighbor to the right. The sequence is 256, 128, 64, 32, 16, 8, 4, 2, 1. These 8 boxes represent a byte and each of the positions is a binary digit or bit. Two sets of 8 boxes as in 2 bytes or 16 bits represents a binary "word". Half a byte as in 4 bits is a nibble (or nybble to some).<br /><br />The total number of distinct combinations of 8 bits from 0000 0000 to 1111 1111 is 256 and goes as 2^8. A binary word composed of 16 bits can assume 2^16 or 65,536 distinct combinations. Recall that we are limiting ourselves to positive integers so we are only able to handle numbers up to 65,536. There are schemes to handle signed integers such as 2’s complement arithmetic and to be completely flexible there are floating point schemes which look a lot like scientific notation.<br /><br />Four binary bits can assume 16 distinct combinations and is the basis of the hexadecimal number system which has symbols 0 through 9 plus A, B, C, D, E, and F. Four binary bits are also used for BCD or binary coded decimal notation by throwing away the six unused states.<br /><br />How would one go about doing math operations on a computer? Well, microprocessors are very good and quick at adding or subtracting but clumsy when multiplying or dividing. Early microprocessors required many operations or, so called, clock cycles to produce numerical products and it was common to have a math coprocessor standing by to do the heavy lifting. For example, if you want to multiply a number by 10 in the decimal system you just move the decimal point one position to the right. In the binary system you would shift left (x2), shift left again (x4), shift left again (x8), and then add twice to achieve the 10x product. Clearly, there is a lot of time consuming overhead doing math in this fashion. Contemporary microprocessors are constructed with onboard and dedicated numerical processors with slick routines and which unburden the main unit.<br /><br />If you look at the schematic of any computer one thing will pop out immediately. There are lots of parallel paths connecting the various semiconductor packages. These parallel wire structures are called busses and might be as wide as 16 bits… possibly more… for memory addressing as an example. There is likely a data buss as well. One line generally represents the buss with breakouts at the ends. Each wire handles one bit of data on the data buss.<br /><br />In summary, the intent of this presentation is to show that symbols can be used to tally events and that recycling symbols will work in any number system. Starting with the familiar decimal number system and showing that symbol manipulation leads handily to the very simple two state, or binary, number system. A bit is a two state binary digit, a nibble is four associated bits, a byte is 2 associated nibbles or 8 bits, and a word is 2 bytes of 16 associated bits. Modern computers are said to have 32 bit words and, in some cases, 64 bit words.<br /><br />This concludes the set up discussion for bits, nibbles, bytes, and words. Are there any questions or comments with regard to tonight's discussion topic?<br /><br />This is N7KC for the Wednesday night Educational Radio NetAnonymousnoreply@blogger.com4tag:blogger.com,1999:blog-4632435085083780021.post-63878788543716763892009-09-23T18:02:00.000-07:002009-09-23T19:50:09.078-07:00Phase Shift Keying, Bob, No. 70Tonight I am continuing with my series on Spread Spectrum Radio. I am going to discuss Phase Shift Keying (PSK), which is the form of modulation used by Direct Sequence Spread Spectrum (DSSS) Radio.<br /><br /><span style="font-weight: bold;">Spread Spectrum Radio Review</span><br />Let's have a short review of spread spectrum. The two main kinds in use in ham radio are Frequency Hopping and Direct Sequence. Frequency hopping is relatively easy to understand. Your carrier, rather than being on a fixed frequency, jumps from one frequency to another. As long as the equipment receiving makes the same jumps you will be able to transmit the signal and prevent interference on any one frequency from causing a problem. This can be used for analog or digital transmission but is most commonly used for digital. Note that you must have a pattern of frequency changes that is known to both parties in order to allow the receiver to follow the transmission.<br /><br />In the other method, Direct Sequence, you only transmit digital information. In fact the name "Direct Sequence" comes from the 11 digit sequence of ones and zeros that is used to modulate the carrier. If your data bit is a zero then you send the sequence normally. If your data bit is a one then you send a one where the sequence has a zero and send a zero where the sequence has a one. For example 101 would turn into 010. I mentioned that the carrier is modulated by this sequence but I didn't say how. It is modulated using Phase Shift Keying.<br /><br /><span style="font-weight: bold;">Phase Shift Keying (PSK)</span><br />So, what exactly is phase shift keying? It is a way of changing the phase of a carrier to transmit a digital signal. In essence what you are doing with PSK is phase hopping. In the simplest example called Binary Phase Shift Keying (BPSK) you hop 180 degrees out of phase to transmit a certain piece of digital data. So the signal is either in it's "normal" phase or in it's 180 degree out phase which is to say, inverted. Note that the frequency of the carrier isn't changed but when you change the phase and modulate the carrier you create side-band emissions. The faster you modulate the signal, the wider the side-bands. In addition to BPSK there is Quadrature PSK (QPSK) where the phase can be one of four values, 0, 90, 180 or -90. There is also 8PSK using 8 phase angles and so on. The general term is Multiple Phase Shift Keying (MPSK).<br /><br /><br /><span style="font-weight: bold;">Differential Phase Shift Keying (DPSK)</span><br />Basic BPSK has the signal at normal 0 phase to represent a digital zero and at 180 degrees out to represent a digital 1. A commonly used variation on this is called Differential Binary Phase Shift Keying (DBPSK) and instead of a 1 being 180 degrees out of phase, a 1 always changes the phase while a 0 always keeps the phase the same. This way you don't need a reference signal to know which is 0 degrees and which is 180 degrees.<br /><br /><span style="font-weight: bold;">PSK-31</span><br />If you want a very narrow signal you are limited to a slow digital transfer rate. This is the case with PSK-31. The 31 comes from the 31.25 bits per second data rate which generates 31.25Hz sidebands. This is pretty much the opposite of spread spectrum. The whole point of PSK-31 was to use such a small slice of the band that you could actually fit many PSK-31 channels in the space of a typical SSB voice bandwidth.<br /><br /><span style="font-weight: bold;">PSK for Spread Spectrum</span><br />With spread spectrum you want a very wide bandwidth; by definition, one that is much wider than necessary to convey the information. By encoding each bit of data with the 11 bit sequence used in DSSS you now modulate the signal 11 times for each bit transferred. So for a 1 Mbit/sec transmission, you modulate at 11 MHz. This achieves the spread spectrum you are looking for. This modulation is encoded using DBPSK and a suppressed carrier.Bob Hellinghttp://www.blogger.com/profile/02352636352618704676noreply@blogger.com0tag:blogger.com,1999:blog-4632435085083780021.post-3297077994687619952009-09-16T19:39:00.000-07:002009-09-16T19:48:13.068-07:00THE VACUUM DIODE EXPOSED, Lee Bond N7KC<strong>September 16, 2009 Educational Radio Net, PSRG 69th Session</strong><br /><br />What a digital summer we experienced at the hands of Curt Black, WR5J! Curt pulled all the stops on a summers survey of free software downloads for your computer which, more or less, turned your radio into an analytical tool. As impressive as this tour was, one must ultimately realize that the most complex task that your computer performs is based on tiny packets of electrons or "charge" being directed here and there by the software commands. Elemental electrons in motion, or moving electric "charge", is the bottom line idea in electrical theory and all electrical devices including radio equipment.<br /><br />Let's review what we know about "charge". We know that it enjoys the symbol Q in the literature. We also know that it is an assembly of electrons and can be as few a one electron. We know that a collection of electrons numbering 6.14 x 10^18 is known as a Coulomb of charge. We know that charge will move under the influence of an electric field. We know that the original notion, or conventional notion, of charge was based on the erroneous idea that charge carried a positive sign hence moved in the direction of an applied electric field. Modern theory has reversed the original positive charge idea since electrons are negative entities and, in fact, move counter to the direction of any applied electric field. We know that charge can be motionless as in static charge. We know that an electrical current is charge in motion. It would seem that we know a lot about charge.<br /><br />The study of charge is best represented by the science of Physics with Physical Chemistry running a close second. The study of charge as it applies to the vacuum tube would come under the heading of Classical Newtonian Physics in contrast to the study of charge in semiconductor materials which would come under the heading of Modern Quantum Physics. In my view the vacuum tube represents the most elegant device for demonstrating the behavior of electrical charge influenced by an electric field. Lucky me to be raised in the heyday of the vacuum tube. As late as 1963 the US Navy destroyer to which I was assigned had a single piece of transmitting equipment that had modern solid state diodes in the circuitry. The selenium rectifier preceded germanium devices and modern silicon devices and required no heater but it is a stretch to include it as more than a rudimentary solid state device. The solid state transistor with all its ramifications is a relative newcomer to the field of electronics. Modern radio equipment's are solid state for the most part and only the old timers can relate stories of warming their hands in the glow of those magnificent glass bottles.<br /><br />No one has actually seen an electron. These entities are very, very tiny and to image them requires wavelengths small in comparison to the size of an electron. The one common instance of, more or less, stationary electrons occurs in the lattice structure of many crystals and x-ray crystallography has demonstrated diffraction images suggesting that these things are real. The fact that we can manipulate these tiny guys to the degree that we can is testimony to the very clever work of early scientists.<br /><br />We know that conductors have an abundance of so called "free" electrons. This is in contrast to tightly "bound" electrons which are not available to contribute to electric current flow. For example the neutral copper atom has 29 electrons associated with the nucleus in 4, so called, shells with the innermost shell containing 2 electrons followed by the next shell containing 8 electrons followed by the next shell containing 18 electrons followed by the outermost shell with a single, so called, valence electron. The three inner shells are tightly bound to the atomic nucleus but the outer single electron is easily forced out of place and can contribute to the electric current bumping along a copper wire. Most metals are conductors to varying degrees with silver, copper, and gold at the top. A copper atom missing its valence electron is known as a copper ion.<br /><br />I think we now have enough information to appreciate how a two terminal vacuum diode works so let's move on to some apparatus to demonstrate the effect. Forget the little glass bottle for the moment. We are going to use a laboratory bell jar and good quality vacuum pump as a part of our apparatus. Everyone has seen the "bell" jar on a stand with a mechanical vacuum pump attached. For our purposes the bell jar stand needs some electrical penetrations so that we can supply potentials to the bell jar innards. The first of the two inside devices is the filament or heater which also serves as a cathode. There are several schemes for heaters so let me select the one known as the directly heated filament cathode. This will be a tungsten wire section which will glow a bright red to orange when filament voltage is applied. Adjacent to the filament-cathode wire we will position a "plate" of flat metal such that it does not touch the filament. This metallic plate is, in fact, called the "plate" electrode in vacuum tube terminology and serves as the anode. Note that the plate may be cylindrical and surround the filament in real world devices.<br /><br />Our demonstration diode is complete. We have a filament (cathode) and plate (anode) plus a means of producing a good vacuum so on goes the bell jar but someone forgot to start the vacuum pump. Not realizing that a good vacuum is missing we switch on the filament voltage and sure enough the filament starts to light. Then there is a bright flash as the oxygen in the bell jar contributes to the destruction of the filament. Oops. Off with the jar and we install another filament wire. Ok, this time we turn on the pump and let it run until it chortles. Now when we flip the switch for the filament the wire glows a cheery orange. The chortling pump indicates that the internal vacuum (or pressure) is in the 1 to 10 micron range and suitable for our demonstration. The low internal pressure means that atoms of oxygen and nitrogen are scarce and will not interfere with the electronic process that we are interested in observing.<br /><br />Let's think about the filament voltage for a moment. I did not mention it but the source of the filament voltage is a battery. Traditionally the battery used for filament power is known as the "A" battery.<br /><br />So, here is our situation... we have a nicely glowing filament with an unconnected plate nearby and both are within a reasonably good vacuum. The glowing filament is probably heated to 800 degrees F or thereabouts and the thermal energy of the filament has caused lightly bound electrons to break free and form a cloud in the immediate vicinity of the filament-cathode. The thermal energy for breakaway is known as the work function and metals vary in this regard. Some substances such as barium offer very low work functions and are used in cooler, indirectly heated, cathode structures.<br /><br />Our cloud of electrons is negatively charged. If we cause the nearby plate element to become positively charged with respect to the filament-cathode then the electrons will move toward the plate anode and, since moving electrons constitute electrical current, we can measure a plate current if we insert some current measuring device in series with the plate. With regard to the plate, the battery traditionally used to supply plate voltage is known as the "B" battery hence follows the term B+ for the plate positive voltage supply.<br /><br />There is a third battery associated with vacuum tubes which is known as the "C" battery however it is not relevant here since we are using a two terminal device or diode and the C battery is only relevant in triode structures and beyond for grid biasing.<br /><br />At this point we have demonstrated that electrons will traverse a vacuum if the plate is positive with respect to the source of electrons. If the plate is negative relative to the source then the electrons are repelled and no plate current will flow. Herein lies the secret of the rectifying diode. If the plate is alternately positive then negative with respect to the cathode as would happen if connected to alternating mains then plate current only flows on positive excursions of plate voltage. Bi-directional current from AC mains becomes unidirectional current in the plate circuit. A single diode offers half wave rectification and a dual diode (or two individual diodes) offers full wave rectification.<br /><br />The high vacuum in the bell jar or little glass bottle performs two functions. First the pumping process removes virtually all oxygen so the filament suffers no oxidation. Secondly, the high vacuum is synonymous with low pressure both which equate to few residual gas particles present to hinder electron flow from cathode to plate anode. In reality small glass bottles with high internal temperatures will out gas damaging particles which will poison the vacuum so special devices known as "getters" are used internally to trap these vacuum destroyers.<br />Special attention must be given to the metal leads going through the little glass tube envelopes. If the glass and wire conductors do not expand and contract in the same manner with extreme changes in temperature then the seal will be broken and the tube will be rendered useless in short order. Special wire alloys which match the glass thermal characteristics are used to avoid this problem.<br /><br />In summary, the physics and mathematics associated with the classic vacuum tube is elegant and a fun pursuit for the very curious. The concept of electronic charge flow within a triode vacuum tube is easily grasped and directly applicable to field effect transistors. The natural extension from diode to triode by introducing a control grid between cathode and plate made possible amplification and the rest is history. <br /><br />This concludes the set up discussion for the Vacuum Diode. Are there any questions or comments with regard to tonight's discussion topic?<br /><br />This is N7KC for the Wednesday night Educational Radio NetAnonymousnoreply@blogger.com1tag:blogger.com,1999:blog-4632435085083780021.post-43260561847087575222009-09-09T00:35:00.000-07:002009-09-09T00:38:27.350-07:00Winlink 2000, Boone Barker KC7RK, no. 68<span style="font-weight: bold;font-size:130%;" >The Winlink 2000 System: E-Mail by Radio for Radio Amateurs<br /></span>Boone Barker, KC7RK<br /><br />Introduction<br />This paper provides a brief introduction to the Winlink 2000 system—what it is and how it works, and how to become a user.<br /><br />To start, here are a couple of defining quotes from the Winlink web site at www.winlink.org .<br /><br />“Winlink 2000 (WL2K) is a worldwide system of volunteer resources supporting e-mail by radio, with non-commercial links to internet e-mail.”<br /><br /> “To use the Winlink 2000 system, you must hold an Amateur Radio license or be a member of a supported organization or agency. Use of the system and all software is free of charge for those who qualify.”<br /><br />So Winlink is global, with access around the world. It is developed and supported entirely by volunteers. It is free. The system provides e-mail services to licensed Radio Amateurs without access to the internet such as mariners at sea or expeditions in remote areas.<br /><br />In addition, a growing number of government agencies and organizations have included WL2K in their emergency communication plans. Winlink 2000 can provide user -to-user e-mail services in a familiar format from inside a disaster area, using only a radio to connect to the outside world. <br /><br />Elements of Winlink 2000<br />At the heart of the WL2K system are five mirror image, redundant Common Message Server (CMS) hubs. They are located in San Diego (USA), Wein (Austria), Perth (Australia), Halifax (Canada), and Washington DC (USA). With this redundancy, the system will remain operational even if large segments of the internet are down.<br /><br />Connected to the five CMS sites are a multitude of Radio Message Server (RMS) nodes, like spokes on a wheel. Traffic flows between the CMS hubs and the internet e-mail recipient, and between the end users and the RMS gateways.<br /><br />As an aside, the term “PMBO” (for a participating mailbox) is being phased out, but still shows up in Winlink writings.<br /><br />The radio network has both RMS HF stations and RMS VHF/UHF Packet stations.<br /><br />RMS HF stations form a controlled and frequency-coordinated global network of Winlink stations. The HF stations all use Pactor, a digital ARQ mode that transfers text files and graphics quickly and error-free. Pactor 2 and 3, the faster modes, are only available on TNC’s produced by SCS in Germany. The WL2K Development Team is working on WINMOR, a new HF transmission protocol that will be freely distributed. It will complement, not replace Pactor; RMS HF stations will be able to handle both modes.<br /><br />RMS VHF/UHF Packet stations are also part of the network, providing automated messaging capability using AX.25 packet radio in combination with the WL2K Common Message Servers. Although limited in range, RMS Packet stations are widely available in the United States and a few other countries. RMS Packet can provide regular local access to Winlink, or a temporary emergency portal for radio e-mail users, or for fixed installation at unattended remote locations where it can provide radio e-mail communications to the “last mile.”<br /><br />The locations of public and emcomm RMS stations are shown in maps on the Winlink web site. Related status tables list station call sign, with frequency and mode and grid locator. Note that information about frequencies used by RMS HF emcomm stations is limited to authorized sysops and users.<br /><br />WL2K Client Software<br />Paclink is a Winlink 2000 radio e-mail client that links to common e-mail programs such as Outlook Express and Mozilla Thunderbird. Paclink adds telnet, VHF packet radio, HF Pactor radio and WINMOR HF radio channels for WL2K connectivity to compatible user e-mail client programs. Installation and configuration are relatively easy.<br /><br />Airmail is the oldest and most widely used e-mail program for sending and receiving messages on the Winlink system. Airmail supports HF Pactor, VHF/UHF Packet, and telnet connections over any TCP/IP medium including the internet and high-speed radio media like D-Star. Airmail also has position reporting capability, and a very nice HF propagation prediction program. It can be linked to common e-mail programs such as Outlook Express. Installation and configuration are somewhat difficult, but a nice guide is available; just Google “INSTALLATION AND SETUP FOR WINLINK AIRMAIL”.<br /><br />Airmail is a stand-alone e-mail program. The primary drawback of Airmail is that it only works with a short list of hardware modems. But it is well suited for WL2K HF connections using a Pactor modem. And the latest version of Airmail 3.3.081 can be used with AGW Packet Engine and a soundcard to make VHF/UHF packet connections, by installing AMPE software. See http://www.qsl.net/mararc/ampe.htm web site.<br /><br />On the other hand, Paclink has to be linked with an e-mail program. But it works with a wide variety of hardware TNC’s and modems and with AGW Packet Engine. TNC initialization scripts can be modified by the user. Also, scripts can be used to connect through a digipeater or packet node. CMS Telnet is simple and easy on Paclink, to send and receive WL2K messages on an internet connection.<br /><br />Both programs are free to download from the Winlink web site.<br /><br />Other software<br />AGW Packet Engine (AGWPE) handles traffic between your TNC or soundcard and packet programs that are configured to use AGWPE. It is free to download from the SV2AGW.com web site. A lengthy tutorial for installation and configuration is located at http://www.kc2rlm.info/soundcardpacket .<br /><br />Winlink 2000 RMS Packet gateways can also be accessed with regular packet software, to compose and send a message from the keyboard. Just connect to the RMS Packet node and read the greeting. Type H for help and then follow the instructions to compose a message. This is perhaps the easiest way to try out Winlink if you already have a packet setup.<br /><br />Hardware<br />For telnet connection to a CMS, the only hardware needed is a computer with internet access. WL2K e-mail through RMS Packet stations requires a VHF radio, a compatible TNC or modem or soundcard, and necessary interface cables.<br /><br />To connect with an RMS HF gateway on Pactor 1 requires that you have any one of the hardware TNC’s on setup lists in Airmail or Paclink. Pactor 2 or 3 requires that you have a Pactor TNC made by SCS . These cost $1,000 or more.<br /><br />How do you get started?<br />First and obviously, you need an amateur radio license. With that, here is a suggested initial sequence.<br /><br />Go to www.winlink.org, register on the web site, and download Paclink or Airmail—your choice. Install and configure the software for telnet to a CMS site. Compose a test message to your internet e-mail address. Send the message using the telnet connection. When that is successful, reply to your Winlink e-mail address.<br /><br />Another option: if you already have an operational packet setup, use it to connect to a local RMS Packet node. The Winlink web site has a map that shows all of the active RMS Packet stations. Just zoom in on your local area and pick them out. Then go to the Reports tab on the Winlink Web site, scroll down to RMS Packet Status, and look up frequencies of those stations in the table. Sometimes these local nodes are not functioning. So if you don’t get a connection, try another station.<br /><br />With your first radio or telnet e-mail you will be registered in the WL2K system. Your e-mail address will be [your call]@winlink.org.<br /><br />You can use WL2K client software with packet and your TNC if it is listed in the setup for Paclink Packet TNC Channels or in Airmail VHF Packet Client Setup. Check out the TNC using a simple terminal program. Then try connecting to one of the local RMS Packet stations.<br /><br />If you want to use a soundcard for packet, first download and install AGW Packet Engine. Create a new radioport for your soundcard. Then configure Paclink or Airmail to use AGWPE. Remember that Airmail requires that AMPE be running. There is a link to AGWPE is the Airmail TNC list but it is not functional.<br /><br />You might also want to download AGWTerninal, and AGWMonitor from the SV2AGW web site. They are free. AGW Monitor lets you see all the traffic to and from your TNC/modem/soundcard, and AGWTerminal is a nice simple terminal program. AGWTracker is a simple APRS program, also nice. All require that AGWPE or Packet Engine Pro be running.<br /><br />If an online course is to your liking, there is a “Winlink for Dummies” course that takes you through all the steps. It can be accessed through www/winlink.org/GetStarted. <br /><br />Some recommendations<br />You should always format WL2K e-mail messages in plain text. HTML format adds unnecessary bytes to the message. Attachments should be made as small as possible.<br /><br />Learn about the Winlink Whitelist and how to work with it. This is an anti-spam filter. E-mails to your Winlink e-mail address need to have //WL2K in the subject line or they will be rejected—unless they come from an e-mail account on your Whitelist. E-mail addresses on outgoing messages are automatically added to your Whitelist.<br /><br />When you configure a radioport in AGWPE for SignaLink USB, select an unused printer port (LPT3) as your PTT port. It’s easy to hang up at this point in the setup.<br /><br />Summary<br />Winlink 2000 has been used since 1999 by Radio Amateurs at sea and in the jungles to send e-mail messages by radio. As a result of experience in Katrina recovery operations and other disasters, Winlink has been included in operational plans of a growing number of emcomm organizations such as RACES and ARES units, Red Cross, MARS, Baptist Relief, and the Salvation Army.<br /><br />Another defining quote from the Winlink web site:<br /><br />“The WL2K mission is to provide, through a volunteer network, effective last resort communications in civil emergencies and personal communications in non-emergency conditions.”<br /><br />As a Radio Amateur, you may already have experience with packet radio—that’s all you need to access Winlink by radio. Another simple start involves connecting by telnet over the internet. And if you are already a Winlink user, you might consider becoming the sysop for your own RMS Packet station. Software and guidelines are on the web site.<br /><br />So have fun setting up Winlink and trying it out. It might well be very useful in an emergency, to you and to your community.<br /><br />September 9, 2009Bob Hellinghttp://www.blogger.com/profile/02352636352618704676noreply@blogger.com0tag:blogger.com,1999:blog-4632435085083780021.post-40079166148914967272009-09-01T22:58:00.000-07:002009-09-02T19:51:54.601-07:00Spread Spectrum Communications, Bob, no. 67Tonight's topic, spread spectrum communications, may seem to be the stuff of spy fiction and ultra-expensive military hardware, but you have almost certainly used spread spectrum whether you know it or not and you probably have the sophisticated spread spectrum radio gear right in your own house. I'm talking about wireless networking gear, also known as WiFi. More on that later.<br /><br /><span style="font-weight: bold;">WHAT IS SPREAD SPECTRUM?</span><br />According to the ARRL Handbook, spread spectrum is defined as using an RF bandwidth much larger than needed to carry the signal, and where the bandwidth of the signal is independent of the modulation by the signal. It is a form of radio transmission that makes use of a wide bandwidth to avoid interference by noise or other signals. You can imagine that if you are transmitting a simple AM signal over 100 frequencies at the same time then someone transmititng on any one of those frequencies will only contribute one percent toward the final recombined signal. This would be fine until you had someone else also transmitting an AM signal on the same 100 frequencies. Then you would be back to a big interference problem. Partly in order to allow hams to use the same frequency range, there are more sophisticated ways to use those multiple frequencies. We will discuss those in a moment.<br /><br /><span style="font-weight: bold;"><span style="font-weight: bold;">SPREAD SPECTRUM TRADE-OFFS</span></span><span><br />In general, spread spectrum transmissions offer three big advantages:<br /></span><ul><li>Relative Immunity to Interference<br />As described above, unless someone else is using the very same spread spectrum technique and is synchronized with you, you likely won't notice the interference</li><li>Security<br />As we will see, there are sophisticated ways to encrypt a signal. This is why it is still valuable to the military.</li><li>Lower Power Density<br />By spreading the signal over a range of frequencies, the power at any given frequency is so low it can be below the noise floor and unnoticed.</li></ul>There is only one real trade-off and that is the technical complexity necessary to accomplish spread spectrum.<br /><br /><br /><span style="font-weight: bold;">HISTORY OF SPREAD SPECTRUM</span><br />In a sense you could say that spread spectrum began with the earliest radio transmitters. Spark gap transmitters created CW signals that covered a very broad spectrum. You could charitably say that this signal could get through interfering signals but really, it was more of an interfering signal.<br /><br />Early experiments with intentional spread spectrum began in the late 20's but it was World War II and the military that really pushed the technology forward. Unfortunately, because spread spectrum is still used by the military, much of the history is still kept secret.<br /><br /><br /><span style="font-weight: bold;">SPREAD SPECTRUM IN HAM RADIO</span><br />In 1981, a group called the Amateur Radio Research and Development Corporation (AMRAD) began experimentation with spread spectrum. In 1989 an idea was put forth to use the Wireless LAN (WLAN) devices in ham radio, and in 1999 the FCC relaxed their rules about hams using spread spectrum. This relaxation opened the door for hams to use equipment already being made for WLAN.<br /><br />Analog signals can be carried over spread spectrum transmissions, but nearly all spread spectrum use today is with digital signals and that is what we will discuss.<br /><br /><span style="font-weight: bold;">COMMON TYPES</span><br />Frequency Hopping Spread Spectrum (FHSS)<br />As the name implies, the transmitting frequency hops around in a pre-arranged pattern. In the 802.11 spec, there are 3 sets of 26 such patterns using 75 frequencies. By some clever hopping algorithms you can have 802.11 devices using different sequences, or channels, on the same 75 frequencies without interfering with each other. Because there are only 78 sequences, a receiving device could discover the channel being used by the various transmitters and sync up with one.<br /><br />Direct-Sequence Spread Spectrum (DSSS)<br />In this method, a pseudo-random code is used to modulate the signal and drive a phase modulator using phase shift keying. I have to admit this it getting into the fringes of what I know so I am going to leave it at that.<br />Note that by using a pseudo-random code that is not generally known it would be possible to securely encrypt a signal with DSSS. Of course we are not allowed to do that in amateur radio and we avoid that pitfall by using published codes as can be found on the ARRL web site.<br /><br />Orthogonal Frequency Division Modulation (OFDM)<br />This method is more like what you may think when you think of spread spectrum. In this mode, the signal is transmitted on 52 carrier frequencies simultaneously. Four of these are called pilot carriers and they help provide the synchronization. The other 48 each transmit independent bit streams so at any given time, 48 bits are being transmitted at once. The reason it is called orthogonal is that the frequencies and modulation patterns are chosen so that each frequency falls in the null of the neighboring frequencies.<br /><br /><span style="font-weight: bold;">THE FUTURE</span><br />Since this mode is so new and underutilized in ham radio, I'm going to do something I don't normally do and that is predict the future of spread spectrum. It is here to stay until something better comes along and, though it may not happen, I wouldn't be surprised to see it adopted in the low bands eventually. I know some of the new digital modes use it to some degree and I can see the FCC, being the pragmatists they are, expanding the use of it as the technology allows.<br /><br />I want to acknowledge two primary sources for tonights lesson. The ARRL Handbook, a wealth of all things Ham; and <a href="http://sss-mag.com/">Spread Spectrum Scene</a> which I barely scratched the surface of.Bob Hellinghttp://www.blogger.com/profile/02352636352618704676noreply@blogger.com1tag:blogger.com,1999:blog-4632435085083780021.post-35300525132796319812009-08-25T22:29:00.000-07:002009-08-25T22:37:41.573-07:00Reminder - Educational Radio Net Wednesday night 8:00pm and Last Summer of Digital Fun PostReminder - Educational Radio Net Wednesday night 8:00pm PSRG 146.96<br /><br />For the new folks on this WA-DIGITAL list, the Summer of Digital Fun Series<br />finishes up this Wednesday on the PSRG machine, 146.96 (-600 kHz offset, 103.5<br />tone)in Seattle.<br /><br />All are welcome.<br /><br />Make no mistake, the Educational Radio Nets will continue and the Digital Series<br />will also continue, but for things digital, probably once or so per month as we<br />keep exercising with these amazing modes.<br /><br />I was tempted to talk about the Automatic Position Reporting System, APRS - a<br />tasty flavor of packet radio. Just eavesdrop on 144.39 for a sense of how<br />popular this mode is. However, it seems the last couple of weeks have seriously<br />challenged the group which has been winnowed down to just a few players. I hope<br />folks will pursue APRS on their own or contact me off list for any help they<br />might need with that system - it is really a blast. For lots of help including<br />a well developed Elmering program, check out http://www.nwaprs.info/ or just<br />look at the cool maps at http://aprs.fi/<br /><br />So, for this last Summer Session we'll have more digital fun with a recap of<br />what we've done through the summer. Please begin the net with FLDIGI up and<br />running with acoustic coupling between your radio and the computer.<br /><br />The best way to enjoy the Educational Radio Net is to have your software set up<br />and running as the net starts at 8:00.<br /><br />If you have an interface, hook it up to your two-meter rig, otherwise use<br />acoustic coupling with a microphone feeding shack audio into your computer and<br />the rig audio softly coming out of a speaker in the room with you fairly close<br />to the mic.<br /><br />If this is your first session, no problem. Pull the software off the WA-DIGITAL<br />files section and install it. Tune in and we'll go over set up of the software<br />during the session. The software is on the WA-DIGITAL yahoo group. If you are<br />using VISTA, please load the version FLDIGI 3.11.4-WinV. When the update went<br />to 3.12.4 for all windows systems, something bad happened, and VISTA stopped<br />working. There are Linux and Mac versions of the software as well - just Google<br />NBEMS or go to http://www.w1hkj.com/ .<br /><br />Posts 2 and 3 go into setting up for FLDIGI. The first part of Post #4<br />describes the set up for acoustic coupling. IF you are set up for acoustic<br />coupling, you should see a difference in the waterfall as you open and close the<br />squelch on the rig you are using to monitor the PSRG machine. If you don't, go<br />to the CONFIGURATION menu and the AUDIO tab, then devices to point the software<br />to the audio source.<br /><br />We will start out tonight with a blast of MT-63 preceded with an RS-ID to<br />automatically switch your software to the correct mode and frequency, so get<br />ready to receive on the output of the PSRG machine, 146.96. Remember to setup<br />FLDIGI with menu item CONFIGURATION, then under the ID tab to check the box next<br />to "TRANSMIT MODE RSID" and "RSID SEARCHES ENTIRE PASSBAND" Finally on the main<br />receive screen, be sure and check the little box up in the upper right corner of<br />the screen labeled "RS-ID" so that a green light is visible indicating you are<br />ready to switch modes and frequency when the signal is received. This feature<br />has to be turned on each time you want to use it - mostly to keep from being<br />wrenched out of an ongoing QSO by receiving another RS-ID.<br /><br />If you have trouble with copy during the net, you might check the input of the<br />repeater to see if that is better for you. Several folks sent messages last week<br />suggesting that.<br /><br />See you on the Net.<br /><br />Hopefully this will be just the beginning of some great digital adventures.<br /><br />I would like to suggest we continue using the WA-DIGITAL mail reflector to<br />schedule digital QSOs with other folks, also don't forget<br />http://www.obriensweb.com/sked/ to set up SKEDS or WSPRNET.ORG to monitor your<br />received whisperings.<br /><br />Also, please consider joining the Pennsylvania NBEMS group via Echolink on a<br />local repeater or in the privacy of your home computer. The Pittsburgh hams have<br />been having a net using about 50% voice and 50% MT-63. We may join them by<br />Echolink by connecting to W3YJ-R (node 177325) at 5:00pm Sunday evenings (8:00pm<br />Eastern Time).<br /><br />After the 5:00pm net I would like to suggest we retire to the SEA machine on<br />145.010 simplex. (just "Connect SEA" and then type "TALK" to join the group and<br />//ex to leave (the instructions come up when you join.)<br /><br />As the fall comes on, I would like to suggest we dive into some of the major<br />pieces of software available and checkout all that they are capable of - I'm<br />thinking of MULTIPSK which does way more than just PSK, and HAM RADIO DELUXE -<br />HRD with D780 for digital modes - a beautiful piece of software.<br /><br />Our continuing thanks to the PSRG for the use of the repeater for this net and<br />so many others that enhance our radio community.<br /><br /><br />vy 73 de WR5J<br /><br />Curt Black<br />black@nwfirst.com<br /><br /><br />As a reminder, here is what we covered this summer:<br /><br />Blog Post - #1 Intro to Digital Communication, Software and Modes Wednesday,<br />June 3, 2009<br /><br />Blog Post - #2 Intro to FLDIGI – Install, Setup and Mode Selection, Wednesday,<br />June 10, 2009<br /><br />Blog Post - #3 Using FLDIGI – Starting with PSK-31 and Transmitting a Good<br />Signal Wednesday, June 24<br /><br />Blog Post - #4 More FLDIGI – RTTY, the WRAP Utility and RS-ID, Wednesday July 1,<br />2009<br /><br />Blog Post - #5 WSPR – Weak Signal Propagation Reporter, Wednesday July 8, 2009<br /><br />Blog Post - #6 MMSSTV/EasyPAL, Slow Scan Image Transmission, Wednesday July 15,<br />2009<br /><br />Blog Post - #7 Digital SSTV (week 2) EasyPAL, Wednesday July 22, 2009<br /><br />Blog Post - #8 WSJT-JT65A – Terrestrial HF, Wednesday July 29, 2009<br /><br />Blog Post - #9 WSJT-HS-Meteor Scatter, Wednesday August 5, 2009<br /><br />Blog Post - #10 Packet Radio Using Flex32, Wednesday August 12, 2009<br /><br />Blog Post - #11 Packet Radio Using AGW Packet Engine, Wednesday August 19,<br />2009<br /><br />Blog Post - #12 WINDRM – Digital Voice and HRD/DM780, Wednesday August 26, 2009<br /><br />OK - we didn't really do WINDRM - take a look at the blog post and you will see<br />why - we still might give it a try, but it is the same modulation approach used<br />by EasyPAL and that didn't fly very far through the PSRG machine - However, we<br />did very well with an after-net on the 444.550 WW7SEA machine - as in perfect<br />copy and 22dB S/N ratios. We've got to find out what that is about...WR5Jhttp://www.blogger.com/profile/16316513702643319581noreply@blogger.com0tag:blogger.com,1999:blog-4632435085083780021.post-79634607857086951792009-08-25T13:09:00.000-07:002009-08-25T13:15:04.720-07:00Blog-Post-12 – WinDRM—Digital Data and Voice Using Digital Radio Mondiale<meta equiv="Content-Type" content="text/html; charset=utf-8"><meta name="ProgId" content="Word.Document"><meta name="Generator" content="Microsoft Word 11"><meta name="Originator" content="Microsoft Word 11"><link rel="File-List" href="file:///C:%5CDOCUME%7E1%5Ccblack%5CLOCALS%7E1%5CTemp%5Cmsohtml1%5C02%5Cclip_filelist.xml"><link rel="Edit-Time-Data" href="file:///C:%5CDOCUME%7E1%5Ccblack%5CLOCALS%7E1%5CTemp%5Cmsohtml1%5C02%5Cclip_editdata.mso"><!--[if !mso]> <style> v\:* {behavior:url(#default#VML);} o\:* {behavior:url(#default#VML);} w\:* {behavior:url(#default#VML);} .shape {behavior:url(#default#VML);} </style> <![endif]--><o:smarttagtype namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="City"></o:smarttagtype><o:smarttagtype namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="PlaceName"></o:smarttagtype><o:smarttagtype namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="PlaceType"></o:smarttagtype><o:smarttagtype namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="place"></o:smarttagtype><o:smarttagtype namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="State"></o:smarttagtype><!--[if gte mso 9]><xml> <w:worddocument> <w:view>Normal</w:View> <w:zoom>0</w:Zoom> <w:punctuationkerning/> <w:validateagainstschemas/> <w:saveifxmlinvalid>false</w:SaveIfXMLInvalid> <w:ignoremixedcontent>false</w:IgnoreMixedContent> <w:alwaysshowplaceholdertext>false</w:AlwaysShowPlaceholderText> <w:compatibility> <w:breakwrappedtables/> <w:snaptogridincell/> <w:wraptextwithpunct/> <w:useasianbreakrules/> <w:dontgrowautofit/> </w:Compatibility> <w:browserlevel>MicrosoftInternetExplorer4</w:BrowserLevel> </w:WordDocument> </xml><![endif]--><!--[if gte mso 9]><xml> <w:latentstyles deflockedstate="false" latentstylecount="156"> </w:LatentStyles> </xml><![endif]--><!--[if !mso]><object classid="clsid:38481807-CA0E-42D2-BF39-B33AF135CC4D" id="ieooui"></object> <style> st1\:*{behavior:url(#ieooui) } </style> <![endif]--><style> <!-- /* Font Definitions */ @font-face {font-family:TimesNewRomanPS-ItalicMT; panose-1:0 0 0 0 0 0 0 0 0 0; mso-font-alt:Arial; mso-font-charset:0; mso-generic-font-family:swiss; mso-font-format:other; mso-font-pitch:auto; mso-font-signature:6147 0 0 0 33 0;} @font-face {font-family:TimesNewRomanPS-BoldMT; panose-1:0 0 0 0 0 0 0 0 0 0; mso-font-alt:Arial; mso-font-charset:0; mso-generic-font-family:swiss; mso-font-format:other; mso-font-pitch:auto; mso-font-signature:8195 0 0 0 65 0;} @font-face {font-family:Arial-BoldMT; panose-1:0 0 0 0 0 0 0 0 0 0; mso-font-alt:Arial; mso-font-charset:0; mso-generic-font-family:swiss; mso-font-format:other; mso-font-pitch:auto; mso-font-signature:8195 0 0 0 65 0;} @font-face {font-family:Arial-BoldItalicMT; panose-1:0 0 0 0 0 0 0 0 0 0; mso-font-charset:0; mso-generic-font-family:swiss; mso-font-format:other; mso-font-pitch:auto; mso-font-signature:3 0 0 0 1 0;} @font-face {font-family:Arial-ItalicMT; panose-1:0 0 0 0 0 0 0 0 0 0; mso-font-alt:Arial; mso-font-charset:0; mso-generic-font-family:swiss; mso-font-format:other; mso-font-pitch:auto; mso-font-signature:6147 0 0 0 33 0;} /* Style Definitions */ p.MsoNormal, li.MsoNormal, div.MsoNormal {mso-style-parent:""; margin:0in; margin-bottom:.0001pt; mso-pagination:widow-orphan; font-size:12.0pt; font-family:"Times New Roman"; mso-fareast-font-family:"Times New Roman";} h3 {mso-margin-top-alt:auto; margin-right:0in; mso-margin-bottom-alt:auto; margin-left:0in; mso-pagination:widow-orphan; mso-outline-level:3; font-size:13.5pt; font-family:"Times New Roman"; font-weight:bold;} a:link, span.MsoHyperlink {color:blue; text-decoration:underline; text-underline:single;} a:visited, span.MsoHyperlinkFollowed {color:#606420; text-decoration:underline; text-underline:single;} p {mso-margin-top-alt:auto; margin-right:0in; mso-margin-bottom-alt:auto; margin-left:0in; mso-pagination:widow-orphan; font-size:12.0pt; font-family:"Times New Roman"; mso-fareast-font-family:"Times New Roman";} @page Section1 {size:8.5in 11.0in; margin:1.0in 1.25in 1.0in 1.25in; mso-header-margin:.5in; mso-footer-margin:.5in; mso-paper-source:0;} div.Section1 {page:Section1;} --> </style><!--[if gte mso 10]> <style> /* Style Definitions */ table.MsoNormalTable {mso-style-name:"Table Normal"; mso-tstyle-rowband-size:0; mso-tstyle-colband-size:0; mso-style-noshow:yes; mso-style-parent:""; mso-padding-alt:0in 5.4pt 0in 5.4pt; mso-para-margin:0in; mso-para-margin-bottom:.0001pt; mso-pagination:widow-orphan; font-size:10.0pt; font-family:"Times New Roman"; mso-ansi-language:#0400; mso-fareast-language:#0400; mso-bidi-language:#0400;} </style> <![endif]--> <h3 style="margin-right: -0.25in;"><a name="6302631280933418248"></a><u><span style="color: rgb(51, 102, 255);"><a href="http://educationalradionet.blogspot.com/2009/07/blog-post-5-fldigi-wrap-up-review-and.html"><span style="color: rgb(51, 102, 255);">Blog Post 12 – WinDRM—</span></a>Digital Data and Voice Using Digital Radio Mondiale on the Han Bands <o:p></o:p></span></u></h3> <p class="MsoNormal" style="margin: 0in -0.25in 0.0001pt -27pt;"><i style=""><span style="font-size: 9pt; color: rgb(51, 102, 255);"><span style=""> </span></span></i><i style=""><span style="font-size: 9pt;"><o:p></o:p></span></i></p> <p class="MsoNormal" style="margin: 0in -0.25in 0.0001pt -27pt; text-indent: 27pt;"><span style="color: black;">Wednesday August 26, 2009</span></p> <p class="MsoNormal" style="margin-right: -0.25in;"><b><span style="font-size: 16pt;">This is Curt Black, WR5J, with the Educational Radio Net –<o:p></o:p></span></b></p> <p class="MsoNormal" style="margin-right: -0.25in;"><b><span style="font-size: 16pt;">Please standby for a WinDRM Digital QST <o:p></o:p></span></b></p> <p class="MsoNormal" style="margin-right: -0.25in;"><b><span style="font-size: 16pt;"><o:p> </o:p></span></b></p> <p class="MsoNormal" style=""><b><span style="font-size: 16pt;">OK, we are out of time for the Summer of Digital Fun, but I had prepared some material for this mode, so here is what I have so far.<span style=""> </span><o:p></o:p></span></b></p> <p class="MsoNormal" style=""><b><span style="font-size: 16pt;"><o:p> </o:p></span></b></p> <p class="MsoNormal" style=""><b><span style="font-size: 16pt;">The problem with these digital voice modes is the loss of the use of a proprietary <span style=""> </span>codec<span style=""> </span>- here is a recent message from Mel Whitten:<o:p></o:p></span></b></p> <p class="MsoNormal" style=""><span style="font-size: 14pt; color: black;"><mel@melwhitten.com></span><span style="font-size: 14pt; color: black;"> <o:p></o:p></span></p> <p class="MsoNormal" style=""><b style=""><span style="font-size: 14pt; color: black;">Curt,<o:p></o:p></span></b></p> <p class="MsoNormal" style=""><b style=""><span style="font-size: 14pt; color: black;">The MELP codec is no longer available because it was brought to<o:p></o:p></span></b></p> <p class="MsoNormal" style=""><b style=""><span style="font-size: 14pt; color: black;">The attention of one of the IP holders that we were using it.<span style=""> </span>I <o:p></o:p></span></b></p> <p class="MsoNormal" style=""><b style=""><span style="font-size: 14pt; color: black;">don't think the IP holder would really "care" because of the way<o:p></o:p></span></b></p> <p class="MsoNormal" style=""><b style=""><span style="font-size: 14pt; color: black;">we were using MELP, but when confronted by this "person" in writing..<o:p></o:p></span></b></p> <p class="MsoNormal" style=""><b style=""><span style="font-size: 14pt; color: black;">then the IP holder had to defend his property.<span style=""> </span>Thus, we are left<o:p></o:p></span></b></p> <p class="MsoNormal" style=""><b style=""><span style="font-size: 14pt; color: black;">with LPC-10, which does not sound "too bad" and could be used to<o:p></o:p></span></b></p> <p class="MsoNormal" style="margin-right: -0.25in;"><b style=""><span style="font-size: 14pt; color: black;">demonstrate capability.<span style=""> </span></span></b><b><span style="font-size: 14pt;"><o:p></o:p></span></b></p> <p class="MsoNormal" style=""><b style=""><span style="font-size: 14pt;">…<span style="color: black;"> 14.236 is calling/net freq for digital voice.<span style=""> </span>Some stations may be<o:p></o:p></span></span></b></p> <p class="MsoNormal" style=""><b style=""><span style="font-size: 14pt; color: black;">heard around noon central time.<span style=""> </span>Nets are still run (summer time thy're<o:p></o:p></span></b></p> <p class="MsoNormal" style=""><b style=""><span style="font-size: 14pt; color: black;">not as frequent) on Sat and Sun on the times given on the web site.<o:p></o:p></span></b></p> <p class="MsoNormal" style=""><b style=""><span style="font-size: 14pt; color: black;">keep in mind, that you may find FDMDV, AOR's DV and WinDRM on these frequencies.<span style=""> </span>FDMDV suffered the most from the loss of MELP and does not sound very good with the lower bit rate LPC-10 but it has "instant" sync and simple to use.<span style=""> </span>With MELP, FDMDV was a real winner. Work <span style=""> </span>continues to find a replacement, but this is very difficult.<span style=""> </span>There are<span style=""> </span>no "legal" problems with any DV using MELP or SPEEX codecs.<span style=""> </span>They are both open source.<span style=""> </span>DV is about dead and probably will remain that way until a MELP equivalent codec is found or some new technology is found.<span style=""> </span>AOR's DV is not robust enough to cope with current poor band conditions do to low sun spot activity. It does work very good with at least S9 signals and no QRM.<span style=""> </span>Excellent voice quality but so -was- WinDRM with MELP.<span style=""> </span><o:p></o:p></span></b></p> <p class="MsoNormal" style=""><b style=""><span style="font-size: 14pt; color: black;"><o:p> </o:p></span></b></p> <p class="MsoNormal" style=""><b style=""><span style="font-size: 14pt; color: black;">Channelization for DV would be optimum.<span style=""> </span>QRM is a real problem from SSB.<span style=""> </span>FCC rules say DV must operate in the Voice sub-bands. . .</span></b></p><p class="MsoNormal" style=""><<<end>>>
<br /><b style=""><span style="font-size: 14pt; color: black;"><o:p></o:p></span></b></p> <p class="MsoNormal"><b style=""><span style="font-size: 14pt;"><o:p> </o:p></span></b></p> <p class="MsoNormal"><b style=""><span style="font-size: 14pt;">The software is on the Yahoo WA-DIGITAL files section <a href="http://groups.yahoo.com/group/wa-digital/files/">http://groups.yahoo.com/group/wa-digital/files/</a><o:p></o:p></span></b></p> <p class="MsoNormal"><b style=""><span style="font-size: 14pt;"><o:p> </o:p></span></b></p> <p class="MsoNormal"><b style=""><span style="font-size: 14pt;">It sounds like the loss of the Codec may have delt a fatal blow – but here is the installation and use information for those who might want to experiment – 73 de WR5J<o:p></o:p></span></b></p> <p class="MsoNormal"><b style=""><span style="font-size: 14pt;"><o:p> </o:p></span></b></p> <p class="MsoNormal"><b style=""><span style="font-size: 14pt;"><o:p> </o:p></span></b></p> <p class="MsoNormal"><!--[if gte vml 1]><v:shapetype id="_x0000_t75" coordsize="21600,21600" spt="75" preferrelative="t" path="m@4@5l@4@11@9@11@9@5xe" filled="f" stroked="f"> <v:stroke joinstyle="miter"> <v:formulas> <v:f eqn="if lineDrawn pixelLineWidth 0"> <v:f eqn="sum @0 1 0"> <v:f eqn="sum 0 0 @1"> <v:f eqn="prod @2 1 2"> <v:f eqn="prod @3 21600 pixelWidth"> <v:f eqn="prod @3 21600 pixelHeight"> <v:f eqn="sum @0 0 1"> <v:f eqn="prod @6 1 2"> <v:f eqn="prod @7 21600 pixelWidth"> <v:f eqn="sum @8 21600 0"> <v:f eqn="prod @7 21600 pixelHeight"> <v:f eqn="sum @10 21600 0"> </v:formulas> <v:path extrusionok="f" gradientshapeok="t" connecttype="rect"> <o:lock ext="edit" aspectratio="t"> </v:shapetype><v:shape id="_x0000_i1025" type="#_x0000_t75" style="'width:477pt;"> <v:imagedata src="file:///C:\DOCUME~1\cblack\LOCALS~1\Temp\msohtml1\02\clip_image001.emz" title=""> </v:shape><![endif]--><!--[if !vml]-->
<br /><!--[endif]--></p> <p class="MsoNormal"><o:p> </o:p></p> <p class="MsoNormal"><o:p> </o:p></p> <p class="MsoNormal"><o:p> </o:p></p><meta equiv="Content-Type" content="text/html; charset=utf-8"><meta name="ProgId" content="Word.Document"><meta name="Generator" content="Microsoft Word 11"><meta name="Originator" content="Microsoft Word 11"><link rel="File-List" href="file:///C:%5CDOCUME%7E1%5Ccblack%5CLOCALS%7E1%5CTemp%5Cmsohtml1%5C02%5Cclip_filelist.xml"><link rel="Edit-Time-Data" href="file:///C:%5CDOCUME%7E1%5Ccblack%5CLOCALS%7E1%5CTemp%5Cmsohtml1%5C02%5Cclip_editdata.mso"><!--[if !mso]> <style> v\:* {behavior:url(#default#VML);} o\:* {behavior:url(#default#VML);} w\:* {behavior:url(#default#VML);} .shape {behavior:url(#default#VML);} </style> <![endif]--><!--[if gte mso 9]><xml> <w:worddocument> <w:view>Normal</w:View> <w:zoom>0</w:Zoom> <w:punctuationkerning/> <w:validateagainstschemas/> <w:saveifxmlinvalid>false</w:SaveIfXMLInvalid> <w:ignoremixedcontent>false</w:IgnoreMixedContent> <w:alwaysshowplaceholdertext>false</w:AlwaysShowPlaceholderText> <w:compatibility> <w:breakwrappedtables/> <w:snaptogridincell/> <w:wraptextwithpunct/> <w:useasianbreakrules/> <w:dontgrowautofit/> </w:Compatibility> <w:browserlevel>MicrosoftInternetExplorer4</w:BrowserLevel> </w:WordDocument> </xml><![endif]--><!--[if gte mso 9]><xml> <w:latentstyles deflockedstate="false" latentstylecount="156"> </w:LatentStyles> </xml><![endif]--><style> <!-- /* Style Definitions */ p.MsoNormal, li.MsoNormal, div.MsoNormal {mso-style-parent:""; margin:0in; margin-bottom:.0001pt; mso-pagination:widow-orphan; font-size:12.0pt; font-family:"Times New Roman"; mso-fareast-font-family:"Times New Roman";} @page Section1 {size:8.5in 11.0in; margin:1.0in 1.25in 1.0in 1.25in; mso-header-margin:.5in; mso-footer-margin:.5in; mso-paper-source:0;} div.Section1 {page:Section1;} --> </style><!--[if gte mso 10]> <style> /* Style Definitions */ table.MsoNormalTable {mso-style-name:"Table Normal"; mso-tstyle-rowband-size:0; mso-tstyle-colband-size:0; mso-style-noshow:yes; mso-style-parent:""; mso-padding-alt:0in 5.4pt 0in 5.4pt; mso-para-margin:0in; mso-para-margin-bottom:.0001pt; mso-pagination:widow-orphan; font-size:10.0pt; font-family:"Times New Roman"; mso-ansi-language:#0400; mso-fareast-language:#0400; mso-bidi-language:#0400;} </style> <![endif]--><span style="font-size: 12pt; font-family: "Times New Roman";"><!--[if gte vml 1]><v:shapetype id="_x0000_t75" coordsize="21600,21600" spt="75" preferrelative="t" path="m@4@5l@4@11@9@11@9@5xe" filled="f" stroked="f"> <v:stroke joinstyle="miter"> <v:formulas> <v:f eqn="if lineDrawn pixelLineWidth 0"> <v:f eqn="sum @0 1 0"> <v:f eqn="sum 0 0 @1"> <v:f eqn="prod @2 1 2"> <v:f eqn="prod @3 21600 pixelWidth"> <v:f eqn="prod @3 21600 pixelHeight"> <v:f eqn="sum @0 0 1"> <v:f eqn="prod @6 1 2"> <v:f eqn="prod @7 21600 pixelWidth"> <v:f eqn="sum @8 21600 0"> <v:f eqn="prod @7 21600 pixelHeight"> <v:f eqn="sum @10 21600 0"> </v:formulas> <v:path extrusionok="f" gradientshapeok="t" connecttype="rect"> <o:lock ext="edit" aspectratio="t"> </v:shapetype><v:shape id="_x0000_i1025" type="#_x0000_t75" style="'width:477pt;"> <v:imagedata src="file:///C:\DOCUME~1\cblack\LOCALS~1\Temp\msohtml1\02\clip_image001.emz" title=""> </v:shape><![endif]--><!--[if !vml]--><img src="file:///C:/DOCUME%7E1/cblack/LOCALS%7E1/Temp/msohtml1/02/clip_image002.gif" shapes="_x0000_i1025" width="636" height="428" /><!--[endif]--></span><p class="MsoNormal"><o:p> </o:p></p> <p class="MsoNormal"><o:p> </o:p></p> <p class="MsoNormal"><o:p> </o:p></p> <p class="MsoNormal"><o:p> </o:p></p> <p class="MsoNormal"><o:p> </o:p></p> <p class="MsoNormal"><a href="http://n1su.com/windrm/download.html">http://n1su.com/windrm/download.html</a></p> <p class="MsoNormal"><o:p> </o:p></p> <p class="MsoNormal" style=""><i><span style="font-family: TimesNewRomanPS-ItalicMT; color: black;">WinDRM Docs </span></i><i><span style="font-family: TimesNewRomanPS-ItalicMT; color: black;">– </span></i><i><span style="font-family: TimesNewRomanPS-ItalicMT; color: black;">Release 1.3 </span></i><span style="color: black;">was developed by Cesco, HB9TLK from a relatively new broadcast</span><i><span style="font-family: TimesNewRomanPS-ItalicMT; color: black;"> </span></i><span style="color: black;">standard called Digital Radio Mondiale (DRM) and it’s open source</span><i><span style="font-family: TimesNewRomanPS-ItalicMT; color: black;"><o:p></o:p></span></i></p> <p class="MsoNormal" style=""><span style="color: black;">encoder/decoder named Dream (</span><span style="color: blue;">http://drm.sourceforge.net/</span><span style="color: black;">). DRM is based on a proven<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">data communications technology called Coded Orthogonal Frequency Division<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">Multiplexing (COFDM) with Quadrature Amplitude Modulation (QAM). COFDM uses<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">many parallel narrow band sub-carriers instead of just one single wide band carrier for<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">transporting the data. As a result, WinDRM provides an efficient and robust method to<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">exchange information over HF including Digital Voice using open source CODECs.<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">WinDRM utilizes Forward Error Correction (FEC) and an Automatic-Repeat-Request<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">(ARQ) mode to ensure error free data transfers. WinDRM runs efficiently under<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">Windows operating system 2000 and XP. No modifications are required for modern SSB<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">HF ham transceivers. Current releases of WinDRM software may be found at<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: blue;">www.n1su.com/windrm</span><span style="color: black;">. Other digital HF data/picture transfer software such as </span><i><span style="font-family: TimesNewRomanPS-ItalicMT; color: black;">Digtrx,<o:p></o:p></span></i></p> <p class="MsoNormal" style=""><i><span style="font-family: TimesNewRomanPS-ItalicMT; color: black;">EasyPal </span></i><span style="color: black;">and </span><i><span style="font-family: TimesNewRomanPS-ItalicMT; color: black;">HamPAL </span></i><span style="color: black;">share the same core ham-DRM standard and therefore are<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">compatible with WinDRM. WinDRM is not compatible with all newer encoding methods<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">now being used by </span><i><span style="font-family: TimesNewRomanPS-ItalicMT; color: black;">HamPal. </span></i><span style="color: black;">WinDRM is not compatible with AOR’s ARD 9000/9800<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">fast radio modem.<o:p></o:p></span></p> <p class="MsoNormal" style=""><b><span style="font-size: 16pt; font-family: TimesNewRomanPS-BoldMT; color: black;">The WinDRM GUI </span></b><span style="color: black;">(graphic user interface</span><b><span style="font-family: TimesNewRomanPS-BoldMT; color: black;">)<o:p></o:p></span></b></p> <p class="MsoNormal" style=""><span style="color: black;">Five “State” Radio Buttons - (enabled under program control during receive ) as follows:<o:p></o:p></span></p> <p class="MsoNormal" style=""><b><span style="font-family: TimesNewRomanPS-BoldMT; color: black;">Input/Output<o:p></o:p></span></b></p> <p class="MsoNormal" style=""><b><span style="font-family: TimesNewRomanPS-BoldMT; color: black;">IO </span></b><span style="color: black;">– Enabled: Sound card is linked and passing data to the processor. Disabled:<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">Indicates sound card is not compatible and/or PC’s processor is too slow. If not enabled,<o:p></o:p></span></p> <p class="MsoNormal" style=""><b><span style="font-size: 16pt; font-family: TimesNewRomanPS-BoldMT; color: black;">WinDRM<o:p></o:p></span></b></p> <p class="MsoNormal" style=""><span style="color: black;">2<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">WinDRM will not decode data. Note: IO should always be enabled during receive </span><i><span style="font-family: TimesNewRomanPS-ItalicMT; color: black;">and<o:p></o:p></span></i></p> <p class="MsoNormal" style=""><span style="color: black;">transmit.<o:p></o:p></span></p> <p class="MsoNormal" style=""><b><span style="font-family: TimesNewRomanPS-BoldMT; color: black;">Frequency Acquisition<o:p></o:p></span></b></p> <p class="MsoNormal" style=""><b><span style="font-family: TimesNewRomanPS-BoldMT; color: black;">Freq – </span></b><span style="color: black;">Enabled: The three FAC reference carriers/pilots (3 higher intensity vertical lines<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">in the waterfall displays) have been found. These correlate with the DC Offset frequency<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">(normally 350Hz) which is graphically shown as a blue vertical line.<o:p></o:p></span></p> <p class="MsoNormal" style=""><b><span style="font-family: TimesNewRomanPS-BoldMT; color: black;">Time Synchronization Acquisition<o:p></o:p></span></b></p> <p class="MsoNormal" style=""><b><span style="font-family: TimesNewRomanPS-BoldMT; color: black;">Time </span></b><span style="color: black;">– Enabled: Timing acquisition is done. This indicates the search for the beginning<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">of the OFDM symbol has been completed. Disabled: No synchronization, (usually<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">caused by poor SNR) distortion of the transmitted signal and/or receive band pass is too<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">narrow. Note: False indications (flickering) can be caused by AWGN (atmospheric<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">noise) and generally, may be ignored.<o:p></o:p></span></p> <p class="MsoNormal" style=""><b><span style="font-family: TimesNewRomanPS-BoldMT; color: black;">Frame Synchronization<o:p></o:p></span></b></p> <p class="MsoNormal" style=""><b><span style="font-family: TimesNewRomanPS-BoldMT; color: black;">Frame </span></b><span style="color: black;">- Enabled: Frame synchronization is completed and the start of a DRM frame<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">(400ms) has been found. The Receiver is in synchronization with the transmitting station.<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">Disabled: Lost frequency synchronization due to poor SNR or change in frequency (avoid<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">“tuning” once in sync). Note: False indications (flickering) can be caused by AWGN<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">(atmospheric noise) and generally, may be ignored.<o:p></o:p></span></p> <p class="MsoNormal" style=""><b><span style="font-family: TimesNewRomanPS-BoldMT; color: black;">Fast Access Channel<o:p></o:p></span></b></p> <p class="MsoNormal" style=""><b><span style="font-family: TimesNewRomanPS-BoldMT; color: black;">FAC </span></b><span style="color: black;">– Enabled: Receiver is in the tracking mode, has received a good Cyclic<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">Redundancy Check (8-bit CRC) and is in synchronization with the WinDRM transmitting<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">station. FAC is a separate logical channel and modulated with 4-Amplitude Quadrature<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">Modulation (4QAM). FAC provides bandwidth spectrum occupancy (2.3/2.5khz), call<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">sign and other DRM transmit parameters for the WinDRM receiver. Time, Frame and<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">FAC always precede (must be enabled) MSC channel data. Disabled: Caused by lost<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">sync, failed CRC, QRM, change in frequency and/or distortion of the transmitted signal.<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">FAC provides the data for the receiving WinDRM station to set it up to automatically<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">receive data for file transfer or digital voice (no intervention required by the receive end<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">operator).<o:p></o:p></span></p> <p class="MsoNormal" style=""><b><span style="font-family: TimesNewRomanPS-BoldMT; color: black;">Main Service Channel<o:p></o:p></span></b></p> <p class="MsoNormal" style=""><b><span style="font-family: TimesNewRomanPS-BoldMT; color: black;">MSC </span></b><span style="color: black;">- Enabled: Indicates actual audio and data bits are being decoded for voice, text<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">message and/or images. MSC may be modulated using 4QAM, 16QAM or 64QAM (see<o:p></o:p></span></p> <p class="MsoNormal" style=""><st1:place st="on"><st1:city st="on"><span style="color: black;">DRM</span></st1:city><span style="color: black;"> <st1:state st="on">TX</st1:state></span></st1:place><span style="color: black;"> settings). 4QAM is unique to WinDRM (DRM uses 16 and 64QAM in the<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">MSC). The larger the QAM rate the higher spectral efficiency but with lower<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">performance (less robust in presence of errors caused by poor propagation or<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">QRM/QRN). Robustness is improved through interleaving of the MSC symbols. This<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">provides time diversity so that a burst of errors is spread across up to several frames<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">minimizing the destructive effects on the received data. Like FAC, MSC enabled<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">indicates the Cyclic Redundancy Check (CRC) has been acknowledged and good data<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">has been received (Info’s data for MSC will increment after the CRC has been<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">computed). Disabled: Disruptions (dropouts), text message not received, or missed<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">3<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">block/segment/packet image data. QRM/QSB/QRN and weak signals can cause MSC to<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">fail or “flicker” during reception. A minimum SNR of 7dB generally ensures MSC will<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">remain enabled. Note: All these radio buttons must be enabled (from decoded<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">transmitted data) before the file/picture or voice data will be received.<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="font-size: 16pt; font-family: Arial; color: black;">Files: </span><span style="color: black;">(download from: </span><span style="color: blue;">www.n1su.com/windrm/ </span><span style="color: black;">)<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">The .wav files must be created using Digtrx or similar program. For docs on how to<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">create these files, go to </span><span style="color: blue;">http://www.kiva.net/~djones/index.htm </span><span style="color: black;">. Note: These wave files<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">are not necessary to execute/use WinDRM. WinDRM stores files/pictures with errors in<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">the Corrupt folder. Good, error free Files/pictures are stored in the Pictures folder.<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">Mixer.bin contains data for the sound card’s mixer settings. Settings.txt file stores user<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">settings such as com port, call sign, etc. User files/pictures to be sent may be stored in<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">any directory for transmission, but are normally kept in the WinDRM directory for quick<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">access. Note: Digtrx creates 16bit 8000Hz sample rate wave files. WinDRM requires<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">16 bit 48000Hz wave file format. Use a freeware program like Audacity<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">(</span><span style="color: blue;">http://audacity.sourceforge.net/</span><span style="color: black;">) to convert the wave files from 8000Hz to 48000Hz<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">mono.<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">Other files are created by WinDRM include:<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">bsr.bin<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">bsr0.bin<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">bsrreq.bin<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">bsrreq0.bin<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">RX_Log.txt<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">4<o:p></o:p></span></p> <p class="MsoNormal" style=""><b><span style="font-size: 13pt; font-family: Arial-BoldMT; color: black;">Known specs and definitions:<o:p></o:p></span></b></p> <p class="MsoNormal" style=""><b><span style="font-size: 13pt; font-family: Arial-BoldMT; color: black;">TX Data rate<o:p></o:p></span></b></p> <p class="MsoNormal" style=""><span style="color: black;">MSC transmit data rate in bits-per-second (bps) is shown in the SNR box when<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">transmitting. For the DRM TX “Default” setting this is 2617bps. The Mode box will<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">display B/S/16/0/2.5 for this setting (see “Mode” for explanation of this data). The<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">CODECs (Linear Predictive Coding, SPEEX and Mixed-Excitation Linear Predictive)<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">require at least 2400bps. For data, WinDRM offers a “Speed” mode at a higher bit rate<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">of 4362bps and a “Robust” slower bit rate mode of 997bps. By changing these DRM TX<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">settings, the MSC protection, Coding, Bandwidth, and Interleave may be carefully chosen<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">to match the transceiver filters and current band conditions. For HF, a good starting point<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">is the default TX DRM setting. For poor band conditions, try the robust mode. Refer to<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">the specs found at: </span><span style="color: blue;">http://www.qslnet.de/member/hb9tlk/drm_h.html<o:p></o:p></span></p> <p class="MsoNormal" style=""><b><span style="font-size: 13pt; font-family: Arial-BoldMT; color: black;">Modulation and Forward Error Correction<o:p></o:p></span></b></p> <p class="MsoNormal" style=""><span style="color: black;">Carriers are modulated using 4QAM, 16 or 64 in the MSC. The QAM constellation size<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">is selected by the user under the DRM TX settings. QAM4 is set by WinDRM for FAC<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">since it is the most robust. OFDM/QAM modulated carriers would appear to be<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">overlapping within their spectrum. However, once they are synchronized at the receiver,<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">they no longer over lap (now orthogonal/unique) and can then be demodulated. QAM<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">has both fixed amplitude and phase modulation. Forward Error Protection (FEC) is<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">provided by Reed Solomon (RS) code. By definition, RS has the ability “…to produce at<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">the sender ‘n’ blocks of encoded data from ‘k’ blocks of source data in such a way that<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">any subset of k encoded blocks suffices at the receiver to reconstruct the source data.”<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">This gives DRM the ability to “repair itself on the fly” by accurately rebuilding the audio<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">or file data as it was originally coded at the transmitter. If this can’t be done, then<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">WinDRM keeps track of the errors (bad data segments) in the file and with the BSR, the<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">data can be replaced with error free data using either the manual request (user<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">intervention required) or automated using the ARQ feature in a point to point QSO.<o:p></o:p></span></p> <p class="MsoNormal" style=""><b><span style="font-size: 13pt; font-family: Arial-BoldMT; color: black;">PC requirements<o:p></o:p></span></b></p> <p class="MsoNormal" style=""><span style="color: black;">Windows OS, 2000 or XP. 700mHz minimum processor speed with 1.2GHz or higher to<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">ensure smooth operation. Avoid executing other programs while WinDRM is decoding or<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">transmitting. For testing/experimenting, 2+ GHz PCs can run two instances (i.e. A to B)<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">of WinDRM in a back-to-back mode (connect sound card line out/speaker to line in/mic<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">and carefully set levels or use Virtual Audio Cables VAC. Instance A may then be used<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">to transmit pictures to instance B. If VAC is available (a separate program), DV may<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">5<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">also be demonstrated since VAC take care of exchanging data between each instance of<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">WinDRM allowing microphone voice input to the sound card.<o:p></o:p></span></p> <p class="MsoNormal" style=""><b><span style="font-size: 13pt; font-family: Arial-BoldMT; color: black;">Status of received data in the Info box for images (RX Pics)<o:p></o:p></span></b></p> <p class="MsoNormal" style=""><span style="color: black;">The “Info” box during receive provides a status of the data being decoded as it is<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">received. These counters are shown in three sets of one to three digits separated with a<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">forward slash (/). The first set is the number of memory segments (size) in the file. The<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">second set shows the number of good segments decoded. The last set shows the segment<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">number of the last segment decoded.<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">The first set of numbers represents what WinDRM “knows about” at the start of the<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">transmission and will change because the program begins assembling the data before the<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">total is known. If a segment is received in error (CRC failure), a following instance<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">provides the opportunity to receive it again. If received OK, the counter will increment.<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">After all the data is received, the segment counts will all agree indicating the file has been<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">received error free. If a picture was received, it will open up in Irfanview or the<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">viewer/program associated with the file’s extension. Note: The segment size increases<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">with the constellation size (4 thru 64) of the QAM since it is possible to transmit more<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">bits per symbol in the higher order constellations.<o:p></o:p></span></p> <p class="MsoNormal" style=""><b><span style="font-size: 13pt; font-family: Arial-BoldMT; color: black;">Status of received data in the Info box for voice (RX)<o:p></o:p></span></b></p> <p class="MsoNormal" style=""><span style="color: black;">While receiving voice, the Info block displays 1 to 100% representing the quality of the<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">decoded data. The quality is determined by the number of good frames of data received<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">*versus bad since the last synchronization. Drop outs (speech loss) may be experienced<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">with 70 percent or less. With SNRs of 12 or higher, expect a quality number near 100<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">percent (no dropouts).<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">6<o:p></o:p></span></p> <p class="MsoNormal" style=""><b><span style="font-size: 13pt; font-family: Arial-BoldMT; color: black;">Status of transmitted data in the Info box for files ( TX Pics)<o:p></o:p></span></b></p> <p class="MsoNormal" style=""><span style="color: black;">After transmitting the lead in sync data, the Info box provides the status of the file as it is<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">being sent. The counter consists of two sets of numbers separated by a forward slash (/).<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">First set shows the instance being sent while the second set shows the percentage (1 to<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">100 percent) of the total segments sent. The number of instances the file will be sent is<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">shown in the “Select File” window. A choice of 1 to 3 may be selected but additional<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">instances can be sent by adding the file in the Select File window more than once.<o:p></o:p></span></p> <p class="MsoNormal" style=""><b><span style="font-size: 13pt; font-family: Arial-BoldMT; color: black;">Status of transmitted data in the Info box for voice (TX)<o:p></o:p></span></b></p> <p class="MsoNormal" style=""><span style="color: black;">No data is shown in the Info box during voice transmission except during the lead in sync<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">period.<o:p></o:p></span></p> <p class="MsoNormal" style=""><b><span style="font-size: 13pt; font-family: Arial-BoldMT; color: black;">Info box during “lead in” transmission<o:p></o:p></span></b></p> <p class="MsoNormal" style=""><span style="color: black;">In both picture and voice transmissions, lead in sync data is sent to the receiving station<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">for setting up the timing and other OFDM carrier information. This lead in maybe<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">lengthened to provide more set up (sync) time at the receive end by selecting long lead in<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">under the Select Files window. While the lead in is being sent (up to several seconds),<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">the Info box will increment various numbers indicating this data is being transmitted and<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">the actual file data has not started. Some of this data includes determining the size of the<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">file and packetizing data prior to be sent.<o:p></o:p></span></p> <p class="MsoNormal" style=""><b><span style="font-size: 13pt; font-family: Arial-BoldMT; color: black;">Text Message data<o:p></o:p></span></b></p> <p class="MsoNormal" style=""><span style="color: black;">Up to 128 ASCII characters (including spacing) may be transmitted. Greater than 128<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">will be truncated at the receive window. Text messages may not be sent with data<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">(file/picture transmissions). Text messages may be added or changed during TX. The<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">data rate is only 80bps, but the message is continuously transmitted during the voice<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">transmission. In receive, the text message window remains open at the end of the<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">transmission. This message window may be closed at any time but will re-open while<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">7<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">data is being received. Text messages may only be sent and received with Digital Voice<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">transmissions.<o:p></o:p></span></p> <p class="MsoNormal" style=""><b><span style="font-size: 13pt; font-family: Arial-BoldMT; color: black;">Transmit and Receive parameters (and transceiver setup)<o:p></o:p></span></b></p> <p class="MsoNormal" style=""><span style="color: black;">For optimum performance, the OFDM carriers must fit within the band pass of the<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">receiver and transmitter. The default 350 Hz DC Offset was chosen to ensure the 2.5Khz<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">wide OFDM signal is inside both the transmit and receive audio band pass. The 350Hz is<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">an offset from DC (0 hertz) and where the carriers of the OFDM begin. The timing<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">(OFDM searches for this) locks on and starts all it’s shifting up in frequency from the DC<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">offset for all 57 carriers. This offset can be changed but it must chosen so the spectrum<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">will fit within the TX and RX band passes. If the DC is moved too much from 350, all<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">the OFDM carriers may not fit within these band passes. Although it is not important to<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">be exactly on the transmitting stations frequency, modern transceivers should allow the<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">receiving station to be within 100hz of this offset frequency. Too far off frequency may<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">result in lowering SNR if OFDM carriers fall outside the receiver’s band pass. If any<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">tuning of the frequency is made during receive, the signal is phase shifted and attenuated.<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">The orthogonality of the OFDM symbols may also be destroyed and this causes ICI<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">(inter-carrier-interference). This will immediately stop decoding data. Click on “Reset”<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">to re-sync the data if any tuning must be done to bring all carriers within the band pass of<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">the receiver. When the WinDRM users talk on SSB, carefully tune to their SSB<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">frequency. This will ensure you are on the frequency being used for DRM data also. Be<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">sure the receiver’s band pass is at least set to at least 2.5 kHz FLAT band pass with no<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">DSP and/or audio processing. For most receivers, setting AGC to Fast (or OFF) will<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">improve SNR. For transmit, minimize distortion by turning off compression, EQ (or DSP<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">filtering within the band pass) and avoid any ALC action. For 100 watt rigs, set power to<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">approximately 15 watts average power. This mode works best with very linear<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">transmitters and amplifiers. All commercial DRM transmitters are Class A. OFDM has a<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">rather high crest factor caused by the mathematical FFT operation applied to the<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">transmitted signal. The peak power is much higher (7-9 dB) than the average power read<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">on a conventional wattmeter. Experience has found that operating out of the linear region<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">of your transceiver and/or amplifier may result in a 3 to 4 dB </span><i><span style="font-family: TimesNewRomanPS-ItalicMT; color: black;">lower </span></i><span style="color: black;">SNR at the receiving<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">station. For a detailed explanation of how to set the power out of your transmitter, go to:<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: blue;">http://www.tima.com/~djones/DRM_power.htm </span><span style="color: black;">WinDRM’s Shifted Power Spectrum<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">Density (Shifted PSD) in the absence of multi-path/QRM, will display a “Flat top” signal<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">across the entire bandwidth of the received signal. Ask the receiving station to comment<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">on your transmitted signal using this display. If it is not “flat”, then either the transmitter<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">or the receiving station’s is not set up properly which can degrade performance.<o:p></o:p></span></p> <p class="MsoNormal" style=""><b><span style="font-size: 13pt; font-family: Arial-BoldMT; color: black;">CODEC<o:p></o:p></span></b></p> <p class="MsoNormal" style=""><span style="color: black;">Select under DRM TX Settings, “CODEC” (voice) or “DATA” (files/pics) being<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">transmitted will be displayed. Under program control (FAC data), the receiving station<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">will automatically decode and display the mode of transmission being sent (LPC,<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">SPEEX, or Data).<o:p></o:p></span></p> <p class="MsoNormal" style=""><b><span style="font-size: 13pt; font-family: Arial-BoldMT; color: black;">SNR<o:p></o:p></span></b></p> <p class="MsoNormal" style=""><span style="color: black;">8<o:p></o:p></span></p> <p class="MsoNormal" style=""><b><span style="font-family: TimesNewRomanPS-BoldMT; color: black;">S</span></b><span style="color: black;">ignal-to-</span><b><span style="font-family: TimesNewRomanPS-BoldMT; color: black;">N</span></b><span style="color: black;">oise-</span><b><span style="font-family: TimesNewRomanPS-BoldMT; color: black;">R</span></b><span style="color: black;">atio is an estimated value that indicates the quality and strength of the<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">received signal. Experience has found, near error free data may be decoded with a SNR<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">greater than 7.0 dB. The higher the number, the better the signal is being received. An<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">SNR of 10 or better usually ensures error free copy. QRN, QRM, transmit distortion and<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">propagation problems caused by multi-path cancellation lower the SNR. Transmitters<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">and amplifiers operating out of their linear region (trying to run too much power!), failure<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">to turn off compression or DSP/EQ and too narrow band pass all degrade SNR. Under<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">ideal band conditions, SNR will rise to 25db or greater when both the transmitting and<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">receiving stations are set up properly. Note: SNR is determined from the carriers<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">between the low (725Hz) and high (1850Hz) reference pilot carriers only.<o:p></o:p></span></p> <p class="MsoNormal" style=""><b><span style="font-size: 13pt; font-family: Arial-BoldMT; color: black;">DC<o:p></o:p></span></b></p> <p class="MsoNormal" style=""><span style="color: black;">Refers to the frequency offset from 0 Hz to the start of OFDM carriers. Default is set at<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">350Hz. This is an arbitrary number chosen to ensure both the 2.3 and 2.5 kHz signal BW<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">“fits” within the bandpass of the receiving station. This may be confirmed by observing<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">the shifted PSD, transfer function displays or the moving waterfall displays. The accuracy<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">of the receiving station’s tuning for the COFDM signal is dependent upon this factor<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">which will allow a 100-125Hz tuning error without affecting the decoding process. It is<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">important to note however, that once sync is obtained, no further “tuning” of the signal<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">should be attempted. A blue vertical line indicates the location of DC offset. Values of 50<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">to 5000 Hz are valid entries but 350 Hz is normally used.<o:p></o:p></span></p> <p class="MsoNormal" style=""><b><span style="font-size: 13pt; font-family: Arial-BoldMT; color: black;">Mode<o:p></o:p></span></b></p> <p class="MsoNormal" style=""><span style="color: black;">Displays the DRM TX settings. The default is:<o:p></o:p></span></p> <p class="MsoNormal" style=""><b><span style="font-family: TimesNewRomanPS-BoldMT; color: black;">B </span></b><span style="color: black;">(DRM Mode B) </span><b><span style="font-family: TimesNewRomanPS-BoldMT; color: black;">S </span></b><span style="color: black;">(Short Interleave) </span><b><span style="font-family: TimesNewRomanPS-BoldMT; color: black;">16 </span></b><span style="color: black;">(Main Service Channel 16 Quadrature<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">Amplitude Modulation) </span><b><span style="font-family: TimesNewRomanPS-BoldMT; color: black;">0 </span></b><span style="color: black;">(Protection level) </span><b><span style="font-family: TimesNewRomanPS-BoldMT; color: black;">2.5 </span></b><span style="color: black;">(2.5 kHz Bandwidth). Most stations<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">use 2.5kHz since additional carriers are available with this wider BW giving better<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">receive performance. TX DRM modes are selected to correlate with the quality of the<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">signal (as affected by propagation, signal strength, QRN, etc) available at the receive end.<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">These modes affect the transmission speed and robustness of the received signal. For<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">more info, see “DRM TX Settings” later in this doc.<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">9<o:p></o:p></span></p> <p class="MsoNormal" style=""><b><i><span style="font-size: 13pt; font-family: Arial-BoldItalicMT; color: black;">Setup<o:p></o:p></span></i></b></p> <p class="MsoNormal" style=""><st1:place st="on"><st1:placename st="on"><b><span style="font-size: 13pt; font-family: Arial-BoldMT; color: black;">PTT</span></b></st1:placename><b><span style="font-size: 13pt; font-family: Arial-BoldMT; color: black;"> <st1:placetype st="on">Port</st1:placetype></span></b></st1:place><b><span style="font-size: 13pt; font-family: Arial-BoldMT; color: black;"><o:p></o:p></span></b></p> <p class="MsoNormal" style=""><span style="color: black;">Any com port 1 through 8 may be selected for control of the transmitter’s PTT using<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">conventional RS232C data terminal ready (DTR) line. For most applications, a standard<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">RS232C cable is used to connect the PC’s com port to the sound card interface<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">(RigBlaster or equivalent). In addition, the DTR or ready to send (RTS) line may be<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">used to mute the receiver’s speaker while receiving data. Implementation of this feature<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">may be found at KB4YZ’s web site. (</span><span style="color: blue;">http://www.kiva.net/~djones/index.htm </span><span style="color: black;">) WinDRM<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">may be started and the PTT controlled in the “Remote” (PTT on CTS or PTT on DSR)<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">mode using the com port’s CTS or DSR line. This Remote mode will allow the use of<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">external switching from the PTT switch on a microphone or a PTT foot switch. To avoid<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">a possible ground loop, an optical isolator or a relay should be used to assert (apply a<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">positive +5 to 12vdc) to either the DSR or CTS line. Note: Due to some ambiguity<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">between Windows OS and WinDRM, the CTS and DSR are reversed (CTS is pin 6 and<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">DSR is pin 8 in the 9 pin Sub-D PC’s com port connector). Use of a pull-down resistor<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">on these pins will help ensure no false PTTs. For com port protection, a current-limiting<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">resistor may be used in series with the positive voltage applied to the DSR or CTS pin.<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">This Remote feature is not saved in WinDRM’s user’s settings file therefore when used,<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">it must be checked each time the program is executed. TX voice may also be activated<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">using the keyboard’s spacebar. With “TX Voice” in focus (as show in above display),<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">taping the spacebar will put WinDRM in transmit (activating PTT) and pushing it again<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">will return WinDRM to receive (a toggle function). To un-focus TX voice and avoid<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">placing WinDRM in transmit while using the keyboard for other functions, push the<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">keyboard’s “Tab” key. Spacebar PTT will not function while in the “Remote” mode.<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">10<o:p></o:p></span></p> <p class="MsoNormal" style=""><b><i><span style="font-size: 13pt; font-family: Arial-BoldItalicMT; color: black;">Setup<o:p></o:p></span></i></b></p> <p class="MsoNormal" style=""><b><span style="font-size: 13pt; font-family: Arial-BoldMT; color: black;">Call sign<o:p></o:p></span></b></p> <p class="MsoNormal" style=""><span style="color: black;">Up to 8 number/letters may be entered. “NOCALL” is the default.<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">11<o:p></o:p></span></p> <p class="MsoNormal" style=""><b><i><span style="font-family: Arial-BoldItalicMT; color: black;">Setup<o:p></o:p></span></i></b></p> <p class="MsoNormal" style=""><b><span style="font-family: Arial-BoldMT; color: black;">Display<o:p></o:p></span></b></p> <p class="MsoNormal" style=""><b><span style="font-family: Arial-BoldMT; color: black;">Receive Spectrum<o:p></o:p></span></b></p> <p class="MsoNormal" style=""><span style="color: black;">The Spectrum’s display is approximately 2.5 kHz wide in the horizontal while the<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">vertical shows the amplitude in dB (no scales are shown for any of the displays). The<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">shape of the signal is rectangular (flat top) and represents the 2.3 or 2.5 KHz band width<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">of the received signal. This display may be used to set the audio input level of the sound<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">card. Too much input will over-drive the sound card (line input should always be used<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">when available) and may cause distortion and low SNR. Carefully adjust the line input<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">level and the receiver audio until the top of the COFDM spectrum averages<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">approximately half way up in the display window. Although there is normally good<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">dynamic range in most sound cards, the goal is obtain the highest SNR reading. After<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">sync has been obtained, a blue vertical line will appear in the spectrum. This blue line<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">shows where the timing for acquiring the COFDM signal has started (the DC offset<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">frequency) which is normally 350Hz. This line may pop up intermittently as it will<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">“false” on random noise and should be ignored when no valid COFDM signal is being<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">received. The three reference pilot carriers are easily seen in the display with frequencies<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">of 725, 1475 and 1850Hz.<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">12<o:p></o:p></span></p> <p class="MsoNormal" style=""><b><span style="font-size: 13pt; font-family: Arial-BoldMT; color: black;">Receive Waterfalls<o:p></o:p></span></b></p> <p class="MsoNormal" style=""><span style="color: black;">Three waterfalls are available, Moving, Static, and Flicker reduced. The COFDM<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">spectrum will be displayed with an </span><i><span style="font-family: TimesNewRomanPS-ItalicMT; color: black;">even </span></i><span style="color: black;">intensity level across its 2.3 or 2.5 KHz<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">bandwidth. Within the waterfall, three FAC reference (or pilot carriers) of higher<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">intensity can be seen. These stand out because they have higher gain (transmitted at<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">twice the power). These FAC pilots are modulated with known fixed phases and<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">amplitude which optimize DRM’s performance for initial synchronization, duration and<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">reliability. They are used to calculate the initial coarse frequency offset of the received<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">DRM signal. This is the first part of the COFDM sync process and must occur before the<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">received DRM signal can be decoded. The high-lighted red markers at the top of the<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">waterfall display indicate where the FAC reference carriers are located when the<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">transmitter and receiver DC offsets match. The moving waterfall sweeps from top to<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">bottom with the red marker’s indicating the position of reference carriers remaining fixed<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">at the top of the display. The moving waterfall adds a visual method to monitor the<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">health of the decoded signal in the form of a vertical line on each side of the waterfall<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">spectrum. During the decoding process, the green vertical lines indicate data is being<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">received without errors and red lines indicate errors. These green/red indicators move<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">with the spectrum instantly showing when and where the data errors occurred. The<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">horizontal line across the top of this display indicates the bandwidth of the COFDM<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">signal. The signal in the waterfall should fully extend the width of this line. The Flicker<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">reduced waterfall is a modified moving waterfall designed to reduce “flicker” from some<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">types of fast LCD or laptop displays. Note: The waterfall display shown above depicts<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">the effects of multi-path cancellation as shown by the darkened (“notches”) areas. The<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">carriers in this area are being attenuated due to these phenomena. The two bright lines (on<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">the bottom left, just before the start of data) is unwanted noise (probably caused by a<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">ground loop between the transceiver and the PC soundcard) on the Speaker Out audio<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">line to the transceiver’s Mic input. Every effort should be made to eliminate this type of<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">interference when connecting audio cables between the PC and the transceiver. To<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">minimize ground loop and/or RFI problems associated with sound cards and the<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">13<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">transceiver, refer to these informative papers found at:<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: blue;">http://audiosystemsgroup.com/SAC0305Ferrites.pdf<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">and </span><span style="color: blue;">http://audiosystemsgroup.com/Ferrites-Ham.pdf<o:p></o:p></span></p> <p class="MsoNormal" style=""><b><span style="font-family: TimesNewRomanPS-BoldMT; color: black;">Important: </span></b><span style="color: black;">It can not be emphasized enough that common mode noise (i.e. ground<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">loops – ac currents) must be eliminated or risk the high probability that unwanted noise<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">will be heard in the speaker at the receiving station while decoding digital voice. When<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">this noise is present, it is directly proportional to the TX microphone (mixer) level input<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">and will reduce the favorable experience expected of this mode. </span><i><span style="font-family: TimesNewRomanPS-ItalicMT; color: black;">Only </span></i><span style="color: black;">the decoded voice<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">should be heard from the PC speakers.<o:p></o:p></span></p> <p class="MsoNormal" style=""><b><span style="font-size: 13pt; font-family: Arial-BoldMT; color: black;">Input Level (receive)<o:p></o:p></span></b></p> <p class="MsoNormal" style=""><span style="color: black;">This display graphically shows the received audio. Sound card (recording) Line Input<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">may be set to approximate the level as shown in the display above.<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">14<o:p></o:p></span></p> <p class="MsoNormal" style=""><b><span style="font-size: 13pt; font-family: Arial-BoldMT; color: black;">Shifted PSD (receive)<o:p></o:p></span></b></p> <p class="MsoNormal" style=""><span style="color: black;">This display plots the “estimated Power Spectrum Density (PSD) of the input signal”.<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">The X axis measures the PSD of 0 to 50dB while the Y axis is frequency from 0 to 12<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">KHz. Here the incoming DC frequency (350 Hz) is mixed with 5650 Hz to give a 6 KHz<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">(the blue vertical line is correctly shown in DRM mode B only). The peak on the left is<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">the mirror image (5650 – 350 = 5300 Hz) and is partially suppressed by the WinDRM’s<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">internal IF filter. If a peak is displayed between the signal and the mirror signal, a<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">50/60Hz noise could be in the transmitted audio from ground loop. The three peaks seen<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">at the top of the waveform are the pilot carriers for sync and have twice the power. Any<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">roll off or dips in the waveform indicate the carriers in these areas have a loss of power<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">caused by QSB and/or attenuation in the band pass of the transmitter or receiver. If the<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">transmitter </span><b><span style="font-family: TimesNewRomanPS-BoldMT; color: black;">or </span></b><span style="color: black;">receiver does not allow the 2.3/2.5khz wide (350 to 2850Hz) DRM signal<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">to pass without attenuation, this waveform will roll off on either end. Up to 10dB or<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">more SNR can be lost because careful attention has not been taken to properly set up the<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">transmitter, receiver and soundcard for the “flat top” OFDM spectrum.<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">15<o:p></o:p></span></p> <p class="MsoNormal" style=""><b><span style="font-size: 13pt; font-family: Arial-BoldMT; color: black;">Transfer Function ( receive)<o:p></o:p></span></b></p> <p class="MsoNormal" style=""><span style="color: black;">This plot shows the “squared magnitude of the channel estimation at each sub carrier”.<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">The green line is the transfer function (TF in dB) while the blue line shows the phase<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">distortion of the channel (Group Delay in ms). Optimum signals will yield a flat response<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">and display even/flat lines across the width of the display.<o:p></o:p></span></p> <p class="MsoNormal" style=""><b><span style="font-size: 13pt; font-family: Arial-BoldMT; color: black;">Impulse Response (receive)<o:p></o:p></span></b></p> <p class="MsoNormal" style=""><span style="color: black;">This plot shows the “estimated Impulse Response (IR) of the channel based on the<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">channel estimation”. This pulse is used in determining the HF channel’s frequency and<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">phase characteristics so the signal may be restored as close as possible to what it looks<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">like at the transmitter. The time delay of the shortest path is taken as the zero reference<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">for the estimated pulse response.<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">16<o:p></o:p></span></p> <p class="MsoNormal" style=""><b><span style="font-size: 13pt; font-family: Arial-BoldMT; color: black;">Fast Access Channel (FAC) Phase (receive)<o:p></o:p></span></b></p> <p class="MsoNormal" style=""><span style="color: black;">This plot shows the 4 QAM rectangular constellation. For more info on QAM see above<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">info under FAC radio button and this URL:<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: blue;">http://en.wikipedia.org/wiki/Quadrature_amplitude_modulation<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">.<o:p></o:p></span></p> <p class="MsoNormal" style=""><b><span style="font-size: 13pt; font-family: Arial-BoldMT; color: black;">Main Service Channel (MSC) (receive)<o:p></o:p></span></b></p> <p class="MsoNormal" style=""><span style="color: black;">This plot shows the various constellations for a 4 through 64 QAM logical channel that<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">provides the voice and file data. High SNR keeps the points in a close (tight)<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">constellation but some scattering is expected on HF where the Reed-Solomon error<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">17<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">correction coding is applied. QAM varies the amplitude and phase of each one of the<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">carriers (for 16 QAM and up). Then, through frequency multiplexing (adding these<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">carriers together across the 2.3/2.5 kHz BW) the OFDM is created. 16QAM is shown<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">here.<o:p></o:p></span></p> <p class="MsoNormal" style=""><b><span style="font-size: 13pt; font-family: Arial-BoldMT; color: black;">Setup<o:p></o:p></span></b></p> <p class="MsoNormal" style=""><b><span style="font-size: 13pt; font-family: Arial-BoldMT; color: black;">CODEC<o:p></o:p></span></b></p> <p class="MsoNormal" style=""><span style="color: black;">Either Linear Predictive Coding (LPC) or SPEEX open source CODECs may be selected<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">for digital voice. LPC is the default. All three require 2.5 kHz/2400bps minimum data<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">(default <st1:place st="on"><st1:city st="on">DRM</st1:city> <st1:state st="on">TX</st1:state></st1:place> settings provide this for the MSC). For further understanding of these<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">CODECs, see: </span><span style="color: blue;">http://www.otolith.com/otolith/olt/lpc.html </span><span style="color: black;">and </span><span style="color: blue;">http://www.speex.org/</span><span style="color: black;">.<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">Robust DV is not “easy” to do on HF and may never meet everyone’s needs. A couple of<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">seconds delay is required for sync before voice can be decoded therefore fast break-ins<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">are not currently possible. And, DV is not as robust as SSB.<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">18<o:p></o:p></span></p> <p class="MsoNormal" style=""><b><i><span style="font-size: 13pt; font-family: Arial-BoldItalicMT; color: black;">Setup<o:p></o:p></span></i></b></p> <p class="MsoNormal" style=""><b><span style="font-size: 13pt; font-family: Arial-BoldMT; color: black;">Text Message<o:p></o:p></span></b></p> <p class="MsoNormal" style=""><b><span style="font-size: 13pt; font-family: Arial-BoldMT; color: black;">Edit TX Text Message (voice mode only)<o:p></o:p></span></b></p> <p class="MsoNormal" style=""><span style="color: black;">Selecting “Edit TX Text Message” will open up a window to enter text.<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">Up to 128 ASCII characters (including spacing) may be transmitted. Greater than 128<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">will be truncated in the receive window. Text messages can not be sent with data<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">(file/picture transmissions). Text messages may be sent, changed or deleted during a<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">voice transmission. The data rate is only 80bps, but the message is continuously<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">transmitted during the voice transmission. This may be used to send your QTH and<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">station info and will remain open after the DV transmission has been completed.<o:p></o:p></span></p> <p class="MsoNormal" style=""><b><span style="font-size: 13pt; font-family: Arial-BoldMT; color: black;">Allow RX Text Message (default)<o:p></o:p></span></b></p> <p class="MsoNormal" style=""><span style="color: black;">Default provides a window for receiving the transmitted messages. This text message<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">window remains open for further review after the transmission has ended. (For more info,<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">see previous “Edit TX Text Message” description)<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">19<o:p></o:p></span></p> <p class="MsoNormal" style=""><b><span style="font-size: 13pt; font-family: Arial-BoldMT; color: black;">Setup<o:p></o:p></span></b></p> <p class="MsoNormal" style=""><b><span style="font-size: 13pt; font-family: Arial-BoldMT; color: black;">Save Received Files<o:p></o:p></span></b></p> <p class="MsoNormal" style=""><span style="color: black;">Checked (default) indicates files received without errors will be saved in the sub-folder of<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">WinDRM named “Pictures”. If a file is missing segments, it will be saved in the<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">“Corrupted” subfolder. Both of these folders are initially created by WinDRM.exe.<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">20<o:p></o:p></span></p> <p class="MsoNormal" style=""><b><span style="font-size: 13pt; font-family: Arial-BoldMT; color: black;">Show Received Files<o:p></o:p></span></b></p> <p class="MsoNormal" style=""><span style="color: black;">Checked (default) indicates error-free files will automatically be displayed (when<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">associated with a viewer such as Irfanview). Irfanview is the “viewer of choice” and may<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">be downloaded free at </span><span style="color: blue;">www.irfanview.com </span><span style="color: black;">Irfanview requires a plug-in and must be<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">associated with the image file extensions (.jpg, jp2 etc) to display pictures. In Irfanview,<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">go to Options>Set File Associations>Extensions then select “Images Only” or just check<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">the extensions you wish Irfanview to display. Note: Received files and pictures will be<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">saved in the Pictures or Corrupt folders even if no viewer has been configured. Note:<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">Plug file name is typically named irfanview_plugins_xxx.exe (xxx = version).<o:p></o:p></span></p> <p class="MsoNormal" style=""><b><span style="font-size: 13pt; font-family: Arial-BoldMT; color: black;">Show Only First Instance<o:p></o:p></span></b></p> <p class="MsoNormal" style=""><span style="color: black;">Checked (default) indicates only a single instance of an error-free file will be displayed<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">when received multiple times.<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">21<o:p></o:p></span></p> <p class="MsoNormal" style=""><b><span style="font-size: 13pt; font-family: Arial-BoldMT; color: black;">Soundcard<o:p></o:p></span></b></p> <p class="MsoNormal" style=""><span style="color: black;">Opening the mixer will display the sound card’s “Recording” and “Playback” sliders for<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">Audio in and out. These are associated as follows:<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">RX Input = Mixer Recording Line-In (connect to receiver’s speaker)<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">TX Output = Mixer Playback Master Volume (connect to transmitter’s microphone input)<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">Voice input = Mixer Recording Mic-In (connect PC microphone to soundcard)<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">Voice output = Mixer Playback Master Volume (connect to amplified PC speakers)<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">22<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">For Digital Voice using a single sound card, inputs are switched under program control<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">(receive line-in switched to mic-in for transmit). Adjust mixer sliders for proper input<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">and output levels. Start with the “sliders” approximately one-third up. Only the<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">RECORDING microphone should be enabled. For transmit, PLAYBACK Master<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">Volume and Wave Out must be selected. Use the Master Volume for the coarse<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">adjustment and Wave out as the fine adjustment. Note: Uncheck/deselect </span><i><span style="font-family: TimesNewRomanPS-ItalicMT; color: black;">all </span></i><span style="color: black;">other<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">inputs/outputs. For decoded Digital Voice, Mixer Playback Master Volume must be<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">manually switched between the PC’s amplified speakers for receive and the transmitter’s<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">mic input for transmit. If two sound cards are available, set up one card for Receive and<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">the other for Transmit. Then, no manual switching will be required. Note: For ease of<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">setup/use, two sound cards are </span><i><span style="font-family: TimesNewRomanPS-ItalicMT; color: black;">highly recommended </span></i><span style="color: black;">Digital Voice. It is very easy to add<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">a second sound card especially if it is a USB. A low cost “USB 2.0 to Audio Adapter<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">w/Microphone Jack” card for (under $10) may be found at </span><span style="color: blue;">www.geeks.com</span><span style="color: black;">. This is a<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">thumbnail size card (p/n HE-280B) and requires no additional drivers for XP. Just plug<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">it in, XP finds and installs the drivers and WinDRM will display both cards under<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">“Soundcard”. USB headsets may also be used (i.e. </span><i><span style="font-family: TimesNewRomanPS-ItalicMT; color: black;">Logitech 250/350</span></i><span style="color: black;">) For further help<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">with the Soundcard Mixer, see </span><span style="color: blue;">http://www.sagebrush.com/mixtech.htm<o:p></o:p></span></p> <p class="MsoNormal" style=""><b><span style="font-size: 13pt; font-family: Arial-BoldMT; color: black;">DRM TX Settings<o:p></o:p></span></b></p> <p class="MsoNormal" style=""><span style="color: black;">Mode A/B/E (A = Ground wave </span><b><span style="font-family: TimesNewRomanPS-BoldMT; color: black;">B </span></b><span style="color: black;">= Single to multi hops E = NVIS Multi-hops)<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">MSC Protection (</span><st1:city st="on"><st1:place st="on"><b><span style="font-family: TimesNewRomanPS-BoldMT; color: black;">Normal</span></b></st1:place></st1:city><b><span style="font-family: TimesNewRomanPS-BoldMT; color: black;"> </span></b><span style="color: black;">= 0 Slower Low = 1 Faster)<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">BandWidth (2.3Khz – </span><b><span style="font-family: TimesNewRomanPS-BoldMT; color: black;">2.5Khz</span></b><span style="color: black;">)<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">Interleave (</span><b><span style="font-family: TimesNewRomanPS-BoldMT; color: black;">Short </span></b><span style="color: black;">400ms – fast QSB Long 2sec – Slow QSB)<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">MSC Coding (4/</span><b><span style="font-family: TimesNewRomanPS-BoldMT; color: black;">16</span></b><span style="color: black;">/64 Quadrature Amplitude Modulation)<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">DC Offset (50-</span><b><span style="font-family: TimesNewRomanPS-BoldMT; color: black;">350</span></b><span style="color: black;">-5000Hz)<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">Clicking the Default button will result in the following <st1:place st="on"><st1:city st="on">DRM</st1:city> <st1:state st="on">TX</st1:state></st1:place> settings:<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">23<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">Mode MSC Protection Bandwidth Interleave MSC Coding DC offset<o:p></o:p></span></p> <p class="MsoNormal" style=""><b><span style="font-family: TimesNewRomanPS-BoldMT; color: black;">B Normal 2.5 Short 16QAM 350<o:p></o:p></span></b></p> <p class="MsoNormal" style=""><i><span style="font-family: TimesNewRomanPS-ItalicMT; color: black;">Robust </span></i><span style="color: black;">lowers the transmission BPS by changing 16QAM to 4QAM. </span><i><span style="font-family: TimesNewRomanPS-ItalicMT; color: black;">Speed </span></i><span style="color: black;">raises the<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">transmission BPS by changing Mode to A, MSC protection to Low and Interleave to<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">Long 2 seconds. Long interleave requires additional sync time. Voice requires 2.5kHz<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">bandwidth for the 2400 bps CODECs. 64QAM on a HF channel requires a higher SNR<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">and minimum multi-path to perform well. MSC Protection A, B and E provides different<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">levels of forward error protection (FEC) to protect the MSC from the detrimental effects<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">of QSB/QRM/QRN. B is higher than A with E (known as D in DRM) for Near Vertical<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">Incidence Skywave (NVIS) transmission where the signal is transmitted with a very high<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">angle of radiation short path propagation. In practice, however the extra protection for<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">this mode appears to have limited results. In DRM, Mode A is used for ground wave<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">propagation where Mode B for single hop/multiple hop propagation. The default mode<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">“B” on HF has shown to have the best overall performance. Mode E has been shown to<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">be the most robust in the presence of multipath and weaker signal levels.<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">Note: A BSR </span><i><span style="font-family: TimesNewRomanPS-ItalicMT; color: black;">request </span></i><span style="color: black;">may be made using different (larger to smaller QAM constellation)<o:p></o:p></span></p> <p class="MsoNormal" style=""><st1:place st="on"><st1:city st="on"><span style="color: black;">DRM</span></st1:city><span style="color: black;"> <st1:state st="on">TX</st1:state></span></st1:place><span style="color: black;"> settings. This is sometimes done under poor band conditions in attempt to get<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">the request through lower SNRs. However, the originating station responding to this<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">request must send the response to this request (“Send bad segment report”) in the </span><i><span style="font-family: TimesNewRomanPS-ItalicMT; color: black;">same<o:p></o:p></span></i></p> <p class="MsoNormal" style=""><st1:place st="on"><st1:city st="on"><span style="color: black;">DRM</span></st1:city><span style="color: black;"> <st1:state st="on">TX</st1:state></span></st1:place><span style="color: black;"> settings it was originally sent.<o:p></o:p></span></p> <p class="MsoNormal" style=""><b><span style="font-size: 13pt; font-family: Arial-BoldMT; color: black;">DRM RX Settings<o:p></o:p></span></b></p> <p class="MsoNormal" style=""><span style="color: black;">Default settings are:<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">24<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">Freq. Acq. Sens. Search Window Size Auto Reset<o:p></o:p></span></p> <p class="MsoNormal" style=""><b><span style="font-family: TimesNewRomanPS-BoldMT; color: black;">60 350 Enabled<o:p></o:p></span></b></p> <p class="MsoNormal" style=""><span style="color: black;">Higher settings increase sensitivity for weak signals but with higher probability of false<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">sync. Fast Auto Reset has shown to be effective in providing faster sync recover under<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">poor signal conditions. These settings work well in the default mode, however this is a<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">good area for hams to experiment and find what settings are best under varying<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">signal/band conditions.<o:p></o:p></span></p> <p class="MsoNormal" style=""><b><span style="font-size: 13pt; font-family: Arial-BoldMT; color: black;">BSR </span></b><span style="color: black;">(Bad Segment Report – </span><i><span style="font-family: TimesNewRomanPS-ItalicMT; color: black;">automated</span></i><span style="color: black;">)<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">BSR provides a procedure to repair (sometimes called a “fix”) a defective file or picture.<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">Normally, a defective file or picture is caused when the received station does not receive<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">all the memory segments error free (segment failed CRC check). Depending upon how<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">many segments were not received, the picture may not be displayed using the SPA (Show<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">Picture Anyway) or will appear unclear/blurry. When this happens, clicking on the<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">“BSR” button will open a window and show the number of segments “missing”. The<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">received station may then send a BSR “Request” to the sending station and request these<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">missing segments be resent so the file (picture) may be repaired and displayed. This is the<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">manual method and requires user intervention. The “automated” BSR completely<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">automates this procedure for P2P (point to point) transfer of files. Auto Open BSR<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">request, TX ARQ and RX ARQ must be checked to initiate this procedure. Note:<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">WinDRM does not look for activity on the frequency. The procedure simply relies on<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">timing between the tx to rx and rx to tx change-overs and does not “listen” on the channel<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">for other activity. Therefore, users should maintain control of the station while this<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">automated BSR is being executed, i.e. “attended” operation. Upon a successful Auto<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">ARQ exchange, the sending station will send “Good Copy” to the receive station’s<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">waterfall. Note: Up to 30 additional segments are sent in with the receiver’s BSR. These<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">“additional” segments are sent to ensure the receiving station is in sync. Up to four<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">multiple BSRs windows may be open at one time. There requests may be transmitted one<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">25<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">at a time or all can be transmitted by clicking on the “BSR send” button while any one of<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">these request are being made (during transmission).<o:p></o:p></span></p> <p class="MsoNormal" style=""><b><span style="font-size: 13pt; font-family: Arial-BoldMT; color: black;">Load last RX file<o:p></o:p></span></b></p> <p class="MsoNormal" style=""><span style="color: black;">When selected, the last error free file received will be loaded in the “Select Files”<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">window. This is normally used when the entire file is to be re-sent.<o:p></o:p></span></p> <p class="MsoNormal" style=""><b><span style="font-size: 13pt; font-family: Arial-BoldMT; color: black;">Auto open BSR request<o:p></o:p></span></b></p> <p class="MsoNormal" style=""><span style="color: black;">Automatically opens up the BSR window when a defective file is received. This must be<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">checked to initiate the automated BSR procedure.<o:p></o:p></span></p> <p class="MsoNormal" style=""><b><span style="font-size: 13pt; font-family: Arial-BoldMT; color: black;">TX ARQ<o:p></o:p></span></b></p> <p class="MsoNormal" style=""><span style="color: black;">Automates the “send” request for the BSR<o:p></o:p></span></p> <p class="MsoNormal" style=""><b><span style="font-size: 13pt; font-family: Arial-BoldMT; color: black;">RX ARQ<o:p></o:p></span></b></p> <p class="MsoNormal" style=""><span style="color: black;">Automates the “receive” request for BSR Note: For auto BSR, both transmit and receive<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">stations must have Auto open BSR Request, TX ARQ and RX ARQ checked.<o:p></o:p></span></p> <p class="MsoNormal" style=""><b><span style="font-family: TimesNewRomanPS-BoldMT; color: black;">BSR </span></b><span style="color: black;">(button)<o:p></o:p></span></p> <p class="MsoNormal" style=""><b><span style="font-size: 13pt; font-family: Arial-BoldMT; color: black;">Bad Segment Report<o:p></o:p></span></b></p> <p class="MsoNormal" style=""><span style="color: black;">When a picture is received with segments missing, a left click on this button will display<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">the number of segments. Press “OK” to request these segments be re-sent.<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">26<o:p></o:p></span></p> <p class="MsoNormal" style=""><b><span style="font-family: TimesNewRomanPS-BoldMT; color: black;">SPA </span></b><span style="color: black;">(button)<o:p></o:p></span></p> <p class="MsoNormal" style=""><b><span style="font-size: 13pt; font-family: Arial-BoldMT; color: black;">Show Picture Anyway<o:p></o:p></span></b></p> <p class="MsoNormal" style=""><span style="color: black;">Left click on this button will attempt to associate and display the last received picture<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">even if it the file is incomplete. If there is enough data for the picture to partially<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">assemble the picture, it will be displayed. Dependent up on the amount of missing data<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">(memory segments) and preference of the received station, the user may then click on the<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">BSR button to show the number of segments missing. Now, the BSR the request can be<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">made to resend the missing data. The picture above is an example of a picture displayed<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">using the SPA with missing segments.<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">Picture shown “repaired” after receiving the missing 35 segments using the BSR request<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">procedure. Note: This entire procedure may be automated when the “Auto Open BSR,”<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">“TX ARQ” and “RX ARQ” checked.<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">27<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">Example of the transmitting station’s responding to a BSR request. Note: This is not the<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">data used in the previous repaired picture.<o:p></o:p></span></p> <p class="MsoNormal" style=""><b><span style="font-family: TimesNewRomanPS-BoldMT; color: black;">G </span></b><span style="color: black;">(button – works with Windows XP only)<o:p></o:p></span></p> <p class="MsoNormal" style=""><b><span style="font-family: TimesNewRomanPS-BoldMT; color: black;">Good </span></b><span style="color: black;">(good picture received)<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">Left click on </span><b><span style="font-family: TimesNewRomanPS-BoldMT; color: black;">G </span></b><span style="color: black;">will transmit a pre-recorded wave file displaying “GOOD” in<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">the received station’s waterfall. Filename: g.wav<o:p></o:p></span></p> <p class="MsoNormal" style=""><b><span style="font-family: TimesNewRomanPS-BoldMT; color: black;">B </span></b><span style="color: black;">(button – works with Windows XP only)<o:p></o:p></span></p> <p class="MsoNormal" style=""><b><span style="font-family: TimesNewRomanPS-BoldMT; color: black;">BAD </span></b><span style="color: black;">(bad picture received)<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">Left click on </span><b><span style="font-family: TimesNewRomanPS-BoldMT; color: black;">B </span></b><span style="color: black;">will transmit a pre-recorded wave file displaying “BAD” in<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">the received station’s waterfall. Filename: b.wav<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">28<o:p></o:p></span></p> <p class="MsoNormal" style=""><b><span style="font-family: TimesNewRomanPS-BoldMT; color: black;">ID </span></b><span style="color: black;">(button – works with Windows XP only) Left click on </span><b><span style="font-family: TimesNewRomanPS-BoldMT; color: black;">ID </span></b><span style="color: black;">will transmit a pre-recorded<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">wave file displaying the transmitting station’s call sign in the received station’s waterfall.<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">Filename: id.wav<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">For help in creating these wave files, go to KB4YZ’s web site:<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: blue;">http://www.kiva.net/~djones/index.htm<o:p></o:p></span></p> <p class="MsoNormal" style=""><b><span style="font-family: TimesNewRomanPS-BoldMT; color: black;">TUNE </span></b><span style="color: black;">(button)<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">Left click on TUNE will transmit a pre-recorded wave file for setting the proper output<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">level of the transmitter. Three reference pilot (sync) carriers will be displayed in the<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">received station’s waterfall. From left to right, A=1850Hz, B=1475Hz and C=725Hz.<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">With a properly adjust transmitter (good linearity – not overdriven!), the receiving station<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">will </span><i><span style="font-family: TimesNewRomanPS-ItalicMT; color: black;">only </span></i><span style="color: black;">see these 3 carriers. Any others displayed (at the receiving station) are products<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">of inter-modulation distortion which will degrade performance. See KB4YZ’s WinDRM<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">tuning file at </span><span style="color: blue;">http://www.tima.com/~djones/drmtune.htm</span><span style="color: black;">. Non-linearity can cause<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">spectral re-growth of unwanted carriers. Driving the typical transceiver and/or power<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">amplifier too hard will cause this spectral regrowth (unwanted carriers). Yes it is just as<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">bad as it sounds and it should be avoided. Drive 100w transceivers to only 20w max<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">average and a typical 1kw amps to 200w average power. For the adverse effects caused<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">by non linear transmissions, see </span><span style="color: blue;">http://www.tima.com/~djones/DRM_power.htm<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">29<o:p></o:p></span></p> <p class="MsoNormal" style=""><b><span style="font-family: TimesNewRomanPS-BoldMT; color: black;">TX Pic </span></b><span style="color: black;">(button)<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">Left click opens a window to add or remove files for transmission. Radio buttons enable<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">from 1 to 3 instances of the file be transmitted. Additional instances of the same file may<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">be sent by adding the file multiple times in the Select Files window. Long Leadin<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">increases the time for sync data at the beginning of the transmission. This is used in the<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">presence of weaker signal conditions or QRM to help ensure the sync is made at the<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">receiving station prior to sending the file data. </span><i><span style="font-family: TimesNewRomanPS-ItalicMT; color: black;">Return </span></i><span style="color: black;">button closes and returns to the<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">opening WinDRM display. </span><i><span style="font-family: TimesNewRomanPS-ItalicMT; color: black;">TX </span></i><span style="color: black;">button starts transmission of sync data followed by the<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">file data.<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">30<o:p></o:p></span></p> <p class="MsoNormal" style=""><b><span style="font-size: 13pt; font-family: Arial-BoldMT; color: black;">TX Voice </span></b><span style="color: black;">(button)<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">Left click starts a voice transmission (or if in focus, tap the spacebar). The microphone<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">must be connected to the soundcard’s “MIC” input. The display graphically shows the<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">transmit microphone level (sound card’s microphone input). Adjust the mixer’s Record<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">slider while speaking across the PC microphone. Best results will be found when the<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">microphone input level is kept rather low while speaking in a loud tone of voice. Keep<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">the average level so peaks fill approximately 50-75% of the display. Speaking too loud<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">will cause the display to turn red. Some PC electret microphones have poor non-linear<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">response and may sound “basey” yet tend to accentuate the highs which cause high peaks<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">and distortion in this application. Experiment in this area to find the best microphone and<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">level for the highest speech quality The audio filter may help the intelligence of the<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">speech in some conditions. SPEEX sounds like it adds more fidelity to the speech (when<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">compared to LPC) but at the same time, it is a bit muffled and tends to “flat top” the input<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">easier. This is an area where a well chosen microphone (such as a one from Heil Sound)<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">will improve the voice quality. The input impedance of most sound cards microphone is<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">approximately 2500 ohms. This impedance may vary but should be a consideration when<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">choosing a microphone. The TX button name changes to “RX” while transmitting.<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">“Echo” of the decoded voice may be caused by some combinations of PC and soundcard.<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">This may be a soundcard latency problem related to the timing and transfer of data or a<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">ground loop. Changing sound cards may correct this problem. Known “good” low cost<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">sound cards include M-Audio, and Sound Blaster Audigy series. When retuning to<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">Receive, the button label will momentarily display “Wait” (for approximately 2 seconds)<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">while the transmit buffer empties. If the “Remote” feature is activated (PTT on DSR or<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">PTT CTS checked under Setup><st1:place st="on"><st1:placename st="on">PTT</st1:placename> <st1:placetype st="on">Port</st1:placetype></st1:place>), the TX Voice button is disabled and will<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">display Remote.<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">Note: A very small low cost (less than $10 USD) USB sound card by C-Media (HE-<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">280B has shown to perform very well with WinDRM. It may be found at<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: blue;">www.geeks.com </span><span style="color: black;">Or use a USB headset such as the Logitec model 250 or 350.<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">31<o:p></o:p></span></p> <p class="MsoNormal" style=""><b><span style="font-size: 13pt; font-family: Arial-BoldMT; color: black;">RESET </span></b><span style="color: black;">(button)<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">Reset re-starts the sync process in receive. Normally, this button is rarely needed.<o:p></o:p></span></p> <p class="MsoNormal" style=""><b><i><span style="font-size: 13pt; font-family: Arial-BoldItalicMT; color: black;">About<o:p></o:p></span></i></b></p> <p class="MsoNormal" style=""><b><span style="font-size: 13pt; font-family: Arial-BoldMT; color: black;">Info<o:p></o:p></span></b></p> <p class="MsoNormal" style=""><span style="color: black;">32<o:p></o:p></span></p> <p class="MsoNormal" style=""><b><i><span style="font-size: 13pt; font-family: Arial-BoldItalicMT; color: black;">About<o:p></o:p></span></i></b></p> <p class="MsoNormal" style=""><b><span style="font-size: 13pt; font-family: Arial-BoldMT; color: black;">Help<o:p></o:p></span></b></p> <p class="MsoNormal" style=""><span style="color: black;">33<o:p></o:p></span></p> <p class="MsoNormal" style=""><b><span style="font-size: 13pt; font-family: Arial-BoldMT; color: black;">Typical connections between PC, interface and radio<o:p></o:p></span></b></p> <p class="MsoNormal" style=""><span style="color: black;">See “<st1:place st="on"><st1:placename st="on">Setup</st1:placename> <st1:placename st="on">PTT</st1:placename> <st1:placetype st="on">Port</st1:placetype></st1:place>” info in this doc for more information on these connections. Any<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">available com port 1 thru 8 may be used for all functions (PTT, Spacebar PTT, Remote<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: black;">PTT and Transceiver Speaker Mute).<o:p></o:p></span></p> <p class="MsoNormal" style=""><b><span style="font-size: 13pt; font-family: Arial-BoldMT; color: black;">Further DRM technical info and software </span></b><span style="color: black;">may be found at:<o:p></o:p></span></p> <p class="MsoNormal" style=""><span style="color: blue;">http://www.drmrx.org/</span><span style="color: black;">, (DREAM 1.10.6cvs or later) and </span><span style="color: blue;">www.drmradio.co.uk<o:p></o:p></span></p> <p class="MsoNormal" style=""><b><span style="font-size: 13pt; font-family: Arial-BoldMT; color: black;">------------------------------------------ -------------- ------------------------------------------<o:p></o:p></span></b></p> <p class="MsoNormal" style=""><i><span style="font-size: 10pt; font-family: Arial-ItalicMT; color: black;">updated 23-Jul-2008<o:p></o:p></span></i></p> <p class="MsoNormal"><i><span style="font-size: 10pt; font-family: Arial-ItalicMT; color: black;">© copyright 2005-2008 by Mel Whitten, KØPFX </span></i><i><span style="font-size: 10pt; font-family: Arial-ItalicMT; color: black;">– </span></i><i><span style="font-size: 10pt; font-family: Arial-ItalicMT; color: blue;"><a href="mailto:mel@melwhitten.com">mel@melwhitten.com</a><o:p></o:p></span></i></p> <p class="MsoNormal"><i><span style="font-size: 10pt; font-family: Arial-ItalicMT; color: blue;"><o:p> </o:p></span></i></p> <h3>Suggested Frequencies:<span style=""> </span>(Warning – most of these are from web pages dated two or more years ago…things look bad)</h3> <p class="MsoNormal"><b>80 Meters:</b></p> <p>3.606 net, 7pm CST, usually daily except Saturdays</p> <p><b>40 Meters:</b></p> <p>7.130 2230Z net
<br />7.096 EU
<br />7.169.33, 7.170, 7.173, 7.177, 7.286, 7.291 (USB)
<br /><b>20 Meters:</b></p> <p>14.255 EU</p> <p><b>Monday-Friday daily net</b> at 11AM Eastern time - 14.236
<br /><b>Saturday/Sunday net</b> at 1900 UTC - 14.236</p> <p>14.236 is most popular AOR frequency</p> <p><b>17 Meters:</b></p> <p>18.1625
<br /><b>15 Meters:</b></p> <p>21.370</p> <p class="MsoNormal">Sorry, many dead links on the AOR and FDMDV pages – especially the on-line finder for skeds</p> <p class="MsoNormal"><o:p> </o:p></p> <p class="MsoNormal"><a href="http://n1su.com/aor-ard-9800.html">http://n1su.com/aor-ard-9800.html</a></p> <p class="MsoNormal"><a href="http://n1su.com/fdmdv/download.html">http://n1su.com/fdmdv/download.html</a></p> <p class="MsoNormal"><o:p> </o:p></p> WR5Jhttp://www.blogger.com/profile/16316513702643319581noreply@blogger.com0tag:blogger.com,1999:blog-4632435085083780021.post-31023457919489834492009-08-16T22:39:00.000-07:002009-08-16T22:41:42.083-07:00Blog-Post -11-Packet Radio by AGW Packet Engine<meta equiv="Content-Type" content="text/html; charset=utf-8"><meta name="ProgId" content="Word.Document"><meta name="Generator" content="Microsoft Word 11"><meta name="Originator" content="Microsoft Word 11"><link rel="File-List" href="file:///C:%5CDOCUME%7E1%5CC11AE%7E1.BLA%5CLOCALS%7E1%5CTemp%5Cmsohtml1%5C01%5Cclip_filelist.xml"><link rel="Edit-Time-Data" href="file:///C:%5CDOCUME%7E1%5CC11AE%7E1.BLA%5CLOCALS%7E1%5CTemp%5Cmsohtml1%5C01%5Cclip_editdata.mso"><!--[if !mso]> <style> v\:* {behavior:url(#default#VML);} o\:* {behavior:url(#default#VML);} w\:* {behavior:url(#default#VML);} .shape {behavior:url(#default#VML);} </style> <![endif]--><o:smarttagtype namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="City"></o:smarttagtype><o:smarttagtype namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="place"></o:smarttagtype><o:smarttagtype namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="PlaceName"></o:smarttagtype><o:smarttagtype namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="PlaceType"></o:smarttagtype><!--[if gte mso 9]><xml> <w:worddocument> <w:view>Normal</w:View> <w:zoom>0</w:Zoom> <w:punctuationkerning/> <w:validateagainstschemas/> <w:saveifxmlinvalid>false</w:SaveIfXMLInvalid> <w:ignoremixedcontent>false</w:IgnoreMixedContent> <w:alwaysshowplaceholdertext>false</w:AlwaysShowPlaceholderText> <w:compatibility> <w:breakwrappedtables/> <w:snaptogridincell/> <w:wraptextwithpunct/> <w:useasianbreakrules/> <w:dontgrowautofit/> </w:Compatibility> <w:browserlevel>MicrosoftInternetExplorer4</w:BrowserLevel> </w:WordDocument> </xml><![endif]--><!--[if gte mso 9]><xml> <w:latentstyles deflockedstate="false" latentstylecount="156"> </w:LatentStyles> </xml><![endif]--><!--[if !mso]><object classid="clsid:38481807-CA0E-42D2-BF39-B33AF135CC4D" id="ieooui"></object> <style> st1\:*{behavior:url(#ieooui) } </style> <![endif]--><style> <!-- /* Font Definitions */ @font-face {font-family:Wingdings; panose-1:5 0 0 0 0 0 0 0 0 0; mso-font-charset:2; mso-generic-font-family:auto; mso-font-pitch:variable; mso-font-signature:0 268435456 0 0 -2147483648 0;} @font-face {font-family:Century; panose-1:2 4 6 3 5 7 5 2 3 3; mso-font-alt:"Lucida Bright"; mso-font-charset:0; mso-generic-font-family:roman; mso-font-format:other; mso-font-pitch:variable; mso-font-signature:3 0 0 0 1 0;} @font-face {font-family:Verdana; panose-1:2 11 6 4 3 5 4 4 2 4; mso-font-charset:0; mso-generic-font-family:swiss; mso-font-pitch:variable; mso-font-signature:536871559 0 0 0 415 0;} /* Style Definitions */ p.MsoNormal, li.MsoNormal, div.MsoNormal {mso-style-parent:""; margin:0in; margin-bottom:.0001pt; mso-pagination:widow-orphan; font-size:12.0pt; font-family:"Times New Roman"; mso-fareast-font-family:"Times New Roman";} h2 {mso-margin-top-alt:auto; margin-right:0in; mso-margin-bottom-alt:auto; margin-left:0in; mso-pagination:widow-orphan; mso-outline-level:2; font-size:18.0pt; font-family:"Times New Roman"; font-weight:bold;} h3 {mso-style-next:Normal; margin-top:12.0pt; margin-right:0in; margin-bottom:3.0pt; margin-left:0in; mso-pagination:widow-orphan; page-break-after:avoid; mso-outline-level:3; font-size:13.0pt; font-family:Arial; font-weight:bold;} h4 {mso-margin-top-alt:auto; margin-right:0in; mso-margin-bottom-alt:auto; margin-left:0in; mso-pagination:widow-orphan; mso-outline-level:4; font-size:12.0pt; font-family:"Times New Roman"; font-weight:bold;} h5 {mso-margin-top-alt:auto; margin-right:0in; mso-margin-bottom-alt:auto; margin-left:0in; mso-pagination:widow-orphan; mso-outline-level:5; font-size:10.0pt; font-family:"Times New Roman"; font-weight:bold;} a:link, span.MsoHyperlink {color:blue; text-decoration:underline; text-underline:single;} a:visited, span.MsoHyperlinkFollowed {color:purple; text-decoration:underline; text-underline:single;} p {mso-margin-top-alt:auto; margin-right:0in; mso-margin-bottom-alt:auto; margin-left:0in; mso-pagination:widow-orphan; font-size:12.0pt; font-family:"Times New Roman"; mso-fareast-font-family:"Times New Roman";} tt {font-family:"Courier New"; mso-ascii-font-family:"Courier New"; mso-fareast-font-family:"Times New Roman"; mso-hansi-font-family:"Courier New"; mso-bidi-font-family:"Courier New";} @page Section1 {size:8.5in 11.0in; margin:1.0in 1.25in 1.0in 1.25in; mso-header-margin:.5in; mso-footer-margin:.5in; mso-paper-source:0;} div.Section1 {page:Section1;} /* List Definitions */ @list l0 {mso-list-id:39012910; mso-list-template-ids:203694652;} @list l0:level1 {mso-level-number-format:bullet; mso-level-text:; mso-level-tab-stop:.5in; mso-level-number-position:left; text-indent:-.25in; mso-ansi-font-size:10.0pt; font-family:Symbol;} @list l0:level2 {mso-level-number-format:bullet; mso-level-text:o; mso-level-tab-stop:1.0in; mso-level-number-position:left; text-indent:-.25in; mso-ansi-font-size:10.0pt; font-family:"Courier New"; mso-bidi-font-family:"Times New Roman";} @list l1 {mso-list-id:63571754; mso-list-template-ids:850925464;} @list l1:level1 {mso-level-number-format:bullet; mso-level-text:; mso-level-tab-stop:.5in; mso-level-number-position:left; text-indent:-.25in; mso-ansi-font-size:10.0pt; font-family:Symbol;} @list l2 {mso-list-id:78210913; mso-list-template-ids:-1928562070;} @list l2:level1 {mso-level-number-format:bullet; mso-level-text:; mso-level-tab-stop:.5in; mso-level-number-position:left; text-indent:-.25in; mso-ansi-font-size:10.0pt; font-family:Symbol;} @list l3 {mso-list-id:82992645; mso-list-template-ids:-2135147104;} @list l3:level1 {mso-level-number-format:bullet; mso-level-text:; mso-level-tab-stop:.5in; mso-level-number-position:left; text-indent:-.25in; mso-ansi-font-size:10.0pt; font-family:Symbol;} @list l3:level2 {mso-level-number-format:bullet; mso-level-text:o; mso-level-tab-stop:1.0in; mso-level-number-position:left; text-indent:-.25in; mso-ansi-font-size:10.0pt; font-family:"Courier New"; mso-bidi-font-family:"Times New Roman";} @list l4 {mso-list-id:98067337; mso-list-template-ids:-2094914850;} @list l4:level1 {mso-level-number-format:bullet; mso-level-text:; mso-level-tab-stop:.5in; mso-level-number-position:left; text-indent:-.25in; mso-ansi-font-size:10.0pt; font-family:Symbol;} @list l4:level2 {mso-level-number-format:bullet; mso-level-text:o; mso-level-tab-stop:1.0in; mso-level-number-position:left; text-indent:-.25in; mso-ansi-font-size:10.0pt; font-family:"Courier New"; mso-bidi-font-family:"Times New Roman";} @list l5 {mso-list-id:145513025; mso-list-template-ids:1946590738;} @list l5:level1 {mso-level-number-format:bullet; mso-level-text:; mso-level-tab-stop:.5in; mso-level-number-position:left; text-indent:-.25in; mso-ansi-font-size:10.0pt; font-family:Symbol;} @list l6 {mso-list-id:152379122; mso-list-template-ids:-1227596932;} @list l6:level1 {mso-level-number-format:bullet; mso-level-text:; mso-level-tab-stop:.5in; mso-level-number-position:left; text-indent:-.25in; mso-ansi-font-size:10.0pt; font-family:Symbol;} @list l7 {mso-list-id:254018525; mso-list-template-ids:-992938398;} @list l7:level1 {mso-level-number-format:bullet; mso-level-text:; mso-level-tab-stop:.5in; mso-level-number-position:left; text-indent:-.25in; mso-ansi-font-size:10.0pt; font-family:Symbol;} @list l7:level2 {mso-level-number-format:bullet; mso-level-text:o; mso-level-tab-stop:1.0in; mso-level-number-position:left; text-indent:-.25in; mso-ansi-font-size:10.0pt; font-family:"Courier New"; mso-bidi-font-family:"Times New Roman";} @list l8 {mso-list-id:255794809; mso-list-template-ids:1891297168;} @list l8:level1 {mso-level-number-format:bullet; mso-level-text:; mso-level-tab-stop:.5in; mso-level-number-position:left; text-indent:-.25in; mso-ansi-font-size:10.0pt; font-family:Symbol;} @list l9 {mso-list-id:264190905; mso-list-template-ids:-901510184;} @list l9:level1 {mso-level-number-format:bullet; mso-level-text:; mso-level-tab-stop:.5in; mso-level-number-position:left; text-indent:-.25in; mso-ansi-font-size:10.0pt; font-family:Symbol;} @list l10 {mso-list-id:320079800; mso-list-template-ids:-2050048842;} @list l10:level1 {mso-level-number-format:bullet; mso-level-text:; mso-level-tab-stop:.5in; mso-level-number-position:left; text-indent:-.25in; mso-ansi-font-size:10.0pt; font-family:Symbol;} @list l11 {mso-list-id:359474373; mso-list-template-ids:-1937203362;} @list l11:level1 {mso-level-number-format:bullet; mso-level-text:; mso-level-tab-stop:.5in; mso-level-number-position:left; text-indent:-.25in; mso-ansi-font-size:10.0pt; font-family:Symbol;} @list l11:level2 {mso-level-number-format:bullet; mso-level-text:o; mso-level-tab-stop:1.0in; mso-level-number-position:left; text-indent:-.25in; mso-ansi-font-size:10.0pt; font-family:"Courier New"; mso-bidi-font-family:"Times New Roman";} @list l12 {mso-list-id:371878687; mso-list-template-ids:-1994076788;} @list l12:level1 {mso-level-number-format:bullet; mso-level-text:; mso-level-tab-stop:.5in; mso-level-number-position:left; text-indent:-.25in; mso-ansi-font-size:10.0pt; font-family:Symbol;} @list l13 {mso-list-id:383260203; mso-list-template-ids:1744231438;} @list l13:level1 {mso-level-number-format:bullet; mso-level-text:; mso-level-tab-stop:.5in; mso-level-number-position:left; text-indent:-.25in; mso-ansi-font-size:10.0pt; font-family:Symbol;} @list l14 {mso-list-id:390353653; mso-list-template-ids:-1337981926;} @list l14:level1 {mso-level-number-format:bullet; mso-level-text:; mso-level-tab-stop:.5in; mso-level-number-position:left; text-indent:-.25in; mso-ansi-font-size:10.0pt; font-family:Symbol;} @list l15 {mso-list-id:525873806; mso-list-template-ids:2129432790;} @list l15:level1 {mso-level-number-format:bullet; mso-level-text:; mso-level-tab-stop:.5in; mso-level-number-position:left; text-indent:-.25in; mso-ansi-font-size:10.0pt; font-family:Symbol;} @list l16 {mso-list-id:561644311; mso-list-template-ids:-2036711158;} @list l16:level1 {mso-level-number-format:bullet; mso-level-text:; mso-level-tab-stop:.5in; mso-level-number-position:left; text-indent:-.25in; mso-ansi-font-size:10.0pt; font-family:Symbol;} @list l16:level2 {mso-level-number-format:bullet; mso-level-text:o; mso-level-tab-stop:1.0in; mso-level-number-position:left; text-indent:-.25in; mso-ansi-font-size:10.0pt; font-family:"Courier New"; mso-bidi-font-family:"Times New Roman";} @list l17 {mso-list-id:572861820; mso-list-template-ids:1012666518;} @list l17:level1 {mso-level-number-format:bullet; mso-level-text:; mso-level-tab-stop:.5in; mso-level-number-position:left; text-indent:-.25in; mso-ansi-font-size:10.0pt; font-family:Symbol;} @list l17:level2 {mso-level-number-format:bullet; mso-level-text:o; mso-level-tab-stop:1.0in; mso-level-number-position:left; text-indent:-.25in; mso-ansi-font-size:10.0pt; font-family:"Courier New"; mso-bidi-font-family:"Times New Roman";} @list l18 {mso-list-id:581184389; mso-list-template-ids:-1737835318;} @list l18:level1 {mso-level-number-format:bullet; mso-level-text:; mso-level-tab-stop:.5in; mso-level-number-position:left; text-indent:-.25in; mso-ansi-font-size:10.0pt; font-family:Symbol;} @list l19 {mso-list-id:586571265; mso-list-template-ids:684333440;} @list l19:level1 {mso-level-number-format:bullet; mso-level-text:; mso-level-tab-stop:.5in; mso-level-number-position:left; text-indent:-.25in; mso-ansi-font-size:10.0pt; font-family:Symbol;} @list l20 {mso-list-id:600840721; mso-list-template-ids:1555744182;} @list l20:level1 {mso-level-number-format:bullet; mso-level-text:; mso-level-tab-stop:.5in; mso-level-number-position:left; text-indent:-.25in; mso-ansi-font-size:10.0pt; font-family:Symbol;} @list l21 {mso-list-id:638150797; mso-list-template-ids:-1859344134;} @list l21:level1 {mso-level-number-format:bullet; mso-level-text:; mso-level-tab-stop:.5in; mso-level-number-position:left; text-indent:-.25in; mso-ansi-font-size:10.0pt; font-family:Symbol;} @list l21:level2 {mso-level-number-format:bullet; mso-level-text:o; mso-level-tab-stop:1.0in; mso-level-number-position:left; text-indent:-.25in; mso-ansi-font-size:10.0pt; font-family:"Courier New"; mso-bidi-font-family:"Times New Roman";} @list l21:level3 {mso-level-number-format:bullet; mso-level-text:; mso-level-tab-stop:1.5in; mso-level-number-position:left; text-indent:-.25in; mso-ansi-font-size:10.0pt; font-family:Wingdings;} @list l22 {mso-list-id:699823941; mso-list-template-ids:-1480130880;} @list l22:level1 {mso-level-number-format:bullet; mso-level-text:; mso-level-tab-stop:.5in; mso-level-number-position:left; text-indent:-.25in; mso-ansi-font-size:10.0pt; font-family:Symbol;} @list l23 {mso-list-id:755512669; mso-list-template-ids:-938284280;} @list l23:level1 {mso-level-number-format:bullet; mso-level-text:; mso-level-tab-stop:.5in; mso-level-number-position:left; text-indent:-.25in; mso-ansi-font-size:10.0pt; font-family:Symbol;} @list l24 {mso-list-id:869489047; mso-list-template-ids:1474733336;} @list l24:level1 {mso-level-number-format:image; list-style-image:url("file:///C:/DOCUME~1/C11AE~1.BLA/LOCALS~1/Temp/msohtml1/01/clip_image001.gif"); mso-level-text:; mso-level-tab-stop:.5in; mso-level-number-position:left; text-indent:-.25in; mso-ansi-font-size:10.0pt; font-family:Symbol;} @list l25 {mso-list-id:925990733; mso-list-template-ids:-64325250;} @list l25:level1 {mso-level-number-format:bullet; mso-level-text:; mso-level-tab-stop:.5in; mso-level-number-position:left; text-indent:-.25in; mso-ansi-font-size:10.0pt; font-family:Symbol;} @list l25:level2 {mso-level-number-format:bullet; mso-level-text:o; mso-level-tab-stop:1.0in; mso-level-number-position:left; text-indent:-.25in; mso-ansi-font-size:10.0pt; font-family:"Courier New"; mso-bidi-font-family:"Times New Roman";} @list l26 {mso-list-id:929460482; mso-list-template-ids:1177944592;} @list l26:level1 {mso-level-number-format:bullet; mso-level-text:; mso-level-tab-stop:.5in; mso-level-number-position:left; text-indent:-.25in; mso-ansi-font-size:10.0pt; font-family:Symbol;} @list l26:level2 {mso-level-number-format:bullet; mso-level-text:o; mso-level-tab-stop:1.0in; mso-level-number-position:left; text-indent:-.25in; mso-ansi-font-size:10.0pt; font-family:"Courier New"; mso-bidi-font-family:"Times New Roman";} @list l27 {mso-list-id:934246908; mso-list-template-ids:561442546;} @list l27:level1 {mso-level-number-format:bullet; mso-level-text:; mso-level-tab-stop:.5in; mso-level-number-position:left; text-indent:-.25in; mso-ansi-font-size:10.0pt; font-family:Symbol;} @list l28 {mso-list-id:1009603587; mso-list-template-ids:-1723188122;} @list l28:level1 {mso-level-number-format:bullet; mso-level-text:; mso-level-tab-stop:.5in; mso-level-number-position:left; text-indent:-.25in; mso-ansi-font-size:10.0pt; font-family:Symbol;} @list l29 {mso-list-id:1010642423; mso-list-template-ids:671150324;} @list l29:level1 {mso-level-number-format:bullet; mso-level-text:; mso-level-tab-stop:.5in; mso-level-number-position:left; text-indent:-.25in; mso-ansi-font-size:10.0pt; font-family:Symbol;} @list l30 {mso-list-id:1027177468; mso-list-template-ids:-1652118488;} @list l30:level1 {mso-level-number-format:bullet; mso-level-text:; mso-level-tab-stop:.5in; mso-level-number-position:left; text-indent:-.25in; mso-ansi-font-size:10.0pt; font-family:Symbol;} @list l31 {mso-list-id:1069576068; mso-list-template-ids:-353102110;} @list l31:level1 {mso-level-number-format:bullet; mso-level-text:; mso-level-tab-stop:.5in; mso-level-number-position:left; text-indent:-.25in; mso-ansi-font-size:10.0pt; font-family:Symbol;} @list l32 {mso-list-id:1073355271; mso-list-template-ids:1374584268;} @list l32:level1 {mso-level-number-format:bullet; mso-level-text:; mso-level-tab-stop:.5in; mso-level-number-position:left; text-indent:-.25in; mso-ansi-font-size:10.0pt; font-family:Symbol;} @list l33 {mso-list-id:1085565271; mso-list-template-ids:-718265564;} @list l33:level1 {mso-level-number-format:bullet; mso-level-text:; mso-level-tab-stop:.5in; mso-level-number-position:left; text-indent:-.25in; mso-ansi-font-size:10.0pt; font-family:Symbol;} @list l34 {mso-list-id:1123811914; mso-list-template-ids:629979726;} @list l34:level1 {mso-level-number-format:bullet; mso-level-text:; mso-level-tab-stop:.5in; mso-level-number-position:left; text-indent:-.25in; mso-ansi-font-size:10.0pt; font-family:Symbol;} @list l35 {mso-list-id:1134641702; mso-list-template-ids:-2010353192;} @list l35:level1 {mso-level-number-format:bullet; mso-level-text:; mso-level-tab-stop:.5in; mso-level-number-position:left; text-indent:-.25in; mso-ansi-font-size:10.0pt; font-family:Symbol;} @list l36 {mso-list-id:1184707915; mso-list-template-ids:1700045642;} @list l36:level1 {mso-level-number-format:bullet; mso-level-text:; mso-level-tab-stop:.5in; mso-level-number-position:left; text-indent:-.25in; mso-ansi-font-size:10.0pt; font-family:Symbol;} @list l36:level2 {mso-level-number-format:bullet; mso-level-text:o; mso-level-tab-stop:1.0in; mso-level-number-position:left; text-indent:-.25in; mso-ansi-font-size:10.0pt; font-family:"Courier New"; mso-bidi-font-family:"Times New Roman";} @list l37 {mso-list-id:1225263571; mso-list-template-ids:1224655206;} @list l37:level1 {mso-level-number-format:bullet; mso-level-text:; mso-level-tab-stop:.5in; mso-level-number-position:left; text-indent:-.25in; mso-ansi-font-size:10.0pt; font-family:Symbol;} @list l38 {mso-list-id:1228999705; mso-list-template-ids:-1225500202;} @list l38:level1 {mso-level-number-format:bullet; mso-level-text:; mso-level-tab-stop:.5in; mso-level-number-position:left; text-indent:-.25in; mso-ansi-font-size:10.0pt; font-family:Symbol;} @list l39 {mso-list-id:1264265940; mso-list-template-ids:2106464336;} @list l39:level1 {mso-level-number-format:bullet; mso-level-text:; mso-level-tab-stop:.5in; mso-level-number-position:left; text-indent:-.25in; mso-ansi-font-size:10.0pt; font-family:Symbol;} @list l40 {mso-list-id:1310550468; mso-list-template-ids:-1798818088;} @list l40:level1 {mso-level-number-format:bullet; mso-level-text:; mso-level-tab-stop:.5in; mso-level-number-position:left; text-indent:-.25in; mso-ansi-font-size:10.0pt; font-family:Symbol;} @list l41 {mso-list-id:1352218220; mso-list-template-ids:878362934;} @list l41:level1 {mso-level-number-format:bullet; mso-level-text:; mso-level-tab-stop:.5in; mso-level-number-position:left; text-indent:-.25in; mso-ansi-font-size:10.0pt; font-family:Symbol;} @list l42 {mso-list-id:1388336955; mso-list-template-ids:2005552538;} @list l42:level1 {mso-level-number-format:bullet; mso-level-text:; mso-level-tab-stop:.5in; mso-level-number-position:left; text-indent:-.25in; mso-ansi-font-size:10.0pt; font-family:Symbol;} @list l43 {mso-list-id:1521165797; mso-list-template-ids:413450324;} @list l43:level1 {mso-level-number-format:bullet; mso-level-text:; mso-level-tab-stop:.5in; mso-level-number-position:left; text-indent:-.25in; mso-ansi-font-size:10.0pt; font-family:Symbol;} @list l44 {mso-list-id:1577011158; mso-list-template-ids:535707172;} @list l44:level1 {mso-level-number-format:image; list-style-image:url("PicExportError"); mso-level-text:; mso-level-tab-stop:.5in; mso-level-number-position:left; text-indent:-.25in; mso-ansi-font-size:10.0pt; font-family:Symbol;} @list l45 {mso-list-id:1603412809; mso-list-template-ids:-420309716;} @list l45:level1 {mso-level-number-format:bullet; mso-level-text:; mso-level-tab-stop:.5in; mso-level-number-position:left; text-indent:-.25in; mso-ansi-font-size:10.0pt; font-family:Symbol;} @list l45:level2 {mso-level-number-format:bullet; mso-level-text:o; mso-level-tab-stop:1.0in; mso-level-number-position:left; text-indent:-.25in; mso-ansi-font-size:10.0pt; font-family:"Courier New"; mso-bidi-font-family:"Times New Roman";} @list l45:level3 {mso-level-number-format:bullet; mso-level-text:; mso-level-tab-stop:1.5in; mso-level-number-position:left; text-indent:-.25in; mso-ansi-font-size:10.0pt; font-family:Wingdings;} @list l46 {mso-list-id:1655139028; mso-list-template-ids:195297862;} @list l46:level1 {mso-level-number-format:bullet; mso-level-text:; mso-level-tab-stop:.5in; mso-level-number-position:left; text-indent:-.25in; mso-ansi-font-size:10.0pt; font-family:Symbol;} @list l47 {mso-list-id:1682970933; mso-list-template-ids:-1890402460;} @list l47:level1 {mso-level-number-format:bullet; mso-level-text:; mso-level-tab-stop:.5in; mso-level-number-position:left; text-indent:-.25in; mso-ansi-font-size:10.0pt; font-family:Symbol;} @list l47:level2 {mso-level-number-format:bullet; mso-level-text:o; mso-level-tab-stop:1.0in; mso-level-number-position:left; text-indent:-.25in; mso-ansi-font-size:10.0pt; font-family:"Courier New"; mso-bidi-font-family:"Times New Roman";} @list l48 {mso-list-id:1691563860; mso-list-template-ids:-1878368356;} @list l48:level1 {mso-level-number-format:bullet; mso-level-text:; mso-level-tab-stop:.5in; mso-level-number-position:left; text-indent:-.25in; mso-ansi-font-size:10.0pt; font-family:Symbol;} @list l49 {mso-list-id:1694383572; mso-list-template-ids:1430160462;} @list l49:level1 {mso-level-number-format:bullet; mso-level-text:; mso-level-tab-stop:.5in; mso-level-number-position:left; text-indent:-.25in; mso-ansi-font-size:10.0pt; font-family:Symbol;} @list l50 {mso-list-id:1709257291; mso-list-template-ids:1448662992;} @list l50:level1 {mso-level-number-format:bullet; mso-level-text:; mso-level-tab-stop:.5in; mso-level-number-position:left; text-indent:-.25in; mso-ansi-font-size:10.0pt; font-family:Symbol;} @list l51 {mso-list-id:1730226866; mso-list-template-ids:1967174754;} @list l51:level1 {mso-level-number-format:bullet; mso-level-text:; mso-level-tab-stop:.5in; mso-level-number-position:left; text-indent:-.25in; mso-ansi-font-size:10.0pt; font-family:Symbol;} @list l52 {mso-list-id:1759860120; mso-list-template-ids:-503801224;} @list l52:level1 {mso-level-number-format:bullet; mso-level-text:; mso-level-tab-stop:.5in; mso-level-number-position:left; text-indent:-.25in; mso-ansi-font-size:10.0pt; font-family:Symbol;} @list l52:level2 {mso-level-number-format:bullet; mso-level-text:o; mso-level-tab-stop:1.0in; mso-level-number-position:left; text-indent:-.25in; mso-ansi-font-size:10.0pt; font-family:"Courier New"; mso-bidi-font-family:"Times New Roman";} @list l53 {mso-list-id:1790471739; mso-list-template-ids:1035000464;} @list l53:level1 {mso-level-number-format:bullet; mso-level-text:; mso-level-tab-stop:.5in; mso-level-number-position:left; text-indent:-.25in; mso-ansi-font-size:10.0pt; font-family:Symbol;} @list l54 {mso-list-id:1823111458; mso-list-template-ids:-871985190;} @list l54:level1 {mso-level-number-format:bullet; mso-level-text:; mso-level-tab-stop:.5in; mso-level-number-position:left; text-indent:-.25in; mso-ansi-font-size:10.0pt; font-family:Symbol;} @list l55 {mso-list-id:1842115651; mso-list-template-ids:-318627084;} @list l55:level1 {mso-level-number-format:bullet; mso-level-text:; mso-level-tab-stop:.5in; mso-level-number-position:left; text-indent:-.25in; mso-ansi-font-size:10.0pt; font-family:Symbol;} @list l56 {mso-list-id:1874534460; mso-list-template-ids:-1096780754;} @list l56:level1 {mso-level-number-format:bullet; mso-level-text:; mso-level-tab-stop:.5in; mso-level-number-position:left; text-indent:-.25in; mso-ansi-font-size:10.0pt; font-family:Symbol;} @list l57 {mso-list-id:1876968026; mso-list-template-ids:1346289882;} @list l57:level1 {mso-level-number-format:bullet; mso-level-text:; mso-level-tab-stop:.5in; mso-level-number-position:left; text-indent:-.25in; mso-ansi-font-size:10.0pt; font-family:Symbol;} @list l58 {mso-list-id:1898275959; mso-list-template-ids:40561422;} @list l58:level1 {mso-level-number-format:bullet; mso-level-text:; mso-level-tab-stop:.5in; mso-level-number-position:left; text-indent:-.25in; mso-ansi-font-size:10.0pt; font-family:Symbol;} @list l58:level2 {mso-level-number-format:bullet; mso-level-text:o; mso-level-tab-stop:1.0in; mso-level-number-position:left; text-indent:-.25in; mso-ansi-font-size:10.0pt; font-family:"Courier New"; mso-bidi-font-family:"Times New Roman";} @list l59 {mso-list-id:1989283783; mso-list-template-ids:-554297444;} @list l59:level1 {mso-level-number-format:bullet; mso-level-text:; mso-level-tab-stop:.5in; mso-level-number-position:left; text-indent:-.25in; mso-ansi-font-size:10.0pt; font-family:Symbol;} @list l60 {mso-list-id:2009209635; mso-list-template-ids:-1979433944;} @list l60:level1 {mso-level-number-format:bullet; mso-level-text:; mso-level-tab-stop:.5in; mso-level-number-position:left; text-indent:-.25in; mso-ansi-font-size:10.0pt; font-family:Symbol;} @list l61 {mso-list-id:2013726812; mso-list-template-ids:-1303980410;} @list l61:level1 {mso-level-number-format:bullet; mso-level-text:; mso-level-tab-stop:.5in; mso-level-number-position:left; text-indent:-.25in; mso-ansi-font-size:10.0pt; font-family:Symbol;} @list l62 {mso-list-id:2046254339; mso-list-template-ids:574110002;} @list l62:level1 {mso-level-number-format:bullet; mso-level-text:; mso-level-tab-stop:.5in; mso-level-number-position:left; text-indent:-.25in; mso-ansi-font-size:10.0pt; font-family:Symbol;} @list l62:level2 {mso-level-number-format:bullet; mso-level-text:o; mso-level-tab-stop:1.0in; mso-level-number-position:left; text-indent:-.25in; mso-ansi-font-size:10.0pt; font-family:"Courier New"; mso-bidi-font-family:"Times New Roman";} @list l63 {mso-list-id:2047369767; mso-list-template-ids:-1770215526;} @list l63:level1 {mso-level-number-format:bullet; mso-level-text:; mso-level-tab-stop:.5in; mso-level-number-position:left; text-indent:-.25in; mso-ansi-font-size:10.0pt; font-family:Symbol;} @list l63:level2 {mso-level-number-format:bullet; mso-level-text:o; mso-level-tab-stop:1.0in; mso-level-number-position:left; text-indent:-.25in; mso-ansi-font-size:10.0pt; font-family:"Courier New"; mso-bidi-font-family:"Times New Roman";} @list l64 {mso-list-id:2071030249; mso-list-template-ids:-800678728;} @list l64:level1 {mso-level-number-format:image; list-style-image:url("PicExportError"); mso-level-text:; mso-level-tab-stop:.5in; mso-level-number-position:left; text-indent:-.25in; mso-ansi-font-size:10.0pt; font-family:Symbol;} @list l65 {mso-list-id:2080326436; mso-list-template-ids:177252396;} @list l65:level1 {mso-level-number-format:bullet; mso-level-text:; mso-level-tab-stop:.5in; mso-level-number-position:left; text-indent:-.25in; mso-ansi-font-size:10.0pt; font-family:Symbol;} @list l65:level2 {mso-level-number-format:bullet; mso-level-text:o; mso-level-tab-stop:1.0in; mso-level-number-position:left; text-indent:-.25in; mso-ansi-font-size:10.0pt; font-family:"Courier New"; mso-bidi-font-family:"Times New Roman";} @list l66 {mso-list-id:2097164342; mso-list-template-ids:-1544264220;} @list l66:level1 {mso-level-number-format:bullet; mso-level-text:; mso-level-tab-stop:.5in; mso-level-number-position:left; text-indent:-.25in; mso-ansi-font-size:10.0pt; font-family:Symbol;} @list l66:level2 {mso-level-number-format:bullet; mso-level-text:o; mso-level-tab-stop:1.0in; mso-level-number-position:left; text-indent:-.25in; mso-ansi-font-size:10.0pt; font-family:"Courier New"; mso-bidi-font-family:"Times New Roman";} @list l67 {mso-list-id:2119369062; mso-list-template-ids:-1049741452;} @list l67:level1 {mso-level-number-format:bullet; mso-level-text:; mso-level-tab-stop:.5in; mso-level-number-position:left; text-indent:-.25in; mso-ansi-font-size:10.0pt; font-family:Symbol;} ol {margin-bottom:0in;} ul {margin-bottom:0in;} --> </style><!--[if gte mso 10]> <style> /* Style Definitions */ table.MsoNormalTable {mso-style-name:"Table Normal"; mso-tstyle-rowband-size:0; mso-tstyle-colband-size:0; mso-style-noshow:yes; mso-style-parent:""; mso-padding-alt:0in 5.4pt 0in 5.4pt; mso-para-margin:0in; mso-para-margin-bottom:.0001pt; mso-pagination:widow-orphan; font-size:10.0pt; font-family:"Times New Roman"; mso-ansi-language:#0400; mso-fareast-language:#0400; mso-bidi-language:#0400;} </style> <![endif]--><!--[if gte mso 9]><xml> <o:shapedefaults ext="edit" spidmax="1028"> </xml><![endif]--><!--[if gte mso 9]><xml> <o:shapelayout ext="edit"> <o:idmap ext="edit" data="1"> </o:shapelayout></xml><![endif]--> <p class="MsoNormal"><b style=""><span style="font-size: 16pt; color: black;"><o:p> </o:p></span></b></p> <p class="MsoNormal"><span style="font-size:180%;"><b style=""><span style="font-size: 16pt; color: black;">Blog-Post -11-</span></b></span><b style=""><span style="font-size: 16pt; color: rgb(21, 34, 43);"><span style="font-size:180%;">Packet Radio by AGW Packet Engine</span><o:p></o:p></span></b></p> <p class="MsoNormal"><span style="color: rgb(21, 34, 43);">Finding and installing SV2AGW’s <span style=""> </span>Packet Engine Software, AGWTerminal, a very simple terminal program.<span style=""> </span>All the software listed here is for Windows – there are other versions of the software for most other operating systems.<span style=""> </span>Just go to the original links provided in the tutorial below.<span style=""> </span>For the windows versions, just go to the WA-DIGITAL yahoo group and check in the files section:<o:p></o:p></span></p> <p class="MsoNormal"><span style="color: rgb(21, 34, 43);"><o:p> </o:p></span></p> <p class="MsoNormal"><span style="color: rgb(21, 34, 43);"><a href="http://groups.yahoo.com/group/wa-digital/files/">http://groups.yahoo.com/group/wa-digital/files/</a> <span style=""> </span><o:p></o:p></span></p> <p class="MsoNormal"><span style="color: rgb(21, 34, 43);">and look in the Packet Radio Folder Using AGW<o:p></o:p></span></p> <p class="MsoNormal"><span style="color: rgb(21, 34, 43);"><o:p> </o:p></span></p> <p class="MsoNormal"><span style="color: rgb(21, 34, 43);">Or go to the original site by SV2AGW<o:p></o:p></span></p> <p class="MsoNormal"><span style="color: rgb(21, 34, 43);"><a href="http://www.sv2agw.com/downloads/default.htm">http://www.sv2agw.com/downloads/default.htm</a> <o:p></o:p></span></p> <p class="MsoNormal"><span style="color: rgb(21, 34, 43);"><o:p> </o:p></span></p> <p class="MsoNormal"><span style="color: rgb(21, 34, 43);">Instructions below were originally from:<span style=""> </span><a href="http://www.kc2rlm.info/soundcardpacket/">http://www.kc2rlm.info/soundcardpacket/</a><o:p></o:p></span></p> <p class="MsoNormal"><span style="color: rgb(21, 34, 43);"><o:p> </o:p></span></p> <p class="MsoNormal"><span style="color: rgb(21, 34, 43);"><o:p> </o:p></span></p> <p class="MsoNormal"><span style="color: black;">A huge THANKS! To Ralph Milnes, KC2RLM for the following information:<o:p></o:p></span></p> <p class="MsoNormal"><span style="color: black;"><o:p> </o:p></span></p> <h2><span style="color: rgb(204, 51, 0);">Download and Install AGWPE</span></h2> <h4><span style="color: rgb(204, 51, 0);">1<a name="download">. Download the AGWPE Program</a></span><span style=""></span></h4> <ul type="disc"><li class="MsoNormal" style=""><b><span style="font-size: 10pt;">The AGWPE web site is <a href="http://www.sv2agw.com/ham/agwpe.htm">http://www.sv2agw.com/ham/agwpe.htm</a> </span></b></li><li class="MsoNormal" style=""><b><span style="font-size: 10pt;">You can <span style="color: rgb(0, 153, 153);">download the AGWPE program</span> from the <a href="http://www.kc2rlm.info/soundcardpacket/AGWPrograms.htm">AGW Programs</a> page on this site. It has download links to get the file from SV2AGW's website or directly from this website.
<br />
<br /> The AGWPE setup file comes in "zip" format. If you need an unzip program, <a href="http://www.winzip.com/ddchomea.htm">visit the WinZip site</a> for the latest copy of WinZip.
<br /> </span></b></li></ul> <h4><span style="color: rgb(204, 51, 0);">2<a name="Install_AGWPE">. Install AGWPE</a></span><span style=""></span></h4> <div align="center"> <table class="MsoNormalTable" style="border: 2.25pt outset ; background: rgb(255, 255, 204) none repeat scroll 0% 0%; width: 90%; -moz-background-clip: -moz-initial; -moz-background-origin: -moz-initial; -moz-background-inline-policy: -moz-initial;" border="1" cellpadding="0" cellspacing="1" width="90%"> <tbody><tr style=""> <td style="padding: 3pt;"> <h4><span style="font-size: 10pt; color: black;">Note: </span><span style="font-size: 10pt; color: rgb(204, 51, 0);">To remove a prior version of AGWPE</span><span style="font-size: 10pt; color: black;"> from your system, simply delete the files in the AGWPE folder or, even simper, delete the folder. You can not use the Windows' "</span><span style="font-size: 10pt; color: rgb(0, 153, 153);">Add or Remove Programs</span><span style="font-size: 10pt; color: black;">" routine in the Control Panel, since AGWPE is not "installed" in Windows like most other programs.
<br />
<br /> Another option is to rename the older version's folder rather than remove it.</span></h4> </td> </tr> </tbody></table> </div> <ul type="disc"><li class="MsoNormal" style=""><b><span style="font-size: 10pt;"> 1. AGWPE does not us the typical Windows "Add or Remove Programs" install routine from the Control Panel (<span style="color: rgb(0, 153, 153);">Start> Settings> Control Panel> Add or Remove Programs </span><span style="color: blue;">). </span>
<br />
<br /> Instead, simply extract the zipped files into a new folder. I always create a new folder for each version of AGWPE that I download, since each version of the program uses the same file names and I don't want to mix files from different versions.</span></b></li></ul> <div align="center"> <table class="MsoNormalTable" style="border: 2.25pt outset ; background: rgb(255, 255, 204) none repeat scroll 0% 0%; width: 80%; -moz-background-clip: -moz-initial; -moz-background-origin: -moz-initial; -moz-background-inline-policy: -moz-initial;" border="1" cellpadding="0" width="80%"> <tbody><tr style=""> <td style="padding: 3.75pt;"> <p class="MsoNormal"><b><span style="font-size: 10pt;">Language files: You do not need to unzip the alternate language files into the AGWPE folder if you plan to use the default language of English. (For more information on alternate language files see the <a href="http://www.kc2rlm.info/soundcardpacket/6tips.htm">Tips and Tricks page</a>.)</span></b></p> </td> </tr> </tbody></table> </div> <ul type="disc"><li class="MsoNormal" style=""><b><span style="font-size: 10pt;">2. Note that the main AGWPE program is called <span style="color: blue;">AGW Packet Engine.exe
<br /> </span>You may want to create a Windows shortcut to this file on your desktop. You can also add a link to <span style="color: blue;">AGW Packet Engine.exe</span> on your Windows <span style="color: rgb(0, 153, 153);">Start Menu</span> by dragging and dropping a copy of the AGWPE shortcut icon onto the Windows <span style="color: blue;">Start</span> button on the Task Bar at the bottom of your screen.</span></b></li></ul> <table class="MsoNormalTable" style="border: 2.25pt outset ; background: rgb(255, 255, 204) none repeat scroll 0% 0%; width: 80%; -moz-background-clip: -moz-initial; -moz-background-origin: -moz-initial; -moz-background-inline-policy: -moz-initial;" border="1" cellpadding="0" width="80%"> <tbody><tr style=""> <td style="padding: 3.75pt;"> <h5>Do I need to install special drivers for using the parallel port to control PTTl?</h5> <p><b><span style="font-size: 10pt;">Not any more. Earlier versions of AGWPE <span style="color: red;">did require </span>special parallel drivers, but they are <span style="color: red;">no longer necessary</span>. For the most recent versions of AGWPE, e.g. since version 2001.38, it is <span style="color: red;">not necessary</span> to download or use the drivers.zip file from the AGWPE site <span style="color: red;">despite</span> what the AGWPE program <span style="color: rgb(0, 153, 153);">Help</span> file or the <span style="color: rgb(0, 153, 153);">AGWPE web site</span> may say.</span></b></p> </td> </tr> </tbody></table> <p class="MsoNormal"><o:p> </o:p></p> <p class="MsoNormal"><o:p> </o:p></p> <p class="MsoNormal"><o:p> </o:p></p> <p class="MsoNormal"><o:p> </o:p></p> <h2><span style="color: rgb(204, 51, 0);">Basic AGWPE Program Setup</span></h2> <p><b><span style="color: blue;">One Radio to One Sound Card</span></b><span style="color: blue;">
<br />
<br /></span><b><span style="font-size: 10pt;"><a href="http://www.kc2rlm.info/soundcardpacket/2agwbasic.htm#Navigating">Navigating in AGWPE</a>
<br /><a href="http://www.kc2rlm.info/soundcardpacket/2agwbasic.htm#portsettings">Configuring the Radio Port Properties</a>
<br /><a href="http://www.kc2rlm.info/soundcardpacket/2agwbasic.htm#soundcardproperties">Configuring the Sound Card</a></span></b></p> <p><b><span style="font-size: 10pt;">AGWPE uses the concept of <span style="color: rgb(204, 51, 0);">Radio Ports</span> to define how it will interface with a radio. An AGWPE radio port is created for each TNC, radio modem or sound card channel that AGWPE will manage. This page will show you how to setup an AGWPE <span style="color: rgb(204, 51, 0);">sound card </span>radio port in just a few minutes. Note that to complete your configuration, you will need to decide which RS-232 port (COM or LPT) you plan to use for PTT control, in other words, where your PTT cable will connect to the computer. Usually this is an unused COM port. See <a href="http://www.kc2rlm.info/soundcardpacket/1cableptt.htm">PTT Cable</a> for more information.</span></b></p> <p><b><span style="font-size: 10pt;">Before starting AGWPE, always close:</span></b></p> <ul type="disc"><li class="MsoNormal" style=""><b><span style="font-size: 10pt;">any programs that might be using the <i>serial or parallel port</i> you plan to use for PTT control</span></b></li><li class="MsoNormal" style=""><b><span style="font-size: 10pt;">any programs that might be accessing the <i>sound card</i></span></b></li></ul> <h4>a. <a name="Navigating">Navigating</a> in AGWPE</h4> <p><b><span style="font-size: 10pt;">When you start the <span style="color: blue;">AGW Packet Engine.exe</span> program for the first time, you will be greeted with a <span style="color: rgb(255, 153, 0);">Packet Engine</span> banner all in gold and a Software License Agreement which you must accept. The banner will disappear in a few seconds or you can click on it once to speed things up. At this point, you will discover that AGWPE does not put an open Window on your desktop, nor will there be a button on the bottom Task Bar of your screen. Instead, all you will find is the AGWPE tower icon <!--[if gte vml 1]><v:shapetype id="_x0000_t75" coordsize="21600,21600" spt="75" preferrelative="t" path="m@4@5l@4@11@9@11@9@5xe" filled="f" stroked="f"> <v:stroke joinstyle="miter"> <v:formulas> <v:f eqn="if lineDrawn pixelLineWidth 0"> <v:f eqn="sum @0 1 0"> <v:f eqn="sum 0 0 @1"> <v:f eqn="prod @2 1 2"> <v:f eqn="prod @3 21600 pixelWidth"> <v:f eqn="prod @3 21600 pixelHeight"> <v:f eqn="sum @0 0 1"> <v:f eqn="prod @6 1 2"> <v:f eqn="prod @7 21600 pixelWidth"> <v:f eqn="sum @8 21600 0"> <v:f eqn="prod @7 21600 pixelHeight"> <v:f eqn="sum @10 21600 0"> </v:formulas> <v:path extrusionok="f" gradientshapeok="t" connecttype="rect"> <o:lock ext="edit" aspectratio="t"> </v:shapetype><v:shape id="_x0000_i1027" type="#_x0000_t75" alt="AGWPE Tower Icon" style="'width:24pt;height:24pt'"> <v:imagedata src="file:///C:\DOCUME~1\C11AE~1.BLA\LOCALS~1\Temp\msohtml1\01\clip_image004.gif" href="http://www.kc2rlm.info/soundcardpacket/AGWImages/AGWPE%20ICON%20Large.gif"> </v:shape><![endif]--><!--[if !vml]--><img src="file:///C:/DOCUME%7E1/C11AE%7E1.BLA/LOCALS%7E1/Temp/msohtml1/01/clip_image004.gif" alt="AGWPE Tower Icon" shapes="_x0000_i1027" border="0" height="32" width="32" /><!--[endif]-->on your Windows System Tray at the bottom right of your screen. This icon is your only access to AGWPE when it is running! To help you find it, a yellow pop-up 'balloon' message points to the icon when AGWPE starts.</span></b></p> <p><b><span style="font-size: 10pt;">To change any of AGWPE's configurations, left or right click on the <span style="color: rgb(0, 153, 153);">AGWPE</span> icon <!--[if gte vml 1]><v:shape id="_x0000_i1028" type="#_x0000_t75" alt="AGWPE Tower Icon" style="'width:24pt;"> <v:imagedata src="file:///C:\DOCUME~1\C11AE~1.BLA\LOCALS~1\Temp\msohtml1\01\clip_image004.gif" href="http://www.kc2rlm.info/soundcardpacket/AGWImages/AGWPE%20ICON%20Large.gif"> </v:shape><![endif]--><!--[if !vml]--><img src="file:///C:/DOCUME%7E1/C11AE%7E1.BLA/LOCALS%7E1/Temp/msohtml1/01/clip_image004.gif" alt="AGWPE Tower Icon" shapes="_x0000_i1028" border="0" height="32" width="32" /><!--[endif]-->to bring up AGWPE's pop-up menu:</span></b></p> <p><!--[if gte vml 1]><v:shape id="_x0000_s1026" type="#_x0000_t75" alt="" style="'position:absolute;margin-left:0;margin-top:0;width:122.25pt;height:162.75pt;" allowoverlap="f"> <v:imagedata src="file:///C:\DOCUME~1\C11AE~1.BLA\LOCALS~1\Temp\msohtml1\01\clip_image005.gif" title="AGWPE%20Menu"> <w:wrap type="square"> </v:shape><![endif]--><!--[if !vml]--><img src="file:///C:/DOCUME%7E1/C11AE%7E1.BLA/LOCALS%7E1/Temp/msohtml1/01/clip_image005.gif" shapes="_x0000_s1026" align="left" height="217" width="163" /><!--[endif]--> </p> <p> </p> <p><b><span style="font-size: 10pt;">Note: The Sound Card Tuning Aid option on the menu
<br />will be grayed out until you create and configure a "radio port"
<br />as described below.</span></b></p> <h5> </h5> <h5> </h5> <h4><span style="font-size: 10pt;">
<br /> </span></h4> <h4><span style="color: rgb(0, 51, 204);">b. <a name="createport">Create and Configure an </a><st1:place st="on"><st1:placename st="on"><span style="">AGWPE</span></st1:placename><span style=""> <st1:placename st="on">Radio</st1:placename> <st1:placetype st="on">Port</st1:placetype></span></st1:place><a name="portsettings"> </a></span><span style=""></span></h4> <p><b><span style="font-size: 10pt;">The first step in working with AGWPE is to create and configure a radio port for a sound card channel and its associated radio.<span style="color: black;"> From the AGWPE menu, select</span> <span style="color: blue;">Properties</span>.<span style="color: black;"> A blank </span><span style="color: rgb(0, 153, 153);">RadioPort Selection</span> <span style="color: black;">window will open. Press the </span><st1:place st="on"><st1:placename st="on"><span style="color: blue;">New</span></st1:placename><span style="color: blue;"> <st1:placetype st="on">Port</st1:placetype></span></st1:place> <span style="color: black;">button on the right. A message window will appear: </span><span style="color: rgb(204, 51, 0);">A New TncPort File Has Been Created</span><span style="color: black;">. Click </span><span style="color: blue;">OK</span> to close the message and move on.
<br />
<br /><span style="color: black;">The </span><span style="color: rgb(0, 153, 153);">Properties for Port`1</span><span style="color: black;"> window should now appear. Remember that AGWPE also can manage TNCs and radio modems, so some of the fields on this screen will not pertain to sound cards. The field outlined in red will be the key fields for a sound card radio port. Follow the step below in filling out the fields:</span></span></b></p> <p> <!--[if gte vml 1]><v:shape id="_x0000_i1029" type="#_x0000_t75" alt="" style="'width:357pt;height:333.75pt'"> <v:imagedata src="file:///C:\DOCUME~1\C11AE~1.BLA\LOCALS~1\Temp\msohtml1\01\clip_image006.gif" href="http://www.kc2rlm.info/soundcardpacket/AGWImages/2PortProperty.gif"> </v:shape><![endif]--><!--[if !vml]--><img src="file:///C:/DOCUME%7E1/C11AE%7E1.BLA/LOCALS%7E1/Temp/msohtml1/01/clip_image006.gif" shapes="_x0000_i1029" border="0" height="445" width="476" /><!--[endif]--></p> <p><b><span style="font-size: 10pt;">1. Make the following selections first on this screen (i.e. <span style="color: rgb(0, 153, 153);">TNC Setup</span> tab):</span></b></p> <table class="MsoNormalTable" style="border: 2.25pt outset ; width: 295.5pt;" border="1" cellpadding="0" cellspacing="0" width="394"> <tbody><tr style=""> <td style="padding: 3.75pt; width: 107.25pt;" width="143"> <p class="MsoNormal"><b><span style="font-size: 10pt; color: rgb(0, 153, 153);"> <st1:place st="on"><st1:placename st="on">Select</st1:placename> <st1:placetype st="on">Port</st1:placetype></st1:place> </span></b></p> </td> <td style="padding: 3.75pt; width: 185.25pt;" width="247"> <p class="MsoNormal"><b><span style="font-size: 10pt;">enter the port where you will attach your <a href="http://www.kc2rlm.info/soundcardpacket/1cablestart.htm">PTT cable</a>, <span style="color: rgb(204, 51, 0);">e.g. COM1 or LPT1;</span> see notes below *</span></b></p> </td> </tr> <tr style=""> <td style="padding: 3.75pt; width: 107.25pt;" width="143"> <p class="MsoNormal"><b><span style="font-size: 10pt; color: rgb(0, 153, 153);">TNC Radioport:
<br /> Port Description </span></b></p> </td> <td style="padding: 3.75pt; width: 185.25pt;" width="247"> <p class="MsoNormal"><b><span style="font-size: 10pt;">you can overwrite the current description for Port 1 and enter a description of your own choice, e.g. <span style="color: blue;">Icom</span><span style="color: rgb(204, 51, 0);"> </span><span style="color: blue;">1200 Packet</span></span></b></p> </td> </tr> </tbody></table> <p>* <b><span style="font-size: 10pt; color: blue;">Notes about Port selections (COM & LPT)</span></b><b><span style="font-size: 10pt;">:</span></b></p> <ul type="disc"><li class="MsoNormal" style=""><b><span style="font-size: 10pt; color: rgb(204, 51, 0);">To select </span></b><b><span style="font-size: 10pt; font-family: Arial; color: rgb(204, 51, 0);">a parallel port</span></b><b><span style="font-size: 10pt; font-family: Arial;"> scroll to the bottom of the port list </span></b></li><li class="MsoNormal" style=""><b><span style="font-size: 10pt; font-family: Arial; color: rgb(204, 51, 0);">If you are setting up a receive-only installation</span></b><b><span style="font-size: 10pt; font-family: Arial;"> or using a SignaLink interface or other audio-controlled PTT interface and don't want to tie up a real port for a PTT line you won't be using, the AGW software <span style="color: rgb(204, 51, 0);">will accept non-existent parallel port</span> assignments, but not non-existent serial ports.</span></b></li></ul> <p><b><span style="font-size: 10pt;">2. You can leave all other selections at their defaults, including <span style="color: rgb(0, 153, 153);">Serial Port/ Modem Baud Rate</span>, which is not used for sound cards.</span></b></p> <p><b><span style="font-size: 10pt;">3. Now go to the <span style="color: rgb(0, 153, 153);">TNC Type</span> field in the top middle of the screen and use the pull down list to select <span style="color: rgb(0, 51, 204);">"Sound Card</span>".
<br /> </span></b></p> <p><a name="soundcardproperties"><b><span style="color: rgb(0, 51, 204);">c. Settings on the Sound Card Setup screen:</span></b></a><b><span style="color: rgb(0, 51, 204);"> </span></b><b><span style="font-size: 10pt;">
<br />
<br />When you select "<span style="color: blue;">Sound Card</span>" for your <span style="color: rgb(0, 153, 153);">TNC Type</span> (or if press the <span style="color: blue;">Options</span> button in the middle of the <span style="color: rgb(0, 153, 153);">TNC setup</span> window, underneath <span style="color: blue;">TNC subtype</span>), the program will bring up the <span style="color: rgb(0, 153, 153);">SoundCard Modem/TNC Setup</span> window which looks like this:</span></b></p> <p> <!--[if gte vml 1]><v:shape id="_x0000_i1030" type="#_x0000_t75" alt="" style="'width:337.5pt;height:351pt'"> <v:imagedata src="file:///C:\DOCUME~1\C11AE~1.BLA\LOCALS~1\Temp\msohtml1\01\clip_image007.gif" href="http://www.kc2rlm.info/soundcardpacket/AGWImages/2scsetup.gif"> </v:shape><![endif]--><!--[if !vml]--><img src="file:///C:/DOCUME%7E1/C11AE%7E1.BLA/LOCALS%7E1/Temp/msohtml1/01/clip_image007.gif" shapes="_x0000_i1030" border="0" height="468" width="450" /><!--[endif]--></p> <p><b><span style="font-size: 10pt;">1. <span style="color: rgb(0, 153, 153);">Baud Rates: </span>Note that your sound card is capable of supporting two radio ports using its left and right audio channels. If you are only using one radio, it will be Port 1 on the left channel. Set the left channel baud rate for the rate you plan to use, i.e. <span style="color: blue;">300</span><span style="color: rgb(204, 51, 0);"> </span>baud for HF SSB work; or <span style="color: blue;">1200, 2400, 4800, </span>or<span style="color: blue;"> 9600</span> for VHF/UHF work.
<br />
<br />Assuming that you will <span style="color: rgb(204, 51, 0);">not</span> be using the right channel for a second radio connection, set the right channel rate for a baud rate <span style="color: rgb(204, 51, 0);">different from</span> the one you have chose for the left channel. This may prevent the possibility of future problems. (If you will be connecting to 2 radios, see <a href="http://www.kc2rlm.info/soundcardpacket/2agw2radios.htm">Configuring AGWPE for 2 Radios</a>. )</span></b></p> <p><b><span style="font-size: 10pt;">2.<span style="color: rgb(0, 153, 153);"> Sound Card Selection:</span> Use the pull down menu to select the sound card device you will be using with AGWPE. You may see other choices, such as a telephone modem (don't use) or another another card if you have two.</span></b></p> <p><b><span style="font-size: 10pt;">3.<span style="color: rgb(0, 153, 153);"> </span>For now leave the other fields at their defaults:</span></b></p> <ul type="disc"><li class="MsoNormal" style=""><b><span style="font-size: 10pt; color: rgb(0, 153, 153);">Full Duplex Driver:</span></b><b><span style="font-size: 10pt;"> The <span style="color: blue;">Full Duplex Driver </span>box should be checked. Most recent sound cards are full-duplex capable. If you later encounter transmitting problems, you may need to un-check the <span style="color: blue;">Full Duplex Driver </span>box. This is likely to apply only to older sound cards; see <a href="http://www.kc2rlm.info/soundcardpacket/5probconnect.htm#SlowExchanges">Problems with Connections </a> for more about this.</span></b></li><li class="MsoNormal" style=""><b><span style="font-size: 10pt; color: rgb(0, 153, 153);">Sound Card Clock:</span></b><b><span style="font-size: 10pt;"> This setting is used if you have problems receiving distant stations; see the <a href="http://www.kc2rlm.info/soundcardpacket/5probrx.htm#RXbaddriver">Problems with Receiving</a> page for more information, but for now leave the setting at 4, the default.</span></b></li></ul> <p><b><span style="font-size: 10pt;">Now press the <span style="color: blue;">OK</span> button to return to the <span style="color: rgb(0, 153, 153);">Properties for Port1</span> window <span style="color: rgb(204, 51, 0);">but do not close it yet</span>. </span></b></p> <p><b><span style="font-size: 10pt;">4. Note that, by default, AGWPE has created two sound card radio ports. To avoid future operating problems, <span style="color: rgb(204, 51, 0);">change</span> the setting from <st1:place st="on"><st1:placename st="on"><span style="color: blue;">Dual</span></st1:placename><span style="color: blue;"> <st1:placetype st="on">Port</st1:placetype></span></st1:place> to <span style="color: blue;">SinglePort </span> in the <span style="color: blue;">TNC Control Commands </span>section of the <span style="color: rgb(0, 153, 153);">Properties for Port1</span> window. (Doesn't apply if you really will be <a href="http://www.kc2rlm.info/soundcardpacket/2agw2radios.htm">connecting to 2 Radio)</a>.</span></b></p> <p><b><span style="font-size: 10pt;">For a simple, first time installation, all other selections can remain "as is" (use the default selections), including those in the <span style="color: rgb(0, 153, 153);">Tnc Commands</span> tab window in the <span style="color: rgb(0, 153, 153);">Properties for Port1</span> window and any other selections on the AGWPE menu.
<br /> </span></b></p> <p><b><span style="font-size: 10pt;">5. Now press the <span style="color: blue;">OK</span> button at the bottom of the <span style="color: rgb(0, 153, 153);">Properties for Port1</span> window. You should get a popup message telling you to restart the program, so click on the <span style="color: rgb(0, 153, 153);">Packet Engine</span> icon <!--[if gte vml 1]><v:shape id="_x0000_i1031" type="#_x0000_t75" alt="AGWPE Tower Icon" style="'width:20.25pt;"> <v:imagedata src="file:///C:\DOCUME~1\C11AE~1.BLA\LOCALS~1\Temp\msohtml1\01\clip_image004.gif" href="http://www.kc2rlm.info/soundcardpacket/AGWImages/AGWPE%20ICON%20Large.gif"> </v:shape><![endif]--><!--[if !vml]--><img src="file:///C:/DOCUME%7E1/C11AE%7E1.BLA/LOCALS%7E1/Temp/msohtml1/01/clip_image008.jpg" alt="AGWPE Tower Icon" shapes="_x0000_i1031" border="0" height="24" width="27" /><!--[endif]-->once again and select '<span style="color: blue;">Exit</span>'. Now restart AGWPE. The <span style="color: rgb(0, 153, 153);">Packet Engine</span> icon <!--[if gte vml 1]><v:shape id="_x0000_i1032" type="#_x0000_t75" alt="AGWPE Tower Icon" style="'width:20.25pt;"> <v:imagedata src="file:///C:\DOCUME~1\C11AE~1.BLA\LOCALS~1\Temp\msohtml1\01\clip_image004.gif" href="http://www.kc2rlm.info/soundcardpacket/AGWImages/AGWPE%20ICON%20Large.gif"> </v:shape><![endif]--><!--[if !vml]--><img src="file:///C:/DOCUME%7E1/C11AE%7E1.BLA/LOCALS%7E1/Temp/msohtml1/01/clip_image008.jpg" alt="AGWPE Tower Icon" shapes="_x0000_i1032" border="0" height="24" width="27" /><!--[endif]-->should once again appear, but in addition you should now see a <span style="color: rgb(0, 153, 153);">TNC icon</span> <!--[if gte vml 1]><v:shape id="_x0000_i1033" type="#_x0000_t75" alt="AGWPE Modem Icon" style="'width:24pt;height:11.25pt'"> <v:imagedata src="file:///C:\DOCUME~1\C11AE~1.BLA\LOCALS~1\Temp\msohtml1\01\clip_image009.gif" href="http://www.kc2rlm.info/soundcardpacket/AGWImages/TNCnone.gif"> </v:shape><![endif]--><!--[if !vml]--><img src="file:///C:/DOCUME%7E1/C11AE%7E1.BLA/LOCALS%7E1/Temp/msohtml1/01/clip_image009.gif" alt="AGWPE Modem Icon" shapes="_x0000_i1033" border="0" height="15" width="32" /><!--[endif]-->next to it. This new icon represents your new sound card <st1:place st="on"><st1:placename st="on">Radio</st1:placename> <st1:placetype st="on">Port.</st1:placetype></st1:place>
<br /> </span></b></p> <h4>d. Editing a Port's Properties</h4> <p><b><span style="font-size: 10pt;">If you want to change a setting in the <st1:place st="on"><st1:placename st="on">Radio</st1:placename> <st1:placetype st="on">Port</st1:placetype></st1:place>'s configuration, click on the AGWPE icon to call up the menu, select <span style="color: rgb(0, 153, 153);">Properties</span>, and then click on the radio port you want to change. Then click <span style="color: blue;">OK </span><span style="color: black;">and edit the fields in the </span><span style="color: rgb(0, 153, 153);">Properties for Portx</span><span style="color: black;"> window</span>. </span></b></p> <h4><span style="color: rgb(0, 51, 204);">
<br /></span>e. Problems?</h4> <ul type="disc"><li class="MsoNormal" style=""><b><span style="font-size: 10pt;">Any time you have trouble starting or configuring AGWPE, it is often best to close AGWPE and delete all <span style="color: blue;">port*.ini</span> files and the<span style="color: blue;"> agwpe.ini</span> file in your AGWPE directory/folder. Then restart and re-configure AGWPE from the very beginning.
<br /> </span></b></li><li class="MsoNormal" style=""><b><span style="font-size: 10pt;">If you don't see this <span style="color: rgb(0, 153, 153);">TNC icon </span><!--[if gte vml 1]><v:shape id="_x0000_i1034" type="#_x0000_t75" alt="AGWPE Modem Icon" style="'width:24pt;"> <v:imagedata src="file:///C:\DOCUME~1\C11AE~1.BLA\LOCALS~1\Temp\msohtml1\01\clip_image009.gif" href="http://www.kc2rlm.info/soundcardpacket/AGWImages/TNCnone.gif"> </v:shape><![endif]--><!--[if !vml]--><img src="file:///C:/DOCUME%7E1/C11AE%7E1.BLA/LOCALS%7E1/Temp/msohtml1/01/clip_image009.gif" alt="AGWPE Modem Icon" shapes="_x0000_i1034" border="0" height="15" width="32" /><!--[endif]-->, you probably have a conflict with another program or device:</span></b></li><ul type="circle"><li class="MsoNormal" style=""><b><span style="font-size: 10pt;">Make sure that the COM or LPT port you have select in AGWPE is not already dedicated to another device, for example, an internal modem or printer) or has been "captured" by another program (for example, your Palm Pilot's "Hot Sync Manager". You'll have to resolve any conflicts by either closing the other program, disabling the device, or selecting another port for AGWPE's PTT control.</span></b></li><li class="MsoNormal" style=""><b><span style="font-size: 10pt;">Make sure that no other program is running and using the the sound card. </span></b></li></ul></ul> <p><b><span style="font-size: 10pt;">For further help in resolving <a href="http://www.kc2rlm.info/soundcardpacket/5probprog.htm#portconflict">port conflicts</a>, go to the <a href="http://www.kc2rlm.info/soundcardpacket/5probprog.htm#portconflict">Problems with Program Behavior</a> page on this site.<o:p></o:p></span></b></p> <p><b><span style="font-size: 10pt;"><o:p> </o:p></span></b></p> <p><b><span style="font-size: 16pt;">BEGIN SPECIAL SIGNALINK SETUP SECTION +++++++++++++++++++++++++++++++++</span></b><b style=""><span style="font-size: 16pt;"><o:p></o:p></span></b></p> <h2><span style="font-size: 13.5pt; color: rgb(204, 51, 0); font-weight: normal;">AGWPE and the SignaLink USB</span><span style="font-family: Arial; color: rgb(51, 0, 153);"><o:p></o:p></span></h2> <p><b><span style="font-size: 10pt; font-family: Arial; color: black;">The Tigertronics SignaLink USB interface (<a href="http://www.tigertronics.com/slusbmain.htm">http://www.tigertronics.com/slusbmain.htm</a>) has many interesting features of value to AGWPE users:</span></b><span style="font-family: Arial; color: black;"><o:p></o:p></span></p> <p class="MsoNormal" style="margin-left: 0.5in; text-indent: -0.25in;"><!--[if !supportLists]--><span style="font-size: 10pt; font-family: Symbol; color: black;"><span style=""><img src="file:///C:/DOCUME%7E1/C11AE%7E1.BLA/LOCALS%7E1/Temp/msohtml1/01/clip_image001.gif" alt="*" height="13" width="13" /><span style="font-family: "Times New Roman"; font-style: normal; font-variant: normal; font-weight: normal; font-size: 7pt; line-height: normal; font-size-adjust: none; font-stretch: normal;"> </span></span></span><!--[endif]--><b><span style="font-size: 10pt; font-family: Arial; color: black;"> Includes a built-in "sound card" chip so AGWPE doesn't need to use your computer's sound card</span></b><span style="font-family: Arial; color: black;"> <o:p></o:p></span></p> <p class="MsoNormal" style="margin-left: 0.5in; text-indent: -0.25in;"><!--[if !supportLists]--><span style="font-size: 10pt; font-family: Symbol; color: black;"><span style=""><img src="file:///C:/DOCUME%7E1/C11AE%7E1.BLA/LOCALS%7E1/Temp/msohtml1/01/clip_image001.gif" alt="*" height="13" width="13" /><span style="font-family: "Times New Roman"; font-style: normal; font-variant: normal; font-weight: normal; font-size: 7pt; line-height: normal; font-size-adjust: none; font-stretch: normal;"> </span></span></span><!--[endif]--><b><span style="font-size: 10pt; font-family: Arial; color: black;"> Uses the TX audio (VOX) to trigger your radio's PTT circuit -- doesn't need a serial or parallel port on your computer for PTT control</span></b><span style="font-family: Arial; color: black;"> <o:p></o:p></span></p> <p class="MsoNormal" style="margin-left: 0.5in; text-indent: -0.25in;"><!--[if !supportLists]--><span style="font-size: 10pt; font-family: Symbol; color: black;"><span style=""><img src="file:///C:/DOCUME%7E1/C11AE%7E1.BLA/LOCALS%7E1/Temp/msohtml1/01/clip_image001.gif" alt="*" height="13" width="13" /><span style="font-family: "Times New Roman"; font-style: normal; font-variant: normal; font-weight: normal; font-size: 7pt; line-height: normal; font-size-adjust: none; font-stretch: normal;"> </span></span></span><!--[endif]--><b><span style="font-size: 10pt; font-family: Arial; color: black;"> Only a single USB cable to the computer -- no audio cables to sound card jacks</span></b><span style="font-family: Arial; color: black;"> <o:p></o:p></span></p> <p class="MsoNormal" style="margin-left: 0.5in; text-indent: -0.25in;"><!--[if !supportLists]--><span style="font-size: 10pt; font-family: Symbol; color: black;"><span style=""><img src="file:///C:/DOCUME%7E1/C11AE%7E1.BLA/LOCALS%7E1/Temp/msohtml1/01/clip_image001.gif" alt="*" height="13" width="13" /><span style="font-family: "Times New Roman"; font-style: normal; font-variant: normal; font-weight: normal; font-size: 7pt; line-height: normal; font-size-adjust: none; font-stretch: normal;"> </span></span></span><!--[endif]--><b><span style="font-size: 10pt; font-family: Arial; color: black;"> Powered by the USB connection</span></b><span style="font-family: Arial; color: black;"> <o:p></o:p></span></p> <p><b><span style="font-family: Arial; color: rgb(51, 0, 153);">1. Configuring the SignaLink USB for AGWPE</span></b><span style="font-family: Arial; color: black;"><o:p></o:p></span></p> <p><b><span style="font-size: 10pt; font-family: Arial; color: black;">Be sure to read the SignaLink USB (SLU) documentation, especially the part about configuring the jumper wires inside the SLU to match your radio's pin-outs .</span></b><span style="font-family: Arial; color: black;"><o:p></o:p></span></p> <p><b><span style="font-size: 10pt; font-family: Arial; color: black;">To create an AGWPE radio port for the SLU, first plug in the SLU's USB cable to your computer. Your computer should recognize a new USB device. (In my XP computer, Windows "connection" tones can be heard when this happens.)</span></b><span style="font-family: Arial; color: black;"><o:p></o:p></span></p> <p><b><span style="font-size: 10pt; font-family: Arial; color: black;">Then follow the <a href="http://kc2rlm.info/soundcardpacket/2agwbasic.htm#createport">basic AGWPE setup</a> to create an AGWPE radio port </span></b><b><span style="font-size: 10pt; font-family: Arial; color: rgb(204, 51, 0);">but with these exceptions</span></b><b><span style="font-size: 10pt; font-family: Arial; color: black;">:</span></b><span style="font-family: Arial; color: black;"><o:p></o:p></span></p> <p><b><span style="font-size: 10pt; font-family: Arial; color: black;">1. In the </span></b><b><span style="font-size: 10pt; font-family: Arial; color: blue;">Properties for Port1</span></b><b><span style="font-size: 10pt; font-family: Arial; color: black;"> window, for the </span></b><b><span style="font-size: 10pt; font-family: Arial; color: rgb(0, 153, 153);">Select Port</span></b><b><span style="font-size: 10pt; font-family: Arial; color: black;"> field, select a non-existent LPT (parallel) port. Since the SLU does not require either a COM or LPT port for PTT control, there is no need for AGWPE to tie up a COM or LPT port on your computer.</span></b><span style="font-family: Arial; color: black;"><o:p></o:p></span></p> <p><b><span style="font-size: 10pt; font-family: Arial; color: black;">2. At the bottom of the </span></b><b><span style="font-size: 10pt; font-family: Arial; color: blue;">SoundCard Modem/TNC Setup</span></b><b><span style="font-size: 10pt; font-family: Arial; color: black;"> window (found by pressing the </span></b><b><span style="font-size: 10pt; font-family: Arial; color: rgb(0, 153, 153);">Options</span></b><b><span style="font-size: 10pt; font-family: Arial; color: black;"> button in the middle of the </span></b><b><span style="font-size: 10pt; font-family: Arial; color: blue;">Properties for Port1 </span></b><b><span style="font-size: 10pt; font-family: Arial; color: black;">window), you will find the </span></b><b><span style="font-size: 10pt; font-family: Arial; color: rgb(0, 153, 153);">SoundCard Selection</span></b><b><span style="font-size: 10pt; font-family: Arial; color: black;"> field. If necessary, use the scroll arrow to reveal and select the SLU's sound card, which is called </span></b><b><span style="font-size: 10pt; font-family: Arial; color: rgb(204, 51, 0);">USB Audio CODEC </span></b><b><span style="font-size: 10pt; font-family: Arial; color: black;">(on some computers it may be called</span></b><b><span style="font-size: 10pt; font-family: Arial; color: rgb(204, 51, 0);"> USB Audio Device</span></b><b><span style="font-size: 10pt; font-family: Arial; color: black;">.</span></b><span style="font-family: Arial; color: black;"><o:p></o:p></span></p> <p><span style="font-family: Arial; color: black;"><a href="http://kc2rlm.info/soundcardpacket/images/signalinkUSB.png"></a></span><!--[if gte vml 1]><v:shape id="_x0000_s1027" type="#_x0000_t75" alt="" href="http://kc2rlm.info/soundcardpacket/images/signalinkUSB.png" style="'position:absolute;" allowoverlap="f" button="t"> <v:imagedata src="file:///C:\DOCUME~1\C11AE~1.BLA\LOCALS~1\Temp\msohtml1\01\clip_image010.png" title="signalinkUSB_small"> <w:wrap type="square"> </v:shape><![endif]--><!--[if !vml]--><a href="http://kc2rlm.info/soundcardpacket/images/signalinkUSB.png"><img src="file:///C:/DOCUME%7E1/C11AE%7E1.BLA/LOCALS%7E1/Temp/msohtml1/01/clip_image011.gif" shapes="_x0000_s1027" align="left" border="0" height="107" width="100" /></a><!--[endif]--><span style="font-family: Arial; color: black;"><a href="http://kc2rlm.info/soundcardpacket/images/signalinkUSB.png"></a></span><span style="font-family: Arial; color: black;"><-- </span><b><span style="font-size: 10pt; font-family: Arial; color: black;">click on this image for a larger image of the </span></b><b><span style="font-size: 10pt; font-family: Arial; color: blue;">SoundCard Modem/TNC Setup</span></b><b><span style="font-size: 10pt; font-family: Arial; color: black;"> window.</span></b><span style="font-family: Arial; color: black;"><o:p></o:p></span></p> <p><span style="font-family: Arial; color: black;"> <o:p></o:p></span></p> <p><span style="font-family: Arial; color: black;"> <o:p></o:p></span></p> <p><span style="font-family: Arial; color: black;"> <o:p></o:p></span></p> <p><b><span style="font-size: 10pt; font-family: Arial; color: black;">Then press </span></b><b><span style="font-size: 10pt; font-family: Arial; color: rgb(204, 51, 0);">OK </span></b><b><span style="font-size: 10pt; font-family: Arial; color: black;">to close all the AGWPE windows and restart AGWPE. The SignaLink USB should now be set to work with AGWPE.</span></b><span style="font-family: Arial; color: black;"><o:p></o:p></span></p> <p><b><span style="font-family: Arial; color: rgb(51, 0, 153);">2. Troubleshooting AGWPE - SignaLink USB (SLU) Problems</span></b><span style="font-family: Arial; color: black;"><o:p></o:p></span></p> <p><b><span style="font-size: 10pt; font-family: Arial; color: black;">The SignaLink USB Installation and Operation Guide contains detailed information about recommended SLU settings and troubleshooting. There is also a website which has troubleshooting information <a href="http://www.tigertronics.com/slusbts.htm">http://www.tigertronics.com/slusbts.htm</a></span></b><span style="font-family: Arial; color: black;"><o:p></o:p></span></p> <p><b><span style="font-size: 10pt; font-family: Arial; color: black;">Here are just a few key things to check if you have difficulties:</span></b><span style="font-family: Arial; color: black;"><o:p></o:p></span></p> <p><b><span style="font-size: 10pt; font-family: Arial; color: black;">a. </span></b><b><span style="font-size: 10pt; font-family: Arial; color: blue;">Received Audio</span></b><b><span style="font-size: 10pt; font-family: Arial; color: black;"> - The </span></b><b><span style="font-size: 10pt; font-family: Arial; color: blue;">RX</span></b><b><span style="font-size: 10pt; font-family: Arial; color: black;"> audio dial on the front of the SLU is the only way to increase or decrease the RX audio levels (unless you are getting the RX audio from the speaker of your radio, in which case your radio volume control dial will also have an effect on the RX audio level). I've had good success with the SLU's </span></b><b><span style="font-size: 10pt; font-family: Arial; color: blue;">RX</span></b><b><span style="font-size: 10pt; font-family: Arial; color: black;"> audio dial set to the 9 o'clock position.</span></b><span style="font-family: Arial; color: black;"><o:p></o:p></span></p> <p><b><span style="font-size: 10pt; font-family: Arial; color: black;">[You may have experience with other sound cards which use the Windows Volume Control </span></b><b><span style="font-size: 10pt; font-family: Arial; color: rgb(204, 51, 0);">Recording</span></b><b><span style="font-size: 10pt; font-family: Arial; color: black;"> sliders to adjust </span></b><b><span style="font-size: 10pt; font-family: Arial; color: rgb(204, 51, 0);">RX</span></b><b><span style="font-size: 10pt; font-family: Arial; color: black;"> volume levels. There is </span></b><b><span style="font-size: 10pt; font-family: Arial; color: rgb(204, 51, 0);">no</span></b><b><span style="font-size: 10pt; font-family: Arial; color: black;"> such control with the SLU; likewise <a href="http://kc2rlm.info/soundcardpacket/3volset.htm#AGWRxSet">the RX control sliders on AGWPE's Sound Card Tuning Aid screen</a> have</span></b><b><span style="font-size: 10pt; font-family: Arial; color: rgb(204, 51, 0);"> no </span></b><b><span style="font-size: 10pt; font-family: Arial; color: black;">effect on the SLU's RX Audio levels.]</span></b><span style="font-family: Arial; color: black;"><o:p></o:p></span></p> <p><b><span style="font-size: 10pt; font-family: Arial; color: black;">Also, set the </span></b><b><span style="font-size: 10pt; font-family: Arial; color: blue;">DLY</span></b><b><span style="font-size: 10pt; font-family: Arial; color: black;"> (Delay) dial on the front of the SLU to the 7 o'clock position (fully counterclockwise). This minimizes the time the SLU keeps your radio in transmit mode. If you increase the delay, the packet station which you are communicating with may begin to transmit before the SLU and your radio return to "receive" mode and you will not receive the first packet from the distant station.</span></b><span style="font-family: Arial; color: black;"><o:p></o:p></span></p> <p><b><span style="font-size: 10pt; font-family: Arial; color: black;">b. </span></b><b><span style="font-size: 10pt; font-family: Arial; color: blue;">TX Audio </span></b><b><span style="font-size: 10pt; font-family: Arial; color: black;">- </span></b><span style="font-family: Arial; color: black;"><o:p></o:p></span></p> <p class="MsoNormal" style="margin-left: 0.5in; text-indent: -0.25in;"><!--[if !supportLists]--><span style="font-size: 10pt; font-family: Symbol; color: black;"><span style=""><img src="PicExportError" alt="*" height="13" width="13" /><span style="font-family: "Times New Roman"; font-style: normal; font-variant: normal; font-weight: normal; font-size: 7pt; line-height: normal; font-size-adjust: none; font-stretch: normal;"> </span></span></span><!--[endif]--><b><span style="font-size: 10pt; font-family: Arial; color: black;"> Use the Windows Volume Control program to control the SLU's TX audio levels. Follow the instructions on the <a href="http://kc2rlm.info/soundcardpacket/3volset.htm#WinTxSet">Sound Card settings</a> page of this web site, but set the </span></b><b><span style="font-size: 10pt; font-family: Arial; color: rgb(0, 153, 153);">Speaker</span></b><b><span style="font-size: 10pt; font-family: Arial; color: black;"> slider for the </span></b><b><span style="font-size: 10pt; font-family: Arial; color: rgb(204, 51, 0);">USB Audio CODEC </span></b><b><span style="font-size: 10pt; font-family: Arial; color: black;">to maximum (up) and set the </span></b><b><span style="font-size: 10pt; font-family: Arial; color: rgb(0, 153, 153);">Wave</span></b><b><span style="font-size: 10pt; font-family: Arial; color: black;"> slider to 50%.
<br /> </span></b><span style="font-family: Arial; color: black;"> <o:p></o:p></span></p> <p class="MsoNormal" style="margin-left: 0.5in; text-indent: -0.25in;"><!--[if !supportLists]--><span style="font-size: 10pt; font-family: Symbol; color: black;"><span style=""><img src="PicExportError" alt="*" height="13" width="13" /><span style="font-family: "Times New Roman"; font-style: normal; font-variant: normal; font-weight: normal; font-size: 7pt; line-height: normal; font-size-adjust: none; font-stretch: normal;"> </span></span></span><!--[endif]--><b><span style="font-size: 10pt; font-family: Arial; color: black;"> Set the TX audio dial on the face of the SLU to the 9 o'clock position.</span></b><span style="font-family: Arial; color: black;"> <o:p></o:p></span></p> <p><b><span style="font-size: 10pt; font-family: Arial; color: black;">c. </span></b><b><span style="font-size: 10pt; font-family: Arial; color: blue;">PTT Transmit fails</span></b><b><span style="font-size: 10pt; font-family: Arial; color: black;">:</span></b><span style="font-family: Arial; color: black;"><o:p></o:p></span></p> <p class="MsoNormal" style="margin-left: 0.5in; text-indent: -0.25in;"><!--[if !supportLists]--><span style="font-size: 10pt; font-family: Symbol; color: black;"><span style=""><img src="PicExportError" alt="*" height="13" width="13" /><span style="font-family: "Times New Roman"; font-style: normal; font-variant: normal; font-weight: normal; font-size: 7pt; line-height: normal; font-size-adjust: none; font-stretch: normal;"> </span></span></span><!--[endif]--><b><span style="font-size: 10pt; font-family: Arial; color: rgb(204, 51, 0);">If the SignaLink USB's PTT LED does NOT turn ON: </span></b><b><span style="font-size: 10pt; font-family: Arial; color: black;">Verify that the SignaLink USB’s PWR LED is ON. If it is not, then make sure that the SignaLink USB's PWR switch is pressed in and the USB cable is securely connected to the computer and the SignaLink. </span></b><span style="font-family: Arial; color: black;"><o:p></o:p></span></p> <p style="margin-left: 0.5in;"><b><span style="font-size: 10pt; font-family: Arial; color: black;">Make sure AGWPE is configured to use the SignaLink USB’s built-in sound card. The program should have “USB Audio CODEC” selected. </span></b><span style="font-family: Arial; color: black;"><o:p></o:p></span></p> <p style="margin-left: 0.5in;"><b><span style="font-size: 10pt; font-family: Arial; color: black;">Try increasing the </span></b><b><span style="font-size: 10pt; font-family: Arial; color: rgb(0, 153, 153);">Wave</span></b><b><span style="font-size: 10pt; font-family: Arial; color: black;"> slider in the Windows Volume Control program for the USB Audio Codec. (There is also a special jumper setting inside the SLU to further increase TX audio levels; see the SLU Installation and Operation Guide.)</span></b><span style="font-family: Arial; color: black;"><o:p></o:p></span></p> <p style="margin-left: 0.5in;"><b><span style="font-size: 10pt; font-family: Arial; color: black;">If the SignaLink is plugged into a USB hub, verify that the hub is a powered hub. Non-powered hubs may not supply enough power for the SignaLink to operate properly (Receive will work, but Transmit may not).</span></b><span style="font-family: Arial; color: black;"><o:p></o:p></span></p> <p style="margin-left: 0.5in;"><span style="font-family: Arial; color: black;"> <o:p></o:p></span></p> <p class="MsoNormal" style="margin-left: 0.5in; text-indent: -0.25in;"><!--[if !supportLists]--><span style="font-size: 10pt; font-family: Symbol; color: black;"><span style=""><img src="PicExportError" alt="*" height="13" width="13" /><span style="font-family: "Times New Roman"; font-style: normal; font-variant: normal; font-weight: normal; font-size: 7pt; line-height: normal; font-size-adjust: none; font-stretch: normal;"> </span></span></span><!--[endif]--><b><span style="font-size: 10pt; font-family: Arial; color: rgb(204, 51, 0);">If the SignaLink USB's PTT LED turns ON</span></b><b><span style="font-size: 10pt; font-family: Arial; color: black;"> but the radio doesn't switch to transmit, then you have most likely incorrectly installed the PTT jumper wires inside the SLU. Double check the wiring there and also make sure that the cable to your radio is going to the correct PTT pin (in some radios, the PTT pin for FM packet is different from the one used for SSB modes such as PSK-31, RTTY and SSTV; if this is the case, you will need a different cable for packet).
<br /> </span></b><span style="font-family: Arial; color: black;"> <o:p></o:p></span></p> <p class="MsoNormal"><b style=""><span style="font-size: 16pt;">END SPECIAL SIGNAL LINK INFO +++++++++++++++++++++++++++++++++++<o:p></o:p></span></b></p> <p class="MsoNormal"><o:p> </o:p></p> <h2><span style="color: rgb(204, 51, 0);">Basic Sound Card Settings for AGWPE</span></h2> <p><b><span style="font-size: 10pt;">For AGWPE to work, you need to set four basic sound card settings correctly:</span></b></p> <ul type="disc"><li class="MsoNormal" style=""><b><span style="font-size: 10pt;"> The <span style="color: blue;">receive</span> audio <span style="color: teal;">source</span></span></b></li><li class="MsoNormal" style=""><b><span style="font-size: 10pt;"> The <span style="color: blue;">receive</span> audio <span style="color: red;">volume</span> <span style="color: red;">level</span></span></b></li><li class="MsoNormal" style=""><b><span style="font-size: 10pt;"> The <span style="color: maroon;">transmit </span>audio <span style="color: teal;">source</span></span></b></li><li class="MsoNormal" style=""><b><span style="font-size: 10pt;"> The <span style="color: maroon;">transmit </span>audio <span style="color: red;">volume</span> <span style="color: red;">level</span></span></b></li></ul> <p><b><span style="font-size: 10pt;">You can adjust these sound card settings in two ways:</span></b></p> <ul type="disc"><li class="MsoNormal" style=""><b><span style="font-size: 10pt;"><a href="http://www.kc2rlm.info/soundcardpacket/3volset.htm#AGWPEVolSet">1. AGWPE's Sound Card Volume Settings screen</a></span></b></li><ul type="circle"><li class="MsoNormal" style=""><b><span style="font-size: 10pt;"><a href="http://www.kc2rlm.info/soundcardpacket/3volset.htm#AGWRxSet">a. Receive Audio Settings</a></span></b></li><li class="MsoNormal" style=""><a href="http://www.kc2rlm.info/soundcardpacket/3volset.htm#AGWTxSet"><b><span style="font-size: 10pt;">b. T</span></b></a><b><span style="font-size: 10pt;"><a href="http://www.kc2rlm.info/soundcardpacket/3volset.htm#AGWTxSet">ransmit Audio Settings</a>
<br /> </span></b></li></ul><li class="MsoNormal" style=""><b><span style="font-size: 10pt;"><a href="http://www.kc2rlm.info/soundcardpacket/3volset.htm#windowsVolSet">2. Windows' </a></span><a href="http://www.kc2rlm.info/soundcardpacket/3volset.htm#windowsVolSet"><span style="font-size: 10pt;">Volume Control Program</span></a></b></li><ul type="circle"><li class="MsoNormal" style=""><a href="http://www.kc2rlm.info/soundcardpacket/3volset.htm#WinTxSet"><b><span style="font-size: 10pt;">a. T</span></b></a><b><span style="font-size: 10pt;"><a href="http://www.kc2rlm.info/soundcardpacket/3volset.htm#WinTxSet">ransmit Audio Settings</a></span></b></li><li class="MsoNormal" style=""><a href="http://www.kc2rlm.info/soundcardpacket/3volset.htm#WinRxSet"><b><span style="font-size: 10pt;">b. R</span></b></a><b><span style="font-size: 10pt;"><a href="http://www.kc2rlm.info/soundcardpacket/3volset.htm#WinRxSet">eceive Audio Settings</a></span></b></li></ul></ul> <p><b><span style="font-size: 10pt;">Other information on this page includes:</span></b></p> <ul type="disc"><li class="MsoNormal" style=""><b><span style="font-size: 10pt;">3. <a href="http://www.kc2rlm.info/soundcardpacket/3volset.htm#2cards">Configuring Two Sound Cards</a></span></b></li><li class="MsoNormal" style=""><b><span style="font-size: 10pt;">4. <a href="http://www.kc2rlm.info/soundcardpacket/3volset.htm#quickmix">Preserving Your Volume Settings (QuickMix)</a></span></b></li></ul> <p><b><span style="font-size: 10pt;">There are some advanced sound card settings that <span style="color: rgb(204, 51, 0);">may</span> also affect you. These include "Speaker Type", "Hardware Acceleration", and "Sample Rate". These are discussed on the <a href="http://www.kc2rlm.info/soundcardpacket/3voladd.htm">Additional Settings</a> page of this web site.</span></b></p> <p> </p> <h4>1. <a name="AGWPEVolSet">Using AGWPE</a> to Adjust Basic Sound Card Settings</h4> <p><b><span style="font-size: 10pt;">To set the volume controls from within AGWPE, right click the AGWPE tower icon <!--[if gte vml 1]><v:shape id="_x0000_i1035" type="#_x0000_t75" alt="" style="'width:18.75pt;height:18.75pt'"> <v:imagedata src="file:///C:\DOCUME~1\C11AE~1.BLA\LOCALS~1\Temp\msohtml1\01\clip_image004.gif" href="http://www.kc2rlm.info/soundcardpacket/AGWImages/TowerIcon.gif"> </v:shape><![endif]--><!--[if !vml]--><img src="file:///C:/DOCUME%7E1/C11AE%7E1.BLA/LOCALS%7E1/Temp/msohtml1/01/clip_image012.jpg" shapes="_x0000_i1035" border="0" height="25" width="25" /><!--[endif]-->to bring up the AGWPE menu and then click on <span style="color: rgb(0, 153, 153);"><a href="http://www.kc2rlm.info/soundcardpacket/3voltuneaid.htm">Sound Card Tuning Aid</a>.</span> The Tuning Aid is a great way to adjust your RX (receive) volume. Note that the Tuning Aid screen window will remain on top of all other windows. You can drag it with the blue Title Bar if it gets in the way, but it's handy to keep it displayed throughout the volume adjusting process:</span></b></p> <p><!--[if gte vml 1]><v:shape id="_x0000_i1036" type="#_x0000_t75" alt="" style="'width:438pt;height:270.75pt'"> <v:imagedata src="file:///C:\DOCUME~1\C11AE~1.BLA\LOCALS~1\Temp\msohtml1\01\clip_image013.gif" href="http://www.kc2rlm.info/soundcardpacket/AGWImages/3sinescreen.gif"> </v:shape><![endif]--><!--[if !vml]--><img src="file:///C:/DOCUME%7E1/C11AE%7E1.BLA/LOCALS%7E1/Temp/msohtml1/01/clip_image013.gif" shapes="_x0000_i1036" border="0" height="361" width="584" /><!--[endif]--></p> <p><b><span style="font-size: 10pt;">Then in the AGWPE <span style="color: rgb(0, 153, 153);"><a href="http://www.kc2rlm.info/soundcardpacket/3voltuneaid.htm">Sound Card Tuning Aid</a></span> window, click on the<span style="color: rgb(0, 153, 153);"> Set Volume </span>button to get to this window:</span></b></p> <p><span style="font-size: 10pt; font-family: Wingdings; color: rgb(0, 153, 153);"><!--[if gte vml 1]><v:shape id="_x0000_i1037" type="#_x0000_t75" alt="" style="'width:409.5pt;height:152.25pt'"> <v:imagedata src="file:///C:\DOCUME~1\C11AE~1.BLA\LOCALS~1\Temp\msohtml1\01\clip_image014.gif" href="http://www.kc2rlm.info/soundcardpacket/AGWImages/3setvol.gif"> </v:shape><![endif]--><!--[if !vml]--><img src="file:///C:/DOCUME%7E1/C11AE%7E1.BLA/LOCALS%7E1/Temp/msohtml1/01/clip_image014.gif" shapes="_x0000_i1037" border="0" height="203" width="546" /><!--[endif]--></span></p> <p><b><span style="font-size: 10pt;">See the sections a. and b. below for more information about these controls:</span></b></p> <table class="MsoNormalTable" style="border: medium none ; border-collapse: collapse;" border="1" cellpadding="0" cellspacing="0"> <tbody><tr style="height: 81pt;"> <td style="padding: 3.75pt; height: 81pt;"> <p class="MsoNormal"><b><span style="font-size: 10pt; color: red;">Bug Report:</span></b><b><span style="font-size: 10pt;"> There are still some problems with this AGWPE feature as of 2003.308:
<br /> </span></b></p> <ul type="disc"><li class="MsoNormal" style=""><b><span style="font-size: 10pt;">By default, this window assumes the LINE IN is the <span style="color: blue;">RX Input Line</span>. If you are using LINE IN, then you will have no problems and can use the volume sliders to adjust your RX audio level.
<br />
<br /> The bug is that the window will <span style="color: red;">not</span> let you change the <span style="color: blue;">RX Input Line</span> (audio source) as the pull down menu suggests. For example, if the sound card is now set to use the "LINE IN" jack as the audio source, then selecting "MIC" as the <span style="color: blue;">RX Input Line</span> in this window will have no affect. The sound card (and AGWPE) will continue to use "LINE IN". You will be able to control the volume sliders for the source you select, e.g. MIC, but your input source will not change to MIC.
<br /> </span></b></li><li class="MsoNormal" style=""><b><span style="font-size: 10pt;">If you have two sound cards in your system, AGWPE only controls the volume settings on the first sound card. If you are using a second sound card for AGWPE, then this window will have no affect on the settings for that second card.</span></b></li></ul> <p><b><span style="font-size: 10pt;">If either of these problems affect you, then you need to use the <span style="color: rgb(0, 153, 153);"><a href="http://www.kc2rlm.info/soundcardpacket/3volset.htm#windowsVolSet">Windows' Volume Control Program (see #2 below)</a></span> to adjust the input source and/or the sound card being used. <a href="http://www.kc2rlm.info/soundcardpacket/3volset.htm#windowsVolSet">See #2</a> below.</span></b></p> </td> </tr> </tbody></table> <p> </p> <h4>a. <a name="AGWRxSet">Receive Audio Settings (via AGWPE)</a></h4> <ul type="disc"><li class="MsoNormal" style=""><b><span style="font-size: 10pt; color: rgb(204, 51, 0);">Receive Audio Volume:</span></b><b><span style="font-size: 10pt;"> The left <span style="color: blue;">Rx </span>slider controls the receive volume (recording volume) of the left channel or port 1 of the sound card. The right column sliders control the right channel or port 2. (If you are using only one radio port in AGWPE, it will be the left slider).
<br />
<br /> I've had good success with the sliders set 1/3 up from the bottom. Be sure not to set them too low since it may stop all input (they don't have to be to the very bottom for audio input to be stopped). Use the sound card tuning aid's Sine Wave scope to see the results of your settings. The sine waves should fill about half the scope as in the Tuning Aid screen shot above. Use the volume slider to adjust the wave size. If you get the output from the radio's speaker jack, you can also adjust the radio volume. AGWPE is pretty tolerant of RX volume levels, but conceivably it is possible for the volume to be too loud or too soft.
<br />
<br /> If you don't see any waves, then your audio source setting is probably incorrect (see next paragraph) or, if you are using the radio's mike or speakers for RX audio, your radio's squelch in on; turn it off so you can hear the channel noise.
<br /> </span></b></li></ul> <table class="MsoNormalTable" style="border: medium none ; margin-left: 0.5in; border-collapse: collapse;" border="1" cellpadding="0" cellspacing="0"> <tbody><tr style=""> <td style="padding: 6pt;"> <p class="MsoNormal"><b><span style="font-size: 10pt;">Visit the <a href="http://www.kc2rlm.info/soundcardpacket/3voltuneaid.htm">Sound Card Tuning Aid page</a> for more information, including screen shots of signal problems.</span></b></p> </td> </tr> </tbody></table> <p style="margin-left: 0.5in; text-indent: -0.25in;"><!--[if !supportLists]--><span style="font-size: 10pt; font-family: Symbol;"><span style="">·<span style="font-family: "Times New Roman"; font-style: normal; font-variant: normal; font-weight: normal; font-size: 7pt; line-height: normal; font-size-adjust: none; font-stretch: normal;"> </span></span></span><!--[endif]--> </p> <ul type="disc"><li class="MsoNormal" style=""><b><span style="font-size: 10pt; color: rgb(204, 51, 0);">Receive Audio Source:</span></b><b><span style="font-size: 10pt;"> See <span style="color: red;">Bug Report</span> above. The Rx Input Line (audio source) does not work as advertised in version 2003.3008. You need to use the <span style="color: rgb(0, 153, 153);"><a href="http://www.kc2rlm.info/soundcardpacket/3volset.htm#windowsVolSet">Windows' Volume Control Program (see #2 below)</a></span> to adjust your settings.
<br />
<br /> [When the bug is corrected, you will be able to select the source of your receive audio, either <span style="color: blue;">Line </span>(meaning LINE IN) or <span style="color: blue;">Microphone</span>, depending where your RX audio cable is plugged. As the screen says, other sources will be muted and that's good.]
<br />
<br /> (If you opt to use the Microphone instead of the Line In for RX in, be sure that you <span style="color: red;">do not use the Microphone Boost option</span> of your sound card. See <span style="color: rgb(0, 153, 153);"><a href="http://www.kc2rlm.info/soundcardpacket/3volset.htm#windowsVolSet">Windows' Volume Control Program</a></span>below for <a href="http://www.kc2rlm.info/soundcardpacket/3volset.htm#boost">instructions on how to configure boost</a>.)
<br />
<br /> </span></b></li><li class="MsoNormal" style=""><b><span style="font-size: 10pt; color: rgb(204, 51, 0);">Set/Restore Options:</span></b><b><span style="font-size: 10pt;"> If you use your sound card for programs other than AGWPE, the <span style="color: blue;">Set These Levels on Start </span>and <span style="color: blue;">Restore Levels on Exit </span>will be helpful. They allow you to set the volume especially for AGWPE and then return them to their previous settings when you exit AGWPE.
<br /> </span></b></li></ul> <h4><a name="AGWTxSet">b. Transmit Audio Settings (via AGWPE)</a></h4> <ul type="disc"><li class="MsoNormal" style=""><b><span style="font-size: 10pt; color: rgb(204, 51, 0);">Transmit Audio Volume:</span></b><b><span style="font-size: 10pt;"> The <span style="color: blue;">Tx Master</span> sliders and two <span style="color: blue;">Tx Wave </span>volume sliders work together: <span style="color: maroon;">Wave</span> means <span style="color: maroon;">Program, </span>in this case AGWPE and the packet tones it generates. The <span style="color: blue;">Tx Master </span>sliders are a master control that will further adjust the <span style="color: blue;">Wave</span> volume.
<br />
<br /> As with the RX sliders, the left column sliders (for both Master and Wave) control the left channel or port 1 of the sound card. The right column sliders control the right channel or port 2.
<br />
<br /> I've had good success with the sliders set 1/3 up from the bottom. Your setting will depend largely on how well the attenuation circuit in your TX audio cable matches the optimal microphone input level for your radio. See <a href="http://www.kc2rlm.info/soundcardpacket/3volset.htm#txhowmuch">How Much TX Volume?</a> below for some further advice.
<br />
<br /> It is essential that none of these two sliders be at the absolute bottom or near the bottom, as that may stop all output.
<br /> </span></b></li></ul> <div align="center"> <table class="MsoNormalTable" style="border: medium none ; border-collapse: collapse;" border="1" cellpadding="0" cellspacing="0"> <tbody><tr style=""> <td style="padding: 5.25pt;"> <h4><a name="txhowmuch">How Much TX Volume</a>?</h4> <p><b><span style="font-size: 10pt;">You can get a rough idea of your TX volume by temporarily plugging your computer speakers into the LINE IN jack. But that will not tell you how what your TX audio sounds like on the air. It would be better to listen to your transmitted audio with a second radio.</span></b></p> <p><b><span style="font-size: 10pt;">But the best way to check your transmit volume is with a deviation meter. The correct deviation is 3.75 kHz of deviation (+/- .25). But since most of us don't have a deviation meter, Jim K6CCC offered this alternate suggestion:</span></b></p> <p><b><span style="font-size: 10pt;">My standard advice for people who do not have access to a deviation meter is to set your path to digipeat through a single local digipeater (e.g. TEST VIA WIDE ), then go into converse mode (UI mode) and transmit a single carriage return. Watch to see if your single packet gets digipeated by that one local digipeater. If it doesn't get digipeated on your first attempt, try several more times because it may not have gotten through because of a collision. <span style="color: red;">If it does not</span> get through after a few attempts, turn up the volume just to that point where it gets through reliably.</span></b></p> <p><b><span style="font-size: 10pt;">Conversely, if the packet <span style="color: red;">does</span> get digipeated, turn down the transmit audio level a little and try again. Keep doing this (turning down the volume) until your packet <span style="color: red;">does not </span>get digipeated reliably. Then turn it back up <span style="color: red;">just a little bit</span> and verify you can get the packet reliably digipeated.</span></b></p> <p><b><span style="font-size: 10pt;">It's FAR better to have your volume too low than too high!</span></b></p> </td> </tr> </tbody></table> </div> <p><b><span style="font-size: 10pt;">When you are done, press OK to save your settings and then close the Tuning Aid window.</span></b></p> <p> </p> <h4><a name="windowsVolSet">2. Using Windows' Volume Control Program</a> to Adjust Sound Card Settings </h4> <p><b><span style="font-size: 10pt;">It's also possible to set the volume control settings with the <span style="color: rgb(0, 153, 153);">Windows' Volume Control</span> program, but the AGWPE method above in #1 is much easier. However, there may be some settings, such as Microphone Boost, that can only be controlled by <span style="color: rgb(0, 153, 153);">Windows' Volume Control</span> program and not AGPWE. The The sections below discuss how to configure <span style="color: rgb(0, 153, 153);">Windows' Volume Control </span>for :</span></b></p> <ul type="disc"><li class="MsoNormal" style=""><b><span style="font-size: 10pt;"><a href="http://www.kc2rlm.info/soundcardpacket/3volset.htm#WinTxSet">Tx source and audio</a> (outgoing packet tones)</span></b></li><li class="MsoNormal" style=""><b><span style="font-size: 10pt;"><a href="http://www.kc2rlm.info/soundcardpacket/3volset.htm#WinRxSet">Rx source and audio</a> (incoming packet tones)</span></b></li></ul> <ul type="disc"><li class="MsoNormal" style=""><b><span style="font-size: 10pt;"><a href="http://www.kc2rlm.info/soundcardpacket/3volset.htm#2cards">two or more sound cards</a></span></b></li><li class="MsoNormal" style=""><b><span style="font-size: 10pt;"><a href="http://www.kc2rlm.info/soundcardpacket/3volset.htm#quickmix">preserving your volume control settings</a></span></b></li></ul> <p><b><span style="font-size: 10pt;">To start, you should see the volume control icon <!--[if gte vml 1]><v:shape id="_x0000_i1038" type="#_x0000_t75" alt="Windows Speaker Icon" style="'width:14.25pt;height:15pt'"> <v:imagedata src="file:///C:\DOCUME~1\C11AE~1.BLA\LOCALS~1\Temp\msohtml1\01\clip_image015.gif" href="http://www.kc2rlm.info/soundcardpacket/AGWImages/WinSpeaker.gif"> </v:shape><![endif]--><!--[if !vml]--><img src="file:///C:/DOCUME%7E1/C11AE%7E1.BLA/LOCALS%7E1/Temp/msohtml1/01/clip_image015.gif" alt="Windows Speaker Icon" shapes="_x0000_i1038" border="0" height="20" width="19" /><!--[endif]-->in the system tray on the lower right of your screen. If you don't, follow the directions on the <a href="http://www.kc2rlm.info/soundcardpacket/3voladd.htm#volicon">sound settings page</a> to display it.</span></b></p> <h4>a. <a name="WinTxSet">Transmit Audio Settings (via Windows)</a></h4> <p><b><span style="font-size: 10pt;">To set the source and volume level of your <span style="color: rgb(204, 51, 0);">outgoing</span> packet tones:</span></b></p> <ul type="disc"><li class="MsoNormal" style=""><b><span style="font-size: 10pt;">Left click twice very quickly on the <span style="color: rgb(0, 153, 153);">Volume Control icon </span><!--[if gte vml 1]><v:shape id="_x0000_i1039" type="#_x0000_t75" alt="Windows Speaker Icon" style="'width:14.25pt;height:15pt'"> <v:imagedata src="file:///C:\DOCUME~1\C11AE~1.BLA\LOCALS~1\Temp\msohtml1\01\clip_image015.gif" href="http://www.kc2rlm.info/soundcardpacket/AGWImages/WinSpeaker.gif"> </v:shape><![endif]--><!--[if !vml]--><img src="file:///C:/DOCUME%7E1/C11AE%7E1.BLA/LOCALS%7E1/Temp/msohtml1/01/clip_image015.gif" alt="Windows Speaker Icon" shapes="_x0000_i1039" border="0" height="20" width="19" /><!--[endif]-->(or go to the <span style="color: rgb(0, 153, 153);">Control Panel</span> and <span style="color: rgb(0, 153, 153);">Sounds: Audio</span>). The <span style="color: rgb(0, 153, 153);">Volume Control</span> window should open . It initially displays settings for just the <span style="color: rgb(204, 51, 0);">Playback</span> or <span style="color: rgb(204, 51, 0);">TX</span> audio ( sound card-to-radio). Here is what that window looks like in my system; it may be somewhat different in your system because of the sound card type:
<br />
<br /> <!--[if gte vml 1]><v:shape id="_x0000_i1040" type="#_x0000_t75" alt="" style="'width:418.5pt;height:235.5pt'"> <v:imagedata src="file:///C:\DOCUME~1\C11AE~1.BLA\LOCALS~1\Temp\msohtml1\01\clip_image016.gif" href="http://www.kc2rlm.info/soundcardpacket/AGWImages/3VolCtrl.gif"> </v:shape><![endif]--><!--[if !vml]--><img src="file:///C:/DOCUME%7E1/C11AE%7E1.BLA/LOCALS%7E1/Temp/msohtml1/01/clip_image016.gif" shapes="_x0000_i1040" border="0" height="314" width="558" /><!--[endif]-->
<br /> </span></b></li></ul> <ul type="disc"><li class="MsoNormal" style=""><b><span style="font-size: 10pt;">The settings of importance on this window are:
<br /> </span></b></li><ul type="circle"><li class="MsoNormal" style=""><b><span style="font-size: 10pt;">The left most <span style="color: blue;">Volume Control</span> volume slider and the <span style="color: blue;">Wave </span>volume slider work together. Consider<span style="color: blue;"> Wave</span> to mean <span style="color: blue;">Program</span><span style="color: maroon;">,</span> in this case AGWPE, which is creating the outgoing packet tones. The <span style="color: blue;">Volume Control </span>slider is a master control that will further adjust the <span style="color: blue;">Wave</span> volume.
<br />
<br /> I've had good success with both sliders set 1/3 up from the bottom. Your setting will depend largely on how well the attenuation circuit in your TX audio cable matches the optimal microphone input of your radio. See <a href="http://www.kc2rlm.info/soundcardpacket/3volset.htm#txhowmuch">How Much TX Volume?</a> below for some further advice.
<br />
<br /> It's essential that neither of these two sliders be at the absolute bottom or near the bottom, and it's essential that the <span style="color: blue;">Mute</span> boxes are <span style="color: red;">not checked</span>.
<br /> </span></b></li><li class="MsoNormal" style=""><b><span style="font-size: 10pt;">Leave all <span style="color: blue;">Balance</span> sliders in the middle. They are for stereo channel control and setting the slider to the wrong side could mute outgoing sounds to one of the two possible sound card channels/radioports.
<br /> </span></b></li><li class="MsoNormal" style=""><b><span style="font-size: 10pt;">I mute all other audio output sources ( Mic, Line In and CD) so that only AGWPE (wave) outputs sound to the radio and not other sources.
<br /> </span></b></li></ul></ul> <h4>b. <a name="WinRxSet">Receive Audio Settings (via Windows)</a> </h4> <p><b><span style="font-size: 10pt;">To set the source and volume level of your <span style="color: rgb(204, 51, 0);">receive or RX</span> audio is a bit more difficult to find. These settings are found in a <span style="color: red;">different</span><i> </i><span style="color: rgb(0, 153, 153);">Volume Control</span> <span style="color: red;">sub-window</span><i>,</i> the <span style="color: rgb(0, 153, 153);">Recording Control </span>window, whereas the outgoing sounds (see A. above) are set in the <span style="color: rgb(0, 153, 153);">Playback</span> window. <span style="color: red;">This is very important. </span>Many people do not realize this <span style="color: rgb(0, 153, 153);">Recording</span> window exists. Failure to get the recording settings correct results in problems receiving packets. To get to the Recording Window:</span></b></p> <ul type="disc"><li class="MsoNormal" style=""><b><span style="font-size: 10pt;">From the <span style="color: rgb(0, 153, 153);">Playback Volume Control</span> window shown above, select the <span style="color: blue;">Options</span> menu choice, then <span style="color: blue;">Properties.
<br /> </span></span></b></li><li class="MsoNormal" style=""><b><span style="font-size: 10pt;">Click on the <span style="color: blue;">Recording</span> radio button to bring up the list of volume controls. Make sure that there's a check mark <!--[if gte vml 1]><v:shape id="_x0000_i1041" type="#_x0000_t75" alt="" style="'width:12pt;height:9.75pt'"> <v:imagedata src="file:///C:\DOCUME~1\C11AE~1.BLA\LOCALS~1\Temp\msohtml1\01\clip_image017.gif" href="http://www.kc2rlm.info/soundcardpacket/AGWImages/checkmark.gif"> </v:shape><![endif]--><!--[if !vml]--><img src="file:///C:/DOCUME%7E1/C11AE%7E1.BLA/LOCALS%7E1/Temp/msohtml1/01/clip_image017.gif" shapes="_x0000_i1041" border="0" height="13" width="16" /><!--[endif]--> next to the jack where you plugged in your <span style="color: rgb(0, 153, 153);">radio RX audio</span> cable -- either <span style="color: blue;">Line In</span> (preferably) or <span style="color: blue;">Microphone</span>. Here's what this window looks like on my system. </span></b></li></ul> <p><!--[if gte vml 1]><v:shape id="_x0000_i1042" type="#_x0000_t75" alt="" style="'width:255.75pt;height:249pt'"> <v:imagedata src="file:///C:\DOCUME~1\C11AE~1.BLA\LOCALS~1\Temp\msohtml1\01\clip_image018.gif" href="http://www.kc2rlm.info/soundcardpacket/AGWImages/3VolCtrPropWin.gif"> </v:shape><![endif]--><!--[if !vml]--><img src="file:///C:/DOCUME%7E1/C11AE%7E1.BLA/LOCALS%7E1/Temp/msohtml1/01/clip_image018.gif" shapes="_x0000_i1042" border="0" height="332" width="341" /><!--[endif]--></p> <p style="margin-left: 0.5in; text-indent: -0.25in;"><!--[if !supportLists]--><span style="font-size: 10pt; font-family: Symbol;"><span style="">·<span style="font-family: "Times New Roman"; font-style: normal; font-variant: normal; font-weight: normal; font-size: 7pt; line-height: normal; font-size-adjust: none; font-stretch: normal;"> </span></span></span><!--[endif]--><b><span style="font-size: 10pt;">When you're done, click on the <span style="color: blue;">OK </span>button.
<br /> </span></b> </p> <p style="margin-left: 0.5in; text-indent: -0.25in;"><!--[if !supportLists]--><span style="font-size: 10pt; font-family: Symbol;"><span style="">·<span style="font-family: "Times New Roman"; font-style: normal; font-variant: normal; font-weight: normal; font-size: 7pt; line-height: normal; font-size-adjust: none; font-stretch: normal;"> </span></span></span><!--[endif]--><b><span style="font-size: 10pt;">You should now see the <span style="color: rgb(0, 153, 153);">Recording Control</span> window (or the <span style="color: rgb(0, 153, 153);">Wave In</span> window as it is called in my system). Since I use the <span style="color: blue;">Line In</span> jack for Radio RX audio, here's what my settings look like. Notice the <span style="color: blue;">Select</span> check mark <!--[if gte vml 1]><v:shape id="_x0000_i1043" type="#_x0000_t75" alt="" style="'width:12pt;height:9.75pt'"> <v:imagedata src="file:///C:\DOCUME~1\C11AE~1.BLA\LOCALS~1\Temp\msohtml1\01\clip_image017.gif" href="http://www.kc2rlm.info/soundcardpacket/AGWImages/checkmark.gif"> </v:shape><![endif]--><!--[if !vml]--><img src="file:///C:/DOCUME%7E1/C11AE%7E1.BLA/LOCALS%7E1/Temp/msohtml1/01/clip_image017.gif" shapes="_x0000_i1043" border="0" height="13" width="16" /><!--[endif]-->under <span style="color: blue;">Line In</span>:
<br />
<br /><!--[if gte vml 1]><v:shape id="_x0000_i1044" type="#_x0000_t75" alt="" style="'width:319.5pt;height:213pt'"> <v:imagedata src="file:///C:\DOCUME~1\C11AE~1.BLA\LOCALS~1\Temp\msohtml1\01\clip_image019.gif" href="http://www.kc2rlm.info/soundcardpacket/AGWImages/3recordset.gif"> </v:shape><![endif]--><!--[if !vml]--><img src="file:///C:/DOCUME%7E1/C11AE%7E1.BLA/LOCALS%7E1/Temp/msohtml1/01/clip_image019.gif" shapes="_x0000_i1044" border="0" height="284" width="426" /><!--[endif]-->
<br /> </span></b> </p> <p style="margin-left: 0.5in; text-indent: -0.25in;"><!--[if !supportLists]--><span style="font-size: 10pt; font-family: Symbol;"><span style="">·<span style="font-family: "Times New Roman"; font-style: normal; font-variant: normal; font-weight: normal; font-size: 7pt; line-height: normal; font-size-adjust: none; font-stretch: normal;"> </span></span></span><!--[endif]--><b><span style="font-size: 10pt;">Click the <span style="color: blue;">Select</span> box for the jack where you will plug in your <span style="color: rgb(0, 153, 153);">radio RX audio</span> cable, either the <span style="color: blue;">Line In</span> (preferably) or <span style="color: blue;">Microphone</span>.
<br /> </span></b> </p> <p style="margin-left: 0.5in; text-indent: -0.25in;"><!--[if !supportLists]--><span style="font-size: 10pt; font-family: Symbol;"><span style="">·<span style="font-family: "Times New Roman"; font-style: normal; font-variant: normal; font-weight: normal; font-size: 7pt; line-height: normal; font-size-adjust: none; font-stretch: normal;"> </span></span></span><!--[endif]--><b><span style="font-size: 10pt;">Set the volume slider about <span style="color: red;">1/3</span> up (soft). This should work for you, but note that AGWPE can probably handle any setting other than "off/quiet". See <a href="http://www.kc2rlm.info/soundcardpacket/3volset.htm#rxhowmuch">How Much RX Volume?</a> below for some further advice.
<br /> </span></b> </p> <p style="margin-left: 0.5in; text-indent: -0.25in;"><!--[if !supportLists]--><span style="font-size: 10pt; font-family: Symbol;"><span style="">·<span style="font-family: "Times New Roman"; font-style: normal; font-variant: normal; font-weight: normal; font-size: 7pt; line-height: normal; font-size-adjust: none; font-stretch: normal;"> </span></span></span><!--[endif]--><b><span style="font-size: 10pt;">Leave the balance slider in the middle.
<br /> </span></b> </p> <p style="margin-left: 0.5in; text-indent: -0.25in;"><!--[if !supportLists]--><span style="font-size: 10pt; font-family: Symbol;"><span style="">·<span style="font-family: "Times New Roman"; font-style: normal; font-variant: normal; font-weight: normal; font-size: 7pt; line-height: normal; font-size-adjust: none; font-stretch: normal;"> </span></span></span><!--[endif]--><b><span style="font-size: 10pt;">After you've made your choices, click the 'X' in the top right corner of the window to close the window and the Volume Control program. Your settings will be saved automatically.
<br />
<br /> </span></b> </p> <p><a name="boost"><b><span style="font-size: 10pt; color: rgb(204, 51, 0);">Microphone Boost:</span></b></a><span style=""><b><span style="font-size: 10pt;"> I</span></b></span><b><span style="font-size: 10pt;">f you opt to use the Microphone instead of the Line In for RX in, <span style="color: red;">do not use the Microphone Boost option</span> if it is offered by your system. I found this option by clicking on the <span style="color: rgb(0, 153, 153);">Advanced</span> button found under the <span style="color: rgb(0, 153, 153);">Microphone</span> slider in the <span style="color: rgb(0, 153, 153);">Recording Control</span> window. The "boost" feature typically adds a 20 dB increase in audio volume and is designed to amplify the weak signal from a computer electret microphone. The audio from your radio is normally already too high for input into the MIC jack (that is why you are advised to add an attenuation circuit to the RX cable). So using the boost feature can make the problem worse.</span></b></p> <p><span style="color: rgb(0, 153, 153);"><!--[if gte vml 1]><v:shape id="_x0000_i1045" type="#_x0000_t75" alt="" style="'width:291pt;height:274.5pt'"> <v:imagedata src="file:///C:\DOCUME~1\C11AE~1.BLA\LOCALS~1\Temp\msohtml1\01\clip_image020.gif" href="http://www.kc2rlm.info/soundcardpacket/AGWImages/2boostxp.gif"> </v:shape><![endif]--><!--[if !vml]--><img src="file:///C:/DOCUME%7E1/C11AE%7E1.BLA/LOCALS%7E1/Temp/msohtml1/01/clip_image020.gif" shapes="_x0000_i1045" border="0" height="366" width="388" /><!--[endif]-->
<br />
<br /> </span></p> <h4><a name="2cards">3. Configuring the</a> Volume Control program for a Second (or more) Sound Card</h4> <p><b><span style="font-size: 10pt;">If you have two or more sound cards installed, you will need to set the playback and record settings for the additional cards (those used by AGWPE). Here's how to do it:</span></b></p> <ul type="disc"><li class="MsoNormal" style=""><b><span style="font-size: 10pt;">Left click twice very quickly on the <span style="color: rgb(0, 153, 153);">Volume Control icon </span><!--[if gte vml 1]><v:shape id="_x0000_i1046" type="#_x0000_t75" alt="Windows Speaker Icon" style="'width:14.25pt;height:15pt'"> <v:imagedata src="file:///C:\DOCUME~1\C11AE~1.BLA\LOCALS~1\Temp\msohtml1\01\clip_image015.gif" href="http://www.kc2rlm.info/soundcardpacket/AGWImages/WinSpeaker.gif"> </v:shape><![endif]--><!--[if !vml]--><img src="file:///C:/DOCUME%7E1/C11AE%7E1.BLA/LOCALS%7E1/Temp/msohtml1/01/clip_image015.gif" alt="Windows Speaker Icon" shapes="_x0000_i1046" border="0" height="20" width="19" /><!--[endif]-->in the System Tray. The <span style="color: rgb(0, 153, 153);">Volume Control</span> window should open.</span></b></li><li class="MsoNormal" style=""><b><span style="font-size: 10pt;">Select the <span style="color: blue;">Options</span> menu choice, then <span style="color: blue;">Properties </span>to bring up the <span style="color: rgb(0, 153, 153);">Properties</span> Window<span style="color: blue;">.</span></span></b></li><li class="MsoNormal" style=""><b><span style="font-size: 10pt;">At the top of the <span style="color: rgb(0, 153, 153);">Properties</span> window, you'll see a <span style="color: blue;">Mixer Device</span> field. Click on the down arrow ▼to the right of the field to call up a list of mixer devices.</span></b></li></ul> <p><!--[if gte vml 1]><v:shape id="_x0000_i1047" type="#_x0000_t75" alt="" style="'width:258pt;height:349.5pt'"> <v:imagedata src="file:///C:\DOCUME~1\C11AE~1.BLA\LOCALS~1\Temp\msohtml1\01\clip_image021.gif" href="http://www.kc2rlm.info/soundcardpacket/AGWImages/3volctrlplay.gif"> </v:shape><![endif]--><!--[if !vml]--><img src="file:///C:/DOCUME%7E1/C11AE%7E1.BLA/LOCALS%7E1/Temp/msohtml1/01/clip_image021.gif" shapes="_x0000_i1047" border="0" height="466" width="344" /><!--[endif]--> <span style="font-size: 10pt; font-family: Wingdings; color: rgb(0, 153, 153);">ç </span><span style="color: rgb(0, 153, 153);">Click to enlarge</span></p> <ul type="disc"><li class="MsoNormal" style=""><b><span style="font-size: 10pt;">Click on the second sound card to select it. Then after making sure the <span style="color: red;">Playback </span>button below it is selected, press the <span style="color: blue;">OK</span> button. This will return you to the Volume Control <span style="color: red;">playback</span> sliders for the <span style="color: red;">second</span> card (the sound card's name will be in the lower left of the window). Make your settings as you did <a href="http://www.kc2rlm.info/soundcardpacket/3volset.htm#WinTxSet">above in Transmit Audio Settings</a>.
<br /> </span></b></li><li class="MsoNormal" style=""><b><span style="font-size: 10pt;">When your done with the playback settings for the second card, select the <span style="color: blue;">Options</span> menu choice again and then <span style="color: blue;">Properties </span>to bring up the <span style="color: rgb(0, 153, 153);">Properties</span> Window<span style="color: blue;"> </span>again.
<br /> </span></b></li><li class="MsoNormal" style=""><b><span style="font-size: 10pt;">Once again click on the down arrow ▼to the right of the <span style="color: blue;">Mixer Device</span> field to call up a list of mixer devices.
<br /> </span></b></li><li class="MsoNormal" style=""><b><span style="font-size: 10pt;">Click on the second sound card again to select it. This time make sure the <span style="color: red;">Recording</span> button is selected and press the <span style="color: blue;">OK</span> button. This will bring you to the Volume Control <span style="color: red;">recording</span> sliders for the second sound card . Make your settings as you did <a href="http://www.kc2rlm.info/soundcardpacket/3volset.htm#WinRxSet">above in Receive Audio Settings</a>.
<br /> </span></b></li></ul> <h4>4<a name="quickmix">. Preserving your volume control settings</a></h4> <p><b><span style="font-size: 10pt;">When most systems reboot, the volume control settings will remain as they were when you shut down. This is more likely if you use the <span style="color: rgb(0, 153, 153);">Set and Restore Options </span>in AGWPE's<span style="color: rgb(0, 153, 153);"> SoundCard Volume Settings screen,</span> <a href="http://www.kc2rlm.info/soundcardpacket/3volset.htm#WinRxSet">see Receive Audio Settings above</a>.<span style="color: rgb(0, 153, 153);"> </span> </span></b></p> <p><b><span style="font-size: 10pt;">However in some sound cards/systems, when Windows reboots, your Volume Control settings may automatically be reset to a default that is something other than you want. This happened to me with one sound card. Even though I would chose <span style="color: blue;">Line In</span> as my desired 'audio in' recording source, as soon as I rebooted, <span style="color: blue;">Microphone</span> became the recording audio source! I'm not sure why this was happening -- perhaps it was the sound card mixer program.</span></b></p> <p><b><span style="font-size: 10pt;">Or your ideal AGWPE settings may be changed by another program that subsequently uses the sound card.</span></b></p> <p><b><span style="font-size: 10pt;">You have two main options if this is happening to you:</span></b></p> <p><b><span style="font-size: 10pt;">1. Each time you run AGWPE after a Windows boot/reboot, re-configure the Volume Control <span style="color: rgb(0, 153, 153);">Recording Control</span> properties as above<span style="color: blue;">.</span></span></b></p> <p><b><span style="font-size: 10pt;">2. Use a utility program that, on startup, automatically sets the Volume Control settings the way you want them. I used a small (260 kb) freeware utility called <span style="color: rgb(0, 153, 153);">QuickMix</span> to do this. You can <a href="http://www.msaxon.com/quickmix/index.htm">download the program from the <span style="color: rgb(0, 153, 153);">Quick Mix</span> web site</a>. </span></b></p> <div align="center"> <table class="MsoNormalTable" style="border: medium none ; width: 75%; border-collapse: collapse;" border="1" cellpadding="0" cellspacing="0" width="75%"> <tbody><tr style=""> <td style="padding: 0in;"> <p><b><span style="font-size: 10pt; color: rgb(0, 153, 153);">Using QuickMix</span></b></p> <p><b><span style="font-size: 10pt;">1. Install QuickMix by running the QuickMixIn.exe program that you downloaded.</span></b></p> <p><b><span style="font-size: 10pt;">2. Set the Windows Volume Controls the way you want.
<br />
<br /> 3. Run the QuickMix program and 'save' the Volume Control settings to a AGWPE.QMX file in the directory of your choice.
<br />
<br /> 4. Then you can run QuickMix (or just click on the .QMX file) to restore your AGWPE settings.
<br />
<br /> If you want to have this .QMX file automatically load at boot-up, put a shortcut to this .QMX file in your Windows startup folder. For me, that would be:</span></b></p> <p><b><span style="font-size: 10pt;"> <span style="color: rgb(0, 153, 153);">C:\WINDOWS\Start Menu\Programs\StartUp</span>
<br />
<br />
<br /> In Windows Explorer, go to this directory and, from the Menu bar, select <span style="color: rgb(0, 153, 153);">File, </span>then <span style="color: rgb(0, 153, 153);">New</span>, then <span style="color: rgb(0, 153, 153);">Shortcut</span>, and then <span style="color: rgb(0, 153, 153);">Browse</span> to the AGWPE.QMX file you want. (Make sure you set the Browse directory window to show <span style="color: blue;">All Files,</span> not Programs.)</span></b></p> <p><b><span style="font-size: 10pt;">5. Now whenever you start Windows, it will automatically read the AGWPE.QMX file, load and run QuickMix, reset the Volume Controls, and then close QuickMix.</span></b></p> </td> </tr> </tbody></table> </div> <p class="MsoNormal"><o:p> </o:p></p> <p class="MsoNormal"><o:p> </o:p></p> <p class="MsoNormal"><o:p> </o:p></p> <p class="MsoNormal"><o:p> </o:p></p> <h2><span style="color: rgb(204, 51, 0);">Additional Sound Card Settings for AGWPE</span></h2> <p><b><span style="font-size: 10pt;"><a href="http://www.kc2rlm.info/soundcardpacket/3voladd.htm#multirmediaprop">Related Multimedia Properties</a></span></b>
<br /><b><span style="font-size: 10pt;"><a href="http://www.kc2rlm.info/soundcardpacket/3voladd.htm#volicon">Displaying the Volume Control Icon</a>
<br /><a href="http://www.kc2rlm.info/soundcardpacket/3voladd.htm#nosounds">Turning Off Window's Sounds</a></span></b></p> <p><b><span style="font-size: 10pt;">This page has additional sound card/multi-media properties that may be help in operating AGWPE successfully. (See the<a href="http://www.kc2rlm.info/soundcardpacket/3volset.htm"> Sound Card Settings page</a> on this site for basic sound card settings.)</span></b></p> <h4>1<a name="multirmediaprop">. Related Multimedia Properties</a></h4> <p><b><span style="font-size: 10pt;">Three additional Windows multi-media properties can affect AGWPE performance:</span></b></p> <ul type="disc"><li class="MsoNormal" style=""><b><span style="font-size: 10pt; color: blue;">Speaker Type</span></b><b><span style="font-size: 10pt;"> - affects TX audio; generally, <span style="color: blue;">Desktop Stereo Speakers </span>should be selected</span></b></li><li class="MsoNormal" style=""><b><span style="font-size: 10pt; color: blue;">Hardware Acceleration</span></b><b><span style="font-size: 10pt;"> - can affect both TX and RX audio; generally, the highest rate the computer can handle should be selected but if AGWPE is having packet decoding or connection problems, set it to a lower speed.</span></b></li><li class="MsoNormal" style=""><b><span style="font-size: 10pt; color: blue;">Sample Rate Conversion Quality</span></b><b><span style="font-size: 10pt;"> -- affects both TX and RX audio; generally, the highest rate the computer can handle should be selected</span></b></li></ul> <p><b><span style="font-size: 10pt;">These settings are usually made from the same general area in version of windows.</span></b></p> <p style="margin-left: 0.5in; text-indent: -0.25in;"><!--[if !supportLists]--><span style="font-size: 10pt; font-family: Symbol;"><span style="">·<span style="font-family: "Times New Roman"; font-style: normal; font-variant: normal; font-weight: normal; font-size: 7pt; line-height: normal; font-size-adjust: none; font-stretch: normal;"> </span></span></span><!--[endif]--><b><span style="font-size: 10pt; color: maroon;">Windows 95: </span></b><b><span style="font-size: 10pt;">There is little to set in the <span style="color: rgb(0, 153, 153);">Multimedia Properties</span> window. I'm not sure if the Recording <span style="color: blue;">Preferred quality </span>or<span style="color: blue;"> CD Quality </span>setting makes a difference. Click on the <span style="color: blue;">Apply</span> button (if not gray-ed out) and then the <span style="color: blue;">OK</span> button to close the window.
<br />
<br /> </span></b> </p> <p style="margin-left: 0.5in; text-indent: -0.25in;"><!--[if !supportLists]--><span style="font-size: 10pt; font-family: Symbol;"><span style="">·<span style="font-family: "Times New Roman"; font-style: normal; font-variant: normal; font-weight: normal; font-size: 7pt; line-height: normal; font-size-adjust: none; font-stretch: normal;"> </span></span></span><!--[endif]--><b><span style="font-size: 10pt; color: maroon;">Windows 98/ME:</span></b><b><span style="font-size: 10pt;"> Go to <span style="color: rgb(0, 153, 153);">Start: Settings: Control Panel</span> and select <span style="color: rgb(0, 153, 153);">Multimedia </span>(98) or <span style="color: rgb(0, 153, 153);">Sounds and Multimedia </span>(ME). With the default <span style="color: rgb(0, 153, 153);">Audio</span> tab showing:</span></b></p> <p style="margin-left: 1in; text-indent: -0.25in;"><!--[if !supportLists]--><span style="font-size: 10pt; font-family: "Courier New";"><span style="">o<span style="font-family: "Times New Roman"; font-style: normal; font-variant: normal; font-weight: normal; font-size: 7pt; line-height: normal; font-size-adjust: none; font-stretch: normal;"> </span></span></span><!--[endif]--><b><span style="font-size: 10pt;">Click first on the <span style="color: rgb(0, 153, 153);"> Advanced Properties</span> button<span style="color: rgb(204, 51, 0);"> </span>under the <span style="color: rgb(204, 51, 0);">Playback: Preferred Device</span><span style="color: rgb(0, 153, 153);"> </span>. On the resulting <span style="color: rgb(0, 153, 153);">Speaker </span>tab, select <span style="color: blue;">Desktop Stereo Speakers</span> (or lap top mono, maybe). According to George SV2AGW, anything else will distort the TX sound.
<br /> </span></b> </p> <p style="margin-left: 1in; text-indent: -0.25in;"><!--[if !supportLists]--><span style="font-size: 10pt; font-family: "Courier New";"><span style="">o<span style="font-family: "Times New Roman"; font-style: normal; font-variant: normal; font-weight: normal; font-size: 7pt; line-height: normal; font-size-adjust: none; font-stretch: normal;"> </span></span></span><!--[endif]--><b><span style="font-size: 10pt;">Then click on the <span style="color: rgb(0, 153, 153);">Performance</span> tab next to the Speakers tab. <span style="color: rgb(0, 153, 153);"> Hardware Acceleration</span> should be set to <span style="color: blue;">Full,</span> at least at first to see if your computer can handle it. If AGWPE is having packet decoding or connection problems, you can try setting it to a lower speed.
<br />
<br /><!--[if gte vml 1]><v:shape id="_x0000_i1048" type="#_x0000_t75" alt="" style="'width:284.25pt;height:282.75pt'"> <v:imagedata src="file:///C:\DOCUME~1\C11AE~1.BLA\LOCALS~1\Temp\msohtml1\01\clip_image022.gif" href="http://www.kc2rlm.info/soundcardpacket/AGWImages/3multprop98.gif"> </v:shape><![endif]--><!--[if !vml]--><img src="file:///C:/DOCUME%7E1/C11AE%7E1.BLA/LOCALS%7E1/Temp/msohtml1/01/clip_image022.gif" shapes="_x0000_i1048" border="0" height="377" width="379" /><!--[endif]-->
<br /> </span></b> </p> <p style="margin-left: 1in; text-indent: -0.25in;"><!--[if !supportLists]--><span style="font-size: 10pt; font-family: "Courier New";"><span style="">o<span style="font-family: "Times New Roman"; font-style: normal; font-variant: normal; font-weight: normal; font-size: 7pt; line-height: normal; font-size-adjust: none; font-stretch: normal;"> </span></span></span><!--[endif]--><b><span style="font-size: 10pt;">Below the Hardware acceleration settings is the <span style="color: rgb(0, 153, 153);">Sample Rate Conversion Quality</span> setting. Set this to <span style="color: blue;">Best</span>. Then click <span style="color: blue;">OK</span> to close the Playback Advanced Properties.
<br /> </span></b> </p> <p style="margin: 5pt 0in 12pt 1in; text-indent: -0.25in;"><!--[if !supportLists]--><span style="font-size: 10pt; font-family: "Courier New";"><span style="">o<span style="font-family: "Times New Roman"; font-style: normal; font-variant: normal; font-weight: normal; font-size: 7pt; line-height: normal; font-size-adjust: none; font-stretch: normal;"> </span></span></span><!--[endif]--><b><span style="font-size: 10pt;">Back on the <span style="color: rgb(0, 153, 153);">Audio</span> tab, click on the<span style="color: rgb(0, 153, 153);"> Advanced Properties</span> button under <span style="color: rgb(204, 51, 0);">Recording: Preferred Device</span>. On the <span style="color: rgb(0, 153, 153);">Performance</span> tab, once again set the <span style="color: rgb(0, 153, 153);">Hardware Acceleration</span> one stop before <span style="color: blue;">Full, </span>at least at first to see if your computer can handle it. If AGWPE is having packet decoding or connection problems, set it to a lower speed.<span style="color: rgb(0, 153, 153);"> </span>And set <span style="color: rgb(0, 153, 153);">Sample Rate Conversion Quality</span> to <span style="color: blue;">Best</span>. Then click OK to close the Sound Recording Advanced Properties. </span></b></p> <p style="margin-left: 1in; text-indent: -0.25in;"><!--[if !supportLists]--><span style="font-size: 10pt; font-family: "Courier New";"><span style="">o<span style="font-family: "Times New Roman"; font-style: normal; font-variant: normal; font-weight: normal; font-size: 7pt; line-height: normal; font-size-adjust: none; font-stretch: normal;"> </span></span></span><!--[endif]--><b><span style="font-size: 10pt;">Back on the <span style="color: rgb(0, 153, 153);">Multimedia Properties</span> window, click on the <span style="color: blue;">Apply</span> button (if not gray-ed out) and then the <span style="color: blue;">OK</span> button.
<br /> </span></b> </p> <p style="margin-left: 1in; text-indent: -0.25in;"><!--[if !supportLists]--><span style="font-size: 10pt; font-family: "Courier New";"><span style="">o<span style="font-family: "Times New Roman"; font-style: normal; font-variant: normal; font-weight: normal; font-size: 7pt; line-height: normal; font-size-adjust: none; font-stretch: normal;"> </span></span></span><!--[endif]--><b><span style="font-size: 10pt;">On the <span style="color: rgb(0, 153, 153);">Audio</span> tab, click on the <span style="color: rgb(0, 153, 153);">Advanced</span> button for<span style="color: rgb(0, 153, 153);"> (Sound) Playback
<br /> </span></span></b> </p> <p style="margin-left: 1in; text-indent: -0.25in;"><!--[if !supportLists]--><span style="font-size: 10pt; font-family: "Courier New";"><span style="">o<span style="font-family: "Times New Roman"; font-style: normal; font-variant: normal; font-weight: normal; font-size: 7pt; line-height: normal; font-size-adjust: none; font-stretch: normal;"> </span></span></span><!--[endif]--><b><span style="font-size: 10pt;">Click <span style="color: blue;">OK</span> to save the settings and leave the <span style="color: rgb(0, 153, 153);">Sounds</span> settings.</span></b> </p> <p style="margin-left: 0.5in;"> </p> <p style="margin-left: 0.5in; text-indent: -0.25in;"><!--[if !supportLists]--><span style="font-size: 10pt; font-family: Symbol;"><span style="">·<span style="font-family: "Times New Roman"; font-style: normal; font-variant: normal; font-weight: normal; font-size: 7pt; line-height: normal; font-size-adjust: none; font-stretch: normal;"> </span></span></span><!--[endif]--><b><span style="font-size: 10pt; color: maroon;">Windows XP</span></b><b><span style="font-size: 10pt;">: Most of the default settings should be as described below but you should check them. Go to <span style="color: rgb(0, 153, 153);">Start: Settings: Control Panel</span> and select <span style="color: rgb(0, 153, 153);">Sound and Audio Devices.</span> On the<span style="color: rgb(0, 153, 153);"> Audio</span> tab, press the<span style="color: rgb(0, 153, 153);"> Advanced </span>button under <span style="color: rgb(0, 153, 153);">Sound Playback</span>
<br /> </span></b></p> <p style="margin-left: 1in; text-indent: -0.25in;"><!--[if !supportLists]--><span style="font-size: 10pt; font-family: "Courier New";"><span style="">o<span style="font-family: "Times New Roman"; font-style: normal; font-variant: normal; font-weight: normal; font-size: 7pt; line-height: normal; font-size-adjust: none; font-stretch: normal;"> </span></span></span><!--[endif]--><b><span style="font-size: 10pt;">On the resulting <span style="color: rgb(0, 153, 153);">Speaker </span>tab, select <span style="color: blue;">Desktop Stereo Speakers</span>, even if this is a lap top.
<br /> </span></b> </p> <p style="margin-left: 1in; text-indent: -0.25in;"><!--[if !supportLists]--><span style="font-size: 10pt; font-family: "Courier New";"><span style="">o<span style="font-family: "Times New Roman"; font-style: normal; font-variant: normal; font-weight: normal; font-size: 7pt; line-height: normal; font-size-adjust: none; font-stretch: normal;"> </span></span></span><!--[endif]--><b><span style="font-size: 10pt;">Then click on the <span style="color: rgb(0, 153, 153);">Performance</span> tab next to the Speakers tab.
<br /> </span></b> </p> <p style="margin-left: 1in; text-indent: -0.25in;"><!--[if !supportLists]--><span style="font-size: 10pt; font-family: "Courier New";"><span style="">o<span style="font-family: "Times New Roman"; font-style: normal; font-variant: normal; font-weight: normal; font-size: 7pt; line-height: normal; font-size-adjust: none; font-stretch: normal;"> </span></span></span><!--[endif]--><b><span style="font-size: 10pt; color: rgb(0, 153, 153);"> Hardware Acceleration</span></b><b><span style="font-size: 10pt;"> should be set to <span style="color: blue;">Full,</span> at least at first to see if your computer can handle it. If AGWPE is having packet decoding or connection problems, you can try setting it to a lower speed.
<br /> </span></b> </p> <p style="margin-left: 1in; text-indent: -0.25in;"><!--[if !supportLists]--><span style="font-size: 10pt; font-family: "Courier New";"><span style="">o<span style="font-family: "Times New Roman"; font-style: normal; font-variant: normal; font-weight: normal; font-size: 7pt; line-height: normal; font-size-adjust: none; font-stretch: normal;"> </span></span></span><!--[endif]--><b><span style="font-size: 10pt; color: rgb(0, 153, 153);">Sample Rate Conversion Quality</span></b><b><span style="font-size: 10pt;"> must be set to <span style="color: blue;">Best</span>.
<br /> </span></b> </p> <p style="margin-left: 1in; text-indent: -0.25in;"><!--[if !supportLists]--><span style="font-size: 10pt; font-family: "Courier New";"><span style="">o<span style="font-family: "Times New Roman"; font-style: normal; font-variant: normal; font-weight: normal; font-size: 7pt; line-height: normal; font-size-adjust: none; font-stretch: normal;"> </span></span></span><!--[endif]--><b><span style="font-size: 10pt;">Then click <span style="color: blue;">OK</span> to close the <span style="color: rgb(0, 153, 153);">Playback Advanced Properties</span> and return to the <span style="color: rgb(0, 153, 153);">Sound and Audio Devices: Audio</span> tab.click on the <span style="color: blue;">Apply</span> button (if not gray-ed out) and then the <span style="color: blue;">OK</span> button.
<br /> </span></b> </p> <p style="margin-left: 0.5in; text-indent: -0.25in;"><!--[if !supportLists]--><span style="font-size: 10pt; font-family: Symbol;"><span style="">·<span style="font-family: "Times New Roman"; font-style: normal; font-variant: normal; font-weight: normal; font-size: 7pt; line-height: normal; font-size-adjust: none; font-stretch: normal;"> </span></span></span><!--[endif]--><b><span style="font-size: 10pt; color: maroon;">Windows 2000:</span></b><b><span style="font-size: 10pt;"> the default hardware acceleration and sample rate conversion sliders are in the middle position. Follow the general instruction for XP above and move these to the right for best performance.
<br /> </span></b></p> <h4>2<a name="volicon">. Displaying the Volume Control Icon</a><span style=""></span><span style="font-size: 10pt; color: blue;"> </span><span style="font-size: 10pt;"><!--[if gte vml 1]><v:shape id="_x0000_i1049" type="#_x0000_t75" alt="Windows Speaker Icon" style="'width:14.25pt;height:15pt'"> <v:imagedata src="file:///C:\DOCUME~1\C11AE~1.BLA\LOCALS~1\Temp\msohtml1\01\clip_image015.gif" href="http://www.kc2rlm.info/soundcardpacket/AGWImages/WinSpeaker.gif"> </v:shape><![endif]--><!--[if !vml]--><img src="file:///C:/DOCUME%7E1/C11AE%7E1.BLA/LOCALS%7E1/Temp/msohtml1/01/clip_image015.gif" alt="Windows Speaker Icon" shapes="_x0000_i1049" border="0" height="20" width="19" /><!--[endif]--></span></h4> <p><b><span style="font-size: 10pt;">If this icon is not currently in your Windows System Tray (bottom far right of your screen), you may want to add it. It lets you quickly access the Windows volume and audio source settings of the sound card, including some that can not be controlled by AGWPE's SoundCard Volume Settings screen. </span></b></p> <ul type="disc"><li class="MsoNormal" style=""><b><span style="font-size: 10pt;">In Windows 98 it's , <span style="color: rgb(0, 153, 153);">Start: Settings: Control Panel: Multimedia: Audio </span>tab and check <!--[if gte vml 1]><v:shape id="_x0000_i1050" type="#_x0000_t75" alt="" style="'width:12pt;height:9.75pt'"> <v:imagedata src="file:///C:\DOCUME~1\C11AE~1.BLA\LOCALS~1\Temp\msohtml1\01\clip_image017.gif" href="http://www.kc2rlm.info/soundcardpacket/AGWImages/checkmark.gif"> </v:shape><![endif]--><!--[if !vml]--><img src="file:///C:/DOCUME%7E1/C11AE%7E1.BLA/LOCALS%7E1/Temp/msohtml1/01/clip_image017.gif" shapes="_x0000_i1050" border="0" height="13" width="16" /><!--[endif]--><span style="color: blue;">Show volume control on the taskbar.</span></span></b></li><li class="MsoNormal" style=""><b><span style="font-size: 10pt;">In Windows ME it's: <span style="color: rgb(0, 153, 153);">Start: Settings: Control Panel: Sounds and Multimedia: Sounds</span> tab; <span style="color: rgb(0, 153, 153);">Sound Volume</span> box and check <!--[if gte vml 1]><v:shape id="_x0000_i1051" type="#_x0000_t75" alt="" style="'width:12pt;height:9.75pt'"> <v:imagedata src="file:///C:\DOCUME~1\C11AE~1.BLA\LOCALS~1\Temp\msohtml1\01\clip_image017.gif" href="http://www.kc2rlm.info/soundcardpacket/AGWImages/checkmark.gif"> </v:shape><![endif]--><!--[if !vml]--><img src="file:///C:/DOCUME%7E1/C11AE%7E1.BLA/LOCALS%7E1/Temp/msohtml1/01/clip_image017.gif" shapes="_x0000_i1051" border="0" height="13" width="16" /><!--[endif]--><span style="color: blue;">Show volume control on the taskbar.</span></span></b></li><li class="MsoNormal" style=""><b><span style="font-size: 10pt;">In XP, it's <span style="color: rgb(0, 153, 153);">Start: Control Panel: Sounds and Audio Devices: Volume </span>tab and check <!--[if gte vml 1]><v:shape id="_x0000_i1052" type="#_x0000_t75" alt="" style="'width:12pt;height:9.75pt'"> <v:imagedata src="file:///C:\DOCUME~1\C11AE~1.BLA\LOCALS~1\Temp\msohtml1\01\clip_image017.gif" href="http://www.kc2rlm.info/soundcardpacket/AGWImages/checkmark.gif"> </v:shape><![endif]--><!--[if !vml]--><img src="file:///C:/DOCUME%7E1/C11AE%7E1.BLA/LOCALS%7E1/Temp/msohtml1/01/clip_image017.gif" shapes="_x0000_i1052" border="0" height="13" width="16" /><!--[endif]--><span style="color: blue;">Place volume icon in the taskbar.</span></span></b></li><li class="MsoNormal" style=""><b><span style="font-size: 10pt;">I'm not sure how it's done in Windows 95, but it's probably very similar to Win 98.
<br /> </span></b></li></ul> <h4>3<a name="nosounds">. Turning Off Window's Sounds</a></h4> <p><b><span style="font-size: 10pt;">On some computers you may have conflicts between a program and Windows itself over the use of the sound card. (A typical crash message is "an application <span style="color: red;">caused an invalid page fault in module WINMM.DLL</span>"). To avoid this, try turning off Windows' sounds.</span></b></p> <ul type="disc"><li class="MsoNormal" style=""><b><span style="font-size: 10pt;">In Windows 98 it's:<span style="color: rgb(0, 153, 153);"> Start: Settings: Control Panel: Sounds: Schemes </span>field = <span style="color: blue;">No Sounds</span></span></b></li><li class="MsoNormal" style=""><b><span style="font-size: 10pt;">In Windows ME it's: <span style="color: rgb(0, 153, 153);">Start: Settings: Control Panel: Sounds: Sound Events: Scheme </span>= <span style="color: blue;">No Sounds.</span></span></b></li><li class="MsoNormal" style=""><b><span style="font-size: 10pt;">In XP, it's <span style="color: rgb(0, 153, 153);">Start: Control Panel: Sounds and Audio Devices: Sounds </span>tab<span style="color: rgb(0, 153, 153);">: Sound Scheme </span>field = <span style="color: blue;">No Sounds.</span></span></b></li><li class="MsoNormal" style=""><b><span style="font-size: 10pt;">I'm not sure how it's done in Windows 95, but it's probably very similar to Win 98.
<br /> </span></b></li></ul> <h2><span style="color: rgb(204, 51, 0);">Sound Card Tuning Aid</span></h2> <p><b><span style="font-size: 10pt;">The <span style="color: rgb(0, 153, 153);">Sound Card Tuning Aid</span> screen is accessible from the AGWPE menu and can be used to "see" the quality of received signals and, for HF packet particularly, help in tuning the radio to the correct frequency. At least one oscilloscope will appear on the left side of the screen. A second scope below the first only appears if you have selected <st1:place st="on"><st1:placename st="on"><span style="color: rgb(0, 153, 153);">Dual</span></st1:placename><span style="color: rgb(0, 153, 153);"> <st1:placetype st="on">Port</st1:placetype></span></st1:place><span style="color: rgb(0, 153, 153);"> </span>use of the sound card on the <a href="http://www.kc2rlm.info/soundcardpacket/2agwbasic.htm#portsettings">Properties screen</a>.</span></b></p> <p><b><span style="font-size: 10pt;">This page gives describes the Tuning Aid and gives some examples of good and bad signals as seen on the tuning aid's oscilloscope.</span></b></p> <p><b><span style="font-size: 10pt;">The first screen shot below shows the Tuning Aid page with the sine wave view selected. Only one oscilloscope is visible since the sound card is running in <st1:place st="on"><st1:placename st="on">Single</st1:placename> <st1:placetype st="on">Port</st1:placetype></st1:place> mode. In <st1:place st="on"><st1:placename st="on">Dual</st1:placename> <st1:placetype st="on">Port</st1:placetype></st1:place> mode, another scope would appear beneath the first. Note the sine wave in the scope. This is what a quiet 1200 baud packet channel looks like. The only undulation in the wave is due to noise. It verifies the audio connection to the sound card and radio is working.</span></b></p> <p><span style="font-size: 10pt;"><a href="http://www.kc2rlm.info/soundcardpacket/AGWImages/3tunea9.gif"><span style="text-decoration: none;"><!--[if gte vml 1]><v:shape id="_x0000_i1053" type="#_x0000_t75" alt="" style="'width:75pt;height:45.75pt'" button="t"> <v:imagedata src="file:///C:\DOCUME~1\C11AE~1.BLA\LOCALS~1\Temp\msohtml1\01\clip_image023.gif" href="http://www.kc2rlm.info/soundcardpacket/AGWImages/3tunea9_small.gif"> </v:shape><![endif]--><!--[if !vml]--><img src="file:///C:/DOCUME%7E1/C11AE%7E1.BLA/LOCALS%7E1/Temp/msohtml1/01/clip_image023.gif" shapes="_x0000_i1053" border="0" height="61" width="100" /><!--[endif]--></span></a><-- Click for larger image</span></p> <p> </p> <p><b><span style="font-size: 10pt;">In contrast, if the sine wave was perfectly flat (or nearly so), as below, then you know you have no audio input from the sound card, either because of a problem with the audio feed from the radio or incorrect sound card volume settings (source or volume): </span></b></p> <p><span style="font-size: 10pt;"><a href="http://www.kc2rlm.info/soundcardpacket/AGWImages/3tunea6.gif"><span style="text-decoration: none;"><!--[if gte vml 1]><v:shape id="_x0000_i1054" type="#_x0000_t75" alt="" style="'width:75pt;height:46.5pt'" button="t"> <v:imagedata src="file:///C:\DOCUME~1\C11AE~1.BLA\LOCALS~1\Temp\msohtml1\01\clip_image024.gif" href="http://www.kc2rlm.info/soundcardpacket/AGWImages/3tunea6_small.gif"> </v:shape><![endif]--><!--[if !vml]--><img src="file:///C:/DOCUME%7E1/C11AE%7E1.BLA/LOCALS%7E1/Temp/msohtml1/01/clip_image024.gif" shapes="_x0000_i1054" border="0" height="62" width="100" /><!--[endif]--></span></a><-- Click for larger image</span></p> <p> </p> <h4><span style="color: navy;">Oscilloscope Styles</span> </h4> <p><b><span style="font-size: 10pt;">There are four (4) display styles available for the Oscilloscope. The first two are generally the most useful.</span></b></p> <p><b><span style="color: rgb(204, 51, 0);">1. Sine Wave</span></b><b><span style="font-size: 10pt;"> - shows strength of the signal (audio volume) and the quality of the signal. A signal with good strength will have waves that fill about 1/2 of the screen (relative distance between the peaks and valleys of the wave). You can use the <a href="http://www.kc2rlm.info/soundcardpacket/3volset.htm">Volume Control settings</a> for RX audio to adjust them.</span></b></p> <p><b><span style="font-size: 10pt;">Signal samples for 1200 baud:</span></b></p> <table class="MsoNormalTable" style="" border="0" cellpadding="0"> <tbody><tr style=""> <td style="padding: 3.75pt; width: 266.25pt;" width="355"> <p class="MsoNormal"><!--[if gte vml 1]><v:shape id="_x0000_i1055" type="#_x0000_t75" alt="" style="'width:253.5pt;height:101.25pt'"> <v:imagedata src="file:///C:\DOCUME~1\C11AE~1.BLA\LOCALS~1\Temp\msohtml1\01\clip_image025.gif" href="http://www.kc2rlm.info/soundcardpacket/AGWImages/3tunea10.gif"> </v:shape><![endif]--><!--[if !vml]--><img src="file:///C:/DOCUME%7E1/C11AE%7E1.BLA/LOCALS%7E1/Temp/msohtml1/01/clip_image025.gif" shapes="_x0000_i1055" border="0" height="135" width="338" /><!--[endif]--></p> </td> <td style="padding: 3.75pt;"> <p class="MsoNormal"><b><span style="font-size: 10pt;">Sample of a good signal;
<br /> packet decoded.
<br /> </span></b></p> </td> </tr> <tr style=""> <td style="padding: 3.75pt; width: 266.25pt;" width="355"> <p class="MsoNormal"><b><span style="font-size: 10pt;"><!--[if gte vml 1]><v:shape id="_x0000_i1056" type="#_x0000_t75" alt="" style="'width:251.25pt;height:100.5pt'"> <v:imagedata src="file:///C:\DOCUME~1\C11AE~1.BLA\LOCALS~1\Temp\msohtml1\01\clip_image026.gif" href="http://www.kc2rlm.info/soundcardpacket/AGWImages/3tunea11.gif"> </v:shape><![endif]--><!--[if !vml]--><img src="file:///C:/DOCUME%7E1/C11AE%7E1.BLA/LOCALS%7E1/Temp/msohtml1/01/clip_image026.gif" shapes="_x0000_i1056" border="0" height="134" width="335" /><!--[endif]-->
<br /> </span></b></p> </td> <td style="padding: 3.75pt;"> <p class="MsoNormal"><b><span style="font-size: 10pt;">Too weak or distant;
<br /> packet was not decoded</span></b></p> </td> </tr> <tr style=""> <td style="padding: 3.75pt; width: 266.25pt;" width="355"> <p class="MsoNormal"><!--[if gte vml 1]><v:shape id="_x0000_i1057" type="#_x0000_t75" alt="" style="'width:253.5pt;height:99.75pt'"> <v:imagedata src="file:///C:\DOCUME~1\C11AE~1.BLA\LOCALS~1\Temp\msohtml1\01\clip_image027.gif" href="http://www.kc2rlm.info/soundcardpacket/AGWImages/3tunea12.gif"> </v:shape><![endif]--><!--[if !vml]--><img src="file:///C:/DOCUME%7E1/C11AE%7E1.BLA/LOCALS%7E1/Temp/msohtml1/01/clip_image027.gif" shapes="_x0000_i1057" border="0" height="133" width="338" /><!--[endif]--><b><span style="font-size: 10pt;">
<br /> </span></b></p> </td> <td style="padding: 3.75pt;"> <p class="MsoNormal"><b><span style="font-size: 10pt;">Collision of packets;
<br /> packet was not decoded
<br /> </span></b></p> </td> </tr> <tr style=""> <td style="padding: 3.75pt; width: 266.25pt;" valign="top" width="355"> <p class="MsoNormal"><!--[if gte vml 1]><v:shape id="_x0000_i1058" type="#_x0000_t75" alt="" style="'width:252pt;height:102.75pt'"> <v:imagedata src="file:///C:\DOCUME~1\C11AE~1.BLA\LOCALS~1\Temp\msohtml1\01\clip_image028.gif" href="http://www.kc2rlm.info/soundcardpacket/AGWImages/3tunea13.gif"> </v:shape><![endif]--><!--[if !vml]--><img src="file:///C:/DOCUME%7E1/C11AE%7E1.BLA/LOCALS%7E1/Temp/msohtml1/01/clip_image028.gif" shapes="_x0000_i1058" border="0" height="137" width="336" /><!--[endif]--></p> </td> <td style="padding: 3.75pt;"> <p class="MsoNormal"><b><span style="font-size: 10pt;">This is from a Yaesu FT209 transceiver with bass boost activated. The boost creates incorrect pre-emphasis: the low tone is emphasized, not the high tone. These packets can only be decoded about 80% of the time. The sending station must turn off the radio's bass boost option to correct this.</span></b></p> </td> </tr> <tr style=""> <td style="padding: 3.75pt; width: 266.25pt;" valign="top" width="355"> <p class="MsoNormal"><b><span style="font-size: 10pt;">
<br />
<br /> </span></b></p> </td> <td style="padding: 3.75pt;"> <p class="MsoNormal"> </p> </td> </tr> </tbody></table> <p><b><span style="font-size: 10pt;"> Below, a 9600 baud signal sample:</span></b></p> <p><!--[if gte vml 1]><v:shape id="_x0000_i1059" type="#_x0000_t75" alt="" style="'width:252pt;height:102.75pt'"> <v:imagedata src="file:///C:\DOCUME~1\C11AE~1.BLA\LOCALS~1\Temp\msohtml1\01\clip_image029.gif" href="http://www.kc2rlm.info/soundcardpacket/AGWImages/3tunea14.gif"> </v:shape><![endif]--><!--[if !vml]--><img src="file:///C:/DOCUME%7E1/C11AE%7E1.BLA/LOCALS%7E1/Temp/msohtml1/01/clip_image029.gif" shapes="_x0000_i1059" border="0" height="137" width="336" /><!--[endif]--></p> <p>
<br /><b><span style="font-size: 10pt;">This is a generally good signal that was decoded, but you can see small sparks caused by some "bug" at either the transmitting station or receiving radio or sound card.</span></b></p> <p><b><span style="font-size: 10pt;">
<br />
<br /></span><span style="color: rgb(204, 51, 0);">2. Waterfall -</span></b><b><span style="font-size: 10pt;"> This is a frequency spectrum display that shows activity in the audio pass band over the last few seconds. Received signals create color streaks which will 'fall' down the display as time progresses. Relative signal strength is indicated by the colors, which are -- weakest to strongest -- blue, green, yellow, red. Black indicates no signal. </span></b></p> <p><b><span style="font-size: 10pt;">The waterfall should be centered between the two vertical white lines. For AFSK (UHF/VHF), it should center automatically. For HF operations (FSK), adjust the radio's receive frequency to center the waterfall. Centering is critical for accurate decoding of HF packets. The strongest signal (yellow/red color streak) must lie between those two lines, as this next screen shot illustrates:</span></b></p> <p><b><span style="font-size: 10pt;"><!--[if gte vml 1]><v:shape id="_x0000_i1060" type="#_x0000_t75" alt="" style="'width:255.75pt;height:105pt'"> <v:imagedata src="file:///C:\DOCUME~1\C11AE~1.BLA\LOCALS~1\Temp\msohtml1\01\clip_image030.gif" href="http://www.kc2rlm.info/soundcardpacket/AGWImages/3tunea15.gif"> </v:shape><![endif]--><!--[if !vml]--><img src="file:///C:/DOCUME%7E1/C11AE%7E1.BLA/LOCALS%7E1/Temp/msohtml1/01/clip_image030.gif" shapes="_x0000_i1060" border="0" height="140" width="341" /><!--[endif]-->
<br /> </span></b></p> <p><b><span style="font-size: 10pt;">The screen shot below shows an HF radio that needs tuning. The yellow area showing packet activity is below the tuned frequency marked by the two vertical lines:</span></b></p> <p><b><span style="font-size: 10pt;"><!--[if gte vml 1]><v:shape id="_x0000_i1061" type="#_x0000_t75" alt="" style="'width:257.25pt;height:108pt'"> <v:imagedata src="file:///C:\DOCUME~1\C11AE~1.BLA\LOCALS~1\Temp\msohtml1\01\clip_image031.gif" href="http://www.kc2rlm.info/soundcardpacket/AGWImages/3tunea16.gif"> </v:shape><![endif]--><!--[if !vml]--><img src="file:///C:/DOCUME%7E1/C11AE%7E1.BLA/LOCALS%7E1/Temp/msohtml1/01/clip_image031.gif" shapes="_x0000_i1061" border="0" height="144" width="343" /><!--[endif]--></span></b></p> <p> </p> <p><b><span style="font-size: 10pt;">This sample below is a waterfall display showing two 1200 baud packets. The packets have black areas to their left and right of the two vertical white lines.</span></b></p> <p><!--[if gte vml 1]><v:shape id="_x0000_i1062" type="#_x0000_t75" alt="" style="'width:256.5pt;height:110.25pt'"> <v:imagedata src="file:///C:\DOCUME~1\C11AE~1.BLA\LOCALS~1\Temp\msohtml1\01\clip_image032.gif" href="http://www.kc2rlm.info/soundcardpacket/AGWImages/3tunea17.gif"> </v:shape><![endif]--><!--[if !vml]--><img src="file:///C:/DOCUME%7E1/C11AE%7E1.BLA/LOCALS%7E1/Temp/msohtml1/01/clip_image032.gif" shapes="_x0000_i1062" border="0" height="147" width="342" /><!--[endif]--></p> <p><b><span style="font-size: 10pt;">The upper packet has fair modulation and was decoded. Also, note in the black area above the packet that there are small green vertical lines. This is the result of TXDelay, i.e. a short interval of carrier with no modulation.
<br />
<br />The bottom packet has very low modulation (little color; similar to a carrier with no modulation), but the packet was still decoded. </span></b></p> <p><b><span style="font-size: 10pt;">
<br /></span><span style="color: rgb(204, 51, 0);">3. Eye </span></b><b><span style="font-size: 10pt;"> - is really a scatter diagram. The closer together the scattered points, the better the signal.
<br />
<br />
<br /></span><span style="color: rgb(204, 51, 0);">4. Frequency -</span></b><b><span style="font-size: 10pt;"> a real-time display of where signals are being heard along a frequency scale. The TWO white vertical lines are centered around the dialed frequency, and the majority of signal peaks and valleys should fall between the left line (lower tone) and the right line (upper tone). If they don't, you'll need to change the radio's dialed frequency to center the signal between the white lines.</span></b></p> <h4><span style="font-size: 10pt;">
<br />
<br /></span><span style="color: navy;">Set Volume Button</span></h4> <p><b><span style="font-size: 10pt;">Pressing this button takes you to the s<a href="http://www.kc2rlm.info/soundcardpacket/3volset.htm">ound card Volume Settings window</a> where you can adjust TX audio levels, RX audio levels, and the RX input source jack.</span></b></p> <h2> <span style="color: rgb(204, 51, 0);">Problems with Program Behavior</span></h2> <p><span style="font-size: 10pt;">1..<a href="http://www.kc2rlm.info/soundcardpacket/5probprog.htm#general">Problems with the AGWPE Program</a>
<br />2. <a href="http://www.kc2rlm.info/soundcardpacket/5probprog.htm#Clients">Linking to Client Applications</a></span>
<br /><span style="font-size: 10pt;">3. <a href="http://www.kc2rlm.info/soundcardpacket/5probprog.htm#extrapackets">Extra packets seen</a></span> </p> <p><b><span style="color: red;">Note:</span></b><b><span style="font-size: 10pt;"> Please make sure you are using the <a href="http://www.kc2rlm.info/soundcardpacket/AGWPrograms.htm">latest version of AGWPE</a> before troubleshooting problems. Your problem may have been fixed by the most recent version of AGWPE!</span></b></p> <p><b><span style="font-size: 10pt;">As you troubleshoot receive problems, remember that AGWPE provides you with a some visual aids:</span></b></p> <ul type="disc"><li class="MsoNormal" style=""><b><span style="font-size: 10pt;">If AGWPE loads successfully, you will see the AGWPE tower icon <!--[if gte vml 1]><v:shape id="_x0000_i1063" type="#_x0000_t75" alt="" style="'width:24pt;height:24pt'"> <v:imagedata src="file:///C:\DOCUME~1\C11AE~1.BLA\LOCALS~1\Temp\msohtml1\01\clip_image004.gif" href="http://www.kc2rlm.info/soundcardpacket/AGWImages/TowerIcon.gif"> </v:shape><![endif]--><!--[if !vml]--><img src="file:///C:/DOCUME%7E1/C11AE%7E1.BLA/LOCALS%7E1/Temp/msohtml1/01/clip_image004.gif" shapes="_x0000_i1063" border="0" height="32" width="32" /><!--[endif]-->at the bottom right of your screen in the Windows <span style="color: rgb(0, 153, 153);">System Tray</span>.
<br /> </span></b></li><li class="MsoNormal" style=""><b><span style="font-size: 10pt;">If a "radioport" has been successfully configured, you should see the AGWPE modem icon <!--[if gte vml 1]><v:shape id="_x0000_i1064" type="#_x0000_t75" alt="" style="'width:24pt;height:11.25pt'"> <v:imagedata src="file:///C:\DOCUME~1\C11AE~1.BLA\LOCALS~1\Temp\msohtml1\01\clip_image009.gif" href="http://www.kc2rlm.info/soundcardpacket/AGWImages/TNCnone.gif"> </v:shape><![endif]--><!--[if !vml]--><img src="file:///C:/DOCUME%7E1/C11AE%7E1.BLA/LOCALS%7E1/Temp/msohtml1/01/clip_image009.gif" shapes="_x0000_i1064" border="0" height="15" width="32" /><!--[endif]-->next to the tower icon. There will be one modem icon for each working radioport. A green pixel in the modem icon will flash once if AGWPE successfully decodes a packet. A red pixel in the modem icon will flash once if AGWPE has sent a packet to the soundcard and radio for transmission.
<br /> </span></b></li></ul> <h4>1. <a name="general">General Program Problems</a></h4> <p><b><span style="font-size: 10pt; color: red;">General Troubleshooting Hint:</span></b><b><span style="font-size: 10pt;"> Any time you have trouble with a configuration setting in AGWPE, it may be best to just start fresh: close AGWPE and delete any <span style="color: blue;">port*.ini</span> files and the <span style="color: blue;">agwpe.ini</span> in your AGWPE directory/folder. Then restart and re-configure AGWPE from the very beginning. It doesn't take much time.</span></b></p> <ul type="disc"><li class="MsoNormal" style=""><b><span style="font-size: 10pt; color: rgb(204, 51, 0);">When I try to start AGWPE, I get an error message that says "Can not find WS2_32.dll"</span></b></li></ul> <p style="margin-left: 0.5in;"><b><span style="font-size: 10pt;">Sounds like you're running Windows 95. You need the Winsock 2 Update from Microsoft. See the <a href="http://www.kc2rlm.info/soundcardpacket/4winupdate.htm">Windows update page</a> on this site for the full solution. </span></b></p> <ul type="disc"><li class="MsoNormal" style=""><b><span style="font-size: 10pt; color: navy;">I'm running Windows 98 SE. After I configure AGWPE for my sound card and restart AGWPE, I get Windows' blue crash screen saying </span></b><b><span style="font-size: 10pt; color: red;">"A fatal exception 0E has occurred at (some address) in VXD KMIXER. The current application will be terminated."
<br />
<br /> </span></b><b><span style="font-size: 10pt;">You have a problem with your sound card driver and the KMIXER.SYS, Windows' audio mixer kernel. Windows 98 used VXD drivers in its original version but then switched to WDM drivers in SE (Second Edition). I suspect there's a problem with Windows calling the incorrect driver file. You might try totally uninstalling the card and drivers from Windows and then, when it restarts, point it to the new WDM drivers. On the other hand, some users have found success, with the opposite, counter-intuitive strategy -- uninstall the newer WDM drivers and install the VXD drivers.<span style="color: red;">
<br />
<br /> </span>Warren sent me his solution that is, essentially, to install the latest drivers for his sound card:</span></b></li></ul> <p><b><span style="font-size: 10pt; color: rgb(0, 51, 204);">"Here is my solution to the Win98SE problem with the VXD and WDM issue with AGWPE. My problem was the VXD KMIXER(06) fatal error </span></b></p> <p><b><span style="font-size: 10pt; color: rgb(0, 51, 204);">My environment: Win98SE All Windows updates done Pentium 533MHz 512MB Ram Chipset Via Pro133 82C693A and 82C686A (<st1:place st="on"><st1:city st="on">Southbridge</st1:city></st1:place>). Sound is integrated on the mother board and is AC'97 v2.1 CODEC in the 82C686A <st1:city st="on"><st1:place st="on">Southbridge</st1:place></st1:city> chip. </span></b></p> <p><b><span style="font-size: 10pt; color: rgb(0, 51, 204);">When first checked, the drivers being used for the sound chip were:
<br /></span></b><b><span style="font-size: 10pt; color: rgb(51, 153, 102);">VIAaudio.sys 4.10.3104 MMDevldr 4.10.1998 </span></b></p> <p><b><span style="font-size: 10pt; color: rgb(0, 51, 204);">A visit to the VIA site gave a later driver package. The file downloaded was </span></b><b><span style="font-size: 10pt; color: rgb(51, 153, 102);">Vinyl_AudioCodec_V570a.zip </span></b></p> <p><b><span style="font-size: 10pt; color: rgb(0, 51, 204);">(This also produces another volume controls interface, called Vinyl Deck, that gives an easier volume interface than the Windows one. )</span></b></p> <p><b><span style="font-size: 10pt; color: rgb(0, 51, 204);">Even though I read the suggestion about forcing Win98SE to take the VXD driver, I decided to just let the new driver package run and install WDM as it should. This proved successful and AGWPE does not now produce the VXD error. </span></b></p> <p><b><span style="font-size: 10pt; color: rgb(0, 51, 204);">The drivers are now: Vinyl AC'97 Codec Combo Driver (WDM) 10.10.2004 </span></b></p> <p><b><span style="font-size: 10pt; color: rgb(0, 51, 204);">So it looks like a fix by using the latest sound drivers and these more modern drivers seem to take care of the use of VXD / WDM in different Win98/98SE editions."</span></b></p> <ul type="disc"><li class="MsoNormal" style=""><b><span style="font-size: 10pt; color: navy;">The AGWPE banner comes up, but then I get an error message that says:
<br /> "</span></b><b><span style="font-size: 10pt; color: red;">Your SoundCard Driver cannot Support the Wave Format</span></b><b><span style="font-size: 10pt; color: navy;">".</span></b><span style="font-size: 10pt;">
<br />
<br /> <b>One of two things maybe wrong:
<br /> </b></span></li><ul type="circle"><li class="MsoNormal" style=""><b><span style="font-size: 10pt;">Most likely AGWPE is configured to use a device other than a sound card, most commonly, a <span style="color: red;">telephone modem</span>. To fix this, go to the<span style="color: rgb(0, 153, 153);"> <a href="http://www.kc2rlm.info/soundcardpacket/2agwbasic.htm#soundcardproperties">Sound Card Modem /TNC Setup</a> </span>window, and select a sound card in the <span style="color: blue;">Sound Card Selection</span> field.
<br /> </span></b></li><li class="MsoNormal" style=""><b><span style="font-size: 10pt;">Your sound card driver really can not support the wave format. Make sure you have the most recent version of the driver for your version of Windows.
<br />
<br /> </span></b></li></ul><li class="MsoNormal" style=""><b><span style="font-size: 10pt; color: navy;">AGWPE tries to start but then a "</span></b><b><span style="font-size: 10pt; color: red;">Copyright Violation</span></b><b><span style="font-size: 10pt; color: navy;">" box appears. I click "OK", but the program then closes</span></b><b><span style="font-size: 10pt;">.
<br /> </span></b><span style="font-size: 10pt;">
<br /> <b>The <span style="color: rgb(0, 153, 153);">AGWPE.SYS</span> file is missing from your AGWPE folder. You can reinstall the entire program from the zip file or just the <span style="color: rgb(0, 153, 153);">AGWPE.SYS</span> file. (The AGWPE.SYS file has the date of the program, so don't use the AGWPE.SYS file from another version. It will display the wrong version date when you start the program.)
<br /> </b>
<br /> </span></li><li class="MsoNormal" style=""><b><span style="font-size: 10pt; color: navy;">AGWPE starts and runs but first I get a message that says:
<br /> "</span></b><b><span style="font-size: 10pt; color: red;">AGWTCPIP.SYS Not Found! TCPIP Over Radio will be IDLE!</span></b><b><span style="font-size: 10pt; color: navy;">"</span></b><span style="font-size: 10pt;">
<br />
<br /> <b>You have turned on AGWPE's special <span style="color: rgb(0, 153, 153);">"TCP/IP Over Radio" (TOR)</span> feature but have not installed the special TOR software adapter. If you really meant to use this feature, <a href="http://www.kc2rlm.info/soundcardpacket/6tor.htm">see the TOR pages</a> on this web site for information about installing the adapter. Most people do not need or use this feature. It is NOT needed for normal packet functions or to interface with your applications (applications use the <span style="color: rgb(0, 153, 153);">TCP/IP Application Interface</span> to connect to AGWPE, not <span style="color: rgb(0, 153, 153);">TCP/IP Over Radio).
<br />
<br /> </span>To turn <span style="color: rgb(0, 153, 153);">TOR</span> off and stop the message, go to the AGWPE menu (click on the AGWPE tower icon) and select <span style="color: rgb(0, 153, 153);">TCP/IP Over Radio Setup.</span> In the resulting window select "<span style="color: blue;">Thank's NO TCP/IP</span>".
<br /> </b></span></li><li class="MsoNormal" style=""><b><span style="font-size: 10pt; color: navy;">I can run AGWPE and my packet program on my laptop for about 30 (or 15 or 60) minutes and then it just crashes.
<br /> </span></b><b><span style="font-size: 10pt;">
<br /> Turn off the computer's energy saving mode.
<br /> </span></b></li><li class="MsoNormal" style=""><b><span style="font-size: 10pt; color: navy;">When I drag my mouse over AGWPE's modems icon in the system tray, a message pops up telling me how the port is configured and how many frames (packets) I have received and sent. But even when I haven't sent any frames, as time goes on, AGWPE says that I have been sending more and more frames. Is that normal?</span></b><b><span style="font-size: 10pt; color: rgb(0, 51, 204);">
<br />
<br /> </span></b><b><span style="font-size: 10pt;">It is normal. In its default mode, AGWPE calculates the "best" traffic parameters (slot/persist, resptime, etc.), every 2 minutes and these recalculated values get reported as sent frames even though nothing is actually transmitted by the radio. Don't worry. AGWPE is not keying up your radio and transmitting on its own.
<br /> </span></b></li><li class="MsoNormal" style=""><b><span style="font-size: 10pt; color: navy;">AGWPE loads but then my system just freezes. I need to power off to reboot.
<br /> </span></b><b><span style="font-size: 10pt;">
<br /> One user said that new sound card drivers fixed the problem.
<br />
<br /> </span></b></li><li class="MsoNormal" style=""><b><span style="font-size: 10pt; color: navy;">AGWPE starts but then gives a message that "</span></b><b><span style="font-size: 10pt; color: red;">Packet Engine Pro Shuts Down Abnormaly, It Is Strong Recommended to restart your Computer</span></b><b><span style="font-size: 10pt; color: navy;">".
<br /> </span></b><span style="font-size: 10pt; color: navy;">or<b>
<br /> AGWPE is behaving very strangely, particularly my radioport configuration.
<br /> </b>or<b>
<br /> AGWPE won't start and locks my system.
<br /> </b></span><b><span style="font-size: 10pt;">
<br /> In the AGWPE folder, delete the AGWPE.ini file and all port?.ini (port0.ini, port1.ini, etc.) files and then restart and reconfigure AGWPE.
<br />
<br /> The problem may have developed when you configured a radioport to use a COM or LPT port that was already claimed by another program or device; or the TNC was not plugged into the COM or LPT port; or you may have tried to delete and add a port without restarting the program after deleting one port and trying to add another.
<br /> </span></b></li><li class="MsoNormal" style=""><b><span style="font-size: 10pt; color: navy;">I'm running Windows 95 and when I start AGWPE, the AGWPE tower icon appears in the Task Bar *not* the System Tray. If I right click on the icon, I get the usual AGWPE menu, but "Setup Interfaces" does nothing; the popup menu just closes. I can't seem to make AGWPE do anything.
<br /> </span></b><b><span style="font-size: 10pt;"> or<span style="color: navy;">
<br /> I fill in the new port information, close the program and restart it, but the port shows "IDLE" and I can't open the</span><span style="color: rgb(204, 51, 0);"> </span><span style="color: rgb(0, 153, 153);">Properties </span><span style="color: navy;">window for that port by clicking on</span><span style="color: rgb(204, 51, 0);"> </span><span style="color: blue;">OK</span><span style="color: rgb(204, 51, 0);">.
<br />
<br /> </span>You need to update the Windows "common controls" file, COMCTL32.DLL file. See the <a href="http://www.kc2rlm.info/soundcardpacket/4winupdate.htm">Windows update page</a> on this site for the full solution.
<br /> </span></b></li><li class="MsoNormal" style="margin-bottom: 12pt;"><b><span style="font-size: 10pt; color: navy;">AGWPE closed and the Packet Engine icon</span><span style="color: navy;"> </span></b><b><span style="font-size: 10pt; color: navy;"><!--[if gte vml 1]><v:shape id="_x0000_i1065" type="#_x0000_t75" alt="" style="'width:24pt;height:24pt'"> <v:imagedata src="file:///C:\DOCUME~1\C11AE~1.BLA\LOCALS~1\Temp\msohtml1\01\clip_image004.gif" href="http://www.kc2rlm.info/soundcardpacket/AGWImages/TowerIcon.gif"> </v:shape><![endif]--><!--[if !vml]--><img src="file:///C:/DOCUME%7E1/C11AE%7E1.BLA/LOCALS%7E1/Temp/msohtml1/01/clip_image004.gif" shapes="_x0000_i1065" border="0" height="32" width="32" /><!--[endif]-->disappeared, but the modem icon <!--[if gte vml 1]><v:shape id="_x0000_i1066" type="#_x0000_t75" alt="" style="'width:20.25pt;"> <v:imagedata src="file:///C:\DOCUME~1\C11AE~1.BLA\LOCALS~1\Temp\msohtml1\01\clip_image033.gif" href="http://www.kc2rlm.info/soundcardpacket/AGWImages/TNC.gif"> </v:shape><![endif]--><!--[if !vml]--><img src="file:///C:/DOCUME%7E1/C11AE%7E1.BLA/LOCALS%7E1/Temp/msohtml1/01/clip_image033.gif" shapes="_x0000_i1066" border="0" height="18" width="27" /><!--[endif]-->remained on the System Tray!
<br /> </span></b><b><span style="font-size: 10pt;">
<br /> This may happen if AGWPE is closed down unexpectedly. Usually restarting AGWPE will correct it, although a reboot may be necessary. If AGWPE fails to start (you may get a "<span style="color: rgb(0, 153, 153);">Fatal Exception Error</span>" message), go to the AGWPE folder/directory and delete all files ending in <span style="color: red;">.ini</span>; then restart and reconfigure AGWPE.</span></b></li><li class="MsoNormal" style=""><b><span style="font-size: 10pt; color: navy;">Modem Icon Never Appears</span></b><b><span style="font-size: 10pt;">:<span style="color: red;"> </span>The modem icon <!--[if gte vml 1]><v:shape id="_x0000_i1067" type="#_x0000_t75" alt="" style="'width:20.25pt;"> <v:imagedata src="file:///C:\DOCUME~1\C11AE~1.BLA\LOCALS~1\Temp\msohtml1\01\clip_image033.gif" href="http://www.kc2rlm.info/soundcardpacket/AGWImages/TNC.gif"> </v:shape><![endif]--><!--[if !vml]--><img src="file:///C:/DOCUME%7E1/C11AE%7E1.BLA/LOCALS%7E1/Temp/msohtml1/01/clip_image033.gif" shapes="_x0000_i1067" border="0" height="18" width="27" /><!--[endif]-->won' t appear until you configure an AGWPE port and then closed and restarted AGWPE. If the modem icon <!--[if gte vml 1]><v:shape id="_x0000_i1068" type="#_x0000_t75" alt="" style="'width:20.25pt;"> <v:imagedata src="file:///C:\DOCUME~1\C11AE~1.BLA\LOCALS~1\Temp\msohtml1\01\clip_image033.gif" href="http://www.kc2rlm.info/soundcardpacket/AGWImages/TNC.gif"> </v:shape><![endif]--><!--[if !vml]--><img src="file:///C:/DOCUME%7E1/C11AE%7E1.BLA/LOCALS%7E1/Temp/msohtml1/01/clip_image033.gif" shapes="_x0000_i1068" border="0" height="18" width="27" /><!--[endif]--> doesn't appear then:
<br /> </span></b></li><ul type="circle"><li class="MsoNormal" style=""><b><span style="font-size: 10pt;">Double check the properties for the AGWPE port to make sure you have done it correctly. Use the <a href="http://www.kc2rlm.info/soundcardpacket/2agwbasic.htm#portsettings">Port Settings</a> information on this site for guidance.
<br /> </span></b></li><li class="MsoNormal" style=""><b><span style="font-size: 10pt;">Look for possible port conflicts with the PTT port you have selected. See next section:</span></b></li></ul></ul> <table class="MsoNormalTable" style="border: medium none ; border-collapse: collapse;" border="1" cellpadding="0" cellspacing="0"> <tbody><tr style=""> <td style="padding: 4.5pt;"> <p class="MsoNormal"><a name="portconflict"><b><span style="color: rgb(204, 51, 0);">Port Conflicts</span></b></a></p> <p><b><span style="font-size: 10pt;">It's possible that some other device is affecting the COM/LPT port you have chosen for PTT control. For example, one user forgot that he had an unused phycial adapter "installed" in Windows that was conflicting with the PTT port. Another user reported a conflict with the Palm HotSync Manager, which loads on startup and puts the COM RTS pin high; Windows didn't report that the COM port was being used by the Palm device driver, but it was. Another user had both the COM port and an infrared port assigned to the same IRQ. Another user suggested that, if your XP machine is running an NVIDIA graphics adapter, some of its drivers are reported to tie up COM1 for no reason -- so disable Nview 2.0.
<br />
<br /> It may be difficult to identify port conflicts, since AGWPE may start and run despite the conflict, i.e. no error message. Conflicts may arise either from a device, such as a printer, or from a program that uses the same port.</span></b></p> <p><b><span style="font-size: 10pt;">Try this first: temporarily force AGWPE to a port where there CAN'T be a conflict with another program. Reset the <span style="color: blue;">Serial or <st1:place st="on"><st1:placename st="on">LPT</st1:placename> <st1:placetype st="on">Port</st1:placetype></st1:place></span> in <a href="http://www.kc2rlm.info/soundcardpacket/2agwget.htm#Port%20Settings">AGWPE's properties window</a> to a <span style="color: rgb(204, 51, 0);">non-existent</span> <span style="color: blue;">parallel port</span>, perhaps LPT 3 (scroll down past all the COM options to the LPT options).</span></b></p> <p><b><span style="font-size: 10pt;">If AGWPE now receives packets and your other program now works, then you know you did indeed have a port conflict. Fix the conflict (see below) and then change the AGWPE PTT port settings back to a real port, i.e. not the non-existent one.</span></b></p> <p><b><span style="font-size: 10pt;">To search for a device that might be causing the problem, first go to the <span style="color: rgb(0, 153, 153);">Start menu </span>and then<span style="color: rgb(0, 153, 153);"> Settings: Control Panel: System. </span>On the<span style="color: rgb(0, 153, 153);"> "Device Manager </span>tab, select "<span style="color: blue;">View devices by Connection</span>" and double click on "<span style="color: blue;">Computer</span>". This should tell you which devices are using each IRQ. Look for a conflict with your chosen AGWPE PTT physical port (COMx, LPTx) and some other device.
<br />
<br /> If there is a device conflict, you'll need to either reset the port used by the conflicting device (could be hard) or tell AGWPE to use a different PTT port (might be easer). To change the port AGWPE uses, move the PTT cable to a different physical COM or LPT port. Then make the corresponding change in the <a href="http://www.kc2rlm.info/soundcardpacket/2agwbasic.htm#portsettings">Port Properties</a> in AGWPE.
<br />
<br /> If only one device is assigned to each COMx and LPTx port "serial port IRQ", then there is no conflicting <i>device</i>, so there is probably a conflicting <i>program</i> which is using the port. Either:</span></b></p> <ul type="disc"><li class="MsoNormal" style=""><b><span style="font-size: 10pt;">reconfigure the conflicting program to use another port</span></b></li><li class="MsoNormal" style=""><b><span style="font-size: 10pt;">just close the offending program before working with AGWPE</span></b></li><li class="MsoNormal" style=""><b><span style="font-size: 10pt;">change the PTT port in AGWPE (see paragraph above).</span></b></li></ul> </td> </tr> </tbody></table> <h4><span style="font-size: 10pt;">
<br /></span>2. <a name="Clients">Linking to Client Applications</a></h4> <ul type="disc"><li class="MsoNormal" style=""><b><span style="font-size: 10pt; color: navy;">I am having trouble configuring my client application to link to AGWPE.</span></b><b><span style="font-size: 10pt;">
<br />
<br /> There may be instructions in the <span style="color: rgb(0, 153, 153);">Help</span> section of your client application; or you can try the <span style="color: navy;"><a href="http://www.kc2rlm.info/soundcardpacket/7compat.htm">Application Setup</a></span> page on this website.
<br />
<br /> If you're having trouble getting a particular application to work with AGWPE, first make sure AGWPE works with <span style="color: rgb(0, 153, 153);"><a href="http://www.kc2rlm.info/soundcardpacket/AGWPrograms.htm">AGW Terminal Program.</a></span> If AGWTerm won't work with AGWPE, then you have a problem with AGWPE that needs to be resolved first.</span></b><span style="font-size: 10pt;">
<br /> </span></li><li class="MsoNormal" style=""><b><span style="font-size: 10pt; color: navy;">I see the little</span></b><b><span style="font-size: 10pt; color: rgb(204, 51, 0);"> </span></b><b><span style="font-size: 10pt; color: rgb(51, 153, 102);">green </span></b><b><span style="font-size: 10pt; color: navy;">pixel flashing on the TNC icon <!--[if gte vml 1]><v:shape id="_x0000_i1069" type="#_x0000_t75" alt="" style="'width:24pt;height:11.25pt'"> <v:imagedata src="file:///C:\DOCUME~1\C11AE~1.BLA\LOCALS~1\Temp\msohtml1\01\clip_image034.png" href="http://www.kc2rlm.info/soundcardpacket/AGWImages/greenblink.gif"> </v:shape><![endif]--><!--[if !vml]--><img src="file:///C:/DOCUME%7E1/C11AE%7E1.BLA/LOCALS%7E1/Temp/msohtml1/01/clip_image035.jpg" shapes="_x0000_i1069" border="0" height="15" width="32" /><!--[endif]--> so it appears AGWPE is receiving packets, but the packets don't seem to be getting from AGWPE to my packet program; my program isn't showing any packet activity.
<br /> or
<br /> When I try to run a client application, I get an error message from the client indicating the IP connection was refused.
<br />
<br /> </span></b><b><span style="font-size: 10pt;">Check for these problems:<span style="color: navy;">
<br /> </span></span></b></li><ul type="circle"><li class="MsoNormal" style=""><b><span style="font-size: 10pt;">Make sure AGWPE's <span style="color: rgb(0, 153, 153);">TCP/IP Application Interface</span> is active: from the AGWPE menu select <span style="color: rgb(51, 204, 204);">Setup Interfaces</span> . On the <span style="color: rgb(0, 153, 153);">Winsock & HTTP Interface Setup screen; Winsock Interface tab</span>, enable the <span style="color: blue;">Winsock TCP/IP Application Interface </span>with a checkmark<span style="color: blue;">.</span> Also make sure the <span style="color: rgb(0, 153, 153);">TCP</span> field is set <span style="color: blue;">8000</span>.
<br /> </span></b></li><li class="MsoNormal" style=""><b><span style="font-size: 10pt;">Any application linking to AGWPE with the TCP/IP Application Interface should have a corresponding field to specify AGWPE's TCP port number (8000, by default); see the <span style="color: navy;"><a href="http://www.kc2rlm.info/soundcardpacket/7compat.htm">Application Setup</a></span> page for advice about selected programs. The application should also have a field to specify the IP Address of the computer where AGWPE is running. That address will be "127.0.0.1" or "localhost" if AGWPE is on the same computer as the application. Read the application's <span style="color: rgb(0, 153, 153);">Help</span> section or see <a href="http://www.kc2rlm.info/soundcardpacket/6network.htm">AGWPE on a Network</a> for advice when AGWPE is on a different computer.
<br /> </span></b></li><li class="MsoNormal" style=""><b><span style="font-size: 10pt;">Make sure the application is listening to the correct AGWPE radio ports. The application may be linked to AGWPE but not linked to all of AGWPE's radio ports. For example, some programs, such as UI-View, allow you to block access to specific AGWPE radio ports (UI-View calls it "masking" ). Read the application's <span style="color: rgb(0, 153, 153);">Help</span> section or see the <span style="color: navy;"><a href="http://www.kc2rlm.info/soundcardpacket/7compat.htm">Application Setup</a></span> page for advice about selected programs.
<br /> </span></b></li><li class="MsoNormal" style=""><b><span style="font-size: 10pt;">Make sure the TCP/IP Protocol is installed on your computer. If you use the internet successfully, then it is. If you don't have either the Window's Dialup adapter or a network card installed on your computer, then the protocol may not be installed. To correct this, just create a Dialup connection (see Windows' <span style="color: rgb(0, 153, 153);">Help</span> for advice; you can use a dummy telephone number for the connection).
<br />
<br /> If you still have a problem, make sure the "Internet Protocol (TCP/IP)" is installed for the Dialup connection or the network adapter. Normally it is installed by default and active, but it may have been deleted somehow (see the <a href="http://www.kc2rlm.info/soundcardpacket/4wintcp.htm">Windows: Enabling the TCP/IP Protocol page</a> for advice).
<br /> </span></b></li><li class="MsoNormal" style=""><b><span style="font-size: 10pt; color: red;">If you have a firewall program and/or router running</span></b><b><span style="font-size: 10pt;">, turn off the firewall temporarily to see if this fixes the problem. If it does, configure the firewall and/or router so that AGWPE can communicate with other programs via AGWPE's TCP/IP Application Interface port (default is 8000).
<br /> </span></b></li><li class="MsoNormal" style=""><b><span style="font-size: 10pt;">Try changing the default <st1:place st="on"><st1:placename st="on">TCP</st1:placename> <st1:placetype st="on">Port</st1:placetype></st1:place> from 8000 to some other number, say 8100. Make the change in both AGWPE and in your client program.</span></b><span style="font-size: 10pt;">
<br /> </span></li></ul><li class="MsoNormal" style=""><b><span style="font-size: 10pt; color: navy;">My packet program suddenly closed and I got this error message from Windows:</span></b><b><span style="font-size: 10pt; color: rgb(204, 51, 0);">
<br />
<br /> </span></b><b><span style="font-size: 10pt; color: rgb(0, 51, 204);">(The Application) caused an invalid page fault in module WINMM.DLL</span></b></li></ul> <p style="margin-left: 0.5in;"><b><span style="font-size: 10pt;">You probably have a Windows sound scheme in effect and there was a conflict over use of the sound card. To prevent this from happening, set the Windows' <span style="color: rgb(0, 153, 153);">Sound scheme</span> to <span style="color: rgb(0, 51, 204);">No Sounds</span>. See the <a href="http://www.kc2rlm.info/soundcardpacket/3voladd.htm#nosounds">Window Sound Settings page</a> on this site for further advice.
<br />
<br /> </span></b></p> <ul type="disc"><li class="MsoNormal" style=""><b><span style="font-size: 10pt; color: navy;">I seem to have the AGWPE program working fine. My problem is when I run certain packet programs, such as RXClust or AGWTerm, a box opens saying:</span></b></li></ul> <table class="MsoNormalTable" style="background: silver none repeat scroll 0% 0%; -moz-background-clip: -moz-initial; -moz-background-origin: -moz-initial; -moz-background-inline-policy: -moz-initial;" border="1" cellpadding="0"> <tbody><tr style=""> <td style="padding: 2.25pt;"> <p class="MsoNormal"><b><span style="font-size: 10pt;">Object Windows Exception</span></b> </p> <p><b><span style="font-size: 10pt;">Failure in common control DLL</span></b></p> <p><b><span style="font-size: 10pt;">OK to resume? YES / NO</span></b></p> </td> </tr> </tbody></table> <p><b><span style="font-size: 10pt;">This is a Windows 95, 98, and ME problem. Do an online search for </span><span style="color: rgb(0, 51, 204);">comctl32.dll</span></b> <b><span style="font-size: 10pt;">to find a download patch for your version of windows.</span></b>
<br /> </p> <ul type="disc"><li class="MsoNormal" style=""><b><span style="font-size: 10pt; color: navy;">I have two applications sharing an AGWPE sound card radio port. But Application A is not seeing packets sent by Application B and vice versa.</span></b></li></ul> <p style="margin-left: 0.5in;"><b><span style="font-size: 10pt;">It is a feature of AGWPE that the received frames it sends to an application do not include frames transmitted by other applications using the same instance of AGWPE. So if you have this:</span></b></p> <p style="margin-left: 0.5in;"><b><span style="font-size: 10pt; font-family: Century; color: rgb(0, 51, 204);">App A --------|
<br /> |
<br /> AGWPE -------- radio(s) etc.
<br /> |
<br />App B --------|</span></b></p> <p style="margin-left: 0.5in;"><b><span style="font-size: 10pt;">Then, using KISS frames, App A will not see the original frames transmitted by App B.
<br />
<br />If you do want App A to see App B's transmission, then a work-round is to configure a loop-back port in AGWPE. Then transmit the beacons from your application(s) to the RF radioport <span style="color: red;">and</span> to the loop-back port, and configure your application(s) to "listen" on both the RF radioport and the loop-back port so they can hear what the other program asked AGWPE to send.
<br /> </span></b> </p> <h4><a name="extrapackets">3. Extra Packets Seen</a></h4> <ul type="disc"><li class="MsoNormal" style=""><b><span style="font-size: 10pt;">If your packet application displays duplicates of every received packet, reasons can be:</span></b></li><ul type="circle"><li class="MsoNormal" style=""><b><span style="font-size: 10pt;">the second sound card radioport is active in AGWPE even though it is not being used. To correct this, select <st1:placename st="on"><span style="color: blue;">Single</span></st1:placename><span style="color: blue;"> <st1:placetype st="on">Port</st1:placetype></span> (not <st1:place st="on"><st1:placename st="on">Dual</st1:placename> <st1:placetype st="on">Port</st1:placetype></st1:place>) on the <a href="http://www.kc2rlm.info/soundcardpacket/2agwbasic.htm#portsettings">Properties screen</a></span></b></li><li class="MsoNormal" style=""><b><span style="font-size: 10pt;">you are using a mono plug instead of a stereo plug for the LINE IN jack
<br /> </span></b></li></ul><li class="MsoNormal" style=""><b><span style="font-size: 10pt;">If your packet application displays packets that are from another frequency:</span></b></li><ul type="circle"><li class="MsoNormal" style=""><b><span style="font-size: 10pt;">you are probably running two radio ports from the sound card (left and right channels) and audio from one radio port is being heard on the other port. The reason for this is not clear. The best known solution is to reduce the RX audio input on each radioport to the minimum needed to decode packets using the <a href="http://www.kc2rlm.info/soundcardpacket/3volset.htm#AGWPEVolSet">volume control settings</a>.</span></b></li></ul></ul> <p><b><span style="font-size: 10pt;">If your problem is not resolved by the problem solving pages on this website, join the AGWPE Yahoo Group to ask a question or search the archives for previous postings that may relate to your problem</span></b></p> <h2><span style="color: rgb(204, 51, 0);">Problems with Receiving</span></h2> <p><b><span style="font-size: 10pt;">As you troubleshoot receive problems, remember that AGWPE provides you with a some visual aids:</span></b></p> <ul type="disc"><li class="MsoNormal" style=""><b><span style="font-size: 10pt;">The <span style="color: navy;"><a href="http://www.kc2rlm.info/soundcardpacket/3voltuneaid.htm">Sound Card Tuning Aid</a></span><a href="http://www.kc2rlm.info/soundcardpacket/3voltuneaid.htm"> screen</a> is accessible from the AGWPE menu. It can be used to "see" the quality of received signals and, for HF packet particularly, help in tuning the radio to the correct frequency. Go to the <span style="color: navy;"><a href="http://www.kc2rlm.info/soundcardpacket/3voltuneaid.htm">Tuning Aid</a></span><a href="http://www.kc2rlm.info/soundcardpacket/3voltuneaid.htm"> page</a> to see examples of how good and packet signals should look.
<br /> </span></b></li><li class="MsoNormal" style=""><b><span style="font-size: 10pt;"> If AGWPE successfully decodes a packet on a radioport, then the <span style="color: green;">green</span> light on that radioport's modem icon will flash once <!--[if gte vml 1]><v:shape id="_x0000_i1070" type="#_x0000_t75" alt="" style="'width:24pt;height:11.25pt'"> <v:imagedata src="file:///C:\DOCUME~1\C11AE~1.BLA\LOCALS~1\Temp\msohtml1\01\clip_image034.png" href="http://www.kc2rlm.info/soundcardpacket/AGWImages/greenblink.gif"> </v:shape><![endif]--><!--[if !vml]--><img src="file:///C:/DOCUME%7E1/C11AE%7E1.BLA/LOCALS%7E1/Temp/msohtml1/01/clip_image035.jpg" shapes="_x0000_i1070" border="0" height="15" width="32" /><!--[endif]-->.</span></b></li></ul> <p><b><span style="color: red;">Note:</span></b><b><span style="font-size: 10pt;"> Please make sure you are using the <a href="http://www.kc2rlm.info/soundcardpacket/AGWPrograms.htm">latest version of AGWPE</a> before troubleshooting problems. Your problem may have been fixed in the most recent version of AGWPE!</span></b></p> <p><span style="font-size: 10pt;">1. <a href="http://www.kc2rlm.info/soundcardpacket/5probrx.htm#NoActivity">No Sine Wave in Oscilloscope</a>
<br />2. <a href="http://www.kc2rlm.info/soundcardpacket/5probrx.htm#NoDecode">Oscilloscope Activity But No Decoding</a></span></p> <div class="MsoNormal" style="text-align: center;" align="center"> <hr align="center" size="2" width="100%"> </div> <h3><span style="color: rgb(0, 0, 153);">1. <a name="NoActivity">No Sine Wave in Oscilloscope </a></span><span style=""></span></h3> <h3><span style="font-size: 10pt; color: black;">Tune to a busy packet channel and select the Sine Wave oscilloscope mode in the </span><span style="font-size: 10pt; color: navy;"><a href="http://www.kc2rlm.info/soundcardpacket/3voltuneaid.htm">Sound Card Tuning Aid</a></span><span style="font-size: 10pt; color: black;">. If you do not see sine wave activity, look for a reason at one of five places along the RX audio path:</span></h3> <ul type="disc"><li class="MsoNormal" style=""><a href="http://www.kc2rlm.info/soundcardpacket/5probrx.htm#RXradio"><span style="font-size: 10pt;">a</span></a><span style="font-size: 10pt;"><a href="http://www.kc2rlm.info/soundcardpacket/5probrx.htm#RXradio">. Radio/antenna</a></span></li><li class="MsoNormal" style=""><a href="http://www.kc2rlm.info/soundcardpacket/5probrx.htm#RXportset"><span style="font-size: 10pt;">b</span></a><span style="font-size: 10pt;"><a href="http://www.kc2rlm.info/soundcardpacket/5probrx.htm#RXportset">. AGWPE's radioport settings</a></span></li><li class="MsoNormal" style=""><a href="http://www.kc2rlm.info/soundcardpacket/5probrx.htm#RXVolCtrl"><span style="font-size: 10pt;">c</span></a><span style="font-size: 10pt;"><a href="http://www.kc2rlm.info/soundcardpacket/5probrx.htm#RXVolCtrl">. Volume Control settings</a></span></li><li class="MsoNormal" style=""><span style="font-size: 10pt;"><a href="http://www.kc2rlm.info/soundcardpacket/5probrx.htm#RXcable">d. RX audio cable</a></span></li><li class="MsoNormal" style=""><span style="font-size: 10pt;"><a href="http://www.kc2rlm.info/soundcardpacket/5probrx.htm#RXcard">e. Sound card or driver</a></span></li></ul> <p><b><span style="font-size: 10pt; color: rgb(204, 51, 0);">a. <a name="RXradio">Radio/antenna</a></span></b><span style=""></span></p> <p><b><span style="font-size: 10pt;">First confirm that audio signals -- preferably packets! -- are are being received at the radio. Disconnect the sound card interface temporarily and see if you can hear packets from the radio's speaker and/or see the radio's 'S' bars or the 'Busy" indicator light up.</span></b></p> <ul type="disc"><li class="MsoNormal" style=""><b><span style="font-size: 10pt;">If you don't see or hear packet activity:</span></b></li><ul type="circle"><li class="MsoNormal" style=""><b><span style="font-size: 10pt;">is the squelch too high? Since AGWPE prefers no squelch for <span style="color: maroon;">transmitting</span>, it's best to leave the squelch off (even though AGWPE will still <span style="color: maroon;">receive</span> with the squelch on, providing the squelch is not set too high). </span></b></li><li class="MsoNormal" style=""><b><span style="font-size: 10pt;">is tone squelch (CTCSS and DTSS) turned off? </span></b></li><li class="MsoNormal" style=""><b><span style="font-size: 10pt;">if dual VFOs, is the correct VFO/band selected? </span></b></li><li class="MsoNormal" style=""><b><span style="font-size: 10pt;">is the antenna connected? </span></b></li><li class="MsoNormal" style=""><b><span style="font-size: 10pt;">is the radio tuned to the right frequency? </span></b></li><li class="MsoNormal" style=""><b><span style="font-size: 10pt;">is the mode set for FM and not accidentally in CW, SSB or another mode?</span></b></li><li class="MsoNormal" style=""><b><span style="font-size: 10pt;">can you hear packets by using a different antenna (more gain)? or by moving the antenna to another location (higher, away from possible EMI interference)?</span></b></li><li class="MsoNormal" style=""><b><span style="font-size: 10pt;">can you hear packets using a different radio with a different antenna? with a different radio but the same antenna?</span></b></li></ul><li class="MsoNormal" style=""><b><span style="font-size: 10pt;">If you can't hear packets from the radio's speaker (internal or external):</span></b></li><ul type="circle"><li class="MsoNormal" style=""><b><span style="font-size: 10pt;">Is the speaker volume knob set too low? Low speaker volume would only affect sound card receiving if your interface's RX cable connects to the radio's external speaker or microphone jack, not a data jack.</span></b></li><li class="MsoNormal" style=""><b><span style="font-size: 10pt;">If your interface's RX audio connects to the radio's external speaker jack, is that radio jack known to work with speakers? Plug in a different speaker or use a meter to test the jack.</span></b></li></ul></ul> <p><b><span style="font-size: 10pt; color: rgb(204, 51, 0);">b. R<a name="RXportset">adioport settings</a></span></b><span style=""></span></p> <p><b><span style="font-size: 10pt;">Check the following in the <a href="http://www.kc2rlm.info/soundcardpacket/2agwbasic.htm#portsettings">Properties settings</a> for the sound card:</span></b></p> <ul type="disc"><li class="MsoNormal" style=""><b><span style="font-size: 10pt;">Make sure you have selected the correct sound card device
<br /> </span></b></li><li class="MsoNormal" style=""><b><span style="font-size: 10pt;">Make sure you have selected the correct packet baud rate for the radioport channel</span></b></li></ul> <p><b><span style="font-size: 10pt; color: rgb(204, 51, 0);">c. <a name="RXVolCtrl">Volume Control settings </a></span></b><span style=""></span></p> <p><b><span style="font-size: 10pt;">Use the <a href="http://www.kc2rlm.info/soundcardpacket/3volset.htm#rxaudioset">Volume Control screen</a> to check your sound card settings:</span></b></p> <p style="margin-left: 0.5in; text-indent: -0.25in;"><!--[if !supportLists]--><span style="font-size: 10pt; font-family: Symbol;"><span style="">·<span style="font-family: "Times New Roman"; font-style: normal; font-variant: normal; font-weight: normal; font-size: 7pt; line-height: normal; font-size-adjust: none; font-stretch: normal;"> </span></span></span><!--[endif]--><b><span style="font-size: 10pt;">If you happen to have more than one sound card (i.e. mixer device), make sure you are working with <span style="color: rgb(204, 51, 0);">Recording</span> settings for the <span style="color: rgb(204, 51, 0);">correct sound card</span>. (Program Bug: if you have more than one sound card, AGWPE's Volume Control Screen can be used to set the first card but not a second card. To control the second card, you will need to use the <a href="http://www.kc2rlm.info/soundcardpacket/3volset.htm#windowsVolSet">Windows Volume Control Program</a>.)
<br /> </span></b> </p> <p style="margin-left: 0.5in; text-indent: -0.25in;"><!--[if !supportLists]--><span style="font-size: 10pt; font-family: Symbol;"><span style="">·<span style="font-family: "Times New Roman"; font-style: normal; font-variant: normal; font-weight: normal; font-size: 7pt; line-height: normal; font-size-adjust: none; font-stretch: normal;"> </span></span></span><!--[endif]--><b><span style="font-size: 10pt;">Make sure you are working with the Volume Control <span style="color: blue;">Recording</span> settings, not the <span style="color: blue;">Playback</span> settings.
<br /> </span></b> </p> <p style="margin-left: 0.5in; text-indent: -0.25in;"><!--[if !supportLists]--><span style="font-size: 10pt; font-family: Symbol;"><span style="">·<span style="font-family: "Times New Roman"; font-style: normal; font-variant: normal; font-weight: normal; font-size: 7pt; line-height: normal; font-size-adjust: none; font-stretch: normal;"> </span></span></span><!--[endif]--><b><span style="font-size: 10pt;">Make sure you have selected the correct input jack -- LINE IN or MIC -- where your RX interface cable is attached.
<br /> </span></b> </p> <p style="margin-left: 0.5in; text-indent: -0.25in;"><!--[if !supportLists]--><span style="font-size: 10pt; font-family: Symbol;"><span style="">·<span style="font-family: "Times New Roman"; font-style: normal; font-variant: normal; font-weight: normal; font-size: 7pt; line-height: normal; font-size-adjust: none; font-stretch: normal;"> </span></span></span><!--[endif]--><b><span style="font-size: 10pt;">Make sure the vertical volume sliders for the selected input jack is not at or near the bottom (about 1/3 up is fine). If you see Balance sliders, make sure they are centered.
<br /> </span></b> </p> <p style="margin-left: 0.5in; text-indent: -0.25in;"><!--[if !supportLists]--><span style="font-size: 10pt; font-family: Symbol;"><span style="">·<span style="font-family: "Times New Roman"; font-style: normal; font-variant: normal; font-weight: normal; font-size: 7pt; line-height: normal; font-size-adjust: none; font-stretch: normal;"> </span></span></span><!--[endif]--><b><span style="font-size: 10pt;">If there are still no signals, try selecting the other input source -- <span style="color: blue;">Microphone</span> or <span style="color: blue;">Line In</span>. You may have the plug in the wrong jack. If this was the problem, move the plug back to the correct jack and reset the input source.</span></b> </p> <p><b><span style="font-size: 10pt; color: rgb(204, 51, 0);">d. <a name="RXcable">RX audio cable</a></span></b><span style=""></span></p> <p><b><span style="font-size: 10pt;">See the <a href="http://www.kc2rlm.info/soundcardpacket/1cablerx.htm">RX audio cable page</a> for wiring schematics and other hints.</span></b></p> <ul type="disc"><li class="MsoNormal" style=""><b><span style="font-size: 10pt;">Is the RX cable plugged in completely at the sound card jack? Make sure you haven't used the wrong sound card jack or haven't confused the RX cable with the TX or PTT cable. (Hint: put labels on the ends of all cables.)
<br /> If you are using two sound cards, is the RX cable plugged into the right one?
<br /> </span></b></li><li class="MsoNormal" style=""><b><span style="font-size: 10pt;">Are you using a stereo jack at the sound card plug? You should use a stereo plug for most sound cards.
<br /> </span></b></li><li class="MsoNormal" style=""><b><span style="font-size: 10pt;">You can not interface two radios to the sound card using the microphone jack. The Microphone jack on sound cards is not stereo capable, so you will probably only receive audio from the port 1 (left channel) radio. Use the LINE IN jack instead (<a href="http://www.kc2rlm.info/soundcardpacket/1cablerx.htm">see Rx audio page</a>).
<br /> </span></b></li></ul> <ul type="disc"><li class="MsoNormal" style=""><b><span style="font-size: 10pt;">Test the cable: </span></b></li><ul type="circle"><li class="MsoNormal" style=""><b><span style="font-size: 10pt;">Unplug it from the sound card jack and plugging it into a speaker (if the speaker has a plug and not a jack, use clips leads or an in-line coupler to join the two plugs). If you hear RX audio in the speaker, the RX cable is OK, or</span></b></li><li class="MsoNormal" style=""><b><span style="font-size: 10pt;"> Use a multi-meter: </span></b></li><ul type="square"><li class="MsoNormal" style=""><b><span style="font-size: 10pt;">test for continuity and short circuits. Check your solder connections if you find a problem.</span></b></li><li class="MsoNormal" style=""><b><span style="font-size: 10pt;">Is the RX audio line wired to the tip of the stereo plug? The ring of the stereo plug should be unwired, unless you are interfacing to two radios. The sleeve should be wired to the sound card ground.</span></b></li></ul><li class="MsoNormal" style=""><b><span style="font-size: 10pt;">Is the RX line securely soldered to the correct pin in the radio plug? </span></b></li><li class="MsoNormal" style=""><b><span style="font-size: 10pt;">If the RX cable has an in-line isolation transformer, make sure it is a 1:1 transformer, unless you are using the radio's external speaker for RX audio. If you are using the external speaker, then you should be using a 1000:8 transformer and the 1000 Ohm primary coil of the transformer should be wired to the sound card side, not the radio side.
<br /> </span></b></li></ul><li class="MsoNormal" style=""><b><span style="font-size: 10pt;">Try using another cable without a transformer. </span></b></li></ul> <p><b><span style="font-size: 10pt; color: rgb(204, 51, 0);">e. S<a name="RXcard">ound card or driver</a></span></b><span style=""></span></p> <ul type="disc"><li class="MsoNormal" style=""><b><span style="font-size: 10pt;">Does the sound card work with other Windows' sound generating programs? If not, in the Windows <span style="color: rgb(0, 153, 153);">Control Panel</span> under <span style="color: rgb(0, 153, 153);">Sounds/Multimedia</span>, make sure the sound card is installed and there are no conflicts with other devices.
<br /> </span></b></li><li class="MsoNormal" style=""><b><span style="font-size: 10pt;">Sound card suddenly stops working after a few minutes and always about the same number of minutes: This probably a power management issue; your computer or laptop is going into power saving mode and is turning off the sound card.
<br /> </span></b></li><li class="MsoNormal" style=""><b><span style="font-size: 10pt;">Driver: Make sure you have the latest driver for your version of Windows. You can the latest version from the sound card/chipset manufacturer's website (better source than the computer manufacturer).
<br /> </span></b></li><li class="MsoNormal" style=""><b><span style="font-size: 10pt;">Card: <span style="color: red;">Some cards may not work with AGWPE </span>even with the correct driver. (Read the section on <a href="http://www.kc2rlm.info/soundcardpacket/soundcards.htm">Compatible Sound Cards</a> on the <span style="color: rgb(0, 153, 153);">More About AGWPE</span> page on this site.)
<br />
<br /> If the problem appears to be your sound card, consider replacing the card or adding another. New cards are fairly inexpensive or you may find a "used" sound card at a hamfest/computer show or in a discarded computer. PCMCIA and USB sound cards are also available. A second sound card dedicated only to ham programs may actually be very useful. Your first card then be used for Windows and other programs.
<br /> </span></b></li></ul> <p><b><span style="font-size: 10pt; color: rgb(204, 51, 0);">Note:</span></b><b><span style="font-size: 10pt;"> If receiving works for a while but then stops, your computer's power management settings may be turning off the sound card. </span></b></p> <p><b><span style="font-size: 10pt;">SignaLink USB Interface user? See the <a href="http://www.kc2rlm.info/soundcardpacket/1signalinkusb.htm">AGWPE-Signalink USB page</a> on this web site for troubleshooting suggestions.</span></b></p> <div class="MsoNormal" style="text-align: center;" align="center"> <hr align="center" size="2" width="100%"> </div> <h3><span style="color: rgb(0, 0, 153);">2. <a name="NoDecode">Oscilloscope Activity But No Decoding</a></span><span style=""></span></h3> <p><b><span style="font-size: 10pt;">If AGWPE is receiving signals but is not decoding them, look at these possibilities:</span></b></p> <ul type="disc"><li class="MsoNormal" style=""><b><span style="font-size: 10pt;"><a href="http://www.kc2rlm.info/soundcardpacket/5probrx.htm#RXlevel">f. Recording volume settings</a></span></b></li><li class="MsoNormal" style=""><b><span style="font-size: 10pt;"><a href="http://www.kc2rlm.info/soundcardpacket/5probrx.htm#Rxportset2">g. AGWPE settings</a></span></b></li><li class="MsoNormal" style=""><b><span style="font-size: 10pt;"><a href="http://www.kc2rlm.info/soundcardpacket/5probrx.htm#RXpoorsignal">h. Poor Signal quality</a></span></b></li><li class="MsoNormal" style=""><b><span style="font-size: 10pt;"><a href="http://www.kc2rlm.info/soundcardpacket/5probrx.htm#RXinterference">i. Interference</a></span></b></li><li class="MsoNormal" style=""><b><span style="font-size: 10pt;"><a href="http://www.kc2rlm.info/soundcardpacket/5probrx.htm#RXbaddriver">j. Sound card or driver</a></span></b></li><li class="MsoNormal" style=""><b><span style="font-size: 10pt;"><a href="http://www.kc2rlm.info/soundcardpacket/5probrx.htm#radiosettings">k. Radio Settings</a></span></b></li></ul> <p><b><span style="font-size: 10pt; color: rgb(204, 51, 0);">f. "Recording" <a name="RXlevel">Volume Settings</a></span></b><span style=""></span></p> <p><b><span style="font-size: 10pt;">AGWPE is very tolerant of RX audio volume levels, but your volume settings may still be too loud or too soft.</span></b></p> <p style="margin-left: 0.5in; text-indent: -0.25in;"><!--[if !supportLists]--><span style="font-size: 10pt; font-family: Symbol;"><span style="">·<span style="font-family: "Times New Roman"; font-style: normal; font-variant: normal; font-weight: normal; font-size: 7pt; line-height: normal; font-size-adjust: none; font-stretch: normal;"> </span></span></span><!--[endif]--><b><span style="font-size: 10pt; color: blue;">Too soft/muted:</span></b><b><span style="font-size: 10pt;"> try raising the receive <a href="http://www.kc2rlm.info/soundcardpacket/3volset.htm">volume sliders</a> until you see more deflection (peaks and valleys) in the <span style="color: rgb(0, 153, 153);"><a href="http://www.kc2rlm.info/soundcardpacket/3voltuneaid.htm">Tuning Aid's</a></span> Sine Wave. If the sliders don't change the wave significantly, try turning up the volume at the radio.
<br />If the RX audio from the radio is still too low:</span></b></p> <p style="margin-left: 1in; text-indent: -0.25in;"><!--[if !supportLists]--><span style="font-size: 10pt; font-family: "Courier New";"><span style="">o<span style="font-family: "Times New Roman"; font-style: normal; font-variant: normal; font-weight: normal; font-size: 7pt; line-height: normal; font-size-adjust: none; font-stretch: normal;"> </span></span></span><!--[endif]--><b><span style="font-size: 10pt;">make sure you are pulling audio from the correct radio pin/plug. Some radios have different RX audio pins/plugs for different modes or packet baud rates. Make sure you are using the one for your packet baud rate. (Example: the Yaesu FT-847 has a Data In/Out stereo plug jack for HF modes and a 6 pin mini-DIN jack for packet. Audio from the HF jack will be too weak for packet. If you buy a sound card interface, you may get only the Data In/Out plug and not the 6-pin mini-DIN plug.)</span></b> </p> <p style="margin-left: 1in; text-indent: -0.25in;"><!--[if !supportLists]--><span style="font-size: 10pt; font-family: "Courier New";"><span style="">o<span style="font-family: "Times New Roman"; font-style: normal; font-variant: normal; font-weight: normal; font-size: 7pt; line-height: normal; font-size-adjust: none; font-stretch: normal;"> </span></span></span><!--[endif]--><b><span style="font-size: 10pt;">remove any attenuation circuit you may have in the RX line</span></b> </p> <p style="margin-left: 1in; text-indent: -0.25in;"><!--[if !supportLists]--><span style="font-size: 10pt; font-family: "Courier New";"><span style="">o<span style="font-family: "Times New Roman"; font-style: normal; font-variant: normal; font-weight: normal; font-size: 7pt; line-height: normal; font-size-adjust: none; font-stretch: normal;"> </span></span></span><!--[endif]--><b><span style="font-size: 10pt;">try plugging the RX audio line into the MIC jack instead of the LINE IN</span></b> </p> <p style="margin-left: 1in; text-indent: -0.25in;"><!--[if !supportLists]--><span style="font-size: 10pt; font-family: "Courier New";"><span style="">o<span style="font-family: "Times New Roman"; font-style: normal; font-variant: normal; font-weight: normal; font-size: 7pt; line-height: normal; font-size-adjust: none; font-stretch: normal;"> </span></span></span><!--[endif]--><b><span style="font-size: 10pt;">install an audio pre-amplifier in the RX line.
<br /> </span></b> </p> <p style="margin-left: 0.5in; text-indent: -0.25in;"><!--[if !supportLists]--><span style="font-size: 10pt; font-family: Symbol;"><span style="">·<span style="font-family: "Times New Roman"; font-style: normal; font-variant: normal; font-weight: normal; font-size: 7pt; line-height: normal; font-size-adjust: none; font-stretch: normal;"> </span></span></span><!--[endif]--><b><span style="font-size: 10pt; color: blue;">Too loud:</span></b><b><span style="font-size: 10pt;"> If the sine pattern has very thick and tall waves (nearly fill the scope top to bottom), try lowering the volume settings. (If the sliders don't change the wave, try turning down the volume at the radio.)
<br /> </span></b> </p> <p style="margin-left: 0.5in; text-indent: -0.25in;"><!--[if !supportLists]--><span style="font-size: 10pt; font-family: Symbol;"><span style="">·<span style="font-family: "Times New Roman"; font-style: normal; font-variant: normal; font-weight: normal; font-size: 7pt; line-height: normal; font-size-adjust: none; font-stretch: normal;"> </span></span></span><!--[endif]--><b><span style="font-size: 10pt; color: blue;">MIC input</span></b><b><span style="font-size: 10pt;">: If you are using Microphone input, note that most sound cards expect a maximum input voltage on the microphone line of about 200 mV, which is much less than most radio's maximum output, e.g. 500 mV. For this reason, you should probably use a voltage <a href="http://www.kc2rlm.info/soundcardpacket/1cablerx.htm#mikecable">attenuation circuit in a microphone RX cable</a>. The ideal attenuation will depend on the sound card's input and radio's output specifications. You can try to use the volume sliders to find an ideal spot, but the setting is likely to be very delicate without the attenuation circuit.
<br />
<br />In addition, check that your are <span style="color: red;">not</span> using the Microphone Boost or the 20dB option on our sound card, if available. This option is not found in the AGWPE Volume settings, but it may be found as a button in the <a href="http://www.kc2rlm.info/soundcardpacket/3volset.htm#boost">Windows' Recording Volume Setting<span style="color: navy;"> </span></a>window under the <span style="color: rgb(0, 153, 153);">Microphone </span>slider (you may need to use the <span style="color: rgb(0, 153, 153);">Option: Advanced</span> menu option to have it display). This option will increase the MIC input by 100 times, which could distort your packet even more.</span></b> </p> <p><b><span style="font-size: 10pt; color: rgb(204, 51, 0);">g. AGWPE<a name="Rxportset2"> Setting</a>s</span></b></p> <ul type="disc"><li class="MsoNormal" style=""><b><span style="font-size: 10pt;">Baud Rate: Make sure you have selected the correct packet baud rate in the <a href="http://www.kc2rlm.info/soundcardpacket/2agwbasic.htm#soundcardproperties">Sound Card Setup screen</a></span></b></li><li class="MsoNormal" style=""><b><span style="font-size: 10pt;">Ports: If you are only using one port, set AGWPE for <st1:placename st="on"><span style="color: blue;">Single</span></st1:placename><span style="color: blue;"> <st1:placetype st="on">Port</st1:placetype></span> (not <st1:place st="on"><st1:placename st="on">Dual</st1:placename> <st1:placetype st="on">Port</st1:placetype></st1:place>) on the <a href="http://www.kc2rlm.info/soundcardpacket/2agwbasic.htm#portsettings">Properties screen</a></span></b></li></ul> <p><b><span style="font-size: 10pt; color: rgb(204, 51, 0);">h. Poor S<a name="RXpoorsignal">ignal qualit</a>y:</span></b></p> <ul type="disc"><li class="MsoNormal" style=""><b><span style="font-size: 10pt; color: blue;">1200 baud packet</span></b><b><span style="font-size: 10pt;">: To successfully decode a packet, you need about an S3 signal at minimum.
<br /> </span></b></li><li class="MsoNormal" style=""><b><span style="font-size: 10pt; color: blue;">9600 baud packet:</span></b><b><span style="font-size: 10pt;"> To successfully decode a packet, you need nearly an S9 signal. (see <a href="http://www.kc2rlm.info/soundcardpacket/6modes.htm#9600">9600 Packet Operations</a> on the Baud Rates and Modes page. for additional advice about 9600 baud packet operations.)
<br /> </span></b></li><li class="MsoNormal" style=""><b><span style="font-size: 10pt; color: blue;">300 baud packet (HF SSB):</span></b><b><span style="font-size: 10pt;"> Use the <span style="color: navy;"><a href="http://www.kc2rlm.info/soundcardpacket/3voltuneaid.htm">Sound Card Tuning Aid</a>'s </span>Waterfall Scope to accurately tune the signal. (see <a href="http://www.kc2rlm.info/soundcardpacket/6modes.htm#300%20baud">HF Packet Operations</a> on the Baud Rates and Modes page. for additional advice about HF packet operations.
<br /> </span></b></li><li class="MsoNormal" style=""><b><span style="font-size: 10pt;">Are you tuned to the correct frequency exactly?
<br /> </span></b></li><li class="MsoNormal" style=""><b><span style="font-size: 10pt;">Is the mode set for FM and not accidentally in CW, SSB or another mode?
<br /> </span></b></li><li class="MsoNormal" style=""><b><span style="font-size: 10pt;">Do you have tone squelch on? Do you have manual squelch on? Is the radio's squelch set too high and blocking many signals. (The squelch should not be operating when using AGWPE. When it transmits, AGWPE needs to hear the frequency at all times.)
<br /> </span></b></li><li class="MsoNormal" style=""><b><span style="font-size: 10pt;">Packet collisions -- two or more transmitting stations send packets at the same time, making both unintelligible. This is a common problem on busy frequencies, e.g. APRS. No real solution is available although network members could experiment with traffic reduction and collision avoidance schemes and settings, such as slotting.
<br /> </span></b></li><li class="MsoNormal" style=""><b><span style="font-size: 10pt;">The other station's packets are too distant, faint, or noisy: </span></b></li><ul type="circle"><li class="MsoNormal" style=""><b><span style="font-size: 10pt;">Increase your radio knob's volume control if the radio knob controls RX audio volume; or increase your <a href="http://www.kc2rlm.info/soundcardpacket/3volset.htm#rxaudioset">RX Volume Setting</a> for <span style="color: navy;">LINE IN</span> (or MIC, if you are using that).</span></b></li><li class="MsoNormal" style=""><b><span style="font-size: 10pt;">Poor radio signal path: You may be experiencing multi-path refraction/ reflection problems (signal waves arriving out of phase) or a Fresnel null (part of the signal wave is blocked) because of the antenna's poor position. Try moving your antenna.</span></b></li><li class="MsoNormal" style=""><b><span style="font-size: 10pt;">Use a better antenna (more height, more gain, more separation from noise or interference sources).</span></b></li><li class="MsoNormal" style=""><b><span style="font-size: 10pt;">Ask the other station to increase power.</span></b></li><li class="MsoNormal" style=""><b><span style="font-size: 10pt;">Ask the other station to try a different antenna or a different antenna location.</span></b></li><li class="MsoNormal" style=""><b><span style="font-size: 10pt;">Consider an antenna feed-line problem at your station if there is any other evidence of weakened signals, e.g. moving the antenna doesn't help and you experience low audio and static on your RX signal compared to the signal someone nearby is receiving.
<br /> </span></b></li></ul><li class="MsoNormal" style=""><b><span style="font-size: 10pt;">The packets the other station is sending are are poorly formed:</span></b></li><ul type="circle"><li class="MsoNormal" style=""><b><span style="font-size: 10pt;">The sending station sent the packet without sufficient TX delay. Its radio didn't have sufficient time to power up or switch from receive to transmit. As a result, the beginning of the packet was lost. Ask the sending station to increase TX delay in his station's TNC or sound card.</span></b></li><li class="MsoNormal" style=""><b><span style="font-size: 10pt;">The sending station's TNC or sound card was over-driving the radio (sending packet tones that were too loud) and his radio had to "clip" the signal (reduce the deviation). This results in a poorly formed packets at the receiving end (low tone is louder than high tone). Ask the sending station to reduce his station's TNC drive level.</span></b></li><li class="MsoNormal" style=""><b><span style="font-size: 10pt;">Some radios offer a bass boost function that will distort a packet signal. Make sure the sending station is not using this feature.
<br /> </span></b></li></ul><li class="MsoNormal" style=""><b><span style="font-size: 10pt;">Are you using the MIC jack on the sound card instead of the LINE In jack? Then you probably should have an attenuation circuit in the RX cable. See the <a href="http://www.kc2rlm.info/soundcardpacket/1cablerx.htm#mikecable">RX audio cable Help page</a> for such a circuit.
<br /> </span></b></li><li class="MsoNormal" style=""><b><span style="font-size: 10pt;">Note that distorted packet signals simply cannot be decoded. For example, if you have mountains (or tall buildings) near you, then signals may be reflected by the mountains (or buildings) and result in multipath (or phase) errors. You can try using a small beam antenna to overcome the problem. Align the antenna with the boom parallel to the mountains.</span></b></li></ul> <p><b><span style="font-size: 10pt; color: rgb(204, 51, 0);">i. <a name="RXinterference">Interference</a></span></b><span style=""></span></p> <p><b><span style="font-size: 10pt;">Signal interference from EMI, RFI, and ground loops can distort received packet signals so much that they can not be decoded. Radios such as the Yaesu FT-290 are known for being susceptible to computer noise interference. And computer (laptop) noise can get into radios (particularly HTs) and antenna if they are too close to the computer.</span></b></p> <ul type="disc"><li class="MsoNormal" style=""><b><span style="font-size: 10pt;">Power noise: Especially on laptops, noise can enter the sound card from the power supply. Try disconnecting the power supply and run on battery only. If your radio is connected to a poor quality power supply or if it's connected to a battery charged by a poor quality power supply, you may also have problems. See <a href="http://www.buxcomm.com/pdfzips/hum-and-noise-solutions.pdf">http://www.buxhamparts.com/humsolving.html</a>
<br /> </span></b></li></ul> <ul type="disc"><li class="MsoNormal" style=""><b><span style="font-size: 10pt; color: blue;">EMI, electro-magnetic interference</span></b><b><span style="font-size: 10pt;">, can come from any nearby AC-powered source, such as your monitor. Turn off the monitor temporarily and then turn it on to see if your packet program recorded any signal when it was off. You may be able to reduce EMI if you:</span></b></li><ul type="circle"><li class="MsoNormal" style=""><b><span style="font-size: 10pt;">change the monitor scan rates or screen size or combinations of both in:
<br /> Windows Desktop > Right Click > Setting Tab > Monitor ----- etc....</span></b></li><li class="MsoNormal" style=""><b><span style="font-size: 10pt;">replace outdated or incorrect monitor driver software</span></b></li><li class="MsoNormal" style=""><b><span style="font-size: 10pt;">place a ferrite snap-on core on the monitor cable, close to the computer and another close to the monitor</span></b></li><li class="MsoNormal" style=""><b><span style="font-size: 10pt;">re-locate either the device or your interface cables</span></b></li><li class="MsoNormal" style=""><b><span style="font-size: 10pt;">use shielded interface cables</span></b></li><li class="MsoNormal" style=""><b><span style="font-size: 10pt;">use ferrite cores (split or toroids) on the interface cables.</span></b></li><li class="MsoNormal" style=""><b><span style="font-size: 10pt;">use shielding on the radiating device</span></b></li><li class="MsoNormal" style=""><b><span style="font-size: 10pt;">move mag-mount or HT antennas away from the computer</span></b></li></ul></ul> <p style="margin-left: 0.5in;"> </p> <ul type="disc"><li class="MsoNormal" style=""><b><span style="font-size: 10pt; color: blue;">RFI, radio frequency interference,</span></b><b><span style="font-size: 10pt;"> can be reduced if you:</span></b></li><ul type="circle"><li class="MsoNormal" style=""><b><span style="font-size: 10pt;">limit the length of your interface cable</span></b></li><li class="MsoNormal" style=""><b><span style="font-size: 10pt;">use interface cables <span style="color: blue;">with </span>shielding</span></b></li><li class="MsoNormal" style="margin-bottom: 12pt;"><b><span style="font-size: 10pt;">use ferrite cores (split or toroids) on cables.</span></b></li></ul><li class="MsoNormal" style=""><b><span style="font-size: 10pt; color: blue;">Ground loops</span></b><b><span style="font-size: 10pt;"> can result when DC current flows between your computer and your radio. Normally, DC current should not flow between the devices, but it will if there is a voltage potential difference between the devices. Unfortunately, a sound card interface can become that link.
<br />
<br /> If you have your computer and radio plugged in to a different branch of the AC wiring in your house, you may have problems. Plug your computer in to the same AC outlet strip as your radio, so they share the same electrical ground. </span></b></li></ul> <p><b><span style="font-size: 10pt;">To break the ground loop, you should use isolation transformers on your RX and TX audio cables, plus a phototransistor, or optocoupler, in the PTT line (a simple transistor in the PTT line does not does provide isolation). You must isolate all three connecting cables.
<br />
<br />Note that some manufactured interfaces may not provide isolation on all three cables (For example, the <st1:place st="on"><st1:placename st="on">West</st1:placename> <st1:placetype st="on">Mountain</st1:placetype></st1:place> NOMIC does not provide isolation for a RX cable). You can verify if the interface does by visual inspection: look for a small transformer in audio line circuit; or ask the manufacturer.</span></b></p> <table class="MsoNormalTable" style="border: medium none ; width: 90%; border-collapse: collapse;" border="1" cellpadding="0" cellspacing="0" width="90%"> <tbody><tr style=""> <td style="padding: 3.75pt;"> <p class="MsoNormal"><b><span style="font-size: 10pt;"> I see that Buxcomm now offers a simple add-on audio isolation cable if you don't want to build your own. You simply plug in the Buxcomm isolation cable between your sound card jacks and your audio in and your audio out lines. The item is called a ISOL8R and you can order it for $9.97 ($17.97 for 2) at <a href="http://www.buxcomm.com/pdfzips/hum-and-noise-solutions.pdf">http://www.buxhamparts.com/humsolving.html</a> </span></b></p> </td> </tr> </tbody></table> <p><b><span style="font-size: 10pt;"> Below are screen shots from the <a href="http://www.kc2rlm.info/soundcardpacket/3voltuneaid.htm">Tuning Aid's</a> Sine Wave scope showing a ground loop: </span></b></p> <p style="text-align: center;" align="center"><!--[if gte vml 1]><v:shape id="_x0000_i1071" type="#_x0000_t75" alt="" style="'width:252pt;height:103.5pt'"> <v:imagedata src="file:///C:\DOCUME~1\C11AE~1.BLA\LOCALS~1\Temp\msohtml1\01\clip_image036.gif" href="http://www.kc2rlm.info/soundcardpacket/AGWImages/5probrx1.gif"> </v:shape><![endif]--><!--[if !vml]--><img src="file:///C:/DOCUME%7E1/C11AE%7E1.BLA/LOCALS%7E1/Temp/msohtml1/01/clip_image036.gif" shapes="_x0000_i1071" border="0" height="138" width="336" /><!--[endif]--></p> <p style="text-align: center;" align="center"><b> <!--[if gte vml 1]><v:shape id="_x0000_i1072" type="#_x0000_t75" alt="" style="'width:252pt;height:102.75pt'"> <v:imagedata src="file:///C:\DOCUME~1\C11AE~1.BLA\LOCALS~1\Temp\msohtml1\01\clip_image037.gif" href="http://www.kc2rlm.info/soundcardpacket/AGWImages/5probrx2.gif"> </v:shape><![endif]--><!--[if !vml]--><img src="file:///C:/DOCUME%7E1/C11AE%7E1.BLA/LOCALS%7E1/Temp/msohtml1/01/clip_image037.gif" shapes="_x0000_i1072" border="0" height="137" width="336" /><!--[endif]-->
<br /> </b></p> <table class="MsoNormalTable" style="border: medium none ; border-collapse: collapse;" border="1" cellpadding="0" cellspacing="0"> <tbody><tr style=""> <td style="padding: 4.5pt;"> <p class="MsoNormal"><b><span style="color: rgb(204, 51, 0);">EMI or RFI on Your Receive Audio Cable?
<br />
<br /> </span></b><b><span style="font-size: 10pt;">You can use the <a href="http://www.kc2rlm.info/soundcardpacket/3voltuneaid.htm">Sound Card Tuning Aid </a>to "see" if you have interference or some other problem affecting your RX audio cable. Here is a way to hear it:
<br /> </span></b></p> <ul type="disc"><li class="MsoNormal" style=""><b><span style="font-size: 10pt;">Temporarily plug your computer speakers into LINE OUT jack of the soundcard.</span></b></li><li class="MsoNormal" style=""><b><span style="font-size: 10pt;">Open AGWPE's <a href="http://www.kc2rlm.info/soundcardpacket/3volset.htm#AGWPEVolSet">Soundcard Volume Settings screen</a> </span></b></li><li class="MsoNormal" style=""><b><span style="font-size: 10pt;">If you can't hear the radio's RX audio in your computer speakers, increase the RX volume sliders'</span></b></li><li class="MsoNormal" style=""><b><span style="font-size: 10pt;">When you do hear RX radio audio, tune to a quiet frequency and lower the RX volume slider to its minimum (you may need to also turn down the radio' speaker volume dial if you get RX audio from the radio's mic or speaker jack. ) </span></b></li><li class="MsoNormal" style=""><b><span style="font-size: 10pt;">Now increase the TX Playback volume (WAVE & TX Master) to maximum.</span></b></li><li class="MsoNormal" style=""><b><span style="font-size: 10pt;">You should hear no radio signals or radio noise. If you hear any Hummmmmm or Hissssssss it should be very, very slight. If it very distinct, you probably have a RFI, EMI or ground loop problem with your RX audio cable. Just to be sure, compare the sounds from your computer speakers with the sounds from your radio's speaker to see if the sounds are the same as the radio's (no problem) or unique.</span></b></li></ul> </td> </tr> </tbody></table> <p> </p> <p><b><span style="font-size: 10pt; color: rgb(204, 51, 0);">j. <a name="RXbaddriver">Sound Card or Driver</a></span></b><span style=""></span></p> <ul type="disc"><li class="MsoNormal" style=""><b><span style="font-size: 10pt;">You can try adjusting the <span style="color: rgb(0, 153, 153);">sound card clock</span> from the <a href="http://www.kc2rlm.info/soundcardpacket/2agwbasic.htm#soundcardproperties">Sound Card Modem Setup screen</a>. Sound cards have a reference "clock" that oscillates at approximately 11025 Hz. The exact speed usually varies for each person's sound card. The clock setting in AGWPE can be used to better match AGWPE to the actual sound card clock speed.
<br /> </span></b></li></ul> <table class="MsoNormalTable" style="border: medium none ; margin-left: 0.5in; border-collapse: collapse;" border="1" cellpadding="0" cellspacing="0"> <tbody><tr style=""> <td style="padding: 3.75pt;"> <p class="MsoNormal"><b><span style="font-size: 10pt;">All TNCs try to adjust their receiving clock (a software component) to match the bit rate they receive and thus follow the clock changes of the receiving signal. The AGWPE soundcard modem does the same using the soundcard clock. In certain cards, that clock may be very wrong (fast or slow). The clock setting value you can change in AGWPE tries to adjust the sound card clock using software inside AGWPE's modem code. It doesn't change anything in the sound card.</span></b></p> </td> </tr> </tbody></table> <p style="margin-left: 0.5in; text-indent: -0.25in;"><!--[if !supportLists]--><span style="font-size: 10pt; font-family: Symbol;"><span style="">·<span style="font-family: "Times New Roman"; font-style: normal; font-variant: normal; font-weight: normal; font-size: 7pt; line-height: normal; font-size-adjust: none; font-stretch: normal;"> </span></span></span><!--[endif]--><b><span style="font-size: 10pt;">AGWPE's default clock setting is "4", which is no adjustment. Using trial-and-error, you can try to find a setting that is better. (I do not know in absolute terms how much change in Hz there is for each setting; or even if "2" is slower or or faster than "4".) </span></b></p> <p style="margin-left: 0.5in; text-indent: -0.25in;"><!--[if !supportLists]--><span style="font-size: 10pt; font-family: Symbol;"><span style="">·<span style="font-family: "Times New Roman"; font-style: normal; font-variant: normal; font-weight: normal; font-size: 7pt; line-height: normal; font-size-adjust: none; font-stretch: normal;"> </span></span></span><!--[endif]--><b><span style="font-size: 10pt;">For your experimentation:</span></b></p> <ul type="disc"><ul type="circle"><li class="MsoNormal" style=""><b><span style="font-size: 10pt;">after you select a new clock setting, you must restart AGWPE. Clock setting changes are NOT immediate.</span></b></li><li class="MsoNormal" style=""><b><span style="font-size: 10pt;">it's best to test reception of a weak station (less than S8) </span></b></li></ul></ul> <p style="margin-left: 0.5in;"><b><span style="font-size: 10pt;">Interestingly, you may find the perfect setting for some stations may change with the seasons, if the hardware in those stations are outdoors and exposed to heat fluctuations.
<br /> </span></b> </p> <ul type="disc"><li class="MsoNormal" style="margin-bottom: 12pt;"><b><span style="font-size: 10pt;">If AGWPE appears to be receiving good quality packet signals that are not being decoded, then you may have an incompatible sound card. (This seems to be more prevalent with integrated, "on board" sound "cards".)
<br /> <a href="http://www.kc2rlm.info/soundcardpacket/5probrx.htm#RXcard">See "e." above.</a></span></b></li></ul> <p><b><span style="font-size: 10pt; color: rgb(204, 51, 0);">k. <a name="radiosettings">Radio Settings</a></span></b><span style=""></span></p> <ul type="disc"><li class="MsoNormal" style=""><b><span style="font-size: 10pt;">If your radio has signal processing settings, turn them off. For example, some Yaesus have a "bass boost" function. Others radios such as the ICOM IC-706MKIIG, have a "DSP" setting. These settings should be turned off/disabled.
<br /> </span></b></li><li class="MsoNormal" style=""><b><span style="font-size: 10pt;">Make sure you are using the correct RX data output source on the radio. For example, on a Yaesu FT-8500, AGWPE can not decode 1200 bps through the data port , only through the speaker-out jack. The "problem" with the data port is that it has no de-emphasis circuitry and so the packet tones are skewed by at least 6 dB. (To fix that, "You would need to add the right value capacitor." Sorry I can't help much beyond that.)
<br /> </span></b></li><li class="MsoNormal" style="margin-bottom: 12pt;"><b><span style="font-size: 10pt;">Hand-held radio often have a "battery saver' or "power saver" setting that turns off the radio's receiver circuit for a few seconds or parts of a second. It that setting is on, you may be missing the first part of packets.</span></b></li></ul> <p><b><span style="font-size: 10pt;">If your problem is not resolved by the problem solving pages on this website, join the AGWPE Yahoo Group to ask a question or search the archives for previous postings that may relate to your problem</span></b></p> <h2><span style="font-family: Verdana; color: rgb(204, 51, 0);">Problems with Transmitting </span><span style="font-family: Verdana;"><o:p></o:p></span></h2> <p><b><span style="font-size: 10pt;">As you troubleshoot transmit problems, remember that AGWPE provides you this visual aid: </span></b></p> <ul type="disc"><li class="MsoNormal" style=""><b><span style="font-size: 10pt;">If AGWPE receives a packet transmission request from a client application and then successfully passes that packet to the sound card and radio for transmission, the <span style="color: red;">red </span>light in the transmitting radioport's modem icon will flash once <!--[if gte vml 1]><v:shape id="_x0000_i1073" type="#_x0000_t75" alt="" style="'width:26.25pt;"> <v:imagedata src="file:///C:\DOCUME~1\C11AE~1.BLA\LOCALS~1\Temp\msohtml1\01\clip_image038.gif" href="http://www.kc2rlm.info/soundcardpacket/AGWImages/redblink.gif"> </v:shape><![endif]--><!--[if !vml]--><img src="file:///C:/DOCUME%7E1/C11AE%7E1.BLA/LOCALS%7E1/Temp/msohtml1/01/clip_image038.gif" shapes="_x0000_i1073" border="0" height="21" width="35" /><!--[endif]--> and your radio should transmit.</span></b></li></ul> <p><b><span style="font-size: 10pt;">To Force a Transmission through AGWPE, use the <a href="http://www.kc2rlm.info/soundcardpacket/AGWPrograms.htm">AGWTerminal (TCPIP version</a>) program to send a <span style="color: rgb(0, 153, 153);">QRA</span> packet: From AGWTerm tool bar, press the "Tower & Question mark" button, and then select the radioport you want to test. </span></b></p> <p><b><span style="color: red;">Note:</span></b><b><span style="font-size: 10pt;"> Please make sure you are using the <a href="http://www.kc2rlm.info/soundcardpacket/AGWPrograms.htm">latest version of AGWPE</a> before troubleshooting problems. Your problem may have been fixed in the most recent version of AGWPE!</span></b></p> <p><span style="font-size: 10pt;">1. <a href="http://www.kc2rlm.info/soundcardpacket/5probtx.htm#NoKeyUp">Radio Doesn't transmit</a>
<br />2. <a href="http://www.kc2rlm.info/soundcardpacket/5probtx.htm#RadioLocks">Radio Locks in Transmit mode</a>
<br />3. <a href="http://www.kc2rlm.info/soundcardpacket/5probtx.htm#IntermittentTrans">Intermittent Transmissions</a>
<br />4. <a href="http://www.kc2rlm.info/soundcardpacket/5probtx.htm#NoAudio">No audio or poor audio on transmit</a></span>
<br /> </p> <p><b><span style="color: navy;">1. <a name="NoKeyUp">Radio Doesn't Transmit</a></span></b><span style=""></span></p> <ul type="disc"><li class="MsoNormal" style=""><b><span style="font-size: 10pt; color: blue;">A. No Red Light Seen:</span></b><b><span style="font-size: 10pt;"> My application program sent a packet, but I do <span style="color: red;">not</span> see the <span style="color: red;">red</span> light in the AGWPE modem icon indicating it has transmitted the packet to the radio.
<br /> </span></b></li><ul type="circle"><li class="MsoNormal" style=""><b><span style="font-size: 10pt;">Make sure the radio's is <span style="color: blue;">ON</span> and the squelch is fully open at all times. AGWPE needs to hear the frequency noise level at all times -- no squelching! -- otherwise it may not transmit.
<br /> </span></b></li><li class="MsoNormal" style=""><b><span style="font-size: 10pt;">Make sure you application program is correctly linked to AGWPE. See the <a href="http://www.kc2rlm.info/soundcardpacket/5probprog.htm#Clients">Program Behavior page about Linking to Client Programs.</a>
<br /> </span></b></li><li class="MsoNormal" style=""><b><span style="font-size: 10pt;">Make sure the application program really is requesting a packet transmission. For example, a terminal program will not send anything if it is linked to AGWPE in COMMAND mode (unless you use the CONNECT or DISCONNECT commands). Try a CONNECT command if you are not yet connected or go to CONVERSE mode (K) if you are connected.
<br />
<br />
<br /> </span></b></li></ul></ul> <ul type="disc"><li class="MsoNormal" style=""><b><span style="font-size: 10pt; color: blue;">B. </span></b><b><span style="font-size: 10pt; color: red;">Red</span></b><b><span style="font-size: 10pt; color: blue;"> Light is Seen</span></b><b><span style="font-size: 10pt;">: I saw the <span style="color: red;">red</span> light blink in the AGWPE modem icon, but the radio isn't transmitting.
<br /> </span></b></li><ul type="circle"><li class="MsoNormal" style=""><b><span style="font-size: 10pt;">Double check that the PTT cable is connected tightly to the appropriate COM (or LPT) port. Make sure you do not have a loose connection.
<br /> </span></b></li><li class="MsoNormal" style=""><b><span style="font-size: 10pt;">It may be that the physical COM or LPT port where your PTT cable is connected isn't really the port you think it is: e.g. you think it's COM1, but your mouse or internal modem is on COM1, so your PTT is really plugged into COM2 . Try changing the port for <span style="color: navy;">PTT Control </span>in the <a href="http://www.kc2rlm.info/soundcardpacket/2agwbasic.htm#portsettings">Port Properties</a> or move the PTT cable to another COM or LPT port.
<br /> </span></b></li><li class="MsoNormal" style=""><b><span style="font-size: 10pt;">Is there a problem with your PTT cable and circuit? You can test it by using a 9 volt battery to apply voltage to the cable's RTS/DTR pin (in the DB9 or DB25 connector) and then using a voltmeter to test for voltage on the radio end of the cable or, if the cable is connected to the radio, look to see if the radio is transmitting.
<br /> </span></b></li><li class="MsoNormal" style=""><b><span style="font-size: 10pt;">Your application program may be configured for the wrong AGWPE radioport. If you need instructions for changing the radioport, look in the Help section of the client application; or you can try the <span style="color: navy;"><a href="http://www.kc2rlm.info/soundcardpacket/7compat.htm">Application Setup</a></span><a href="http://www.kc2rlm.info/soundcardpacket/7compat.htm"> </a>page.
<br /> </span></b></li><li class="MsoNormal" style=""><b><span style="font-size: 10pt;">Are you using the parallel port (LPT) for PTT control and running Windows XP or 2000? This can't be done with AGWPE and those versions of Windows. For those versions, your only choice is to purchase <span style="color: rgb(0, 153, 153);"><a href="http://www.sv2agw.com/ham/pepro.htm">Packet Engine Pro</a></span>. (Windows XP and 2000 use a port addressing scheme that is different than the scheme used in Win 95, 98, and ME, which do let AGWPE use the LPT port for PTT control.) Alternatively, you can use the following PTT signaling methods instead of the LPT if you have Windows XP/2000:</span></b></li><ul type="square"><li class="MsoNormal" style=""><b><span style="font-size: 10pt;">use a serial (COM) port</span></b></li><li class="MsoNormal" style=""><b><span style="font-size: 10pt;">use a USB port by obtaining a <st1:place st="on"><st1:placename st="on">USB-to-Serial</st1:placename> <st1:placetype st="on">Port</st1:placetype></st1:place> (COM) adapter</span></b></li><li class="MsoNormal" style=""><b><span style="font-size: 10pt;">use a TX audio tone keyer that uses detected audio to trip the PTT circuit</span></b></li></ul></ul></ul> <p style="margin-left: 1in;"><b><span style="font-size: 10pt;">These are all described on the <a href="http://www.kc2rlm.info/soundcardpacket/1cableptt.htm">PTT cable page</a>.
<br /> </span></b> </p> <ul type="disc"><ul type="circle"><li class="MsoNormal" style=""><b><span style="font-size: 10pt;">Are you using the parallel port (LPT) with Windows 98SE/ ME? It should work but, if it doesn't, some users have success configuring the LPT1 port to a "legacy" I/O address, i.e. IRQ 7 and address 0378-037F. To do this, go into Settings, Control Panel, System, Device Manager, Ports, <st1:place st="on"><st1:placename st="on">Printer</st1:placename> <st1:placetype st="on">Port</st1:placetype></st1:place> and select the Resources tab. Configure manually to the above settings and reboot. Check that there are no conflicts with other devices.
<br /> </span></b></li><li class="MsoNormal" style=""><b><span style="font-size: 10pt;">Is your PTT cable wired to the correct pin at the computer's RS-232 port (COM or LPT)? AGWPE sends the PTT signal <span style="color: rgb(204, 51, 0);">to the RTS pin only</span> if you have chosen <st1:place st="on"><st1:placename st="on"><span style="color: blue;">Single</span></st1:placename><span style="color: blue;"> <st1:placetype st="on">Port</st1:placetype></span></st1:place><span style="color: blue;"> </span>in the <a href="http://www.kc2rlm.info/soundcardpacket/2agwbasic.htm#portsettings">Port Properties</a> window. It does <span style="color: rgb(204, 51, 0);">not</span> also send it to the <span style="color: navy;">DTR</span> pin, as some other sound card programs do or as earlier versions of AGWPE did. If AGWPE is set for <span style="color: blue;">Dual Port</span> then the radioport 1 radio (left channel ) will use the <span style="color: navy;">RTS</span><span style="color: blue;"> </span>pin, while radioport 2 (right channel) will use the <span style="color: navy;">DTR</span>. See the <a href="http://www.kc2rlm.info/soundcardpacket/1cableptt.htm">PTT Cable page</a> for wiring schematics. Possibly so some manufactured interfaces may have wired the PTT cable to the <span style="color: navy;">DTR</span> pin only and not the RTS.
<br /> </span></b></li><li class="MsoNormal" style=""><b><span style="font-size: 10pt;">SignaLink USB Interface user? See the <a href="http://www.kc2rlm.info/soundcardpacket/1signalinkusb.htm">AGWPE-Signalink USB page</a> on this web site for troubleshooting suggestions.
<br /> </span></b></li><li class="MsoNormal" style=""><b><span style="font-size: 10pt;">Occasionally there is a problem with the physical port. You can use a voltmeter to test the COM/LPT port pin. There should be DC voltage on the pin when the red pixel in the AGWPE modem icon lights.
<br />
<br /> Note: When Windows boots, it tests all COM and LPT ports by momentarily putting a signal on the port pins (Windows XP does it 5 times). If you have your PTT cable connected and your radio "on" when Windows boots, then the radio PTT will activate for a few short bursts during the boot sequence. This is a good indication that your PTT cable is working correctly.
<br />
<br /> </span></b></li></ul></ul> <table class="MsoNormalTable" style="border: 1.5pt outset ; width: 4.75in; margin-left: 1in;" border="1" cellpadding="0" width="456"> <tbody><tr style=""> <td style="padding: 5.25pt;"> <p class="MsoNormal"><st1:place st="on"><st1:placename st="on"><b><span style="color: blue;">COM</span></b></st1:placename><b><span style="color: blue;"> <st1:placetype st="on">Port</st1:placetype></span></b></st1:place><b><span style="color: blue;"> Problem?</span></b></p> <p><b><span style="font-size: 10pt;">Although I haven't heard of this happening with sound card interfaces or AGWPE, I have heard that TNCs and GPS units attached to a COM port can pose problems for Windows and your ability to use that COM port for packet programs. </span></b></p> <p><b><span style="font-size: 10pt;">During the boot up process, Windows will automatically try to determine what device is attached to every COM port if finds. For example, if it finds a TNC or GPS on COM1, it may incorrectly identify that device as a "Ballpoint" track ball mouse, reserve it for that (non-existent) mouse and prevent other programs, such as packet programs, from using COM1.</span></b></p> <p><b><span style="font-size: 10pt;">Booting up without the sound card interface/ TNC / GPS attached to the COM port may be one way to avoid this problem. (Another, more radical but still temporary fix is to use Windows' Device Manager to delete the COM port, turn off the computer, and disconnect the device from the COM port. When you restart the computer, Windows will re-discover the empty COM port and not reserve it for a particular use. You can then re-attach your device to the COM port and use it for your packet programs.) </span></b></p> <p><b><span style="font-size: 10pt;">But a better, more permanent solution to this problem is to run Microsoft's free <span style="color: blue;">COMdisable</span> utility. Contrary to it's name, this Microsoft utility does not disable COM ports or even disable the boot-up detection of COM ports. Rather, it prevents Windows' from trying to identify what devices are connected to COM ports and reserving ports unnecessarily. You need run <span style="color: blue;">COMdisable</span> only once; Windows will remember your preferences. After you run <span style="color: blue;">COMdisable</span>, you then will be able to leave your TNC/GPS/sound card interface attached to your preferred COM port when you boot up.</span></b></p> <p><b><span style="font-size: 10pt;">You can get <span style="color: blue;">COMdisable</span> at: </span></b></p> <p><b><span style="font-size: 10pt;"><a href="http://support.microsoft.com/default.aspx?scid=kb;en-us;819036">http://support.microsoft.com/default.aspx?scid=kb;en-us;819036</a> </span></b></p> <p><b><span style="font-size: 10pt;">Thanks to Stephen WA8LMF for this tip. He also keeps a copy of <span style="color: blue;">COMdisable</span> on his site: <a href="http://wa8lmf.net/aprs/GPS_Mouse.htm">http://wa8lmf.net/aprs/GPS_Mouse.htm</a> </span></b></p> </td> </tr> </tbody></table> <p style="margin-left: 1in; text-indent: -0.25in;"><!--[if !supportLists]--><span style="font-size: 10pt; font-family: "Courier New";"><span style="">o<span style="font-family: "Times New Roman"; font-style: normal; font-variant: normal; font-weight: normal; font-size: 7pt; line-height: normal; font-size-adjust: none; font-stretch: normal;"> </span></span></span><!--[endif]--><b><span style="font-size: 10pt;">
<br /> </span></b> </p> <ul type="disc"><ul type="circle"><li class="MsoNormal" style=""><b><span style="font-size: 10pt;">Many new transceivers, e.g. Yaesu 8100, won't transmit if the TX audio level is too high. Use the <a href="http://www.kc2rlm.info/soundcardpacket/3volset.htm#txaudioset">Volume Settings screen</a> to lower the <span style="color: rgb(0, 153, 153);">TX Master</span><span style="color: navy;"> </span>and/or <span style="color: rgb(0, 153, 153);">TX Wave</span><span style="color: navy;"> </span>volume. Or adjust the potentiometer on the line, if thre is one.
<br /> </span></b></li><li class="MsoNormal" style=""><b><span style="font-size: 10pt;">Some radios may use different TX audio pins for HF and VHF/UHF. The ICOM 706 is one. Consult your radio's user manual for pin out instructions. This can be the solution if your interface works correctly for HF digital modes such as PSK31, but won't work for VHF/UHF packet, or vice versa.
<br /> </span></b></li><li class="MsoNormal" style=""><b><span style="font-size: 10pt;">If AGWPE seems to run fine for a set time (15, 30 minutes) and then stops transmitting, your computer's power management scheme may be turning off the COM/LPT port that controls PTT.</span></b><span style="font-size: 10pt;">
<br /> </span></li><li class="MsoNormal" style=""><b><span style="font-size: 10pt; color: blue;">I'm using a commercial sound card interface (in this case a RASCAL GLX). I can transmit once, but I can't transmit again unless I reboot. I'm running Win2k Pro, SP4 (but may be a problem with other Windows versions).
<br />
<br /> </span></b><b><span style="font-size: 10pt;">Many commercial interfaces are wired to allow PTT control by either the RTS or DTR line of the COM port. It may be that a</span></b><tt><b><span style="font-size: 10pt; font-family: Arial;"> small amount of negative voltage (-V) on the DRT line was canceling the positive voltage +V on RTS line.</span></b></tt></li></ul></ul> <p style="margin-left: 1in;"><b><span style="font-size: 10pt;">To fix this, you will need to disconnect the wire in the interface that connects the DTR line to the PTT circuit. Use just the RTS line for AGWPE in single port mode.<span style="color: blue;">
<br /> </span></span></b> </p> <h4><span style="color: navy;">2. <a name="RadioLocks">Radio Locks in Transmit mode</a></span><span style=""></span></h4> <ul type="disc"><li class="MsoNormal" style=""><b><span style="font-size: 10pt;">First try closing and restarting the packet application and AGWPE; or try rebooting.
<br /> </span></b></li><li class="MsoNormal" style=""><b><span style="font-size: 10pt;">If you are using a hand held radio:</span></b></li><ul type="circle"><li class="MsoNormal" style=""><b><span style="font-size: 10pt;">Remember that, in addition to the usual PTT circuit components, you will still need all the PTT components recommended by the radio manufacturer for MIC and Speaker jack data use. Many handhelds need a capacitor on the TX audio line between the radio and the PTT gate circuit (as well as a resistor on the PTT line). Without that capacitor, the PTT circuit may be active at all times.</span></b></li><li class="MsoNormal" style=""><b><span style="font-size: 10pt;">If the manufacturer says to use a stereo plug for the radio's MIC jack, don't use a mono plug!
<br /> </span></b></li></ul><li class="MsoNormal" style=""><b><span style="font-size: 10pt;">You may have a wiring problem in the PTT cable. Double check the wiring, components, and circuit routing:</span></b></li><ul type="circle"><li class="MsoNormal" style=""><b><span style="font-size: 10pt;">the PTT line from the radio must not touch the shield or ground before it gets to the transistor or optocoupler.</span></b></li><li class="MsoNormal" style=""><b><span style="font-size: 10pt;">the PTT line must be wired to the correct pin on the transistor or optocoupler. See <a href="http://www.kc2rlm.info/soundcardpacket/1cableptt.htm">PTT Cable</a> for a schematic. If the PTT <span style="color: rgb(204, 51, 0);">closes</span> when AGWPE transmits, then you most likely have the transistor or optocoupler wiring inverted. (You can test your cable and circuit by using a 9 volt battery to simulate the computer RTS line: plug the PTT cable into the radio and on the computer end of the cable, apply the positive side of the battery to the #7 pin (RTS ) pin and the negative side to the #5 pin (Ground). This should close the transistor/optocoupler gate and the radio should transmit.)
<br /> </span></b></li></ul><li class="MsoNormal" style=""><b><span style="font-size: 10pt;">Windows can start up leaving the COM port handshaking lines "high" (with voltage) instead of "low" as it should. This seems to be limited to ound card interfaces that are wired to use the DTR line to key the transmitter (many commercial interfaces are wired to use either the RTS or DTR line for PTT keying). This has been reported happening with Windows ME and XP; also in other versions of Windows when using a <st1:place st="on"><st1:placename st="on">USB-to-Serial</st1:placename> <st1:placetype st="on">Port</st1:placetype></st1:place> Adapter.
<br />
<br /> For Windows ME: Look first on the Microsoft web site for a Windows fix; see <a href="http://support.microsoft.com/default.aspx?scid=kb;en-us;285894">http://support.microsoft.com/default.aspx?scid=kb;en-us;285894</a> ). </span></b></li></ul> <p style="margin-left: 0.5in;"><b><span style="font-size: 10pt;">Or Roger Barker, G4IDE/SK, wrote a free 20 kb utility, <a href="http://www.kc2rlm.info/programs/hsoff100.zip">HSOFF</a>, that can be used to reset the handshaking lines of a COM port if they are left "high". HSOFF come in a zip file that includes a .TXT file of instructions. (Note that the program needs the Microsoft runtime libraries MSVBVM60.DLL and MSCOMM32.OCX to run. These libraries are installed if you install <a href="http://www.kc2rlm.info/soundcardpacket/7uiview.htm#viewvsview32">UI-View32</a>; and they are also available at some web sites -- do a web search to find them.)
<br />
<br />For Windows XP: Although I couldn't find verification of this problem on the Microsoft web site, it have been said that when Windows XP boots up, it too may leave the DTR (Data Terminal Ready) line of the serial port in a HIGH state. The supposed fix for this is problem is to go to the <span style="color: rgb(0, 153, 153);">Device Manager</span> within Windows XP and remove all of the Communication Ports, or COM ports, as listed under "Ports (COM & LPT)". After doing that, re-boot Windows XP and it will re-install all of the drivers for these ports.
<br /> </span></b> </p> <ul type="disc"><li class="MsoNormal" style=""><b><span style="font-size: 10pt;">It's possible that some other device is affecting the COM/LPT port you have chosen for PTT control. For example, one user forgot that he had an unused adapter "installed" in Windows that was conflicting with the PTT port. Another user reported a conflict with the Palm HotSync Manager, which loads on startup and puts the COM RTS pin high; Windows didn't report that the COM port was being used by the Palm device driver, but it was. Still another user had both the COM port and an infrared port assigned to the same IRQ. Another user suggested that, if your XP machine is running an NVIDIA graphics adapter, some of its drivers are reported to tie up COM1 for no reason -- so disable Nview 2.0.
<br /> </span></b></li><li class="MsoNormal" style=""><b><span style="font-size: 10pt;">Try disabling the <span style="color: rgb(0, 153, 153);">Full Duplex</span> mode of the card. On the <a href="http://www.kc2rlm.info/soundcardpacket/2agwbasic.htm#portsettings">Sound Card Setup screen</a>, <span style="color: red;">un- </span>check <span style="color: blue;">Full Duplex</span>.
<br /> </span></b></li><li class="MsoNormal" style=""><b><span style="font-size: 10pt;">On older/slower computers, the default sound card sampling rate may be too high for the computer to process. You can try using the Windows <span style="color: rgb(0, 153, 153);">Control Panel</span> to adjust the soundcard hardware acceleration and sample rate quality until you find an optimum setting (For example, in Windows XP, you get there by clicking on <span style="color: navy;">S</span><span style="color: rgb(0, 153, 153);">ound and Audio Devices</span>, then click on the <span style="color: rgb(0, 153, 153);">Audio</span> tab. Under <span style="color: rgb(0, 153, 153);">Sound Playback</span>, click on the <span style="color: rgb(0, 153, 153);">Advanced </span>button then click on the <span style="color: rgb(0, 153, 153);">Performance</span> tab.)
<br /> </span></b></li></ul> <h4><span style="color: navy;">3. </span><a name="IntermittentTrans">Intermittent Transmissions</a></h4> <ul type="disc"><li class="MsoNormal" style=""><b><span style="font-size: 10pt;">Sometimes AGWPE will not transmit immediately if AGWPE's automatic timing features are in effect. AGWPE monitors the frequency and uses "slotting" to send your packet when the frequency is not likely to be busy. So, AGWPE is holding the packet for a few seconds before transmitting it.
<br />
<br /> If this delay really bothers you, you can override this feature by setting the timing parameters yourself. Call up the <span style="color: rgb(0, 153, 153);">Properties</span> screen for the radioport, click on the the <span style="color: rgb(0, 153, 153);">Tnc Commands</span> tab, select <span style="color: blue;">Let me Control Parameters</span>. , and then change the Persist and Slot parameters. But remember that AGWPE usually does a very good job of adjusting the timing to match traffic conditions on the frequency. You may make matters worse by controlling them yourself. For example, you may not be as prompt to change parameters when frequency traffic changes.
<br />
<br /> Another reason for a transmit delay is if the sound card is busy processing other sounds from Windows or your application programs. For example, UI-View has an option to announce received callsigns and this slows everything down. Usually there is an option to turn these sounds off in the application, as there is for Windows' sound schemes.
<br /> </span></b></li><li class="MsoNormal" style=""><b><span style="font-size: 10pt; color: rgb(204, 51, 0);">Problem</span></b><b><span style="font-size: 10pt;">: I can send and receive a few packets, but pretty soon transmitting stops, especially if I try to send packets too rapidly. This clears up if I close and restart AGWPE and the packet application, but it just happens again.
<br /> *
<br /> <span style="color: green;">Solution</span>: This seems to happen mostly on computers with older processors. It's possible your computer isn't keeping up with the quick switching that is taking place between the sound card and AGWPE. The computer may have missed a "hand shaking" data segment from AGWPE, so it's waiting for a signal from AGWPE that will never come again. This may mean you need a faster processor or perhaps a sound card driver upgrade to run AGWPE, although you can try to cut the processor load by shutting down other programs and background tasks. Also, see the paragraph above about interruptions of the packet stream.
<br /> </span></b></li><li class="MsoNormal" style=""><b><span style="font-size: 10pt; color: rgb(204, 51, 0);">Note:</span></b><b><span style="font-size: 10pt;"> If transmitting works for a while but then stops, your computer's power management settings may be turning off the sound card and/or the serial ports. </span></b></li></ul> <h4>4. <a name="NoAudio">No audio or poor audio on Transmit</a></h4> <div align="center"> <table class="MsoNormalTable" style="border: 1.5pt outset ; width: 95%;" border="1" cellpadding="0" width="95%"> <tbody><tr style=""> <td style="padding: 3.75pt;"> <p class="MsoNormal"><b><span style="color: rgb(204, 51, 0);">How does my transmit audio sound?</span></b></p> <p><b><span style="font-size: 10pt;">The surest test of your transmitted audio is to use a second radio to listen to the audio transmitted by your first radio. A hand held radio is great for this. Or ask a nearby friend to listen. You should be hearing packets signals from your station that sound similar to the packets you hear from other stations (although perhaps a bit louder and with less noise).</span></b></p> <p><b><span style="font-size: 10pt;">Remember that your audio signal must pass through four ( 4 ) devices that could modify it: </span></b></p> <ul type="disc"><li class="MsoNormal" style=""><b><span style="font-size: 10pt;">the sound card's mixer,</span></b></li><li class="MsoNormal" style=""><b><span style="font-size: 10pt;">the interface cable, </span></b></li><li class="MsoNormal" style=""><b><span style="font-size: 10pt;">the radio and </span></b></li><li class="MsoNormal" style=""><b><span style="font-size: 10pt;">your transmission system, i.e. antenna and feed line.</span></b></li></ul> <p><b><span style="font-size: 10pt;">For example, you can test the audio coming from the sound card mixer by temporarily putting your computer speakers back into the LINE OUT jack. This will give you a fairly good indication of whether you have good volume level settings, but it isn't how your final audio will sound. </span></b></p> <p><b><span style="font-size: 10pt;">Your interface's TX cable has an attenuation circuit or potentiometer that could reduce the audio significantly -- or maybe not enough. As a result, your radio may be receiving audio that is too weak or too loud.</span></b></p> <p><b><span style="font-size: 10pt;">Even your radio may have audio modification circuits in it. Some VHF radios have a "bass boost" option (should be off), and HF radios have speech compression settings (should be off), drive settings (should be turned all the way up) and microphone gain settings (should be left at normal). </span></b></p> <p><b><span style="font-size: 10pt;">And of course your transmission system -- feed line and antenna -- could attenuate your signals.</span></b></p> <p><b><span style="font-size: 10pt;">So the best way to test your audio is to listen to how it sounds on another radio. </span></b></p> </td> </tr> </tbody></table> </div> <p><b><span style="font-size: 10pt;">If you might have a problem with your TX audio:</span></b></p> <ul type="disc"><li class="MsoNormal" style=""><b><span style="font-size: 10pt;">Re-check AGWPE's <a href="http://www.kc2rlm.info/soundcardpacket/3volset.htm#txaudioset">volume settings for Playback (TX audio)</a>. Make sure the <span style="color: rgb(0, 153, 153);">TX Master</span> and <span style="color: rgb(0, 153, 153);">TX Wave</span> settings are <span style="color: rgb(204, 51, 0);">not muted</span> and that none of the four sliders is too close to the bottom of the scale (remember that sliders 1 and 3 control the transmit audio for radioport 1, while sliders 2 and 4 control audio for radioport 2).
<br /> </span></b></li><li class="MsoNormal" style=""><b><span style="font-size: 10pt;">The <a href="http://www.kc2rlm.info/soundcardpacket/1cabletx.htm">attenuation circuit</a> in your TX cable may be over/under attenuating your TX audio. If you have a variable resistor (pot) in the attenuation circuit, try adjusting it. </span></b></li></ul> <table class="MsoNormalTable" style="border: medium none ; border-collapse: collapse;" border="1" cellpadding="0" cellspacing="0"> <tbody><tr style=""> <td style="padding: 5.25pt;"> <h4>Adjusting Your Transmit Audio Level</h4> <p><b><span style="font-size: 10pt;">With TNCs and sound cards you want a transmit audio level that is decodable but not too high. One of the biggest reasons for poor packet performance is <span style="color: rgb(204, 51, 0);">too much audio</span>. If you do not have access to a deviation meter to set the level (you want about 3 KHz of deviation), use a local digipeater and "trial-and-error" to get the lowest audio level that works reliably.</span></b></p> <p><b><span style="font-size: 10pt;">Use a program that can send unconnected packets or a beacon (<a href="http://www.kc2rlm.info/soundcardpacket/7agwsuite.htm#AGWTerm">AGWTerm</a> can send a beacon; <a href="http://users.skynet.be/on1dht/uiss.htm">UISS</a> can send unconnected packets). Set the beacon PATH to relay through the digipeater (e.g. TEST VIA LOCALDIGI), then go into converse mode and transmit a single carriage return. Watch to see if your single packet gets digipeated by that one local digipeater. If it doesn't get through, try several more times because it may not have gotten through because of a collision. </span></b></p> <p><b><span style="font-size: 10pt;">If it does get through, turn down the transmit audio level a little and try again. Keep turning down the audio until your packet reliable DOES NOT get digipeated ... and then turn it back up just a little bit until it does once again.</span></b></p> <p><b><span style="font-size: 10pt;">Remember, in packet, soft is better than loud.</span></b></p> </td> </tr> </tbody></table> <p> </p> <ul type="disc"><li class="MsoNormal" style=""><b><span style="font-size: 10pt;">Are the TX Audio cables connected tightly to the <span style="color: navy;">LINEOUT</span> jack on the sound card of a desktop computer (or the headphones jack on a laptop?)</span></b>
<br /> </li><li class="MsoNormal" style=""><b><span style="font-size: 10pt;">Make sure you are using a stereo plug (has 2 bands below the tip) for the <span style="color: navy;">LINE OUT</span> (TX audio) jack. If you use a mono cable (has 1 band below the tip) you may get only half the audio volume on transmit or you may even short out one channel of the sound card.
<br /> </span></b></li><li class="MsoNormal" style=""><b><span style="font-size: 10pt;">Re-check the soldering and component placement in the <a href="http://www.kc2rlm.info/soundcardpacket/1cabletx.htm">TX cable</a>.
<br /> </span></b></li><li class="MsoNormal" style=""><b><span style="font-size: 10pt;">EMI or RFI: The strong magnetic fields in your monitor may be distorting the signal, or there may be electro-magnetic interference (EMI) from your computer or other nearby devices, or there may be radio frequency interference (FRFI):</span></b></li><ul type="circle"><li class="MsoNormal" style=""><b><span style="font-size: 10pt;">Use a shielded audio cable. Connect the shield to either the sound card ground or the radio's ground but not both.</span></b></li><li class="MsoNormal" style=""><b><span style="font-size: 10pt;">Try using ferrite chokes on the audio cable</span></b></li><li class="MsoNormal" style=""><b><span style="font-size: 10pt;">If you antenna is near your computer, move it further away
<br /> </span></b></li></ul><li class="MsoNormal" style=""><b><span style="font-size: 10pt;">If you have unusual sounds in your transmitted audio or experience delays before AGWPE transmits a packet, it may be that your sound card is getting input from sources other than AGWPE:</span></b></li><ul type="circle"><li class="MsoNormal" style=""><b><span style="font-size: 10pt;">Turn off any sound schemes for Windows.</span></b></li><li class="MsoNormal" style=""><b><span style="font-size: 10pt;">Turn off any sounds that might be generated by your packet applications, for example voice announcements in UI-View.</span>
<br /> </b></li></ul><li class="MsoNormal" style=""><b><span style="font-size: 10pt;">Some radios offer a bass boost function that will distort a packet signal. Make sure you are not using this feature.
<br /> </span></b></li><li class="MsoNormal" style=""><b><span style="font-size: 10pt;">HF: Speech compression should probably be off for digital modes and the Drive adjustment should be turned all the way up (use the <a href="http://www.kc2rlm.info/soundcardpacket/3volset.htm">Volume settings</a> to control transmit power output). Microphone Gain should be set to normal.
<br /> </span></b></li><li class="MsoNormal" style=""><b><span style="font-size: 10pt; color: rgb(204, 51, 0);">If you hear interruptions, or stuttering, of the packet stream</span></b><b><span style="font-size: 10pt;">, it may be because:</span></b></li><ul type="circle"><li class="MsoNormal" style=""><b><span style="font-size: 10pt;">your sound card is not fully capable of full duplex operations (sending and receiving). This is mostly a factor on older 16-bit sound cards. To turn off Full Duplex, go to the <st1:place st="on"><st1:placename st="on">AGWPE</st1:placename> <st1:placetype st="on">Port</st1:placetype></st1:place> properties' <a href="http://www.kc2rlm.info/soundcardpacket/2agwbasic.htm#soundcardproperties">Sound Card Setup screen</a> and uncheck the <span style="color: blue;">Full Duplex</span> box.</span></b></li><li class="MsoNormal" style=""><b><span style="font-size: 10pt;">your computer/or driver is not fast enough. In that case, <a href="http://www.kc2rlm.info/soundcardpacket/2agwbasic.htm">set the Port Properties </a>for <st1:place st="on"><st1:placename st="on"><span style="color: blue;">Single</span></st1:placename><span style="color: blue;"> <st1:placetype st="on">Port</st1:placetype></span></st1:place> use and use only the left channel. Also, set your VGA card accelerator a click below full level and adjust the soundcard hardware acceleration and sample rate quality until you find an optimum setting (these sound card settings are made through the Window Control Panel. For example, in Windows XP, you get there by clicking on <span style="color: rgb(0, 153, 153);">Sound and Audio Devices</span>, then click on the <span style="color: rgb(0, 153, 153);">Audio </span>tab. Under <span style="color: rgb(0, 153, 153);">Sound Playback</span>, click on the <span style="color: rgb(0, 153, 153);">Advanced </span>button then click on the <span style="color: rgb(0, 153, 153);">Performance</span> tab.)</span></b></li></ul></ul> <p style="margin-left: 0.5in;"><b><i><span style="color: rgb(204, 51, 0);">Listen!</span></i></b><b><span style="font-size: 10pt;"> ---> Sample Wav files: one with <a href="http://www.kc2rlm.info/soundcardpacket/WAV/no_stut.wav">no stuttering</a> in packet and one <a href="http://www.kc2rlm.info/soundcardpacket/WAV/STUTTER.wav">with stuttering</a>.
<br />
<br /> </span></b> </p> <ul type="disc"><li class="MsoNormal" style=""><b><span style="font-size: 10pt;">If you hear other noises mixed in with your packets, our sound card is getting input from sources other than AGWPE, such as you CD player or another application:
<br /> </span></b></li><ul type="circle"><li class="MsoNormal" style=""><b><span style="font-size: 10pt;">Go to the <a href="http://www.kc2rlm.info/soundcardpacket/3volset.htm#txaudioset">Volume Control program</a> and mute other input sources for playback, e.g. CD or microphone.
<br /> </span></b></li><li class="MsoNormal" style=""><b><span style="font-size: 10pt;"><a href="http://www.kc2rlm.info/soundcardpacket/3voladd.htm#nosounds">Turn off any sound schemes for Windows</a>.
<br /> </span></b></li><li class="MsoNormal" style=""><b><span style="font-size: 10pt;">Turn off any sound generated by you applications (varies by program; see the program's Help file for possible advice).</span></b></li></ul></ul> <p> </p> <p><b><span style="font-size: 10pt;">If your problem is not resolved by the problem solving pages on this website, join the AGWPE Yahoo Group to ask a question or search the archives for previous postings that may relate to your problem</span></b></p> <h2><span style="color: rgb(204, 51, 0);">Problems with Packet Connections </span></h2> <p><span style="font-size: 10pt;">A. <a href="http://www.kc2rlm.info/soundcardpacket/5probconnect.htm#NotMade">Connections not made</a>
<br />B. <a href="http://www.kc2rlm.info/soundcardpacket/5probconnect.htm#Dropping">Connections not maintained</a>
<br />C. <a href="http://www.kc2rlm.info/soundcardpacket/5probconnect.htm#SlowExchanges">Slow Exchanges</a></span>
<br /><span style="font-size: 10pt;">D. <a href="http://www.kc2rlm.info/soundcardpacket/5probconnect.htm#Diagnosing">Diagnosing Exchange Problems by Packet Type</a></span></p> <h4>A. <a name="NotMade">Connections not made</a></h4> <p><b><span style="font-size: 10pt;">First, make sure you don't have an underlying problem <a href="http://www.kc2rlm.info/soundcardpacket/5probrx.htm">receiving</a> or <a href="http://www.kc2rlm.info/soundcardpacket/5probtx.htm">transmitting</a>. </span></b></p> <ul type="disc"><li class="MsoNormal" style=""><b><span style="font-size: 10pt; color: rgb(204, 51, 0);">I can see on my radio that the PTT has been opened and the radio is transmitting, but I can't connect with another station</span></b><b><span style="font-size: 10pt; color: navy;">.
<br /> </span></b></li><ul type="circle"><li class="MsoNormal" style=""><b><span style="font-size: 10pt;">Are you tuned to the right frequency? Are you operating in duplex mode and transmitting on the offset frequency</span></b></li><li class="MsoNormal" style=""><b><span style="font-size: 10pt;">Does one of the stations have <span style="color: rgb(204, 51, 0);">tone</span> squelch turned on?</span></b></li><li class="MsoNormal" style=""><b><span style="font-size: 10pt;">Consult the <a href="http://www.kc2rlm.info/soundcardpacket/5probtx.htm#NoAudio">No Audio or Poor Audio section of the <span style="color: teal;">Problems with Transmitting page</span></a>.
<br /> </span></b></li></ul><li class="MsoNormal" style=""><b><span style="font-size: 10pt; color: rgb(204, 51, 0);">It looks like the other station heard my connections request and is responding since the radio is receiving packets, but AGWPE is not decoding the packets.</span></b><b><span style="font-size: 10pt;">
<br /> </span></b></li><ul type="circle"><li class="MsoNormal" style=""><b><span style="font-size: 10pt;">Consult the <a href="http://www.kc2rlm.info/soundcardpacket/5probrx.htm">Problems with Receiving page</a>.
<br /> </span></b></li></ul><li class="MsoNormal" style=""><b><span style="font-size: 10pt; color: rgb(204, 51, 0);">I'm having difficulty connecting at 9600 baud.
<br /> </span></b><b><span style="font-size: 10pt;">
<br /> Read the <a href="http://www.kc2rlm.info/soundcardpacket/6modes.htm#9600">9600 baud section of the Baud Rates and Modes page</a> for a discussion of the difficulties or operating 9600 baud packet. Problems could be: your radio is not 9600 capable without modification; incorrect radio settings; using audio transformers in the audio cables; and poor signal quality.
<br /> </span></b></li><li class="MsoNormal" style=""><b><span style="font-size: 10pt; color: rgb(204, 51, 0);">I having difficulty connecting on HF at 300 baud.
<br /> </span></b><b><span style="font-size: 10pt;">
<br /> Use the Sound Card Tuning Aid to help tune your radio to the correct frequency. Also read the <a href="http://www.kc2rlm.info/soundcardpacket/6modes.htm#300%20baud">300 baud section of the Baud Rates and Modes page</a> for a discussion of the difficulties or operating 300 baud packet.
<br />
<br /> </span></b></li></ul> <h4>B. <a name="Dropping">Connections not maintained</a></h4> <ul type="disc"><li class="MsoNormal" style=""><b><span style="font-size: 10pt; color: rgb(204, 51, 0);">When I connect, the other station (a BBS) immediately disconnects me.</span></b><b><span style="font-size: 10pt; color: navy;">
<br /> </span></b><b><span style="font-size: 10pt;">
<br /> You probably have <st1:place st="on"><st1:placename st="on"><span style="color: blue;">Dual</span></st1:placename><span style="color: blue;"> <st1:placetype st="on">Port</st1:placetype></span></st1:place> selected in the <a href="http://www.kc2rlm.info/soundcardpacket/2agwbasic.htm#portsettings">port properties screen</a> and probably have the same baud selected for both ports. Try changing the second port's baud rate to something other than the first. Better yet, if you are not using the second port, select <span style="color: blue;">Single Port,</span> close AGWPE, delete the <span style="color: rgb(0, 153, 153);">port1.ini</span> file from the AGWPE folder (retain <span style="color: rgb(0, 153, 153);">port0.ini</span>, do not delete it) and restart AGWPE.
<br />
<br /> If you are using the second port (to run two different radios from the same sound card) and want to use the same baud rate on both channels, the only know solution is to reduce the receive (RX) audio volume in both channels to the minimum needed to decode packets reliably (find this setting through trial-and-error.) You can do this with the <a href="http://www.kc2rlm.info/soundcardpacket/3volset.htm#AGWRxSet">volume control recording sliders</a>, but it may help to reduce the volume using <a href="http://www.kc2rlm.info/soundcardpacket/1cablerx.htm#mikecable">a voltage attenuator circuit in the RX audio line</a>; or if you are pulling the audio from the radio's speaker jack, turn down the radio's volume control.
<br />
<br /> What seems to be happening is that there is not adequate audio channel separation, i.e. cross-talk, in the sound card, so AGWPE hears both radio ports. In the scenario above, port 1 asks for a connection and the BBS sends a connect confirmation. Because of cross-talk, AGWPE hears this on both port 1 and 2. Realizing this is problem, AGWPE sends a disconnect request, which the BBS accepts and that is the message you see.
<br /> </span></b></li><li class="MsoNormal" style=""><b><span style="font-size: 10pt; color: rgb(204, 51, 0);">I can send and receive a few packets, but pretty soon transmitting stops, especially if I try to send packets too rapidly. This clears up if I close and restart AGWPE and my packet application, but then it just happens again.
<br /> </span></b><b><span style="font-size: 10pt;">
<br /> It may be that your computer isn't keeping up with the quick switching that is taking place between the sound card and AGWPE. The computer may have missed a "hand shaking" data segment from AGWPE, so it's waiting for a signal from AGWPE that will never come again. This may mean you need a faster processor (or perhaps a sound card driver upgrade) to run AGWPE, although you can try to cut the processor load by shutting down other programs and background tasks.</span></b><span style="font-size: 10pt;"> (<b><a href="http://www.sv2agw.com/ham/sc.htm">George, SV2AGW, talks about this problem on his web site.)</a></b></span>
<br /> </li></ul> <h4>C. <a name="SlowExchanges">Slow Exchanges</a></h4> <ul type="disc"><li class="MsoNormal" style=""><b><span style="font-size: 10pt; color: rgb(204, 51, 0);">The other station doesn't seem to hear all my transmission, so my station is sending many repeats.</span></b><b><span style="font-size: 10pt;">
<br />
<br /> Try disabling the <span style="color: rgb(0, 153, 153);">Full Duplex</span> mode of the card. On the <a href="http://www.kc2rlm.info/soundcardpacket/2agwbasic.htm#portsettings">Sound Card Setup screen</a>, <span style="color: red;">un-</span>check <span style="color: blue;">Full Duplex</span>. Some sound cards (usually older ones) have only one 16-bit and one 8-bit channel, so they can not handle both receive and transmit (i.e. full duplex) at 16-bit rates. They compensate by moving one function -- usually transmit -- to the 8-bit channel where the audio signal is not as good. By un-checking Full Duplex, you force the card to alternate between receive and transmit, but it will always use the 16-bit channel.</span></b></li></ul> <table class="MsoNormalTable" style="width: 90%;" border="1" cellpadding="0" width="90%"> <tbody><tr style=""> <td style="padding: 0.75pt;"> <h4><a name="FullDuplex">Is Your Sound Card Full Duplex Capable?</a></h4> <p><b><span style="font-size: 10pt;">Can your sound card send and receive simultaneously? In Windows, you can test for full-duplex capability by launching two copies of Sound Recorder.
<br />
<br /> You'll find Sound Recorder from the Start button: <span style="color: rgb(0, 153, 153);">Programs > Accessories > Entertainment > Sound recorder</span></span></b></p> <p><b><span style="font-size: 10pt;">Repeat the process in the above sentence to launch two copies of the Sound Recorder. You can test for full duplex by playing a file on one Windows Sound Recorder and, while that file is playing, making a recording with the Sound Recorder.</span></b></p> <p><b><span style="font-size: 10pt;">Another way to test is with an AGWPE debugging log. AGWPE asks soundcard drivers if they have Full Duplex capabilities. To see the results of this query:</span></b></p> <ul type="disc"><li class="MsoNormal" style=""><b><span style="font-size: 10pt;">Open the agwpe.ini file in Notepad and edit the file to add these lines:
<br /> <span style="color: blue;">[DEBUG]
<br /> TRACE=3</span></span></b></li><li class="MsoNormal" style=""><b><span style="font-size: 10pt;">When AGWPE restarts it will create an <span style="color: rgb(0, 153, 153);">agwpe.log</span> file. If you open that file with noted pad, you should find a SOUND CARD: FULLDUPLEX line that says either YES or NO, which is the result of AGWPE's query of the card.
<br /> </span></b></li></ul> </td> </tr> </tbody></table> <h4>D. <a name="Diagnosing">Diagnosing</a> Exchange Problems by Packet Type</h4> <p><b><span style="font-size: 10pt;">The following suggestions are based on observations which can be made by running AGWTerm: (download from the <a href="http://www.kc2rlm.info/soundcardpacket/AGWPrograms.htm">AGW Programs</a> page on this site). </span></b></p> <p><b><span style="font-size: 10pt;">When you use AGWTerm to make a connection with another station, you can monitor ALL packets in the exchange by selecting <span style="color: rgb(0, 153, 153);">Window: Unproto Channel</span> from the AGWTerm menu. This will let you see supervisory packets not normally seen in AGWTerm's "receive" window. The type of packet -- SABM, UA, I, RR, REJ -- is identified immediately after the target or VIA station's callsign in the packet, for example here is an RR packet: <span style="color: blue;">1:Fm KC2RLM To SV2AGW <</span><span style="color: red;">RR</span><span style="color: blue;"> P/F R1 ></span></span></b></p> <p><b><span style="font-size: 10pt;">Remember to leave the <span style="color: rgb(0, 153, 153);">Unproto channel</span> window and switch back to the the <span style="color: rgb(0, 153, 153);">Channel 1 </span>window to resume your exchange with the other station. You can not send from the Unproto channel window. </span></b></p> <ul type="disc"><li class="MsoNormal" style=""><b><span style="font-size: 10pt; color: rgb(204, 51, 0);">I'm receiving many REJ packets.
<br /> </span></b><span style="font-size: 10pt;">
<br /> <b>Increase your <span style="color: navy;">TXDelay</span> parameter on the <span style="color: rgb(0, 153, 153);"><a href="http://www.kc2rlm.info/soundcardpacket/6traffic.htm">TNC commands</a></span> tab of the <span style="color: rgb(0, 153, 153);">Properties for Port</span>x<span style="color: rgb(0, 153, 153);"> screen.</span></b>
<br /> </span></li><li class="MsoNormal" style=""><b><span style="font-size: 10pt; color: rgb(204, 51, 0);">I'm sending many REJ packets</span></b><span style="font-size: 10pt;">.
<br />
<br /> <b>Ask the other station to increase his <span style="color: navy;">TXDelay.</span></b>
<br /> </span></li><li class="MsoNormal" style=""><b><span style="font-size: 10pt; color: rgb(204, 51, 0);">I'm seeing a RR packet from the other station, then a RR packet from my station, and then this repeats again and again.</span></b><span style="font-size: 10pt;">
<br />
<br /> <b>The other station is not hearing your acknowledgement of a packet it just sent you. Increase you transmitted audio (Wave "playback" in the sound card volume control) or improve you transmitted signal (higher power, better antenna).</b>
<br /> </span></li><li class="MsoNormal" style=""><b><span style="font-size: 10pt; color: rgb(204, 51, 0);">I'm receiving many RR packets in the same transmission.
<br /> </span></b><b><span style="font-size: 10pt;">
<br /> Increase your <span style="color: navy;">FRACK</span> parameter on the <span style="color: rgb(0, 153, 153);"><a href="http://www.kc2rlm.info/soundcardpacket/6traffic.htm">TNC commands</a></span> tab of the <span style="color: rgb(0, 153, 153);">Properties for Port</span>x<span style="color: rgb(0, 153, 153);"> screen</span>. Consider letting AGWPE resume controlling the parameter.
<br />
<br /> </span></b></li><li class="MsoNormal" style=""><b><span style="font-size: 10pt; color: rgb(204, 51, 0);">I'm sending many RR packets (R1, R2, R3, etc.) in the same transmission.
<br /> </span></b><b><span style="font-size: 10pt;">
<br /> Increase your <span style="color: navy;">RESPTIME </span>parameter on the <span style="color: rgb(0, 153, 153);"><a href="http://www.kc2rlm.info/soundcardpacket/6traffic.htm">TNC commands</a></span> tab of the <span style="color: rgb(0, 153, 153);">Properties for Port</span>x<span style="color: rgb(0, 153, 153);"> screen</span> . Consider letting AGWPE resume controlling the parameter.</span></b><span style="font-size: 10pt;">
<br /> </span></li><li class="MsoNormal" style=""><b><span style="font-size: 10pt; color: rgb(204, 51, 0);"> After receiving a burst of data, AGWPE usually responds, for example, with "RR R3", "RR R4", "RR R5", all in ONE burst. But with this one BBS, AGWPE frequently responds with a short break between "RR R3" and "RR R4". During the break, AGWPE releases the PTT and that results in the BBS sending more data. This new data causes a collision with AGWPE's transmission of "RR R4", and the whole packet exchange slows down dramatically. Why does AGWPE insert that break?</span></b></li></ul> <p><b><span style="font-size: 10pt;">This problem usually results when the sender -- the BBS in this case -- isn't using the AX.25 ver. 2 protocol and has a PACLEN of less than 255 characters. This creates a timing problem in the acknowledgement of packets.</span></b></p> <p><b><span style="font-size: 10pt;">Since you are seeing multiple "RR"s, this means you are probably setting the timing parameters yourself and not letting AGWPE control the timing (AGWPE would probably only send one "RR").<span style="color: red;"> Increase</span> the value of the <span style="color: blue;">RespTime</span> until the problem goes away. Or select let the AGWPE "program adjust parameters"</span></b></p> <p><b><span style="font-size: 10pt;">
<br />If your problem is not resolved by the problem solving pages on this website, join the AGWPE Yahoo Group to ask a question or search the archives for previous postings that may relate to your problem</span></b></p> <p><o:p> </o:p></p> <p class="MsoNormal"><o:p> </o:p></p> <p class="MsoNormal"><o:p> </o:p></p> <p class="MsoNormal"><o:p> </o:p></p> <span style="font-size: 12pt; font-family: "Times New Roman";">
<br /></span><b><span style="font-size: 21.5pt; font-family: "Times New Roman";">OK, you ask, "Now that I can get some packet racket into my computer and decode it, what's next?"</span></b><span style="font-size: 12pt; font-family: "Times New Roman";">
<br />
<br /><b>Check out some local Bulletin Boards (BBS’s)</b>
<br />145.010 for SEA<span style=""> </span>-- just Connect SEA or C SEA and type H for a list of commands such as BBS or NODES or MH for a list of monitored calls from this machine
<br /><b>Do some DX Cluster monitoring for distant stations to work:</b>
<br />145.73 for K7PKT, or via SEA to one of the K7EK clusters
<br /><b>Connect to the EOC and drop off an emergency message:</b>
<br />W7acs-3 w7acs-10 or any of the WINLINK stations below (for our region, roughly north to south):
<br />Edmonds, WA7AUX-10, 145.050 1200baud
<br />Woodinville, KD6GKD-4, 145.670, 1200baud
<br />Duval, K7DV-10, freq?
<br /><st1:place st="on"><st1:city st="on">Bellevue</st1:city></st1:place>, W7EFR-4, 144.950, 1200baud
<br />Sammamish, W7SRG-5, 144.950, 1200baud
<br />Seattle ACS, not currently on map...?
<br />Vashon, W7VMI-11, 445.075, 9600baud
<br />Federal Way, WA7FW-10, 144.930 1200baud
<br />Maple Valley, NS7C-10, 145.030, 1200baud
<br />Maple BValley, KC7KEY-10, 145.030, 1200baud
<br />Tacoma, W7DK-4, 144.910, 1200baud
<br />Puyallup, AA7ZV-10, 145.630, 1200baud
<br />
<br />This system is subject to relentless improvement, please check out
<br />http://www.winlink.org/RMSPacketPositions
<br />for current resource availability
<br />
<br />
<br /><b>Check out all the things you can do with the Automatic Position Reporting System - "APE-Errs" or A.P.R.S...
<br />http://aprs.fi/?call=wr5j&mt=m&z=11&timerange=3600
<br />http://www.nwaprs.info/
<br />http://www.aprs.net/
<br />
<br />
<br />Setup your own bulletin board, gateway or node</b>
<br />
<br /><b>Try out HF Packet</b>
<br />
<br /><b>Connect to the International Space Station or the Shuttle:</b>
<br />Check out http://spaceflight.nasa.gov/station/reference/radio/
<br />and
<br />http://www.issfanclub.com/taxonomy/term/43
<br />and maybe some tracking software like Jtrack or Satscape
<br />http://science.nasa.gov/RealTime/jtrack/
<br />http://www.satscape.co.uk/main/satscape.php
<br />
<br />
<br /><b>Try sending TCP/IP data encapsulated in AX.25 packets:</b>
<br />http://www.wetnet.net/node/759
<br />http://www.microhams.com/binfile/talks/200011.ppt
<br />add: Bob at Boeing 9.6 and Vashon group link...
<br />
<br />Next week - more of the same with APRS and Airmail
<br />
<br />vy 73 de WR5J - Curt
<br />black@nwfirst.com
<br /> <!--[if !supportLineBreakNewLine]-->
<br /> <!--[endif]--></span>WR5Jhttp://www.blogger.com/profile/16316513702643319581noreply@blogger.com0tag:blogger.com,1999:blog-4632435085083780021.post-37859399851947492652009-08-06T08:46:00.000-07:002009-08-06T14:13:52.064-07:00NOTE: As has been the case in the past, the Educational Radio Net Blog post is lacking the graphics that are in the same post on the Yahoo, WA-DIGITAL group. Sorry but it just isn’t working here - and that is bad because I just looked at the post and it is 1/4 the length and 1% of the usefulness. Please go to the Yahoo WA-DIGITAL source or the original location shown below (although I updated the screen shots to the current version for this post (no more German dialog boxes). Please check back before the Wednesday night net for updated info on local packet resources and frequencies, that part isn’t done as of Thursday, August 6, 2009… <br />vy 73 de WR5J – Curt<br />..<br /><br /><br /><br /><span style="font-weight: bold;font-size:180%;" >Blog-Post -10-Packet Radio </span><br /><span style="font-weight: bold;">Finding and installing Flex32 Packet Soundcard Modem Software, Term32, a very simple terminal program and Paxon a more fully featured terminal program to make your packet radio experience as pleasant as possible.</span><br /><br />All the software listed here is for Windows – there are many other versions of the software for most other operating systems. Just go to the original links provided in the tutorial below. For the windows versions, just go to the WA-DIGITAL yahoo group and check in the files section:<br /><br />http://groups.yahoo.com/group/wa-digital/files/<br /><br />Originally from: http://uspacket.org/network/index.php/topic,21.msg23/topicseen.html#new<br /><br /><span style="font-weight: bold;">A huge THANKS! To Charles Brabham, N5PVL for the following information:</span><br /><br />Flex32 / Soundcard Packet for Windows<br /><br />by Charles Brabham N5PVL<br /><br />Many Hams have expressed an interest in Soundcard Packet Radio, and this is understandable! It makes amateur packet radio available to any Ham with a VHF transceiver and a soundcard-equipped computer, at little or no expense. There is soundcard packet software available for DOS, and most modern operating systems including MS Windows, the focus of this article.<br /><br />Some Amateurs are intrigued by the notion of a bit of free software replacing the function of an expensive bit of hardware, others are more interested in the technical triumph that soundcard packet represents, or the performance edge that digital signal processing (DSP) offers. - The point here being that though soundcard packet is the inexpensive alternative, it is also an advanced, great performing one. The FlexNet setup I will describe here can give you measurably better performance than any new packet TNC can offer, fresh out of the box. You can find more general information about FlexNet, and why it performs so well here.<br /><br />FlexNet, with its easy set up, advanced design and high performance is the "best of the best" for this mode. Here is a step-by-step account of how to go about setting up Flex32 with your MS Windows computer's soundcard acting as the TNC. Flex32 is designed to work with all versions of Windows from Win95 on up. Though the details of the setup shown here may differ slightly from yours, it is hoped that it will serve as a general guide.<br /><br />The computer I will be using for the purposes of this article is a 500 MHz Pentium II PC, with a 16-bit Soundblaster sound card and Windows 98 SE. If your sound card is Soundblaster compatible, it should work just as well.<br /><br />The PTT / Soundcard Interface<br /><br />If you only wish to monitor Packet, and do not intend to transmit, then all you need is a cable with the proper plugs to connect the speaker output of your radio to the LINE IN jack on your soundcard. If you have no LINE IN jack on your soundcard, the MIC jack will do just as well.<br /><br />If you wish to go on the air, and are already set up with a soundcard interface for PSK31, SSTV, or other soundcard modes, then all you really need now is the software. In either of these two cases, you should move on to the next section.<br /><br />This section is for those would like to transmit with the soundcard as a TNC, but have no interface and would like to find out something about them.<br /><br />Which Interface?<br /><br />If you only intend to use the soundcard for packet, the following simple interface will give you a Push-To-Talk ( PTT ) signal to key up your radio.<br />Serial Port PTT schematic.<br /><br /><br /><br />A Transistor, a Resistor and a Diode...<br /><br />It cost me just over three dollars to buy the parts, and ten minutes to build the PTT circuit shown above, which allows FlexNet to switch the radio from receive to transmit mode as needed.<br /><br />In addition to this circuit, I had the soundcard's SPEAKER connection going to the radio's microphone plug, and the soundcard's LINE IN connected to the radio's speaker jack so the computer and radio could swap audio. Flex32 uses the soundcard driver to do the rest, processing audio signals to and from the radio to act as an advanced DSP packet modem and TNC.<br /><br />Commercial Soundcard Interfaces<br /><br />The Interface shown above will get you on the air, but for the best performance, the TX and RX audio lines that go between your radio and computer need to be electrically isolated. This prevents a "ground loop" condition that will degrade your audio signal with obnoxious humming noise. The PTT signal should be isolated as well. It is possible (in some cases) to get by with just the Interface above for VHF Packet, but for the HF modes like PSK-31, or for really good performance on VHF Packet, a more serious interface is a must.<br /><br />It is possible to add an optical isolator to the PTT circuit above, and isolation transformers to your audio lines for a home-brew interface, but a simpler solution is to buy a commercial soundcard interface that already has all of these components.<br /><br />There are a number of interfaces on the market, listed in ads in the Ham magazines and on the Internet. My personal favorite and recommended unit is the "Rascal" Interface made by K4ABT "Buck Rogers". The Rascal is available already assembled and tested, or you can order it as a kit for a substantial savings. I put one of the kits together, and found it to be fairly easy and straightforward. Everybody I know who has tried one of these has had good luck with it, but any of the commercial Interfaces will do the job. Choose your favorite, hook it up and go!<br /><br />Getting the Software:<br /><br />The first thing to do is to go the FlexNet web-site:<br /><br />FlexNet Home Page<br />http://www.afthd.tu-darmstadt.de/~flexnet/<br /><br />The Flexnet page has information about the FlexNet E-mail support list, and there is also a link called "Downloading Information". Click this and when it comes up, read the information there and then go on to the "Directory Page" link, at the bottom of the page.<br /><br />From the Directory page, download the following files. They will be the first two files listed on the page:<br /><br />flexnet32.zip<br /><br /># This file contains the Flex32 software, some assorted drivers, and a simple terminal program.<br /><br />soundmodem-flex.zip<br /><br /># This is the soundcard driver module, along with a setup utility. The FlexNet page gives you a link to the web site where the latest version of this driver can be found. Be sure to get the proper version for your operating system.<br /><br />After downloading the two files, create a new directory called C:\FLEX32 , and unzip the files into the new directory. WinZip is a popular shareware program for handling ZIP files.<br /><br />Put the C:\FLEX32 directory in your computer's PATH statement, in C:\AUTOEXEC.BAT. If your autoexec file does not have a PATH statement, add this line to the file:<br /><br />PATH C:\FLEX32<br /><br />This will allow Flex32 compatible programs to bring up the Control center and its drivers automatically on startup. When you run your terminal program, FlexNet comes up "automagically" this way, saving you a few extra mouse-clicks.<br /><br />Setting Up the Software:<br /><br />Before you can set up Flex32, you will need to run the setup program for the soundcard driver, soundmodemconfig.exe... It's hard to miss this file, because the name is so long.<br />________________________________________<br /><br />Run soundmodemconfig, and from the FILE menu, choose NEW, then CONFIGURATION:<br /><br /><br />________________________________________<br /><br />It will ask for a configuration name. I decided to call mine "PVL_CFG"... Any name will do:<br /><br /><br />________________________________________<br /><br />Then it looked like this:<br /><br /><br />________________________________________<br /><br />When you click the configuration name, it highlights and shows the settings on the right. I used COM1 for the PTT:<br /><br /><br />________________________________________<br /><br />Next I clicked the "Channel Access" tab, and set the TXDELAY for 150 ms as shown below. I recommend that you start off with a TXD of 300 ms, then later on try to edge it down as low as you can get it for the best performance. If you start off with your TXD too low, you'll wonder why you can't connect... If you leave it set too high, it will always slow you down.<br /><br />TXDELAY is a parameter that must be custom-set for your particular radio. Some radios need more TXD than others, but they all should be set up with the shortest delay possible, for "snappy" performance on the air. Your radio needs a certain amount of delay... Anything over and above that just slows you down unnecessarily.<br /><br />Once you get everything working good on the air with 300 ms TXD, go back and start edging it down until you start detecting trouble getting a connection, then edge it back up "just a hair". By doing this, I discovered that a radio I had been running at 300 ms "default" TXD for years was really capable of getting by with half as much delay. - Only 150 ms!<br /><br /><br />________________________________________<br /><br />Now go to the FILE menu, choose NEW, then CHANNEL:<br /><br /><br />________________________________________<br /><br />Indicate (highlight) the new channel to see this:<br /><br /><br />________________________________________<br /><br />In the MODE menu, choose: afsk. Do this for both the modulator and demodulator tabs.<br /><br /><br />________________________________________<br /><br />At this point, you should theoretically be ready to go. Test the setup you have by going into the DIAGNOSTICS menu and choosing the SCOPE:<br /><br /><br /><br />I tested the PTT function. It worked! Generally though, if the SCOPE comes up and you get a moving, squiggly line, that's a good sign. When you get this to behave properly, the soundmodem driver is set up, and you're ready to go on to the next section.<br /><br />If the line just won't squiggle, or you get I/O errors upon trying to run the scope, then click here for troubleshooting info.<br /><br /><br />________________________________________<br /><br />FlexNet Control center<br /><br />Look in your Flex32 directory for a file called "Flexctl.exe" ... It will have a "rainbow" icon. This is the FlexNet Control center:<br /><br /><br />________________________________________<br /><br />Go to the TOOLS menu, and choose PARAMETERS:<br /><br /><br />________________________________________<br /><br />The empty PARAMETER screen looks like this:<br /><br /><br />________________________________________<br /><br />Right-click CHANNEL 0, and choose NEW DRIVER:<br /><br /><br />________________________________________<br /><br />From the pop-up menu, choose SOUNDMODEM:<br /><br /><br />________________________________________<br /><br />Another pop-up box will ask for the soundmodem configuration. From the drop-down menu, choose your configuration name. ( PVL_CFG in my case. )<br /><br /><br />________________________________________<br /><br />If you get the following screen, then you have the soundmodem configured for channel 0 in the FlexNet Control center, and are ready to test the installation with a terminal program, on the air!<br /><br /><br />________________________________________<br /><br />TNC32<br /><br />From your desktop, create a shortcut to the file Tnc32.exe, located in your Flex32 directory. This simple term program will get you on the air, and is useful for testing and troubleshooting your installation.<br /><br />Tnc32 is a command-line program. That means a set of parameters must be given along with the program name, in order for it to work. To do this, right-click the icon for Tnc32.exe on your desktop, and choose PROPERTIES from the pop-up menu.<br /><br />Here is how I set mine up.<br />In the TARGET section, I put in: <br /><br />C:\Flex32\TNC32.EXE n5pvl-9 4 4<br /><br />n5pvl-9 - My call with SSID. ( SSID is optional )<br />4 - Number of streams<br />4 - Buffer in kb.<br /><br /><br />________________________________________<br /><br />Now use the shortcut icon you made on your desktop to bring up TNC32.<br /><br /><br />________________________________________<br /><br />To enter a command in TNC32, press the ESCAPE key and a command prompt will appear. Here, I have brought up the command prompt and entered H for Help:<br /><br /><br />________________________________________<br /><br />Here, I connected to the local TheNet node, sent the "I" for "Information" command, so the node would send some text back.<br /><br /><br />________________________________________<br /><br />To quit TNC32, hit the ESCAPE key for the command prompt and enter Q to Quit.<br /><br /><br /><br />________________________________________<br /><br />If I could get it working, so can you! Now you will be wanting a better term program. Only a few term programs work with Flex32. Of those, PAXON is my personal favorite. - A really great Windows Packet Terminal.<br /><br />Final Setup:<br /><br />Once you are set up, running a Flex32 compatible terminal program or application such as TNC32 or PAXON will automatically bring up the FlexNet Control center and its drivers. - Just click the term program and off you go!<br /><br />When you shut down the FlexNet Control center, FlexNet and the soundmodem driver go away completely, leaving the system ready for other soundcard applications. If you want to have FlexNet always there, you can put your term program in your computer's STARTUP folder so that it loads itself and FlexNet automatically at boot-up.<br /><br />Support!<br /><br />The Forum secton here at USPacket.Org is the best place to go for resolving sticky technical problems.<br /><br />Good luck! Charles Brabham, N5PVL<br /><br /><br /><br />On to PAXON<br />http://uspacket.org/network/index.php/topic,20.0.html<br /><br /><br /><br />Paxon Packet Radio Terminal and Flex32<br /><br />by Charles Brabham N5PVL<br /><br />If you have recently set up Flex32, you really owe it to yourself to try out Paxon, a great terminal program that is very efficient with Flex32, directly accessing the FlexNet kernal rather than having to use a driver.<br /><br />The web-site, help files and installation program for Paxon are all in German, but the program comes up ready for English speaking users. This tutorial will guide you through the web-site and installation of this excellent software. - You will find that it is well worth the effort!<br /><br />Getting the Software<br /><br />The first thing to do is to go the download page at the Paxon web-site:<br /><br />Paxon Download Page<br />http://www.paxon.de/download.php<br /><br />The Paxon web-site is all in German, but when you get the software installed, it comes up in English so don't worry about that. In the center of the download page is a link for the file: SetupPaxon1114.exe<br /><br />( 1114 was the version when this tutorial was written. This number will change as new versions are released.)<br /><br />Download this file, and save it somewhere on your hard-drive as a backup installer. You can also install from that location, if you prefer.<br /><br />Setting Up the Software:<br /><br />Run the installation program SetupPaxon1114.exe. ( Or a later version, if available )<br />Choose English as your language unless you prefer some other (German is nice)…________________________________________<br /><br />Here's the opening screen for this installer:<br /><br /><br /><br />Click "Next" to continue...<br />________________________________________<br /><br /><br /><br />This screen wants to be sure that you have read and understood all of the legal mumbo-jumbo. After carefully reading the mumbo-jumbo, choose the I Accept…”, and then click "Next" to continue:<br />________________________________________<br /><br /><br /><br />Now it wants to establish where the program will be installed. It's probably best to go with the default location shown above. Continue as usual, with the "Next" button.<br />________________________________________<br /><br /><br /><br />This is where it sets up a Paxon folder in your START menu:<br />________________________________________<br /><br /><br /><br />Here it puts an Icon on your Desktop: Hit INSTALL to continue<br />________________________________________<br /><br />Click the Run Paxon box and then click “Finish”<br /><br /> <br /><br /><br /><br /><br /><br /><br />This is the Paxon logo flashscreen that comes up when the program starts.<br />________________________________________<br /><br /><br /><br />The first time you run Paxon, you get this little "First Steps" help screen in English. If you want to look at it later, it is in the program's "Help" menu. The actual Windows help files for Paxon are all written in German. If you follow the basic steps outlined here though, all should go well for you.<br />________________________________________<br /><br /><br /><br />Here I have clicked "Tools", then "Settings" to obtain this setup box. It should come up with the "General" tab selected, as shown here.<br /><br />Now I am going to click the "Add" button, in order to enter my callsign and the SSID's I want to use.<br />________________________________________<br /><br /><br /><br />In this little pop-up box, I have entered my callsign, and indicated which SSID's I wanted to use. If you are unsure about what SSID's to use, click the "All" button, before clicking "OK" to move on to the next step.<br />________________________________________<br /><br /><br /><br />Now it displays your callsign and SSID's in the "originating callsigns" box. <br /><br />Finished with this, it is time to click the "Devices" tab, and move on to the next step.<br />________________________________________<br /><br /><br /><br />Right now there are no device drivers listed in the box, so click the "Add" button.<br />________________________________________<br /><br /><br /><br />Choose "PC FlexNet" and click "Add"...<br />________________________________________<br /><br /><br /><br />Now it shows PC FlexNet as your driver. Note that FlexNet is not active yet.<br />________________________________________<br /><br /><br /><br />Assuming you have Flex32 installed and ready to run, clicking "Apply" should cause FlexNet to come up "Ready" as shown here. You may have to manually start Flex32 the first time, but it should come up automatically for Paxon thereafter.<br /><br />If you have trouble getting this to work automatically, create a PATH statement in AUTOEXEC.BAT that shows the path to your FlexNet directory.<br /><br />Once you get FlexNet listed here as "Ready", then click "OK", and on the main (terminal) screen, click the "Connect" button for the next step.<br />________________________________________<br /><br /><br /><br />Now enter the callsign for the Station you want to connect to, then put your own call in the "Callsign" box, and choose which port in your Flex32 installation you want to use for the connect. Here I am connecting to the local FlexNet node, N5PVL-3, with the Soundmodem.<br />________________________________________<br /><br /><br /><br />Hey, it worked! - I hope it works for you too!<br /><br />Try browsing around in Paxon's "Settings" and you will be amazed at all of the nice things this program can do. I find it to be the very best I have ever used for file transfers, remote SYSOP'ing, and as a personal terminal. I hope that you enjoy it too, and that this tutorial has been helpful in getting you started with Paxon!<br /><br />Good luck! Charles Brabham, N5PVL<br /><br /><br /><span style="font-weight: bold;font-size:180%;" >OK, you ask, "Now that I can get some packet racket into my computer and decode it, what's next?"</span><br /><br /><span style="font-weight: bold;">Check out some local Bulletin Boards (BBS’s)</span><br /><br /><span style="font-weight: bold;">Do some DX Cluster monitoring for distant stations to work:</span><br /><br /><span style="font-weight: bold;">Connect to the EOC and drop off an emergency message:</span><br />W7acs-3 w7acs-10 or any of the WINLINK stations below (for our region, roughly north to south):<br />Edmonds, WA7AUX-10, 145.050 1200baud<br />Woodinville, KD6GKD-4, 145.670, 1200baud<br />Duval, K7DV-10, freq?<br />Bellevue, W7EFR-4, 144.950, 1200baud<br />Sammamish, W7SRG-5, 144.950, 1200baud<br />Seattle ACS, not currently on map...?<br />Vashon, W7VMI-11, 445.075, 9600baud<br />Federal Way, WA7FW-10, 144.930 1200baud<br />Maple Valley, NS7C-10, 145.030, 1200baud<br />Maple BValley, KC7KEY-10, 145.030, 1200baud<br />Tacoma, W7DK-4, 144.910, 1200baud<br />Puyallup, AA7ZV-10, 145.630, 1200baud<br /><br />This system is subject to relentless improvement, please check out<br />http://www.winlink.org/RMSPacketPositions<br />for current resource availability<br /><br /><br /><span style="font-weight: bold;">Check out all the things you can do with the Automatic Position Reporting System - "APE-Errs" or A.P.R.S...<br />http://aprs.fi/?call=wr5j&mt=m&z=11&timerange=3600<br />http://www.nwaprs.info/<br />http://www.aprs.net/<br /><br /><br />Setup your own bulletin board, gateway or node</span><br /><br /><span style="font-weight: bold;">Try out HF Packet</span><br /><br /><span style="font-weight: bold;">Connect to the International Space Station or the Shuttle:</span><br />Check out http://spaceflight.nasa.gov/station/reference/radio/<br />and<br />http://www.issfanclub.com/taxonomy/term/43<br />and maybe some tracking sofware like Jtrack or Satscape<br />http://science.nasa.gov/RealTime/jtrack/<br />http://www.satscape.co.uk/main/satscape.php<br /><br /><br /><span style="font-weight: bold;">Try sending TCP/IP data encapsulated in AX.25 packets:</span><br />http://www.wetnet.net/node/759<br />http://www.microhams.com/binfile/talks/200011.ppt<br />add: Bob at Boeing 9.6 and Vashon group link...<br /><br />Next week - more of the same with APRS and Airmail<br /><br />vy 73 de WR5J - Curt<br />black@nwfirst.com<br />206 755-4541cell/fieldWR5Jhttp://www.blogger.com/profile/16316513702643319581noreply@blogger.com0tag:blogger.com,1999:blog-4632435085083780021.post-66294593689166876652009-08-05T12:30:00.000-07:002009-08-06T08:45:27.383-07:00Blog Post 9 – FSK441 and JT6M—High Speed Meteor Scatter Modes by K1JT<meta equiv="Content-Type" content="text/html; charset=utf-8"><meta name="ProgId" content="Word.Document"><meta name="Generator" content="Microsoft Word 11"><meta name="Originator" content="Microsoft Word 11"><link rel="File-List" href="file:///C:%5CDOCUME%7E1%5Ccblack%5CLOCALS%7E1%5CTemp%5Cmsohtml1%5C01%5Cclip_filelist.xml"><link rel="Edit-Time-Data" href="file:///C:%5CDOCUME%7E1%5Ccblack%5CLOCALS%7E1%5CTemp%5Cmsohtml1%5C01%5Cclip_editdata.mso"><!--[if !mso]> <style> v\:* {behavior:url(#default#VML);} o\:* {behavior:url(#default#VML);} w\:* {behavior:url(#default#VML);} .shape {behavior:url(#default#VML);} </style> <![endif]--><o:smarttagtype namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="City"></o:smarttagtype><o:smarttagtype namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="place"></o:smarttagtype><o:smarttagtype namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="address"></o:smarttagtype><o:smarttagtype namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="country-region"></o:smarttagtype><o:smarttagtype namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="Street"></o:smarttagtype><!--[if gte mso 9]><xml> <w:worddocument> <w:view>Normal</w:View> <w:zoom>0</w:Zoom> <w:punctuationkerning/> <w:validateagainstschemas/> <w:saveifxmlinvalid>false</w:SaveIfXMLInvalid> <w:ignoremixedcontent>false</w:IgnoreMixedContent> <w:alwaysshowplaceholdertext>false</w:AlwaysShowPlaceholderText> <w:compatibility> <w:breakwrappedtables/> <w:snaptogridincell/> <w:wraptextwithpunct/> <w:useasianbreakrules/> <w:dontgrowautofit/> </w:Compatibility> <w:browserlevel>MicrosoftInternetExplorer4</w:BrowserLevel> </w:WordDocument> </xml><![endif]--><!--[if gte mso 9]><xml> <w:latentstyles deflockedstate="false" latentstylecount="156"> </w:LatentStyles> </xml><![endif]--><!--[if !mso]><object classid="clsid:38481807-CA0E-42D2-BF39-B33AF135CC4D" id="ieooui"></object> <style> st1\:*{behavior:url(#ieooui) } </style> <![endif]--><style> <!-- /* Style Definitions */ p.MsoNormal, li.MsoNormal, div.MsoNormal {mso-style-parent:""; margin:0in; margin-bottom:.0001pt; mso-pagination:widow-orphan; font-size:12.0pt; font-family:"Times New Roman"; mso-fareast-font-family:"Times New Roman";} h3 {mso-margin-top-alt:auto; margin-right:0in; mso-margin-bottom-alt:auto; margin-left:0in; mso-pagination:widow-orphan; mso-outline-level:3; font-size:13.5pt; font-family:"Times New Roman"; font-weight:bold;} a:link, span.MsoHyperlink {color:blue; text-decoration:underline; text-underline:single;} a:visited, span.MsoHyperlinkFollowed {color:#606420; text-decoration:underline; text-underline:single;} p {mso-margin-top-alt:auto; margin-right:0in; mso-margin-bottom-alt:auto; margin-left:0in; mso-pagination:widow-orphan; font-size:12.0pt; font-family:"Times New Roman"; mso-fareast-font-family:"Times New Roman";} pre {margin:0in; margin-bottom:.0001pt; mso-pagination:widow-orphan; tab-stops:45.8pt 91.6pt 137.4pt 183.2pt 229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt 641.2pt 687.0pt 732.8pt; font-size:10.0pt; font-family:"Courier New"; mso-fareast-font-family:"Times New Roman";} @page Section1 {size:8.5in 11.0in; margin:1.0in 1.25in 1.0in 1.25in; mso-header-margin:.5in; mso-footer-margin:.5in; mso-paper-source:0;} div.Section1 {page:Section1;} /* List Definitions */ @list l0 {mso-list-id:687373788; mso-list-template-ids:1364636558;} @list l1 {mso-list-id:933047878; mso-list-template-ids:-338524432;} @list l1:level1 {mso-level-tab-stop:.5in; mso-level-number-position:left; text-indent:-.25in;} @list l2 {mso-list-id:1235508301; mso-list-template-ids:-520313360;} @list l2:level1 {mso-level-tab-stop:.5in; mso-level-number-position:left; text-indent:-.25in;} ol {margin-bottom:0in;} ul {margin-bottom:0in;} --> </style><!--[if gte mso 10]> <style> /* Style Definitions */ table.MsoNormalTable {mso-style-name:"Table Normal"; mso-tstyle-rowband-size:0; mso-tstyle-colband-size:0; mso-style-noshow:yes; mso-style-parent:""; mso-padding-alt:0in 5.4pt 0in 5.4pt; mso-para-margin:0in; mso-para-margin-bottom:.0001pt; mso-pagination:widow-orphan; font-size:10.0pt; font-family:"Times New Roman"; mso-ansi-language:#0400; mso-fareast-language:#0400; mso-bidi-language:#0400;} </style> <![endif]--> <h3 style="margin: 5pt -0.25in 5pt -27pt;"><a name="6302631280933418248"></a><u><span style="color: rgb(51, 102, 255);"><a href="http://educationalradionet.blogspot.com/2009/07/blog-post-5-fldigi-wrap-up-review-and.html"><span style="color: rgb(51, 102, 255);">B</span></a></span></u></h3><meta equiv="Content-Type" content="text/html; charset=utf-8"><meta name="ProgId" content="Word.Document"><meta name="Generator" content="Microsoft Word 11"><meta name="Originator" content="Microsoft Word 11"><link rel="File-List" href="file:///C:%5CDOCUME%7E1%5Ccblack%5CLOCALS%7E1%5CTemp%5Cmsohtml1%5C01%5Cclip_filelist.xml"><!--[if gte mso 9]><xml> <w:worddocument> <w:view>Normal</w:View> <w:zoom>0</w:Zoom> <w:punctuationkerning/> <w:validateagainstschemas/> <w:saveifxmlinvalid>false</w:SaveIfXMLInvalid> <w:ignoremixedcontent>false</w:IgnoreMixedContent> <w:alwaysshowplaceholdertext>false</w:AlwaysShowPlaceholderText> <w:compatibility> <w:breakwrappedtables/> <w:snaptogridincell/> <w:wraptextwithpunct/> <w:useasianbreakrules/> <w:dontgrowautofit/> </w:Compatibility> <w:browserlevel>MicrosoftInternetExplorer4</w:BrowserLevel> </w:WordDocument> </xml><![endif]--><!--[if gte mso 9]><xml> <w:latentstyles deflockedstate="false" latentstylecount="156"> </w:LatentStyles> </xml><![endif]--><style> <!-- /* Style Definitions */ p.MsoNormal, li.MsoNormal, div.MsoNormal {mso-style-parent:""; margin:0in; margin-bottom:.0001pt; mso-pagination:widow-orphan; font-size:12.0pt; font-family:"Times New Roman"; mso-fareast-font-family:"Times New Roman";} a:link, span.MsoHyperlink {color:blue; text-decoration:underline; text-underline:single;} a:visited, span.MsoHyperlinkFollowed {color:#606420; text-decoration:underline; text-underline:single;} @page Section1 {size:8.5in 11.0in; margin:1.0in 1.25in 1.0in 1.25in; mso-header-margin:.5in; mso-footer-margin:.5in; mso-paper-source:0;} div.Section1 {page:Section1;} --> </style><!--[if gte mso 10]> <style> /* Style Definitions */ table.MsoNormalTable {mso-style-name:"Table Normal"; mso-tstyle-rowband-size:0; mso-tstyle-colband-size:0; mso-style-noshow:yes; mso-style-parent:""; mso-padding-alt:0in 5.4pt 0in 5.4pt; mso-para-margin:0in; mso-para-margin-bottom:.0001pt; mso-pagination:widow-orphan; font-size:10.0pt; font-family:"Times New Roman"; mso-ansi-language:#0400; mso-fareast-language:#0400; mso-bidi-language:#0400;} </style> <![endif]--><span style="font-size:180%;"><a name="6302631280933418248"></a></span><span style="font-size:180%;"><u><span style=";font-family:";font-size:12;" ><a href="http://educationalradionet.blogspot.com/2009/07/blog-post-5-fldigi-wrap-up-review-and.html"><span style="color: rgb(51, 102, 255);">Blog Post 9 – FSK441 and JT6M—</span></a>High Speed Meteor Scatter Modes by K1JT</span></u></span>
<br />
<br /><p class="MsoNormal" style="margin: 0in -0.25in 0.0001pt -27pt;"><i style=""><span style="color: rgb(51, 102, 255);font-size:9;" ><span style=""> </span></span></i><i style=""><span style="font-size:9;"><o:p></o:p></span></i></p> <p class="MsoNormal" style="margin: 0in -0.25in 0.0001pt -27pt; text-indent: 45pt;">Wednesday August 5, 2009</p> <p class="MsoNormal" style="margin: 0in -0.25in 0.0001pt -27pt;"><o:p> </o:p></p> <p class="MsoNormal" style="margin-right: -0.25in;"><b><span style="font-size:16;">This is Curt Black, WR5J, with the Educational Radio Net –<o:p></o:p></span></b></p> <p class="MsoNormal" style="margin-right: -0.25in;"><b><span style="font-size:16;">Please standby for a FSK441 Digital QST <o:p></o:p></span></b></p> <p class="MsoNormal" style="margin-right: -0.25in;"><o:p> </o:p></p> <p class="MsoNormal" style="margin-right: -0.25in;"><b style=""><span style=";font-size:14;color:black;" >Before the net:<span style=""> </span><span style=""> </span>Please download tonight’s software – WSJT, Weak Signal Modes by K1JT and set it up according to the blog and WA-DIGITAL Yahoo Group instructions.<span style=""> </span>You should already have it from Blog Post 8 – we are still using the WSJT software from Joe Taylor, just this week we will use two new modes – FSK441 and JT6M<o:p></o:p></span></b></p> <p class="MsoNormal" style="margin-right: -0.25in;"><b style=""><span style=";font-size:14;color:black;" ><o:p> </o:p></span></b></p> <p class="MsoNormal" style="margin-bottom: 12pt;"><b><span style="font-size:14;">The software at 5.5Mbytes is just a little too big to be downloaded to the Yahoo site, so, if you haven’t yet, folks need to go to the source:<o:p></o:p></span></b></p> <p class="MsoNormal" style="margin-bottom: 12pt;"><b><span style="font-size:14;"><a href="http://physics.princeton.edu/pulsar/K1JT/wsjt.html">http://physics.princeton.edu/pulsar/K1JT/wsjt.html</a><o:p></o:p></span></b></p> <p class="MsoNormal" style="margin-bottom: 12pt;"><b><span style="font-size:14;">and grab the current WSJT version 7.03 – the download will include the users guide in English.<span style=""> </span>Set up as follows:<o:p></o:p></span></b></p> <p class="MsoNormal" style="margin-bottom: 12pt;"><span style=";font-family:Arial;font-size:10;" >
<br /></span><b style=""><span style=";font-family:Arial;font-size:14;" >1. Use the WSJT7 black and white DOS-like window to check your input and output device numbers –
<br />2. then transfer that info to the colorful WSJT7 by K1JT window - look under the SETUP menu - OPTIONS choice and enter the AUDIO IN and AUDIO OUT device numbers you got from the first column on the DOS screen in step 1.
<br />3. Also make sure you have set the MODE menu item to FSK441 and hit the MONITOR button.
<br />4. Also left click on the TOL control (under the DECODE button and above the DEFAULTS button) to set the TOLERANCE to 400, the maximum. <span style=""> </span>A Right Click would decrease the value.
<br />5. Finally, start SPECJT by selecting it under the VIEW Menu. Arrange the windows so you can see each of them during the net<o:p></o:p></span></b></p> <p class="MsoNormal" style="margin-bottom: 12pt;"><b><u><span style=";font-size:14;color:black;" >WSJT</span></u></b><b><span style=";font-size:14;color:black;" > (<i>"Weak Signal communicatons, by K1JT"</i>) is the <u>DIGITAL FSK Meteor Scatter</u> and <u>EME Program</u> <span style=""> </span>and <u>HF DX Program</u> and <u>Weak Signal Propagation Program</u> written by <a href="http://www.qsl.net/w8wn/hscw/papers/archive.html#Nobel"><span style="color:black;">Joe Taylor, K1JT</span></a>.</span></b><b style=""><span style="font-size:14;"> <span style=""> </span>It is amazing – it allows digital communication using protocols explicitly optimized for a number of different propagation modes.</span></b><b><u><span style=";font-size:18;color:yellow;" > <span style=""></span><o:p></o:p></span></u></b></p> <p class="MsoNormal" style="margin-bottom: 12pt;"><b><span style=";font-size:14;color:black;" >Last week we used JT65A which allows worldwide communication on HF or Moonbounce (EME_- Earth Moon Earth contacts with stations that (by moonbounce standards) are quite modest. </span></b><b><span style=";font-size:18;color:black;" ><span style=""> </span><o:p></o:p></span></b></p> <p>To determine <i>EME Path Loss</i> we need to know -</p> <ol start="1" type="1"><li class="MsoNormal" style="">Moon distance from either the transmitting or receiving station</li><li class="MsoNormal" style="">Transmitter station output in watts, expressed as <a href="http://en.wikipedia.org/wiki/Effective_radiated_power" title="Effective radiated power">ERP</a> [roughly transmitter power output (minus feedline loss) x forward antenna gain]</li><li class="MsoNormal" style="">Receive station gain (actual receiver gain minus feedline loss, x antenna gain)</li><li class="MsoNormal" style="">The operating frequency of the transmitter and receiver</li></ol> <p>As the <a href="http://en.wikipedia.org/wiki/Albedo" title="Albedo">albedo</a> of the moon is very low (maximally 12% but usually closer to 7%), and the<span style="font-weight: bold;font-size:130%;" > <a href="http://en.wikipedia.org/wiki/Path_loss" title="Path loss">path loss</a></span> over the <a href="http://en.wikipedia.org/wiki/1_E8_m" title="1 E8 m">770,000 kilometre</a> return distance is extreme --<span style="font-weight: bold;font-size:130%;" > around 250 to 310 <a href="http://en.wikipedia.org/wiki/Decibel" title="Decibel">dB</a></span> -- depending on VHF-UHF band used, <a href="http://en.wikipedia.org/wiki/Modulation" title="Modulation">modulation</a> format and <a href="http://en.wikipedia.org/wiki/Doppler_shift" title="Doppler shift">Doppler shift</a> effects), high power (more than 100 watts) and <a href="http://en.wikipedia.org/wiki/High-gain_antenna" title="High-gain antenna">high-gain antennas</a> (more than 20 dB) must be used.</p> <p>In practice, this limits the use of this technique to the spectrum at <a href="http://en.wikipedia.org/wiki/VHF" title="VHF">VHF</a> and above.</p> <p>The moon <b>must</b> be visible in order for EME communications to be possible.</p> <p class="MsoNormal" style="margin-bottom: 12pt;"><b><span style=";font-size:14;color:black;" ><o:p> </o:p></span></b></p> <p class="MsoNormal" style="margin-bottom: 12pt;"><b><span style=";font-size:14;color:black;" ><span style="font-size:180%;">Enough about Moonbounce – what about Meteor Scatter?<span style=""> </span></span>
<br /></span></b></p><p class="MsoNormal" style="margin-bottom: 12pt;"><b><span style=";font-size:14;color:black;" >Meteor Scatter (MS) allows us to use frequencies that are higher than the “Maximum Usable Frequency” or MUF that is controlled by solar radiation acting on the earth’s upper atmosphere.<span style=""> </span>Instead, we reflect signals in the 2 meter and 70cm signals (144 Mhz to 450 MHz range)<span style=""> </span>back to earth with the trails of ionized gas produced by passing meteors. <o:p></o:p></span></b></p> <p class="MsoNormal" style="margin-bottom: 12pt;"><b><span style=";font-size:14;color:black;" >WSJT/FSK441 is now the primary meteor scatter program and mode over nearly all the world.<span style=""> </span>It is a High Speed MS mode.<span style=""> </span>People have used SSB and Slow CW for meteor scatter work for decades – but it takes a sizable chunk of material to create sufficient ionization to get enough time to say much on either of those modes.<span style=""> </span><u><o:p></o:p></u></span></b></p> <p class="MsoNormal" style="margin-bottom: 12pt;"><b><span style=";font-size:14;color:black;" >However, High Speed Meteor Scatter, HSMS, lets us use much smaller slices of time from the much more common and nearly constant stream of dust and sand being swept up by the earth.<span style=""> </span><o:p></o:p></span></b></p> <p class="MsoNormal" style="margin-bottom: 12pt;"><b><span style=";font-size:14;color:black;" >There are a couple of flavors of HSMS.<span style=""> </span>If I were writing this ten years ago, I would be pointing you to WinMSDSP a program to allow you to send CW at very high speed –when a ping was recorded, the software would slow that ping down and you would decode the CW by ear at whatever speed your skill allowed.<span style=""> </span>HSCW has been largely supplanted by FSK441 with its amazing decode capability thanks to Joe Taylor’s digital skill.<span style=""> </span>Just in case you want to try it, WinMSDSP is available here:<span style=""> </span><a href="http://www.qsl.net/w8wn/hscw/winmsdsp/setup.exe">http://www.qsl.net/w8wn/hscw/winmsdsp/setup.exe</a> <o:p></o:p></span></b></p> <p class="MsoNormal" style="margin-bottom: 12pt;"><b><span style=";font-size:14;color:black;" >HSMS is <u>much</u> more efficient than slow CW or SSB meteor scatter! Also, HSMS is usable <u>every day</u> of the year, not just during the peaks of major showers. <span style=""> </span>This is because HSMS needs only the fractional-second <u>underdense</u> pings of sporadic meteors. These are available just about all the time. It is the best way to get your 144MHz signal out to between 500 and 1200 miles.<span style=""> </span>Grids can be worked that aren't available by most other propagation types.<u><o:p></o:p></u></span></b></p> <p class="MsoNormal" style="margin-bottom: 12pt;"><b><span style=";font-size:14;color:black;" ><span style=""> </span>While we are practicing on 2 meters FM, the typical setup would be a 2 meter sideband rig in USB feeding a horizontally polarized directional antenna pointing toward some group of potential QSO partners or grid square on your need list.<span style=""> </span>All the things that help with weak signal work like good feedlines and some power help but mostly it depends on the ionization of meteors providing a reflector to send your signal back to earth over the horizon.<span style=""> </span>Luckily, even tiny grains of dust and sand are enough to give you a 1/10<sup>th</sup> second ping – and with HSCW or FSK441 you can get both call signs or your report into that tiny window.<o:p></o:p></span></b></p> <p class="MsoNormal"><b style=""><span style="font-size:14;">Specifically:<span style=""> </span><o:p></o:p></span></b></p> <p class="MsoNormal"><b style=""><span style="font-size:14;"> </span></b><span style=";font-size:14;color:black;" ><span style=""> </span><b>FSK441</b> is a high speed meteor scatter mode at 441 baud or about<span style=""> 9000 letters per minute (1800 wpm).<span style=""> </span></span><span style=""> </span><u><span style="">FSK441</span></u><span style=""> uses <u>4-tone Frequency Shift Keying</u>, It contains a number of features to increase its sensitivity and reliability over any other method now available. <span style=""> </span><o:p></o:p></span></span></p> <p class="MsoNormal"><b style=""><span style="font-size:14;"><o:p> </o:p></span></b></p> <p class="MsoNormal" style="margin-bottom: 12pt;"><b style=""><span style="font-size:14;">Every so often, you will see reference to JT44 – that is the old name for JT65.<span style=""> </span>The original JT65 is compatible with JT65A, Joe developed JT65B to have greater tolerance of frequency instability and suggested people move to JT65B, but the most used mode still seems to be JT65A.<span style=""> </span>Check the Sked Pages such as <a href="http://www.obriensweb.com/sked/">http://www.obriensweb.com/sked/</a><span style=""> </span>and click the Digitalradio button.<o:p></o:p></span></b></p> <p class="MsoNormal" style="margin-bottom: 12pt;"><b style=""><span style="font-size:14;">We are exactly one week out from this year’s Perseid Meteor Shower.<span style=""> </span>Check out <o:p></o:p></span></b></p> <p class="MsoNormal" style="margin-bottom: 12pt;"><b style=""><span style="font-size:14;"><a href="http://spaceweather.com/">http://spaceweather.com/</a> <o:p></o:p></span></b></p> <p class="MsoNormal" style="margin-bottom: 12pt;"><b style=""><span style="font-size:14;"><a href="http://science.nasa.gov/headlines/y2009/31jul_perseids2009.htm">http://science.nasa.gov/headlines/y2009/31jul_perseids2009.htm</a><o:p></o:p></span></b></p> <p class="MsoNormal" style="margin-bottom: 12pt;"><b style=""><span style="font-size:14;"><a href="http://www.skyandtelescope.com/observing/highlights/36787804.html">http://www.skyandtelescope.com/observing/highlights/36787804.html</a><o:p></o:p></span></b></p> <p class="MsoNormal" style="margin-bottom: 12pt;"><b style=""><span style="font-size:14;">Recall that your front windshield gets more bugs on it than the back window.<span style=""> </span>For that same reason, on Tuesday night August 11, you might want to set your alarm for the predawn hours <span style=""> </span>of August 12 when our part of the planet will be on the leading edge of plowing through the debris from comet Swift-Tuttle.<span style=""> </span>From SpaceWeather: </span></b>This year's Perseid meteor shower could be even better than usual. "A filament of comet dust that boiled off in 1862 has drifted across Earth's path and when Earth passes through it, sometime between 0800 and 0900 UT (1 - 2 am PDT) on August 12th, the Perseid meteor rate could surge to twice its normal value," says Bill Cooke of NASA's Meteoroid Environment Office.<b style=""><span style="font-size:14;"><o:p></o:p></span></b></p> <p class="MsoNormal" style="margin-bottom: 12pt;"><b style=""><span style="font-size:14;">That grain of sand or piece of dust, as it starts interacting with the atmosphere about 60 miles above the planet, is moving pretty fast – the Dutch Meteor Society has measured thousands of them and the fast ones are around 70 km per second, or about 160,000 miles per hour (recall that 60,000mph of that is just our velocity around the sun)<o:p></o:p></span></b></p> <p class="MsoNormal" style="margin-bottom: 12pt;"><b style=""><span style="font-size:14;">Remember, you don’t need a meteor shower to use the HSMS mode FSK441, but it doesn’t hurt to have lots of activity – and it serves as a reminder to use those rocks to get those grids.<o:p></o:p></span></b></p> <p class="MsoNormal" style="margin-bottom: 12pt;"><b style=""><span style="font-size:14;">If you want to set up a SKED go to <o:p></o:p></span></b></p> <p class="MsoNormal" style="margin-bottom: 12pt;"><b style=""><span style="font-size:14;"><a href="http://www.pingjockey.net/cgi-bin/pingtalk">http://www.pingjockey.net/cgi-bin/pingtalk</a><o:p></o:p></span></b></p> <p class="MsoNormal" style="margin-bottom: 12pt;"><b style=""><span style="font-size:14;"><o:p> </o:p></span></b></p> <p class="MsoNormal" style="margin-bottom: 12pt;"><b><span style="font-family:Arial;"><span style="font-size:180%;">HSMS Resources:</span><o:p></o:p></span></b></p> <pre><b style=""><span style=";font-family:";font-size:12;" >Book:<span style=""> </span>"Beyond Line of Sight",<span style=""> </span>edited by Emil Pocock.<o:p></o:p></span></b></pre> <p class="MsoNormal" style=""><b><a href="http://www.qsl.net/w8wn/hscw/papers.html">http://www.qsl.net/w8wn/hscw/papers.html</a><o:p></o:p></b></p> <p class="MsoNormal" style=""><b><span style="font-family:Arial;"><a href="http://www.qsl.net/w8wn/hscw/hscw.html">http://www.qsl.net/w8wn/hscw/hscw.html</a><o:p></o:p></span></b></p> <p class="MsoNormal" style=""><b><span style="font-family:Arial;"><a href="http://www.nitehawk.com/rasmit/welcome2-1.html">http://www.nitehawk.com/rasmit/welcome2-1.html</a></span></b></p><p class="MsoNormal" style="">
<br /></p><p class="MsoNormal" style="">
<br /><b><span style="font-family:Arial;"> <o:p></o:p></span></b></p> <p style="text-align: center;" align="center"><b><u><span style="font-size:16;"><span style="font-size:180%;">METEOR SCATTER PROCEDURES FOR ITU REGION 2</span>
<br /></span></u></b></p><p style="text-align: center;" align="center"><b><u><span style="font-size:16;"> (N & S America)<o:p></o:p></span></u></b></p> <p style="text-align: center;" align="center"><b><u>From:<span style=""> </span><a href="http://www.qsl.net/w8wn/hscw/hscw.html">http://www.qsl.net/w8wn/hscw/hscw.html</a><span style=""> </span><o:p></o:p></u></b></p> <p>This document describes the <b>Standard Operating Procedures</b> for <b><u>HSMS</u> (<u>HSCW</u> and <u>FSK441</u>)</b> operation throughout the IARU <b>Region 2</b>, North and <st1:place st="on">South America</st1:place>. <b><u>SSB</u></b> and <b><u>slow CW</u></b> procedures are also covered briefly, <u>below</u>.</p> <p class="MsoNormal">In following these procedures, all stations using HSMS for meteor scatter communications within the <st1:country-region st="on"><st1:place st="on">Americas</st1:place></st1:country-region> will be operating in an expected and regular manner, ensuring highest communications efficiency. These procedures are not a set of "rules", but rather an attempt to allow all those operating MS to be confident that <b>every operator knows what the others are doing. </b>This revision reflects the ongoing growth and changes of HSMS operation in Region 2, especially with the addition of FSK441 MS.
<br /><b><u>Note</u></b> - Meteor scatter procedures for <b><u>Region 1</u></b> are <b><u>not</u></b> the same, and <b>EME procedures (worldwide)</b> differ from MS procedures, and also differ on the various bands. See the appropriate documents for more, and use the proper procedures for the region, mode, and band. As the old saying goes, <b><i>"When in <st1:city st="on"><st1:place st="on">Rome</st1:place></st1:city>, shoot Roman candles!"</i></b></p> <p class="MsoNormal"><b>TRANSATLANTIC TESTS</b> - As these tests become more common, it should be publicly announced what set of procedures are being used.</p> <div class="MsoNormal" style="text-align: center;" align="center"> <hr align="center" size="2" width="30%"> </div> <p class="MsoNormal"><b>FREQUENCY DETERMINATION, <u>FSK441 DIGITAL METEOR SCATTER</u></b>:
<br />The stated frequency is the <b>USB dial reading</b>.</p> <p class="MsoNormal"><b>FREQUENCY DETERMINATION, <u>HIGH SPEED CW METEOR SCATTER</u>:</b>
<br />The stated frequency is the signal's <b><u>actual zero-beat frequency</u></b>, or the frequency that would be displayed by a frequency counter during key-down.
<br />Thus, when using audio-tone injection, <b>the dial frequency is the desired zero-beat frequency <u>minus the tone frequency</u></b>.
<br /><i>For example</i>: for a <u>schedule on 144.110</u> - <u>Transmitter VFO</u> is set on <u>144.108 USB</u>, <u>2000 Hz audio tone injected</u>. Sked is thus made for "<u>144.110</u>" (or "<u>144.110 ZB</u>"). <u>Receiving</u> station will want approximately a 1500 Hz tone, so will put the <u>receiver</u> on 144.108.5 USB.
<br />(This is using <b>audio-injection J2A</b> keying. Direct <u>A1A</u> make-break keying <u>cannot be used in <st1:place st="on">North America</st1:place></u> at the normal HSCW speeds).</p> <div class="MsoNormal" style="text-align: center;" align="center"> <hr align="center" size="2" width="30%"> </div> <p class="MsoNormal"><b>METEOR SCATTER SEQUENCING</b>:
<br />On meteor scatter <u>schedules</u> using <b>FSK441</b>, the <u>Western-most station transmits the first calling period</u>. Since <u>30-second periods</u> are used, this would be the first 30 seconds of each minute.
<br />For <b>HSCW schedules</b>, the <u>Western-most</u> station transmits the <u>first</u> calling period (first minute) of each hour and half hour.
<br /><b>NOTE - This is for <st1:place st="on"><u>Western Hemisphere</u></st1:place><u>, Region 2, MS</u>. In all other parts of the world the <u>reverse</u> sequencing is used.</b>
<br />("Western station transmits first" has been the procedure for <st1:place st="on">North America</st1:place> since the 1950's, so it's difficult to try to change now).
<br /><b><u>DXpeditions</u> normally run all schedules and CQs using the same sequence, usually the first period, <u>regardless of direction</u> (<u>recommended</u>).</b>
<br /><b>Also, CQs by <u>any</u> station may be on <u>either</u> period, and commonly are on the first period</b> (because on MS a reply may come from any direction).</p> <div class="MsoNormal" style="text-align: center;" align="center"> <hr align="center" size="2" width="30%"> </div> <p class="MsoNormal"><b>REQUIREMENTS FOR A QSO</b>:
<br />The same as for any mode of operation or propagation - an exchange of <b><u>both call signs</u></b>, an exchange of <b>some type of <u>information or report</u></b>, and an exchange of <b><u>confirmation</u> </b>of reception of the report or information.
<br /><b>When a station copies both calls, he sends calls and report.
<br />If he gets both calls and a report, he sends his report & Roger.
<br />If he gets report and Roger, he sends <st1:city st="on"><st1:place st="on">Rogers</st1:place></st1:city>.
<br />When both get a pair of <st1:city st="on"><st1:place st="on">Rogers</st1:place></st1:city> (you usually need at least two R's to be sure!), the QSO is officially complete. However, the other station will not know this. So it is customary to then send "73" to let the other station know that it's complete, even though the "73" is <u>not</u> required for a complete QSO.<o:p></o:p></b></p> <p class="MsoNormal"><st1:city st="on"><st1:place st="on"><b>Mobile</b></st1:place></st1:city><b>, portable and DXpedition stations normally never send 73 unless they're shutting down, but instead return to calling CQ immediately after the exchange of R's.</b> </p> <div class="MsoNormal" style="text-align: center;" align="center"> <hr align="center" size="2" width="30%"> </div> <p><b>IDENTIFYING</b>: When the schedule progresses to the "Roger, Report" and later sections, <u>calls</u> are no longer being sent. To remain legal, the simplest method is this:
<br />ON <b>FSK441</b>, activate the automatic ID in WSJT so that it will send your <b><i>ID.WAV</i></b> file at the proper time.
<br />On <b>HSCW</b>, every ten minutes jump back to the first (calls-only) transmit buffer for about one second, then immediately return to the current transmit buffer.</p> <div class="MsoNormal" style="text-align: center;" align="center"> <hr align="center" size="2" width="30%"> </div> <p class="MsoNormal"><b>REPORTS, EXCHANGE OF INFORMATION:
<br /></b>Except when something special is required for a contest, an exchange of <b>any</b> additional information is valid for a QSO. The commonly-accepted (and expected) exchange for all <b>HSMS</b> operation is the <b>burst duration-signal strength report (<u>"2-number" report</u>). This is now standard worldwide for HSMS operation</b>.</p> <div align="center"> <table class="MsoNormalTable" style="" border="1" cellpadding="0"> <tbody><tr style=""> <td style="padding: 0.75pt;"> <p class="MsoNormal"><b>FIRST NUMBER (<st1:place st="on">PING</st1:place> DURATION)--<o:p></o:p></b></p> </td> <td style="padding: 0.75pt;"> <p class="MsoNormal" style="text-align: center;" align="center"><b>--SECOND NUMBER (SIGNAL STRENGTH)<o:p></o:p></b></p> </td> </tr> <tr style=""> <td style="padding: 0.75pt;"> <p class="MsoNormal"><b>1 - Ping with no info. (Not sent)<o:p></o:p></b></p> </td> <td style="padding: 0.75pt;"> <p class="MsoNormal"><b><o:p> </o:p></b></p>
<br /></td> </tr> <tr style=""> <td style="padding: 0.75pt;"> <p class="MsoNormal"><b>2 - ping, up to 5 sec in length<o:p></o:p></b></p> </td> <td style="padding: 0.75pt;"> <p class="MsoNormal"><b>6 - up to S3 in strength<o:p></o:p></b></p> </td> </tr> <tr style=""> <td style="padding: 0.75pt;"> <p class="MsoNormal"><b>3 - 5-15 sec in length<o:p></o:p></b></p> </td> <td style="padding: 0.75pt;"> <p class="MsoNormal"><b>7 - S4 to S5<o:p></o:p></b></p> </td> </tr> <tr style=""> <td style="padding: 0.75pt;"> <p class="MsoNormal"><b>4 - 15-60 sec burst<o:p></o:p></b></p> </td> <td style="padding: 0.75pt;"> <p class="MsoNormal"><b>8 - S6 to S7<o:p></o:p></b></p> </td> </tr> <tr style=""> <td style="padding: 0.75pt;"> <p class="MsoNormal"><b>5 - over 60 sec burst<o:p></o:p></b></p> </td> <td style="padding: 0.75pt;"> <p class="MsoNormal"><b>9 - S8 and stronger<o:p></o:p></b></p> </td> </tr> </tbody></table> </div> <p class="MsoNormal">(In <u>Australia</u> where all MS operation is FSK441, there is a slight modification of this, with "06" meaning "20 ms, 0 to 10 dB," "17" meaning "40 to 80 ms, 11 to 16 dB," etc. See their HSMS Web sites for more).
<br />Note that there cannot be any confusion between the first and second number as the ranges do not overlap; also note that the second number is <b>not</b> itself an "S-meter reading". (The duration report suggested here is slightly different from the European standard and also from some of the older North American charts).
<br /><b>This is now the preferred exchange for HSMS operation</b>. But, <b>if</b> the other station uses a different reporting system, simply copy what he sends and send your report.
<br />The typical ping will have a Burst Duration of 2, a Strength of 6. (This <b>is</b> a weak-signal mode).
<br /><b>Once you have started sending a report, it is <u>NOT</u> changed during that schedule, even though you suddenly get a much better burst</b>. <i>E.g.,</i> if you start sending "26", this is the report you would continue to send, even if you next get a "38-quality" ping. Changing the report could result in the loss of a contact.</p> <p class="MsoNormal"><b>Note on WSJT's FSK441 North American reporting:</b> The #2 Standard Text Box defaults to <i>"Firstcall report Secondcall report report"</i> (e.g., <i>K1JT 26 W8WN 2626</i>). The reason for this format is to allow monitoring stations to tell which station they're hearing. Since the pair of calls is the longest string of text to exchange, lower-power stations may find it advantageous to change this to <i>"Firstcall report Secondcall report"</i> or even <i>"Firstcall Secondcall report."</i>
<br />This change is <u>definitely</u> recommended for contests when the <st1:street st="on"><st1:address st="on"><b>Grid Square</b></st1:address></st1:street> is required for the report.</p> <p class="MsoNormal">Other sometimes-used exchanges:
<br />Burst length "<b><u>S</u></b>" report. Standard in <st1:place st="on">North America</st1:place> since the 1950's for <u>slow CW</u> and later for <u>SSB</u>.
<br /><u>Grid square</u>. <u>Required for most contests</u>. Sometimes used by portable or /MM stations; however, on FSK441, it is becoming common for the portable or /MM station to include their current grid in the CQ . The grid square normally should <u>not</u> be used on HSMS for the report except for contests.</p> <div class="MsoNormal" style="text-align: center;" align="center"> <hr align="center" size="2" width="30%"> </div> <p class="MsoNormal"><st1:city st="on"><st1:place st="on"><b>ROGERS</b></st1:place></st1:city><b> - HOW MUCH IS ENOUGH?</b>
<br />An exchange of Rogers (R's) is necessary to complete a contact, regardless of the mode. But how many R's are required? It's much like the old question, <i>"How many angels can dance on the head of a pin?"</i>
<br />Regardless of mode, only one (1) Roger is actually required. But are you <u>sure</u> you received it? Was it <u>really</u> an R? Many EME and MS operators have been greatly saddened to learn that the "definite R" they received was actually another letter, chopped up! This is why most operators don't trust conditions and their hearing to accept a single, isolated R, but prefer to have 2 or more.
<br />So how many R's are required? <u>As few or as many as you need to feel comfortable that you have it!</u> If you rely on only a single R, many times you'll be correct. But all too often you'll later learn that the other station was not sending R's and the contact was not completed. (Those of us who have been on MS and EME for awhile have experienced this all too often - from both ends!)</p> <div class="MsoNormal" style="text-align: center;" align="center"> <hr align="center" size="2" width="30%"> </div> <p><b>MISSING INFORMATION</b>:
<br /><b>On High-Speed CW MS operation, it is possible to request a missing piece of information.
<br />Note - this does not work as well for FSK441, but could possibly be used.</b> (On FSK441, it's best to just <b>ask</b> for the needed information as these letters are likely to be interpreted as only gibberish).</p> <p class="MsoNormal"><b>BBB</b> - <b>B</b>oth call signs needed
<br /><b>MMM</b> - <b>M</b>y call sign needed
<br /><b>YYY</b> - <b>Y</b>our call sign needed
<br /><b>SSS</b> - Report (or whatever report/information exchange used) needed (some have suggested <b>GGG</b> for needing the grid)
<br /><b>UUU</b> - <b>U</b>r keying is unreadable
<br />(Use "U" when needed. Remember that the other station cannot monitor his keying).
<br /><b>These "requests for repeat" letters are used <u>only</u> when the other station mis-copies something and <u>jumps ahead</u> in the sequence. Thus, they are seldom needed (but <u>very</u> valuable at that time).</b>
<br />When these are used, <b><u>nothing</u></b> but the appropriate string of letters is sent. (E.g., "YYYYYYYYYY").
<br /><u>The other operator should respond by sending <b>only</b> the requested information</u>. (E.g., "W8WN W8WN W8WN").
<br />When the requesting operator has the needed data, he returns again to the proper exchange sequence.</p> <div class="MsoNormal" style="text-align: center;" align="center"> <hr align="center" size="2" width="30%"> </div> <p class="MsoNormal"><b>HSCW SPEEDS</b>:
<br />For <b>CQs</b>, a speed of 6000 lpm has now become standard in <st1:place st="on">North America</st1:place>, with most schedules run between 6000 and 10,000 lpm.</p> <p><b>HSCW SCHEDULES</b> - <u>always</u> determine what speed the other operator wishes to use. If you are very far off the other station's speed, not only is copy impossible, you can't even tell whether he's a lot faster or slower than your settings!
<br /><b>The most <u>effective</u> schedule speeds with current equipment and techniques are<u> 6000-10,000 lpm</u>.</b> The signal-to-noise ratio becomes poorer above about 12,000 lpm; thus, higher speeds are not recommended for <b>routine</b> operating, although a number of stations are testing various techniques for use at these higher speeds.</p> <p style="text-align: center;" align="center"><b>FREQUENCY USE</b>:</p> <p><b>SCHEDULES</b>:
<br />Schedule frequencies are arranged between the two individual stations on any seemingly unused frequency.
<br />On <b>144 MHz</b>, North American HSMS operation is normally conducted between 144.100 and 144.200 to avoid interference with EME operation below 144.100, and with SSB operation near and above 144.200.
<br />(Remember, in the <st1:country-region st="on"><st1:place st="on">US</st1:place></st1:country-region>, frequencies below 50.1 and 144.1 are <u>CW only</u>).</p> <p class="MsoNormal">At this time, most <b>50 MHz</b> schedules are being made between 50.240 and 50.310.
<br />Schedules should always be made at least 5 kHz away from the calling (CQ) frequencies.
<br />(Speeds, frequency, exact procedures, etc., must <u>always</u> be <b>confirmed</b> between the two stations, <b><u>especially</u></b> if something different from the standard procedure is desired or one of the operators is new to this mode).</p> <p><b>CALLING CQs - no offset:
<br /><u>On 2 meters - 144.140 dial for FSK441 and 144.100 zero-beat for HSCW</u>.</b> Call, listen, and operate on the <u>same</u> frequency, <b>unless</b> there seem to be several stations operating there. If this is the case, the <b><u>CQ-Letter</u></b> or <b>Uxx/Dxx</b> method should be used.
<br /><b><u>On 50 MHz - 50.260 dial for FSK441 and 50.300 zero-beat for HSCW</u></b>.
<br />Either period may be used, since they could be answered from any direction (see <i>sequencing</i>).
<br /><b>HSMS CQs on other frequencies are almost certain to be unsuccessful unless they have been announced on the proper real-time Web site.</b>
<br />Note - except during contests or other periods of high activity, it is always necessary to announce that you are going to call a CQ.
<br />For <b>other VHF/UHF bands</b>, no calling frequencies have been decided on. Due to the difficulty of operating MS on <b>220</b> and <b>432</b>, all operation is currently by means of schedules.</p> <p class="MsoNormal"><b>CQ, OFFSET LISTENING:</b>
<br /><b>FSK441</b> - If it is apparent that there are several operating, immediately following the letters "<b>CQ</b>", a specific <b>letter and number</b> are inserted to indicate the frequency that will be used for <b>reception</b> when the CQ sequence ends.
<br /><i>For example</i>: <b><i>"CQU5"</i> means <i>"I'm <u>listening</u> and <u>will reply</u> Up 5 kHz."</i></b>
<br /><b><i>"CQD8"</i></b> means <i>"I'm listening and will reply <b>Down 8 kHz"</b></i>.
<br /><b>The offset frequency is always <u>relative</u> to the CQ frequency.</b> Thus, <b><i>"CQU8"</i> on 144.250</b> would mean that the contact will take place on <b>144.258 MHz</b>. (144.250 is not a good frequency for an HSMS CQ, but is simply used as an example).
<br />When using FSK441, instead of sending Up or Down, you could <u>specify the actual frequency</u>, such as <b><i>"CQ 123"</i></b> would mean <b><i>"I am listening and will answer on 144.123 MHz."</i></b>
<br />When the CQing station hears a call on the <b><u>offset</u></b> frequency (<b><u>not</u></b> on the CQ frequency, for <u>he is <b>not</b> listening there</u>), he/she immediately then also <b>moves</b> to the <b><u>offset</u></b> frequency, and the QSO takes place <b><u>there</u></b> with <b><u>BOTH</u></b> stations now <u>transmitting</u> and <u>receiving</u> on the <u>new</u> designated frequency.</p> <p class="MsoNormal"><b>HSCW</b> - If it is apparent that there are several operating, immediately following the letters "<b>CQ</b>", a specific <b>letter</b> is inserted to indicate the frequency that will be used for <b>reception</b> when the CQ sequence ends. <u>This letter indicates the frequency offset from the actual CQ calling frequency used</u>. For example, <b><i>"CQE"</i> </b>would indicate that <b>the CQing station would <u>listen</u> 5 kHz above his CQ frequency</b>. In all cases the letter used indicates a frequency <b>higher</b> than the CQ frequency. When the CQing station hears a call on the <b><u>offset</u></b> frequency (<b><u>not</u></b> on the CQ frequency, for <u>he is <b>not</b> listening there</u>), he/she immediately then also <b>moves</b> to the <b><u>offset</u></b> frequency, and the QSO takes place <b><u>there</u></b> with <b><u>BOTH</u></b> stations now <u>transmitting</u> and <u>receiving</u> on the <u>new</u> designated frequency.
<br /><i>For example</i>:
<br />CQC - Up 3 kHz
<br />CQE - Up 5 kHz
<br />CQZ - Up 26 kHz
<br />CQAA - Up 27 kHz. Etc.</p> <p>Note that the letter indicates <u>the number of kHz <b>higher</b></u> than the CQ frequency. It does <b>not</b> indicate any <b>specific</b> frequency. Thus, if a DXpedition is using some <u>other</u> frequency for CQs, the letter again indicates<b> the number of kHz <u>higher</u></b> where they are listening and to which they will <b>QSY</b> for QSO attempts.</p> <p class="MsoNormal"><b>CQ with <st1:street st="on"><st1:address st="on">GRID SQUARE</st1:address></st1:street></b> - It is now common for /MM, /M, and portable stations (who may change locations) to <b>include <u>their</u> <st1:street st="on"><st1:address st="on">Grid Square</st1:address></st1:street> in the CQ</b>. This enables the receiving stations to know the location of the portable/mobile station, and whether or not they need that particular grid square. Thus, W1LP/MM might call <b><i>"CQ W1LP EL62"</i></b>. This is <u>not</u> recommended for fixed stations - it adds unnecessary information to the CQ, as the locations of most fixed stations are usually already known.</p> <p><b>ANSWERING A CQ:
<br /></b>If it is only a <b>straight CQ</b>, you transmit and receive on the frequency that is being used for the CQ.
<br />If it is a <b>CQ-letter</b> or a <b>CQUxx or CQDxx</b>, you <b>change both your transmitter <u>and</u> receiver to the indicated frequency</b>.
<br />You then <b>call <u>and</u> listen</b> on this <b><u>new</u></b> frequency. When (if) the CQing station copies both calls,<b> he will <u>also</u> QSY to this new frequency</b> and the contact will take place <b>there</b>.
<br /><b>WARNING</b> - Even during a major shower, pings may be few and far between. When you reply to a CQ, do <b>not</b> quit after only a few minutes. It may require 20 minutes, 30 minutes, or longer before the CQing station copies your call and you get a ping back from him. <b>Plan to continue calling for a while.</b>
<br />When you call the CQing station, you use the standard 1x1 calls (e.g., <i>W4HHK N1BUG W4HHK N1BUG</i>, etc. - <b><u>NO</u> reports</b>. [This is different in <st1:place st="on">Europe</st1:place>]).
<br />When the CQing station copies you (on the <b>new</b> frequency, if a <b>CQ-letter</b> or <b>CQUx or CQDx</b> has been used), he will respond with <b>both calls and a report.
<br /></b>The calling station continues with the 1x1 calls until he copies the calls and report, then switches to the <b>Roger-Report</b>, and then on through the usual sequence.
<br />(If the CQing station gets only <b>partial</b> calls, he should <b>QSY</b> and call <b><i>"QRZ?</i>"</b> on the <b>new</b> frequency).</p> <div class="MsoNormal" style="text-align: center;" align="center"> <hr align="center" size="2" width="30%"> </div> <p class="MsoNormal"><b>OTHER</b>:
<br />Schedules are <b>always</b> made in <b>Universal Time</b>. However, for evening schedules, the <u>local</u> time/day may <b>also</b> need to be stated to be certain that the date is understood properly.</p> <div class="MsoNormal" style="text-align: center;" align="center"> <hr align="center" size="2" width="30%"> </div> <p class="MsoNormal"><b>USE OF THE WEB, HF, ETC, DURING A CONTACT</b>:
<br />The Internet has made the setting up of schedules, checking results, real-time help, etc, very easy. Its use (and other, similar methods) are always encouraged for these purposes.
<br />But what about confirming individual portions of a contact in real time, <u>while the contact is in progress?</u> (E.g., <i>"OK, I have your calls and report, I'm sending R26s now"</i>, etc).
<br />This depends upon the <u>purpose</u> of the attempted contact. <b>For many contests, this is <u>not</u> allowed. And if contact by any other means is made while the attempted VHF contact is in progress and any information concerning the contact is exchanged, the contact must be restarted again from the beginning.</b>
<br />For claiming a record, or for a new state, etc, while not technically "illegal", it is <b>strongly frowned on and discouraged</b>. <u>Most VHF operators do not communicate with the other station by the Internet (or similar means) from the time the contact has started until it has obviously been completed</u> (i.e., one station has received "73").
<br /><b>Obvious exceptions</b> to this would be if there's a major problem at either end (need to change frequency, rig problems, the other signal is not readable, etc), or <u>incidental</u> comments having <u>nothing to do with the contact in progress</u>.
<br />For <u>routine contacts, tests, experiments, etc.</u> with a station you've worked many times, obviously there's nothing wrong with comments concerning the contact, for you won't even bother exchanging QSLs again. And the Internet is a great way to help fellows set up their rig, learn the proper procedures, and get things operating properly.
<br /><b>The bottom line is, what is the <u>purpose</u> of the VHF contact?</b> If it's really to make this <b><u>VHF Contact</u></b>, it should be made on <u>VHF</u> with <u>no</u> outside help, once the schedule is set up and started. If it's completely <u>routine</u>, one contact of many with that station, <u>for tests or help</u>, etc, and it really doesn't matter whether or not the contact is completed, then it really doesn't matter what else you're doing at the same time.</p> <div class="MsoNormal" style="text-align: center;" align="center"> <hr align="center" size="2" width="30%"> </div> <p>These are the current <b>HSMS Procedures</b> for <b><u>Region 2</u></b>. If you wish to experiment with <u>variations</u>, that is up to you and the other station; this is the way the procedures grow and improve. But by using these for <u>routine</u> operating, you are less likely to disappoint the other station by seemingly failing to show up for the schedule, or by not knowing what to do!</p> <div class="MsoNormal" style="text-align: center;" align="center"> <hr align="center" size="2" width="30%"> </div> <p class="MsoNormal"><b>SSB METEOR SCATTER PROCEDURES FOR REGION 2:
<br /><u>SSB</u></b> exchange requirements and procedures are the same as HSMS procedures, with the following <u>changes</u>:</p> <ol start="1" type="1"><li class="MsoNormal" style="">The period is normally <b>15 seconds</b>, with the <b>Western</b> station again calling <b>first</b> at the start of each minute.</li><li class="MsoNormal" style=""><b>Random</b> MS operation does not necessarily follow an exact sequence<b>. Break-in</b> is commonly used.</li><li class="MsoNormal" style="">Information exchange (report) is usually <b>the burst-length "S" report</b> (S1 through S5) <b>on schedules, Grid Squares</b> on <b>random</b> contacts. For random contacts, yet other exchanges are sometimes heard.</li><li class="MsoNormal" style=""><b>Phonetics</b> must be used for <b>random</b> operation; they should <b>not</b> be used for <b>schedules</b>.</li><li class="MsoNormal" style="">For CQs, the usual SSB calling frequencies are usually used during periods of low activity. However, during the peaks of major showers, they quickly become overcrowded. Frequencies every 5 kHz above and below the calling frequencies are then commonly used.</li><li class="MsoNormal" style="">On SSB, attempts are usually made to complete the entire QSO on a single long burst. Thus<b>, <u>break-in</u></b><u> procedures</u> should be used whenever possible.</li></ol> <div class="MsoNormal" style="text-align: center;" align="center"> <hr align="center" size="2" width="30%"> </div> <p class="MsoNormal"><b>"SLOW" CW (UNDER 50 WPM) MS PROCEDURES FOR REGION 2:
<br /></b>Again, the procedures for <b><u>CW</u></b> are the same as for HSCW or SSB, with the following <u>changes</u>:</p> <ol start="1" type="1"><li class="MsoNormal" style="">The period may be 15, 30, or 60 seconds. Thus, this <b>must</b> be stated.</li><li class="MsoNormal" style="">The exchange (report) is normally <b>the burst-length "S" report</b>.</li><li class="MsoNormal" style="">Random CQs may follow the 15-second sequence, or they may be short calls with a break.</li></ol> <div class="MsoNormal" style="text-align: center;" align="center"> <hr align="center" size="2" width="30%"> </div> <p class="MsoNormal" style="text-align: center;" align="center"><b><u>JT44/JT65 OPERATION</u></b>:</p> <p class="MsoNormal"><b>JT44 and JT65</b>, other weak-signal modes of <b>WSJT</b>, are useful for distances too short for meteor scatter operation but where tropo scatter might be possible, and especially for EME operation. They should also be good for TE, IOS, and other modes of propagation where the signal is expected to be very weak but more or less steady.
<br />For <b>terrestrial JT44/JT65 operation</b> (i.e., not EME), procedures, sequencing, etc., may be <b>either</b> the same as for MS <b>or</b> for EME! Therefore, the sequencing must be stated and agreed on prior to each schedule.
<br />Frequencies used are in the same portion of the band as used for meteor scatter operation. There is no commonly-accepted frequency for CQs, though <b>144.163</b> has been proposed.</p> <p class="MsoNormal">For <b>JT44/JT65 EME operation</b>, the procedures are generally the same as worldwide EME procedures for the band in question, except for the length of the transmit period (30 seconds for JT44, 60 seconds for JT65).
<br />On 144 MHz, two sets of frequencies are currently in use - 144.105-144.135 and 144.145-144.170. EME JT44/JT65 CQs are most often simply announced on the JT44 EME Web page.
<br />Japanese stations must operate above 144.4.
<br />(Remember, in the <st1:country-region st="on"><st1:place st="on">US</st1:place></st1:country-region>, frequencies below 50.1 and 144.1 are <u>CW only</u>).</p> <p class="MsoNormal">This "Procedures" paper is primarily for <u>meteor scatter</u> operation. <b>JT44/JT65</b>, both EME and terrestrial, are too new for all of the procedures to have been worked out. If you have questions, people on the "Ping Jockey" and "JT44" real-time web pages, as well as the "HSMS/JT44 Reflector," should be able to give you the latest information.</p> <div class="MsoNormal" style="text-align: center;" align="center"> <hr align="center" size="2" width="30%"> </div> <p class="MsoNormal" style=""><b>FOR MORE INFORMATION:
<br /><u>Region 1</u></b> Meteor Scatter procedures can be found at URL <b>http://www.scit.wlv.ac.uk/vhfc/iaru.r1.vhfm.4e/5B.html</b>. (Due to be revised soon).
<br />This <b>Region 2</b> document covers only the basic <b>procedures</b>. For more <b>General HSCW information</b>, go to <b>http://nitehawk.com/rasmit/ws1_15.html</b> or <b>http://www.qsl.net/w8wn/hscw/hscw.html, and follow the links</b>. Charts and many other papers are available to assist with both operating and technical information.
<br />To download the latest version of <b>WSJT</b>, go to http://pulsar.princeton.edu/~joe/K1JT/, or the mirror site at www.vhfdx.de.
<br />To keep up with what is happening on meteor scatter, JT44 operation, and general VHF news, check the <b>Hot News Page</b> regularly at <b><a href="http://www.qsl.net/w8wn/hscw/papers/hot_news.html">http://www.qsl.net/w8wn/hscw/papers/hot_news.html</a></b>.</p> <p class="MsoNormal" style=""><o:p> </o:p></p> <p style="text-align: center;" align="center"><b>WHAT IS THE BEST TIME FOR METEOR SCATTER OPERATION?</b></p> <p class="MsoNormal"><b><u><span style="font-size:10;">SPORADIC METEORS</span></u></b><span style="font-size:10;"><o:p></o:p></span></p> <p><span style="font-size:10;">In the <b>morning</b> hours, around 0600 local time, that part of the earth is facing the same direction as the direction of travel of the earth in its orbit around the sun. Thus, not only are meteors swept up which are heading toward the earth, but the movement of the earth around the sun allows it to catch up with some of the slower meteors and pull them in, also.<o:p></o:p></span></p> <p><span style="font-size:10;">On the <b>evening</b> side (facing away from the direction of the earth's orbit), the only meteors reaching the earth are those which can overtake it.<o:p></o:p></span></p> <p><span style="font-size:10;">The best time for <u>visual</u> observing is considered to be between 2 and 4 am local time. This is because during the season when the sporadics are at their peak (summer), the sky brightness is increasing after 4 am.<o:p></o:p></span></p> <p><span style="font-size:10;">It must be remembered, however, that many or probably most "sporadic" meteors are actually the remains of long-gone showers. Thus, on a given day, there could be meteors from 5 or 6 of these "extinct" showers hitting the atmosphere, causing an enhancement at an unexpected time.<o:p></o:p></span></p> <p><span style="font-size:10;">There is a considerable seasonal variation of sporadics, also, with February being the low month and July being the highest. (KB0VUK has a chart of this on his Web page). Note the number of major and minor showers in the June-September period and the reason for this will become obvious.<o:p></o:p></span></p> <p><span style="font-size:10;">There are also several other factors that influence the number of sporadics, and also the ratio of morning to evening. But these are not that important. Just be aware that the variation can be significant month to month, day to day, and even minute to minute!<o:p></o:p></span></p> <p><span style="font-size:10;">The best reference for MS operation is still the second article by <b>W4LTU</b>, reprinted in<i> "Beyond Line of Sight"</i> (available from the ARRL). <u>This is <b>NECESSARY</b> reading for anyone thinking of MS operation</u>. Also, see the <b>text files</b> that accompany <b>OH5IY's MS-Soft program</b>.<o:p></o:p></span></p> <p><span style="font-size:10;">Yes, <b>HSMS</b> is possible <b>any</b> time. But there are 4 to 6 times the average number of sporadics at 6 a.m. local time than at 6 p.m. On a good path, evening HSMS operation is quite possible; and the pings, while fewer, often seem to be stronger in the evening. (On a <u>difficult</u> path, unless there's a shower peak, I wouldn't try evenings. There just are not enough sporadics).<o:p></o:p></span></p> <div class="MsoNormal" style="text-align: center;" align="center"><span style="font-size:10;"> <hr align="center" size="2" width="100%"> </span></div> <p><b><u><span style="font-size:10;">SHOWERS</span></u></b><span style="font-size:10;"><o:p></o:p></span></p> <p class="MsoNormal"><span style="font-size:10;">The peak of a shower may come at a time other than the 4-8 a.m. period, of course. In this case, the maximum rate may be at some other time of night (or day - remember that there are a number of <u>daylight</u> showers, too. These are seldom mentioned because visual observers can't experience them).<o:p></o:p></span></p> <p><span style="font-size:10;">Some showers are spread over several days, others have <u>VERY</u> sharp peaks. As of now, these peaks can be predicted <u>only very generally</u>, and may be off by many hours. Their intensity may be off by an order of magnitude or more, also. This is because all predictions in the past have simply placed the probable peak time at the time when the earth's orbit should cross the orbit of the meteor stream. However, this does not take into account any variations, simply assuming that the meteors are now spread out evenly in their orbit. But, as has been realized in the past decade, this often is <u>not</u> true. Especially for streams that may have established a resonance with Jupiter, a stream may be bunched in filaments, as the Leonids have proved to be. Because of the work of Asher, McNaught, and others, predictions in coming years may begin to improve greatly in accuracy. For more on this subject, go to <a href="http://www.qsl.net/w8wn/hscw/prop/leodust.html">The Upcoming Leonids Storms</a>, the <a href="http://www.qsl.net/w8wn/hscw/papers/archive.html">Archived News Page</a> and also the pages of <a href="http://www.arm.ac.uk/leonid/dustexpl.html">Asher</a> and <a href="http://www.atnf.csiro.au/asa_www/info_sheets/leonids.html">McNaught</a>, who are revolutionizing meteor shower predictions with their dust-trail model.<o:p></o:p></span></p> <p><span style="font-size:10;">The <u>big</u> mistake most operators make during a shower is trying to operate using shower meteors <u>when the shower radiant is below their horizon</u>. The <u>radiant</u> is the point in the sky from which the meteors appear to come. If this part of the sky is still below the horizon, the number of shower meteors available for your use is going to be low. Yet during every major shower, stations will be heard on 144.200 calling long before the radiant rises.<o:p></o:p></span></p> <p><span style="font-size:10;">If you're operating <u>HSMS</u>, you may be able to catch enough sporadic meteors almost any time of day or night, even during the early evening. However, for <u>slow CW or SSB</u>, when overdense bursts or a number of good underdense pings are needed, it is of little value to operate when shower meteors are not expected! See the tables in W4LTU's articles, or use OH5IY's MS-Soft program to determine the rise and set time of the radiants of the various showers. (You will also note that, until the radiant's elevation is up 30 degrees or so, it isn't considered a very good time for their utilization).<o:p></o:p></span></p> <div class="MsoNormal" style="text-align: center;" align="center"><span style="font-size:10;"> <hr align="center" size="2" width="100%"> </span></div> <p class="MsoNormal" style=""><span style="font-size:10;">This page contains only the most basic information on sporadic and shower meteors. To be successful during showers, you <u>must</u> study W4LTU's articles and the text files bundled with MS-Soft, here:<span style=""> </span><a href="http://www.kolumbus.fi/oh5iy/">http://www.kolumbus.fi/oh5iy/</a><span style=""> </span>.<span style=""> </span><span style=""> </span>Then watch the "Hot News" page for the latest predictions (remembering, however, that the peak times for the showers will continue to be only approximate). For HSMS operation, except for difficult paths, use the daily sporadic meteors, or the beginning and end days of a major shower. During the peak of a major shower, SSB is probably going to be more efficient. But plan your SSB schedules <u>when the radiant is at a proper elevation</u> if you expect results. Study the articles referenced above, read the other papers on <a href="http://www.qsl.net/w8wn/hscw/papers.html">this Web site</a> and the <a href="http://www.nitehawk.com/rasmit/ws1_15.html">W6/PAØZN Main NA HSCW Web Site</a>, and follow the links from these papers and from the list of other Web sites that each HSMS Web site maintains.</span><b><span style="font-family:Arial;"><o:p></o:p></span></b></p> <p class="MsoNormal" style=""><b><span style="font-family:Arial;"><o:p> </o:p></span></b></p> <p class="MsoNormal" style=""><b><span style="font-family:Arial;">Here is the etiquette section from http://www.qsl.net/wa5ufh/DOS/Etiquette.htm<o:p></o:p></span></b></p> <p><span style="font-size:180%;"><span style="color: rgb(128, 128, 64);font-size:24;" >Ping Jockey Etiquette</span></span>
<br /><span style="font-size:18;">M</span>en have a hard time remembering which fork to use, the long one or the short one. Which side of the plate does the napkin go? How many times is it appropriate to stir the tea after the sugar is added. The steak can be eaten with the short fork and the tea beat into submission, but it is not always considered proper etiquette.
<br />
<br /><span style="font-size:18;">W</span>e all know there is behavior on the Ping Jockey that is acceptable during a contact attempt and behavior that is just not as acceptable. This page will discuss Ping Jockey Etiquette and to my knowledge most of these things are not documented like the proper table etiquette thus our thoughts are conceived from what seems proper and valid.
<br />
<br /><span style="color: rgb(128, 128, 64);font-size:24;" >Ping Jockey Schedules</span>
<br /><span style="font-size:18;">A</span>mateurs who operate High Speed Meteor Scatter are completing qso’s daily, or are they? Typically qso’s are either scheduled or random. Schedules are easily arranged via the Ping Jockey Page. Schedules that are made have an advantage over random qso’s because the two stations share important information via the internet prior to the start. This often times includes:</p> <p>• The call of the other station
<br />• A specified frequency
<br />• Who will transmit first
<br />• Will Single Tones or Multi-tones be used
<br />• Which Azimuth direction will be used
<br />• Often times QSY to another frequency because of perceived interference
<br />• A start time or announcement of “ I am running” or both
<br />• Sometimes a ending time is set in case the communications fail
<br />• Equipment conditions / parameters
<br />• Noise descriptions or lack of noise
<br />(And often times much more!)</p> <p><span style="font-size:18;">W</span>ith all the discussions and exchange of information before the actual attempt to communicate, one might wonder; how could they fail? Of course we all know that meteor scatter contacts are not automatic. There are times when attempts just fail, for whatever the reason, even with all the prior knowledge shared before the attempt.
<br />
<br /><span style="font-size:18;">T</span>he known elements shared before attempts are good and the smart operator will use them to his advantage. However to reduce the clutter on an often times busy page the information exchanged prior to the QSO start should be short and precise. </p> <p>What Frequency will we use?
<br />Who will go first? (Savvy operators know based on the Standard Operating Procedures
<br />When will we start / stop?
<br />Do you want to use ST or all MT? </p> <p><span style="color:red;">(This is off topic BUT schedules should not be made on Meteor Scatter Calling Frequencies)</span>
<br />
<br /><span style="color: rgb(128, 128, 64);font-size:24;" >What Constitutes A Contact</span>
<br />
<br /><span style="font-size:18;">T</span>his has been decided years back. Both stations must copy "Both Radio Calls", and "both must also copy their respected report and at least one Roger" (you usually need at least two <st1:place st="on"><st1:city st="on">Rogers</st1:city></st1:place> to be sure!), and then the QSO is officially complete. This is the minimum. In times past after schedules were made both operators left the web to return at a preset time. This is still a good practice.
<br />
<br /><span style="font-size:18;">E</span>ither stations, or at least "the station receiving the <st1:city st="on"><st1:place st="on">Rogers</st1:place></st1:city>" often times sends 73 back. This is a good practice so that the station sending RRR knows to stop and it terminates the qso via “amateur radio” rather than the “internet”! However if time does not permit or the “meteors slow down or appear to stop” then it is permissible to let the other station know his RRR was received via the Ping Jockey but the preferred method is for all contact information including the termination of the contact to be via the meteor pings and not the telephone modem..
<br />
<br /><span style="font-size:18;">T</span>he validity and integrity of the following list of accomplishments by stations can be “brought into question” when contact requirements are communicated, hinted or suggested by the use of the Ping Jockey either by those attempting to make a contact or someone monitoring and posting what they are copying.</p> <p>• VUCC
<br />• States Worked
<br />• Initial Contacts</p> <p><strong><span style="color: rgb(128, 128, 64);font-size:24;" >How far can we go before the Contact becomes invalid?</span></strong>
<br />
<br /><span style="font-size:18;">F</span>irst let us consider this fact. WSJT works sufficiently well so that no other means of sending or sharing information is necessary to complete a contact via meteor scatter. Thus it is not necessary for meteor scatter operators to give out informtion about the contact during the contact. For schedules, everything is worked out ahead of time and after the contact starts it is not good etiquette to discuss, hint or share information pertaining to the contact attempt that is in progress! There will be some who think other wise, but the divisions are, make the schedule first and execute the schedule second.
<br />
<br /><span style="font-size:18;">T</span>he operators of WSJT, from the beginning of Ping Jockey asked that the following message to be posted for all new and experienced operators. That message is “Exchanging any contact details on here before you're complete, invalidates the contact”
<br />
<br /><span style="color: rgb(128, 128, 64);font-size:24;" >The following are examples of statements</span> that would certainly call into question a contact by either attempting station. Blatant communicating contact details during a contact attempt are wrong!
<br />
<br />Have you gotten both calls yet?
<br />Sorry I skipped a message, going back to Calls and Reports
<br />Sending RRR now.
<br />I just got your Report.
<br />What message are you sending?
<br />Have R 26, I am sendng RRR now.
<br />
<br /><span style="font-size:18;">F</span>rom the beginning of HSCW, Operators have always considered contact details to be information about the details of what is or has been sent.
<br />
<br /><span style="color: rgb(128, 128, 64);font-size:24;" >The following examples are statements that </span>don’t exactly tell where you are in the contact but like setting the table wrong or eating the steak with the short fork, are better just not said.</p> <p>• Are you sending single tones now?
<br />• I can hear you now
<br />• I have up to 10db burst no decodes
<br />• Just got a big one!
<br />• Keep going
<br />• Your DF is 102
<br />• Leave your antenna there!
<br />• Not hearing anything, moving to Hot A
<br />• I am getting some single tone, is that you?
<br />• Wow! You hit me hard, 13db!
<br />• Keep going we are almost finished.
<br />• There is 500 watts out have anything yet?</p> <p><span style="color: rgb(128, 128, 64);font-size:24;" >Sometimes the contact is compromised by someone who is just monitoring.</span>
<br />
<br />I hear your single tones good here Joe!
<br />They are almost finished Joe is sending reports now.
<br />Look what I copied 155630 27.4 240 1 26 -64 2626 WA5UFH 26 K4FJW (be careful what you post)</p> <p><span style="font-size:18;">T</span>here are many ways that a contact can be compromised. What should one do when this happens? The best answer is to start over! That is the right thing to do and easily done. If the qso was compromised by a contact station, the offending station should be reminded to read the “Blue” line at the top of the Ping Jockey Page. Meteor Scatter is a valid mode and all operators should honor the requirements for completing contacts strictly via Meteor Scatter refractions on our vhf bands.
<br />
<br /><span style="color: rgb(128, 128, 64);font-size:18;" >Is there ever a time for compromising a contact by sharing contact information?</span>
<br />
<br />The answer is no<strong><span style="font-size:18;">! </span></strong>
<br />
<br />Meteor Scatter Contacts never involve the sharing of QSO details after the contact is started. Not even a hint or suggestive statement is good etiquette. If contact information is shared, even though all elements might have been received by both stations, the contact was tainted and does not meet the requirements of using “Meteor Scatter Only” for the exchange. The trail of suggestive or shared information relating to the “supposed contact” is on the Ping Jockey screen for all to view. As stated earlier, WSJT is capable of transmitting all the required data via your radios and meteor scatter.
<br />
<br /><span style="color: rgb(128, 128, 64);font-size:18;" >Is it acceptable to QSY to another Frequency because of QRM or QRN?</span>
<br />
<br /><span style="font-size:18;">I</span>f QRM has creped into your passband and might cause you to miss some received messages then the smart thing to do is QSY to another frequency. This can be accomplished by posting the need to QSY on the Ping Jockey without sharing any contact details.
<br />
<br /><span style="color: rgb(128, 128, 64);font-size:18;" >What if I have a catastrophic failure?</span>
<br />
<br /><span style="font-size:18;">A</span>nytime a contact attempt is terminated and is latter restarted, both stations are to start over at the beginning. If you must stop, the courteous thing to do is notify the other station you have stopped. A temporary problem can be posted like, keep going I am having a temporary problem and not compromise the contact. Often times a problem can be corrected easily without terminating the contact attempt.
<br />
<br /><span style=";font-size:24;color:olive;" >What if it’s not a <strong>Contact</strong>?</span>
<br />
<br /><span style="font-size:18;">N</span>ow if it’s not a contact, let’s say someone asks you to listen for their signal and see if they are on frequency or maybe they are testing their transmit for the fist time. Talk all you wish, this is not a contact. The majority of what occurs on the Ping Jockey constitutes a contact where two amateurs agree to have a prearranged sked for the purpose of completing a contact. If you have worked the same station 100 other times, the rules for a contact do not change just because you have his card on the wall.
<br />
<br /><span style="color: rgb(128, 128, 64);font-size:18;" >Ping Jockey Etiquette; “Because I respect the Posted Guidelines on the page</span>”
<br />
<br /><span style="font-size:18;">P</span>ing Jockey is a useful system for Meteor Scatter operators, Weak Signal Operators and EME scheduling. The Ping Jockey pages are self explanatory however many seem to be happy carrying on all their business on the Ping Jockey Central. Ping Jockey Central, the main page, is not designed to be a “Chat Room”. At the top of the page we all see the message, “If it's not HIGH-SPEED METEOR SCATTER, it doesn't belong here! Even with this message, we find discussions about antennas, radios, club meetings and many other discussions not relating to HSMS!
<br />
<br /><span style="font-size:18;">T</span>here is another page called “Relief Page” that is similar to the Main Page but because of less activity it will support discussions and the appropriate thing for operators to do is move off topic discussions there just like it is appropriate to move stations willing to run JT44 off the Ping Jockey Central page to the JT44 Link page.
<br />
<br /><span style="font-size:18;">T</span>he other pages, CQ Announcements and Skeds in Progress are self explanatory and during times of higher volume traffic, like contests, these pages should be used to reduce the potential of qrm.
<br />
<br /><span style="font-size:18;">W</span>e are fortunate to have such a system as Ping Jockey. We should all thank Chris often and we should honor his posted instructions.
<br />
<br /><span style=";font-size:24;color:black;" >So </span><span style=";font-size:18;color:black;" >What Can I Do During a Contact Attempt via Meteor Scatter</span>
<br />
<br />Computers are multitasking. One can play cards, surf the web, clean the shack, read email, work on the projects bench etc. but please, don’t bring any element of doubt on your contacts or your friends contacts by posting information about the contact prior to it being completed.
<br />
<br /><span style=";font-size:18;color:black;" >Why This Article</span><span style="font-size:24;">?</span>
<br />
<br /><span style="font-size:18;">I</span> am not without guilt. I suppose we all have been guilty of some questionable act relating to meteor scatter. We should all strive for a higher operating plane and the experienced should lead by proper example. Before things get too far out of hand, let us all focus on Meteor Scatter Only Contacts. </p> <p>Make the sked on Ping Jockey and then execute the sked on the radio.</p> <p>Thanks to all those who helped critique this sheet. ( WB5APD,N0UK,K1SIX and others...)</p> <p>WA5UFH (Tip)</p> <p class="MsoNormal" style=""><b><span style="font-family:Arial;"><o:p> </o:p></span></b></p> <p class="MsoNormal" style=""><span style="font-size:180%;"><b><span style="font-family:Arial;">Next week:<span style=""> </span></span></b></span><span style="color: rgb(21, 34, 43);"><span style="font-size:180%;">Packet Radio and Airmail</span>
<br /></span></p><p class="MsoNormal" style=""><span style="color: rgb(21, 34, 43);">
<br /></span></p><p class="MsoNormal" style=""><span style="color: rgb(21, 34, 43);"> That setup is a little more complicated than the others we have done to date.<span style=""> </span>Since it has a few steps, I put the materials and software on the WA-DIGITAL site a few weeks ago.<span style=""> </span>Check out Blog Post 10 for the setup.<span style=""> </span>Of course, if you are using a hardware TNC for packet decoding, then just hook up your TNC and you are good to go…</span><b><span style="font-family:Arial;"><o:p></o:p></span></b></p> <p class="MsoNormal" style=""><b><span style="font-family:Arial;"><o:p> </o:p></span></b></p> <p class="MsoNormal" style=""><b><span style="font-family:Arial;">Write with any questions - See you on the bands!<o:p></o:p></span></b></p> <p class="MsoNormal" style=""><b><span style="font-family:Arial;"><o:p> </o:p></span></b></p> <p class="MsoNormal" style=""><b><span style="font-family:Arial;">vy 73 de WR5J<o:p></o:p></span></b></p> <p class="MsoNormal" style=""><b><span style="font-family:Arial;"><o:p> </o:p></span></b></p> <p class="MsoNormal" style=""><b><span style="font-family:Arial;">Curt Black – <a href="mailto:black@nwfirst.com">black@nwfirst.com</a><o:p></o:p></span></b></p> <p class="MsoNormal" style=""><b><span style="font-family:Arial;"><o:p> </o:p></span></b></p> <p class="MsoNormal" style=""><b><span style="font-family:Arial;"><o:p> </o:p></span></b></p> WR5Jhttp://www.blogger.com/profile/16316513702643319581noreply@blogger.com1tag:blogger.com,1999:blog-4632435085083780021.post-4022077399456540542009-07-16T12:35:00.000-07:002009-07-16T12:47:12.764-07:00Blog Post 8 – JT65A—HF Weak Signal Mode by K1JT, Joe TaylorBlog Post 8 – JT65A—HF Weak Signal Mode by K1JT, Joe Taylor<br /> <br />Wednesday July 29, 2009<br /><br />This is Curt Black, WR5J, with the Educational Radio Net –<br />Please standby for a JT65A Digital QST<br />.<br />Before the net. Please download tonight’s software – WSJT, Weak Signal Modes by K1JT and set it up according to the blog and WA-DIGITAL Yahoo Group instructions. <br />.<br />The software at 5.5Mbytes is just a little too big to be downloaded to the Yahoo site, so folks need to go to the source:<br />.<br />http://physics.princeton.edu/pulsar/K1JT/wsjt.html<br />and grab the current WSJT version 7.03 – the download will include the users guide in English.<br />.<br />WSJT facilitates basic digital communication using protocols explicitly optimized for a number of different propagation modes.<br />.<br />Specifically: <br />• FSK441 for meteor scatter<br />• JT6M for ionospheric scatter<br />• JT65 for EME at VHF/UHF, and for HF skywave propagation<br />• JT2, JT4, WSPR: experimental modes<br />.<br />Once you have the HF Terrestrial Mode, JT65A under your belt, you will be poised to take on the others on your own. There are some quirky things about the software, and it helps a lot to have someone show the way, but they tend to be consistent from protocol to protocol. <br />.<br />Andy, K3UK, a british sleeper cell agent in North America has produced a great guide to getting started with JT65A. It is what I used when I first tried the software and it worked great. For the net, we’ll just work our way through the setup and try sending a few transmissions back and forth.<br />.<br /><span style="font-weight: bold;">The Complete Bozo's Guide to HF JT65A<br />( a work in progress)<br />by Andy K3UK</span><br />Version 2.03 Last updated March 7 2009<br />Images are not availabe on the BLOG - they just aren't working -<br />please see<br />.<br />http://groups.yahoo.com/group/wa-digital/files/<br />.<br />This article may be freely re-distributed if credit to the author is given<br /><br />Introduction:<br />This article was originally composed in 2007. At that time JT65A was a new mode for HF, and the WSJT software was new and puzzling to most hams. Since that time, the mode and software have become quite popular and less puzzling. Another application, Multipsk, has also added JT65A. WSJT also added another mode, WSPR. A brief K3UK Guide to WSPR mode has been added to the end of this article.<br />.<br />I have left the article mostly in its original form, since it was aimed at the total beginner . I have made a few small updates to reflect some new aspects of WSJT.<br />----------------------------------------------------------------------<br />.<br />As a complete bozo, I am quite qualified to write this guide. I have been using the mode for a whole month now and have had "QSOs" with dozens of stations in several continents. For example, South Africa on 40 meters. All DX worked with low power and a simple piece of wire in a tree. I have no idea why the software works but if I, K3UK, can figure out how to get it to work.....anyone can! <br />.<br />If you are smart, and know more than me about this software, please feel free to email me via k3ukandy@gmail.com I will be happy to add your help to this document. Please let me know if I have added anything that is just plain stupid, or wrong!<br />.<br />History: <br />.<br />The JT65A discussed in this guide is a submode within a suite of applications collectively referred to as WSJT. The WSJT software has been available for several years (2001) and was initially designed by Joe, K1JT. This amazing piece of software has evolved to the point that there is now a team, rather than one individual, that are developing the software. That team consists of Joe K1JT, DL3LST, KK7KA, ON/G4KLX., N5HY, VA3DB, and James Courtier-Dutton . This team is to be commended for their contributions to the advancement of amateur radio communications.<br />.<br />These non-bozos have already written a document that serves as a useful guide. I have read it several times; it takes several readings for this bozo to understand just a little. If you would like to read the smart people's guide, you can find it at http://physics.princeton.edu/pulsar/K1JT/WSJT_User_600.pdf <br />.<br />The first HF terrestrial use of JT65 appears to have been a JT65B QSO on August 14 2006 between Victor UA0LGY and Tetsu JE5FLM. The recent explosion of HF activity began after VE3FGU, and several of his friends, started experimenting with the JT65B on March 23 , 2007 and JT65A on March 24. 2007. <br />.<br />On March 28th 2007, several members of the digitalradio reflector (http://groups.yahoo.com/group/digitalradio/ ) noted some unknown digital signals on 20M and on March 30th concluded that they were JT65A signals. The experiments of Mike VE3FGU, Tetsu JE5FLM, David WD4KPD, Marshall W9RVG, Seli TF3AO, and others, quickly exploded in to the hottest HF mode for weak signal DXing and experimentation.<br />.<br />What Skills Do I Need ?<br />.<br />1. The ability to set your computer's clock accurately and keep it synchronized 2. The ability to connected your radio to a sound card for receive and transmit (receive only, if an SWL). 4. Able to use a computer mouse or keyboard (fingers, feet , or nose will work just fine).<br />.<br />What can I do with this software ?<br />.<br />This is not software that is designed for a "rag-chew" ( a British-American colloquialism for having a long conversations) . If you want to find out how Bert's operation went, try PSK 31 , DominoEx, Olivia , or some other digital mode well suited for keyboard chats. This software is for brief exchanges of information. Mostly callsign, location, signal report, and confirmation of the signal report. Since it is very good for weak signal detection, it is a great QRP HF mode. You will find the software useful for monitoring propagation and, if you are a DX hunter interested it a quick 5NN and moving on , this is a mode for you! Why not a "rag-chew”? Well, you could, but the software is designed for brief exchanges of no more than 5-6 words and each exchange takes one minute. So, it would take you about 6 minutes to establish contact with Bert and find out that the surgeon removed the wrong organ. <br />.<br />The software was designed for EME and Meteor Scatter communications but I will leave that for another bozo to write about. I have to use a spell-checker to spell meteor.<br />.<br /><br />Where do I get the software ?<br />.<br />They don't make it easy to obtain. A quick trip to Google will give you several dead links and even a visit to WSJT "Smooth Jazz”, an FM station in Florida. We want "jazz" of a different kind, so go to http://www.physics.princeton.edu/pulsar/K1JT/ for the most recent version. If you have a REAL slow computer, there are older versions that will work well, check http://physics.princeton.edu/pulsar/K1JT/Download.htm for these. <br /><br />.<br />Installing the software:<br />.<br />Assuming you remember which folder you downloaded the software to, go to that folder and click on the WSJT7.EXE file. The install will default to your program files folder and the usual path will be c:\program files\wsjt7\wsjt7.exe. Once you have done this, boot up the program. Take a deep breath; prepare to be confused and amazed.<br />.<br /><br />Setting Up The Software:<br />.<br />This should take less than a minute . When the program boots up, you will see a brief dos-type window pop up. Ignore this for a while, it s a useful window but something you may never need to pay much attention too. A few moments later you will see the WSJT main screen. Don't panic if the "waterfall" is dark and devoid of signals, this is normal at this stage. Click on MODE and select JT65A.<br />.<br />Here is what you will see when the main window opens up .<br /><br />.<br /><br />Ignore the bit about the moon unless you are thinking of a moonlight walk with that new sweet-thing, or plan to bounce radio signals off the moon. Yeah right...like that's really possible. In fact, yeah .. like BOTH are really possible !<br />.<br />Now, we will set it up for your callsign and your location. To do this, you need to click on SETUP and then select OPTIONS.<br />.<br /><br /><br /><br />In the box named MY CALL, enter in your call sign. Next you need to figure out where you are and then you place your grid locator in , you guessed it... the box called GRID LOCATOR. Since you are a complete bozo like me, you may not know what your grid square is. Grid locators can get very specific, to within a few metres. For JT65A HF work, you really don't need to be that precise. The grid square for your post office or town centre will do. Americans can go to http://www.arrl.org/locate/locate.html . Britons can go to http://www.aber.ac.uk/cgi-bin/user/auj/locate.pl . It may be hard for some American and Britons to realize , but there are other countries in the world. That is good , because we need other countries to make DXing more exciting., and provide places to go on vacation. If you live in one of these other places , try http://www.qsl.net/ad7db/yourgrid.html A new alternative is F6FVY's Google Maps server that allows you to find your location on a Google map and your grid square will pop up on the map. Check http://f6fvy.free.fr/qthLocator/fullScreen.php . The WSJT software does not require grid locators but the grid locators are used in the default mode instead of an RST report.<br />WR5J likes http://www.qrz.com - put in your call sign and look yourself up. Then click on the green “Click for more detail” bar. Then click on the link to the “Explore on Grid Map” and check out your location – you can scroll around and actually update your location if it is off in the FCC database. You should so definitely do that…use the EDIT RECORD link.<br />.<br />Setting the Radio for Transmit<br />.<br />OK, so you have entered in your callsign and location. If you want to make the software key your radio when transmitting, you need to tell WSJT which comm port you are using for "PTT". My station uses a virtual serial port , port 5. You will likely use 1, or 3 if you are using a regular serial port. Enter your port where it says PTT PORT.<br />.<br />Just one more thing to do. The software can calculate the distance between your grid locator and the received station's grid locator. Most sensible folks use metres but a few people clutch to a old system referred to as "miles" (mainly those Brits and Americans, again). Remember, I am a complete bozo, so I use miles. Click on the ML or KM in the DISTANCE UNIT area.<br />.<br />That's it. Leave all the other stuff alone.<br />.<br /><br />Receiving signals : <br />.<br />Assuming you already have the audio from your radio receiver connected to the input of your sound card, you are close to being ready to receive. Remember though, the software was written by somebody completely intelligent. There are many useful things that can be done with the software, the smart author thus decided that the receiving of signals needs to be activated. Your WSJT main screen should now look like this.<br />.<br /><br /><br /><br />Note that I have highlighted a button called MONITOR. Note also that the other area I highlighted has your callsign and grid square inserted. Now, click on the MONITOR button with your radio tuned to any HF frequency and you will eventually see signals on what looks like a waterfall. I say eventually, because this waterfall is one thoughtful waterfall. It needs to think a while about what it is receiving and then, precisely when your PC's clock signifies the start of a new minute, the display will come to life with some interesting squiggly lines. Assuming you see some squiggly lines , you are in good shape and ready to move on. To be honest, this "waterfall" is not a waterfall in the traditional sense. The waterfalls that you see in Digipan, Multispsk, fldigi, MMTTY, Winwarbler, DM780, MixW, etc etc, display the signal on a continuous basis and indicate the intensity of the received signal. This display in WSJT actually takes a snap shot of what you have received in the past 48 seconds and displays it all at once. The moon-bouncing meteor dodging hams that use the WSJT software, use this aspect to analyze minute details that enable them to determine if the Martians have actually entered our ionosphere. It is an important "main graphical area" ( as the official guide calls it) , even for HF applications. More on how to interpret this later.<br />.<br />Frequencies : <br />.<br />We might as well get the radio tuned to frequencies known to be used for JT65A on HF. The most commonly used frequencies are 14.076 and 7.076 in North America 3576 (North America ) , 3796 (Europe) , also 18102, 18106, 10147, 21076, 24910 . 1805 to 1808 . 14076 or 7076 are the best places to start. These are DIAL or VFO frequencies, most use USB but there are some that use LSB. By far the simplest method of figuring out where the action can be found is to use your web browser and go to http://www.chris.org/cgi-bin/jt65talk . This web site is the place to go for announcements of who is active and what frequency they are using. The website is maintained by Chris, N0UK. Yes, he is N0UK and I am K3UK. We are both part of a British plot to take control of the JT65 world and lay the foundation for re-acquisition of colonial America in 2076. The Queen visiting the Kentucky Derby was also part of this plot. IF you do not trust us Britons, there is an American you might try. Check in at http://www.w6cqz.org/ . This American is non-bozo, he is clever enough to develop a system of "reverse beacons" , you can transmit your JT65A signal and see if other stations automatically receive your signal.<br />.<br />So tune to one of the above frequencies , get a cup of coffee and relax for a minute or to.<br />.<br />Tuning Accuracy :<br />.<br />Now, some important stuff. The smart JT65A users will eventually point this out to us bozos, so I figured I will tell you now. The software decodes signals over a wide range, up to 600 Hz. So you can decode several signals within this 600 Hz range . You can be decoding all of them but if you transmit you could be several hundred Hz from the other station's transmit signal. This , to the JT65A afficinados, is a crime and war crime tribunals may get formed. Even a bozo like me can understand this after a while. It's like working "split" and taking up more spectrum than is needed. It is also like not being zero-beat in CW and trying to work a person who has a 200 Hz filter active. If you are 300 Hz from his frequency, he is not going to hear you. Don't fear, this is easy to address, more on this a little later in the document.. <br />.<br />Let's not worry about accuracy at the moment, lets just tune a signal. After a few minutes on an active frequency your main screen may look like this<br />.<br /><br /><br />The blue highlighted text is my work, your screen will not automatically highlight text..<br />.<br />The highlighted text is...<br />.<br />163500 11 -7 -0.7 -73 3 # DL5SWB DK7OM JO53 OOO 1 0<br />.<br />What the heck does this mean? Smart guys already know, but bozos like me are still learning. It tells you that at 1635 (and zero seconds) the software decoded DK70M responding to DL5SWB. Just like a regular phone contact "P5DX de K3UK". . It also tells you that DK7OM is in grid square JO53 . This string of information also tells me that the dB was averaging -7 during the minute or so the software was decoding DK7OM's signal . This is a signal to noise type of reference. 7 dB in to the noise. This is a good signal, WSJT will decode signals well below -20 dB. The minus 73 under the DF area tells me that I am close in frequency , about 73 Hz off, good enough for now. I'll save the other info in that string for a later discussion.<br />.<br />What About The Rest In The Window. ?<br />.<br />The "RO" RRR" and "73" are just snippets of a conversation used to confirm the QSO. Its like tuning in your radio and hearing someone say "Roger" or "73" . More on this later. Version 5.9.7 has an option that suspends use of the RO , RRR, and 73 messages. This option was specifically added for the new HF application of JT65A. The RO , RRR, and 73 messages in the default format were designed with EME and Meteor Scatter QSO in mind and are as brief as possible. For HF application of JT65A, the need for very brief bursts of information is not paramount., so the new version has added an option to include callsigns and signal reports . The RO , RRR, and 73 messages are messages in a special format and can be decoded and even weaker signal levels that the other messages. So when signals are very weak on HF you may still see these messages. <br />.<br />That Weird Waterfall Thingy : <br />.<br />As mentioned earlier , that weird waterfall thingy (the "main graphical display" ) can tell you a lot. The rookie user needs to know a few basics that will enable you to be closer to the received station's frequency. In the picture below you will see a red spike on the spectrum display. <br />.<br /><br />You can take your mouse and click on the red spike (see center of picture above) and that will get you close to the right frequency. The peaked blue spike tells you something useful too, I will add that at another date.<br />.<br />Those RRR and 73 reports that are decoded will show up as orange or purple lines on the waterfall.<br />.<br /><br />Reportedly, clicking on the purple peak will also serve as an tuning aide, I have not tested that yet. For meteor scatter and EME work, the orange, purple, and green lines can be valuable in digging out a signal. For JT65A on HF, they are not as important.<br />.<br />Using a "waterfall" that has to think for a minute before it updates information can be frustrating. Don't worry, the author has another trick up his sleeve, a second waterfall! This is a REAL waterfall just like the ones Peter Martinez and Skip Teller invented for use old PSK31 users. Click on VIEW at the top of the main window and then select SPECJT. A real waterfall will open up (if you are using an older version you may need to manually boot up "spectran.exe" for this ). This waterfall can detect RF generated by a flatulent butterfly 1000 kilometers away. Eventually you will stare at this waterfall and see the tiniest hint of a signal and be amazed as the software decodes information from it. Note on the picture below, you will see this second waterfall, a received signal and the mouse cursor indicating tuning the signal to the sync tone. For HF work, this second graphical display will be the most important display for identifying the presence of a signal and in accurately tuning in the station.<br />.<br /><br /><br />Clicking with the mouse, on the longer sync tone will get you very precisely tuned. The sync tones are actually 1270 Hz, you and your dog should have no difficulty learning to recognize the sync tone both in the SpecJT, and via your ears (actually, your dog may have difficulty understanding the waterfall display, sorry to point this out ) . The authors of this software think of bozos like me and actually send the sync tone quite frequently, so you get lots of chances to spot it. If you have monitored the active HF JT65A frequencies you will have heard a few JT65A signals. These tones sound a little like the old Throb mode, and a little like very slow DominoEX. This throbbing type signal actually sends the important sync tone about 65 times in a typical sequence, the other tones in a sequence are sending information. The tones actually change a little during a "QSO", and some of the messages actually don't use the sync tone in the same way. That's too complicated for a bozo's guide, but the aforementioned smart people's guide explains it well. . The general rule of thumb, detect a signal within the SpectJT that looks like JT65A and click on the LEFT edge of the signal. Be aware that the SpectJT will display all kind of other signals within the range of the waterfall, so you may see PACTOR bandits, PSK Rangers, RTTY rompers, Hell raisers, and a plethora of other digital modes. JT65 is fairly easy to spot after a couple of attempts, the only other digital mode that looks a little like it in the SpectJT is MFSK16, but this sounds very different. <br />.<br />The signal in the picture above is a very weak signal. Sometimes just a very very slight line has shown in the SPECJT waterfall and I have successfully decoded a signal. Remember, you don't need to be that precise to just decode signals; you need to get precise to be transmitting as close as possible to their transmitted signal. The reason you want to be close is because the smart JT65A operator my not want to be receiving signals more than a certain distance from his transmit signal. He may have, for example, set the software to ignore signals from more than 200 Hz away from his signal. So, if you are 300 Hz away, he will never decode your signal. I often listen with a 600 Hz range so that I can get a sense of who is active on the band, but switch to 200 Hz when trying to have QSOs. To set the range, left click on the number in the TOL box to raise the setting, right-click on the number to lower the setting. Click the "freeze" button to maintain this. <br />.<br /><br />Remember to raise TOL to 600 and Freeze "off", if you are just looking for QSOs.<br />.<br /><br />While the SpecJT window is open, click on OPTIONS and select JT65 DF Axis. This will help further in precision tuning. While there, you can also play with the palette settings and vary the appearance of the waterfall. There will be a few occasions where you cannot even see a signal even in this highly sensitive waterfall. The different palettes will make it possible to see extremely weak signals, try "hot" for example. <br />.<br />Note at the bottom of SpectJT there is a "gain" area, just to the right of the digital clock. You can adjust the gain of the waterfall with this control. You can also adjust the brightness and contrast of the SpecJT waterfall. Try that, if your ears detect a signal but you don't see it on the waterfall. The gain control can be an important factor if you experience a situation where you are unable to decode signals, please see the "trouble" section of this document.<br />.<br /><br /><br />A good Bozo's guide should be short and sweet, but I need to explain a few more useful tips about receiving a signal. Take a look at this<br />.<br /><br />The stronger signal at the bottom right-hand corner is VE5MU. The weaker signal is K4CML. They are working each other but not exactly on the same frequency. Their QSO copied at my station shows....<br />.<br />022200 3 -16 -1.5 -143 4 * VE5MU K4CML FM17 1 0<br />022300 19 -4 1.4 -22 3 * CQ VE5MU DO70 1 0<br />.<br />Pretty close though and will work unless they have their TOL set to less than 100.<br />.<br />Now take a look at this<br />.<br /><br />VE5MU and VE7TIL copied at my station on 40M, both almost exactly tuned with each other. My station recorded their QSO<br />024800 9 -7 1.5 -121 3 # VE7TIL VE5MU DO70 OOO 1 0<br />024900 3 -9 0.1 -116 3 # VE5MU VE7TIL CN89 OOO 1 0<br />.<br />Although -121 and -116 DF from where I was tuned, they were within 5 Hz of each other.<br />.<br />Please note, the callsign in the above pictures do NOT appear in the SpecJT, I added them for illustrative purposes. <br />.<br />I am sure you wonder what all the other numbers mean, this will be added at a later date but it is worth mentioning that the last number in the line (the zero as in " 1 0 " ) is an indicator of how confident the software is that it has decoded correctly. The software is quite sophisticated and sometimes acts like a human ear/brain, it guesses what it heard. The confidence scale goes up to 10 , supposedly anything under a three is questionable. I'm still trying to figure out what most are given a zero but even when obviously accurately decoded. The smart author of software, Joe W1JT, took pity on this bozo and sent me the following...<br />.<br />"You mention the two numbers at the end of each line of decoded text. If the first of these is 1, it means that "Deep Search" was not required and decoding will nearly always be 100% correct. If the first number is 0, the second (some number between 1 and 10) gives an indication of relative confidence of a Deep Search decoding. Since the default list of "plausible" callsigns is VHF/UHF and EME oriented, Deep Search will not be very useful on HF unless the operator becomes fairly sophisticated in using WSJT".<br /> .<br />Deep Search has no relation to Linda Lovelace and has apparently no connection to the Deep Throat that did Nixon in. It is a software function designed to help the moon-bounce and meteor scatter hams find fragments of RF and match the fragments to known users of the software. It is recommended that you turn this feature off in the main graphical display area , by going to OPTIONS/DECODE/JT65 and then checking "no deep search" . Leaving it on does not cause global warming but does, on occasion, cause a "phantom signal" to call you. If you see a call to you when you have not been transmitting, it is possible that Deep Search caused it. <br />.<br />One more item on receiving...<br />.<br />In the SpecJT waterfall you will notice a receive noise level indicator in the lower right-hand corner. It displays the noise level in dB. I have been told that things do not decode very well if you have something like a 4-5 dB level (above zero, not below) . I have also noticed that it does not decode very well when you have a very low figure, like -20 dB. A number of factors can influence this and the noise level will change from band to band. The biggest single factor will be whether you are getting enough, or too much, audio from your radio to the input of your soundcard. Many digital mode interfaces like Microham or Rigblaster products have knobs that control the audio levels. If your RX noise level is too high or low, adjust the audio so that your noise level is around 0 db without a signal present. Smart people have also suggested it works better with AGC off, play around and see. You can experiment with your rig's filters, noise reduction circuitry, AGC settings , RF gain settings , etc, etc. <br />.<br />Transmitting Signals/Having A QSO.<br />.<br />I've said this three times already but... to transmit you first need to understand that the smart JT65A guys all expect you to transmit at a certain time. That time needs to be synchronized, so synchronize your PC's clock with Internet time or WWV. I use an application called Dimension 4 that keeps my clock synchronized. Why? Because the software needs time to decode your transmitted signal and also switches to transmit at certain times. If your timing is off, the other station may have already switched to transmit and thus not decode your signal, or their decode period would be so short that it did not get a chance to decode all your information. You can get the freeware Dimension 4 at http://www.thinkman.com/dimension4/download.htm<br />.<br />Transmitting Frequency.<br />.<br />Popular digital mode software like MixW, Multipsk, MMTTY, have functions that maintain a relationship between the received and transmit frequency. These functions, often via a "net" on/off feature, cause the radio and/or soundcard to adjust when you click on a signal in a waterfall. The WSJT software has a similar function and is labeled in the main graphical display as TxDF= . In the older versions one had to always match your transmit and receive frequency manually. It may be useful to first understand how to do this, and then learn the new TxDF= feature. So, lets begin an manual reception and transmit.<br />.<br /><br /><br />Here we see a CQ from P5DX , my radio was tuned to 14076 USB but my eagle eyes (and bat-like ears) spotted a signal further down the waterfall. I clicked on the left-side of the signal on the SpectJT waterfall and the green scale markers shifted to show that I am tuned about 500 Hz below where I started. Although working North Korea is becoming routine for me, I take pity of the poor guy and decide to work him once again. If I just transmit, my rig will transmit at the zero mark, 14076 USB. He is 500 Hz below, at 14075.500. So all I really have to do is manually turn my dial 500 Hz lower, to 14075.5 and then...<br />.<br /><br /><br />Here you can see the old received signal shifted 500 Hz to the left and more importantly the new receive frequency is close to my transmit frequency at 14076 USB. Simple , right? <br />.<br />To get more adept at precise matching of the received frequency and transmit frequency, use your mouse to move left and right on the SpecJT waterfall. Note how the frequency and DF changes.<br />.<br /><br /><br />Mouse pointer at 881 Hz and 388 Hz below transmit frequency.<br />.<br /><br />What About This New Fangled "TXDF= feature? <br />.<br />Not only am I a complete Bozo, I can be a little mean. I threw the word "fangled" in here just to puzzle the folks that bring you the Russian and Spanish translations of this document. I think we should offer a prize to someone who can tell us the origin of the word "fangled". Anyway, I deviate from the mission at hand. Actually "deviate" is a key term for this section of the guide. When you tune a signal and successfully decode it, the decoded text will tell you how far your tuned frequency is from what will be your transmit frequency. For example , this decoded text<br />.<br />035100 10 -15 3.4 -160 3 * VK7CAV N5BO -16 1 0<br />.<br />Shows that the DF was 160 hz below where my transmit is set. The very smart author of the software has now enabled us to match the receive and transmit frequency instantly via a simple double left-click with your mouse.<br />.<br /> <br />TxDF set to default zero TxDF adjusted 98 Hz and matched<br />.<br />To do this, locate the signal in the SpecJT, aim your mouse on the left edge of the signal and double click on it. Now single left click on the TXDF and the deviated frequency will be indicated You , despite being a bozo, will have achieved something akin to mastering rocket science...your transmit frequency and receive frequency will match! Now, actually the smart author is doing this via having the software fiddle around with the capabilities of your soundcard. Your radio is not adjusted, don't worry about that "split" button being activated or, God forbid, that RIT thingy being turned on !<br />.<br />A word to the wise: Users of some RTTY or PSK31 software might be used to the fact that once you have instructed your software to match receive and transmit frequencies, they stay matched even as you re-tune and work stations on other frequencies/bands. This WSJT software requires that you make the adjustment each time you are going to transmit, assuming the station you want to work is on a different frequency than the one you just worked. For example, suppose you worked a station that had a DF of 233 Hz. You left-clicked on TxDF and it matched your settings so you were exactly on the same receive and transmit frequency. Now that you have worked the station, you see on your screen that KT2Q has been decoded with DF of -321 Hz. You will need to again click on the TXDF button for it to match the DF , before you transmit.<br />.<br />Audio levels:<br />.<br />As with any digital mode that relies on your PC's sound card, you need to pay a little attention to the quality of your transmitted signal. Typically, when using modes like Olivia or the old PSK31, people suggest you keep your ALC level to the very minimum. One of the non-bozo types emailed be recently and suggested that the nature of the JT65A signals is such that you don't have to worry about this as much , and can give a good amount of ALC. I still keep mine fairly low, old habits... <br />.<br />Another friendly ham reminded me that this mode is full duty cycle and he suggested that people should not use full power for long periods. This mode does not need a whole lot of power. A ham, Tony KT2Q, popped up one day and said he had a "Bird meter in line". Being not only a bozo, but a British bozo, I wondered whether a bird meter was something similar to "a chic magnet", perhaps? Maybe it can detect the fairer sex at a thousand paces? Well, it turns out that this KT2Q guy is one of them non-bozo hams. The bird meter had a "plug" in it . So does my bath tub, but the bath tub does not help with most of my radio projects,. Well the "plug" enables him to calibrate his radio output and accurately determine how low his power is . I was able to detect and decode his JT65A signal when he was using 250 milliwatts on 40 meters. Another ham, some 600 miles away from KT2Q, was able to detect him below 50 milliwatts. So, you don't need to have your transmitter set for high power. I often run just 5-10 watts on 20M. <br />.<br />CQing. <br />.<br />If you want to CQ, you have to decide whether you want to transmit "1st minute" or "second minute". This helps to maintain world peace and keeps QSOs orderly. "First minute" means 00 and any even numbered minute 02 , 04, 06, and so on. Second minute means 01 and any odd numbered minute , 03, 05, etc. <br />.<br />So, if you were transmitting a CQ on the first minute, you should set the main window to TX 1st and select your CQ message. You should also use the auto transmit method. As illustrated below.<br />.<br /><br /><br />At the precise minute, your rig will transmit. It will send the CQ for about 48 seconds . You then will wait until the beginning of the next odd numbered minute and , if lucky, you may hear or see a signal responding to your CQ. Please be aware that you may NOT see a signal in the SPECJT or hear a signal with your ears but may actually be decoding a signal. After about 50 seconds in to the minute, a blue decode button on your screen should be active and around 55 seconds ,or so , any decoded signal will pop up on the screen. On my slow computer, the decoded signal sometimes does not pop up until several seconds in to the next minute . This can be annoying and confusing, so if this happens to you turn on QUICK DECODE and the decoding process will start about 5 seconds earlier. You will then get the decoded text in time to read the information before your next transmission. To turn on QUICK DECODE go to go to DECODE in the main graphical area, select JT65, and then Quick Decode as illustrated below<br /><br />.<br /><br /><br /><br />If, after CQing, you receive something like this <br />. 171500 0 -7 -0.1 471 3 <br />It probably means no one responded, or your rig did not hear anyone respond. This is essentially random noise.<br />.<br />If you received something like this ... <br />165200 10 -11 -0.2 -27 5 * YOURCALL WQ5S EM13<br />.<br />It means WQ5S heard you and is responding with your callsign , his callsign, and his grid locator which serves as a report (they may also respond sometimes with and R and a number instead of a grid square, this is a signal report) Here is an actual example..<br />.<br /><br />165100 12 -7 -0.1 97 3 * CQ VE5MU DO70 1 0<br />165200 10 -11 -0.2 -27 5 * VE5MU WQ5S EM13 1 0<br />.<br /><br />Lets pretend you are VE5MU (haven't we all wanted to be VE5MU at some point in our lives ?) You called CQ, WQ5S answered. Now what the heck do you do ? The new version now gives you a choice of what responding message format you can use. If you left-double click on the callsign of WQ5Q you will see<br />.<br /><br />Some standard messages have incorporated your callsign and his callsign automatically. However, the new recommended format for HF use of JT65A is that you access a different message set. Instead of left-double clicking on a received callsign , RIGHT-double click. At my location this causes a 20% increase in carpel tunnel syndrome symptoms, but hopefully all it causes at your house is the following.<br /><br />.<br /><br />Note, I have now switched from using VE5MU as an example to using UA0AET. In the above box, you will see that it not only copied the callsign of the other station when I right-double clicked, it also copied the signal to noise ratio which is illustrated in the TX2 and TX 3 boxes . In this case it is -7dB, a good signal! If you used the right-double click maneuver, you should note that the Auto-ON button has turned red. This means that your radio will begin transmitting automatically at the top of the next minute. Since you are the station calling "CQ", you most likely would have already selected auto-on.<br />.<br /><br />Before each transmission, you need to determine which of the possible six messages you will be sending. Obviously, if CQing, you will select TX6. So, if P5DX in North Korea has heard your CQ and has responded with:<br />.<br />VE5MU P5DX PM27<br />.<br />Now what the heck do you do? Well, just like in most other amateur radio modes, you respond with his/her callsign to let him know your heard him/her. You also respond with a signal report. Under the new "HF enhanced" version of WSJT-JT65A, you would respond with TX3 which is... "P5DX K3UK R-7"<br />.<br />P5DX would then send his report as ...VE5MU P5DX RRR (TX4)<br />.<br />You would then respond with either message TX4 also or some operators just skip to message TX5 and sent the 73.<br />.<br />P5DX may also send 73 but it is not required.<br />.<br />All of this assumes you are hearing each other well. Suppose you got the first couple of messages, but when P5DX took his/her minute to confirm your report with RO, you never received it. The convention is that you just send your previous message again. P5DX will receive it again (hopefully) and realize that this means you did not receive his RO. He will send it again and , if you copy it this time, you will send..... This format can be repeated for any of the message stages .<br /><br />Writing this down in a Bozo guide can make it more complicated than it really is. Remember that smart bloke that wrote the software? A dude called Joe. Joe is so smart that he stuck simple way of helping us bozos right in to the software. If you hold your SHIFT key down and press the F5 key at the same time, you will see something like this ...<br /><br />.<br /><br />Actually, I broke it down for us bozos. The chart above explains the newer method intended for HF use under fair to good conditions.<br />.<br />Alternative Message Format<br />.<br />As mentioned earlier, the new HF enhanced version should work well for most HF conditions. However, you may run in to some "old timers" who use the older method, or find someone using the older "short hand" messages because they can be decoded better when a signal is very weak. So, it may be useful for this Bozo's Guide to explain this message format too.<br />.<br />The author's chart best illustrates this:<br />.<br /><br /><br /><br /><br />Don't ask me what the OOO actually stand for, but this exchange means that you have received WQ5S’ information. If WQ5S received your 000's, he will respond with simply with RO, no call sign, just RO. This means he has received your 000's. After you receive his RO, you send message number TX4 by selecting it before your turn to transmit arrives. TX4 will transmit at the top of the minute and send RRR. Again, no calls signs, just RRR. This means you have received everything for a valid QSO, : A valid QSO consists of his callsign , the fact that he has your call sign correct, the acknowledgment that he received your OOO's . He will send you RRR to let you know that all is correct his end. Often, you then send the message number TX5 with a 73 in it. Some people type in extra info in this message like<br />.<br />73 TU good night ur best -7 db. This is optional and usually is typed in to TX1, message number 1.<br /><br />.<br />This will sounds confusing but after a couple of contacts you will have it easily figured out. If you did not receive the acknowledgment of the OOO's or an RR, just resend and hopefully you will get it the next try. <br />.<br />Remember, the teams designing the software are not bozos, they are smart blokes and their inventiveness is extremely helpful to us bozos. In their cleverness, they designed a mode that actually changes the nature of the digital tones depending on what is going on in the QSO. This is almost like switching from SSB phone to CW in the middle of a QSO because you want to make sure your weak signal got through. In JT65A (and other modes in WSJT) a CQ message , TX1, will appear differently on the SpecJT waterfall that other messages. The RO or 73 messages will appear different too. Let's take a look at the picture below<br />.<br /><br />Short Hand Message in older format and for WEAK signal decode<br />(I have RRR confused with RO, I will re-do this graphic later when I get a better capture, but it does basically illustrate what you need to know)<br />.<br />I have illustrated , in the above picture, the typical patterns you will see in the SpecJT. With a little experience you will be able to visually SEE what is going on in a QSO, and know which part of the exchange is taking place. You will also be able to HEAR the difference because the tones sound different to the human ear. Knowing what the different stages (messages) of a QSO sound like, can be useful when working weak signals in a pile-up.<br />.<br />You will note that the CQ signal is quite distinctive, much wider than the short-hand messages.. Some people get confused by the fact that the RO, RRR messages appear without a call sign. Was he really coming back to me? It is confusing, that is why K1JT revised the software and added the new message formats that can be accessed via double right-clicking on a callsign. These messages have callsigns throughout and avoid the confusion.<br />However, the nature of these "shorthand" messages is such that they can be decoded a further -5dB in to the mud ! This can make the difference between working that rare DX station or not. <br />.<br />Some people will send you a message that says something “Best -18 TU 73". These smart people are manually typing the message in to the TX1 message text box and sending it instead of the optional TX5 message. Since it is sent after a QSO has been validated by RRR, it is perhaps not that essential that the message get through, so they use the wider , less robust, TX1 message. <br />.<br />Responding to a CQ<br />.<br />Take a look at this <br />.<br />182800 9 -13 0.4 -124 4 * CQ N4WO EL88 1 0<br />182900 10 -15 0.0 -73 3 * CQ DK7OM JO53 1 0<br />183000 7 -10 0.0 -124 3 * CQ N4WO EL88 1 0<br />183100 7 -19 -0.1 -73 3 * CQ DK7OM JO53 1 0<br />183200 7 -15 0.0 -124 21 * CQ N4WO EL88 1 0<br /><br />.<br />N4WO is CQ on the first minute ( 1828, 1830, 1832, ) and DK7OM is transmitting the second minute (1829 and 1831) .<br />.<br />Both are within 61 Hz or so of each other but are not hearing each other. If you want to work them, you have a choice. Who do you want to work? The new HF enhanced version makes the choice a little easier. If you want to work N4WO there are three things you need to do..<br />.<br />1. Determine which minute N4WO is transmitting.<br />2. Set the messages group with callsigns and signal report.<br />3 Match the received frequency with your transmit frequency<br />.<br /><br /><br />Setting 1st or Second Minute : In the above example, N4WO was transmitting at 183200, 32 minutes past the hour, and even numbered minute. This is the first minute, so you need to unchecked the TX1st box so that you transmit the second minute. You will do this just once at the beginning of the QSO. The second minute sequence will be maintained throughout.<br />.<br />Setting messages group with callsigns and signal report.: If you wanted to work N4WO you would have seen something like...<br />.<br />183200 9 -13 0.4 -124 4 * CQ N4WO EL88 1 0 Right-Double click will populate the message groups with the callsigns and signal reports..<br />.<br /><br />Matching Received and TX Frequency: After you have selected N4WO, above, you can then double click on the signal in the SpectJT (or on the red spike in the main graphical display ) and then click on the TXDF button. It will turn red and the frequency deviation will be shown. Using the above example, it would read TXDF= -124. That's it, you are matched!<br />.<br /><br />So, at the top of the minute, your rig sends TX1, which is N4WO VE5MU DO70<br />.<br />N4WO receives this information and now knows that you are calling him and his signal report is -13 db.<br />.<br />He sends TX2.... VE5MU N4WO -8<br />.<br />He is letting you know that he is receiving you with a signal to noise ratio of -8 dB.<br />.<br />You then send... N4WO VE5MU RRR or the 73 message. <br />.<br /><br />This tells N4WO that your received his R-8 report and that you are "rogering" the report. N4WO will like this because when he receives "RRR" or 73 it makes his contact official. He may reply with another RRR, rogering your information or he may skip straight to a 73 message. "VE5MU N4WO RRR" or "VE5MU N4WO 73"<br />.<br />So, the QSO is "good" now that you have received his "RRR" or "73" . <br />.<br />Instead of TX5's basic 73. Some folks get a little fancy and send a brief message , perhaps like "Tnx John 73". This is usually done by typing the "Tnx John 73" in to the message box TX1. <br />.<br />You will notice that when transmitting, the message box you have selected changes to a certain color. More on this later, it just signifies what type of message you are sending. I am mentioning it here because some new users panic when they see the message box turn RED. Red does not mean your rig is about to explode, it does not indicate anything bad at all!<br />.<br />Ok, I just worked North Korea on 160M, where do I log it. ? <br />.<br />Clicking on the "log QSO" button will log the QSO but you will need to first tell WSJT which band you are on, the software does NOT read your radio's frequency. To do this, click BAND in the main graphical display and select the band. Note, the bands are labeled via Frequency not wavelength. e.g "14" is 14 mHz or 20 metres.<br />.<br />You can view the log by opening the log.txt file with a text editor , like Wordpad or Note pad. log.txt can be found in your main WSJT folder.<br />.<br />In the folder there is also another interesting text file, called all.txt. This tells you knot only who you log but who you received and when you transmitted.<br />e.g.<br />.<br />010100 3 -17 -0.4 -13 4 # K3UK ZS6BUN KG43 OOO 1 0<br />010300 3 -13 -0.1 -16 3 # K3UK ZS6BUN KG43 OOO 1 0<br />010414 Transmitting: JT65A RO (Shorthand)<br />010500 10 -19 -15 1 RRR ? <br />010612 Transmitting: JT65A RRR (Shorthand)<br />010700 10 -16 -15 4 73 ? <br />010815 Transmitting: JT65A 73 (Shorthand)<br />010900 6 -13 0.3 -16 1 * TNX ANDY -11 1 0<br /><br /><br />.<br />I'm hooked, where can a get more of this J65A drug?<br />.<br />Go to http://www.chris.org/cgi-bin/jt65talk this is a great resource for meeting other who are looking for QSOs. There is a large, very active email discussion group at http://groups.yahoo.com/group/digitalradio/<br />This group has a lot of discussion about J65A HF and other digital modes. A WSJT specific group can be found at http://groups.yahoo.com/group/wsjtgroup/<br />.<br /><br />I've worked a lot of JT65A and am not getting the same high anymore, is there a more potent drug?<br />The bigger "high" can be gotten from EME or Meteor Scatter operations. Once addicted to this, you become known as a Ping Jockey. See http://www.pingjockey.net/cgi-bin/pingtalk for more on this addiction.<br />.<br /><br />Trouble :<br />.<br />Remember that "DOS-type" window that I told you to ignore at the beginning of this document. This can actually tell you if there is a problem with the sound card device or if your PTT circuit is not open. If you suspect a problem of this nature, log on to http://groups.yahoo.com/group/wsjtgroup/ and ask for help their.<br />.<br />Soundcard Clock<br />.<br />If you have an obvious JT65A signal that you can hear and the waterfall sees but it is NOT decoding, you may want to make sure your soundcard clock is accurate. Most digital software like MultiPSK, MixW, and Winbarbler, have features that will enable you to adjust your soundcard and keep it accurate. The WSJT software displays your clock rate as highlighted below<br />.<br /><br />You want your settings to be around a 1.0 . <br />.<br />It appears that WSJT also can adjust the soundcard rate, check the SETUP/OPTIONS /RATE IN /RATE OUT area.<br /><br />.<br />Audio Levels in to the Soundcard<br />.<br />As mentioned earlier in this document, you may experience problems in decode if the audio level is too strong or too low. You can lower or raise these values first with the Gain Control slider in SpecJT and additionally with your soundcard line-in control mixer. With no signal present, -2dB seems to be a good level. These are not always critical but if you cannot decode an obviously clear signal you might want to make sure you are not in the -20 dB or + 20 db range. See below for key areas in control of the audio level.<br /><br />.<br /><br />If you cannot get enough audio from your rig to the PC soundcard, consider using the MIC-IN jack on you soundcard. Be careful not to put TOO much audio in to your soundcard. <br />.<br />Acknowledgment:<br />.<br />As a complete bozo, I needed help understanding things, Thanks to all that responded to my questions in the first few weeks of learning. Thanks to David WD4KPD, Tony KT2Q. Chris, N2YYZ, Steinar LA5VNA, Mike VE3FGU, Colin K4CML, John VE5MU, Bill N9DSJ, George G4PCI, Bruce, N5SIX, John W5UBW, Walt K5YFW, Scott VE7TIL, John N2JH, Al WB7SWW. Marshall W9RVG. Joe K1JT. More to be added soon.<br /><br />.<br />K3UK WSPR Guide<br />I am not sure if it is really needed nowadays, but I just updated my<br />quick guide to WSPR by K1JT. This reflects the latest significant<br />advancements that Joe has programmed.<br />.<br />K3UK's Quick Guide to WSPR Revised July 26 2008.<br />.<br />There are now two options for using WSPR. WSPR.exe is the manned<br />beacon only software . The latest beta release of WSJT now includes a<br />version of WSPR that allows for two-way "QSOs". WSJT also includes<br />modes FSK440, JT6M, JT65 variants, JT4 variants, JT2, and may also<br />add JT6a soon,<br />.<br />This quick guide has been updated to reflect the WSPR changes. The<br />quick guide to the QSO mode appears towards the end of this guide.<br />.<br />General Information:<br />.<br />Download software from<br />.<br />http://physics.princeton.edu/pulsar/K1JT/WSPR100.EXE<br />http://physics.princeton.edu/pulsar/K1JT/WSJT700r973.EXE<br />.<br />Get detailed help from<br />.<br />http://physics.princeton.edu/pulsar/K1JT/WSPR_Quick_Start.TXT<br />http://physics.princeton.edu/pulsar/K1JT/WSJT_User_600.pdf<br />http://www.obriensweb.com/bozoguidejt65a.htm (a little dated )<br />.<br /><br /><br />*** WSPR : Very LOW Power Attended Beacon Mode ***<br />.<br />1. First , remember it is NOT a QSO mode. It is "manned experimental<br />propagation transmitter". Stations transmit the audio tones at varying<br />times (as determined by the software) for TWO minutes. It is a "slow"<br />mode, so does well in very weak conditions. MANNED is important it is<br />not intended for unattended operations. Get the software from<br />http://physics.princeton.edu/pulsar/K1JT/WSPR100.EXE<br />.<br />2. Make sure your PC clock is sync'd with an Internet time server. If<br />your clock is off by more than 5 seconds or so, other stations my have<br />trouble decoding you.<br />.<br />3. Keep you power low, most are one watt or less, some 5 watts. More<br />than 5 watts can cause too strong a signal and the software sometimes<br />has difficulty decoding very strong signals.<br />.<br />4. In the SETUP/Options area of the software. Enter your callsign,<br />grid square , PTT port, and power in dBMm (example 30 dBM = one watt).<br />Go to http://www.radioing.com/eengineer/rfcalc.html for some dB to<br />watt conversion help. (tnx K2MO).<br />.<br />5. That is all you need to do for set-up , if you have more than one<br />soundcard in your PC, you may need to additionally change the device<br />settings if you want to use the NON-default soundcard.<br />.<br />6. Tune to a known WSPR/MEPT frequency. 30M is the most popular with<br />10.138,6 the standard listening frequency.<br />.<br />7. In the main WSPR window, enter 10.1386 in the RX box and then<br />choose a TX frequency<br />.<br />8. The TX frequency is the frequency the soundcard will generate the<br />tones. Your RIG should NOT be in split mode. Just keep your VFO on<br />10.1386 USB. Your TX audio tones should be around 1500 Hz above the RX<br />frequency. The software has a default 30M TX frequency, I suggest you<br />change it so that everyone is NOT transmitting on the same frequency.<br />I use 10.140119 In the following example, you will see what other<br />frequencies people are using ..<br />.<br />080409 0120 4 -16 0.7 10.140163 VE7TIL CN89 30<br />080409 0120 5 -14 -0.6 10.140198 WA7ADK DN31 18<br />.<br />VE7TIL was received by my rig on 10.149163<br />WA7ADK was received by my rig on 10.140198<br />.<br />Other slow mode weak signal operators use near by frequencies, WSPR<br />users are asked to make sure that you do not set you transmit settings<br />BELOW 10.140100 since the "visual" MEPT folks use that area.<br />.<br />9. In the main WSPR window you can choose to select the "RX" button<br />just to receive ONLY or you can select 20%, 25%, or 33% T/R option.<br />The T/R option is a ratio of how often your rig transmits in one hour.<br />I usually choose 20%/. The software then listens most of the time but<br />20% of the hour it will transmit. Sometimes , when you boot up the<br />software it may wait several minutes before it decides to transmit. If<br />you want to force a transmit, choose the TX option. Make sure you turn<br />this option OFF eventually because your rig will transmit for 2<br />minutes , pause for a few seconds , and then transmit for another two<br />minutes and repeat UNTIL you turn it off! Please note that the<br />software , when it is going to transmit, waits until the top of an<br />even minute. It does NOT transmit every even minute if you choose T/R<br />20, 25, 33%, but when it does transmit it will wait until the top of<br />an even minute.<br />.<br />10. When you run the software at first, you will see an inactive<br />waterfall. The current version has a waterfall that updates ONLY every<br />two minutes. After your software have run for a few minutes you may<br />see WSPR signals as narrow lines that are HORIZONTAL on the waterfall.<br />The waterfall does not display the signal "live" but a later version<br />may add this capability<br />.<br />11. After the software has run for a few minutes you may receive<br />decoded signals, they will be displayed as... 080409 0200 2 -14 1.0<br />10.140128 KL7QR DM33 30 The above line is date, time decoded, sync,<br />signal to noise ration in dB, DT, received frequency, callsign, grid<br />square, noise level. Please note that this mode is very NARROW, about<br />6HZ wide. You can find a lot of signals in the 200 Hz wide frequency<br />range that the software monitors. The software has the ability to<br />decode several signals at the same time, I recently decoded FIVE<br />signals at the signals. I started a web page for people to spot each<br />other, it became so popular that is was moved to another server and a<br />database of all spots was created. You can use a small batch file to<br />automate the uploading of your received signals to the database. Go to<br />http://www.wsprnet.org/ for details. This site is now run by W1BW and<br />the coding was done by N8FQ. As I type this, the following stations<br />are connected<br />Users seen in last 10 minutes:<br />9V1LF - F4FQM - F6IRF - K1JT - K3UK - K7ZTM - KS7S - LA6TPA - N3TFM -<br />TF3HZ - VE7KPB - W1BW - WD4KPD<br />.<br />and some of the latest in the database are...<br />Power Reported Distance Date Call Freq SNR Grid dBm Rec by loc km mi<br />.<br />2008-07-26 16:36 PA2ABC 10.140208 -10 0 JO22jq<br /> +37 <br />5.012 F1TE IN94qs 966 600<br />2008-07-26 16:34 N2BJW 10.140159 -17 0 FN34im <br />+27 0.501<br /> W2RXG EL88xu 1907 1185<br />2008-07-26 16:34 NN6RF 10.140113 -25 0 CM87uw <br />+23 0.200<br /> W2RXG EL88xu 3840 2386<br />2008-07-26 16:34 PA2ABC 10.140204 -23 0 JO22jq<br /> +37 <br />5.012 9V1LF OJ11vh 10499 6524<br />2008-07-26 16:34 PA2ABC 10.140206 -19 0 JO22jq<br /> +37 <br />5.012 TF3TTY HP94ac 1984 1233<br />2008-07-26 16:34 PA2ABC 10.140184 -16 0 JO22jq<br /> +37 <br />5.012 UNLIS JN89bo 861 535<br />.<br />There are many DX stations to be spotted via WSPR.<br />.<br />-------------------------------------------------------------------------<br /><br /><br />.<br />*** TW0-WAY QSO WSPR MODE ****<br />.<br />The latest beta version of WSJT , available from<br />http://physics.princeton.edu/pulsar/K1JT/WSJT700r973.EXE, now allows<br />for two-way communication. The transmitted messages differ in format<br />from the one-way WSPR mode , therefore this version of WSPR is NOT the<br />version you want to use to automatically upload your reception reports<br />to WSPR.org. Here is how to do two-way WSPR:<br />.<br />Download and install WSJT . Boot up the software. Click on SETUP<br />then OPTIONS. Enter in your grid square, call sign , PTT port , and<br />setting for your sound card. My system has one sound card and I use 0<br />for both Audio IN and Audio Out. Exit the options area.<br />.<br />Now click on MODE and select WSPR . Next click on the MONITOR button<br />towards the middle of the screen. It should turn green and you are<br />now set up to begin receiving audio from your radio (sorry, I forgot<br />that part...you DO need a radio capable of being in SSB mode , one<br />that is very stable. The radio needs to have audio in and out cables<br />connected to the souncard of your computer).)<br />.<br /><br />At the bottom of the screen you will now see a little box entitled RX<br />Noise. It will give you a reading. Vary your audio level IN to the<br />computer so that it is around 0 dB when there are no signals present.<br />The Rx noise level will increase when a strong signal is detected.<br />The main graphic display in WSJT is a powerful tool but a tad<br />overwhelming for the rookie. Read the K3UK Complete Bozo's Guide to<br />HF JT65A for more about this display method, or even read the original<br />WSJT manual! I suggest ignoring the main graphical display and<br />instead advise that you use a "waterfall" display with WSJT. Click on<br />VIEW and select SPECT JT.<br />.<br />Now you will see a waterfall-type display. You can click on OPTIONS<br />and set volume levels if you wish. Select FREQUENCY AXIS. Select a<br />speed suitable for you PC hardware. I simply use 3.<br />.<br />Almost there now.<br />.<br />Turn your dial to 10139, and wait a while. If WSPR is present you<br />will see a very narrow vertically displayed signal . If you see one,<br />you need to tune it in using the software. Take your mouse and click<br />on the signal that you see in SPECJT. After you have clicked, you<br />will see a green line at the top of the SPECJT screen. It will shift<br />to where you clicked. Consider the green line to be a guide as to the<br />frequency range , or range on the waterfall, that you will be capable<br />of decoding signals . If you suddenly see a signal outside of the<br />range of the green line you need to again click your mouse and the<br />green line will now move to where the new signal was spotted. The<br />green line range can be changed. Click on the TOL button in WSJT and<br />the TOLerance number should change from 50 to 100 Hz. I say "should"<br />because I swear I could do this a few days ago, today when I tried<br />nothing changed.<br />.<br />If you came across a signal that is in the middle of a transmission,<br />you may not be able to decode it. The signals start at the TOP of the<br />minute and last TWO MINUTES. You will need to wait for the station to<br />start again if you missed it initially. Again, make sure your<br />computers clock is very accurate.<br />.<br />That's pretty much it for receiving Two-way WSPR. With your dial set<br />at 10.139 USB you may see some signals at around 1500 Hz in the<br />SPECJT waterfall. These are usually the ones calling CQ in WSPR mode.<br />You will probably see several manned beaconing stations at around the<br />1200 Hz level. They will not be interested in a two-way QSO. Do not<br />call CQ or initiate a two-way WSPR QSO in the beacon section of the<br />band. You can , since there are no rules, but it is requested that<br />you voluntarily conduct WSPR QSO a little further up (in the same area<br />JT65A HF signals can be found).<br />.<br /><br />TRANSMITTING.<br /><br />To answer a CQ you should first double click on a received callsign.<br />That callsign will then appear in the message area in the lower<br />right-hand section of WSJT. You need to select a message that you<br />intend to reply with. They are self-explanatory, but just in case,<br />check http://physics.princeton.edu/pulsar/K1JT/WSPR_mode.pdf for<br />details from the author Joe K1JT. Click the AUTO IS OFF and it will<br />change to AUTO IS ON, if you so desire. The will allow your<br />transmissions to start automatically at the top of the minute. It<br />usually requires you to have the message you intend to send already<br />selected (click on the little circle to the right of the message0 .<br />You can also send 'on the fly” by clicking on TX1 through 6. If you<br />start transmitting late, too far past the top of the minute, the other<br />station may not get enough data to decode you. You can do lots of<br />other fancy stuff to the message format but I suggest you read the<br />WSJT Guide or K3UK Bozo Guide for more on that. You can change the<br />number in the S report to indicate the level of reception.<br />.<br />Enjoy the latest from K1JT<br />.<br />73 de Andy K3UK<br />..WR5Jhttp://www.blogger.com/profile/16316513702643319581noreply@blogger.com1tag:blogger.com,1999:blog-4632435085083780021.post-86765606467060632352009-07-16T09:22:00.000-07:002009-07-16T10:40:57.595-07:00Blog Post 7 – EasyPAL—Digital Slow Scan Television software using DRM – Digital Radio Mondiale<meta equiv="Content-Type" content="text/html; charset=utf-8"><meta name="ProgId" content="Word.Document"><meta name="Generator" content="Microsoft Word 11"><meta name="Originator" content="Microsoft Word 11"><link rel="File-List" href="file:///C:%5CDOCUME%7E1%5Ccblack%5CLOCALS%7E1%5CTemp%5Cmsohtml1%5C03%5Cclip_filelist.xml"><link rel="Edit-Time-Data" href="file:///C:%5CDOCUME%7E1%5Ccblack%5CLOCALS%7E1%5CTemp%5Cmsohtml1%5C03%5Cclip_editdata.mso"><!--[if !mso]> <style> v\:* {behavior:url(#default#VML);} o\:* {behavior:url(#default#VML);} w\:* {behavior:url(#default#VML);} .shape {behavior:url(#default#VML);} </style> <![endif]--><o:smarttagtype namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="place"></o:smarttagtype><o:smarttagtype namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="City"></o:smarttagtype><!--[if gte mso 9]><xml> <w:worddocument> <w:view>Normal</w:View> <w:zoom>0</w:Zoom> <w:punctuationkerning/> <w:validateagainstschemas/> <w:saveifxmlinvalid>false</w:SaveIfXMLInvalid> <w:ignoremixedcontent>false</w:IgnoreMixedContent> <w:alwaysshowplaceholdertext>false</w:AlwaysShowPlaceholderText> <w:compatibility> <w:breakwrappedtables/> <w:snaptogridincell/> <w:wraptextwithpunct/> <w:useasianbreakrules/> <w:dontgrowautofit/> </w:Compatibility> <w:browserlevel>MicrosoftInternetExplorer4</w:BrowserLevel> </w:WordDocument> </xml><![endif]--><!--[if gte mso 9]><xml> <w:latentstyles deflockedstate="false" latentstylecount="156"> </w:LatentStyles> </xml><![endif]--><!--[if !mso]><object classid="clsid:38481807-CA0E-42D2-BF39-B33AF135CC4D" id="ieooui"></object> <style> st1\:*{behavior:url(#ieooui) } </style> <![endif]--><style> <!-- /* Font Definitions */ @font-face {font-family:Verdana; panose-1:2 11 6 4 3 5 4 4 2 4; mso-font-charset:0; mso-generic-font-family:swiss; mso-font-pitch:variable; mso-font-signature:536871559 0 0 0 415 0;} /* Style Definitions */ p.MsoNormal, li.MsoNormal, div.MsoNormal {mso-style-parent:""; margin:0in; margin-bottom:.0001pt; mso-pagination:widow-orphan; font-size:12.0pt; font-family:"Times New Roman"; mso-fareast-font-family:"Times New Roman";} h1 {mso-style-next:Normal; margin-top:12.0pt; margin-right:0in; margin-bottom:3.0pt; margin-left:0in; mso-pagination:widow-orphan; page-break-after:avoid; mso-outline-level:1; font-size:16.0pt; font-family:Arial; mso-font-kerning:16.0pt; font-weight:bold;} h3 {mso-margin-top-alt:auto; margin-right:0in; mso-margin-bottom-alt:auto; margin-left:0in; mso-pagination:widow-orphan; mso-outline-level:3; font-size:13.5pt; font-family:"Times New Roman"; font-weight:bold;} a:link, span.MsoHyperlink {color:blue; text-decoration:underline; text-underline:single;} a:visited, span.MsoHyperlinkFollowed {color:#606420; text-decoration:underline; text-underline:single;} p {mso-margin-top-alt:auto; margin-right:0in; mso-margin-bottom-alt:auto; margin-left:0in; mso-pagination:widow-orphan; font-size:12.0pt; font-family:"Times New Roman"; mso-fareast-font-family:"Times New Roman";} @page Section1 {size:8.5in 11.0in; margin:1.0in 1.25in 1.0in 1.25in; mso-header-margin:.5in; mso-footer-margin:.5in; mso-paper-source:0;} div.Section1 {page:Section1;} /* List Definitions */ @list l0 {mso-list-id:612252916; mso-list-template-ids:702159778;} @list l0:level1 {mso-level-tab-stop:.5in; mso-level-number-position:left; text-indent:-.25in;} ol {margin-bottom:0in;} ul {margin-bottom:0in;} --> </style><!--[if gte mso 10]> <style> /* Style Definitions */ table.MsoNormalTable {mso-style-name:"Table Normal"; mso-tstyle-rowband-size:0; mso-tstyle-colband-size:0; mso-style-noshow:yes; mso-style-parent:""; mso-padding-alt:0in 5.4pt 0in 5.4pt; mso-para-margin:0in; mso-para-margin-bottom:.0001pt; mso-pagination:widow-orphan; font-size:10.0pt; font-family:"Times New Roman"; mso-ansi-language:#0400; mso-fareast-language:#0400; mso-bidi-language:#0400;} </style> <![endif]--><u><span style="color: rgb(51, 102, 255);"><span style="font-size:130%;"><a href="http://educationalradionet.blogspot.com/2009/07/blog-post-5-fldigi-wrap-up-review-and.html"><span style="color: rgb(51, 102, 255);">Blog Post 7 – EasyPAL—Digital Slow</span></a> Scan Television software using DRM – Digital Radio Mondiale ** </span><o:p></o:p></span></u> <p class="MsoNormal" style="margin: 0in -0.25in 0.0001pt -27pt;"><i style=""><span style="color: rgb(51, 102, 255);font-size:9;" ><span style=""> </span>**<span style=";font-size:85%;" > </span><span style="font-size:85%;">MAHN-DEE-AL (like DEE rhymes with BEE and <st1:state st="on"><st1:place st="on">AL</st1:place></st1:state> as in Senator Al Franken)</span><o:p></o:p></span></i></p> <p class="MsoNormal" style="margin: 0in -0.25in 0.0001pt -27pt;"><i style=""><span style="font-size:9;"><o:p> </o:p></span></i></p> <p class="MsoNormal" style="margin: 0in -0.25in 0.0001pt -27pt; text-indent: 45pt;">Wednesday July 22, 2009</p> <p class="MsoNormal" style="margin: 0in -0.25in 0.0001pt -27pt;"><o:p> </o:p></p> <p class="MsoNormal" style="margin: 0in -0.25in 0.0001pt -27pt;"><b><span style="font-size:16;">This is Curt Black, WR5J with the Educational Radio Net Please standby for a Digital SSTV QST <o:p></o:p></span></b></p> <p class="MsoNormal" style="margin: 0in -0.25in 0.0001pt -27pt;"><o:p> </o:p></p> <p class="MsoNormal" style="margin: 0in -0.25in 0.0001pt -27pt;"><b style=""><span style=";font-size:14;color:black;" >Before the net. Please download tonight’s software – EASYPAL and set it up according to the blog and WA-DIGITAL instructions.<span style=""> </span><o:p></o:p></span></b></p> <p class="MsoNormal" style="margin: 0in -0.25in 0.0001pt -27pt;"><b style=""><span style=";font-size:14;color:black;" ><o:p> </o:p></span></b></p> <p class="MsoNormal" style="margin: 0in -0.25in 0.0001pt -27pt;"><b style=""><span style=";font-size:14;color:black;" ><!--[if gte vml 1]><v:shapetype id="_x0000_t75" coordsize="21600,21600" spt="75" preferrelative="t" path="m@4@5l@4@11@9@11@9@5xe" filled="f" stroked="f"> <v:stroke joinstyle="miter"> <v:formulas> <v:f eqn="if lineDrawn pixelLineWidth 0"> <v:f eqn="sum @0 1 0"> <v:f eqn="sum 0 0 @1"> <v:f eqn="prod @2 1 2"> <v:f eqn="prod @3 21600 pixelWidth"> <v:f eqn="prod @3 21600 pixelHeight"> <v:f eqn="sum @0 0 1"> <v:f eqn="prod @6 1 2"> <v:f eqn="prod @7 21600 pixelWidth"> <v:f eqn="sum @8 21600 0"> <v:f eqn="prod @7 21600 pixelHeight"> <v:f eqn="sum @10 21600 0"> </v:formulas> <v:path extrusionok="f" gradientshapeok="t" connecttype="rect"> <o:lock ext="edit" aspectratio="t"> </v:shapetype><v:shape id="_x0000_i1025" type="#_x0000_t75" style="'width:7in;"> <v:imagedata src="file:///C:\DOCUME~1\cblack\LOCALS~1\Temp\msohtml1\03\clip_image001.png" title=""> </v:shape><![endif]--><!--[if !vml]--><img src="file:///C:/DOCUME%7E1/cblack/LOCALS%7E1/Temp/msohtml1/03/clip_image002.jpg" shapes="_x0000_i1025" width="672" border="0" height="487" /><!--[endif]--><o:p></o:p></span></b></p> <p class="MsoNormal" style="margin: 0in -0.25in 0.0001pt -27pt;"><b style=""><span style=";font-size:14;color:black;" ><o:p> </o:p></span></b></p> <p class="MsoNormal" style="margin: 0in -0.25in 0.0001pt -27pt;"><b style=""><span style=";font-size:14;color:black;" >As we discussed last week with MMSSTV, Slow Scan TV (SSTV) is a way to get the high-information density of visual images shoe-horned into the audio-bandwidth typically used by the human voice of about 2.5kHz.<span style=""> </span>For full motion NTSC video requires a bandwidth of about 4.5MHz or 9.0MHz if you use both sidebands as you transmit– so minimally our shoehorn is working with a ratio of about 2000/1.<span style=""> </span>We accomplish this by using more than 1/30<sup>th</sup> of a second to transmit our images.<span style=""> </span>In this case 30 to 300 seconds is more typical.<o:p></o:p></span></b></p> <p class="MsoNormal" style="margin: 0in -0.25in 0.0001pt -27pt;"><b style=""><span style=";font-size:14;color:black;" ><o:p> </o:p></span></b></p> <p style="margin: 5pt -0.25in 5pt -27pt;"><b style=""><span style=";font-size:14;color:black;" >Digital Radio Mondiale or DRM means "Digital World Radio."<span style=""> </span><span style=""> </span>DRM is a fairly new digital radio standard for use by HF broadcasters. The DRM standard uses a bandwidth from 4.5 KHz and up to and beyond 20 KHz using OFDM modulation. <span style=""> </span>It provides FM quality stereo audio over HF as well as the ability to send data.<span style=""> </span><span style=""> </span>Dream is a software implementation of a DRM receiver. <span style=""> </span><o:p></o:p></span></b></p> <p style="margin: 5pt -0.25in 5pt -27pt;"><b style=""><span style=";font-size:14;color:black;" >The HamDream software is a modified form of Dream by Cesco HB9TLK. HamDream uses only 2.5 KHz bandwidth and is the basis for several 2.5 khz DRM programs.<span style=""> </span>WinDRM replaced HamDream software by Cesco and it uses either <span style="">2.3 KHz or 2.5 KHz</span> bandwidth. It also has a digital voice mode. <span style=""> </span>HamDRM is a Windows DLL program by Cesco based on his WinDRM program. <o:p></o:p></span></b></p> <p class="MsoNormal" style="margin-right: -0.25in;"><b style=""><span style=";font-size:14;color:black;" ><o:p> </o:p></span></b></p> <p class="MsoNormal" style="margin: 0in -0.25in 0.0001pt -27pt;"><b style=""><span style=";font-size:14;color:black;" >EasyPAL is a piece of software by Erik, VK4AES, that uses DRM encoding and allows us to send images.<span style=""> </span>PAL is just the European standard that corresponds to our NTSC video standard.<span style=""> </span>EasyPAL, just like MMSSTV allows us to fit our image into a standard sideband voice bandwidth.<span style=""> </span>However, instead of audio frequencies corresponding to brightness and colors, images are disassembled pixel by pixel and sent as a digital stream that is decoded and reassembled into our image.<span style=""> </span><o:p></o:p></span></b></p> <p class="MsoNormal" style="margin: 0in -0.25in 0.0001pt -27pt;"><b style=""><span style=";font-size:14;color:black;" ><o:p> </o:p></span></b></p> <p class="MsoNormal" style="margin: 0in -0.25in 0.0001pt -27pt;"><b style=""><span style=";font-size:14;color:black;" >This digital format allows us to send considerable additional information including data on our station, the filename, image data, and ultimately, much more than just images.<span style=""> </span>If you look at the menu bar you will see “LOAD ANY” which is the clue that we can send any type of file on your computer.<span style=""> </span>Just like with FLDIGI, with great power comes great responsibility.<span style=""> </span>We have that same training issue we did with FLDIGI of not sending a megabyte when 2 kilobytes will do.<span style=""> </span><o:p></o:p></span></b></p> <p class="MsoNormal" style="margin: 0in -0.25in 0.0001pt -27pt;"><b style=""><span style=";font-size:14;color:black;" ><o:p> </o:p></span></b></p> <p class="MsoNormal" style="margin: 0in -0.25in 0.0001pt -27pt;"><b style=""><span style=";font-size:14;color:black;" >Another amazing thing about this software is that we can request “fills” or retransmission of any blocks not received perfectly (hit that BSR button – BAD SEGMENT REQUEST and a message is formatted that reports to the sending station the specific segments numbers that require retransmission.<span style=""> </span>The sending station can collect these reports (Visible with the FIX button) and then select them one at a time to retransmit the needed data for a perfectly received transmission at each station. <o:p></o:p></span></b></p> <p class="MsoNormal" style="margin: 0in -0.25in 0.0001pt -27pt;"><b style=""><span style=";font-size:14;color:black;" ><o:p> </o:p></span></b></p> <p class="MsoNormal" style="margin: 0in -0.25in 0.0001pt -27pt;"><b style=""><span style=";font-size:14;color:black;" >OR, <span style=""> </span>if you prefer, you may avoid all this re-transmission stuff.<span style=""> </span>You can Reed-Solomon encode everything you send to increase the probability your information will make it through the first time.<span style=""> </span><span style=""> </span>Just select the encoding appropriate to the band and mode – for tonight’s demo through an FM repeater, I’ve got “very light” encode on.<span style=""> </span>RS Encoding is controlled by the check box next to the RS1 to RS4.<span style=""> </span>Left click to toggle encoding.<span style=""> </span>Right click to change from light encoding to heavy.<span style=""> </span><o:p></o:p></span></b></p> <p class="MsoNormal" style="margin: 0in -0.25in 0.0001pt -27pt;"><b style=""><span style=";font-size:14;color:black;" ><o:p> </o:p></span></b></p> <p class="MsoNormal" style="margin: 0in -0.25in 0.0001pt -27pt;"><b style=""><span style=";font-size:14;color:black;" >If you choose RS4 – your recipient can loose up to 50% of the data and still put your file back together perfectly without any resending..<span style=""> </span>That is why you may see the picture (or file) appear before the transmission is done.<span style=""> </span>You may have enough data to assemble a perfect picture even though the progress bar is only ½ of the way through the transmission.<span style=""> </span>Tonight I’m using between 16 and<span style=""> </span>64 simultaneous data streams.<span style=""> </span>Click the QAM button to set the number of data carriers used 4-16-or-64.<span style=""> </span><o:p></o:p></span></b></p> <p class="MsoNormal" style="margin: 0in -0.25in 0.0001pt -27pt;"><b style=""><span style=";font-size:14;color:black;" ><o:p> </o:p></span></b></p> <p class="MsoNormal" style="margin: 0in -0.25in 0.0001pt -27pt;"><b style=""><span style=";font-size:14;color:black;" ><o:p> </o:p></span></b></p> <p class="MsoNormal" style="margin: 0in -0.25in 0.0001pt -27pt;"><b style=""><span style=";font-size:14;color:black;" ><o:p> </o:p></span></b></p> <p class="MsoNormal" style="margin: 0in -0.25in 0.0001pt -27pt; text-align: center;" align="center"><b style=""><span style=";font-size:20;color:black;" >Getting Started<o:p></o:p></span></b></p> <p class="MsoNormal" style="margin: 0in -0.25in 0.0001pt -27pt;"><b style=""><span style=";font-size:14;color:black;" ><o:p> </o:p></span></b></p> <p class="MsoNormal" style="margin: 0in -0.25in 0.0001pt -27pt;"><b style=""><span style=";font-size:14;color:black;" >Pull the software off the Yahoo Group Files Section at </span></b><b style=""><span style=";font-size:14;color:blue;" ><a href="http://groups.yahoo.com/group/wa-digital/files/">http://groups.yahoo.com/group/wa-digital/files/</a></span></b><b style=""><span style=";font-size:14;color:black;" ><o:p></o:p></span></b></p> <p class="MsoNormal" style="margin: 0in -0.25in 0.0001pt -27pt;"><b style=""><span style=";font-size:14;color:blue;" ><o:p> </o:p></span></b></p> <p class="MsoNormal" style="margin: 0in -0.25in 0.0001pt -27pt;"><b style=""><span style=";font-size:14;color:black;" >Or go to the source at </span></b><b style=""><span style=";font-size:14;color:blue;" ><a href="http://vk4aes.com/">http://vk4aes.com/</a></span></b><b style=""><span style=";font-size:14;color:black;" ><span style=""> </span><o:p></o:p></span></b></p> <p class="MsoNormal" style="margin: 0in -0.25in 0.0001pt -27pt;"><b style=""><span style=";font-size:14;color:black;" >or<o:p></o:p></span></b></p> <p class="MsoNormal" style="margin: 0in -0.25in 0.0001pt -27pt;"><b style=""><span style=";font-size:14;color:blue;" ><a href="http://kc1cs.com/">http://kc1cs.com/</a></span></b><b style=""><span style=";font-size:14;color:black;" ><span style=""> </span>or<span style=""> </span></span></b><b style=""><span style=";font-size:14;color:blue;" ><span style=""> </span><a href="http://www.g4rob.co.uk/easypal.htm">http://www.g4rob.co.uk/easypal.htm</a></span></b><b style=""><span style=";font-size:14;color:black;" ><o:p></o:p></span></b></p> <p class="MsoNormal" style="margin: 0in -0.25in 0.0001pt -27pt;"><b style=""><span style=";font-size:14;color:black;" ><o:p> </o:p></span></b></p> <p class="MsoNormal" style="margin: 0in -0.25in 0.0001pt -27pt;"><b style=""><span style=";font-size:14;color:black;" >If you need help, someone on the DIGSSTV newsgroup can probably help you. Be sure to include the version number in any report of a problem. Also keep up to date and use the latest version.<span style=""> </span></span></b><b style=""><span style=";font-size:14;color:blue;" ><a href="http://groups.yahoo.com/group/digsstv/">http://groups.yahoo.com/group/digsstv/</a></span></b><b style=""><span style=";font-size:14;color:black;" ><o:p></o:p></span></b></p> <p class="MsoNormal" style="margin: 0in -0.25in 0.0001pt -27pt;"><b style=""><span style=";font-size:14;color:black;" ><o:p> </o:p></span></b></p> <p class="MsoNormal" style="margin: 0in -0.25in 0.0001pt -27pt;"><b style=""><span style=";font-size:14;color:black;" >When looking for folks to QSO with, there is our own WA-DIGITAL<o:p></o:p></span></b></p> <p class="MsoNormal" style="margin: 0in -0.25in 0.0001pt -27pt;"><b style=""><span style=";font-size:14;color:black;" ><a href="http://groups.yahoo.com/group/wa-digital/post">http://groups.yahoo.com/group/wa-digital/post</a><o:p></o:p></span></b></p> <p class="MsoNormal" style="margin: 0in -0.25in 0.0001pt -27pt;"><b style=""><span style=";font-size:14;color:black;" ><o:p> </o:p></span></b></p> <p class="MsoNormal" style="margin: 0in -0.25in 0.0001pt -27pt;"><b style=""><span style=";font-size:14;color:black;" >Also try <a href="http://www.obriensweb.com/sked/">http://www.obriensweb.com/sked/</a><span style=""> </span>for skeds a little farther afield.<o:p></o:p></span></b></p> <p class="MsoNormal" style="margin: 0in -0.25in 0.0001pt -27pt;"><b style=""><span style=";font-size:14;color:black;" ><o:p> </o:p></span></b></p> <p class="MsoNormal" style="margin: 0in -0.25in 0.0001pt -27pt;"><a href="http://groups.yahoo.com/group/digsstv"><b style=""><span style="font-size:14;">http://groups.yahoo.com/group/digsstv</span></b></a> is a good resource on frequencies and folks to QSO with.<b style=""><span style=";font-size:14;color:black;" ><o:p></o:p></span></b></p> <p style="margin: 5pt -0.25in 5pt -27pt;">
<br /><span style="font-size:13;">Here are some suggested SSTV frequencies : <o:p></o:p></span></p> <p style="margin: 5pt -0.25in 5pt -27pt;"><span style="font-size:13;">-10 Meters : 28.673 28.677 28.680=calling frequency 28.683 28.686 28.690=K3ASI repeater 28.700=ON4VRB repeater</span>
<br /><span style="font-size:13;">-15 Meters : 21.334 21.337 21.340=calling frequency 21.343 21.346 Avoid SSTV around 21.350 because there is a Phone DX Net running </span>
<br /><span style="font-size:13;">-20 Meters : 14.230=calling frequency 14.233 14.236 14.239 <o:p></o:p></span></p> <p style="margin: 5pt -0.25in 5pt -27pt;"><span style="font-size:13;">Avoid SSTV on 14.227 because there is a Phone DX Net running <o:p></o:p></span></p> <p style="margin: 5pt -0.25in 5pt -27pt;"><span style="font-size:13;">80% of all SSTV traffic is done on those frequencies so please don't transmit SSTV pictures BETWEEN those suggested frequencies, it will QRM a lot .<o:p></o:p></span></p> <p style="margin: 5pt -0.25in 5pt -27pt;"><span style="font-size:13;"><span style=""> </span>3Kc spacing is really a must for not interfering on nearby stations </span></p> <h1 style="margin: 12pt -0.25in 3pt -27pt; text-align: center;" align="center"><o:p> </o:p></h1> <h1 style="margin: 12pt -0.25in 3pt -27pt; text-align: center;" align="center"><o:p> </o:p></h1> <h1 style="margin: 12pt -0.25in 3pt -27pt; text-align: center;" align="center">The Ten Commandments
<br />of Slowscan</h1> <p class="MsoNormal" style="margin: 0in -0.25in 0.0001pt -27pt; text-align: center;" align="center">by <b>Dave Jones - KB4YZ</b></p> <p class="MsoNormal" style="margin-right: -0.25in; margin-left: -27pt; text-indent: -0.25in;"><!--[if !supportLists]--><span style="">1.<span style=";font-family:";font-size:7;" > </span></span><!--[endif]-->Use voice before sending SSTV. </p> <p class="MsoNormal" style="margin-right: -0.25in; margin-left: -27pt; text-indent: -0.25in;"><!--[if !supportLists]--><span style="">2.<span style=";font-family:";font-size:7;" > </span></span><!--[endif]-->Wait for voice and SSTV traffic to finish before sending SSTV. </p> <p class="MsoNormal" style="margin-right: -0.25in; margin-left: -27pt; text-indent: -0.25in;"><!--[if !supportLists]--><span style="">3.<span style=";font-family:";font-size:7;" > </span></span><!--[endif]-->Choose an SSTV mode that is proper for the image to be sent, band conditions, and the receive capability of the receiving stations. </p> <p class="MsoNormal" style="margin-right: -0.25in; margin-left: -27pt; text-indent: -0.25in;"><!--[if !supportLists]--><span style="">4.<span style=";font-family:";font-size:7;" > </span></span><!--[endif]-->Announce the SSTV mode used prior to sending. </p> <p class="MsoNormal" style="margin-right: -0.25in; margin-left: -27pt; text-indent: -0.25in;"><!--[if !supportLists]--><span style="">5.<span style=";font-family:";font-size:7;" > </span></span><!--[endif]-->Transmit on frequency as confirmed by calibration of the VFO with WWV. </p> <p class="MsoNormal" style="margin-right: -0.25in; margin-left: -27pt; text-indent: -0.25in;"><!--[if !supportLists]--><span style="">6.<span style=";font-family:";font-size:7;" > </span></span><!--[endif]-->Send straight pictures as confirmed by calibration of the clock timing with WWV. </p> <p class="MsoNormal" style="margin-right: -0.25in; margin-left: -27pt; text-indent: -0.25in;"><!--[if !supportLists]--><span style="">7.<span style=";font-family:";font-size:7;" > </span></span><!--[endif]-->Send quality pictures with call sign on image. </p> <p class="MsoNormal" style="margin-right: -0.25in; margin-left: -27pt; text-indent: -0.25in;"><!--[if !supportLists]--><span style="">8.<span style=";font-family:";font-size:7;" > </span></span><!--[endif]-->Send full frame. </p> <p class="MsoNormal" style="margin-right: -0.25in; margin-left: -27pt; text-indent: -0.25in;"><!--[if !supportLists]--><span style="">9.<span style=";font-family:";font-size:7;" > </span></span><!--[endif]-->Avoid sending a CW ID unless required by regulations. </p> <p class="MsoNormal" style="margin-right: -0.25in; margin-left: -27pt; text-indent: -0.25in;"><!--[if !supportLists]--><span style="">10.<span style=";font-family:";font-size:7;" > </span></span><!--[endif]-->Describe the picture only after it is confirmed that it was properly received. </p> <p class="MsoNormal" style="margin: 0in -0.25in 0.0001pt -27pt;"><b style=""><span style=";font-size:14;color:black;" ><o:p> </o:p></span></b></p> <p class="MsoNormal" style="margin: 0in -0.25in 0.0001pt -27pt;"><span style=";font-family:Verdana;font-size:10;" >
<br />=============================== Setup
<br />
<br />Setup: Initial Setup - Enter/change Callsign, Soundcard, and CommPort.
<br /> Click the "OK" or "Apply" button to update/exit.
<br />
<br /> The setup for CommPort includes options for
<br /> "FAC Green". Using an external circuit this
<br /> option could be used to mute the speaker while
<br /> receiving the digital signal.
<br />
<br /> It is recommended that you close the program
<br /> and re-start after setting up or making changes
<br /> to the soundcard settings.
<br />
<br />RX Input -
<br /> Allows quick access to Recording Control.
<br /> Select the input where the received audio comes into the soundcard.
<br />
<br />TX Volume -
<br /> Allows quick access to Master Volume for soundcard.
<br /> All inputs should be Muted except for the Master Volume and Wave.
<br />
<br /> RX Input and TX Volume are not shown when running under <st1:place st="on">Vista</st1:place>.
<br />
<br />BSR Mode Automatic (recommended) -
<br /> Will automatically switch the DRM transmit mode required by the Bad Segment Request.
<br />
<br />BSR Mode User Select (advanced)
<br /> Allows the user to force the DRM transmit mode to a mode other than
<br /> that requested by the Bad Segment Request.
<br />
<br />Expanded GUI -
<br /> EasyPal Full runs in a window that is 925x570.
<br /> The user may optionally select the "Expanded GUI" which will
<br /> resize the window to fill out the available space on screen.
<br /> Generally, this will be a 4x3 aspect ratio but the actual
<br /> number of pixels would be determined by the screen resolution.
<br />
<br />W/Fall Color -
<br /> Allows the user to select the color of the waterfall.
<br /> Using "negative" will display black on white line drawings more
<br /> effectively provided that the image is made negative prior to
<br /> being sent. When the received is viewed in the "negative"
<br /> waterfall, it will appear with the proper contrast.
<br />
<br />Very Light Encode -
<br /> Selects the Encode1 level of RS encoding - ".rs1" file extension.
<br /> Transmission time will be increased by 13%.
<br /> At least 89% of the segments transmitted must be received.
<br />
<br />Light Encode -
<br /> Selects the Encode2 level of RS encoding - ".rs2" file extension.
<br /> Transmission time will be increased by 31%.
<br /> At least 76% of the segments transmitted must be received.
<br />
<br />Medium Encode -
<br /> Selects the Encode3 level of RS encoding - ".rs3" file extension.
<br /> Transmission time will be increased by 54%.
<br /> At least 64% of the segments transmitted must be received.
<br />
<br />Heavy Encode -
<br /> Selects the Encode4 level of RS encoding - ".rs4" file extension.
<br /> Transmission time will be increased by 86%.
<br /> At least 51% of the segments transmitted must be received.
<br />
<br /> Encoded files will have interleaved redundancy using Reed-Solomon
<br /> error correction. The encoded file with redundant data is
<br /> sent so that the original file may be created even though not all
<br /> segments were received.
<br />
<br /> There is no progressive receive in this mode. The received file
<br /> will decode after a sufficient number of segments are copied and
<br /> the image will appear as soon as the decoding is finished. This
<br /> may happen even before the transmission is complete. Receiving
<br /> RS encoded files is automatic - no need to select for receive.
<br />
<br /> Use of Encode may reduce the need for BSR's and FIX'es.
<br /> Compatable only with others running EasyPal.
<br /> A stand alone decode program is available that will allow those
<br /> not using EasyPal to decode the .rs files manually. See:
<br /> http://www.tima.com/~djones/rsdecoder.htm
<br />
<br />Default (resolution) -
<br /> Will resize down a large image to fit within 640 x 480 pixels.
<br /> Small images that are PASTED will be resized larger to fit
<br /> within 640 x 480 pixels.
<br />
<br />HiRES (Downsize if > 1280*1024) -
<br /> Will resize down a large image to fit within 1280 x 1024 pixels.
<br /> Small images that are PASTED will be resized larger to fit
<br /> within 1280 x 1024 pixels.
<br />
<br />HiRES (Best)
<br /> Will not resize image.
<br /> This is the best setting to use when an external program such as
<br /> "sstvPics" is used to resize the image prior to pasting into
<br /> EasyPal.
<br />
<br /> The HiRES setting will not affect the image when "LoadAny" is used.
<br />
<br />Show RX Screen -
<br /> Selects the RX tab to view the RX Screen and RX information line.
<br /> Gamma -
<br /> Allows for the adjustment of the brightness of the received image.
<br /> RX Filename -
<br /> The filename of the received image. Note this when selecting
<br /> the proper file to select for the "Send Selected Request" BSR.
<br />
<br /> Click on image to display full screen.
<br /> Animated GIF files will not be displayed full screen.
<br />
<br /><st1:place st="on"><st1:city st="on">Show</st1:city> <st1:state st="on">TX</st1:state></st1:place> Screen -
<br /> Selects the TX tab to view the TX Screen and TX information line.
<br /> Secs -
<br /> This is the number of seconds it would take to transmit this image.
<br /> K -
<br /> This is the file size for the image to transmit. Does not apply
<br /> to images loaded using LoadAny.
<br /> Slider -
<br /> The setting of this slider changes the level of the JPEG-2000
<br /> compression that determines the file size.
<br /> SET -
<br /> If the slider has changed position after the image has been loaded,
<br /> it will be necessary to click the SET button so that the JPEG-2000
<br /> compression can be reapplied.
<br /> TX Filename -
<br /> The name of the file to be transmitted. The filename will change
<br /> when the transmission starts.
<br />
<br />TX mode = RX mode -
<br /> This provides a way to quickly change the TX mode to match the
<br /> DRM mode just received.
<br />
<br />Define Additional Save Directory -
<br /> Received files will be saved into a user selected folder in addition
<br /> to being saved in the "Autosave" folder.
<br /> (Not working)
<br />
<br />=============================== Action
<br />
<br />Action:
<br />
<br />Send Text -
<br /> Turns the TX window into a text editor for the sending of text.
<br /> Text may be typed, pasted, and edited prior to transmitting.
<br />
<br />Session Log -
<br /> Logs the calls and time for current session only.
<br />
<br />QuickTxMode -
<br /> This screen serves as a quick reminder for what DRM modes are
<br /> suitable for different conditions.
<br />
<br />USE Repeater -
<br /> Show Repeater Commands - Check to enable "Repeater" menu.<o:p></o:p></span></p> <p class="MsoNormal" style="margin: 0in -0.25in 0.0001pt -27pt;"><span style=";font-family:Verdana;font-size:10;" ><o:p> </o:p></span></p> <p class="MsoNormal" style="margin: 0in -0.25in 0.0001pt -27pt;"><o:p> </o:p></p> <p class="MsoNormal" style="margin: 0in -0.25in 0.0001pt -27pt;"><span style=";font-family:Verdana;font-size:10;" >
<br />
<br />============================== LoadPic
<br />
<br />LoadPic:
<br /> Brings up Window for selecting an image file to load, resize,
<br /> and convert into JPEG-2000 (JP2) format. When transmitted,
<br /> the filename is changed to "############-originalfilename.JP2".
<br /> The "############" is a 12 digit number representing the
<br /> current year/month/day/hour/minute/seconds.
<br />
<br />=============================== LoadAny
<br />
<br />LoadAny:
<br /> Allows for the loading of most any file type to be transmitted.
<br /> The file will be renamed but will keep the original extension.
<br /> This is useful when sending animated GIF files where
<br /> conversion to JPEG-2000 is not desired.
<br />
<br />=============================== Copy
<br />
<br />Copy:
<br /> Standard image copy to clipboard from the RX or TX screen.
<br />
<br />=============================== Paste
<br />
<br />Paste:
<br /> Standard image paste from clipboard to the RX or TX screen.
<br /> Paste to the TX screen will compress and convert the image
<br /> to JPEG-2000 format. The image may be resized based on the
<br /> setting for HiRES.
<br />
<br />=============================== FIX
<br />
<br />FIX:
<br /> Brings up Last FIX Request. Use when the receiving station
<br /> requires the same FIX sent again.
<br />
<br /> After receiving a BSR, you will have a message on the title bar:
<br />
<br /> it may be a message like this:
<br /> "-W9VMT-Requests-63/92 segments for-070707122834-cat1.jp2"
<br /> Just click "FIX NOW" to send the FIX.
<br />
<br /> or it may be a message like this:
<br /> "You can repair 63/92 segments in 070707122834-cat1.jp2 for W9VMT"
<br /> Just click "FIX NOW" to send the FIX.
<br />
<br /> or it may be a message like this:
<br /> "This BSR is not for you"
<br /> You do not have this file.
<br /> This BSR request is for another station.
<br /> In this case, you will have to get the file repaired
<br /> before you will be able to send any fixes.
<br />
<br /> or it may be a message like this:
<br /> 'You do not have this file for "K9NP ERIC" to Repair'
<br /> You do not have this file.
<br /> This BSR request is for another station.
<br /> In this case, you will have to get the file repaired
<br /> before you will be able to send any fixes.
<br />
<br /> If there is no message in the title bar and you think that
<br /> you received the BSR request OK, and you should be able to
<br /> send the FIX, go ahead and send the FIX anyway. It may work!
<br />
<br /> The FIX sends "FIX" in the waterfall before the data.
<br />
<br /> Any station running EasyPal that successfully receives an image,
<br /> can send the fix for any other station that sends an BSR for that
<br /> same image from EasyPal. (The original image may be sent from any
<br /> program using a compatable DRM mode.) If the original image was
<br /> transmitted with a filename that had spaces within the filename,
<br /> it may require the original sender to do the FIX.
<br />
<br /> There is no need to reload an image to fix someone.
<br />
<br /> The "Last FIX Request" includes the Call from the station that
<br /> sent the BSR, mode, segments, and filename. If the mode details
<br /> are in any way different from the mode the file was sent, then the
<br /> FIX will not work. Ask for an "Old Type" BSR instead.
<br />
<br />=============================== WAV
<br />
<br />WAV:
<br /> Brings up the "Play Wave File" list. Selecting a WAV file
<br /> and clicking "TX Now" will immediatelly play the audio from this
<br /> WAV file. Create the wav files using "WFPic",
<br /> "WFTxt" or an external program such as HamPAL or DIGTRX.
<br />
<br /> These special wave files must be in the main EasyPal folder:
<br /> BEACON.wav - repeater sends at preset intervals when "Beacon" is checked.
<br /> BEGIN.wav - sent before each DRM file transmission.
<br /> BSR.wav - sent before each user initiated BSR transmission.
<br /> DELETED.wav - repeater sends this when selected file is deleted.
<br /> DIR.wav - repeater sends before the RS Encoded file (repeaterdir.txt.rs2)
<br /> in responce to "View Repeater Directory".
<br /> FILEFAIL.wav - repeater sends before the BSR.
<br /> FILEOK.wav - repeater sends when it successfully receives a file.
<br /> FIX.wav - sent before each FIX transmission.
<br /> NOTDEL.wav - repeater sends this when selected file is not allowed to be deleted.
<br /> NOTEXIST.wav - repeater sends this when selected file is not available for deletion.
<br /> PAUSED.wav - repeater sends in responce to "Shutdown ALL/Specific Repeater".
<br /> REPFIX.wav - repeater sends before the FIX transmission.
<br /> REPLAY.wav - sent before repeater sends out the last received file.
<br /> REPLY.wav - repeater sends in responce to "Interrogate Repeater".
<br /> RESTART.wav - repeater sends in responce to "Restart ALL Repeaters".
<br /> SELECTED.wav - repeater sends in responce to "Send Back Specified File".
<br /> TIMEOUT.wav - repeater sends this when selected file is too large to send.
<br /> TOOBIG.wav - repeater sends this when selected file is too large to send.
<br /> WEBCAM.wav - repeater sends before the current webcam picture.
<br />
<br />=============================== WFPic
<br />
<br />WFPic: (Waterfall picture)
<br /> Transforms the image on screen into a grey scale image that
<br /> becomes analog encoded audio to produce a like image in the
<br /> waterfall.
<br />
<br />=============================== WFTxt
<br />
<br />WFTxt: (Waterfall text)
<br /> Transforms a user provided text message with the choice of
<br /> various sizes and fonts into analog encoded audio to produce
<br /> the text as an image in the waterfall.
<br />
<br /> To make a waterfall ID click "WFTxt". Type your call into the
<br /> Waterfall Text window using all caps. You may want to add a space
<br /> between each character. Select a plain bold font to make it
<br /> easier to read when displayed in the waterfall. Click Save and
<br /> use your call as the filename. To send this, click WAV and
<br /> select the file, then click "Tx Now".
<br />
<br />=============================== Clear
<br />
<br />Clear:
<br /> Clears the selected (RX/TX) screen.
<br />
<br />
<br />=============================== Info Area
<br />
<br />Callsign -
<br /> The callsign of a transmitting station will appear in the upper
<br /> left corner while receiving an DRM transmission.
<br />
<br />RX audio level bar graph.
<br /> (Higher incoming audio produces more green.)
<br />
<br />% -
<br /> RX signal quality level bar graph - equivalent to
<br /> SNR (Signal to Noise Ratio). There will be more green area with
<br /> increased signal quality.
<br />
<br />TX -
<br /> DRM submode selected for transmit.
<br /> Right click mode parameter to toggle through settings.
<br /> Any changes to the mode are saved for future sessions
<br /> when the program is closed.
<br />
<br /> Default DRM Mode should be Mode B, Width
<br /> 2.5 khz, Error HI, QAM 16, and LeadIn 24.
<br /> Interleave is always Long and cannot be changed.
<br /> These settings are the best choices for general use
<br /> on the HF bands.
<br />
<br /> LeadIn 12 will reduce transmit time by reducing
<br /> the number of redundant segments. For very short
<br /> transmissions such as Text messages, LeadIn 12
<br /> may be too short a time for all stations to
<br /> achieve MSC sync before the transmission is
<br /> finished. In this case, select LeadIn 24.
<br />
<br />RX -
<br /> DRM submode received.
<br /> FAC must be green before the mode can be detected and the
<br /> callsign decoded. In addition to those mode settings that
<br /> may be changed on transmit, the RX will also reveal the
<br /> interleave setting. Lng for long and Sht for short. The
<br /> receive mode settings are automatic and do not require the
<br /> operator to make any changes for receiving any DRM mode.
<br />
<br />RX mode display: (red/green bars)
<br /> MSC - Green light indicates MSC (Main Service Channel) lock.
<br /> FAC - Green light indicates FAC (Fast Access Channel) lock.
<br /> Frame - Green light indicates Frame Sync.
<br /> Time - Green light indicates Time Sync.
<br /> IO - Green light indicates Soundcard is active.
<br />
<br /> Data cannot be decoded until the MSC has a lock. So the MSC
<br /> must be green before you will be able to copy anything.
<br />
<br />Total -
<br /> "Total" is the number of segments in the image file being received.
<br />
<br />OK Segs -
<br /> "OK Segs" is the number of segments successfully decoded so far.
<br />
<br />Position -
<br /> "Position" is the segment number that was last decoded.
<br />
<br />not processed -
<br /> This is the number of segments that still need to be received.
<br />
<br />Transmit progress bar indicates the % transmitted.
<br />(Visable only during transmit).
<br />
<br />=============================== Buttons
<br />
<br />TRANSMIT -
<br /> Starts the transmission of the file.
<br />
<br />Tune -
<br /> Immediatelly sends the three tone tuning tone for 7 seconds.
<br /> Green markers in waterfall should match the "Tune" signal
<br /> or pilot carriers.
<br />
<br />Replay RX -
<br /> Replays last received image file. It may be renamed but it
<br /> will have the exact same content.
<br />
<br />ABORT -
<br /> Allows for stopping a picture, WAV, BSR, or FIX transmission.
<br />
<br />Encode -
<br /> Left click to toggle RS encoding for transmitted files.
<br /> Right click to toggle through the four levels of encoding.
<br />
<br />ProgRX - Progressive RX
<br /> Check to enable viewing image as it is coming in.
<br /> Using Progressive RX may slow other processes
<br /> such as the waterfall display.
<br />
<br />BSR Requests -
<br /> Brings up the BSR Requests window.
<br /> For those transmissions that have a partial file stored,
<br /> there will be a file name listed. The sender's call is
<br /> listed first. Click a file name from the list to display
<br /> a partial image (if available) and other information.
<br /> There may be more than one file for the same image.
<br /> If this is the case, you should select the one that has
<br /> the fewest number of missing segments. Selecting the
<br /> file first is only necessary when using the
<br /> "Send Selected Request".
<br />
<br />"Send Selected Request" -
<br /> CAUTION - TRANSMITTING THIS TYPE OF BSR MAY LOCKUP
<br /> NON-COMPATABLE SYSTEMS. (DIGTRX and HamPal)
<br /> This type of BSR is available even after EasyPal has been
<br /> closed and restarted. Use when you require a third party
<br /> FIX from another station running EasyPal. You must select
<br /> the file from the list to be fixed before clicking the
<br /> "Send Selected Request" button.
<br />
<br />"Old Type BSR (compatable all)"
<br /> Use this type BSR when requesting segments from non-compatable
<br /> systems. Only the original sender or one that replayed the
<br /> file will be able to fix you with this type of BSR.
<br />
<br />"Old Type Fast BSR (not compatable)"
<br /> This is the normal type of BSR to use when requesting segments
<br /> from the original sender that is also running EasyPal.
<br /> This type of BSR is a bit different from the BSR format used
<br /> in the past. It is called a "Fast BSR" because it uses a form of
<br /> shorthand to indicate contiguous segments. This new "Fast BSR"
<br /> will send faster because the text file listing the missing
<br /> segments is smaller. One drawback to the use of the new
<br /> "Fast BSR" is that older programs such as HamPal may not
<br /> recognize all the segments required and if there are many,
<br /> HamPal may only be able to send fixes for two or three
<br /> segments at a time. This is only a problem when pictures are
<br /> sent from HamPal to EasyPal.
<br />
<br /> "Old Type" BSR's do NOT require that you select the filename.
<br />
<br /> "Old Type" BSR may not be available. You will get the message,
<br /> "nothing to fix". This is most likely the case where you have
<br /> received a BSR from another station but not copied any of the FIX.
<br /> In this case, have the original station send part of the file
<br /> and abort. The "Old Type" BSR should now be available.
<br />
<br />"Bad Segment Report"
<br /> Each type of BSR starts the transmission of a short text file
<br /> that lists the segment numbers that were missing on the last
<br /> received file (or selected file).
<br /> During this transmission, many instances will be sent to ensure
<br /> that the information gets through. When many segments are
<br /> required, the transmission time for the BSR may be much longer.<o:p></o:p></span></p> <p class="MsoNormal" style="margin: 0in -0.25in 0.0001pt -27pt; text-indent: 27pt;"><span style=";font-family:Verdana;font-size:10;" >You may be better off to simply resend the original file – possibly with <o:p></o:p></span></p> <p class="MsoNormal" style="margin: 0in -0.25in 0.0001pt -27pt; text-indent: 27pt;"><span style=";font-family:Verdana;font-size:10;" >a higher Reed-Solomon error correction setting.
<br />
<br />=============================== TABS
<br />
<br />RX tab -
<br /> Click to view RX screen and RX information line.
<br />
<br />TX tab -
<br /> Click to view TX screen and TX information line.
<br />
<br />View tab -
<br /> Click to view thumbnails of Last RX Pictures.
<br /> Click to view thumbnails of Last TX Pictures.
<br />
<br />Send to TX -
<br /> This allows for a replay of the thumbnail image.
<br /> Transfers selected thumbnail to TX window. JPEG-2000
<br /> compression is applied and filename is changed when
<br /> transmitted. Quality is reduced each time this type
<br /> of replay is used.
<br />
<br />Full Screen -
<br /> Displays selected thumbnail to full screen.
<br /> Image displayed will always be the original size.
<br /> The image is displayed against a black background.
<br /> Animated GIF files might not be displayed.
<br /> To return to the program screen, click the mouse
<br /> or hit the "Esc" key.
<br />
<br />Delete to Recycle Bin -
<br /> Selected thumbnail will be deleted.
<br /> Since not all selected thumbnails will actually be
<br /> deleted, it may be necessary to open the "RxFiles"
<br /> or the "TxFiles" folder to manually delete these
<br /> files. Selecting the very last thumbnail to
<br /> delete for the second time may actually delete the
<br /> first.
<br />
<br />Send to Repeater Directory - ("USE Repeater" checked)
<br /> Transfers selected thumbnail to "Repeater" folder.
<br /> Additional JPEG-2000 compression is applied based on
<br /> setting of slider on the TX window. If "Encode" is
<br /> checked, then this level of RS Encoding will be
<br /> applied and the filename extension will be changed
<br /> to the one for that level of RS Encoding. Quality
<br /> may be reduced for this type of conversion.
<br />
<br /> Thumbnails are standard JPEG (.jpg) images that are
<br /> re-compressed copies of the files received and sent.
<br /> Image files in the "LastRX" folder may not have the
<br /> quality and characteristics as the original files sent.
<br />
<br /> The original files received are stored in the
<br /> "Autosave" folder. These files should be identical to
<br /> the quality and characteristics of the original files sent.
<br />
<br />=============================== NOTES
<br />
<br />The waterfall may be paused - just left click to pause/restart.
<br />
<br />When EasyPal is closed, the contents of the "Transient" folder is deleted.
<br />Temp files in other folders are also deleted.
<br />
<br />Partially received files (ones with missing segments) will be saved
<br />into the "Corrupt" folder. They are stored here until they are repaired
<br />or manually deleted by the user.
<br />
<br />Hints will appear after mouse pointer is placed over selected buttons
<br />and areas.</span></p> <p class="MsoNormal" style="margin: 0in -0.25in 0.0001pt -27pt;"><o:p> </o:p></p> <p class="MsoNormal" style="margin: 0in -0.25in 0.0001pt -27pt;"><o:p> </o:p></p> WR5Jhttp://www.blogger.com/profile/16316513702643319581noreply@blogger.com0tag:blogger.com,1999:blog-4632435085083780021.post-87097124313543766502009-07-09T22:55:00.000-07:002009-07-09T23:15:18.441-07:00<a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgE08CF27T6CPa2jIOdcZk-pUDwL1zwuMwlQnIDUQIEvRR4T00IDAPl7r-lUUY72bstigdsv1U_eTb3ds7ZN8IiJzvpiOmNsLpqK-E0SjCQRaB7aPtcI4sU4QrzclkTgvAfeeFEblDzxdU/s1600-h/Picture20.jpg"><img style="margin: 0px auto 10px; display: block; text-align: center; cursor: pointer; width: 400px; height: 312px;" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgE08CF27T6CPa2jIOdcZk-pUDwL1zwuMwlQnIDUQIEvRR4T00IDAPl7r-lUUY72bstigdsv1U_eTb3ds7ZN8IiJzvpiOmNsLpqK-E0SjCQRaB7aPtcI4sU4QrzclkTgvAfeeFEblDzxdU/s400/Picture20.jpg" alt="" id="BLOGGER_PHOTO_ID_5356707247519525922" border="0" /></a><br /><div style="text-align: center;"><span style="font-size:130%;"><span style="font-weight: bold;">Blog Post 6 – MMSSTV—Slow Scan Television software by Makoto Mori, JA3HHT – Introduction to analog image transmission</span></span><br /></div><br />Wednesday July 15, 2009<br /><br />This is Curt Black, WR5J with the Educational Radio Net – No digital QST tonight so we can get everyone set up and running with MMSSTV.<br /><br />Slow Scan TV (SSTV) is a way to get the high-information density of visual images shoe-horned into the audio-bandwidth typically used by the human voice of about 2.5kHz. Bandwidth for full motion NTSC video requires about 4.5Mhz or 9.0 if you use both sidebands as you transmit– so minimally a bandwidth ratio of about 2000/1.<br />.<br /><br />On slow-scan TV we do this by sending just a single image and spreading that single image out in time. It typically takes from 8 seconds (Robot Grey-scale 160x120) to 269 seconds (ScottieDX RGB 320x256) to transmit an image. And you probably noticed that those images are way smaller than the 525 lines of an NTSC video. It seems like a lot of fuss, but images are powerful things, capable of communicating easily more than the typically cited, “1000 words” of meaning. Like the one at the top of this blog post of the Seattle Library from a recent Simulated Earthquake response for Seattle ACS.<br />.<br /><br />Just like the RS-ID being implemented by our digital modes, SSTV uses a standard burst at the beginning of the transmission called VID to allow the software to decode using the correct format. The details of that signal are appended to the end of the Yahoo Group MMSSTV Setup and Use compilation.<br />.<br />Just like an NTSC TV picture, the SSTV signal is built line by line and point by point. In contrast to the digital pictures we will do next week with EASYPAL, the information is built by capturing the audio information and correlating a particular brightness with a particular audio frequency.<br />To start each line, a sync pulse is sent at 1200 Hz. There is one of these per line, so you should be able to see a peak at 1200 Hz in the energy in the spectrum display. The brightness information is sent between 1500 and 2300Hz. As the picture is being transmitted, you will see clearly this band of frequencies being received. <br />.<br />To tune in the station on HF-USB, just adjust your main tuning dial to place the sync pulse at 1200. MMSSTV and all the other programs provide markers at 1200, 1500 and 2300Hz. to make this easy.<br />.<br /><br />To use this software, just go to the SSTV watering holes such as 14.230 or 14.233. This is the best know and possibly the best defended frequency in all of amateur radio. I enjoy listening during contests as someone innocently goes in to call CQ.<br />.<br /><br />One weakness with this software is its identification of different sound cards. The more you have the harder it is to find it because there are only numbers – no names. You just have to try one number after the other until you are receiving.<br />.<br /><br />For the receive side of this software, you would typically leave the AUTO box checked, but if you don’t start to receive the signal automatically, you can try SCOTTIE 1 or 2 – the most often used modes in North America. If you are receiving DX from Europe or Japan, try MARTIN 1 or 2. Most operators give a voice ID at the beginning of their transmission where they announce the mode being used, although that can be lost in the noise if the stations aren’t strong. You can definitely decode and see adequately signals from stations too weak to allow copy of a voice signal.<br />.<br /><br />To learn more about this mode or ask questions about the software, check out the Yahoo Group http://groups.yahoo.com/group/MM-SSTV/<br />.<br /><br />To check out activity on the bands or see what has been transmitted recently, check out http://www.g0hwc.com/ G0HWC has sites for Analog and Digital SSTV and links to the software as well as helpful discussion.<br />.<br /><br /><span style="font-size:180%;"><br /></span><div style="text-align: center;"><span style="font-size:180%;"><span style="font-weight: bold;">Onward to getting the software setup:</span></span><br />OK, This part isn't working since I can't get the images in the right place - please go to the http://groups.yahoo.com/group/wa-digital/files/<br />area and snag the Blog Post #6 and see what this was supposed to look like... vy sri.<br />.<br /></div>1. Download MMSSTV from http://mmhamsoft.amateur-radio.ca/mmsstv/<br />.<br /><br />2. Install MMSSTV, and work through these instructions. Add your callsign when prompted.<br />.<br /><br />3. Shut down all other programs you might have running, then start MMSSTV and select the OPTIONS pull down from the top tool bar.<br />.<br /><br />4. Select SETUP MMSSTV(0) from the pull down<br />.<br /><br />5. This will bring up a three tabbed window, select the RX Tab.<br />.<br /><br />6. Set up the RX Page as follows, (DO NOT CHANGE THE LEVEL CONVERTER INFO):<br />.<br /><br />7. Set up the TX Page as follows, (DO NOT CHANGE THE TxBPF/TxLPF, TUNE BUTTON INFO, or PORT value):<br />.<br /><br />8. Set up the MISC page as follows, (DO NOT CHANGE THE FIFO, or DEVICE ID):<br /><br />9. Note above: DO NOT change anything in the CLOCK window yet.<br />10. Once you have these items set up calibrate the software to your clock setting by the following procedure:<br />========<br />Clock calibration<br />========<br /><br />In SSTV, errors in the timing of the clock appear as a slanted image. For MMSSTV, you are not required to have the absolute and exact clock frequency value (e.g. 11025Hz). But it is important to get MMSSTV informed of the discrepancy of your soundcard to a standard.<br />.<br /><br />In normal situations, you would only have to adjust the slant by using the Sync window. If you want to calibrate your soundcard very accurately, listen to a standard radio such as WWV, CHU or JJY.<br />.<br /><br />1) Go Option, Setup, Misc page, and push Adj button.<br />2) Receive standard radio signal (e.g., WWV and JJY).<br />3) Tune into the tick sound.<br />4) Continue listening to the sound for a while. You have a vertical line.<br />5) Click the upper point of the line.<br />6) Click the lower point of the line.<br />(these instructions actually show up in the calibration window)<br />.<br /><br />An alternate method is to locate a station that believes they are calibrated correctly. They become the "Standard" for you and all who come after you. Clearly the problem with this is it can become a “blind leading the blind” situation with errors propagating through the community. Cleary if you are willing to do the calibration above you will have done your part to make the world a better place.<br />.<br /><br />11. However, for the non-WWV technique, have the “standard” station send a picture to you. After that picture is complete move to step 12.<br />.<br /><br />12. Select the "SYNC" tab, (you can do this while the picture is being received), then select the NICONICO (Happyface), button ONLY after the picture is complete. A number will appear in a small white box in the upper part of the screen. This is your error from the selected "Master" station.<br />.<br /><br />13. You may press the "MEM" button. This will lock your computer to the "Master" stations clock frequency. Your receive is now setup.<br />.<br /><br /><div style="text-align: center;"><span style="font-size:180%;"><span style="font-weight: bold;">Operation:</span></span><br /></div><br />First you need to get some images to work with. Luckily nothing could be simpler. In MMSSTV, click on the RX tab toward the top of the screen and the S.pic tab at one third up from the bottom. There is room for some 300 photos in this Stock Pictures area.<br />.<br /><br />Open a Windows Explorer/File Manager window and open the folder where you have some images. Select an image and drag it onto the icon on the taskbar for MMSSTV until MMSSTV opens, then continue dragging to one of the open frames along the bottom of the screen. Drag in as many as you find interesting and which you might want to share. Colorful, active photos are best, but standard images of rigs and operators are fine, too.<br />.<br /><br />Set up your Com Port – check your Port assignments by getting to where you can see MY Computer – right click and select Properties –on the window that opens, click the Device Manager tab in the middle of the window. From the list that appears, click on the Ports (COM and LPT) icon and look through the resulting list of ports for the one assigned to your radio PTT. It is certainly possible to brute force try one after another if you can’t get it another way.<br /><br />.<br />That could be it – click the TUNE button and adjust the transmitter for 50% or less of your full power rating for the radio you are using (SSTV is 100% duty cycle – pretty much key down for 90 seconds or more - far more than your voice requires of the equipment – don’t toast your radio.<br />.<br /><br />For more details of the mode, check out the SSTV- MMSSTV-How-To-Set-Up-Doc on the Yahoo Group site for WA-DIGITAL. It starts out with duplicate info as this blog, but then goes into more specifics on the mode and operating.<br /><br />Next week we will contrast tonight’s work with MMSSTV and analog image transfer with EASYPAL – digital image (and much more) transmission. EasyPal is an amazing program. The software is on the WA-DIGITAL site as will be a setup document really soon. Please download it and install it before next week’s session.<br /><br />See you on the waterfall – or right on my screen!<br /><br />VY 73 DE WR5J<br /><br />Curt BlackWR5Jhttp://www.blogger.com/profile/16316513702643319581noreply@blogger.com0tag:blogger.com,1999:blog-4632435085083780021.post-48664726831307650202009-07-09T18:48:00.000-07:002009-07-09T19:48:41.997-07:00Blog Post 5 – FLDIGI Wrap-up Review and the The Amazing World of Weak Signal Modes – WSPR – Weak Signal Propagation Reporter<a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjHs-wYY74cq_yTv-sJ_VxH3LimFdw4gJI3N2wN4s8avNgPCzV4mynOjMcuYE2Rwlopvuga5f3Oi-TPIaKmRfCr8wV2sE_2kOAfRVM8hHdFo2yRUmm2S9wej9fZZosx_GHhWSgk0x-d53Q/s1600-h/5-7.jpg"><img style="cursor: pointer; width: 320px; height: 236px;" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjHs-wYY74cq_yTv-sJ_VxH3LimFdw4gJI3N2wN4s8avNgPCzV4mynOjMcuYE2Rwlopvuga5f3Oi-TPIaKmRfCr8wV2sE_2kOAfRVM8hHdFo2yRUmm2S9wej9fZZosx_GHhWSgk0x-d53Q/s320/5-7.jpg" alt="" id="BLOGGER_PHOTO_ID_5356655279858905490" border="0" /></a>
<br /><a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEht36Wii1_zY2Pcun054XbIVvLSBJYAvXcMQc4CwtGJvPfn_o6F60OBrBC3NhW8cOxFYlObrytUf55fZsmqkDCorRiGyOp6oty7Dr1ouDgDRaxWwpsuWHB25Or_IalA1llIS5BF2fTHKgI/s1600-h/5-7.jpg"><img style="cursor: pointer; width: 320px; height: 236px;" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEht36Wii1_zY2Pcun054XbIVvLSBJYAvXcMQc4CwtGJvPfn_o6F60OBrBC3NhW8cOxFYlObrytUf55fZsmqkDCorRiGyOp6oty7Dr1ouDgDRaxWwpsuWHB25Or_IalA1llIS5BF2fTHKgI/s320/5-7.jpg" alt="" id="BLOGGER_PHOTO_ID_5356655031429610162" border="0" /></a>
<br /><a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhFpRWLeniuojGdHWp1JZnfe65LYM140pM-T6Nua3m1Bz7JUmWwo0lzYe20WPfiNbTU9w4kswzE9AgqNFAA47udionykgq8wLNcXaeD0EAs5v1wuxhMkPi8buHqfMlgR0TbrPO_q5DwZLQ/s1600-h/5-6.jpg"><img style="cursor: pointer; width: 320px; height: 235px;" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhFpRWLeniuojGdHWp1JZnfe65LYM140pM-T6Nua3m1Bz7JUmWwo0lzYe20WPfiNbTU9w4kswzE9AgqNFAA47udionykgq8wLNcXaeD0EAs5v1wuxhMkPi8buHqfMlgR0TbrPO_q5DwZLQ/s320/5-6.jpg" alt="" id="BLOGGER_PHOTO_ID_5356654917673688338" border="0" /></a>
<br /><a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgOGPV1iig0ZejFuem3KtHMowFPSivfbb8iRqdkXupJKMoyeMHZS9pD3Vz3mEgoDx_euYekOwzBvfyqcuB15uLiY12X0N5LWIg0Gr6ZB53f-g_E_26lBezhjajOPfp3pajzL-POH_HwiUY/s1600-h/5-5.jpg"><img style="cursor: pointer; width: 320px; height: 237px;" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgOGPV1iig0ZejFuem3KtHMowFPSivfbb8iRqdkXupJKMoyeMHZS9pD3Vz3mEgoDx_euYekOwzBvfyqcuB15uLiY12X0N5LWIg0Gr6ZB53f-g_E_26lBezhjajOPfp3pajzL-POH_HwiUY/s320/5-5.jpg" alt="" id="BLOGGER_PHOTO_ID_5356654824804056866" border="0" /></a>
<br /><a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgx4S5smwtyxglu2iIuTYoJfc3yMTrkHoXTdADunM7uy2Gpa2-jmqJCzS3m3MD_Fk1Z596vp7karMKkaQcUBR3t9n4j25ZrIpQwLdoLHParN7qNubyRjYc45bL5V4V8gV02HvZRvD0ufXE/s1600-h/5-4.jpg"><img style="cursor: pointer; width: 320px; height: 236px;" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgx4S5smwtyxglu2iIuTYoJfc3yMTrkHoXTdADunM7uy2Gpa2-jmqJCzS3m3MD_Fk1Z596vp7karMKkaQcUBR3t9n4j25ZrIpQwLdoLHParN7qNubyRjYc45bL5V4V8gV02HvZRvD0ufXE/s320/5-4.jpg" alt="" id="BLOGGER_PHOTO_ID_5356654730580764578" border="0" /></a>
<br /><a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiF2XSjH99dARbo0h7SY6TIeCya-fR5rI2Ej9g4HJMlvMD7Pcvh3V1g9fdxXHL189F0s1EV72gJeGA0Z8AXHljBS2e1VLskxxNQV7w6v5zPiZKPbTilKVUSbGPpOms8Zeu8dIoUl3fmE28/s1600-h/5-3.jpg"><img style="cursor: pointer; width: 320px; height: 254px;" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiF2XSjH99dARbo0h7SY6TIeCya-fR5rI2Ej9g4HJMlvMD7Pcvh3V1g9fdxXHL189F0s1EV72gJeGA0Z8AXHljBS2e1VLskxxNQV7w6v5zPiZKPbTilKVUSbGPpOms8Zeu8dIoUl3fmE28/s320/5-3.jpg" alt="" id="BLOGGER_PHOTO_ID_5356654631877379410" border="0" /></a>
<br /><a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEigXLwTYmlRDyIXbhBr5lgwH6CdpWqCPYtdWVW_iilu3UHICX97feRzexCnIKjpqS7Y9v7EdLPiS0xqLy3cXo56riT6Vg93_iO-0KL2v1LHlEtl6P4IU3hFy6RFxeeRYHt-eTwGodAHMxY/s1600-h/5-2.jpg"><img style="cursor: pointer; width: 320px; height: 157px;" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEigXLwTYmlRDyIXbhBr5lgwH6CdpWqCPYtdWVW_iilu3UHICX97feRzexCnIKjpqS7Y9v7EdLPiS0xqLy3cXo56riT6Vg93_iO-0KL2v1LHlEtl6P4IU3hFy6RFxeeRYHt-eTwGodAHMxY/s320/5-2.jpg" alt="" id="BLOGGER_PHOTO_ID_5356654477093947730" border="0" /></a>
<br /><a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgoV8Ex6bwrGWWtiBFvbL1ggpZQtqWduXrG85cLxBvQ60jrm4FB5lKBbX0NdzT3wMHooJA8bY404JWbXe4MHN7zWVcaHqz-tEHpMA17PW3uZ7kAcAIgwh1rrqwSxPV0GMsFgoZXDCEzS40/s1600-h/5-1.jpg"><img style="cursor: pointer; width: 195px; height: 215px;" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgoV8Ex6bwrGWWtiBFvbL1ggpZQtqWduXrG85cLxBvQ60jrm4FB5lKBbX0NdzT3wMHooJA8bY404JWbXe4MHN7zWVcaHqz-tEHpMA17PW3uZ7kAcAIgwh1rrqwSxPV0GMsFgoZXDCEzS40/s320/5-1.jpg" alt="" id="BLOGGER_PHOTO_ID_5356654325772579378" border="0" /></a>
<br /><meta equiv="Content-Type" content="text/html; charset=utf-8"><meta name="ProgId" content="Word.Document"><meta name="Generator" content="Microsoft Word 9"><meta name="Originator" content="Microsoft Word 9"><link rel="File-List" href="file:///C:/DOCUME%7E1/ADMINI%7E1/LOCALS%7E1/Temp/msoclip1/01/clip_filelist.xml"><link rel="Edit-Time-Data" href="file:///C:/DOCUME%7E1/ADMINI%7E1/LOCALS%7E1/Temp/msoclip1/01/clip_editdata.mso"><!--[if !mso]> <style> v\:* {behavior:url(#default#VML);} o\:* {behavior:url(#default#VML);} w\:* {behavior:url(#default#VML);} .shape {behavior:url(#default#VML);} </style> <![endif]--><!--[if gte mso 9]><xml> <w:worddocument> <w:view>Normal</w:View> <w:zoom>0</w:Zoom> <w:donotoptimizeforbrowser/> </w:WordDocument> </xml><![endif]--><style> <!-- /* Font Definitions */ @font-face {font-family:"\;font-size\:10\;"; panose-1:0 0 0 0 0 0 0 0 0 0; mso-font-alt:"Times New Roman"; mso-font-charset:0; mso-generic-font-family:roman; mso-font-format:other; mso-font-pitch:auto; mso-font-signature:0 0 0 0 0 0;} /* Style Definitions */ p.MsoNormal, li.MsoNormal, div.MsoNormal {mso-style-parent:""; margin:0in; margin-bottom:.0001pt; mso-pagination:widow-orphan; font-size:12.0pt; font-family:"Times New Roman"; mso-fareast-font-family:"Times New Roman";} h3 {margin-right:0in; mso-margin-top-alt:auto; mso-margin-bottom-alt:auto; margin-left:0in; mso-pagination:widow-orphan; mso-outline-level:3; font-size:13.5pt; font-family:"Times New Roman";} p.MsoBodyText, li.MsoBodyText, div.MsoBodyText {margin-top:0in; margin-right:-27.0pt; margin-bottom:0in; margin-left:0in; margin-bottom:.0001pt; mso-pagination:widow-orphan; font-size:12.0pt; font-family:"Times New Roman"; mso-fareast-font-family:"Times New Roman"; font-weight:bold;} a:link, span.MsoHyperlink {color:blue; text-decoration:underline; text-underline:single;} a:visited, span.MsoHyperlinkFollowed {color:purple; text-decoration:underline; text-underline:single;} pre {margin:0in; margin-bottom:.0001pt; mso-pagination:widow-orphan; font-size:10.0pt; font-family:"Courier New"; mso-fareast-font-family:"Times New Roman";} @page Section1 {size:8.5in 11.0in; margin:1.0in 1.25in 1.0in 1.25in; mso-header-margin:.5in; mso-footer-margin:.5in; mso-paper-source:0;} div.Section1 {page:Section1;} /* List Definitions */ @list l0 {mso-list-id:1276670365; mso-list-type:hybrid; mso-list-template-ids:1802503346 1535782348 67698713 67698715 67698703 67698713 67698715 67698703 67698713 67698715;} @list l0:level1 {mso-level-start-at:13; mso-level-tab-stop:48.0pt; mso-level-number-position:left; margin-left:48.0pt; text-indent:-30.0pt;} ol {margin-bottom:0in;} ul {margin-bottom:0in;} --> </style> <h3><a name="6302631280933418248"></a><a href="http://educationalradionet.blogspot.com/2009/07/blog-post-5-fldigi-wrap-up-review-and.html">Blog Post 5 – FLDIGI Wrap-up Review and the The Amazing World of Weak Signal Modes – WSPR – Weak Signal Propagation Reporter</a> </h3> <p class="MsoBodyText"><a name="OLE_LINK1">Blog Post 5 – FLDIGI Wrap-up Review and the The Amazing World of Weak Signal Modes – WSPR – Weak Signal Propagation Reporter </a></p> <p class="MsoNormal" style="margin: 0in -27pt 0.0001pt -9pt;"><!--[if !supportEmptyParas]--> <!--[endif]--><o:p></o:p></p> <p class="MsoNormal" style="margin-right: -27pt;">Wednesday July 8, 2009</p> <p class="MsoNormal" style="margin: 0in -27pt 0.0001pt -9pt;"><!--[if !supportEmptyParas]--> <!--[endif]--><o:p></o:p></p> <p class="MsoNormal"><b>This is Curt Black, WR5J with the Educational Radio Net – Please stand by for a DominoEX 22 Digital QST <o:p></o:p></b></p> <p class="MsoNormal"><!--[if !supportEmptyParas]--> <!--[endif]--><o:p></o:p></p> <p class="MsoNormal">(As before please set up your FLDIGI software. (Menu OP MODE, then select DominoEX, then slide over and down to select DominoEX 22 - since we haven’t tried that mode yet. Recall you can right click on the mode box at the bottom left corner to open the configuration screen for the modem. Do that and confirm that filtering and FEC are both checked – the 1.0 filter bandwidth factor is fine) </p> <p class="MsoNormal"><!--[if !supportEmptyParas]--> <!--[endif]--><o:p></o:p></p> <p class="MsoNormal">DominoEX is supposed to be quite robust and moderately fast and it has the advantage of transmitting tactical data during any pauses in the transmission – watch the bottom of the screen in the block to the left of the AFC and SQL check boxes. Just a reminder from last week - don’t have your volume very loud – place your microphone fairly close to your speaker so you don’t confuse the modem with echoes of the audio.</p> <p class="MsoNormal"><!--[if !supportEmptyParas]--> <!--[endif]--><o:p></o:p></p> <p class="MsoNormal">If none of this sounds familiar, go to the blog and look at post #2.
<br /></p><p class="MsoNormal">.</p><p class="MsoNormal">
<br /></p> <p class="MsoNormal"><!--[if !supportEmptyParas]--> <!--[endif]--><o:p></o:p></p> <p class="MsoNormal">OK off we go.</p> <p class="MsoNormal"><!--[if !supportEmptyParas]--> <!--[endif]--><o:p></o:p></p> <p class="MsoNormal">Send File Ghandi – DominoEX 22</p><p class="MsoNormal">.</p><p class="MsoNormal">
<br /></p> <p class="MsoNormal"><!--[if !supportEmptyParas]--> <!--[endif]--><o:p></o:p></p> <p class="MsoNormal"><!--[if !supportEmptyParas]--> <!--[endif]--><o:p></o:p></p> <p class="MsoNormal">Last week we got some practice with RS-ID, the Reed-Soloman Identifer, to automatically switch our software to the correct mode and frequency. It sounded like we were getting about 40% of folks automatically switched by the end of the Net. After the net, I went up with Tammy to practice a little more on the West Seattle repeater and we tried turning on the video ID as well. That sends a short block of Hellschriber encoded text that paints the waterfall with your call, the mode and submode, or some tactical information if you wish.</p><p class="MsoNormal">.</p><p class="MsoNormal">
<br /></p> <p class="MsoNormal"><!--[if !supportEmptyParas]--> <!--[endif]--><o:p></o:p></p> <p class="MsoNormal">It seemed to work better, possibly because the video ID is sent first and maybe the repeater is already pumping out my audio by the time the RS-ID is transmitted. You set all that up on the ID tab under the Configure menu. Right now please make sure your “Detector searches entire passband” check box is checked.</p><p class="MsoNormal">.</p><p class="MsoNormal">
<br /></p> <p class="MsoNormal"><!--[if !supportEmptyParas]--> <!--[endif]--><o:p></o:p></p> <p class="MsoNormal"><!--[if !supportEmptyParas]--> <!--[endif]--><o:p></o:p></p> <p class="MsoNormal">I’ll send a file now with BPSK-250, but I’ll send a short file first, then a longer file. That should give folks a chance to tune into the signal if the software doesn’t do it for you. I’ll transmit RS-ID each time so there should be three chances for the software to switch you automatically before the long file. Please be sure your RSID button is checked and showing green in the upper right corner of the FLDIGI screen.</p><p class="MsoNormal">.</p><p class="MsoNormal">
<br /></p> <p class="MsoNormal"><!--[if !supportEmptyParas]--> <!--[endif]--><o:p></o:p></p> <p class="MsoNormal"><!--[if !supportEmptyParas]--> <!--[endif]--><o:p></o:p></p> <p class="MsoNormal">Send File K3UK…</p><p class="MsoNormal">.</p><p class="MsoNormal">
<br /></p> <p class="MsoNormal"><!--[if !supportEmptyParas]--> <!--[endif]--><o:p></o:p></p> <p style="font-weight: bold; text-align: center;" class="MsoNormal"><span style="font-size:130%;">WSPR – Weak Signal Propagation Reporter</span></p><p style="font-weight: bold; text-align: center;" class="MsoNormal"><span style="font-size:130%;">.</span></p><p style="font-weight: bold; text-align: center;" class="MsoNormal"><span style="font-size:130%;">
<br /></span></p> <p class="MsoNormal"><!--[if !supportEmptyParas]--> <!--[endif]--><o:p></o:p></p> <p class="MsoNormal"><!--[if !supportEmptyParas]--> <!--[endif]--><o:p></o:p></p> <pre style="margin-right: -27pt;">Joe Taylor, K1JT, of Princeton has written a series of programs for brilliantly combining digital Signal Processing (DSP) and ham radio to allow us to plumb the depths of weak signal work.<span style=""> </span>Prior to the development of his tools, moon bounce with a modest station or bouncing short signals off the ionized trails of passing meteors was beyond the realm of possibility.<span style=""> </span>The program's name is WSPR (pronounced "whisper", which seems appropriate for extremely weak signals)
<br />.
<br />The name of the digital protocol implemented in WSPR is MEPT_JT, where the letters stand for "Manned Experimental Propagation Tests, by K1JT".
<br />.
<br />
<br /></pre> <p class="MsoNormal"><!--[if !supportEmptyParas]--> <!--[endif]--><o:p></o:p></p> <pre>1. Download WSPR from the WSJT home page,</pre><pre><span style=""> </span>http://physics.princeton.edu/pulsar/K1JT/
<br />.
<br />
<br /></pre><pre><!--[if !supportEmptyParas]--> <!--[endif]--><o:p></o:p></pre><pre>2. Run the resulting executable file to install WSPR.<span style="">
<br />.
<br /> </span></pre><pre><!--[if !supportEmptyParas]--> <!--[endif]--><o:p></o:p></pre><pre>3. Start the program by double-clicking on its desktop icon.<span style="">
<br />.
<br /> </span></pre><pre><!--[if !supportEmptyParas]--> <!--[endif]--><o:p></o:p></pre><pre>4. Open the Setup -> Options menu and enter your callsign and</pre><pre><span style=""> </span>6-character grid locator.
<br />.
<br />
<br /></pre><pre><!--[if !supportEmptyParas]--> <!--[endif]--><o:p></o:p></pre><pre style="margin-right: -27pt;">5. Enter the COM port number to be used for PTT control in the box labeled</pre><pre style="margin-right: -27pt;"><span style=""> </span>PTT Port.<span style=""> </span>(For example, enter 1 if you will use COM1.)<span style=""> </span>Enter 0 </pre><pre style="margin-right: -27pt;"><span style=""> </span>if you will use VOX control.
<br />.
<br />
<br /></pre><pre style="margin-right: -27pt;"><!--[if !supportEmptyParas]--> <!--[endif]--><o:p></o:p></pre><pre style="margin-right: -27pt;">6. If you have more than one sound card and do not wish to use the</pre><pre style="margin-right: -27pt;"><span style=""> </span>Windows default sound card for WSPR, examine the list of sound</pre><pre style="margin-right: -27pt;"><span style=""> </span>devices in the console window (the one with black background).</pre><pre style="margin-right: -27pt;"><span style=""> </span>Enter the desired device numbers in the boxes labeled Audio In and</pre><pre style="margin-right: -27pt;"><span style=""> </span>Audio Out.
<br />.
<br />
<br /></pre><pre style="margin-right: -27pt;"><!--[if !supportEmptyParas]--> <!--[endif]--><o:p></o:p></pre><pre style="margin-right: -27pt;">7. Select your transmitter power in dBm in the appropriate Options box.
<br />.
<br />
<br /></pre><pre style="margin-right: -27pt;"><!--[if !supportEmptyParas]--> <!--[endif]--><o:p></o:p></pre><pre style="margin-right: -27pt;">8. On the main screen, enter your SSB transceiver dial frequency and</pre><pre style="margin-right: -27pt;"><span style=""> </span>desired Tx frequency in MHz.<span style=""> </span>Your transceiver should be set to USB</pre><pre style="margin-right: -27pt;"><span style=""> </span>mode.<span style=""> </span>(You can also set the Tx frequency by double-clicking with</pre><pre style="margin-right: -27pt;"><span style=""> </span>the mouse on the waterfall display, after setting the Dial</pre><pre style="margin-right: -27pt;"><span style=""> </span>frequency.)
<br />.
<br />
<br /></pre><pre style="margin-right: -27pt;"><!--[if !supportEmptyParas]--> <!--[endif]--><o:p></o:p></pre><pre style="margin-right: -27pt;">9. Click on "Rx" to receive only, on "Tx" to transmit only, or on the</pre><pre><span style=""> </span>desired average percentage of transmission cycles.<span style=""> </span>In this case</pre><pre><span style=""> </span>the program will decide whether to transmit or receive during any</pre><pre><span style=""> </span>given two-minute interval, and will do so in such a way as to</pre><pre><span style=""> </span>randomize your T/R pattern.<span style=""> </span>This procedure will maximize your</pre><pre><span style=""> </span>chances of receiving any other WSPR station operating within a +/-</pre><pre><span style=""> </span>100 Hz range centered 1500 Hz above your dial frequency.
<br />.
<br />
<br /></pre><pre><!--[if !supportEmptyParas]--> <!--[endif]--><o:p></o:p></pre><pre>10. Be sure that your computer clock is correct to +/- 1 second.<span style=""> </span>If</pre><pre><span style=""> </span>necessary you can make small adjustments by left- or right-clicking</pre><pre><span style=""> </span>on the "Dsec" label.
<br />.
<br />
<br /></pre><pre><!--[if !supportEmptyParas]--> <!--[endif]--><o:p></o:p></pre><pre>11. WSPR will begin a Tx or Rx sequence at the start of each even UTC</pre><pre><span style=""> </span>minute.<span style=""> </span>The waterfall will update near the end of each Rx</pre><pre><span style=""> </span>sequence.
<br />.
<br />
<br /></pre><pre><!--[if !supportEmptyParas]--> <!--[endif]--><o:p></o:p></pre><pre>12. Check the box "Upload spots" if your computer is connected to the</pre><pre><span style=""> </span>internet and you want your received spots uploaded to the WSPRnet</pre><pre><span style=""> </span>database.<span style=""> </span>For information on this excellent resource, direct your</pre><pre><span style=""> </span>browser to www.wsprnet.org.
<br />.
<br />
<br /></pre><pre><!--[if !supportEmptyParas]--> <!--[endif]--><o:p></o:p></pre><pre style="margin-left: 48pt; text-indent: -30pt;"><!--[if !supportLists]-->13.The weirdest thing about this software is setting the frequency – just use the drop down box under the BAND menu item.<span style=""> </span>Check the WSPRNET.ORG website at the bottom of each page for the current QRGs or frequency list.<span style=""> </span>If you need to update your software, just type the value into the box on screen and it will update the value in program.</pre><pre><!--[if !supportEmptyParas]--> <!--[endif]--><o:p></o:p></pre><pre><!--[if !supportEmptyParas]--> <!--[endif]--><o:p></o:p></pre><pre>Here are the configuration screens – to find the value for the AUDIO in and AUDIO Out boxes see the next screen...</pre> <p class="MsoNormal"><!--[if gte vml 1]><v:shapetype id="_x0000_t75" coordsize="21600,21600" spt="75" preferrelative="t" path="m@4@5l@4@11@9@11@9@5xe" filled="f" stroked="f"> <v:stroke joinstyle="miter"> <v:formulas> <v:f eqn="if lineDrawn pixelLineWidth 0"> <v:f eqn="sum @0 1 0"> <v:f eqn="sum 0 0 @1"> <v:f eqn="prod @2 1 2"> <v:f eqn="prod @3 21600 pixelWidth"> <v:f eqn="prod @3 21600 pixelHeight"> <v:f eqn="sum @0 0 1"> <v:f eqn="prod @6 1 2"> <v:f eqn="prod @7 21600 pixelWidth"> <v:f eqn="sum @8 21600 0"> <v:f eqn="prod @7 21600 pixelHeight"> <v:f eqn="sum @10 21600 0"> </v:formulas> <v:path extrusionok="f" gradientshapeok="t" connecttype="rect"> <o:lock ext="edit" aspectratio="t"> </v:shapetype><v:shape id="_x0000_i1025" type="#_x0000_t75" style="'width:146.25pt;"> <v:imagedata src="file:///C:/DOCUME~1/ADMINI~1/LOCALS~1/Temp/msoclip1/01/clip_image001.png" title=""> </v:shape><![endif]--><!--[if !vml]-->
<br /><!--[endif]--></p> <p class="MsoNormal"><!--[if !supportEmptyParas]--> <!--[endif]--><o:p></o:p></p> <p class="MsoNormal">
<br /><!--[if gte vml 1]><v:shape id="_x0000_i1026" type="#_x0000_t75" style="'width:6in;height:213.75pt'"> <v:imagedata src="file:///C:/DOCUME~1/ADMINI~1/LOCALS~1/Temp/msoclip1/01/clip_image003.png" title=""> </v:shape><![endif]--><!--[if !vml]--></p><p class="MsoNormal">.</p><p class="MsoNormal">
<br /><!--[endif]--></p> <p class="MsoNormal">Just take the AUDIO DEVICE number from the screen above.<span style=""> </span>If you are running a NAVIGATOR interface or a SIGNALINK, you will see USB AUDIO CODEC as your choices – just pick the one that is both an input channel and USB AUDIO CODEC for the input.</p> <p class="MsoNormal"><!--[if !supportEmptyParas]--> <!--[endif]--><o:p></o:p></p> <p class="MsoNormal">
<br /><!--[if gte vml 1]><v:shape id="_x0000_i1027" type="#_x0000_t75" style="'width:6in;height:338.25pt'"> <v:imagedata src="file:///C:/DOCUME~1/ADMINI~1/LOCALS~1/Temp/msoclip1/01/clip_image005.png" title=""> </v:shape><![endif]--><!--[if !vml]--></p><p class="MsoNormal">.</p><p class="MsoNormal">
<br /><!--[endif]--></p> <p class="MsoNormal">Set your transceiver on one of the frequencies from the website.<span style=""> </span>Then click somewhere to the left of the 100 to 300 frequency scale to set a transmit frequency. <span style=""> </span>As you monitor a frequency, you will see activity as colored horizontal bands in a particular 2-minute time slot.<span style=""> </span>Each slot gets a rectangle on the screen.<span style=""> </span>If you transmit, there will be<span style=""> </span>bright green line and you will notice the time stamp on the bottom of the rectangle will miss a 2 minute period.</p><p class="MsoNormal">.</p><p class="MsoNormal">
<br /></p> <p class="MsoNormal"><!--[if !supportEmptyParas]--> <!--[endif]--><o:p></o:p></p> <p class="MsoNormal">All the stations are synchronized – your computer clock should be within a second of WWV.<span style=""> </span>Use a piece of software like Dimension 4, free for non-commercial use from</p><p class="MsoNormal"> <a href="http://www.thinkman.com/dimension4/download.htm">http://www.thinkman.com/dimension4/download.htm</a> to get your clock to within 0.01 sec.</p><p class="MsoNormal">.</p><p class="MsoNormal">
<br /></p> <p class="MsoNormal"><!--[if !supportEmptyParas]--> <!--[endif]--><o:p></o:p></p> <p class="MsoNormal">This is a weak signal mode – it really doesn’t need much power – try 1 watt and see who hears you and where they are.<span style=""> </span>Try to operate at your local sunrise or sunset to really see what happens as the bands change – that grayline propagation thing really is real – it is when I’ve gotten the farthest.</p><p class="MsoNormal">.</p><p class="MsoNormal">
<br /></p> <p class="MsoNormal"><!--[if !supportEmptyParas]--> <!--[endif]--><o:p></o:p></p> <p class="MsoNormal">The MEPT protocol is a variation of work done by IK0VVE and others which they called QRSS for very slow cw.</p><p class="MsoNormal">.</p><p class="MsoNormal">
<br /><span style=""> </span></p> <p class="MsoNormal"><!--[if !supportEmptyParas]--> <!--[endif]--><o:p></o:p></p> <p class="MsoNormal">More on QRSS here: <a href="http://www.ik0vve.net/mept1.aspx">http://www.ik0vve.net/mept1.aspx</a></p><p class="MsoNormal"><a href="http://www.ik0vve.net/mept1.aspx">.</a></p><p class="MsoNormal"><a href="http://www.ik0vve.net/mept1.aspx">
<br /></a></p> <p class="MsoNormal"><!--[if !supportEmptyParas]--> <!--[endif]--><o:p></o:p></p> <p class="MsoNormal">More on Weak Signal Modes other than WSPR and WSJT (coming soon) like JASON can be found here:</p> <p class="MsoNormal"><a href="http://www.weaksignals.com/">http://www.weaksignals.com/</a></p><p class="MsoNormal"><a href="http://www.weaksignals.com/">.</a></p><p class="MsoNormal"><a href="http://www.weaksignals.com/">
<br /></a></p> <p class="MsoNormal"><!--[if !supportEmptyParas]--> <!--[endif]--><o:p></o:p></p> <p class="MsoNormal">While the software is cool and works great, the aspect that has lead to the significant popularity of WSPR is the website where you can see where your signals are going in real time – or have a record of where every signal you produced was ever heard.<span style=""> </span>That is WSPRNET.ORG</p><p class="MsoNormal">.</p><p class="MsoNormal">
<br /></p> <p class="MsoNormal"><!--[if !supportEmptyParas]--> <!--[endif]--><o:p></o:p></p> <p class="MsoNormal"><!--[if gte vml 1]><v:shape id="_x0000_i1028" type="#_x0000_t75" style="'width:431.25pt;height:313.5pt'"> <v:imagedata src="file:///C:/DOCUME~1/ADMINI~1/LOCALS~1/Temp/msoclip1/01/clip_image007.png" title=""> </v:shape><![endif]--><!--[if !vml]-->
<br /><!--[endif]--></p> <p class="MsoNormal"><!--[if !supportEmptyParas]--> <!--[endif]--><o:p></o:p></p> <p class="MsoNormal"><!--[if !supportEmptyParas]--> <!--[endif]--><o:p></o:p></p> <p class="MsoNormal"><!--[if !supportEmptyParas]--> <!--[endif]--><o:p></o:p></p> <p class="MsoNormal"><!--[if !supportEmptyParas]--> <!--[endif]--><o:p></o:p></p> <p class="MsoNormal"><!--[if !supportEmptyParas]--> <!--[endif]--><o:p></o:p></p><p class="MsoNormal"><!--[if !supportEmptyParas]--> <!--[endif]--><o:p></o:p></p> <p class="MsoNormal"><!--[if !supportEmptyParas]--> <!--[endif]--><o:p></o:p></p><p class="MsoNormal"><!--[if !supportEmptyParas]--> <!--[endif]--><o:p></o:p></p> <p class="MsoNormal"><!--[if !supportEmptyParas]--> <!--[endif]--><o:p></o:p></p> <p style="text-align: center; font-weight: bold;" class="MsoNormal"><span style="font-size:180%;">This Week’s Digital News…</span></p><p style="text-align: center; font-weight: bold;" class="MsoNormal"><span style="font-size:180%;">.</span></p><p style="text-align: center; font-weight: bold;" class="MsoNormal"><span style="font-size:180%;">
<br /></span></p> <p class="MsoNormal"><span style=";font-family:";font-size:100%;" >FLDIGI, the software we have been using the last 5 weeks has been updated to version 3.11.6. No changes that would keep you from doing what we are doing tonight, but changes to the contest logging and other logging functions to automate grabbing the correct info into the correct fields. Also changes to the PSK Reporter functions.
<br /></span></p><p class="MsoNormal"><span style=";font-family:";font-size:100%;" >.</span></p><p class="MsoNormal"><span style=";font-family:";font-size:100%;" >
<br /></span></p> <p class="MsoNormal"><span style=";font-family:";font-size:100%;" >Ham Radio Deluxe version 5 is now available. The new version has RSID, Contestia mode and lots more including:</span></p><p class="MsoNormal"><span style=";font-family:";font-size:100%;" >.</span></p><p class="MsoNormal"><span style=";font-family:";font-size:100%;" >
<br /></span></p> <p class="MsoNormal"><span style=";font-family:";font-size:100%;" >a.. DX Cluster,</span></p> <p class="MsoNormal"><span style=";font-family:";font-size:100%;" >b.. Sunspot (Solar Cycle) displays,</span></p> <p class="MsoNormal"><span style=";font-family:";font-size:100%;" >c.. Audio recorder and monitor ,</span></p> <p class="MsoNormal"><span style=";font-family:";font-size:100%;" >d.. Greyline display,</span></p> <p class="MsoNormal"><span style=";font-family:";font-size:100%;" >e.. Support for Microsoft Access, MySQL and Microsoft SQL Server,</span></p> <p class="MsoNormal"><span style=";font-family:";font-size:100%;" >f.. Full networking.</span></p> <p class="MsoNormal"><span style=";font-family:";font-size:100%;" >a.. Enhanced Digital Master 780:</span></p> <p class="MsoNormal"><span style=";font-family:";font-size:100%;" >a.. User interface simplified,</span></p> <p class="MsoNormal"><span style=";font-family:";font-size:100%;" >b.. Added Contestia and RTTYM.</span></p> <p class="MsoNormal"><span style=";font-family:";font-size:100%;" >a.. Satellite Tracking is now a standalone program:</span></p> <p class="MsoNormal"><span style=";font-family:";font-size:100%;" >a.. Improved display.</span></p> <p class="MsoNormal"><span style=";font-family:";font-size:100%;" >a.. Rotator support is now a standalone program:</span></p> <p class="MsoNormal"><span style=";font-family:";font-size:100%;" >a.. Point and shoot,</span></p> <p class="MsoNormal"><span style=";font-family:";font-size:100%;" >b.. DDE tracking,</span></p> <p class="MsoNormal"><span style=";font-family:";font-size:100%;" >c.. DDE interface,</span></p> <p class="MsoNormal"><span style=";font-family:";font-size:100%;" >d.. Modern display.</span></p> <p class="MsoNormal"><span style=";font-family:";font-size:100%;" >_______________________________________________</span></p> <p class="MsoNormal"><span style=";font-family:";font-size:100%;" >From Seatcp mailing list (If you haven't yet met the SEATCP list - you will when we get to Packet and other resources the are "...digital and fun"...</span></p><p class="MsoNormal"><span style=";font-family:";font-size:100%;" >.</span></p><p class="MsoNormal"><span style=";font-family:";font-size:100%;" >
<br /></span></p> <p class="MsoNormal"><span style=";font-family:";font-size:100%;" >Seatcp@wetnet.net</span></p><p class="MsoNormal"><span style=";font-family:";font-size:100%;" >.</span></p><p class="MsoNormal"><span style=";font-family:";font-size:100%;" >
<br /></span></p> <p class="MsoNormal"><span style=";font-family:";font-size:100%;" ><a href="http://wetnet.net/mailman/listinfo/seatcp">http://wetnet.net/mailman/listinfo/seatcp</a></span></p><p class="MsoNormal">.</p><p class="MsoNormal">
<br /><span style=";font-family:";font-size:100%;" ><o:p></o:p></span></p> <p class="MsoNormal"><span style=";font-family:";font-size:100%;" ><!--[if !supportEmptyParas]--> <!--[endif]--><o:p></o:p></span></p> <p class="MsoNormal"><!--[if !supportEmptyParas]--> <!--[endif]--><span style="font-size:100%;"><o:p></o:p></span></p> <p class="MsoNormal"><span style="font-size:100%;">Get HRD/DM780 here, or if you do</span>n’t like to install things on the bleeding edge, you can wait until next week at this time when an update/bug fix is promised. This is still listed as beta. It is scheduled for official release on October 1, 2009..</p><p class="MsoNormal">.</p><p class="MsoNormal">
<br /></p> <p class="MsoNormal"><a href="http://www.ham-radio-deluxe.com/HRDv5/tabid/139/Default.aspx">http://www.ham-radio-deluxe.com/HRDv5/tabid/139/Default.aspx</a></p><p class="MsoNormal"><a href="http://www.ham-radio-deluxe.com/HRDv5/tabid/139/Default.aspx">.</a></p><p class="MsoNormal"><a href="http://www.ham-radio-deluxe.com/HRDv5/tabid/139/Default.aspx">
<br /></a></p> <p class="MsoNormal"><!--[if !supportEmptyParas]--> <!--[endif]--><o:p></o:p></p> <p class="MsoNormal">There are many enhancements – RS-ID being a primary one. It has RS-ID implemented in a very nice way. When an RS-ID is detected in the audio passband, a window opens and asks you if you would like to switch to Blah-mode on Blah-frequency. A single click takes you there.
<br /></p><p class="MsoNormal">.</p><p class="MsoNormal">
<br /></p> <p class="MsoNormal"><!--[if !supportEmptyParas]--> <!--[endif]--><o:p></o:p></p> <p class="MsoNormal">Just a reminder – we have been messing with FLDIGI because it is a very elegant package that is fully featured but simple to setup and use. HRD is not so simple, but is a great package and when used with DM780 is very fully featured. Your experience with FLDIGI should serve as a great foundation for HRD if you choose to try it out. As an indication, HRD is a 55meg download. FLDIGI is 6.6megs. Just for equal time, MULTIPSK for version 4.14 is 7.9megs. I can not put any of these on the Yahoo site because it has a maximum file size of about 5 megs.</p><p class="MsoNormal">.</p><p class="MsoNormal">
<br /></p> <p class="MsoNormal"><!--[if !supportEmptyParas]--> <!--[endif]--><o:p></o:p></p> <p class="MsoNormal">So, three main digital packages now have RS-ID. Here are the links for each one:</p><p class="MsoNormal">.</p><p class="MsoNormal">
<br /></p> <p class="MsoNormal">FLDIGI by David Freese, W1HKJ and Skip Teller, KH6TY:</p><p class="MsoNormal">.</p><p class="MsoNormal">
<br /></p> <p class="MsoNormal"><a href="http://www.w1hkj.com/">http://www.w1hkj.com/</a></p><p class="MsoNormal"><a href="http://www.w1hkj.com/">.</a></p><p class="MsoNormal"><a href="http://www.w1hkj.com/">
<br /></a></p> <p class="MsoNormal"><!--[if !supportEmptyParas]--> <!--[endif]--><o:p></o:p></p> <p class="MsoNormal">HRD/DM780 by Simon Brown, HB9DRV :</p><p class="MsoNormal">.</p><p class="MsoNormal">
<br /></p> <p class="MsoNormal"><a href="http://www.ham-radio-deluxe.com/HRDv5/tabid/139/Default.aspx">http://www.ham-radio-deluxe.com/HRDv5/tabid/139/Default.aspx</a></p><p class="MsoNormal"><a href="http://www.ham-radio-deluxe.com/HRDv5/tabid/139/Default.aspx">.</a></p><p class="MsoNormal"><a href="http://www.ham-radio-deluxe.com/HRDv5/tabid/139/Default.aspx">
<br /></a></p> <p class="MsoNormal"><!--[if !supportEmptyParas]--> <!--[endif]--><o:p></o:p></p> <p class="MsoNormal">MULTIPSK by Patrick Lindecker, F6CTE:</p><p class="MsoNormal">.</p><p class="MsoNormal">
<br /></p> <p class="MsoNormal"><a href="http://f6cte.free.fr/index_anglais.htm">http://f6cte.free.fr/index_anglais.htm</a></p><p class="MsoNormal"><a href="http://f6cte.free.fr/index_anglais.htm">.</a></p><p class="MsoNormal"><a href="http://f6cte.free.fr/index_anglais.htm">
<br /></a> </p> <p class="MsoNormal"><!--[if !supportEmptyParas]--> <!--[endif]--><o:p></o:p></p> <p class="MsoNormal">Patrick’s package is a great technical achievement. He offers the most sensitive modems and detection routines available and many modes (such as ALE-400) that are not available in any other software. The challenge is his user interface is very dense and can be tough on a first-time user. His philosophy is he wants all the controls in one place – and they are.
<br /></p><p class="MsoNormal">.</p><p class="MsoNormal">
<br /></p> <p class="MsoNormal"><!--[if !supportEmptyParas]--> <!--[endif]--><o:p></o:p></p> <p class="MsoNormal"><!--[if !supportEmptyParas]--> <!--[endif]--><o:p></o:p></p> <p class="MsoNormal">Other packages of significance don’t yet have RS-ID, but may be of interest to you, including:</p><p class="MsoNormal">.</p><p class="MsoNormal">
<br /></p> <p class="MsoNormal"><!--[if !supportEmptyParas]--> <!--[endif]--><o:p></o:p></p> <p class="MsoNormal">WINWARBLER, part of the DXLAB suite and available here:</p><p class="MsoNormal">.</p><p class="MsoNormal"><a href="http://www.dxlabsuite.com/winwarbler/download.htm">http://www.dxlabsuite.com/winwarbler/download.htm</a></p><p class="MsoNormal"><a href="http://www.dxlabsuite.com/winwarbler/download.htm">.</a></p><p class="MsoNormal"><a href="http://www.dxlabsuite.com/winwarbler/download.htm">
<br /></a> </p> <p class="MsoNormal"><!--[if !supportEmptyParas]--> <!--[endif]--><o:p></o:p></p> <p class="MsoNormal">DIGIPAN – by Skip Teller KH6 and one of the authors of FLDIGI and a founding father of digital modes in amateur radio:</p><p class="MsoNormal">.</p><p class="MsoNormal"><a href="http://home.comcast.net/%7Ehteller/digipan/">http://home.comcast.net/~hteller/digipan/</a></p><p class="MsoNormal"><a href="http://home.comcast.net/%7Ehteller/digipan/">.</a></p><p class="MsoNormal"><a href="http://home.comcast.net/%7Ehteller/digipan/">
<br /></a></p> <p class="MsoNormal"><!--[if !supportEmptyParas]--> <!--[endif]--><o:p></o:p></p> <p class="MsoNormal">MixW – updated in Jan, 2009 after a long hiatus. Payment of $50 required after a 15-day trial period.
<br /></p><p class="MsoNormal"><a href="http://www.mixw.net/index.php?j=downloads">.</a></p><p class="MsoNormal"><a href="http://www.mixw.net/index.php?j=downloads">http://www.mixw.net/index.php?j=downloads</a></p><p class="MsoNormal"><a href="http://www.mixw.net/index.php?j=downloads">.</a></p><p class="MsoNormal"><a href="http://www.mixw.net/index.php?j=downloads">
<br /></a></p> <p class="MsoNormal"><!--[if !supportEmptyParas]--> <!--[endif]--><o:p></o:p></p> <p class="MsoNormal">Check out this repository of digital and other ham radio software:</p><p class="MsoNormal">.</p><p class="MsoNormal">
<br /></p> <p class="MsoNormal"><a href="http://www.g3vfp.org/download.html">http://www.g3vfp.org/download.html</a></p><p class="MsoNormal"><a href="http://www.g3vfp.org/download.html">.</a></p><p class="MsoNormal"><a href="http://www.g3vfp.org/download.html">
<br /></a></p> <p class="MsoNormal"><!--[if !supportEmptyParas]--> <!--[endif]--><o:p></o:p></p> <p class="MsoNormal"><!--[if !supportEmptyParas]--> <!--[endif]--><o:p></o:p></p> <p class="MsoNormal"><span style="font-weight: bold;font-size:130%;" >Next week: </span>Slow Scan TV – Image transmission using both analog and digital software.</p><p class="MsoNormal">.
<br /></p> <p class="MsoNormal">Sign up for the Yahoo group at <a href="http://groups.yahoo.com/group/wa-digital">http://groups.yahoo.com/group/wa-digital</a> for past blog posts and the files. New files this week include a sample of about 5 minutes of 20 meters during the last field day from the ACS station. Feel free to practice with the playback function in FLDIGI. Instructions are on the file description on the Yahoo site.</p><p class="MsoNormal">.</p><p class="MsoNormal">
<br /></p> <p class="MsoNormal"><!--[if !supportEmptyParas]--> <!--[endif]--><o:p></o:p></p> <p class="MsoNormal"><!--[if !supportEmptyParas]--> <!--[endif]--><o:p></o:p></p> <p class="MsoNormal">See you on the waterfall</p><p class="MsoNormal">.</p><p class="MsoNormal">
<br /></p> <p class="MsoNormal"><!--[if !supportEmptyParas]--> <!--[endif]--><o:p></o:p></p> <p class="MsoNormal"><!--[if !supportEmptyParas]--> <!--[endif]--><o:p></o:p></p> <p class="MsoNormal">73 de WR5J – Curt Black</p> <p class="MsoNormal"><!--[if !supportEmptyParas]--> <!--[endif]--><o:p></o:p></p> WR5Jhttp://www.blogger.com/profile/16316513702643319581noreply@blogger.com0tag:blogger.com,1999:blog-4632435085083780021.post-19571283041234369402009-07-01T11:17:00.000-07:002009-07-01T11:24:55.235-07:002009 Schedule - Educational Radio Net - Summer of Digital Fun<meta equiv="Content-Type" content="text/html; charset=utf-8"><meta name="ProgId" content="Word.Document"><meta name="Generator" content="Microsoft Word 11"><meta name="Originator" content="Microsoft Word 11"><link rel="File-List" href="file:///C:%5CDOCUME%7E1%5Ccblack%5CLOCALS%7E1%5CTemp%5Cmsohtml1%5C01%5Cclip_filelist.xml"><!--[if gte mso 9]><xml> <w:worddocument> <w:view>Normal</w:View> <w:zoom>0</w:Zoom> <w:punctuationkerning/> <w:validateagainstschemas/> <w:saveifxmlinvalid>false</w:SaveIfXMLInvalid> <w:ignoremixedcontent>false</w:IgnoreMixedContent> <w:alwaysshowplaceholdertext>false</w:AlwaysShowPlaceholderText> <w:compatibility> <w:breakwrappedtables/> <w:snaptogridincell/> <w:wraptextwithpunct/> <w:useasianbreakrules/> <w:dontgrowautofit/> </w:Compatibility> <w:browserlevel>MicrosoftInternetExplorer4</w:BrowserLevel> </w:WordDocument> </xml><![endif]--><!--[if gte mso 9]><xml> <w:latentstyles deflockedstate="false" latentstylecount="156"> </w:LatentStyles> </xml><![endif]--><style> <!-- /* Font Definitions */ @font-face {font-family:"Tms Rmn"; panose-1:2 2 6 3 4 5 5 2 3 4; mso-font-charset:0; mso-generic-font-family:roman; mso-font-format:other; mso-font-pitch:variable; mso-font-signature:3 0 0 0 1 0;} /* Style Definitions */ p.MsoNormal, li.MsoNormal, div.MsoNormal {mso-style-parent:""; margin:0in; margin-bottom:.0001pt; mso-pagination:widow-orphan; font-size:12.0pt; font-family:"Times New Roman"; mso-fareast-font-family:"Times New Roman";} @page Section1 {size:8.5in 11.0in; margin:1.0in 1.25in 1.0in 1.25in; mso-header-margin:.5in; mso-footer-margin:.5in; mso-paper-source:0;} div.Section1 {page:Section1;} --> </style><!--[if gte mso 10]> <style> /* Style Definitions */ table.MsoNormalTable {mso-style-name:"Table Normal"; mso-tstyle-rowband-size:0; mso-tstyle-colband-size:0; mso-style-noshow:yes; mso-style-parent:""; mso-padding-alt:0in 5.4pt 0in 5.4pt; mso-para-margin:0in; mso-para-margin-bottom:.0001pt; mso-pagination:widow-orphan; font-size:10.0pt; font-family:"Times New Roman"; mso-ansi-language:#0400; mso-fareast-language:#0400; mso-bidi-language:#0400;} </style> <![endif]--> <p style="text-align: center;" class="MsoNormal"><span style=";font-family:";font-size:18;color:black;" > <span style="font-weight: bold; font-family: times new roman;">Schedule 2009</span>
<br /></span></p><p style="text-align: center; font-weight: bold; font-family: times new roman;" class="MsoNormal"><span style=";font-size:18;color:black;" >Educational Radio Net
<br /></span></p><p style="text-align: center;" class="MsoNormal"><span style=";font-family:";font-size:18;color:black;" ><span style="font-weight: bold; font-family: times new roman;"> Summer of Digital Fun </span><o:p></o:p></span></p> <p class="MsoNormal"><span style=";font-family:";font-size:9;color:black;" ><o:p> </o:p></span></p> <p class="MsoNormal" style="margin: 0in -45pt 0.0001pt;"><span style="color:black;">Blog Post - #1<span style=""> </span>Intro to Digital Communication, Software and Modes Wednesday, June 3, 2009<o:p></o:p></span></p> <p class="MsoNormal" style="margin: 0in -45pt 0.0001pt;"><o:p> </o:p></p> <p class="MsoNormal" style="margin: 0in -45pt 0.0001pt;"><span style="color:black;">Blog Post - #2<span style=""> </span>Intro to FLDIGI – Install, Setup and Mode Selection, Wednesday, June 10, 2009<o:p></o:p></span></p> <p class="MsoNormal" style="margin: 0in -45pt 0.0001pt;"><o:p> </o:p></p> <p class="MsoNormal" style="margin: 0in -45pt 0.0001pt;"><span style="color:black;">Blog Post - #3 Using FLDIGI – Starting with PSK-31 and Transmitting a Good Signal Wednesday, June 24<o:p></o:p></span></p> <p class="MsoNormal" style="margin: 0in -45pt 0.0001pt;"><o:p> </o:p></p> <p class="MsoNormal" style="margin: 0in -45pt 0.0001pt;"><span style="color:black;">Blog Post - #4 More FLDIGI – RTTY, the WRAP Utility and RS-ID, Wednesday July 1, 2009<o:p></o:p></span></p> <p class="MsoNormal" style="margin: 0in -45pt 0.0001pt;"><o:p> </o:p></p> <p class="MsoNormal" style="margin: 0in -45pt 0.0001pt;"><span style="color:black;">Blog Post - #5 </span>WSPR – Weak Signal Propagation Reporter,<span style="color:black;"> Wednesday July 8, 2009<o:p></o:p></span></p> <p class="MsoNormal" style="margin: 0in -45pt 0.0001pt;"><o:p> </o:p></p> <p class="MsoNormal" style="margin: 0in -45pt 0.0001pt;"><span style="color:black;">Blog Post - #6 </span><span style="color: rgb(21, 34, 43);">MMSSTV/EasyPAL, Slow Scan Image Transmission,</span><span style="color:black;"> Wednesday July 15, 2009</span><span style="color: rgb(21, 34, 43);"> <o:p></o:p></span></p> <p class="MsoNormal" style="margin: 0in -45pt 0.0001pt;"><span style="color: rgb(21, 34, 43);"><o:p> </o:p></span></p> <p class="MsoNormal" style="margin: 0in -45pt 0.0001pt;"><span style="color:black;">Blog Post - #7<span style=""> </span>Digital SSTV (week 2) EasyPAL, <span style=""> </span>Wednesday July 22, 2009<span style=""> </span><o:p></o:p></span></p> <p class="MsoNormal" style="margin: 0in -45pt 0.0001pt;"><o:p> </o:p></p> <p class="MsoNormal" style="margin: 0in -45pt 0.0001pt;"><span style="color:black;">Blog Post - #8 </span>WSJT-JT65A – Terrestrial HF, <span style="color:black;">Wednesday July 29, 2009</span> </p> <p class="MsoNormal" style="margin: 0in -45pt 0.0001pt;"><o:p> </o:p></p> <p class="MsoNormal" style="margin: 0in -45pt 0.0001pt;"><span style="color:black;">Blog Post - #9<span style=""> </span></span>WSJT-HS-Meteor Scatter,<span style="color:black;"> Wednesday August 5, 2009 <o:p></o:p></span></p> <p class="MsoNormal" style="margin: 0in -45pt 0.0001pt;"><o:p> </o:p></p> <p class="MsoNormal" style="margin: 0in -45pt 0.0001pt;"><span style="color:black;">Blog Post - #10<span style=""> </span></span><span style="color: rgb(21, 34, 43);">Packet Radio and MultiPSK,</span><span style="color:black;"> Wednesday August 12, 2009 <o:p></o:p></span></p> <p class="MsoNormal" style="margin: 0in -45pt 0.0001pt;"><span style="color: rgb(21, 34, 43);"><o:p> </o:p></span></p> <p class="MsoNormal" style="margin: 0in -45pt 0.0001pt;"><span style="color:black;">Blog Post - #11<span style=""> </span>Packet APRS – Automatic Position Reporting System, Wednesday August 19, 2009 <o:p></o:p></span></p> <p class="MsoNormal" style="margin: 0in -45pt 0.0001pt;"><span style="color:black;"><o:p> </o:p></span></p> <p class="MsoNormal" style="margin: 0in -45pt 0.0001pt;"><span style="color:black;">Blog Post - #12 </span><span style="color: rgb(21, 34, 43);">WINDRM – Digital Voice </span><span style="color:black;">and HRD/DM780, <span style=""> </span>Wednesday August 26, 2009<span style=""> </span><o:p></o:p></span></p> <p class="MsoNormal" style="margin: 0in -45pt 0.0001pt;"><span style="color:black;"><o:p> </o:p></span></p> <p class="MsoNormal" style="margin: 0in -45pt 0.0001pt;"><span style="color:black;">Blog Post - #13<span style=""> </span>Final Exam and </span><span style="color: rgb(21, 34, 43);">ECHOLINK</span><span style="color:black;">, Wednesday September 2, 2009<o:p></o:p></span></p> WR5Jhttp://www.blogger.com/profile/16316513702643319581noreply@blogger.com0tag:blogger.com,1999:blog-4632435085083780021.post-59436686549186867752009-06-30T16:53:00.000-07:002009-07-01T08:46:10.342-07:00FLDIGI –the WRAP Utility, RS-ID and Radio Teletype (RTTY)<a name="OLE_LINK1"><meta equiv="Content-Type" content="text/html; charset=utf-8"><meta name="ProgId" content="Word.Document"><meta name="Generator" content="Microsoft Word 11"><meta name="Originator" content="Microsoft Word 11"><link rel="File-List" href="file:///C:%5CDOCUME%7E1%5Ccblack%5CLOCALS%7E1%5CTemp%5Cmsohtml1%5C03%5Cclip_filelist.xml"><!--[if gte mso 9]><xml> <w:worddocument> <w:view>Normal</w:View> <w:zoom>0</w:Zoom> <w:punctuationkerning/> <w:validateagainstschemas/> <w:saveifxmlinvalid>false</w:SaveIfXMLInvalid> <w:ignoremixedcontent>false</w:IgnoreMixedContent> <w:alwaysshowplaceholdertext>false</w:AlwaysShowPlaceholderText> <w:compatibility> <w:breakwrappedtables/> <w:snaptogridincell/> <w:wraptextwithpunct/> <w:useasianbreakrules/> <w:dontgrowautofit/> </w:Compatibility> <w:browserlevel>MicrosoftInternetExplorer4</w:BrowserLevel> </w:WordDocument> </xml><![endif]--><!--[if gte mso 9]><xml> <w:latentstyles deflockedstate="false" latentstylecount="156"> </w:LatentStyles> </xml><![endif]--><style> <!-- /* Style Definitions */ p.MsoNormal, li.MsoNormal, div.MsoNormal {mso-style-parent:""; margin:0in; margin-bottom:.0001pt; mso-pagination:widow-orphan; font-size:12.0pt; font-family:"Times New Roman"; mso-fareast-font-family:"Times New Roman";} p.MsoBodyText2, li.MsoBodyText2, div.MsoBodyText2 {margin:0in; margin-bottom:.0001pt; mso-pagination:widow-orphan; font-size:12.0pt; mso-bidi-font-size:10.0pt; font-family:Arial; mso-fareast-font-family:"Times New Roman"; mso-bidi-font-family:"Times New Roman"; mso-ansi-language:FR;} a:link, span.MsoHyperlink {color:blue; text-decoration:underline; text-underline:single;} a:visited, span.MsoHyperlinkFollowed {color:#606420; text-decoration:underline; text-underline:single;} @page Section1 {size:8.5in 11.0in; margin:1.0in 1.25in 1.0in 1.25in; mso-header-margin:.5in; mso-footer-margin:.5in; mso-paper-source:0;} div.Section1 {page:Section1;} --> </style><!--[if gte mso 10]> <style> /* Style Definitions */ table.MsoNormalTable {mso-style-name:"Table Normal"; mso-tstyle-rowband-size:0; mso-tstyle-colband-size:0; mso-style-noshow:yes; mso-style-parent:""; mso-padding-alt:0in 5.4pt 0in 5.4pt; mso-para-margin:0in; mso-para-margin-bottom:.0001pt; mso-pagination:widow-orphan; font-size:10.0pt; font-family:"Times New Roman"; mso-ansi-language:#0400; mso-fareast-language:#0400; mso-bidi-language:#0400;} </style> <![endif]--></a><meta equiv="Content-Type" content="text/html; charset=utf-8"><meta name="ProgId" content="Word.Document"><meta name="Generator" content="Microsoft Word 11"><meta name="Originator" content="Microsoft Word 11"><link rel="File-List" href="file:///C:%5CDOCUME%7E1%5Ccblack%5CLOCALS%7E1%5CTemp%5Cmsohtml1%5C01%5Cclip_filelist.xml"><!--[if gte mso 9]><xml> <w:worddocument> <w:view>Normal</w:View> <w:zoom>0</w:Zoom> <w:punctuationkerning/> <w:validateagainstschemas/> <w:saveifxmlinvalid>false</w:SaveIfXMLInvalid> <w:ignoremixedcontent>false</w:IgnoreMixedContent> <w:alwaysshowplaceholdertext>false</w:AlwaysShowPlaceholderText> <w:compatibility> <w:breakwrappedtables/> <w:snaptogridincell/> <w:wraptextwithpunct/> <w:useasianbreakrules/> <w:dontgrowautofit/> </w:Compatibility> <w:browserlevel>MicrosoftInternetExplorer4</w:BrowserLevel> </w:WordDocument> </xml><![endif]--><!--[if gte mso 9]><xml> <w:latentstyles deflockedstate="false" latentstylecount="156"> </w:LatentStyles> </xml><![endif]--><style> <!-- /* Style Definitions */ p.MsoNormal, li.MsoNormal, div.MsoNormal {mso-style-parent:""; margin:0in; margin-bottom:.0001pt; mso-pagination:widow-orphan; font-size:12.0pt; font-family:"Times New Roman"; mso-fareast-font-family:"Times New Roman";} h1 {mso-style-next:Normal; margin:0in; margin-bottom:.0001pt; text-align:center; mso-pagination:widow-orphan; page-break-after:avoid; mso-outline-level:1; font-size:18.0pt; mso-bidi-font-size:12.0pt; font-family:"Times New Roman"; mso-font-kerning:0pt;} h2 {mso-style-next:Normal; margin:0in; margin-bottom:.0001pt; text-align:center; mso-pagination:widow-orphan; page-break-after:avoid; mso-outline-level:2; font-size:16.0pt; mso-bidi-font-size:12.0pt; font-family:"Times New Roman";} p.MsoBodyText2, li.MsoBodyText2, div.MsoBodyText2 {margin:0in; margin-bottom:.0001pt; mso-pagination:widow-orphan; font-size:12.0pt; mso-bidi-font-size:10.0pt; font-family:Arial; mso-fareast-font-family:"Times New Roman"; mso-bidi-font-family:"Times New Roman"; mso-ansi-language:FR;} a:link, span.MsoHyperlink {color:blue; text-decoration:underline; text-underline:single;} a:visited, span.MsoHyperlinkFollowed {color:#606420; text-decoration:underline; text-underline:single;} @page Section1 {size:8.5in 11.0in; margin:1.0in 1.25in 1.0in 1.25in; mso-header-margin:.5in; mso-footer-margin:.5in; mso-paper-source:0;} div.Section1 {page:Section1;} --> </style><!--[if gte mso 10]> <style> /* Style Definitions */ table.MsoNormalTable {mso-style-name:"Table Normal"; mso-tstyle-rowband-size:0; mso-tstyle-colband-size:0; mso-style-noshow:yes; mso-style-parent:""; mso-padding-alt:0in 5.4pt 0in 5.4pt; mso-para-margin:0in; mso-para-margin-bottom:.0001pt; mso-pagination:widow-orphan; font-size:10.0pt; font-family:"Times New Roman"; mso-ansi-language:#0400; mso-fareast-language:#0400; mso-bidi-language:#0400;} </style> <![endif]--> <p class="MsoNormal" style="margin: 0in -27pt 0.0001pt -9pt;"><a name="OLE_LINK1"><b><span style="font-size: 14pt;">Blog Post 4 – FLDIGI – Radio Teletype (RTTY) the WRAP Utility and RS-ID<span style=""> </span></span></b></a>Wednesday July 1, 2009</p> <p class="MsoNormal"><o:p> </o:p></p> <p class="MsoNormal"><b>This is Curt Black, WR5J with the Educational Radio Net – Please stand by for a PSK-31 Digital QST<span style=""> </span><o:p></o:p></b></p> <p class="MsoNormal"><b><o:p> </o:p></b></p> <p class="MsoNormal">(As before please set up your FLDIGI software for Menu OP MODE, then select PSK then slide over to select BPSK-31 – for binary phase shift keying – 31baud.<span style=""> </span>Just a reminder from last week<span style=""> </span>- don’t have your volume very loud – place your microphone fairly close to your speaker so you don’t confuse the modem with echoes of the audio..<span style=""> </span></p> <p class="MsoNormal">If none of this sounds familiar, go to the blog and look at post #2.<span style=""> </span>OK off we go.</p> <p class="MsoNormal"><o:p> </o:p></p> <p class="MsoNormal">That was a little chunk of field day to remind you what fun that was.<span style=""> </span>There were more digital signals than ever before on the bands.<span style=""> </span>How did folks do on the copy?<span style=""> </span></p> <p class="MsoNormal"><o:p> </o:p></p> <p class="MsoNormal">We have about 10 weeks to go till September 2, so I think I’ll change the format just a bit skip the check-in process so as to recover that 10 minutes I took last week.<span style=""> </span>Although I appreciated the chance to get some feedback from folks on how their installations have gone, maybe we can make it less formal and just grab questions as they come up.<span style=""> </span></p> <p class="MsoNormal"><o:p> </o:p></p> <p class="MsoNormal">I’m beginning to have faith that there are people out there in radio land.<span style=""> </span>Just a reminder, there are now 20 people signed up on the YAHOO! WA-DIGITAL list – that is turning into a good resource for the software and instructions and background documents for this series.<span style=""> </span>Please signup if you haven’t yet.<span style=""> </span>Just this week I put up background documents on PSK-31, RTTY, WSPR and a proposed<span style=""> </span>schedule for the rest of the summer.<span style=""> </span>As always, please feel free to break in with any questions at any time during the net.<span style=""> </span>Also, don’t hesitate to send an email during the week at black@nwfirst.com.</p> <p class="MsoNormal"><o:p> </o:p></p> <p class="MsoNormal">This week I’d like to go over a few more features of FLDIGI.<span style=""> </span>I’d like to get setup for automatic switching to the proper mode using the Reed-Solomon Identifier or RS-ID feature.<span style=""> </span>I’d also like to get us to the point where we can send each other error free messages using the WRAP utility included in the NBEMS suite.<span style=""> </span></p> <p class="MsoNormal"><o:p> </o:p></p> <h2>Review from Last Week</h2> <p class="MsoNormal"><o:p> </o:p></p> <p class="MsoNormal">Several useful features are included in FLDIGI for changing quickly “on the fly”.<span style=""> </span>For example, you can right-click on the macro buttons to edit their content or to cut or paste information.<span style=""> </span>Remember, there are 4 sets accessable from by clicking on the right end of the menu bar.<span style=""> </span>As we discussed on the net, you can left-click on the mode name in the far lower left corner of the screen to switch to other variants of the mode currently selected.<span style=""> </span>A right click of the same button brings up the configuration pane for the mode currently in use.<span style=""> </span></p> <p class="MsoNormal"><o:p> </o:p></p> <p class="MsoNormal">There are just a few features that are not configurable, “on the fly”.<span style=""> </span>During the net I was asked how to customize the height of the waterfall.<span style=""> </span>I had trouble finding it which seemed odd because I’ve rooted around quite a bit in the program.<span style=""> </span>After the net I found it under the Configure Menu /<span style=""> </span>UI<span style=""> </span>(User Interface) choice / then click on the “Restart” tab.<span style=""> </span>This is a strange name and I would say it is why I couldn’t find it during the net, but it is called that because changes made here don’t occur until the next restart of the program.<span style=""> </span></p> <p class="MsoNormal"><o:p> </o:p></p> <p class="MsoNormal">Under the Restart tab you can set how high the waterfall is in pixels and how wide the waterfall is in Hertz.<span style=""> </span>I usually use the max height of 160 and 3500 for the width.<span style=""> </span>You can always zoom in with the X1, X2 or X4 in the bar under the waterfall, using the left facing arrow next to that magnification control to slew the waterfall to the left and the right facing control to move it to the right. The double bar that looks like a pause button is for centering the currently selected location where the modem is focused<span style=""> </span>in the waterfall (all these only work when you are zoomed in enough to need them).</p> <p class="MsoNormal"><o:p> </o:p></p> <p class="MsoNormal">We talked about the 2 minute buffer that is constantly saving the audio and how you can change modems in the OP MODE menu, and then click over an interesting signal with the right mouse button and then left click to decode the last 2 minutes with that new modem. </p> <p class="MsoNormal"><o:p> </o:p></p> <p class="MsoNormal">Last time we talked a little about the makeup of a PSK-31 signal and how sensitive the mode is during transmission to avoid over driving and splattering.<span style=""> </span>We looked at the information in the bottom line of the screen next to the mode identifier.<span style=""> </span>While decoding PSK-31, those boxes contain information on the Signal to Noise ratio and Inter-Modulation Distortion (IMD).<span style=""> </span>Remember to make those measurements on an idling PSK-31 station and that we are working to keep the value below minus 24 dB (for example minus 34 dB would b a great signal – a minus 11 dB would be a nasty signal that would be attracting lots of attention on the band). <b><span style=""> </span>These values are only for </b><b style="">received signals</b> – so you need the help of your fellow hams to find the quality of your own transmitted signal.<span style=""> </span>There are at least two devices to help you monitor your own signal as it is being transmitted – the IMD Meter by KK7UQ, Clint Hurd and the PSK Meter by George Rothbart, KF6VSG.<span style=""> </span>A comparison of the two products is on the bottom of the page found at <a href="http://kk7uq.com/html/imdmeter.html">http://kk7uq.com/html/imdmeter.html</a> </p> <p class="MsoNormal"><o:p> </o:p></p> <p class="MsoNormal"><o:p> </o:p></p> <h2>The Wrap Utility</h2> <p class="MsoNormal"><o:p> </o:p></p> <p class="MsoNormal">The WRAP utility program checksum feature lets sending stations transmit a plain text message, an image or a binary file with embedded coding that includes a checksum calculation. Multiple receiving stations can then verify 100% copy on received text.<span style=""> </span>I thought we would try that now.<span style=""> </span>I’m running version 3.11.5 but all versions in the 3.11 series work for this.<span style=""> </span></p> <p class="MsoNormal"><o:p> </o:p></p> <p class="MsoNormal">Before we get to wrapping, I want to say, “YOU SHOULD NEVER WRAP any of the MICROSOFT OFFICE APPLICATION FILES WITHOUT CONVERTING THEM”<span style=""> </span>You should convert a word document to text, an excel spreadsheet to a Comma Separated Value (CSV) format text file, etc.<span style=""> </span>A Word Document with 1 character in it is 13.8 kilobytes, when zipped it drops to 1.8K, but it is still a ratio of nearly 2 thousand to 1.<span style=""> </span>The WRAPing process expands the file to half again its original size during the ASCII Base64 encoding so that 1 character word file is still nearly 3 k.<span style=""> </span>Send text whenever possible.<span style=""> </span>This is a training issue, we are communicators trying to help transmit information – not a specific file, but the information in that file.<span style=""> </span>Think about efficiency before you hit the TX button.</p> <p class="MsoNormal">
<br />To set up for automated receipt of a “WRAPPED” message, please go to the CONFIGURE menu and slide down to the MISC item.<span style=""> </span>On the window that opens click on the TEXT CAPTURE tab.<span style=""> </span>Click the check box next to, “Enable Detection and Extraction”.</p> <p class="MsoNormal"><o:p> </o:p></p> <p class="MsoNormal">This will cause any text that begins with the string, or series of characters between, “[WRAP:beg] and [WRAP:end] to be pulled out and saved in your WRAP folder inside your FLDIGI.FILES folder under your login name in DOCUMENTS and SETTINGS.<span style=""> </span>This is very WINDOWS centric, but there are similar settings for Linux and Apple OS users.<span style=""> </span>If you navigate to that folder, I would suggest putting a shortcut to it on your start menu.<span style=""> </span>Then you can quickly open it and look for files saved there.<span style=""> </span>I would also put a copy of NOTEPAD and the WRAP.exe file in there – then everything is in one place and you have a shortcut to it on your start menu.</p> <p class="MsoNormal"><o:p> </o:p></p> <p class="MsoNormal">You should now be ready to receive a wrapped file – so lets try that now – Questions?</p> <p class="MsoNormal"><o:p> </o:p></p> <p class="MsoNormal"><o:p> </o:p></p> <p class="MsoNormal">To send a WRAP file, just create a text file by saving from your favorite word processor or pasting text into NOTEPAD.<span style=""> </span>Then save the file into the WRAP folder as a text file.<span style=""> </span>Take that text file and drag it over the icon for the WRAP.EXE utility and a new file will be created in the same directory with the same name except with a.WRAP extension.<span style=""> </span>To send this file, drag the new file to the bottom of the screen over the FLDIGI task and wait for that window to open, then continue dragging until you are anyplace in the send window, most of the bottom half of the screen.<span style=""> </span>Release the mouse button and the wrapped text will appear in the window to be sent.<span style=""> </span>You may want to put some explanatory text in the window before the file, but when you are ready, just press the TX button on the macro line and off it will go.</p> <p class="MsoNormal"><o:p> </o:p></p> <p class="MsoNormal">The powerful thing about this is that it allows transfer of files from one station to many in a format that allows all stations to know they have received the file error free.<span style=""> </span>Previously we would have to use an ARQ (Automatic Repeat reQuest) linking protocol one station at a time.<span style=""> </span>This has great potential for digital nets like this one or those that follow.<span style=""> </span>The NBEMS suite has an application called FLARQ.exe.<span style=""> </span>It allows two stations in QSO to form a linked condition and send error free data back and forth – however it is only one station at a time.<span style=""> </span>Since we can’t demo it through a repeater, and it only works on one station at a time, just check out the documentation on the PA-SITREP website or the author’s website at <a href="http://www.w1hkj.com/FlarqHelpFiles/flarq.html">http://www.w1hkj.com/FlarqHelpFiles/flarq.html</a> </p> <p class="MsoNormal"><o:p> </o:p></p> <p class="MsoNormal">Since that was pretty dense and a radio net is clearly not the best format for such a hands-on lesson, the blog post and Yahoo group file for Post #4 has links to two files on UTIPU which show exactly the steps I’ve described here, but much more graphically.</p> <p class="MsoNormal"><o:p> </o:p></p> <p class="MsoNormal"><a href="http://www.utipu.com/app/tip/id/10407/">http://www.utipu.com/app/tip/id/10407/</a></p> <p class="MsoNormal"><o:p> </o:p></p> <p class="MsoNormal"><a href="http://www.utipu.com/app/tip/id/10396/">http://www.utipu.com/app/tip/id/10396/</a></p> <p class="MsoNormal"><o:p> </o:p></p> <p class="MsoNormal"><a href="http://www.utipu.com/app/tip/id/10407/">http://www.utipu.com/app/tip/id/10407/</a><span style=""> </span>Receiving and unwraping example with Olivia 8/500 and very bad powerline noise</p> <p class="MsoNormal"><o:p> </o:p></p> <h1>RS-ID</h1> <p class="MsoNormal"><o:p> </o:p></p> <p class="MsoNormal"><o:p> </o:p></p> <p class="MsoBodyText2"><span style="font-family: "Times New Roman";">The "RS" ("RS" for "Reed-Solomon") identifier allows automatic identification any digital transmission done in one of the RX/TX modes handled by FLDIGI. If the sending station is using the feature (currently available in MULTIPSK, FLDIGI and by this August, HRD/DM780 – probably someday in MixW).<span style=""> </span>It detects the mode used and the center frequency<span style=""> </span>with a precision of +/- 2.7 Hz. <o:p></o:p></span></p> <p class="MsoBodyText2"><span style="font-family: "Times New Roman";"><o:p> </o:p></span></p> <p class="MsoBodyText2"><span style="font-family: "Times New Roman";">As soon as this identifier is received, FLDIGI switches to the proper mode and frequency and immediately decodes the QSO in progress or the call (CQ). This identifier is transmitted in 1.4 sec and has a bandwidth of 172 Hz. It is usually detected down to a Signal to Noise ratio of -18 dB<span style=""> </span>(or perfectly at about -16 dB), so it has a sensitivity equal or better than the majority of the digital modes (RTTY, PSK31...).<o:p></o:p></span></p> <p class="MsoBodyText2"><span lang="FR"><o:p> </o:p></span></p> <p class="MsoBodyText2"><span style="font-family: "Times New Roman";">This identifier can be transmitted before each CQ call or prior to each answer in a QSO.<span style=""> </span>Turn on this feature by going to the CONFIGURE menu and selecting the ID item.<span style=""> </span>On the window that opens, check both the, “TRANSMIT MODE RSID” box and the “Detector Searches Entire Passband” check box.<span style=""> </span>The actual searching is somewhat processor intensive, so to turn on the function in receive mode, there is a control in the upper right corner of the screen next to the TUNE button labeled, “RSID”.<span style=""> </span>Go ahead and make those settings.<span style=""> </span>Questions ?.<o:p></o:p></span></p> <p class="MsoBodyText2"><span style="font-family: "Times New Roman";"><o:p> </o:p></span></p> <p class="MsoBodyText2"><span style="font-family: "Times New Roman";">Now that you are set up, keep your mode setting on BPSK-31 and we will give it a little test.<span style=""> </span>I’ll pick a new mode and a new frequency.<span style=""> </span>Make sure your RSID button is pressed in the upper right corner of the FLDIGI screen.<span style=""> </span>We’ll see if everyone switches over and starts to decode it.<o:p></o:p></span></p> <p class="MsoNormal"><o:p> </o:p></p> <p class="MsoNormal" style="text-align: center;" align="center"><span style="font-size: 16pt;">RTTY (Radio Teletype)<o:p></o:p></span></p> <p class="MsoNormal"><o:p> </o:p></p> <p class="MsoNormal">The second most popular digital mode.<span style=""> </span>Somewhat more complex to set up and much less spectrally efficient than PSK-31.<span style=""> </span>I think the designer of PSK-31 was hoping his new mode would replace RTTY, but for better or worse, it is wildly popular all around the world and, while somewhat brute-force, is a lot of fun to use.<span style=""> </span>It can be hard to know what frequency to spot either yourself or others.<span style=""> </span>Unlike almost all the other digital modes we will use, this one can be found in Lower Side Band.<span style=""> </span>That is from tradition – and gets more confusing as we try to figure out how to spot our own frequency.<span style=""> </span>We need to pay attention to which sideband we transmit on in SSB.<span style=""> </span>So once we get back to HF and away from these demonstrations in FM, the sideband and frequency will rear their ugly heads as issues.<span style=""> </span>On RTTY, the inverted signal matters in contrast to PSK-31 or the other PSK flavors.<span style=""> </span></p> <p class="MsoNormal"><o:p> </o:p></p> <p class="MsoNormal">Rather than get too bogged down at this stage of our hour together, please look to the following websites for guidance:</p> <p class="MsoNormal"><o:p> </o:p></p> <p class="MsoNormal">Getting Started in RTTY with MMTTY at</p> <p class="MsoNormal"><a href="http://www.dxzone.com/cgi-bin/dir/jump2.cgi?ID=13022">http://www.dxzone.com/cgi-bin/dir/jump2.cgi?ID=13022</a></p> <p class="MsoNormal"><o:p> </o:p></p> <p class="MsoNormal">and</p> <p class="MsoNormal"><o:p> </o:p></p> <p class="MsoNormal">A RTTY Tutorial For Beginners at</p> <p class="MsoNormal"><a href="http://www.iw5edi.com/ham-radio/26/a-rtty-tutorial-for-beginners">http://www.iw5edi.com/ham-radio/26/a-rtty-tutorial-for-beginners</a> </p> <p class="MsoNormal"><o:p> </o:p></p> <p class="MsoNormal">Next Week one of Joe Taylor’s modes, K1JT, called WSPR, “Whisper” – the Weak Signal Propagation Reporter”.<span style=""> </span>An amazing mode that takes about 300hz of HF bandwidth and lets people all over the world share it to test RF propagation.<span style=""> </span>Your individual transmission will only be about 3 Hz wide.<span style=""> </span>It has been tremendously enhanced by the presence of the website, <a href="http://wsprnet.org/">http://wsprnet.org/</a> where after you easily create a free account, you can look at worldwide activity and a database with 7 million spots and growing at about 1000 spots an hour, 24 hours a day.<span style=""> </span>I’ve already put the software on the Yahoo group and the blog post with more info should be up early this weekend.</p> WR5Jhttp://www.blogger.com/profile/16316513702643319581noreply@blogger.com1tag:blogger.com,1999:blog-4632435085083780021.post-44436786692691326932009-06-23T22:56:00.000-07:002009-06-24T00:29:03.395-07:00Digital Radio Post 3 - FLDIGI and PSK-31<span style="font-weight: bold;">Session 3 - Continuing a Summer of Digital Communications Fun</span><br />June 24, 2009<br /><br />This is Curt Black, WR5J with the Educational Radio Net<br />– Please stand by for a DIGITAL QST<br /><br />Send File ALLMODE.wav<br /><br /><span style="font-weight: bold;">CHECKINS</span><br /><br /><br />Tonight I want to practice more with FLDIGI and work our way through more on-screen controls as we continue to acoustically couple our radios to our computers. <br /><br />So, before the net please set up your laptop near your radio with a microphone plugged into the computer so that the sound in your shack shows up visually on the waterfall display on the FLDIGI software. Set it up so if you clap your hands you see an indication of that sound moving down the screen.<br /><br />If this is your first session - go back to the previous blog entries (just lower down on this page) and read about downloading and installing the free software in the Narrow Band Emergency Messaging System (NBEMS) suite. It would be great if you could get your sound card calibrated with the CheckSR.exe software before the net to make sure your copy is as good as possible. If you can't you will still have good copy with MT63, but some of the other modes may not be as forgiving.<br /><br /><span style="font-weight: bold;">PSK-31 - Phase Shift Keying</span><br />(at 31 baud and with two tones 31 Hz apart).<br /><br />As the most popular digital mode on HF, I thought I would be remiss if we didn't start with PSK-31. I want to emphasize that we will be moving on to lots of other modes, so if your eyes are rolling back in your head because this is too pedestrian, have faith, we will be getting to the really cool stuff like WSPR, WSJT and SSTV real soon now. But this week - an intro to the PSK Modes.<br /><br /> I have put some great PDF files of PowerPoint presentations up on the wa-digital group site at<br /><br />http://groups.yahoo.com/group/wa-digital/files/<br /><br />Please join this Yahoo group - it seems the best way for me to get some of these great visual resources into your hands quickly. <br /><br />The two files by Clint Hurd, KK7UQ are from his Anchorage Convention talk last summer in Alaska. Clint lives in Port Orchard and has made interfaces and tools for helping people get the most out of digital modes for many years. Start with the file <span style="font-weight: bold;">Alaska Basic Slides.pdf </span>and check out all his information on digital modes. For the adventurous check out the second file, <span class="title"> <a style="font-weight: bold;" href="http://f1.grp.yahoofs.com/v1/8M5BSr3Aa4OisvoeIXG0efVddJn9H0Z62m1a7BNumgIooPtMWXCOwBIGoMsN16J5XwIlYMI_qz6mlsInASAi2A/Alaska%20Advanced%20Slides.pdf">Alaska Advanced Slides.pdf</a> for great tips on adjusting the waterfall for maximum sensitivity and resistance to strong signals in the audio passband. </span> Much more great information is available directly from Clint at his website:<br /><br /><span style="font-weight: bold;">http://kk7uq.com/html/hamfest.htm</span><br /><br />Here are some hints for working with PSK31 or any of the PSK flavors.<br /><br /><span style="font-weight: bold;">Hints to New PSK Users</span><br /><br />1. Make sure you are putting out a pure signal. Don't overdrive the rig (make sure ALC is showing absolutely no sign of life) You cannot achieve better communications by over driving the audio on any of the digital modes that require linearity. These include all of the modes that have an amplitude modulation component. Some like PSK and THROB have both an amplitude and a frequency or phase modulation component. An overdriven signal may produce more decoder errors than a properly driven signal of lesser power. This is particularly true for all variants of PSK<br /><br />2. The best way to know what your signal is like is to ask on the bands for a report from others – the software of the person receiving your signal will report out what your intermodulation distortion 3rd order intercept is in decibels (IMD) – you want an <span style="font-weight: bold;">IMD</span> value below<span style="font-weight: bold;"> minus 24dB</span>. You don't need a slide rule to figure this value out - the software calculates it anytime there is an <span style="font-weight: bold;">idling</span> PSK-31 station being decoded. It also gives you the signal to noise ratio - you need to pay attention to that before you believe the value you are seeing for the IMD window. If you have a nice -34dB IMD you are transmitting one fine signal. At minus 18 people will probably start giving you unsolicited reports since your signal will be about twice as wide as necessary. At –11dB you will have much of the band after you. For more good news - since we are using FM for these examples, the overdriving part is greatly reduced. But it is extremely important for your HF future as an A-1 Operator.<br /><br /><br />3. Don't type in all caps. This slows down your transmission, makes it more prone to errors, and is just annoying.<br /><br /><br />4. Remember that your HF rig is not set up to operate at a 100% duty cycle – voice operations tax your finals much less than most data modes. Lower your power to a level of 50% of what your rig can produce so you don’t burn out your finals. This will help the bands as well since many of our digital modes are detectable at very low power levels. Particularly for the weak signal modes like WSJT – one loud signal in the passband of your radio can make everyone else, especially DX, sadly unreadable. Chances are you will produce good copy at the stations listening to you with just a few watts. That is particularly true when we get to JT65A on 14.076 USB...<br /><br />5. There is way more to digital operation than PSK31. Tune a little above the PSK activity and call with Hell or MFSK16 or Olivia 16/500. You can use the sked page to arrange experiments with new or more esoteric modes. Try these pages for scheduling some activity –<br /><br /><br /><span style="font-weight: bold;">http://www.obriensweb.com/sked/</span><br /><br /><br /><span style="font-weight: bold;">http://www.hamspots.net/</span><br /><br />These websites aren’t needed for PSK31 – it is nearly always available on the frequencies listed below. But the less common modes are more challenging to find folks for a QSO. Below is a table of common PSK31 frequencies – you will frequently see the wider signals of PSK63 just a little higher.<br /><br />PSK31 FREQUENCIES<br />PSK31 HF Frequencies PSK31 VHF Frequencies<br />Band Frequency Band Frequency<br />160 meters 1.838 MHz 6 meters 50.290 MHz<br />80 meters 3.580 MHz 2 meters 144.144 MHz<br />40 meters 7.035 MHz 1.25 meters 222.07 MHz<br />30 meters 10.140 MHz 70 centi-meters 432.2 MHz<br />20 meters 14.070 MHz 33 centi-meters 909 MHz<br />17 meters 18.100 MHz <br />15 meters 21.080 MHz <br />10 meters 28.120 MHz <br />:<br /><br />We also have permission to practice on the West Seattle repeater at 441.800 output (up 5 MHz for input)with a tone of 141.3. Just ID with voice before and after your digital transmissions and maybe yield to any voice traffic that wants the repeater... It has been pretty quiet lately. Hopefully that will change as we bring the West Seattle Amature Radio Club back to life...<br /><br /><br />The yahoo group is another great way to set up a schedule with your fellow Educational Radio Net folk. Just send your message to wa-digital@yahoogroups.com<br /><br />As we send PSK-31 back and forth tonight - you will probably notice that you can lose copy if the volume gets very loud. The phase shifts that the software is looking for can be really messed up by echos in your shack- particularly from a wall about 16 feet away. The software is looking for phase shifts every 32 milliseconds - sound travels about 1000 feet per second - so that wall 16 feet away is just right to produce an echo at a really bad time - actually all the sound bouncing around your shack is the bad part of acoustic coupling. For PSK-31 just try turning the sound down and getting the mic closer to the speaker on the radio to avoid echos.<br /><br />I guess, this brings us to the desirability of having an interface between your radio and the computer. <br /><br />There are some great advantages to acoustic coupling - for one it couldn't be simpler. Additionally, there is no problem with RF getting into the computer when you are transmitting - at least not from the interface cables. But some of the modes we will want to use are going to be increasingly choosy about phase and the timing of sound arriving for processing. <br /><br />There are lots of choices of interfaces from junk-box parts to the $99 Tigertronics SignaLink to the $360 US Interface Navigator - each has pros and cons. <br /><br />There is lots of satisfaction from doing things out of the junk box. You can build a very workable interface with jacks and wires. You can build a better interface with isolation transformers. You can build a great interface with optoisolators and at some point, the time begins to make some of the commercial products look pretty good. The more expensive units provide lots of control over the radio, actual FSK keying (as opposed to audio-frequency shift keying, AFSK)and great user interfaces with just the controls you need where you might want them.<br /><br />We will continue to do an acoustically coupled transmission each week for practice and will probably try a round-robin through the repeater in another week or so. However, eventually I suspect you will want to have an interface to get signals into and out of your computer in the best possible form. So, please consider if your time and financial resources will allow it - it can open up an amazing world.<br /><br />Please take a look at Clint Hurd's presentations from the Alaska Hamfest last August on the Yahoo Group wa-digital if you haven't already.<br /><br />See you on the waterfall,<br /><br />vy 73 de WR5J<br /><br />Curt Black<br />black@nwfirst.comWR5Jhttp://www.blogger.com/profile/16316513702643319581noreply@blogger.com0tag:blogger.com,1999:blog-4632435085083780021.post-85041866995583484622009-06-09T21:58:00.001-07:002009-06-09T22:14:59.894-07:00Invitation to Join WA-DIGITAL - a Yahoo groupOk, this is Curt - WR5J<br /><br />I'm having trouble adding images to the files in this blog. <br /><br />To get around this, I'd like to invite people to join a Yahoo group I started about a month ago. This group is intended to facilitate communication among Washington State ham radio operators interested in experimentation and utilization of digital communication modes over radio. The software will primarily include NBEMS (Narrow-Band Emergency Messaging System) software and other packages for reliable digital communications on the ham bands (Multipsk, Ham Radio Deluxe (HRD)). <br /><br />The group will be moderated and can be found at:<br /><br />http://groups.yahoo.com/group/wa-digital/<br /><br />TO JOIN Send an email to black@nwfirst.com with your request and I'll send back an email with the invitation. <br /><br />The group is modeled after the Pennsylvania group at:<br />http://www.pa-sitrep.com/NBEMS/index.html<br /><br />Please start with their site to download the NBEMS software, get the MACROS and other supporting files and installation instructions. Good job Pennsylvania!<br /><br />For radio operators in the Seattle Area, we plan to have weekly nets to test and practice with specific modes on both HF and VHF/UHF. For the Summer of 2009 we are meeting on the PSRG Repeater, 146.96 output with a -600khz shift and an access tone of 103.5hz. The net is at 8:00pm on Wednesday evenings. Please check the blog posts at http://www.educationalradionet.blogspot.com/ for the preparation prior to each week's net. Usually, you will need to download some software or configure your station in a particular way to decode the transmissions for the evening.<br /><br />The first motivation for joining would be the diagrams that are included with the step by step instructions for downloading the software are in the Files section of the group. They are the same as the ones on the PA-sitrep site. As soon as I'm able, I'll get the files up there for the software as well as the documentation.<br /><br />I look forward to seeing you on the waterfall!<br /><br />C. W. Black - WR5J<br />West Seattle, Washington<br />black at nwfirst dot comWR5Jhttp://www.blogger.com/profile/16316513702643319581noreply@blogger.com0tag:blogger.com,1999:blog-4632435085083780021.post-10443672675940769402009-06-09T20:13:00.000-07:002009-06-09T21:45:22.283-07:00Session 2 - Summer Digital Series - FLDIGI Setup<meta equiv="Content-Type" content="text/html; charset=utf-8"><meta name="ProgId" content="Word.Document"><meta name="Generator" content="Microsoft Word 9"><meta name="Originator" content="Microsoft Word 9"><link rel="File-List" href="file:///C:/DOCUME%7E1/ADMINI%7E1/LOCALS%7E1/Temp/msoclip1/01/clip_filelist.xml"><link rel="Edit-Time-Data" href="file:///C:/DOCUME%7E1/ADMINI%7E1/LOCALS%7E1/Temp/msoclip1/01/clip_editdata.mso"><!--[if !mso]> <style> v\:* {behavior:url(#default#VML);} o\:* {behavior:url(#default#VML);} w\:* {behavior:url(#default#VML);} .shape {behavior:url(#default#VML);} </style> <![endif]--><!--[if gte mso 9]><xml> <w:worddocument> <w:view>Normal</w:View> <w:zoom>0</w:Zoom> <w:donotoptimizeforbrowser/> </w:WordDocument> </xml><![endif]--><style> <!-- /* Font Definitions */ @font-face {font-family:Wingdings; panose-1:5 0 0 0 0 0 0 0 0 0; mso-font-charset:2; mso-generic-font-family:auto; mso-font-pitch:variable; mso-font-signature:0 268435456 0 0 -2147483648 0;} /* Style Definitions */ p.MsoNormal, li.MsoNormal, div.MsoNormal {mso-style-parent:""; margin:0in; margin-bottom:.0001pt; mso-pagination:widow-orphan; font-size:12.0pt; font-family:"Times New Roman"; mso-fareast-font-family:"Times New Roman";} h1 {mso-style-next:Normal; margin-top:12.0pt; margin-right:0in; margin-bottom:3.0pt; margin-left:0in; mso-pagination:widow-orphan; page-break-after:avoid; mso-outline-level:1; font-size:16.0pt; font-family:Arial; mso-font-kerning:16.0pt; font-weight:bold;} h2 {margin-right:0in; mso-margin-top-alt:auto; mso-margin-bottom-alt:auto; margin-left:0in; mso-pagination:widow-orphan; mso-outline-level:2; font-size:18.0pt; font-family:"Times New Roman"; font-weight:bold;} h3 {mso-style-next:Normal; margin-top:12.0pt; margin-right:0in; margin-bottom:3.0pt; margin-left:0in; mso-pagination:widow-orphan; page-break-after:avoid; mso-outline-level:3; font-size:13.0pt; font-family:Arial; font-weight:bold;} a:link, span.MsoHyperlink {color:blue; text-decoration:underline; text-underline:single;} a:visited, span.MsoHyperlinkFollowed {color:purple; text-decoration:underline; text-underline:single;} p {margin-right:0in; mso-margin-top-alt:auto; mso-margin-bottom-alt:auto; margin-left:0in; mso-pagination:widow-orphan; font-size:12.0pt; font-family:"Times New Roman"; mso-fareast-font-family:"Times New Roman";} @page Section1 {size:8.5in 11.0in; margin:1.0in 1.25in 1.0in 1.25in; mso-header-margin:.5in; mso-footer-margin:.5in; mso-paper-source:0;} div.Section1 {page:Section1;} /* List Definitions */ @list l0 {mso-list-id:399789810; mso-list-type:hybrid; mso-list-template-ids:1972949820 672017848 67698691 67698693 67698689 67698691 67698693 67698689 67698691 67698693;} @list l0:level1 {mso-level-start-at:0; mso-level-number-format:bullet; mso-level-text:-; mso-level-tab-stop:.5in; mso-level-number-position:left; text-indent:-.25in; font-family:"Times New Roman"; mso-fareast-font-family:"Times New Roman";} ol {margin-bottom:0in;} ul {margin-bottom:0in;} --> </style> <p><b style=""><span style="font-size: 16pt;">QST de WR5J – For the Educational Radio Net – Curt in Seattle<o:p></o:p></span></b></p> <p><b style=""><span style="font-size: 16pt;">Here is the second post of the Summer Digital Series for Seattle hams interested in trying out some digital modes over the next several weeks of the coming summer.<o:p></o:p></span></b></p> <p><b style=""><span style="font-size: 16pt;">This post is intended to provide step by step instructions for the download and setup of the FLDIGI software as part of the NBEMS suite.<span style=""> </span>For questions contact Curt at <a href="mailto:black@nwfirst.com">black@nwfirst.com</a> and put SUMMER DIGITAL somewhere in the subject line,<o:p></o:p></span></b></p> <p><b style=""><span style="font-size: 16pt;">Thanks es vy 73 de WR5J<o:p></o:p></span></b></p> <p><b style=""><span style="font-size: 16pt;">Introduction:<o:p></o:p></span></b></p> <p>The purpose of this file is to help Elmer those interested in NBEMS/FLDIGI to develop standardized procedures and settings for the use of the software. </p> <p>The material in this file was only slightly modified from the information on the Pennsylvania SitRep ARES group website for Western Pennsylvania.<span style=""> </span>A big “Thank You to this group for doing the heavy lifting of assembling and organizing the information.<span style=""> </span>Their original information can be found at <a href="http://www.pa-sitrep.com/NBEMS/index.html">http://www.pa-sitrep.com/NBEMS/index.html</a> </p> <p>The use of the NBEMS software requires nothing more than a laptop or desktop computer and an amateur radio transceiver (even an HT) to send and receive data/text using the NBEMS soundcard-based digital software.</p> <p>This site concentrates on only a few of the primary digital communications modes available within the FLDIGI software package that are best suited to Emergency Communications.</p> <p>A key to promoting the widespread adoption of digital communications is to keep the protocols as simple as possible and providing means of conducting digital communications with the use of equipment and transceivers that are already commonly used.</p> <p>The NBEMS/FLDIGI software is the perfect package for digital emergency communications because it is:</p> <p style="margin-left: 0.5in; text-indent: -0.25in;"><!--[if !supportLists]-->-<span style="font-family: "Times New Roman"; font-style: normal; font-variant: normal; font-weight: normal; font-size: 7pt; line-height: normal; font-size-adjust: none; font-stretch: normal;"> </span><!--[endif]-->FREE!
<br />- Easy to configure
<br />- Easy to use
<br />- Easy to modify and standardize
<br />- Works on Windows XP, Windows Vista, Apple and Linux systems
<br />- Usable without the need for additional/complex/expensive hardware</p> <p><b style=""><span style="font-size: 16pt;">Step 1, Get the Software:<o:p></o:p></span></b></p> <p>Here is the link to the NBEMS/FLDIGI Software Download:</p> <p><a href="http://www.w1hkj.com/NBEMS/index.html" target="blank">NBEMS/FLDIGI Software Download</a></p> <p>Make sure you select the proper operating system</p> <p>- "win" is for windows XP
<br />- "winV" is for windows Vista </p> <p>When you click on the link for the appropriate download, you should be prompted to either "Open" or "Save" the program. Select "Save".</p> <p>Click "Next" which lets you select the directory where you want to save the program on your computer. Select the directory for desktop or another directory (make sure you note which directory you save in) then click save.<span style=""> </span>I usually select a download directory so I can archive these files as downloaded.<span style=""> </span>This way, even if the internet is unavailable, I can access the files, possibly move them to a thumbdrive, and easily set up a new installation with the software.<span style=""> </span>Similarly, in the sprit of preparedness, I like to store the files unzipped in a sub-directory, named, “extracted” to avoid any problems with that step. That way you can be certain you have the files and versions you want.</p> <p>An alternate site for download of the software and its help file is <a href="http://www.w1hkj.com/Downloads.html">http://www.w1hkj.com/Downloads.html</a><span style=""> </span>This site may have updated versions a little ahead of the PA-SitRep group and may be worth checking from time to time.<span style=""> </span>It is also the direct source for the Linux and Apple (OS X) versions of the software.</p> <p><b style=""><span style="font-size: 16pt;">Step 2:<span style=""> </span>Installation<o:p></o:p></span></b></p> <p><b>FIRST!</b> - Be sure you have only one copy of cygwin1.dll (the one that came in your zipped file) on your computer.</p> <p><b><u>WindowsXP users:</u></b></p> <p>- Single right click on the "Start" button on the bottom left corner of your desktop.
<br />- Arrow up and single left click "Explore". This opens your entire computer file directory.
<br />- Single right click on your computer's root directory ( usually Local Disc (C:) )
<br />- Arrow down and single left click on "Search".
<br />- In the "All or part of the file name" search box, type cygwin1.dll then click "Search".
<br />- After the search is complete, single right click on the instances of cygwin1.dll <b>(with the exception of the one in your FLDIGI file folder)</b> then arrow down and left click delete. Repeat this for each instance of this file with the exception of the one in your FLDIGI file folder.</p> <p><b><u>Vista users:</u></b></p> <p>- Single right click on the "Start" button on the bottom left corner of your desktop.
<br />- Arrow up and single left click "Explore". This opens your entire computer file directory.
<br />- Single left click on your computer's root directory ( usually Local Disc (C:) )
<br />- In the "search" box in the upper right hand corner of the window, type cygwin1.dll
<br />- Single right click on the instances of cygwin1.dll <b>(with the exception of the one in your FLDIGI file folder)</b> then arrow down and left click delete. Repeat this for each instance of this file with the exception of the one in your FLDIGI file folder.</p> <p><b>Now you are ready to install FLDIGI.</b></p> <p>Go to the desktop (or the directory where you saved the NBEMS/FLDIGI download file) and double click the FLDIGI file icon.</p> <p>This will open up the file folder, which is in a compressed .zip format.</p> <p><b>If running WindowsXP:</b></p> <p>- Click "file" at the top right side of the current window, then click "Extract All". This opens an extraction wizard.
<br />- Click "Next", then click "Browse" and select the directory where you would like the NBEMS/FLDIGI file folder to reside then click "Next". The window should now say that the files were extracted properly.
<br />- Make sure the box marked "Show Extracted Files" is checked, then click "Finish".
<br />- Double click on the FLDIGI folder icon.
<br />- Now single right click on fldigi.exe, arrow down and single left click on "Create Shortcut". A new file will appear in the folder that says "Shortcut to fldigi.exe".
<br />- Single right click on that folder, arrow down and single left click on "Cut".
<br />- Close all open windows, then single right click on your desktop, arrow down and single left click on "paste".
<br />- You should now have a shortcut icon to FLDIGI on your desktop.</p> <p><b>If running Vista:</b></p> <p>- Single left click "Extract all files" from the selections along the top of the current window, then click "Extract All".
<br />- Single left click "Browse" and select the directory where you would like the NBEMS/FLDIGI file folder to reside. Make sure the box marked "Show Extracted Files" is checked, then click "Extract".
<br />- Double click on the FLDIGI folder icon.
<br />- Now single right click on fldigi.exe, arrow down and single left click on "Create Shortcut". A new file will appear in the folder that says "Shortcut to fldigi.exe".
<br />- Single right click on that folder, arrow down and single left click on "Cut".
<br />- Close all open windows, then single right click on your desktop, arrow down and single left click on "paste".
<br />- You should now have a shortcut icon to FLDIGI on your desktop.</p> <p><b style=""><span style="font-size: 16pt;">Step 3, Configuration and Setup:<o:p></o:p></span></b></p> <p>Double click your FLDIGI desktop icon. If you have any errors or the program closes, please see the first item in Step 2, above about the cygwin1.dll file</p> <p>1) Click Configure, arrow down to defaults, arrow over and click Operator. Then enter the appropriate information, click Save Config, then click close.<span style=""> </span>The specific layout of the windows has changed since the figures shown below for FLDIGI 3.03, but the general approach to setup is the same. <meta equiv="Content-Type" content="text/html; charset=utf-8"><meta name="ProgId" content="Word.Document"><meta name="Generator" content="Microsoft Word 9"><meta name="Originator" content="Microsoft Word 9"><link rel="File-List" href="file:///C:/DOCUME%7E1/ADMINI%7E1/LOCALS%7E1/Temp/msoclip1/01/clip_filelist.xml"><link rel="Edit-Time-Data" href="file:///C:/DOCUME%7E1/ADMINI%7E1/LOCALS%7E1/Temp/msoclip1/01/clip_editdata.mso"><link rel="OLE-Object-Data" href="file:///C:/DOCUME%7E1/ADMINI%7E1/LOCALS%7E1/Temp/msoclip1/01/clip_oledata.mso"><!--[if !mso]> <style> v\:* {behavior:url(#default#VML);} o\:* {behavior:url(#default#VML);} w\:* {behavior:url(#default#VML);} .shape {behavior:url(#default#VML);} </style> <![endif]--><!--[if gte mso 9]><xml> <w:worddocument> <w:view>Normal</w:View> <w:zoom>0</w:Zoom> <w:donotoptimizeforbrowser/> </w:WordDocument> </xml><![endif]--><style> <!-- /* Font Definitions */ @font-face {font-family:Wingdings; panose-1:5 0 0 0 0 0 0 0 0 0; mso-font-charset:2; mso-generic-font-family:auto; mso-font-pitch:variable; mso-font-signature:0 268435456 0 0 -2147483648 0;} /* Style Definitions */ p.MsoNormal, li.MsoNormal, div.MsoNormal {mso-style-parent:""; margin:0in; margin-bottom:.0001pt; mso-pagination:widow-orphan; font-size:12.0pt; font-family:"Times New Roman"; mso-fareast-font-family:"Times New Roman";} h1 {mso-style-next:Normal; margin-top:12.0pt; margin-right:0in; margin-bottom:3.0pt; margin-left:0in; mso-pagination:widow-orphan; page-break-after:avoid; mso-outline-level:1; font-size:16.0pt; font-family:Arial; mso-font-kerning:16.0pt; font-weight:bold;} h2 {margin-right:0in; mso-margin-top-alt:auto; mso-margin-bottom-alt:auto; margin-left:0in; mso-pagination:widow-orphan; mso-outline-level:2; font-size:18.0pt; font-family:"Times New Roman"; font-weight:bold;} h3 {mso-style-next:Normal; margin-top:12.0pt; margin-right:0in; margin-bottom:3.0pt; margin-left:0in; mso-pagination:widow-orphan; page-break-after:avoid; mso-outline-level:3; font-size:13.0pt; font-family:Arial; font-weight:bold;} a:link, span.MsoHyperlink {color:blue; text-decoration:underline; text-underline:single;} a:visited, span.MsoHyperlinkFollowed {color:purple; text-decoration:underline; text-underline:single;} p {margin-right:0in; mso-margin-top-alt:auto; mso-margin-bottom-alt:auto; margin-left:0in; mso-pagination:widow-orphan; font-size:12.0pt; font-family:"Times New Roman"; mso-fareast-font-family:"Times New Roman";} @page Section1 {size:8.5in 11.0in; margin:1.0in 1.25in 1.0in 1.25in; mso-header-margin:.5in; mso-footer-margin:.5in; mso-paper-source:0;} div.Section1 {page:Section1;} /* List Definitions */ @list l0 {mso-list-id:399789810; mso-list-type:hybrid; mso-list-template-ids:1972949820 672017848 67698691 67698693 67698689 67698691 67698693 67698689 67698691 67698693;} @list l0:level1 {mso-level-start-at:0; mso-level-number-format:bullet; mso-level-text:-; mso-level-tab-stop:.5in; mso-level-number-position:left; text-indent:-.25in; font-family:"Times New Roman"; mso-fareast-font-family:"Times New Roman";} ol {margin-bottom:0in;} ul {margin-bottom:0in;} --> </style> </p><p><!--[if !supportEmptyParas]--> <!--[endif]--><o:p></o:p></p> <span style="font-size: 12pt; font-family: "Times New Roman";"><!--[if gte vml 1]><v:shapetype id="_x0000_t75" coordsize="21600,21600" spt="75" preferrelative="t" path="m@4@5l@4@11@9@11@9@5xe" filled="f" stroked="f"> <v:stroke joinstyle="miter"> <v:formulas> <v:f eqn="if lineDrawn pixelLineWidth 0"> <v:f eqn="sum @0 1 0"> <v:f eqn="sum 0 0 @1"> <v:f eqn="prod @2 1 2"> <v:f eqn="prod @3 21600 pixelWidth"> <v:f eqn="prod @3 21600 pixelHeight"> <v:f eqn="sum @0 0 1"> <v:f eqn="prod @6 1 2"> <v:f eqn="prod @7 21600 pixelWidth"> <v:f eqn="sum @8 21600 0"> <v:f eqn="prod @7 21600 pixelHeight"> <v:f eqn="sum @10 21600 0"> </v:formulas> <v:path extrusionok="f" gradientshapeok="t" connecttype="rect"> <o:lock ext="edit" aspectratio="t"> </v:shapetype><v:shape id="_x0000_i1025" type="#_x0000_t75" alt="" style="'width:514.5pt;" ole=""> <v:imagedata src="file:///C:/DOCUME~1/ADMINI~1/LOCALS~1/Temp/msoclip1/01/clip_image001.wmz" title=""> </v:shape><![endif]--><!--[if !vml]--><img style="width: 674px; height: 349px;" src="file:///C:/DOCUME%7E1/ADMINI%7E1/LOCALS%7E1/Temp/msoclip1/01/clip_image002.gif" shapes="_x0000_i1025" /><!--[endif]--><!--[if gte mso 9]><xml> <o:oleobject type="Embed" progid="Word.Picture.8" shapeid="_x0000_i1025" drawaspect="Content" objectid="_1306085132"> </o:OLEObject> </xml><![endif]--></span> <meta equiv="Content-Type" content="text/html; charset=utf-8"><meta name="ProgId" content="Word.Document"><meta name="Generator" content="Microsoft Word 9"><meta name="Originator" content="Microsoft Word 9"><link rel="File-List" href="file:///C:/DOCUME%7E1/ADMINI%7E1/LOCALS%7E1/Temp/msoclip1/01/clip_filelist.xml"><link rel="Edit-Time-Data" href="file:///C:/DOCUME%7E1/ADMINI%7E1/LOCALS%7E1/Temp/msoclip1/01/clip_editdata.mso"><!--[if !mso]> <style> v\:* {behavior:url(#default#VML);} o\:* {behavior:url(#default#VML);} w\:* {behavior:url(#default#VML);} .shape {behavior:url(#default#VML);} </style> <![endif]--><!--[if gte mso 9]><xml> <w:worddocument> <w:view>Normal</w:View> <w:zoom>0</w:Zoom> <w:donotoptimizeforbrowser/> </w:WordDocument> </xml><![endif]--><style> <!-- /* Font Definitions */ @font-face {font-family:Wingdings; panose-1:5 0 0 0 0 0 0 0 0 0; mso-font-charset:2; mso-generic-font-family:auto; mso-font-pitch:variable; mso-font-signature:0 268435456 0 0 -2147483648 0;} /* Style Definitions */ p.MsoNormal, li.MsoNormal, div.MsoNormal {mso-style-parent:""; margin:0in; margin-bottom:.0001pt; mso-pagination:widow-orphan; font-size:12.0pt; font-family:"Times New Roman"; mso-fareast-font-family:"Times New Roman";} h1 {mso-style-next:Normal; margin-top:12.0pt; margin-right:0in; margin-bottom:3.0pt; margin-left:0in; mso-pagination:widow-orphan; page-break-after:avoid; mso-outline-level:1; font-size:16.0pt; font-family:Arial; mso-font-kerning:16.0pt; font-weight:bold;} h2 {margin-right:0in; mso-margin-top-alt:auto; mso-margin-bottom-alt:auto; margin-left:0in; mso-pagination:widow-orphan; mso-outline-level:2; font-size:18.0pt; font-family:"Times New Roman"; font-weight:bold;} h3 {mso-style-next:Normal; margin-top:12.0pt; margin-right:0in; margin-bottom:3.0pt; margin-left:0in; mso-pagination:widow-orphan; page-break-after:avoid; mso-outline-level:3; font-size:13.0pt; font-family:Arial; font-weight:bold;} a:link, span.MsoHyperlink {color:blue; text-decoration:underline; text-underline:single;} a:visited, span.MsoHyperlinkFollowed {color:purple; text-decoration:underline; text-underline:single;} p {margin-right:0in; mso-margin-top-alt:auto; mso-margin-bottom-alt:auto; margin-left:0in; mso-pagination:widow-orphan; font-size:12.0pt; font-family:"Times New Roman"; mso-fareast-font-family:"Times New Roman";} @page Section1 {size:8.5in 11.0in; margin:1.0in 1.25in 1.0in 1.25in; mso-header-margin:.5in; mso-footer-margin:.5in; mso-paper-source:0;} div.Section1 {page:Section1;} /* List Definitions */ @list l0 {mso-list-id:399789810; mso-list-type:hybrid; mso-list-template-ids:1972949820 672017848 67698691 67698693 67698689 67698691 67698693 67698689 67698691 67698693;} @list l0:level1 {mso-level-start-at:0; mso-level-number-format:bullet; mso-level-text:-; mso-level-tab-stop:.5in; mso-level-number-position:left; text-indent:-.25in; font-family:"Times New Roman"; mso-fareast-font-family:"Times New Roman";} ol {margin-bottom:0in;} ul {margin-bottom:0in;} --> </style><meta equiv="Content-Type" content="text/html; charset=utf-8"><meta name="ProgId" content="Word.Document"><meta name="Generator" content="Microsoft Word 9"><meta name="Originator" content="Microsoft Word 9"><link rel="File-List" href="file:///C:/DOCUME%7E1/ADMINI%7E1/LOCALS%7E1/Temp/msoclip1/01/clip_filelist.xml"><link rel="Edit-Time-Data" href="file:///C:/DOCUME%7E1/ADMINI%7E1/LOCALS%7E1/Temp/msoclip1/01/clip_editdata.mso"><!--[if !mso]> <style> v\:* {behavior:url(#default#VML);} o\:* {behavior:url(#default#VML);} w\:* {behavior:url(#default#VML);} .shape {behavior:url(#default#VML);} </style> <![endif]--><!--[if gte mso 9]><xml> <w:worddocument> <w:view>Normal</w:View> <w:zoom>0</w:Zoom> <w:donotoptimizeforbrowser/> </w:WordDocument> </xml><![endif]--><style> <!-- /* Font Definitions */ @font-face {font-family:Wingdings; panose-1:5 0 0 0 0 0 0 0 0 0; mso-font-charset:2; mso-generic-font-family:auto; mso-font-pitch:variable; mso-font-signature:0 268435456 0 0 -2147483648 0;} /* Style Definitions */ p.MsoNormal, li.MsoNormal, div.MsoNormal {mso-style-parent:""; margin:0in; margin-bottom:.0001pt; mso-pagination:widow-orphan; font-size:12.0pt; font-family:"Times New Roman"; mso-fareast-font-family:"Times New Roman";} h1 {mso-style-next:Normal; margin-top:12.0pt; margin-right:0in; margin-bottom:3.0pt; margin-left:0in; mso-pagination:widow-orphan; page-break-after:avoid; mso-outline-level:1; font-size:16.0pt; font-family:Arial; mso-font-kerning:16.0pt; font-weight:bold;} h2 {margin-right:0in; mso-margin-top-alt:auto; mso-margin-bottom-alt:auto; margin-left:0in; mso-pagination:widow-orphan; mso-outline-level:2; font-size:18.0pt; font-family:"Times New Roman"; font-weight:bold;} h3 {mso-style-next:Normal; margin-top:12.0pt; margin-right:0in; margin-bottom:3.0pt; margin-left:0in; mso-pagination:widow-orphan; page-break-after:avoid; mso-outline-level:3; font-size:13.0pt; font-family:Arial; font-weight:bold;} a:link, span.MsoHyperlink {color:blue; text-decoration:underline; text-underline:single;} a:visited, span.MsoHyperlinkFollowed {color:purple; text-decoration:underline; text-underline:single;} p {margin-right:0in; mso-margin-top-alt:auto; mso-margin-bottom-alt:auto; margin-left:0in; mso-pagination:widow-orphan; font-size:12.0pt; font-family:"Times New Roman"; mso-fareast-font-family:"Times New Roman";} @page Section1 {size:8.5in 11.0in; margin:1.0in 1.25in 1.0in 1.25in; mso-header-margin:.5in; mso-footer-margin:.5in; mso-paper-source:0;} div.Section1 {page:Section1;} /* List Definitions */ @list l0 {mso-list-id:399789810; mso-list-type:hybrid; mso-list-template-ids:1972949820 672017848 67698691 67698693 67698689 67698691 67698693 67698689 67698691 67698693;} @list l0:level1 {mso-level-start-at:0; mso-level-number-format:bullet; mso-level-text:-; mso-level-tab-stop:.5in; mso-level-number-position:left; text-indent:-.25in; font-family:"Times New Roman"; mso-fareast-font-family:"Times New Roman";} ol {margin-bottom:0in;} ul {margin-bottom:0in;} --> </style><meta equiv="Content-Type" content="text/html; charset=utf-8"><meta name="ProgId" content="Word.Document"><meta name="Generator" content="Microsoft Word 9"><meta name="Originator" content="Microsoft Word 9"><link rel="File-List" href="file:///C:/DOCUME%7E1/ADMINI%7E1/LOCALS%7E1/Temp/msoclip1/01/clip_filelist.xml"><link rel="Edit-Time-Data" href="file:///C:/DOCUME%7E1/ADMINI%7E1/LOCALS%7E1/Temp/msoclip1/01/clip_editdata.mso"><link rel="OLE-Object-Data" href="file:///C:/DOCUME%7E1/ADMINI%7E1/LOCALS%7E1/Temp/msoclip1/01/clip_oledata.mso"><!--[if !mso]> <style> v\:* {behavior:url(#default#VML);} o\:* {behavior:url(#default#VML);} w\:* {behavior:url(#default#VML);} .shape {behavior:url(#default#VML);} </style> <![endif]--><!--[if gte mso 9]><xml> <w:worddocument> <w:view>Normal</w:View> <w:zoom>0</w:Zoom> <w:donotoptimizeforbrowser/> </w:WordDocument> </xml><![endif]--><style> <!-- /* Font Definitions */ @font-face {font-family:Wingdings; panose-1:5 0 0 0 0 0 0 0 0 0; mso-font-charset:2; mso-generic-font-family:auto; mso-font-pitch:variable; mso-font-signature:0 268435456 0 0 -2147483648 0;} /* Style Definitions */ p.MsoNormal, li.MsoNormal, div.MsoNormal {mso-style-parent:""; margin:0in; margin-bottom:.0001pt; mso-pagination:widow-orphan; font-size:12.0pt; font-family:"Times New Roman"; mso-fareast-font-family:"Times New Roman";} h1 {mso-style-next:Normal; margin-top:12.0pt; margin-right:0in; margin-bottom:3.0pt; margin-left:0in; mso-pagination:widow-orphan; page-break-after:avoid; mso-outline-level:1; font-size:16.0pt; font-family:Arial; mso-font-kerning:16.0pt; font-weight:bold;} h2 {margin-right:0in; mso-margin-top-alt:auto; mso-margin-bottom-alt:auto; margin-left:0in; mso-pagination:widow-orphan; mso-outline-level:2; font-size:18.0pt; font-family:"Times New Roman"; font-weight:bold;} h3 {mso-style-next:Normal; margin-top:12.0pt; margin-right:0in; margin-bottom:3.0pt; margin-left:0in; mso-pagination:widow-orphan; page-break-after:avoid; mso-outline-level:3; font-size:13.0pt; font-family:Arial; font-weight:bold;} a:link, span.MsoHyperlink {color:blue; text-decoration:underline; text-underline:single;} a:visited, span.MsoHyperlinkFollowed {color:purple; text-decoration:underline; text-underline:single;} p {margin-right:0in; mso-margin-top-alt:auto; mso-margin-bottom-alt:auto; margin-left:0in; mso-pagination:widow-orphan; font-size:12.0pt; font-family:"Times New Roman"; mso-fareast-font-family:"Times New Roman";} @page Section1 {size:8.5in 11.0in; margin:1.0in 1.25in 1.0in 1.25in; mso-header-margin:.5in; mso-footer-margin:.5in; mso-paper-source:0;} div.Section1 {page:Section1;} /* List Definitions */ @list l0 {mso-list-id:399789810; mso-list-type:hybrid; mso-list-template-ids:1972949820 672017848 67698691 67698693 67698689 67698691 67698693 67698689 67698691 67698693;} @list l0:level1 {mso-level-start-at:0; mso-level-number-format:bullet; mso-level-text:-; mso-level-tab-stop:.5in; mso-level-number-position:left; text-indent:-.25in; font-family:"Times New Roman"; mso-fareast-font-family:"Times New Roman";} ol {margin-bottom:0in;} ul {margin-bottom:0in;} --> </style><img src="file:///C:/DOCUME%7E1/ADMINI%7E1/LOCALS%7E1/Temp/moz-screenshot.jpg" alt="" /><p></p> <p><!--[if gte vml 1]><v:shapetype id="_x0000_t75" coordsize="21600,21600" spt="75" preferrelative="t" path="m@4@5l@4@11@9@11@9@5xe" filled="f" stroked="f"> <v:stroke joinstyle="miter"> <v:formulas> <v:f eqn="if lineDrawn pixelLineWidth 0"> <v:f eqn="sum @0 1 0"> <v:f eqn="sum 0 0 @1"> <v:f eqn="prod @2 1 2"> <v:f eqn="prod @3 21600 pixelWidth"> <v:f eqn="prod @3 21600 pixelHeight"> <v:f eqn="sum @0 0 1"> <v:f eqn="prod @6 1 2"> <v:f eqn="prod @7 21600 pixelWidth"> <v:f eqn="sum @8 21600 0"> <v:f eqn="prod @7 21600 pixelHeight"> <v:f eqn="sum @10 21600 0"> </v:formulas> <v:path extrusionok="f" gradientshapeok="t" connecttype="rect"> <o:lock ext="edit" aspectratio="t"> </v:shapetype><v:shape id="_x0000_i1027" type="#_x0000_t75" alt="" style="'width:515.25pt;"> <v:imagedata src="file:///C:/DOCUME~1/ADMINI~1/LOCALS~1/Temp/msoclip1/01/clip_image001.jpg" href="http://www.pa-sitrep.com/NBEMS/fldigi_config1.jpg"> </v:shape><![endif]--><!--[if !vml]--><meta equiv="Content-Type" content="text/html; charset=utf-8"><meta name="ProgId" content="Word.Document"><meta name="Generator" content="Microsoft Word 9"><meta name="Originator" content="Microsoft Word 9"><link rel="File-List" href="file:///C:/DOCUME%7E1/ADMINI%7E1/LOCALS%7E1/Temp/msoclip1/01/clip_filelist.xml"><link rel="Edit-Time-Data" href="file:///C:/DOCUME%7E1/ADMINI%7E1/LOCALS%7E1/Temp/msoclip1/01/clip_editdata.mso"><!--[if !mso]> <style> v\:* {behavior:url(#default#VML);} o\:* {behavior:url(#default#VML);} w\:* {behavior:url(#default#VML);} .shape {behavior:url(#default#VML);} </style> <![endif]--><!--[if gte mso 9]><xml> <w:worddocument> <w:view>Normal</w:View> <w:zoom>0</w:Zoom> <w:donotoptimizeforbrowser/> </w:WordDocument> </xml><![endif]--><style> <!-- /* Font Definitions */ @font-face {font-family:Wingdings; panose-1:5 0 0 0 0 0 0 0 0 0; mso-font-charset:2; mso-generic-font-family:auto; mso-font-pitch:variable; mso-font-signature:0 268435456 0 0 -2147483648 0;} /* Style Definitions */ p.MsoNormal, li.MsoNormal, div.MsoNormal {mso-style-parent:""; margin:0in; margin-bottom:.0001pt; mso-pagination:widow-orphan; font-size:12.0pt; font-family:"Times New Roman"; mso-fareast-font-family:"Times New Roman";} h1 {mso-style-next:Normal; margin-top:12.0pt; margin-right:0in; margin-bottom:3.0pt; margin-left:0in; mso-pagination:widow-orphan; page-break-after:avoid; mso-outline-level:1; font-size:16.0pt; font-family:Arial; mso-font-kerning:16.0pt; font-weight:bold;} h2 {margin-right:0in; mso-margin-top-alt:auto; mso-margin-bottom-alt:auto; margin-left:0in; mso-pagination:widow-orphan; mso-outline-level:2; font-size:18.0pt; font-family:"Times New Roman"; font-weight:bold;} h3 {mso-style-next:Normal; margin-top:12.0pt; margin-right:0in; margin-bottom:3.0pt; margin-left:0in; mso-pagination:widow-orphan; page-break-after:avoid; mso-outline-level:3; font-size:13.0pt; font-family:Arial; font-weight:bold;} a:link, span.MsoHyperlink {color:blue; text-decoration:underline; text-underline:single;} a:visited, span.MsoHyperlinkFollowed {color:purple; text-decoration:underline; text-underline:single;} p {margin-right:0in; mso-margin-top-alt:auto; mso-margin-bottom-alt:auto; margin-left:0in; mso-pagination:widow-orphan; font-size:12.0pt; font-family:"Times New Roman"; mso-fareast-font-family:"Times New Roman";} @page Section1 {size:8.5in 11.0in; margin:1.0in 1.25in 1.0in 1.25in; mso-header-margin:.5in; mso-footer-margin:.5in; mso-paper-source:0;} div.Section1 {page:Section1;} /* List Definitions */ @list l0 {mso-list-id:399789810; mso-list-type:hybrid; mso-list-template-ids:1972949820 672017848 67698691 67698693 67698689 67698691 67698693 67698689 67698691 67698693;} @list l0:level1 {mso-level-start-at:0; mso-level-number-format:bullet; mso-level-text:-; mso-level-tab-stop:.5in; mso-level-number-position:left; text-indent:-.25in; font-family:"Times New Roman"; mso-fareast-font-family:"Times New Roman";} ol {margin-bottom:0in;} ul {margin-bottom:0in;} --> </style><span style="font-size: 12pt; font-family: "Times New Roman";"><!--[if gte vml 1]><v:shapetype id="_x0000_t75" coordsize="21600,21600" spt="75" preferrelative="t" path="m@4@5l@4@11@9@11@9@5xe" filled="f" stroked="f"> <v:stroke joinstyle="miter"> <v:formulas> <v:f eqn="if lineDrawn pixelLineWidth 0"> <v:f eqn="sum @0 1 0"> <v:f eqn="sum 0 0 @1"> <v:f eqn="prod @2 1 2"> <v:f eqn="prod @3 21600 pixelWidth"> <v:f eqn="prod @3 21600 pixelHeight"> <v:f eqn="sum @0 0 1"> <v:f eqn="prod @6 1 2"> <v:f eqn="prod @7 21600 pixelWidth"> <v:f eqn="sum @8 21600 0"> <v:f eqn="prod @7 21600 pixelHeight"> <v:f eqn="sum @10 21600 0"> </v:formulas> <v:path extrusionok="f" gradientshapeok="t" connecttype="rect"> <o:lock ext="edit" aspectratio="t"> </v:shapetype><v:shape id="_x0000_i1025" type="#_x0000_t75" alt="" style="'width:515.25pt;"> <v:imagedata src="file:///C:/DOCUME~1/ADMINI~1/LOCALS~1/Temp/msoclip1/01/clip_image001.jpg" href="http://www.pa-sitrep.com/NBEMS/fldigi_config1.jpg"> </v:shape><![endif]--><!--[if !vml]--><!--[endif]--></span><!--[endif]--></p> <p>2) Click Configure, arrow down to defaults, arrow over and click Waterfall. Click the left arrow on the low cutoff box until the figure is at 50. Click Save Config, then close.</p> <p><!--[if gte vml 1]><v:shape id="_x0000_i1028" type="#_x0000_t75" alt="" style="'width:7in;height:257.25pt'"> <v:imagedata src="file:///C:/DOCUME~1/ADMINI~1/LOCALS~1/Temp/msoclip1/01/clip_image002.jpg" href="http://www.pa-sitrep.com/NBEMS/fldigi_config2.jpg"> </v:shape><![endif]--><!--[if !vml]-->
<br /><!--[endif]--></p> <p>3) Click Configure, arrow down to defaults, arrow over and click Video. Uncheck small font, video text - type "MT631K-L", video width - 4, check View Xmit Signal, then click Save Config and close.</p> <p><!--[if gte vml 1]><v:shape id="_x0000_i1029" type="#_x0000_t75" alt="" style="'width:503.25pt;height:254.25pt'"> <v:imagedata src="file:///C:/DOCUME~1/ADMINI~1/LOCALS~1/Temp/msoclip1/01/clip_image003.jpg" href="http://www.pa-sitrep.com/NBEMS/fldigi_config3.jpg"> </v:shape><![endif]--><!--[if !vml]--><img src="file:///C:/DOCUME%7E1/ADMINI%7E1/LOCALS%7E1/Temp/msoclip1/01/clip_image003.jpg" shapes="_x0000_i1029" width="671" border="0" height="339" /><!--[endif]--></p> <p>4) Click Configure, arrow down to defaults, arrow over and click Sound Card. Select the appropriate sound card for capture and playback under port audio for the sound card that you will be transmitting with. Click Save Config, then close.<span style=""> </span></p> <p>In Seattle we are starting with <u>acoustic coupling</u> of our radios and computers.<span style=""> </span>For this reason, we will want to set up with the “capture” through the microphone input of the internal soundcard on your computer.<span style=""> </span>“Playback” will be through the speakers by selecting the internal soundcard of your computer.<span style=""> </span>This is different from what is shown below for what we will do later if we install a hardware interface between the computer and the radio.<span style=""> </span></p> <p><!--[if gte vml 1]><v:shape id="_x0000_i1030" type="#_x0000_t75" alt="" style="'width:450pt;height:222.75pt'"> <v:imagedata src="file:///C:/DOCUME~1/ADMINI~1/LOCALS~1/Temp/msoclip1/01/clip_image004.jpg" href="http://www.pa-sitrep.com/NBEMS/fldigi_config4.jpg"> </v:shape><![endif]--><!--[if !vml]--><img src="file:///C:/DOCUME%7E1/ADMINI%7E1/LOCALS%7E1/Temp/msoclip1/01/clip_image005.jpg" shapes="_x0000_i1030" width="600" border="0" height="297" /><!--[endif]--></p> <p>5) Click Configure, arrow down to defaults, arrow over and click Misc. Check Transmit RSID and Wide Search Detector. Make sure Slow CPU is unchecked unless you are operating on a very slow computer.</p> <p><!--[if gte vml 1]><v:shape id="_x0000_i1031" type="#_x0000_t75" alt="" style="'width:500.25pt;height:253.5pt'"> <v:imagedata src="file:///C:/DOCUME~1/ADMINI~1/LOCALS~1/Temp/msoclip1/01/clip_image006.jpg" href="http://www.pa-sitrep.com/NBEMS/fldigi_config5.jpg"> </v:shape><![endif]--><!--[if !vml]--><img src="file:///C:/DOCUME%7E1/ADMINI%7E1/LOCALS%7E1/Temp/msoclip1/01/clip_image006.jpg" shapes="_x0000_i1031" width="667" border="0" height="338" /><!--[endif]--></p> <p>6) On the main screen of FLDIGI, go to the bottom of the screen and set the first waterfall figure to -20, the second figure to 70, and the x setting to x1. Uncheck the sql box on the right bottom of the fldigi window.</p> <p><!--[if gte vml 1]><v:shape id="_x0000_i1032" type="#_x0000_t75" alt="" style="'width:651.75pt;height:94.5pt'"> <v:imagedata src="file:///C:/DOCUME~1/ADMINI~1/LOCALS~1/Temp/msoclip1/01/clip_image007.jpg" href="http://www.pa-sitrep.com/NBEMS/fldigi_config6.jpg"> </v:shape><![endif]--><!--[if !vml]--><img src="file:///C:/DOCUME%7E1/ADMINI%7E1/LOCALS%7E1/Temp/msoclip1/01/clip_image007.jpg" shapes="_x0000_i1032" width="869" border="0" height="126" /><!--[endif]--></p> <h2>Adding the Standardized WPA NBEMS Macro Set</h2> <p class="MsoNormal">1) Go to http://www.pa-sitrep.com/NBEMS/fldigi_macro.htm</p> <p>2) Right click on the link to the macro, arrow down to "Save Target As" and left click.</p> <p>3) You should now see your windows file directory. You will need to click on your profile directory (this will be the name that appears when you start your windows login). Double click on your windows profile name in the directory.</p> <p>4) When you make it to the proper directory, you should see an existing file named "macros". This is the file you will be replacing.</p> <p>5) Left click the save button. A window should come up saying that the file already exists and will ask if you want to replace/overwrite. Click yes.</p> <p>Here is the current WPA Standardized NBEMS/FLDIGI Macro (25-Oct-2008):</p> <p><a href="http://www.pa-sitrep.com/fldigi_files/macros.mdf">NBEMS/FLDIGI macros.mdf</a></p> <p>Right click on the link above, then click "Save Target As", then place the file in the following directory:</p> <p>WindowsXP users save to:
<br />c:\Documents and Settings\urlogin\fldigi.files</p> <p>Vista users save to:
<br />Desktop\urlogin\fldigi.files</p> <p>Replace "urlogin" with your login name when you start your computer.</p> <p>When prompted with the message that this file already exists, select the appropriate option to overwrite or replace the existing file.</p> <div class="MsoNormal" style="text-align: center;" align="center"> <hr size="2" width="100%" align="center"> </div> <p>The primary macro set is indicated with the number 1 in the furthest right button. This is the primary set used during transmit and receive sessions.</p> <p>The number 2 macro set is used for changing to different modes.</p> <p>The number 3 macro set is for the use of MT63 1k Long transmit and receive sessions.</p> <p>Here is a screen shot of the 3 macro sets: <!--[if gte vml 1]><v:shape id="_x0000_i1033" type="#_x0000_t75" alt="" style="'width:495pt;height:60.75pt'"> <v:imagedata src="file:///C:/DOCUME~1/ADMINI~1/LOCALS~1/Temp/msoclip1/01/clip_image008.jpg" href="http://www.pa-sitrep.com/NBEMS/macros.jpg"> </v:shape><![endif]--><!--[if !vml]--><img src="file:///C:/DOCUME%7E1/ADMINI%7E1/LOCALS%7E1/Temp/msoclip1/01/clip_image009.jpg" shapes="_x0000_i1033" width="660" border="0" height="81" /><!--[endif]--></p> <p>To change from one macro set to another while running FLDIGI just click on the number to the far right of the macro line – it will change to 2, then 3 then back to 1 with each mouse click</p> <p><!--[if !supportEmptyParas]--> <!--[endif]--><o:p></o:p></p> <p><!--[if !supportEmptyParas]--> <!--[endif]--><o:p></o:p></p> <p><b style=""><span style="font-size: 16pt;">Step 4, Sound Card Calibration<o:p></o:p></span></b></p> <p>1) Download and save CheckSR.exe to your desktop. This is a small, standalone, application that consist of a single exe file. When you double click on it, once it's saved to your desktop, it provides the capability of analyzing your sound card offsets and gives you the corrections in parts per million (ppm):</p> <p><a href="http://www.pa-sitrep.com/checksr/CheckSR.exe">http://www.pa-sitrep.com/checksr/CheckSR.exe</a></p> <p>2) Open NBEMS/FLDIGI, go to configure, defaults, sound card, audio devices tab and make sure you have the sound card you use for your interface properly selected from the capture and playback drop down choices. For Seattle folk, that will be your internal sound card.<span style=""> </span>Later, if you choose to move to interfaces like the Signalink or Navigator, with their own sound cards inside, we will recalibrate to those external devices.<span style=""> </span>Next click the audio settings tab.</p> <p>3) Under the audio settings tab, you should see a sample rate drop down box for capture and playback. Under each drop down box, select the sample rate that has (native) listed after it and take note of this figure. Click save config, then click save. Close FLDIGI.</p> <p>4) Going back to CheckSR, open the application (if it's not already open, double click on the desktop icon now) and from the drop down boxes for sound card settings, Input and Output, choose the sound card you are using with FLDIGI. Next, select the sample rate from the drop down box in CheckSR for the sample rate that FLDIGI showed as "Native" then click start.</p> <p>5) Let the application run for about 15-20 minutes. You will notice that the numbers will progressively stabilize. After about 15-20 minutes, click stop then write down the resulting figures on input and output for the measurements in Hz and PPM. Keep this record – I keep a little table for each of the hardware interfaces I have as well as each internal soundcard – makes configuring for any laptop, desktop or interface easier… While it might seem counter intuitive, running the application for more than an hour or so seems to produce less accurate values – I don’t know if some internal register or something begins to overflow, but it starts to move to unrealistic numbers with more time.</p> <p>6) Open FLDIGI, go to configure, defaults, sound card and click on the audio settings tab. Enter the PPM figures for RX ppm (CheckSR ppm Input figure) and TX ppm (CheckSR ppm Output figure). If you had a figure that resulted in a minus from CheckSR, enter the PPM setting with the minus symbol followed directly by the figure with no space. Then click save config, then close.</p> <p>Although this procedure does not seem to be necessary for MT63 2k long on FM, it is advisable that anyone using FLDIGI, regardless of modes used, should perform this procedure immediately following setup. Once these calibrations are applied to the software, no changes should ever have to be made again, unless you change your software to radio interface sound card. </p> <p><b style=""><span style="font-size: 16pt;">Step 5<span style=""> </span>First QSO with FLDIGI on BPSK-31<o:p></o:p></span></b></p> <p><b><i>These instructions are assuming that you are using a properly configured sound card interface. Keep in mind that if you do not have a sound card interface, you can plug a simple microphone into your sound card mic jack to monitor received audio from your transceiver speaker, but you will not have automated push to talk in order to transmit.</i></b></p> <p>Double click your FLDIGI desktop icon. If you have any errors or the program closes, please see the first step on the <a href="http://www.pa-sitrep.com/NBEMS/fldigi_instal.htm">installation page</a></p> <p>1) Adjust your TX and RX window sizes by arrowing over the divider between the upper window (received text) and the lower window (transmit text). Left click and hold, then drag the divider up or down. Typically it is better to have the RX (upper window) using about 75% of the overall screen.</p> <p><!--[if gte vml 1]><v:shape id="_x0000_i1034" type="#_x0000_t75" alt="" style="'width:537.75pt;height:387.75pt'"> <v:imagedata src="file:///C:/DOCUME~1/ADMINI~1/LOCALS~1/Temp/msoclip1/01/clip_image010.jpg" href="http://www.pa-sitrep.com/NBEMS/fldigi_started1.jpg"> </v:shape><![endif]--><!--[if !vml]--><img src="file:///C:/DOCUME%7E1/ADMINI%7E1/LOCALS%7E1/Temp/msoclip1/01/clip_image010.jpg" shapes="_x0000_i1034" width="717" border="0" height="517" /><!--[endif]--></p> <p>2) Go to Op Mode at the top of the screen and left click, arrow down to PSK then arrow over to BPSK-31 and left click. This sets you in PSK-31, the most common digital mode you'll find on the HF bands.</p> <p>3) Tune your transceiver to a common PSK31 frequency:
<br />Daytime: 14.070 MHz/USB, 10.140 MHz/USB, 7.070 MHz/USB
<br />Evenings/Night: 3.580 MHz/USB, 7.070 MHz/USB, 10.140 MHz/USB</p> <p>4) As is the case for all digital comms with FLDIGI, make sure all DSP including compression and noise blanker are turned off on your transceiver.</p> <p>5) Arrow over a PSK signal in the waterfall and left click on the signal. You should now see the receive text being decoded in the upper RX window. If you see no text, make sure the squelch box at the bottom right hand corner of the program is unchecked.</p> <p>6) Wait for a station to call CQ. On the received text, arrow over the first character on the Call Sign in the CQ and RIGHT click. This brings up a window that will let you insert the text that you right clicked on into the log. Arrow to Call and left click. You will notice that the call sign has now been inserted into the log.<span style=""> </span>You are now ready to respond to the calling station.</p> <p>7) Left click on the 2nd macro in the 1 set that is labled "ANS CALL/CQ" or hit F2 on your keyboard. You should now be transmiting and you should see that the station call you added in the log is now being sent along with your call sign. At the end of your response, assuming you are using a sound card interface, the rig should automatically go back into receive. At any time if your rig does not return to receive mode, you can pres the esc button on your keyboard to manually abort transmission.</p> <p>8) If your system is configured properly and band conditions are sufficient, the CQ calling station should respond. Typical first exchange is name, location and signal report. </p> <p>9) As you receive the calling station's name and location, you can right click on the given text and insert the information into the log, just as you did in step 6 to insert the call sign into the log. If the location is city and state (two words), highlight both words by left clicking and holding then drag over the desired text, then unclick. You will see that the text is now highlighted and you can right click to insert to the appropriate section of the log.</p> <p>10) To respond with your first information exchange, click on the "exchange" macro or hit F3 on your keyboard. Now you can manually type your information or click the station info macro.</p> <p>11) IT IS IMPORTANT TO NOTE that the exchange and station information macros will not automatically end your transmission, so you will want to click the BTU (Back to you) macro or hit F4 on your keyboard.</p> <p>The symbols displayed on the macro buttons indicate how the macro will function:</p> <p><!--[if gte vml 1]><v:shape id="_x0000_i1035" type="#_x0000_t75" alt="" style="'width:14.25pt;height:9.75pt'"> <v:imagedata src="file:///C:/DOCUME~1/ADMINI~1/LOCALS~1/Temp/msoclip1/01/clip_image011.jpg" href="http://www.pa-sitrep.com/NBEMS/fldigi_start_stop.jpg"> </v:shape><![endif]--><!--[if !vml]--><img src="file:///C:/DOCUME%7E1/ADMINI%7E1/LOCALS%7E1/Temp/msoclip1/01/clip_image011.jpg" shapes="_x0000_i1035" width="19" border="0" height="13" /><!--[endif]-->Indicates auto transmit and auto receive</p> <p><!--[if gte vml 1]><v:shape id="_x0000_i1036" type="#_x0000_t75" alt="" style="'width:14.25pt;height:10.5pt'"> <v:imagedata src="file:///C:/DOCUME~1/ADMINI~1/LOCALS~1/Temp/msoclip1/01/clip_image012.jpg" href="http://www.pa-sitrep.com/NBEMS/fldigi_start.jpg"> </v:shape><![endif]--><!--[if !vml]--><img src="file:///C:/DOCUME%7E1/ADMINI%7E1/LOCALS%7E1/Temp/msoclip1/01/clip_image012.jpg" shapes="_x0000_i1036" width="19" border="0" height="14" /><!--[endif]-->Indicates auto start (you will need to use BTU or manually switch to receive)</p> <p><!--[if gte vml 1]><v:shape id="_x0000_i1037" type="#_x0000_t75" alt="" style="'width:14.25pt;height:10.5pt'"> <v:imagedata src="file:///C:/DOCUME~1/ADMINI~1/LOCALS~1/Temp/msoclip1/01/clip_image013.jpg" href="http://www.pa-sitrep.com/NBEMS/fldigi_stop.jpg"> </v:shape><![endif]--><!--[if !vml]--><img src="file:///C:/DOCUME%7E1/ADMINI%7E1/LOCALS%7E1/Temp/msoclip1/01/clip_image013.jpg" shapes="_x0000_i1037" width="19" border="0" height="14" /><!--[endif]-->Indicates auto receive</p> <p><b style=""><span style="font-size: 16pt;">Step 6 – Try Different Modes – Olivia <o:p></o:p></span></b></p> <p><!--[if !supportEmptyParas]--> <!--[endif]--><o:p></o:p></p> <p>We will be focusing on 3 primary digital communications modes:</p> <h2 style="text-align: center;" align="center"><span style="font-size: 14pt;">MT63 - Olivia - DominoEX<o:p></o:p></span></h2> <p class="MsoNormal">Each mode has it's advantages and disadvantages and the WPA-SitRep group recommendations are based on extensive field testing under varying situations and conditions.</p> <h2><span style="font-size: 14pt;">MT63 2k Long - Local FM Comms<o:p></o:p></span></h2> <p class="MsoNormal">For local portable, mobile and fixed station operations on 2m and 70cm FM (repeater or simplex), MT63 2K long is our primary mode for detailed situation reports and database transmission and has been chosen for the following reasons:</p> <p>- Can be used very effectively without a sound card interface (audio coupling)
<br />- Extremely effective under poor RF conditions
<br />- Extremely accurate decoding (major duplication of data and forward error corrected)
<br />- Very forgiving on sound card tuning and calibration when used on FM
<br />- Excellent for sending larger situation reports or databases</p> <h2><span style="font-size: 14pt;">MT63 1k Long - Regional/Local HF Comms<o:p></o:p></span></h2> <p class="MsoNormal">For regional and local portable, mobile and fixed station operations on HF USB under moderate to good condition, MT63 1K long is our primary mode for detailed situation reports and database transmissions and has been chosen for the following reasons:</p> <p style="margin-left: 0.5in; text-indent: -0.25in;"><!--[if !supportLists]-->-<span style="font-family: "Times New Roman"; font-style: normal; font-variant: normal; font-weight: normal; font-size: 7pt; line-height: normal; font-size-adjust: none; font-stretch: normal;"> </span><!--[endif]-->Very effective under moderate to good RF conditions
<br />- Extremely accurate decoding (major duplication of data and forward error corrected)
<br />- Works extremely well under QRM and QRN conditions - Excellent for sending larger situation reports or databases</p> <p style="margin-left: 0.5in; text-indent: -0.25in;"><!--[if !supportLists]-->-<span style="font-family: "Times New Roman"; font-style: normal; font-variant: normal; font-weight: normal; font-size: 7pt; line-height: normal; font-size-adjust: none; font-stretch: normal;"> </span><!--[endif]--><!--[if !supportEmptyParas]--> <!--[endif]--><o:p></o:p></p> <p>Disadvantages:</p> <p>- Requires fairly accurate tuning
<br />- Does not work well under very poor RF weak signal conditions
<br />- Long decoding FEC delay not well suited for short keyboard to keyboard communications
<br />- 1k audio bandwidth is very wide as compared to other digital modes</p> <h2><span style="font-size: 14pt;">Olivia 16 Tone/500 Hz - Regional/Local HF Comms<o:p></o:p></span></h2> <p class="MsoNormal">For regional and local portable, mobile and fixed station operations on HF USB under good to poor conditions, Olivia 16/500 is our primary mode for short messages and situation reports and has been chosen for the following reasons:</p> <p>- <b>EXTREMELY</b> accurate decode, even under the worst conditions (major duplication of data and forward error corrected)
<br />- Very resiliant to QRM and QRN
<br />- Best suited for short messages and situation reports under poor HF conditions</p> <p>Disadvantages:</p> <p>- Slow data rate (slightly faster than writing speed)
<br />- 500 Hz audio bandwidth is wider than several other modes</p> <h2><a name="dom"><span style="font-size: 14pt;">DominoEX11(FEC) - Regional/Local HF Comms<o:p></o:p></span></a></h2> <p class="MsoNormal"><span style=""><!--[if gte vml 1]><v:shape id="_x0000_i1038" type="#_x0000_t75" alt="" style="'width:300.75pt;height:208.5pt'"> <v:imagedata src="file:///C:/DOCUME~1/ADMINI~1/LOCALS~1/Temp/msoclip1/01/clip_image014.jpg" href="http://www.pa-sitrep.com/NBEMS/domex11fec.jpg"> </v:shape><![endif]--><!--[if !vml]--><img src="file:///C:/DOCUME%7E1/ADMINI%7E1/LOCALS%7E1/Temp/msoclip1/01/clip_image014.jpg" shapes="_x0000_i1038" width="401" border="0" height="278" /><!--[endif]--></span></p> <p><span style="">For regional and local portable, mobile and fixed station operations on HF USB under good to moderate conditions, DominoEX11(FEC) is our primary mode for short messages and keyboard to keyboard communications and has been chosen for the following reasons:</span></p> <p><span style="">- Duplication of data and forward error correction provides good copy under moderate RF conditions
<br />- Well suited for keyboard to keyboard (chat)
<br />- Relatively narrow audio bandwidth (approx. 200 Hz)
<br />- More forgiving on tuning inacuracies than Olivia
<br />- Resiliant to QRM and QRN</span></p> <p><span style="">Disadvantages:</span></p> <p><span style="">- Not available on many programs other than NBEMS/FLDIGI and Multipsk
<br />- Not as reliable as Olivia 16/500 under very weak RF conditions</span></p> <p><!--[if !supportEmptyParas]--> <!--[endif]--><o:p></o:p></p> <p class="MsoNormal"><b style=""><span style="font-size: 16pt;">Step 7 – Specifics on Operations and Procedures by Mode<o:p></o:p></span></b></p> <p class="MsoNormal"><b style=""><span style="font-size: 16pt;"><!--[if !supportEmptyParas]--> <!--[endif]--><o:p></o:p></span></b></p> <h1 style="text-align: center;" align="center"><span style="color: orange;">Operations and Proceedures</span></h1> <h2 style="text-align: center;" align="center">MT63 - Olivia - DominoEX</h2> <h3><a name="mt632kl"><span style="color: orange;">MT63 VHF/UHF FM ops - 2K Long Interleave<o:p></o:p></span></a></h3> <p class="MsoNormal"><span style="">Instructions for FM 6m/2m/70cm ops:</span></p> <p><span style="">### SETUP ###</span></p> <p><span style="">1) Go to Configure/Modems and click the MT63 tab.
<br />2) Click 64 bit interleave long, save configuration, then close (on vs 3.03 this setting is now saved after restarts of the program).
<br />3) Go to Op Mode/MT63, arrow over and click on MT63 - 2000.</span></p> <p><span style="">### TUNING ###</span></p> <p><span style="">1) Tune transceiver to desired FM frequency (make sure all DSP, compression and noise blanker settings are disabled and stations operating under weak signal conditions should open the squelch on the transceiver).
<br />2) All stations should always center on 1500 Hz on the waterfall (MT63 always uses a bottom freq of 500 Hz on transmit. When you initialize MT63, the waterfall tx will be set to this default).
<br />3) Transmit and receive some text to make sure all stations are decoding properly. Assuming that all soundcards are properly calibrated, no tuning should be necessary. </span></p> <div class="MsoNormal" style="text-align: center;" align="center"> <hr size="2" width="100%" align="center"> </div> <h3><a name="mt631kl"><span style="color: orange;">MT63 HF USB ops - 1K/Long Interleave<o:p></o:p></span></a></h3> <p class="MsoNormal"><span style="">(recommended USB frequencies: 3.590, 7.090, 14.109):</span></p> <p><span style="">### SETUP ###</span></p> <p><span style="">1) Go to Configure/Modems and click the MT63 tab.
<br />2) Click 64 bit interleave long, save configuration, then close (on vs 3.03 this setting is now saved after restarts of the program).
<br />3) Go to Op Mode/MT63, arrow over and click on MT63 - 1000.</span></p> <p><span style="">### TUNING ###</span></p> <p><span style="">1) Tune transceiver to desired HF frequency (always us USB and make sure all DSP, compression and noise blanker settings are disabled).
<br />2) All stations should always center on 1000 Hz on the waterfall (MT63 always uses a bottom freq on 500 Hz on transmit. When you initialize MT63, the waterfall tx will be set to this default).
<br />3) Click tune button in the upper right corner of the program and let it transmit for about 10 seconds. Click the tune button again to go back into receive.
<br />4) RX stations center on the received 1000 Hz tone by tuning the receiver VFO.
<br />5) Transmit and receive some text to make sure all stations are tuned and decoding properly.</span></p> <h3><a name="oliv16_500"><span style="color: orange;">Olivia HF USB ops - 500Hz/16 Tones<o:p></o:p></span></a></h3> <p class="MsoNormal"><span style="">(recommended USB frequencies: 3.584, 7.074, 14.074):</span></p> <p><span style="">### SETUP ###</span></p> <p><span style="">1) Go to Op Mode, left click, arrow over Olivia, arrow over to 16/500 and left click.</span></p> <p><span style="">### TUNING ###</span></p> <p><span style="">1) Tune transceiver to desired HF frequency (always us USB and make sure all DSP, compression and noise blanker settings are disabled).
<br />2) All stations should always center on 1000 Hz on the waterfall.
<br />3) Click tune button in the upper right corner of the program and let it transmit for about 10 seconds. Click the tune button again to go back into receive.
<br />4) RX stations center on the received 1000 Hz tone by tuning the receiver VFO.
<br />5) Transmit and receive some text to make sure all stations are tuned and decoding properly.</span></p> <h3><a name="dominoex11fec"><span style="color: orange;">Domino HF USB ops - DominoEX11(FEC)<o:p></o:p></span></a></h3> <p class="MsoNormal"><span style="">(recommended USB frequencies: 3.583, 7.073, 14.073):</span></p> <p><span style="">### SETUP ###</span></p> <p><span style="">1) Left click on Configure, left click on Modems, left click the Dom tab.
<br />2) Type in your secondary text (i.e. call sign, tactical call, station location), left click both check boxes for Filter On and FEC, then left click save config, then left click close.
<br />3) Go to Op Mode, left click, arrow to DominoEX, arrow over to DominoEX 11 and left click.</span></p> <p><span style="">### TUNING ###</span></p> <p><span style="">1) Tune transceiver to desired HF frequency (always us USB and make sure all DSP, compression and noise blanker settings are disabled).
<br />2) All stations should always center on 1000 Hz on the waterfall.
<br />3) Click tune button in the upper right corner of the program and let it transmit for about 10 seconds. Click the tune button again to go back into receive.
<br />4) RX stations center on the received 1000 Hz tone by tuning the receiver VFO.
<br />5) Transmit and receive some text to make sure all stations are tuned and decoding properly.</span></p> WR5Jhttp://www.blogger.com/profile/16316513702643319581noreply@blogger.com0tag:blogger.com,1999:blog-4632435085083780021.post-56077198627200948102009-06-03T23:30:00.000-07:002009-06-07T22:42:39.840-07:00Session 1 - Summer of Digital Communications FunThis is Curt Black, WR5J with the Educational Radio Net –<br />Please stand by for a DIGITAL QST<br /><br />Send File ALLMODE.wav from KK7UQ (Thanks, Clint)<br /><br />CHECK-INS KD7ZYM, N7KC, K9PQ, AD7SK, N7KV, K7LWW, W7MAV<br /><br />Starting a Summer of Digital Communications Fun<br />(and Maybe to Make the Next Emergency More Fun, Too)<br /><br />First – Intro: Curt Black – Environmental Scientist – Ham for ¼ century – ¼ century ago had a digital node in a packet network that passed traffic all around texas<br /><br />Also a naturalist – birds and bats and nature in general – Sound Recordist – just finished teaching a class for nature sound recording at the UW.<br /><br />Schedule – This week – Introduction Then a two week break – I’ll be on a research vessel next week doing geophysics in Puget Sound and the full week after that I’m teaching a workshop on field techniques for bat research in eastern Washington. The 8:00pm timeslot is a very full one if you are doing bat research.<br /><br />But you blog readers have an assignment for the next two weeks. Download a specific software package, FLDIGI, and get it configured for your soundcard. Also, setup a microphone in your shack. Do it in such a way that as you are monitoring the waterfall, you can see all the sounds in your shack appearing on the waterfall.<br /><br />After the 2 week break – we'll start with setting the software up and then Acoustic Coupling of radios and computers and work our way through a few modes. Then we’ll move into harware coupling of radios and computers with interfaces. These interfaces can range from very simple ones for a few bucks to $100 for a Tigertronics SignaLink USB. If you want to keep going you can go up to a $369 US Interface Navigator - Lots of choices.<br /><br />As another potential assignment, you might want to start working on your interface over the next 2 weeks – One plan is in this months, June 2009, QST on page 30 – a nice article by Skip Teller- KH6TY and a $5 offer for the circuit board for the project. If you are considering the TigerTronics product, I just talked to them at SeaPac and the 4 week backorder on the SignaLink USB interfaceis a thing of the past. They say they are current with orders and hope to remain so.<br /><br /><br />We’ll revisit some of those modes we were experimenting with through acoustic coupling and use our hardware interfaces and see if that improves copy on some of the more sensitive modes. Then we’ll try some other software, week by week working our way through different modes or packages. I’ll put complete instructions on the website and if folks have trouble, my phone number and email will be on there as well. Then we’ll set up of the software for WSPR, the Weak Signal Propagation Reporter, WSJT a group of modes by Joe Taylor for Weak signal work terrestrially or via moon bounce that inlcudes JT65A used on HF and just exquisitely sensitive.<br /><br />Then if there is interest, we could visit some of the image transfer modes like EASYPAL <a href="http://www.kc1cs.com/">http://www.kc1cs.com/</a> – a mode that uses Digital Radio Mondiale or DRM to send the contents of an image file with repeats of any blocks containing errors so the picture comes through perfect – picture perfect if you like. We might even try some digital voice since the software is out there and very few people are using it. FDMDV, Frequency Division Multiplex Ditgital Voice, is a replacement for WinDRM and DRMDV - programs that just like EasyPal are using the Digital Radio Mondiale encoding technique.<br /><br />Not to be a slave to things digital, I have greatly enjoyed some analog slow scan television (SSTV) in the past. A Japanese ham, Makoto (Mako) Mori has a series of applications MMSSTV and MMRTTY among them availabe at <a href="http://mmhamsoft.amateur-radio.ca/">http://mmhamsoft.amateur-radio.ca/</a><br /><br /><strong>This Training Program and its Congruence with the Overarching Purposes of Ham Radio<br /></strong>Review of §97.1 Basis and purpose.<br />The rules and regulations in this Part are designed to provide an amateur radio service having a fundamental purpose as expressed in the following principles:<br />(a) VOLUNTARY PUBLIC SERVICE<br />(b) ADVANCE RADIO ARTS<br />(c) SKILLED CPMMUNICATORS AND TECHNICIANS<br />(d) EXPANDED RESERVOIR OF TECHNICIANS<br />(e) ENHANCE INTERNATIONAL GOODWILL<br /><br />We should be able to do just about all of this during this summer...<br /><br /><strong>Whats Digital?</strong><br /><br />Definition of a digital mode – for us, let's say, a mode made to be generated by and decoded by machine – not typically intended to be decoded by ear –<br /><br />What about CW? It was originally intended to be machine or visually read, but operators found they could copy the messages from the sounds of the equipment – so now it is by ear with practice. Is it digital – go onto a discussion listserv and argue for either position – you will discover people of great passion on both sides (this may be true of all topics in ham radio).<br /><br />When you get to high speed CW for meteor scatter work , it is particularly true it is only readable by machine. Several of the other modes more traditionally considered digital are also at least partly readable by ear - RTTY, esp. calling CQ, is very distinctive.<br /><br />For later we will go through all the words in this definition, but for now, CW is a three symbol code with source coding (variable length alphabet, like varicode) with soft decision coding, and mild FEC (operators interpretation of the code based on S/N) and some convolutional coding with soft decisions (matching characters received against patterns / words.<br /><br /><strong>Decoding Digital Modes</strong><br />If they are meant to be decoded by machine what do you need to do the decoding? Luckily some very generous and clever people have written some amazing software for decoding a wide range of digital modes.<br /><br />Some programs just specialize on one mode.<br /><br />Like Pawel Jalocha SP9VRC and Nino Porcino IZ8BLY MT63 Terminal (from <a href="http://xoomer.virgilio.it/aporcino/MT63/index.htm#Download">http://xoomer.virgilio.it/aporcino/MT63/index.htm#Download</a><br /><br />or DIGIPAN by Skip Teller for BPSK-31 and QPSK-31 and 64 from <a href="http://www.digipan.net/">http://www.digipan.net/</a><br /><br /><br />Often it is the introductory package that showed the world what the mode could do and made the mode popular, but eventually many modes are incorporated into programs that combine many modes and offer great flexibility with just one set up of the hardware and one user interface.<br /><br />By far, the most wide ranging piece of software currently available is MULTIPSK.<br /><br />Contrary to the name, it does far more than decode just PSK modes, and in fact, it decodes more different modes or protocols than any other package. Check out the author, Patrick Lindecker, F6CTE – and his (english language) website at <a href="http://f6cte.free.fr/index_anglais.htm">http://f6cte.free.fr/index_anglais.htm</a> for MultiPSK 4.14 and a listing of the incredible range of modes supported.<br /><br />Patrick is updating his code and adding modes nearly every week – it is amazing. The only downside is that the user interface is pretty daunting and the documentation is occasionally hard to decipher (although far better than if Patrick had reciprically insisted that I write the documentation in French). A very complete version of the program is free. For a donation, registration will activiate other desirable features.<br /><br />The other end of the spectrum on the user interface scale is Ham Radio Deluxe (HRD) with the companion program DM780 for the digital modes. This is the most polished piece of software I believe I have ever seen. While Simon Brown, HB9DRV, has not expanded the modes decoded to the range of those in MultiPSK, the user interface is very polished and the software works like a dream. Its only drawback is a very comprehensive suite of capabilities. These include logging functions, web lookup and spotting and many more that can make the package somewhat daunting to a first time user. HRD can be found at <a href="http://www.ham-radio-deluxe.com/">http://www.ham-radio-deluxe.com/</a> and the companion digital mode decoding package, DM780 is at<br /><a href="http://www.ham-radio-deluxe.com/Programs/DigitalMaster780/tabid/89/Default.aspx">http://www.ham-radio-deluxe.com/Programs/DigitalMaster780/tabid/89/Default.aspx</a><br /><br />MixW has a long history <a href="http://www.mixw.net/">http://www.mixw.net/</a> . It is a package with many features which requires a $50 payment to keep the program functional after an introductory period. This was pretty standard in 1996 when it was introduced, but there are some great programs out there in competition with for free. It went from February, 2007 to January 2009 without updates, but fairly recently was updated with several new modes and features. If you are a MixW user, you are probably familiar with the help files available from <a href="http://k6ix.net/MixW.html">http://k6ix.net/MixW.html</a> For many years MixW was the most feature rich and fairly simple piece of software for digital modes, but I think it has been supplanted by some of those already mentioned and is particularly true for the package I'll discuss next.<br /><br />The NBEMS Suite of software, Narrow Band Emergency Messaging System, has been developed to fill a need for a fairly concise set of features and modes in a package that is well designed, easy to install, set up, and operate. It meets each of these design goals very well. It is free for downloading from <a href="http://www.w1hkj.com/Downloads.html">http://www.w1hkj.com/Downloads.html</a> On that page, you will find Linux versions, and versions for Windows 2000, XP through Vista.<br /><br /><br />A Pennsylvania Radio Amateur Emergency group <a href="http://www.pa-sitrep.com/">http://www.pa-sitrep.com/</a> has assembled instructions for downloading, installing, configuring, calibrating, operating and enhancing the NBEMS software. Find them at <a href="http://www.pa-sitrep.com/NBEMS/index.html">http://www.pa-sitrep.com/NBEMS/index.html</a> and follow their sequence. Hopefully, that doesn't sound daunting. They have nicely put the information into bite sized pieces. This coupled with the clean and well organized user interface make this my current sofware choice for quickly getting people up and running on digital modes.<br /><br /><strong>What Modes are out there?</strong> (limiting ourselves to machine readable modes)<br />(in later weeks we’ll take these one by one and look at how the information is encoded and what the strengths and weaknesses are of each.)<br /><br />In rough order of “popularity”:<br /><br />By a landslide, <strong>PSK31 </strong>– Phase Shift Keying – with the flavors, Binary Phase Shift Keying BPSK-31, Quadrature Phase Shift Keying, QPSK-31, BPSK- 63, QPSK-63, BPSK- 125, QPSK 125, BPSK-250, QPSK-250<br /><br /><strong>RTTY</strong> – 45 baud, 50-baud, 75-baud<br /><br /><strong>Olivia</strong> – several flavors from 250 to 1000Hz bandwidth and with from 8 to 32 tones<br /><br /><strong>MFSK</strong> (Multi Frequency Shift Keying) which varies from 4 to 64 tones<br /><br /><strong>DominoEX</strong> (4,5,8,11,16,22)<br /><br /><strong>Hell modes</strong> (Feld Hell, Slow Hell, Feld Hell 5, Feld Hell 9, FSK Hell, FSK Hell-105, Hell 80) The Hellschreiber or Feldhellschreiber was a <a title="Facsimile" href="http://en.wikipedia.org/wiki/Facsimile">facsimile</a>-based <a title="Teleprinter" href="http://en.wikipedia.org/wiki/Teleprinter">teleprinter</a> invented by <a title="Rudolf Hell" href="http://en.wikipedia.org/wiki/Rudolf_Hell">Rudolf Hell</a> in the 1920s. It has since been emulated on computer sound cards by <a title="Amateur radio operator" href="http://en.wikipedia.org/wiki/Amateur_radio_operator">amateur radio operators</a>; the resulting mode is referred to as Hellschreiber, Feld-Hell, or simply Hell. "Hellschreiber" translates into English as "Light Writer," "Bright Writer," or "Clear Writer," and is a pun on the name of its inventor (Hell (the adjective) is German for "light," the adverb is "bright.") from Wikipedia<br /><br /><strong>MT-63</strong> (500, 1000, 2000 Hz bandwidths)<br /><br /><strong>Thor (</strong>4, 5, 8, 11, 16, 22)<br /><br /><strong>Throb </strong>(1, 2, 4)<br /><strong>ThrobX</strong> (1, 2, 4)<br /><br /><strong>Chip 64</strong> a phase shift keying application that utilizes some spread spectrum methods<br /><br /><br /><br /><strong>And a Universe of Others…<br /></strong><br /><br /><a href="http://physics.princeton.edu/pulsar/K1JT/WSJT703r1090.EXE">WSJT 7.03</a> Latest release by K1JT, Joe Taylor of Princeton<br /><br /><a href="http://physics.princeton.edu/pulsar/K1JT/WSJT703r1090.EXE">http://physics.princeton.edu/pulsar/K1JT/WSJT703r1090.EXE</a><br /><br />WSJT Protocols inlcude the following modes<br /><br /><strong>FSK441</strong> for meteor scatter<br /><br /><strong>JT6M</strong> for ionospheric scatter<br /><br /><strong>JT65</strong> for EME at VHF/UHF, and<br /><br /><strong>JT65A</strong> HF skywave propagation Frequently heard at 14.076<br /><a href="http://physics.princeton.edu/pulsar/K1JT/JT2_JT4.TXT">JT2, JT4</a>,<br /><br />Joe Taylor also wrote:<br /><a href="http://physics.princeton.edu/pulsar/K1JT/WSPR_mode.pdf">WSPR</a>: - Weak Signal Propagation Reporter<br /><a href="http://physics.princeton.edu/pulsar/K1JT/WSPR_mode.pdf">http://physics.princeton.edu/pulsar/K1JT/WSPR_mode.pdf</a><br />I’ve used 1 Watt and been copied in Singapore, New Zealand, Australia and South Africa<br />Check out the <a href="http://wsprnet.org/drupal/">http://wsprnet.org/drupal/</a> site for the database of propagation reports. Listen on 10.1387usb, 14.0956usb. As people begin to trust the ionisphere more and more with this mode, you see increasing numbers of entries in the database for 0.1 and 0.01 Watt signals.<br /><br />PC-ALE - The Automatic Linking and Embedding protocol for testing the ionisphere, finding a path, connecting stations and exchanging information. The program listed is a pretty dense read, steming possibly from its military background, but Patrick Lindecker in MultiPSK has taken the best of ALE and developed a new mode ALE-400 with a narrow bandwidth and some nice keyboard to keyboard features. I suspect his mode will be incorporated into other packages soon.<br /><br />APRS - the Automatic Position Reporting System - a flavor of packet radio which is probably a summer of adventure on its own. Once we have the interfaces working for our radios and computers, the addition of Packet Engine <a href="http://www.sv2agw.com/ham/agwpe.htm">http://www.sv2agw.com/ham/agwpe.htm</a> by SV2AGW, with some great help files and setup instructions from Ralph Milnes at <a href="http://www.kc2rlm.info/soundcardpacket/">http://www.kc2rlm.info/soundcardpacket/</a><br /><br />And if you are doing packet, you might as well be setup for message traffic for the next emergency, so PacLink should be on your radar. Particularly with the addition of a new sound card digital mode, Winmor which is undergoing testing right now. As part of the winlink system, PacLink can be found at <a href="http://www.winlink.org/ClientSoftware">http://www.winlink.org/ClientSoftware</a> After testing, Winmor will be fully integrated with PacLink and shows promise for being a sound card replacement for previous hardware solutions like Pactor which was propriatary and pricy for the average ham.<br /><br />The really good news is that whatever interface we set up for any of these digital modes opens up just about all of them (there is a caveat for the topic of Rig Control and antennas - the ALE system likes to roam around in the various ham bands listening and occasionally transmitting "soundings" and that can't be done if your computer isn't communicating with your radio and if your radio can't switch to various bands and find a good antenna waiting there. The good news is that you don't have to do ALE on multiple frequencies - you can tell it stay on one band, or even one frequency. While this defeats some of the intended benefit of ALE, it lets us experiment a bit - which I'm hoping is what ham radio is about.<br /><br /><strong>Steps for getting setup with NBEMS </strong><br />(I'll follow up with transfering the Pennsylvania instructions to a blog entry)<br /><br />Download the file for your machine from:<br /><a href="http://www.w1hkj.com/Downloads.html">http://www.w1hkj.com/Downloads.html</a><br />There are 2 windows versions and a Linux version, and I think there is a OS X version on the original W1HKJ page, but not the <a href="http://www.pa-sitrep.com/">http://www.pa-sitrep.com</a> link<br />What I know about NBEMS, the Narrow Band Emergency Messaging System, I learned on the Pennsylvania Situation Report website: <a href="http://www.pa-sitrep.com/">http://www.pa-sitrep.com/</a><br /><br />And Specifically the NBEMS portion of the site:<br /><a href="http://www.pa-sitrep.com/NBEMS/index.html">http://www.pa-sitrep.com/NBEMS/index.html</a><br /><br />Assignment 1 – go to the BLOG <a href="http://www.educationalradionet.blogspot.com/">http://www.educationalradionet.blogspot.com/</a> (link from the PSRG site to avoid the long blogspot address if you like <a href="http://www.psrg.org/">http://www.psrg.org/</a> ) and follow the instructions for downloading the NBEMS software.<br /><br />The only program you need for awhile will be <strong>FLDIGI</strong> -but just get everything that comes in the zipped package – WRAP, FLARQ, FLDIGI and some utilities like a sound card calibration piece called CHECKSR (ssome of those may not be in the same zip file). The zip file also contains CYGWIN1.DLL - follow their instructions to make sure your really only have one copy on your machine and all will be fine.<br /><br />If you are willing – keep going through the PA-Sitrep site instructions and download their macro set – <a href="http://www.pa-sitrep.com/NBEMS/fldigi_macro.htm">http://www.pa-sitrep.com/NBEMS/fldigi_macro.htm</a> . Also continue to the bottom of the page for the Definitions and Preferences files - note to save them in a different location from the Macro file<br /><br />Finally, think about what sort of interface you might like.<br /><br />It could be none, but if you are willing to do a bit of building or buying, your horizons are unlimited. We will spend several weeks messing with just acoustic coupling – so no pressure.<br /><br />We are at an amazing time for digital modes. There is phenomenal computational power in our computers and we now have software that can do stunning things with weak radio signals. This is perfect for this difficult phase of the sunspot cycle. It is also nearly ideal for people in situations where an “aluminum sky” of antennas is not an option.<br /><br />We are about to get some very effective ways of automating the identification of a large number of digital modes. This has been one of the most daunting things for hams wanting to move beyond PSK-31. Soon HRD/DM780 will join FLDIGI and MULTIPSK in automatically scanning the audio passband for the unique sound of Reed-Solomon identifiers for each digital mode and submode. In this way your rig can automatically recognize the mode, switch to decode it, move it to the center of your audio passband, close your filters down around the selected signal and decode it for you. We live in some great times. For more information about the automated identification of digital modes, since I may have mangled the concept during the session on the repeater, please check out Patrick’s description at <a href="http://f6cte.free.fr/The_RS_ID_easy_with_Multipsk.doc">http://f6cte.free.fr/The_RS_ID_easy_with_Multipsk.doc</a><br /><br />I’ll see everyone on Wednesday June 24 at 8:00pm – hopefully recovered from any bat bites and sea-sickness.<br /><br />Curt Black – <a href="mailto:black@nwfirst.com">black@nwfirst.com</a><br />WR5J – West Seattle, Washington, CN87tn<br />Download and install instructions will follow in the next postWR5Jhttp://www.blogger.com/profile/16316513702643319581noreply@blogger.com0