If you're trying to use the COM port to interface with the rig's
control port (i.e. for frequency/mode display and tracking in
WriteLog), you generally *can't* use that same port to key the rig
without some extra work on your part. A few rigs (FT-1000MP, FT-100 and
probably a few others) support software commands to key the rig so you
don't even need a keying line for those (and you wouldn't be having
this problem). But most rigs do not have software commands to key them.
WriteLog *can* use the same serial port for rig control and for keying,
but you have to build a cable that splits out the keying circuit (the
RTS line) from the rest of the serial cable.
Assuming you're only using the serial port for the keying line (and not
rig interfacing), you next need to know whether the RigBlaster is
configured to key via RTS or DTR (two different pins on the serial
port) -- WriteLog wants to use RTS (it uses DTR for sending CW and for
FSK keying.) This is likely a jumper setting within the RigBlaster.
Does the RigBlaster key the transmitter when you use other programs?
Obviously you need to be sure the RigBlaster is working correctly.
-Marty NW0L
martyt@pobox.com
--- John Desmond <jdesmon@uswest.net> wrote:
>
> I have been trying to get Writelog (V10.20B) to key the rig via
> COM1
> on a laptop via Rigblaster. The
> Rigblaster manual says that as the PC boots, the data lamp should
> flash
> and the rig should key. I never see this
> but I know the COM port works fine as I use it all the time for other
> functions.
> I looked at the Rigblaster site and saw what they had as an
> example
> for setting that up. That did not help. I
> am thinking that maybe the laptop (IBM 770Z Thinkpad) may not
> activate
> the right leads for this function to work.
> Any ideas out there?
__________________________________________________
Do You Yahoo!?
Get personalized email addresses from Yahoo! Mail - only $35
a year! http://personal.mail.yahoo.com/
--
WWW: http://www.writelog.com/
Submissions: writelog@contesting.com
Administrative requests: writelog-REQUEST@contesting.com
Problems: owner-writelog@contesting.com
|