What program are you using to capture the trace?  Wouxun typically encodes the data transfer to and from the radio so using the factory CPS shows the encoded data.   

I have done more than 10 wouxun radio drivers and in all of them,  the per channel tones are part of the 16 bytes of memory for each channel.  In fact they have always been bytes 8 and 9 and bytes 10 and 11.   

I would have you take a look at one of the drivers already in existence for clues....the 935G or the 980P drivers would show how a typical memory map is laid out for the recent wouxun radios.   
If you have images downloaded from chirp for the 805 I can take a look.   

There is also the chance that the 805 uses a comm protocol that has not been decoded yet and it can be fooling you. The 916 and the S88 are radios that seem to use a comm protocol that is not as "predictable" as the 935G or the 980p. 


Mel

On Sat, Mar 22, 2025, 8:43 PM Chris Mildebrandt via Developers <developers@lists.chirpmyradio.com> wrote:
Hello,

I'd love some help creating a driver for the Wouxun KG-805g radio (https://chirpmyradio.com/issues/11214). I've performed captures of all the settings, they can be found here: https://github.com/mildebrandt/kg805g

Looking at the trace files, I'm a little confused about the memory layout. I changed the R-CTC setting from "off" to "67.0" on channels 3, 4, and 13. Here are the differences:

CH03: change is at the 89th position
<570010405062254650622546ffffffff95ffffff5087254650872546ffffffff95ffffff5012264650122646ffffffff95ffffff5037264650372646ffffffff95ffffff
<570010405062254650622546ffffffff95ffffff5087254650872546ffffffff95ffffff50122646501226469e02ffff95ffffff5037264650372646ffffffff95ffffff

CH04: change is at the 121st position
<570010405062254650622546ffffffff95ffffff5087254650872546ffffffff95ffffff5012264650122646ffffffff95ffffff5037264650372646ffffffff95ffffff
<570010405062254650622546ffffffff95ffffff5087254650872546ffffffff95ffffff5012264650122646ffffffff95ffffff50372646503726469e02ffff95ffffff

CH13: change is at the 25th position
<5700d0405087764650877646ffffffff95cfffff5012774650127746ffffffff95cfffff0050254600502546ffffffff95ffffff0075254600752546ffffffff95ffffff
<5700d04050877646508776469e02ffff95cfffff5012774650127746ffffffff95cfffff0050254600502546ffffffff95ffffff0075254600752546ffffffff95ffffff
 
My uninformed thought would be that I'd see the bytes change in the same position for the same setting on each channel, but they seem to be all over the place.

What does this mean for me trying to lay out the memory? Am I being fooled by the trace output...and it's being recorded out of sequence? I wouldn't think so since the ordering looks to be stable per channel.

I'll describe my setup in case there's something weird there. I have an Intel Macbook Pro with Fedora Linux installed. In Fedora, I have a qemu Windows 10 machine that's running the Wouxun software. I'm running tshark on the Linux side to capture the USB traffic.

Any pointers would be appreciated. I'm pretty far over my head, but hopefully I can help get this radio into chirp. :)

Thanks!
-Chris
_______________________________________________
Developers mailing list -- developers@lists.chirpmyradio.com
To unsubscribe send an email to developers-leave@lists.chirpmyradio.com