Re: [chirp_users] Chirp Data transfer
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
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@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users
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
chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users
chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users
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 ........
-- 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
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
chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users
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
On 07/04/11 16:50, Ken Simpson, W8EK wrote:
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:
I'm at a loss, we will have to wait for Dan the man to chime in. Enjoy the rest of your 4th.
-Rick
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 >
chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users
I am assuming that all of the those zeros equate to no data going thru.
Actually, that's what it looks like when you enter clone mode on the radio *after* you've already clicked OK on the clone settings box. The radio barfs a little garbage (in the form of a few null bytes) as it boots up into clone mode.
On 07/04/11 17:01, Dan Smith wrote:
I am assuming that all of the those zeros equate to no data going thru.
Actually, that's what it looks like when you enter clone mode on the radio *after* you've already clicked OK on the clone settings box. The radio barfs a little garbage (in the form of a few null bytes) as it boots up into clone mode.
Ahh!
Perhaps the order is wrong then....
Boot the radio into clone mode (turn on while holding F/W), then tell chirp to download from radio, then hit band.
Better now?
-Rick
That is the way I have been doing it!
Richard Farina wrote, On 7/4/2011 5:09 PM:
On 07/04/11 17:01, Dan Smith wrote:
I am assuming that all of the those zeros equate to no data going thru.
Actually, that's what it looks like when you enter clone mode on the radio *after* you've already clicked OK on the clone settings box. The radio barfs a little garbage (in the form of a few null bytes) as it boots up into clone mode.
Ahh!
Perhaps the order is wrong then....
Boot the radio into clone mode (turn on while holding F/W), then tell chirp to download from radio, then hit band.
Better now?
-Rick _
That is the way I have been doing it!
So, if you want to try something:
1. Open up HyperTerminal 2. Set to the proper COM port, no flow control, 19200 baud 3. Type something, which should be echo'd to the screen if the cable is working as expected (even when not connected to the radio) 4. Then put your radio in clone mode and hit the band key 5. See if you get "AH028" on your screen
If you do, then I'm out of ideas. If you don't then there's something wrong with the cable, serial port, radio, etc.
I have tried Hyperterminal, and I get part way.
I set the Com 1 port (since I am using the "real serial cable" to 19200 baud, and 8-N-1 with no flow control.
At step 3, I get nothing back when I type anything. And I don't think I should since there is no "wrap" plug on the cable connecting "data out" back to "data in" or TxD to RxD, if you prefer.
I tried steps 4 and 5, and nothing happens.
Thanks.
73,
Ken, W8EK
Dan Smith wrote, On 7/4/2011 5:30 PM:
That is the way I have been doing it!
So, if you want to try something:
- Open up HyperTerminal
- Set to the proper COM port, no flow control, 19200 baud
- Type something, which should be echo'd to the screen if the cable is working as expected (even when not connected to the radio)
- Then put your radio in clone mode and hit the band key
- See if you get "AH028" on your screen
If you do, then I'm out of ideas. If you don't then there's something wrong with the cable, serial port, radio, etc.
I tried the same on the laptop with the USB cable on Com 5.
I DO get echo back on that (I can see what I am typing), but when I try to go into clone mode (step 4) nothing comes back. It sort of sounds like the cable is not connected to the radio. But both cables?????
Thanks.
73,
Ken, W8EK
Ken Simpson, W8EK wrote, On 7/4/2011 5:53 PM:
I have tried Hyperterminal, and I get part way.
I set the Com 1 port (since I am using the "real serial cable" to 19200 baud, and 8-N-1 with no flow control.
At step 3, I get nothing back when I type anything. And I don't think I should since there is no "wrap" plug on the cable connecting "data out" back to "data in" or TxD to RxD, if you prefer.
I tried steps 4 and 5, and nothing happens.
Thanks.
73,
Ken, W8EK
Dan Smith wrote, On 7/4/2011 5:30 PM:
That is the way I have been doing it!
So, if you want to try something:
- Open up HyperTerminal
- Set to the proper COM port, no flow control, 19200 baud
- Type something, which should be echo'd to the screen if the cable is working as expected (even when not connected to the radio)
- Then put your radio in clone mode and hit the band key
- See if you get "AH028" on your screen
If you do, then I'm out of ideas. If you don't then there's something wrong with the cable, serial port, radio, etc.
I DO get echo back on that (I can see what I am typing)...
Echo in HyperTerminal is a setting: File >> Properties >> Settings >> ASCII Setup >> "Echo characters typed locally".
sounds like the cable is not connected to the radio. But both cables?????
Is there by chance a "null modem" adapter involved (which would switch the transmit/receive signals)?
Do you know the cable's pinout (for all intermediate cables)?
73 de Daniel KB3MUN
The USB cable is a direct cable with a USB connection on one end, and the 3.5 mm 4 conductor plug that is normally speaker mic, but used to clone. Nothing in between. It was purchased specifically for the VX-3.
The "real serial cable" comes from the 9 pin D connector to a 3.5 mm regular stereo connector (3 conductors including ground), that then goes thru an adapter to the 3.5 mm 4 conductor plug used for cloning. Years ago, this worked fine this way with a VX-5, so I doubt it has changed, unless the VX-3 and VX-5 have the TxD and RxD switched.
At this point, I am thinking that possibly the plastic around the jack on the VX-3s do not permit the cable to go all of the way in. It looks like it goes in all of the way, but it is really up against the plastic case, so it is hard to tell for sure. And no way to really test that. Of course if it was not in all of the way, the TxD and RxD connections would not be the right place, and it would not work.
Of course one would hope that a cable bought specifically for the VX-3 would fit the VX-3!
Any other ideas?
Thanks.
73,
Ken, W8EK
D. Daniel McGlothin KB3MUN wrote, On 7/4/2011 6:19 PM:
I DO get echo back on that (I can see what I am typing)...
Echo in HyperTerminal is a setting: File >> Properties >> Settings >> ASCII Setup >> "Echo characters typed locally".
sounds like the cable is not connected to the radio. But both cables?????
Is there by chance a "null modem" adapter involved (which would switch the transmit/receive signals)?
Do you know the cable's pinout (for all intermediate cables)?
73 de Daniel KB3MUN
The USB cable is a direct cable with a USB connection on one end, and the 3.5 mm 4 conductor plug that is normally speaker mic, but used to clone. Nothing in between. It was purchased specifically for the VX-3.
There *should* be something in between. The radio does not speak USB, which means you need a USB-to-serial chip in between. This is normally hidden inside the USB hood, since it's so small. If you didn't have anything, then you wouldn't see a new serial port show up when you plug it in.
Given the discussion below, I really think it's a combination of potentially one bad cable and maybe a not-fully-seated second cable. If you don't get the clone header in HyperTerminal, then something's just plain not connected.
The "real serial cable" comes from the 9 pin D connector to a 3.5 mm regular stereo connector (3 conductors including ground), that then goes thru an adapter to the 3.5 mm 4 conductor plug used for cloning. Years ago, this worked fine this way with a VX-5, so I doubt it has changed, unless the VX-3 and VX-5 have the TxD and RxD switched.
Yep, agreed, although I'd suspect any and all of that as being the problem, either preventing physical insertion, or not connecting the proper pins.
At this point, I am thinking that possibly the plastic around the jack on the VX-3s do not permit the cable to go all of the way in. It looks like it goes in all of the way, but it is really up against the plastic case, so it is hard to tell for sure. And no way to really test that. Of course if it was not in all of the way, the TxD and RxD connections would not be the right place, and it would not work.
Yep, this is why I asked about fully seating the connector. Sounds like there may still be some work to be done here.
Of course one would hope that a cable bought specifically for the VX-3 would fit the VX-3!
Where did you get it? There are tons of devices that use 3 and 4 conductor TRS connectors for cloning and I wouldn't put it past many of the ebayers to have sent you the wrong cable.
If you have the ability to check that the pins are properly connected, that might be a good next step. The pinout is:
http://www.kc8unj.com/pinout.jpg
I realize there are electronics in the USB cable. I was just referring to any cable changes, criss crosses, or possible places for error.
I got the USB to VX-3 cable on e-bay. It was listed as being specifically for the VX-3, but as you say, anything is possible.
Thanks for the pin out info. I did not have that. From that diagram, it would look like the VX-3 might be trying to send data to the speaker, and that the data/clone connection is likely connected to the Mic/PTT, which might be lose enough to ground to not permit echo in hyperterminal when plugged in.
Looking at the USB/VX-3 cable from e-bay, it looks like the distance on each side of the center pin to the outside is almost the same as the diameter of the center pin. In the picture you sent, it looks like the distance on each side is less than half of the diameter of the center pin. It also appears to be somewhat cone shaped. My guess at this point is that is where the problem is. The cable simply is not going all of the way in. Obviously, that would account for all of the problems!
Looking at the "real serial cable" used with the VX-5 years ago, the insulation diameter is much less than the USB/VX-3 cable, but still much greater than shown in your example picture.
I hate to perform surgery on the VX-3, but I think I will try some sandpaper and/or file on the smaller connector, and see if I can make it even smaller, and then see what happens.
I really appreciate everyone's help, especially since it turns out not to be a chirp problem.
Thanks.
73,
Ken, W8EK
Dan Smith wrote, On 7/4/2011 6:47 PM:
The USB cable is a direct cable with a USB connection on one end, and the 3.5 mm 4 conductor plug that is normally speaker mic, but used to clone. Nothing in between. It was purchased specifically for the VX-3.
There *should* be something in between. The radio does not speak USB, which means you need a USB-to-serial chip in between. This is normally hidden inside the USB hood, since it's so small. If you didn't have anything, then you wouldn't see a new serial port show up when you plug it in.
Given the discussion below, I really think it's a combination of potentially one bad cable and maybe a not-fully-seated second cable. If you don't get the clone header in HyperTerminal, then something's just plain not connected.
The "real serial cable" comes from the 9 pin D connector to a 3.5 mm regular stereo connector (3 conductors including ground), that then goes thru an adapter to the 3.5 mm 4 conductor plug used for cloning. Years ago, this worked fine this way with a VX-5, so I doubt it has changed, unless the VX-3 and VX-5 have the TxD and RxD switched.
Yep, agreed, although I'd suspect any and all of that as being the problem, either preventing physical insertion, or not connecting the proper pins.
At this point, I am thinking that possibly the plastic around the jack on the VX-3s do not permit the cable to go all of the way in. It looks like it goes in all of the way, but it is really up against the plastic case, so it is hard to tell for sure. And no way to really test that. Of course if it was not in all of the way, the TxD and RxD connections would not be the right place, and it would not work.
Yep, this is why I asked about fully seating the connector. Sounds like there may still be some work to be done here.
Of course one would hope that a cable bought specifically for the VX-3 would fit the VX-3!
Where did you get it? There are tons of devices that use 3 and 4 conductor TRS connectors for cloning and I wouldn't put it past many of the ebayers to have sent you the wrong cable.
If you have the ability to check that the pins are properly connected, that might be a good next step. The pinout is:
On 07/04/11 18:30, Ken Simpson, W8EK wrote:
The USB cable is a direct cable with a USB connection on one end, and the 3.5 mm 4 conductor plug that is normally speaker mic, but used to clone. Nothing in between. It was purchased specifically for the VX-3.
I feel like a complete jerk even saying this, but you realize that the data port on the radio isn't the same as the earphone port right?
Data port is on the top next to the antenna.
Just trying to rule everything out....
-Rick
The "real serial cable" comes from the 9 pin D connector to a 3.5 mm regular stereo connector (3 conductors including ground), that then goes thru an adapter to the 3.5 mm 4 conductor plug used for cloning. Years ago, this worked fine this way with a VX-5, so I doubt it has changed, unless the VX-3 and VX-5 have the TxD and RxD switched.
At this point, I am thinking that possibly the plastic around the jack on the VX-3s do not permit the cable to go all of the way in. It looks like it goes in all of the way, but it is really up against the plastic case, so it is hard to tell for sure. And no way to really test that. Of course if it was not in all of the way, the TxD and RxD connections would not be the right place, and it would not work.
Of course one would hope that a cable bought specifically for the VX-3 would fit the VX-3!
Any other ideas?
Thanks.
73,
Ken, W8EK
D. Daniel McGlothin KB3MUN wrote, On 7/4/2011 6:19 PM:
I DO get echo back on that (I can see what I am typing)...
Echo in HyperTerminal is a setting: File>> Properties>> Settings>> ASCII Setup>> "Echo characters typed locally".
sounds like the cable is not connected to the radio. But both cables?????
Is there by chance a "null modem" adapter involved (which would switch the transmit/receive signals)?
Do you know the cable's pinout (for all intermediate cables)?
73 de Daniel KB3MUN
chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users
DUH!!!!!
I am a dummy!
I am a dummy!
Of course I was using the speaker mic connection on the side. That is all that I have ever used, and it has a 4 conductor plug to use, so that is what I used.
Actually, I just checked the manual, and it says to use the speaker mic connection. So why would any one use a connection on top that is different? Obviously, I did not! In reality, I did not even realize there was a connector on the top. The rubber cover looks just like the rest of the top, and it is not that visible.
In any case, all is well now, and I have learned a lot. I have used it with the "real serial cable" and will try the USB cable shortly.
FWIW, it might be good to have a note with the VX-3 info that the "cloning port" on the top needs to be used.
I really appreciate everyone's help, especially since it was such a dumb mistake on my part.
Thanks.
73,
Ken, W8EK
Richard Farina wrote, On 7/4/2011 11:46 PM:
On 07/04/11 18:30, Ken Simpson, W8EK wrote:
The USB cable is a direct cable with a USB connection on one end, and the 3.5 mm 4 conductor plug that is normally speaker mic, but used to clone. Nothing in between. It was purchased specifically for the VX-3.
I feel like a complete jerk even saying this, but you realize that the data port on the radio isn't the same as the earphone port right?
Data port is on the top next to the antenna.
Just trying to rule everything out....
-Rick
The "real serial cable" comes from the 9 pin D connector to a 3.5 mm regular stereo connector (3 conductors including ground), that then goes thru an adapter to the 3.5 mm 4 conductor plug used for cloning. Years ago, this worked fine this way with a VX-5, so I doubt it has changed, unless the VX-3 and VX-5 have the TxD and RxD switched.
At this point, I am thinking that possibly the plastic around the jack on the VX-3s do not permit the cable to go all of the way in. It looks like it goes in all of the way, but it is really up against the plastic case, so it is hard to tell for sure. And no way to really test that. Of course if it was not in all of the way, the TxD and RxD connections would not be the right place, and it would not work.
Of course one would hope that a cable bought specifically for the VX-3 would fit the VX-3!
Any other ideas?
Thanks.
73,
Ken, W8EK
D. Daniel McGlothin KB3MUN wrote, On 7/4/2011 6:19 PM:
I DO get echo back on that (I can see what I am typing)...
Echo in HyperTerminal is a setting: File>> Properties>> Settings>> ASCII Setup>> "Echo characters typed locally".
sounds like the cable is not connected to the radio. But both cables?????
Is there by chance a "null modem" adapter involved (which would switch the transmit/receive signals)?
Do you know the cable's pinout (for all intermediate cables)?
73 de Daniel KB3MUN
In any case, all is well now, and I have learned a lot. I have used it with the "real serial cable" and will try the USB cable shortly.
Glad to hear it. Thanks should go to Rick for thinking outside the box... :)
On 07/05/11 07:17, Ken Simpson, W8EK wrote:
DUH!!!!!
I am a dummy!
I am a dummy!
Of course I was using the speaker mic connection on the side. That is all that I have ever used, and it has a 4 conductor plug to use, so that is what I used.
You aren't by any chance in the Navy are you? Normally I only have to tell sailors.... nevermind.... :-)
Glad to hear it works, please let us know how you like chirp now that it is working.
-Rick
Actually, I just checked the manual, and it says to use the speaker mic connection. So why would any one use a connection on top that is different? Obviously, I did not! In reality, I did not even realize there was a connector on the top. The rubber cover looks just like the rest of the top, and it is not that visible.
In any case, all is well now, and I have learned a lot. I have used it with the "real serial cable" and will try the USB cable shortly.
FWIW, it might be good to have a note with the VX-3 info that the "cloning port" on the top needs to be used.
I really appreciate everyone's help, especially since it was such a dumb mistake on my part.
Thanks.
73,
Ken, W8EK
Richard Farina wrote, On 7/4/2011 11:46 PM:
On 07/04/11 18:30, Ken Simpson, W8EK wrote:
The USB cable is a direct cable with a USB connection on one end, and the 3.5 mm 4 conductor plug that is normally speaker mic, but used to clone. Nothing in between. It was purchased specifically for the VX-3.
I feel like a complete jerk even saying this, but you realize that the data port on the radio isn't the same as the earphone port right?
Data port is on the top next to the antenna.
Just trying to rule everything out....
-Rick
The "real serial cable" comes from the 9 pin D connector to a 3.5 mm regular stereo connector (3 conductors including ground), that then goes thru an adapter to the 3.5 mm 4 conductor plug used for cloning. Years ago, this worked fine this way with a VX-5, so I doubt it has changed, unless the VX-3 and VX-5 have the TxD and RxD switched.
At this point, I am thinking that possibly the plastic around the jack on the VX-3s do not permit the cable to go all of the way in. It looks like it goes in all of the way, but it is really up against the plastic case, so it is hard to tell for sure. And no way to really test that. Of course if it was not in all of the way, the TxD and RxD connections would not be the right place, and it would not work.
Of course one would hope that a cable bought specifically for the VX-3 would fit the VX-3!
Any other ideas?
Thanks.
73,
Ken, W8EK
D. Daniel McGlothin KB3MUN wrote, On 7/4/2011 6:19 PM:
I DO get echo back on that (I can see what I am typing)...
Echo in HyperTerminal is a setting: File>> Properties>> Settings>> ASCII Setup>> "Echo characters typed locally".
sounds like the cable is not connected to the radio. But both cables?????
Is there by chance a "null modem" adapter involved (which would switch the transmit/receive signals)?
Do you know the cable's pinout (for all intermediate cables)?
73 de Daniel KB3MUN
chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users
Echo in HyperTerminal is a setting: File>> Properties>> Settings>> ASCII Setup>> "Echo characters typed locally".
Local echo should be *disabled* and you should *still* see echo.
The echo comes from the fact that these radios use a single pin for transmit and receive, and thus the TX and RX lines are tied together inside the radio. Since you see no echo and no data when you try to initiate the clone, something is wrong with hardware. Since you have two cables, it sure sounds like the radio. Since you said you tried two radios, it sounds like the serial port. Since you tried two serial ports... well, not sure what to say :)
However, we can rule out CHIRP here since you aren't getting the beginning of the clone message from the radio.
First, I did not know that the TxD and RxD lines were tied together. That means we are only using one pin of the 3 active pins, plus ground. I find that once I take the cable out of the radio, I DO get echo. That would insinuate that the data line is being grounded when plugged into the radio, so that no echo would come back.
It is certainly looking like a hardware problem, likely with the plug not going all the way in. Now the big question -- do I want to perform surgery on a VX-3?
I agree that we can rule out the chirp program at this point, and I certainly thank you for the efforts to get things going.
Thanks.
73,
Ken, W8EK
Dan Smith wrote, On 7/4/2011 6:41 PM:
Echo in HyperTerminal is a setting: File>> Properties>> Settings>> ASCII Setup>> "Echo characters typed locally".
Local echo should be *disabled* and you should *still* see echo.
The echo comes from the fact that these radios use a single pin for transmit and receive, and thus the TX and RX lines are tied together inside the radio. Since you see no echo and no data when you try to initiate the clone, something is wrong with hardware. Since you have two cables, it sure sounds like the radio. Since you said you tried two radios, it sounds like the serial port. Since you tried two serial ports... well, not sure what to say :)
However, we can rule out CHIRP here since you aren't getting the beginning of the clone message from the radio.
participants (4)
-
D. Daniel McGlothin KB3MUN -
Dan Smith -
Ken Simpson, W8EK -
Richard Farina