[chirp_devel] Decoding the TYT TH-UV88
I’ve got one of these radios on order, but notice that Jim Unroe has uploaded a portmon capture on the open issue so thought I’d start having a look. Some caveats, I’m just reading source; I’m not a python programmer; and I don’t have the radio in my hands yet. I’m just trying to get ahead of the game!
However, it seems that it doesn’t follow the protocol I see in the other TYT radio drivers. It looks like the ICOM CIV clone standard, as described in icf.py. I also found this reference online which corresponds with the file - http://www.oocities.org/blakkekatte/clone/icomclonedoc.pdf
However, the capture shows that the after the clone retrieval command the software starts downloading blocks instead of the whole memory (this is from Jim’s capture)
189 0.00012079 TH-UV88.exe IRP_MJ_WRITE ProlificSerial0 SUCCESS Length 12: FE FE EE EF EB 00 00 00 00 00 20 FD 281 0.00000316 TH-UV88.exe IRP_MJ_READ ProlificSerial0 SUCCESS Length 45: FE FE EF EE E4 00 00 00 00 00 20 B8 CD A4 02 B8 CD A4 02 FF 0F FF 0F 00 00 04 20 20 20 20 20 20 78 17 DE 00 78 17 DE 00 FF 0F FF C3 FD 283 0.00018276 TH-UV88.exe IRP_MJ_WRITE ProlificSerial0 SUCCESS Length 12: FE FE EE EF EB 00 00 00 20 00 20 FD 375 0.00000355 TH-UV88.exe IRP_MJ_READ ProlificSerial0 SUCCESS Length 45: FE FE EF EE E4 00 00 00 20 00 20 0F 00 00 04 20 20 20 20 20 20 E4 03 08 01 E4 03 08 01 FF 0F FF 0F 00 00 06 20 20 20 20 20 20 A8 83 FD
This command – EB – is not listed anywhere I can find, but it looks like it is asking for a block of memory at a time.
This will be enough, I think, for me to read the memory when I get the radio – so this is a style question. Should I base my attempts off the icf.py - or because this is an alternate implementation perhaps I should copy it into a new file specifically for the TH-UV88 until it is clear if other radios use this style of communication? I’m guessing the clone out will similarly be block based when I get the radio.
Best wishes James
participants (1)
-
James Berry