[chirp_devel] Noob, want to add a driver, getting started questions
Hi all,
I'm new to Chirp, and looking to set up a driver for my favorite radio - the Yaesu FT-8000.
I have lots of experience coding, and am familiar with Python. I have read the developer docs and I'm trying to follow the 'Using existing Chirp code' procedure, but running into a snag.
I see there's a driver for the FT-8100, and it's my understanding that the 8100 was based on the 8000, with the main differences being the 8100 has twice as many memories, and a removable front panel.
Using the 8100 driver, I can initiate a download from the FT-8000 but when the FT-8000 stops sending its data (it is sending less data than the 8100 driver expects) instead of giving me the option to save the 'incomplete' dump, the process just times out and fails, and the incomplete capture is lost.
I can see the progress bar advances to about 75% then it stops, and then I get the error that the radio stopped responding and the download is gone.
Contrary to the instructions in the 'Add a Radio' document, I never get the chance to save the image.
Is there a toggle or setting I need to switch somewhere, or some code I need to change, that will let me save 'incomplete' reads rather than Chirp just dropping them after it times out?
FWIW I am running on OSX 10.12.4 and using the latest version of Chirp, 20170420 at the moment.
I can confirm that my set-up works fine on other radios; I have successfully used the same cable and Chirp to program a Yaesu FT-7900.
Thank you!
73 de Stephanie va3uxb
On Wed, Apr 26, 2017 at 8:01 AM, Stephanie Maks via chirp_devel chirp_devel@intrepid.danplanet.com wrote:
Using the 8100 driver, I can initiate a download from the FT-8000 but when the FT-8000 stops sending its data (it is sending less data than the 8100 driver expects) instead of giving me the option to save the 'incomplete' dump, the process just times out and fails, and the incomplete capture is lost.
I can see the progress bar advances to about 75% then it stops, and then I get the error that the radio stopped responding and the download is gone.
Contrary to the instructions in the 'Add a Radio' document, I never get the chance to save the image.
Is there a toggle or setting I need to switch somewhere, or some code I need to change, that will let me save 'incomplete' reads rather than Chirp just dropping them after it times out?
I would use a debugger or edit the download routine to print the length as it is downloading. Once you know the number of bytes it's sending, plug that into _memsize and you won't get the error message anymore.
Tom
Thanks for the suggestion Tom.
I tweaked the download routine to give me sizes but I was getting different numbers each time, and even at that I still couldn't get it to give me a save option. Ontop of the timeout, then there's checksums and model checks etc etc. It just seems like there is no way to force Chirp to let you save the image data unless everything is perfect.
In the end I went ahead and coded a save step right into yaesu_clone.py so for now every time I read from any yaesu radio I get a binary dump of the read on my desktop.
With that I'm finally able to get started mapping out the memory, and already made some progress with it.
Cheers & 73 de Stephanie va3uxb
On 2017-Apr-26, at 11.14.25, Tom Hayward tom@tomh.us wrote:
On Wed, Apr 26, 2017 at 8:01 AM, Stephanie Maks via chirp_devel chirp_devel@intrepid.danplanet.com wrote:
Using the 8100 driver, I can initiate a download from the FT-8000 but when the FT-8000 stops sending its data (it is sending less data than the 8100 driver expects) instead of giving me the option to save the 'incomplete' dump, the process just times out and fails, and the incomplete capture is lost.
I can see the progress bar advances to about 75% then it stops, and then I get the error that the radio stopped responding and the download is gone.
Contrary to the instructions in the 'Add a Radio' document, I never get the chance to save the image.
Is there a toggle or setting I need to switch somewhere, or some code I need to change, that will let me save 'incomplete' reads rather than Chirp just dropping them after it times out?
I would use a debugger or edit the download routine to print the length as it is downloading. Once you know the number of bytes it's sending, plug that into _memsize and you won't get the error message anymore.
Tom
participants (2)
-
Stephanie Maks -
Tom Hayward