SD 14.29 Windows XP Pro SP3 Ten-Tec Omni VII The RAC Winter Contest was my first outing using rig control, so maybe I got something wrong. I started SD, went through the setup for the contest, used t
Unfortunately, the serial port of the Omni VII is fixed at 57600; I think the same is true for a few other current Ten-Tec rigs. I'll just remember to re-enter the LINK and POLL values whenever I sta
Rather than trying to configure SD on the fly, I'd like to create a template file for the Minnesota QSO party next month (rules here: http://www.w0aa.org/mnqp_rules.htm). I've tried building one out
Still trying to get this right, I found that with no other changes, if I used "NAQP.MLT" as the multiplier file, it worked correctly, but if I used my own "MNQP.MLT", it reverted to wanting to send a
SD 14.30 Windows XP Pro SP3 During the ARRL CW DX contest this past weekend, I ran into the following unwanted behavior, operating in S+P mode: 1. Enter other guy's call in "Call" field, hit ENTER My
Isn't that what the "AUTOFILL" command is for? When SD identifies area codes from the callsign, or from previous QSOs, it auto-fills the data in the exchange field. This may be a nuisance in S&P mode
SD 15.21 Windows XP Pro SP3 I had previously configured COM1 for rig control and LPT1 for keying of my Ten-Tec Omni 7 and both were working correctly. Firing up SD for another practice session for up
Another piece of information ... SD 14.30 (the version I'd been using until yesterday) worked correctly at startup. Switching back and forth between 15.21 and 14.30, 15.21 failed at startup and 14.30
SD 15.22 Windows XP SP3 I operated strictly in S+P mode, and SD's internal keyer worked just fine throughout this past weekend's SS except for two problems: 1. When I'd typed the other station's call
My reason for wanting to be able to do that is that several times after calling the other station at what I thought was an appropriate speed, on hearing him send his exchange I realized that I really
SD 15.22 Windows XP SP3 During the CW SS, I pulled up the SD manual in Adobe Reader 9.0. When I returned to SD, I was surprised to see that I was in "keyboard mode." Experimenting, I find that SD wil
Just downloaded and installed V15.25, and it signs on as V15.24. The README.1ST file says V15.25, so I guess it's just a matter of an edit being missed. -- Bert Hyman W0RSB St. Paul, MN bert@iphouse.
SD 15.27 Ten-Tec Omni VII Windows XP Pro SP3 With ESM on and in "S+P" mode, changing my rig from UCW to LSB or USB, either from the front panel or by selecting a memory with that mode stored, caused
SD 15.27 Windows XP Pro SP3 The .ALL file only contains the first 4 characters of the contact's name, followed by a space, followed by the state: 14021 CW 110108 190706 VE7WEB 599 599 BRIA BC 01 ú M
For what it's worth, I found that I could coerce some VERY strange behavior out of SD when I would occasionally start flailing around the keyboard when an exchange didn't go as expected (I don't do w
The AUTOFILL command is supposed to toggle that behavior on and off: When SD identifies district codes from the callsign, or from previous QSOs, it auto-fills the data in the exchange field. This may
YOW! A new version with a fix to a major SS bug released two days before the contest. What was the last version WITHOUT this bug, just in case something else pops up with this new one? Wish I could r
Windows XP Pro SP3 Ten-Tec Omni VII Rig control is set for the O7, PRIORITY is set to 1, initial QTH and miscellaneous setup for SS is done. MSG1-MSG8 were left at their default setting. CW keying (v
Beating on 15.52 some more in S&P mode, I found that 1. When the cursor is in the field for entering the other station's exchange, pressing the "-" key send my call, rather than clearing the entire e
These problems probably involve my USB keyboard. I went back to 15.32 and the same problems exist. My old PS2 keyboard died and I replaced it with this USB model. -- Bert Hyman W0RSB bert@iphouse.com