[chirp_devel] Need help with tracing/logging serial communication

Leo Bärring
Sun Oct 16 09:16:21 PDT 2016


I can't really advise on how to solve the situation in windows, since I'm a linux guy,
but since I did my protocol snooping on the hardware side, /that/ part should be
the same, if you're not averse to a little hardware hacking, and can find the right
software to dump serial data (as in just listen to the port, not listening in on a port
that some other program is using).

What I did was to open up the programming cable, so that I could get at the RX
and TX lines, and then listened in on these lines by also connecting them to
the RX lines of two more serial ports. Then I just listened to the data arriving
on the additional ports with regular serial dumping software. (I used jpnevulator,
which can listen on multiple ports, so I get the back and forth interleaved correctly,
but it's linux only.)

You need two additional serial ports of course, whether regular hardware or usb
to serial converters. And you need to take care to make sure that the the voltage
levels are correct, that is some serial devices use rs232 voltage levels, some
devices use 5V logic levels. You may need to pass data through e.g. max232
chips to convert levels where appropriate.

/Leo








-------- Original Message --------
Subject: [chirp_devel] Need help with tracing/logging serial communication
Local Time: October 16, 2016 5:29 PM
UTC Time: October 16, 2016 3:29 PM
From: chirp_devel at intrepid.danplanet.com
To: chirp_devel at intrepid.danplanet.com

Hello!

We are currently running an amateur radio license training and will
provide all successful participants (hopefully about 30) with Alinco DJ
500. The Alinco software does it's job, but I want to have support for
that model in CHIRP.
I'm happy to see that CHIRP is written in Python and does a very nice
job in doing all this bit and structure shuffling.

I have a running programming setup, that is the HT, original FTDI-based
USB Serial converter and the software, running in Virtualbox 4.3 both
Windows XP 32 bit and Windows 7 32 bit.
Now I followed
http://chirp.danplanet.com/projects/chirp/wiki/DevelopersAdd_a_Radio
and tried to get a trace of the communication while reading/writing the
channels.

Unfortunately Portmon 3.02, the last version that was published, does
not support Windows 7. I tried compatibility settings for XP, not
better. I tried Portmon in Windows XP, no trace possible. Portmon simply
does not offer to trace at all.

What are your experiences with working setup?
Which recommendations can you give me?

Best Regards

73 de Patrick OE6PSE
--
Engineers motto: cheap, good, fast - choose any two
Amateur Radio Operator / Ham / Funkamateur / QTH: JN77rb
http://oevsv.at/
One of the lucky 10.000: http://xkcd.com/1053
Use Mail Encryption Today! PGP Key ID: 0xDF8A127E5A120903
Patrick Strasser-Mikhail OE6PSE <oe6pse at oevsv dot at>
_______________________________________________
chirp_devel mailing list
chirp_devel at intrepid.danplanet.com
http://intrepid.danplanet.com/mailman/listinfo/chirp_devel
Developer docs: http://chirp.danplanet.com/projects/chirp/wiki/Developers
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://intrepid.danplanet.com/pipermail/chirp_devel/attachments/20161016/b19b2eb0/attachment-0001.html 


More information about the chirp_devel mailing list