New Model #2909
openSainSonic RST599
0%
Description
"SainSonic RST599":http://www.sainsonic.com/two-way-radio/sainsonic-rst-series/sainsonic-rst599-136-174-400-520mhz-uhf-vhf-2m-70cm-handheld-radio-ars-ip66.html is a supposedly water-resistant unit. I'm not sure whether this is a yet another clone of Baofeng. "SainSonic":http://www.sainsonic.com/ manufactured(?) "something for Baofeng":http://www.sainsonic.com/two-way-radio/baofeng-gt-series.html called GT-3 and GT3-TP, but all these seem different from canonical UV-5R.
I've set up hub4com using signed driver from com0com on Win 8.1 64 bit and intercepted communication while reading settings off the radio that I'm about to attach.
Files
Updated by Mikhail Titov over 8 years ago
Failed to mention about the log, COM3 is provided by USB VCP with the radio on the other side, and COM4 is "plugged" into COM5 used by original software.
Original software uses dot ysF files. And it looks like data extraction is initiated with "06 59 41 53 48 45 ff ff" that has "YASHE" in it. Also "LiSheng" is being transmitted and stored in dumps by original software. I haven't seen any dot py files having anything alike.
Also I'm attaching a copy of original dump saved by original software.
Updated by Dux Mux over 8 years ago
I own this radio, I'm proficient in Python but I didn't do much serial/HW programming. Is there anything I can do to make RST599 driver? Where should I start. I can read and learn from existing drivers, but I'd rather not brick the device.
Updated by Pavel Milanes over 8 years ago
Hi Dux Mux, WELCOME !!!
I'm a recent addition to the developer list in Chirp, you can found help here [[[http://chirp.danplanet.com/projects/chirp/wiki/Developers]]]
From my work flow I can suggest this steps:
1 - Capture the download process (logs already attached to this issue) and analyze it to get and idea of the comm process
2 - Make a standalone script like this [[[http://chirp.danplanet.com/attachments/2105/uv5001.py]]] it don't state the Licensing, it's GPL 2.0, I'm the author, feel free to use it as skeleton. (This stand alone script will make your life easier on step 6) See the original issue to know more [[[http://chirp.danplanet.com/issues/3015]]]
3 - Once you have success in the download part of the script, then make the upload part work.
4 - Study the similar drivers already in chirp to determine if this radio is a clone of others or need a new driver
5 - Start a driver from the template and/or adapt the present "similar" driver on a file apart; all you have is to port/modify the code in your stand alone script.
6 - Start the mapping function, use the script to automate the process of mapping the radio mem and the tips on the developer pages on the wiki.
7 - Code until you have everything working.
Don't be afraid to brick your radio.
Use the factory software to save a copy of the mem/settings and if something goes wrong just download the backup copy with the original software.
Don't be afraid to ask.
Updated by Mikhail Titov over 8 years ago
Hey, Dux Mux!
I didn't end up finalizing things and got carried away with other projects. If you want something to start with a partly deciphered data structures, here is the gist I just uploaded https://gist.github.com/mlt/d145fa0ef48ccc7a4e04 . It is more or less usable as is, but as I said I haven't touch it in a few months :(
The decision I failed to made is whether we should use data format compatible with original software or not. It would be really nice to make it compatible and it is doable, however forgetting about compatibility would be easier...
Updated by Mikhail Titov over 8 years ago
And here is another gist https://gist.github.com/mlt/d2e41c9855c2c993ab89 you might find useful just to fetch data from RST599 as is outside of Chirp.