[chirp_users] Chirp Data transfer

Ken Simpson, W8EK W8EK at flham.net
Mon Jul 4 13:50:18 PDT 2011


I don't think there is any question that it is a communications 
problem, but the real question is what is it and how to fix it.

I downloaded the daily build, installed it, and ran it. Here is the 
debug file after that, using the "real serial port" on Com 1:

CHIRP daily-06292011 on WinXP
autorpt not set et
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


I am assuming that all of the those zeros equate to no data going 
thru.  That almost sounds like a bad cable.  But I have used both a 
USB one made specifically for the VX-3, and an older DB-9 serial cable 
that was used years ago with a VX-5.  It is hard to think that both 
could be bad.  And I tried the USB on 2 different computers.

It is really getting frustrating!


Thanks.

73,

Ken, W8EK


Richard Farina wrote, On 7/4/2011 4:36 PM:
> On 07/04/11 16:18, Ken Simpson, W8EK wrote:
>> Actually doing a hard reset is not a problem.  I have two VX-3s.  One
>> is partially loaded. but the other is "empty".  I did a hard reset on
>> the one, and there is what I get:
>>
>> Log initialized
>> Clone thread started
>> 000: 00 00 00 00 00 00 00 00   ........
> See now, something just looks wrong there.... If I'm reading the debug 
> right that should be the first line the radio spits out and all 0's 
> isn't correct at all.  There pretty well has to be a communication 
> problem of some kind here...
> 
> Looking at the exceptions it is hard to tell, but I'm guessing a serial 
> port driver issue of some kind.  Perhaps use google and get a new driver 
> for your usb cable? Try with the serial port one and lowering the buffer 
> value?
> 
> Honestly I'm not exactly sure what is going on, I am significantly 
> lacking experience using chirp on windows and this seems like a windows 
> driver or windows python issue.
> 
> Maybe try the last daily build?
> 
> http://trac.chirp.danplanet.com/chirp_daily/daily-06292011/
> 
> -Rick
> 
>> -- 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 54, in chunk_read
>>     File "chirpui\clone.pyo", line 189, in __status
>> CloneCancelledException
>> ------
>> Clone failed:
>> Clone thread ended
>>
>> Close to the same, except the last line.
>>
>> Does this help any?
>>
>> Thanks.
>>
>> 73,
>>
>> Ken, W8EK
>>
>>
>>
>>
>> Richard Farina wrote, On 7/4/2011 3:58 PM:
>>> On 07/04/11 15:46, Ken Simpson, W8EK wrote:
>>>> 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   ........
>>>>
>>> Oh man, I so hate to me the jerk that says this but.... um.... can you
>>> hard reset your radio and try again?  If what you just posted is correct
>>> then your radio is identifying with all 0's which is just wrong.  In  my
>>> experience sometimes the Yaesu's just go out to lunch cloning wise, and
>>> a hard reset tends to fix it.
>>>
>>> I hope you don't have a lot programmed in it yet.....
>>>
>>> Otherwise, do you have any other software that it is working with right now?
>>>
>>> -Rick
>>>> -- 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
>>>>>>



More information about the chirp_users mailing list