Nate,
I recently went through a similar experience with the TH-7800 driver. I used Serial Port Monitor 6 to "sniff" the serial traffic while uploading and downloading the radio via the OEM software. The TYT software is really limited, but it does that part well. Once I figured out the protocol, it was easy to modify the a very similar driver to work. I'm betting Alinco has their own software you can do this with. Good luck! :)
Regards, Nathan
On Sun, Jun 12, 2016 at 7:45 AM, Nate Bargmann via chirp_devel < chirp_devel@intrepid.danplanet.com> wrote:
Hello all.
I have two Alinco DR-635T radios and am looking to CHIRP as a way to manage the memories between them. I recently purchased an interface cable and decided to test things this morning. I am aware the radio is presently not supported and have read bug 313 and the three other bugs requesting support for this radio.
I added the patch supplied by Richard Shaw in bug 313 to chirp/drivers/alinco.py with a modification to the 2 meter range changing 335000000 to 136000000. After verifying my adapter is to be found at /dev/ttyUSB0, I connected the cable to the powered off radio and then powered it back on. As my modified version of CHIRP now shows the DR-635T, I tried to download from it and received the following failure in the terminal I launched chirpw from:
ERROR: -- Exception: -- ERROR: Traceback (most recent call last): File "/home/nate/git/chirp.hg/chirp/ui/clone.py", line 238, in run self.__radio.sync_in() File "/home/nate/git/chirp.hg/chirp/drivers/alinco.py", line 196, in sync_in self._mmap = self._download(self._memsize) File "/home/nate/git/chirp.hg/chirp/drivers/alinco.py", line 138, in _download data += self._download_chunk(addr) File "/home/nate/git/chirp.hg/chirp/drivers/alinco.py", line 116, in _download_chunk raise errors.RadioError("No response from radio") RadioError: No response from radio
ERROR: ---------------- ERROR: Clone failed: No response from radio ERROR: --- Exception Dialog: No response from radio --- ERROR: None
I also tried setting the radio into clone mode as the master while attempting to read from CHIRP and received the same error text as above.
What is my next step for trying to read the memory data?
This is new territory for me as I've been involved with the Hamlib project for some time and am used to working with (mostly) documented protocols. As I see it the radio *should* be capable of being supported by CHIRP as a proprietary program claims support.
73, Nate N0NB
--
"The optimist proclaims that we live in the best of all possible worlds. The pessimist fears this is true."
Ham radio, Linux, bikes, and more: http://www.n0nb.us _______________________________________________ chirp_devel mailing list chirp_devel@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_devel Developer docs: http://chirp.danplanet.com/projects/chirp/wiki/Developers