[chirp_users] Chirp Data transfer

Ken Simpson, W8EK
Mon Jul 4 12:46:37 PDT 2011


I tried turning off the FIFO buffers on my main computer, and using 
the real 9 pin serial cable on Com 1, I got the following in the bedug 
file:

Log initialized
Clone thread started
000: 00 00 00 00 00 00 00 00   ........

-- Exception: --
Traceback (most recent call last):
   File "chirpui\clone.pyo", line 217, in run
   File "chirp\yaesu_clone.pyo", line 178, in sync_in
   File "chirp\yaesu_clone.pyo", line 69, in clone_in
   File "chirp\yaesu_clone.pyo", line 44, in chunk_read
   File "serial\serialwin32.pyo", line 212, in read
CloneCancelledException
------
Clone failed:
Clone thread ended


That is slightly different than the one on the laptop with the USB 
cable, but not much.  Again it is progress over just "Log initialized".


Thanks.

73,

Ken, W8EK


Ken Simpson, W8EK wrote, On 7/4/2011 3:23 PM:
> I MAY be making progress.
> 
> I turned off the buffers on the laptop (as outlined below), and 
> reinstalled ver 0.1.11 to use with the VX-3 (you will recall I had 
> switched to ver 0.1.10 on the laptop, just to try it to see if any 
> difference).
> 
> I now have something in the debug file!
> 
> Here is what it says:
> 
> 
> Log initialized
> Clone thread started
> 
> -- Exception: --
> Traceback (most recent call last):
>    File "chirpui\clone.pyo", line 217, in run
>    File "chirp\yaesu_clone.pyo", line 178, in sync_in
>    File "chirp\yaesu_clone.pyo", line 69, in clone_in
>    File "chirp\yaesu_clone.pyo", line 44, in chunk_read
>    File "serial\serialwin32.pyo", line 195, in read
> CloneCancelledException
> ------
> Clone failed:
> Clone thread ended
> 
> 
> 
> Hopefully that will mean something to you.
> 
> At least the log says something more than "log initialized".
> 
> Thanks very much for your help.
> 
> 73,
> 
> Ken, W8EK
> 
> 
> 
> 
> D. Daniel McGlothin KB3MUN wrote, On 7/4/2011 2:33 PM:
>> [mailed direct in case greylist prevents this message from reaching the 
>> list.]
>> 
>>> Any other ideas?
>> 
>> 
>> 
>>  > By the way, I am using Win XP with SP3.
>> 
>> You might try disabling the COM port buffers.  We find this necessary at 
>> times to do serial communications with certain machine tools so that any 
>> pacing requirements are not upset.
>> 
>> How to:  Right-click MyComputer and choose Properties then click 
>> Hardware tab (Alternately, from Control Panel, double-click System); 
>> click Device Manager button.  Expand the Ports(COM&LPT) and double-click 
>> the COM port in question.  Choose PortSettings tab; click Advanced 
>> button.  After making sure that the expected COM port number is selected 
>> on the "Advanced Settings" window, either uncheck the 'Use FIFO 
>> buffers'; or leave it checked and experiment with lower values in the 
>> Receive & Transmit buffers.
>> 
>> 
>>  > Since I wrote this, I also got an older serial cable (as in 9 pin D
>>  > connector and not usb) that I had for a VX-5, and tried it.  Same
>>  > result (although it is on Com 1).
>> 
>> Does either of the cable setups work with the VX-5 and Chirp?  Do you 
>> have any other radio that does work with Chirp and the computer(s)?  If 
>> so, what are the differences in cabling?
>> 
>> 73 de Daniel KB3MUN
>> 
> _______________________________________________
> chirp_users mailing list
> chirp_users at intrepid.danplanet.com
> http://intrepid.danplanet.com/mailman/listinfo/chirp_users
> 



More information about the chirp_users mailing list