++++++++++++++++++ See also some items in KIO2_Software ++++++++++++++++++++ Date: 12 Aug 2001 21:20:53 -0400 From: Richard Mulvey Subject: Re: [Elecraft] Software interface On 12 Aug 2001 16:27:50 -0700, Mike Studer wrote: > Some programming questions related to the KIO2 interface. > > Is the status sent from the K2 a null terminated string? > I am trying to figure out when it is done sending stuff. > No - it comes across as a continuous data stream. You can determine that it's done simply by examining the response strings, and validating them against the expected number of bytes. > Why is AI1 not reporting at 2 second intervals? > > I sent AI1; to the K2 but I only get status when something changes. > I thought it was supposed to send information about every 2 seconds. > Not as far as I've seen in the documentation - the description on Page 3 of the programmers reference simply says that it will report based on front panel events. - - Rich ++++++++++++++++++++++++ Date: Sun, 12 Aug 2001 22:39:49 -0700 (PDT) From: Mike Studer Subject: Re: [Elecraft] Software interface On 12 Aug 2001, Richard Mulvey wrote: > On 12 Aug 2001 16:27:50 -0700, Mike Studer wrote: > > Some programming questions related to the KIO2 interface. > > > > Is the status sent from the K2 a null terminated string? > > I am trying to figure out when it is done sending stuff. > > > > No - it comes across as a continuous data stream. > > You can determine that it's done simply by examining the response > strings, and validating them against the expected number of bytes. > Yuck. > > > Why is AI1 not reporting at 2 second intervals? > > > > I sent AI1; to the K2 but I only get status when something changes. > > I thought it was supposed to send information about every 2 seconds. > > > > Not as far as I've seen in the documentation - the description on Page 3 > of the programmers reference simply says that it will report based on > front panel events. >From page 3 of the manual. AI (Auto-info mode) 1. Periodic auto-info: The K2 sends and IF (info) response every 2 seconds, except during vfo movement. Perhaps you can see why this description makes me expect to see an IF packet every 2 seconds. Mike AB6CV +++++++++++++++++++++++++ Date: Mon, 13 Aug 2001 08:30:45 -0400 (EDT) From: Rich Subject: Re: [Elecraft] Software interface >Mike Studer Writes: > >On 12 Aug 2001, Richard Mulvey wrote: > >> On 12 Aug 2001 16:27:50 -0700, Mike Studer wrote: >> > Some programming questions related to the KIO2 interface. >> > >> > Is the status sent from the K2 a null terminated string? >> > I am trying to figure out when it is done sending stuff. >> > >> >> No - it comes across as a continuous data stream. >> >> You can determine that it's done simply by examining the response >> strings, and validating them against the expected number of bytes. >> > >Yuck. Actually, it's pretty strightforward. And a good check for validating the KIO2 response. I'm doing it just by building a small state machine that examines each response, and validates it before passing it up to the higher API layers. > >> >> > Why is AI1 not reporting at 2 second intervals? >> > -------------snip --------------- > >Perhaps you can see why this description makes me expect to see an IF >packet every 2 seconds. I'm assuming that you must have an older revision of the manual - - I'm working from Rev. C, which doesn't include that text, just the description I mentioned above. Rev C is the version currently at the Elecraft site. - - Rich ++++++++++++++++++++++++++ Date: Mon, 13 Aug 2001 09:48:35 -0700 From: Eric Swartz WA6HHQ - Elecraft Subject: Re: [Elecraft] Software interface Hi, All K2 command responses are terminated by a semicolon, making it easy detect the end of a response. In my VB6 programs I simply use a switch case statement to parse the response once a semicolon has been detected. The AI2 function reports when something changes on the radio, not every two seconds. Our original version of the programmer's guide incorrectly stated it was sent every two seconds. You must have this earlier version. The latest version of the programmer's guide, which has been on the manual download page since July 9th, correctly documents this. 73, Eric WA6HHQ Rich wrote: > >>From page 3 of the manual. > >AI (Auto-info mode) > > > >1. Periodic auto-info: The K2 sends and IF (info) response every 2 > >seconds, except during vfo movement. > > > >Perhaps you can see why this description makes me expect to see an IF > >packet every 2 seconds. > > I'm assuming that you must have an older revision of the manual > - I'm working from Rev. C, which doesn't include that text, just the > description I mentioned above. Rev C is the version currently at the > Elecraft site. > > - Rich ++++++++++++++++++++++++++ Date: Mon, 13 Aug 2001 15:23:31 -0400 (EDT) From: Rich Subject: [Elecraft] Re: Software Interface >All K2 command responses are terminated by a semicolon, making it easy detect >the end of a response. In my VB6 programs I simply use a switch case statement >to parse the response once a semicolon has been detected. > Actually, I think I'd still go with my original response. I've had at least one case where I apparently had a serial overrun ( It was a really, really, really busy Sparcstation :-) ) that caused half of the response to be lost by my KIO2 interface code. That ended up making me parse the response as it came in, after setting a timeout alarm waiting for the entire response to appear. If there's no timeout while waiting for a ';' to show up, it would presumably cause the interface code to wait in a busy-loop, forever. - - Rich +++++++++++++++++++++++++ Date: Mon, 13 Aug 2001 14:20:14 -0500 From: ke6d at juno.com Subject: Re: [Elecraft] Re: Software Interface > Actually, I think I'd still go with my original response. I've > had > at least one case where I apparently had a serial overrun ( It was > a really, really, really busy Sparcstation :-) ) that caused half > of the response to be lost by my KIO2 interface code. That ended > up making me parse the response as it came in, after setting a > timeout alarm waiting for the entire response to appear. If there's > no timeout while waiting for a ';' to show up, it would presumably > cause the interface code to wait in a busy-loop, forever. > > - Rich Hi Rich, I am also working on a version of the K2 remote control software on the NT/95 platform using Visual C++ and MFC just for the fun of it. For the portion which deals with the K2 comm port, I created 3 threads (task in UNIX world). - - One of these threads is the incoming command parsing thread. Its only task is to monitor the serial port for incoming characters, assemble these characters into complete command, then pass this command over to GUI thread using one of inter-process communication mechanism available to a multitasking kernel. - - The GUI thread (as its name implies) is in charge of updating the K2 GUI screen and passing the user inputs to the outgoing command transmit thread. - - The outgoing command transmit thread basically formats the commands into correct K2 KIO format and send them out. It also gets notification from the coming command parsing thread on the "KY" command so that it can pace the "KY" text appropriately. These 3 threads talk to each other extensively using inter-process communication protocol so none of them is actually hung up if nothing is happening. If you are using Unix on a Sparcstation, I highly recommend you to do the same. Otherwise, your GUI (is what the user will see all the time) will be very sluggish... 73, Dan KE6D ========================================================= Amateur Radio Station: KE6D Danh Le, Milpitas, California ke6d at arrl.net, ke6d at juno.com http://www.qsl.net/ke6d ++++++++++++++++++++++++++ Date: 13 Aug 2001 18:18:52 -0400 From: Richard Mulvey Subject: Re: [Elecraft] Re: Software Interface On 13 Aug 2001 14:20:14 -0500, ke6d at juno.com wrote: > > Hi Rich, > > I am also working on a version of the K2 remote control software on the > NT/95 platform using Visual C++ and MFC just for the fun of it. For the --------snip----------- > Actually, the way I've structured the code is that I have a very small serial/network bridge process that has one thread reading the serial port, a second thread writing the port, and a third that handles tcp/ip communication. The server ensures that only well-formed requests and responses are passed to the client, to relieve the GUI of the necessity of dealing with the hardware. The client GUI, which may or may not run on the same machine, communicates with the server via tcp/ip, and simply reads and writes the command/responses to the server sockets as a stream, as straight ASCII. In fact, right now, I have the K2 hooked up to my Linux box in the basement, and I'm running it from my Linux box up the den. I was using it from work earlier today, too, with the client running under Windows on my laptop. The net is a wonderful thing. :-) This is all running under Java at the moment, so the GUI code runs on Solaris, Linux, Windows, etc - basically anything that can run a Java application. The server component has to run on a machine that implements the javax.comm extentions to handle the serial port, but that includes all of the major platforms out there today, anyhow. Once I get all of this cleaned up, I'll be releasing the source for anyone who wants to use it. - - Rich +++++++++++++++++++++++ Date: Wed, 10 Oct 2001 09:15:37 -0700 From: Eric Swartz WA6HHQ - Elecraft Subject: Re: [Elecraft] K2 programming problem Hi Julian, The only way to program the CW memories is via the regular CW paddle input. The KIO2 KY command generates CW but does not function if you are in CW memory store mode. Basically we did not have enough code space to add that feature. I'd love to have it though, so it is on our future desired feature list if room opens up. 73, Eric WA6HHQ ========= "Julian, G4ILO" wrote: > > I am trying to write a program to load text into the K2's CW memories. I > get as far as putting the K2 into record mode, but the text I send is > ignored. In fact I can't get the KY command (send CW from text) to work at > all. What am I doing wrong? +++++++++++++++++ Date: 12 Oct 2001 20:43:39 -0400 From: Richard Mulvey Subject: Re: [Elecraft] FW (Filter Bandwith) Extended SET ??? On 12 Oct 2001 18:28:10 -0500, Rich Lentz wrote: > The KIO2 Programers Reference indicates that you can directly set to FL1 - > FL4 by sending FWxxxn; where xxxx are any numbers and n is the filter to be > selected. > > However when I send this command the the K2 nothing happens!! (I have a K2 > with KSB2 and KIO2.) > > The command "FW0000;" will change the filter to the next filter. However, > "FW00001;" "FW00002;" "FW00003;" "FW00004;" does nothing. Also have the > same problems with the extended RSR format. > Are you absolutely sure you've set up the rig in extended mode? I just tried cycling through the filters with FW00001-FW00004, and it worked just as expected. For filter 4, filter 1 was actually selected, since I don't have filter 4 defined in SSB modes. - - Rich ++++++++++++++++++ Date: Fri, 12 Oct 2001 20:25:17 -0500 From: "Rich Lentz" Subject: RE: [Elecraft] FW (Filter Bandwidth) Extended SET ??? Thanks Guess I should have read the WHOLE Programmers Reference. Also for some strange reason or by design on my setup commands must be in lower case. Rich KE0ZX ++++++++++++++++++++ Date: Fri, 25 Jan 2002 12:00:49 -0800 (PST) From: Fernando Quinones To: Elecraft at mailman.qth.net Subject: [Elecraft] FYI Hello Listers.. If you are not into programming. I have learn quite a bit from the postings and would like to put some back. Being into kit building, there are a couple of avenues for those interested in trying out to program something. Just to see if you would like it without any overhead. Sort of kit building but on the computer. So here a kit that might interest you. All the ingredients are free and found on the web. You already have the major component if you are reading this. A tutorial, an editor and a programming environment. Again all free!! The turorial is availble by the graciousness of a college professor and can be found here: He has pointers to a very nice editor and the programming environment. NOTE: not a send money gimmick. So if you would like to see what programming is about in a painless fashion try it. You might be surprise how easy it is. Perhaps your thoughts are like mine and was wondering how to program that computer interface to the K2. No.. it would show you explicitly how is done, (open the com1, send command, receive response, do something with the response,etc..) but it get you thinking. Above all, this is not to start a thread on which one is better than another. Lets leave that for the other forum. disclaimer applies.. enjoy ===== 73's Fernando NF6Q/NNN0JYM San Jose,CA. CCA #01187 FISTS #8649 K2 #2330 (in it's infancy) ++++++++++++++++ Reply-To: From: "J. Edward (Ed) Muns" To: Date: Tue, 29 Oct 2002 11:38:27 -0800 Subject: [Elecraft] Saving & Restoring K2 Menu Parameters via RS232 Has anyone written a program for a PC to download all the user-settable menu parameters from the K2? It would be nice to be able to edit the parameters on the PC and to be able to upload the saved or modified parameter set back to the K2. This would be particularly handy when updating the MCU with one that comes with the factory defaults. Or, just to see in one place the entire configuration of the K2. Or, to have different configurations for different applications of the K2 that could be uploaded when going from, say, a SSB contesting weekend to digital work. All the necessary K2 programming info is in the Programmer's Reference Guide on the website. If you find any menu parameters that are NOT downloadable or uploadable, let Wayne know ... in case he can correct that in the next firmware revision. 73, Ed - W0YK +++++++++++++++++ Date: Fri, 21 Feb 2003 16:02:08 -0800 Subject: Re: [Elecraft] Error in Kio2 Programmers PDF Cc: To: "Tony Wells" From: Jack Brindle Actually, it appears that the K2 accepts both formats, and then some. It definitely accepts "PCxxx;" in extended mode, but it also appears to accept "PCxxxx;" and "PCxxxxx;" as well as "PCxxxxxx;". In all cases on my K2 (no KPA100) it accepts the data and truncates the digits following the third digit. I'll let the list pundits consider what all this might mean, but that number of digits conceivably could allow setting power up to 99,999.9 watts... On Friday, February 21, 2003, at 02:35 AM, Tony Wells wrote: > The Kio2 programmers ref has an error on extended mode power setting. > I am > using the latest firmware. > > The pdf says: > > "Extended SET format: PCnnn; where nnn is 000-150 in 0.1-watt units > without > the PA, 000-150 watts with." > > It should say: > > "Extended SET format: PCnnnn; where nnnn is 0000-1500 in 0.1-watt > units....." > > I also think it should say, but cannot confirm as my PA is not > connected: > > ".......with the PA, 0000-1500 in 0.1 watt." > > Regards, > > Tony > M3CJF > G7IGG ++++++++++++++++++ Date: Fri, 21 Feb 2003 16:41:18 -0800 Subject: Re: [Elecraft] Error in Kio2 Programmers PDF Cc: "Tony Wells" To: elecraft at mailman.qth.net From: Jack Brindle While we are on the subject of the KIO2 interface, I can say with some authority that there actually is an error in the programmers reference manual, but Tony actually didn't find it. The error occurs in the translation table for the DS command. The table shows that a received 'Z' is translated to an 'X'. The correction is that a 'Z' should be translated to a lower-case 'c'. As noted in a private email from Wayne, trailing digits are ignored by the K2 on received RS-232 commands. This means that the number of digits in the argument is limited by the size of the K2 command receive buffer. This is slightly disappointing to me since I was really looking forward to acquiring a 10GW amplifier (and the required associated electrical utility) to make sure I will be heard in the EQP next month. Now I guess I'll just have to make due with my "hefty" 15 watts... On Friday, February 21, 2003, at 04:02 PM, Jack Brindle wrote: > Actually, it appears that the K2 accepts both formats, and then some. > It definitely accepts "PCxxx;" in extended mode, but it also appears > to accept "PCxxxx;" and "PCxxxxx;" as well as "PCxxxxxx;". In all > cases on my K2 (no KPA100) it accepts the data and truncates the > digits following the third digit. I'll let the list pundits consider > what all this might mean, but that number of digits conceivably could > allow setting power up to 99,999.9 watts... > -Jack Brindle, WA4FIB ======================================================================= MacDobs - helping to shift the paradigm for low-cost amateur astronomy. +++++++++++++++++++++ From: "Tony Wells" To: , "Jack Brindle" Subject: Re: [Elecraft] Error in Kio2 Programmers PDF Date: Sat, 22 Feb 2003 00:48:45 -0000 > Jack Brindle wrote: > Actually, it appears that the K2 accepts both formats, and then some. > It definitely accepts "PCxxx;" in extended mode, but it also appears to > accept "PCxxxx;" and "PCxxxxx;" as well as "PCxxxxxx;". In all cases Folks,. It wasn't the SET so much as the GET that alerted me. Go into Extended mode and enter "PC;" You will see nnnn emitted, not nnn. If you think that's esoteric, you should see my paper on the undocumented opcodes inside the Pentium III 8-) ++++++++++++++++++ Date: Fri, 21 Feb 2003 17:09:39 -0800 Subject: Re: [Elecraft] Error in Kio2 Programmers PDF Cc: To: "Tony Wells" From: Jack Brindle Well, take a look at the KIO2 programmers reference manual for the PC instruction. It states: "Extended RSP format: PCnnnx; where nnn is power (extended SET format), and x is 0 (PA off) or 1 (PA on)." Which explains why the K2 returns 4 digits for the response. Three for power and one for PA on/off. So the K2 could receive a command to set the power to my mythical 10GW, but it could only tell me that the power had been set to 99.9 watts. And a side note to Wayne: This could actually mean that _I_ am the one who "needs a life"... On Friday, February 21, 2003, at 04:48 PM, Tony Wells wrote: >> Jack Brindle wrote: > >> Actually, it appears that the K2 accepts both formats, and then some. >> It definitely accepts "PCxxx;" in extended mode, but it also appears >> to >> accept "PCxxxx;" and "PCxxxxx;" as well as "PCxxxxxx;". In all cases > > Folks,. > > It wasn't the SET so much as the GET that alerted me. Go into > Extended > mode and enter "PC;" You will see nnnn emitted, not nnn. ++++++++++++++++++ To: t.wells at blueyonder.co.uk Cc: elecraft at mailman.qth.net, jackbrindle at earthlink.net Date: Sat, 22 Feb 2003 10:13:06 -0800 Subject: Re: [Elecraft] Error in Kio2 Programmers PDF From: ke6d at juno.com Hi, The documentation for the PC command is correct. The last digit of the command indicates whether the AMP is on or off since the K2 can optionally turn off the AMP if the power is below 10W or so. Suppose if your K2 does not have the AMP installed, and the power setting is 5.0W. Doing a PC, will get a PC0500 returned. If your AMP is installed, and the power setting is at 50W, doing a PC, will get a PC0501 returned by the K2. One key point to remember is that the K2 may send a '0' as the last digit even though you have the amp enabled. The reason for this is the K2 will turn off the amp if the power setting is below 10W or so. To fully utilize the amp scale setting, one needs to send the last digit as '1' if one wants to use the larger scale. 73 es Hope this will clear things up. Dan, KE6D +++++++++++++++++ Date: Thu, 1 May 2003 17:38:09 -0100 From: "Julian (G4ILO)" To: "Elecraft List" Subject: [Elecraft] CW sending using the CAT KY command I'm having trouble implementing CW sending by CAT in K2Net. According to the docs, you can only send 24 characters at a time using the KY command. The trouble is that the K2 doesn't automatically report when the buffer is empty so that I can fill it with more text. To work around this problem, I have a timer send a KY; command at 500ms intervals. According to the docs, in extended response mode this will return a value of 0 when the buffer is full, 1 when it is 75% full and 2 when it is completely empty. However, what I appear to be getting is a response of 0 until all the text has been sent, then a response of 2. Because I can't top up the buffer with text before it becomes empty, there is an unacceptable gap in the sending every 24 characters. Am I going about this the wrong way? Hopefully Wayne or Eric will respond to this, but as others have also written remote control software for the K2 perhaps they have some ideas too. 73, -- Julian, G4ILO. (RSGB, ARRL, G-QRP, K2 #392) G4ILO's Shack: http://www.qsl.net/g4ilo ++++++++++++++ Date: Thu, 1 May 2003 11:10:50 -0700 Subject: Re: [Elecraft] CW sending using the CAT KY command Cc: "Elecraft List" To: "Julian (G4ILO)" From: Jack Brindle On Thursday, May 1, 2003, at 11:38 AM, Julian (G4ILO) wrote: > I'm having trouble implementing CW sending by CAT in K2Net. According > to > the docs, you can only send 24 characters at a time using the KY > command. > The trouble is that the K2 doesn't automatically report when the > buffer is > empty so that I can fill it with more text. Let me take a stab at this one. It is fairly easy to make this work quite smoothly. > To work around this problem, I have a timer send a KY; command at 500ms > intervals. According to the docs, in extended response mode this will > return a value of 0 when the buffer is full, 1 when it is 75% full and > 2 > when it is completely empty. You have managed to reverse the meanings of the values. For the KY command, the KI2 programmers reference guide states: "Basic RSP format: KYn; where n is 0 (CW text buffer not full) or 1 (buffer full). Extended RSP format: KYn; where n is 0 (buffer < 75% full), 1 (buffer > 75% full), or 2 (buffer completely empty AND transmit of previous string is complete." If you get an extended response of 0, you should be able to send at least six characters to the K2. A value of 2 means that you can send up to 24 characters, AND that the K2 has actually stopped transmitting. > However, what I appear to be getting is a response of 0 until all the > text has been sent, then a response of 2. Because I can't top up the > buffer with text before it becomes empty, there > is an unacceptable gap in the sending every 24 characters. Am I going > about > this the wrong way? Your algorithm should be: if response is 0, send five or six characters to the K2, then continue polling. if response is 1, simply continue polling. if response is 2, send up to 24 characters to fill the buffer, OR use the information to indicate that the previous transmission has completed. A couple of items of note - the '<' and '>' characters can come in quite handy in the use of the KY command. Everything between a '<' and the next '>' is simply sent to the speaker, and not transmitted on the air. This can be very useful in alerting the user to some station condition. Be careful, though, to avoid interrupting the transmission (by pressing a key, for example), or you could leave the K2 in test mode where all further KY commands get sent to the speaker and not to the air. Methods of detecting this situation are left as an exercise for the user. ;-) The second item is a follow-on to the first. KY transmissions can be interrupted by pressing a key on the front panel, or even simulating a keypress using the SW command. Doing so will abort the current transmission, meaning that everything following in the buffer will not be interpreted (thus the above described problem). This may also cause serial commands following the KY to be flushed. As an example, suppose you implement a 10-minute CW ID for sideband operation. Every ten minutes you might send the following string to the K2: "MD3;KY DE WA4FIB;MD1;". This string commands the radio to go to CW mode, send the identification, then return to LSB mode. If the command is interrupted during the transmission, the radio will not execute the last command, and you will stay in CW mode. Thus it is important to check the response strings to make sure that all the commands you send are indeed carried out. > Hopefully Wayne or Eric will respond to this, but as others have also > written remote control software for the K2 perhaps they have some > ideas too. Those two are a bit busy at the moment, so don;t expect a quick response. Let's just say that spring is a very busy time around the Elecraft offices... -Jack Brindle, WA4FIB +++++++++++++++++ Date: Fri, 2 May 2003 11:16:07 -0100 From: "Julian (G4ILO)" Subject: Re: [Elecraft] CW sending using the CAT KY command To: "Elecraft List" Jack, Many thanks indeed for that information. It was just what I needed to get this working properly. It's counterintuitive that the buffer full value (1) is between the two values that say you can send text, and as I never saw a response of 1 even right after sending a full 24 characters I was coming to the conclusion that it didn't work as documented. Thanks again. -- Julian, G4ILO. (RSGB, ARRL, G-QRP, K2 #392) G4ILO's Shack: http://www.qsl.net/g4ilo Jack Brindle wrote: You have managed to reverse the meanings of the values. For the KY command, the KI2 programmers reference guide states: "Basic RSP format: KYn; where n is 0 (CW text buffer not full) or 1 (buffer full). Extended RSP format: KYn; where n is 0 (buffer < 75% full), 1 (buffer > 75% full), or 2 (buffer completely empty AND transmit of previous string is complete." If you get an extended response of 0, you should be able to send at least six characters to the K2. A value of 2 means that you can send up to 24 characters, AND that the K2 has actually stopped transmitting. [snipped} ++++++++++++++ Date: Sat, 24 May 2003 13:41:56 -0700 Subject: Re: [Elecraft] KIO2 and reading voltage/current Cc: elecraft at mailman.qth.net To: Steve Muncy From: Jack Brindle On Saturday, May 24, 2003, at 01:26 PM, Steve Muncy wrote: > I may have overlooked it, but I can't find a GET command that will > provide the current voltage and current in the K2 when using the KIO2. > Does anyone know how I can access this info except through clicking > the display switch in software? That's it. You have to issue the following sequence: "SW02;DS;SW02;" and parse the data string returned in the DS reply to get the voltage and current information. Make sure the K2 is NOT in menu mode when you do this... -Jack Brindle, WA4FIB +++++++++++++++ Date: Wed, 28 May 2003 09:51:20 -0100 From: "Julian (G4ILO)" Subject: Re: [Elecraft] Announcement: K2Net v0.3 To: "Dave" Cc: Elecraft at mailman.qth.net That's great to hear, Dave. Regarding the CW characters, according to the KIO2 Programmers Ref, the following characters are mapped to CW "Prosigns": ( KN + AR = BT % AS * SK so the server strips out ( ) + = % and * from the text, then looks for " KN ", " AR " etc and substitutes the special characters for them. Therefore you can't send any of those symbols, but to send KN etc you just type it as a word, followed by a space. It's a good idea to get in the habit of ending every word with a space because the client transmits your text to the server on a "word at a time" basis. 73, -- Julian, G4ILO. (RSGB, ARRL, G-QRP, K2 #392) G4ILO's Shack: http://www.qsl.net/g4ilo ==== Original message ==== > Julian > > That worked first time... great stuff. My home network consists of an XP > Pro > machine in the shack and a networked Win 95 machine with only a 486 DX66 > processor and 8 MB of RAM... I didn't use the audio streaming, just > connected a speaker (with volume control on the speaker) to a pair of > wires > running along the network cable route. > > Did you forget to include the special (or not so special) Morse > characters? > I don't seem able to send KN, SK, AR properly, nor does it want to send > / > ( ) and = characters for some reason. > > I've already had QSOs with it... could call them "arm chair copy" as > they > were from the sofa in the front room! > > Dave, G4AON > K2 #1892 ++++++++++++++++