CHIRP

How did you create the dump of the serial communications?

Jim KC9HI

Jim Unroe wrote:

How did you create the dump of the serial communications?

Jim KC9HI

I used a windows program called "Serial Port Monitor", this is the html output from that. I didn't have a working linux / wine setup at the time. There's a much better chance I can get things working under wine now that I have the right hardware combination. I will try to get that working if needed.

The communication here should include a full read of the memory, and two writes to memory.

john Terry wrote:

Jim Unroe wrote:

How did you create the dump of the serial communications?

Jim KC9HI

I used a windows program called "Serial Port Monitor", this is the html output from that. I didn't have a working linux / wine setup at the time. There's a much better chance I can get things working under wine now that I have the right hardware combination. I will try to get that working if needed.

OK. That is what I use here. I just export the "dump" view to a *.txt file. The reason I asked was I am trying to locate something simple-to-use and free that I can tell others to use to capture the transfer from/to their radio like you did.

Jim KC9HI

Jim Unroe wrote:

A patch has been submitted. Support should be in the next CHIRP daily build following acceptance.

Jim KC9HI

That's amazing! Thanks Jim! I look forward to giving it a spin!

Jim Unroe wrote:

john Terry wrote:

Jim Unroe wrote:

How did you create the dump of the serial communications?

Jim KC9HI

I used a windows program called "Serial Port Monitor", this is the html output from that. I didn't have a working linux / wine setup at the time. There's a much better chance I can get things working under wine now that I have the right hardware combination. I will try to get that working if needed.

OK. That is what I use here. I just export the "dump" view to a *.txt file. The reason I asked was I am trying to locate something simple-to-use and free that I can tell others to use to capture the transfer from/to their radio like you did.

Jim KC9HI

FWIW, I did try both the wine approach, and the USBPCap approach to no avail. I may have gotten the USB way to work eventually with enough futzing. In this case, the radio software was using some serial API not yet implemented by wine, and raising a NotImplemented System.IO.Ports.SerialPort.set_ReceivedBytesThreshold error. The USBPcap method might've worked for me eventually, but I couldn't seem to get the right capture filter, and when I thought I had it, the file was only 2KB with very little in it when opened in wireshark... I'm not a windows user so this was difficult.

What I wanted to try was running a Windows VM on linux and passing through & sniffing the serial port from linux. I guess maybe next time ;)

I'd love to look at the patch, but I can wait until its in a mainline branch. Just curious, I was staring at the code myself for a while, but couldn't quite get it.