CHIRP

Hi Anthony,

Looking at the serial logs I can tell this radio is not a clone of the BTECHs & family, it's a completely new model. In your serial logs are the 40% of the info to make a driver from it, I'm very busy right now.

If you offer to loan a radio of these maybe some other developer can pick it up and build a driver for it. At a glance the download/upload is straight forward and channel data looks not very complicated.

I'm busy with work now and I live in Cuba, radio transceivers import/export from here is a no go (for now, I have a bird telling me this may change in a very near future, I hope for this to happen soon)

73 Pavel CO7WT

I got a spare time and I get into playing with your logs and I found this:

Radio comms baud-rate & parity are not clear at this time

To put radio in Clone mode send "PROM_LIN" in binary, radio answer with the classic ACK (\x06)

From this point forward you simply ask for data with the syntax: "READ" + 2 bytes of address + one unknown byte + one byte for the data payload. Apparently there is no header in the data and no ACK for the received data.

So far this is the most wide range identified: 0x0400-0x1C00 But the radio has another mem zones, it will be fun to hack into it...

73.

This appears to be complete.