Might be easier to prove KU8E's new CT-17 is working...
Disconnect CT-17 from everything but computer. Fire up
computer with terminal program, talking to COM port CT-17
is connected to. Turn "echo off". Baud rate, parity, stop
doesn't matter. You should see what you type. Turn
baud rate down a bit (say 110 or 300) & you can even get
some wiggle from a volt meter across the CI-V bus.
Then reconnect to rig, make sure CI-V addresses are
set correctly, same baud rates, etc. The addressing is
likely to be tripping you up. Unlike others, with ICOM all
the rigs are on one bus - it isn't simply plug & talk as
there is only one radio on the other end... despite there
being only one radio in your case.
Physically, ICOM doesn't play silly buggers with DCE/DTE,
so no need for funky cabling like Yaesu.
Logically, the "transceive" function can cause the radio
to talk on its own & if the application on the computer doesn't
expect this (because of not doing CI-V fully), this can result in
collisions on the bus that make things appear not to work, or
intermittently not work.
73, VR2BrettGraham
_______________________________________________
CQ-Contest mailing list
CQ-Contest@contesting.com
http://lists.contesting.com/mailman/listinfo/cq-contest
|