[ICOM] Splitting the CI-V data stream

Gary P. Fiber gfiber at comcast.net
Fri Jan 29 18:49:53 EST 2010


Ya I had forgot you ops are getting all that information via the CI-V 
these days.
I go clear back the IC-735 4 bit data days. Well sounds like Data 
Collisions are more prevalent with more devices connected on the CI-V 
data buss.
Polling was the way to go when the Transceive function got in the way 
having 2 or more rigs connected to the CI-V buss but now it seems you 
need both.
No more ideas from me to solve it.

Gary K8IZ

On 1/29/2010 1:37 PM, Dave AA6YQ wrote:
> If you turn off the rig control application's polling and rely instead on
> enabling "CI-V transceive", then the rig control application can't display
> anything but the transceiver's current frequency and mode, e.g. no RX
> bandwidth readout, AF and RF gain, RF power, S-meter, etc.
>
>     73,
>
>         Dave, AA6YQ
>
> -----Original Message-----
> From: icom-bounces at mailman.qth.net
> [mailto:icom-bounces at mailman.qth.net]On Behalf Of Gary P. Fiber
> Sent: Friday, January 29, 2010 3:51 PM
> To: ICOM Reflector
> Subject: Re: [ICOM] Splitting the CI-V data stream
>
>
> Maybe turn off the polling of the PC software and let the Transceive
> setting of the CI-V report to the PC the Frequency and mode.
> As I remember your stuck with transceive needing to be enabled so the
> PW-1 follows the transceiver around in frequency and band.
> I wrote one of the original write-ups how to get the PW-1 and a
> Transceiver to connect and use CI-V control, was a matter of starting
> one before the other but that's as far as I went with it. AND is been 10
> years ago.
>
> I do remember the Transceive was an issue when tying two or more
> transceivers together as what you did to one the others would follow as
> far as they could, generally the mode would follow.
>
> Gary K8IZ
>
> On 1/29/2010 12:28 PM, Dave AA6YQ wrote:
>    
>>>>> AA6YQ comments below
>>>>>
>>>>>            
>> -----Original Message-----
>> From: icom-bounces at mailman.qth.net
>> [mailto:icom-bounces at mailman.qth.net]On Behalf Of Mel
>> Sent: Friday, January 29, 2010 1:54 PM
>> To: ng7z at arrl.net; icom at mailman.qth.net
>> Subject: [ICOM] Splitting the CI-V data stream
>>
>>
>> I think you are trying to fix the wrong problem, Paul. Splitting the
>> CI-V bus is unlikely to cause "lost bits" but data collisions are. The
>> problem can be caused if more than one device is active instead of
>> passive. For example, the logging program should not poll the bus if the
>> rig is in CI-V transceive (active) mode.
>>
>>
>>      
>>>>> Or the logging program should be designed to work correctly in the face
>>>>>
>>>>>            
>> of collisions.
>>
>>       73,
>>
>>           Dave, AA6YQ
>>
>> ----
>> 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
>>
>>
>>      
> ----
> 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
> No virus found in this incoming message.
> Checked by AVG - www.avg.com
> Version: 8.5.406 / Virus Database: 271.1.1/2644 - Release Date: 01/29/10
> 09:08:00
>
> ----
> 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
>
>    



More information about the Icom mailing list