[ICOM] Testing CI-V port

[Joe Stepansky]

Yes, I always check for baud rate and CI-V address, because I know myself
and the kinds of silly things I can do.

73, Joe KQ3F

-----Original Message-----
From: Icom [mailto:icom-bounces at mailman.qth.net] On Behalf Of ZL2AAA
Sent: Monday, July 04, 2016 5:00 PM
To: ICOM Reflector
Subject: Re: [ICOM] Testing CI-V port

Have you checked that the baud rate is the same for radio and software or
com port open?

-----Original Message-----
From: Joe Stepansky
Sent: Tuesday, July 05, 2016 3:10 AM
To: 'ICOM Reflector'
Subject: [ICOM] Testing CI-V port

Noticed at Field Day that my 756 Pro2 wasn't communicating with the computer
for frequency info. I resolved when I got home to make sure my 756 Pro3
(different rig) was working fine, then substitute the Pro2 and modify
software settings to make sure something was really wrong.



Imagine my surprise when the Pro3 was exhibiting the same behavior. No
frequency info between rig and software. I substituted a second Rigblaster
with the same result.



Before I send both rigs off for repair (who knows what may have happened,
but the Pro2 hasn't even been connected to an antenna), is there a good way
to test the CI-V port?



73, Joe KQ3F

----
Your Moderator: Dick Flanagan K7VC: icom-owner at mailman.qth.net Icom Users
Net: Sundays, 1700Z, 14.316 MHz Icom FAQ: http://www.qsl.net/icom/ To
support QSL/QTH.net: http://www.qsl.net/donate.html 


---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus

----
Your Moderator: Dick Flanagan K7VC: icom-owner at mailman.qth.net Icom Users
Net: Sundays, 1700Z, 14.316 MHz Icom FAQ: http://www.qsl.net/icom/ To
support QSL/QTH.net: http://www.qsl.net/donate.html