I got my WinKey keyer hooked up and working (for the most part) in DXbase, but the pot on the WinKey doesn't function.
In the setup menu in DXbase, there is a setting for the pot control - mine was set by default to 127. Is anyone aware of any setting in the setup menu that will allow the pot (it's nothing more than an external speed control) to function properly? Kudos to the author of DXbase for the shortcut capabilities. I was able to quickly program the CW memories into the numbers on the keypad and I'm using the numpad "-" and "+" to increase and decrease CW speed. Any better ideas (or other ideas/approaches in general) are welcome. Art - K4IRS From [EMAIL PROTECTED] Sat Mar 4 05:29:41 2006 From: [EMAIL PROTECTED] (Brendan Minish EI6IZ) Date: Sat Mar 4 05:30:21 2006 Subject: [Dxbase] Follow-up on the IC-7000 In-Reply-To: <[EMAIL PROTECTED]> References: <[EMAIL PROTECTED]> Message-ID: <[EMAIL PROTECTED]> On Mon, 2006-02-27 at 19:22 -0500, Peter Dougherty (W2IRT) wrote: I did the elecraft k2 support and also have a pro2 which I have tweaked a bit for faster operation. here are a few suggestions, you mileage may vary! but please share your end results with us > What is somewhat annoying is the lag between clicking the QSY command > and the radio actually responding. I changed the pacing from 50 to 10 > and it made no difference. Using 19200/N/8/1. Any way to speed this up? yes, firstly you can probably reduce pacing to 5 (or less) with any modern Icom running at 9600 or above. the biggest delay by far however is with the eoc commands on the end of each line, the 706 defaults are 250 you can try reducing these to 100 if 100 works try for less (say 75 or even 50) but don't set these too close to 'just working' or you will have occasional problems the eoc values set how long the driver waits for a response before issuing the next command, in the stock 706 file it's waiting 1/4 of a second between each command, by reducing eof you are speeding up the time between commands. when you get things working the way you like. please test over a range of interface speeds You may be better off starting with the pro2 or pro3 entries as a template as they are already a lot faster than the 706 entries and I suspect that the 7000 will be similar in response times. If you need any help please drop me a line and I'll see what I can do to help > Also, when I have the radio in split mode, I can't seem to get DX > Base to acknowledge the activity on VFO-B or post it to the cluster, > etc. Is this a known issue with ICOMs? yes i think so, there is no way to read over the wire split mode so it's impossible to detect vfoB under these circumstances for spotting Dunno if the 7000 has this problem too but but I guess Icom still are not listening to customer feedback in relation to the Civ protocol? If you look at the pro series there are separate entries for vfo only mode, see which works the best for you, the vfo A only files will be quicker (less commands to issue and wait for results ) but won't set vfo b either. Personally I prefer this since most split spots are 'ballpark only' for the TX QRG 73 Brendan EI6IZ
