[chirp_devel] [GE-PCS] adding support for ge pcs, odd handshaking

[Jens J.]

Ok looking at tmv71.py code, seems like I could do something like this in __init__?

self.pipe.setBaudrate(300)
self.pipe.write("\x00")
self.pipe.setBaudrate(1200)
....

?



________________________________
 From: Jens J. <kd4tjx at yahoo.com>
To: "chirp_devel at intrepid.danplanet.com" <chirp_devel at intrepid.danplanet.com> 
Sent: Friday, July 26, 2013 5:34 PM
Subject: [chirp_devel] [GE-PCS] adding support for ge pcs, odd handshaking
 


I'm considering writing a new radio driver from scratch for older GE/Ericsson PCS radios. As usual, they have a proprietary, ancient dos-only program.
I was able to reverse engineer enough of the serial protocol to come up with these details:
http://pastebin.com/3jD6NESu


I'm reading over the example radio driver (template.py), but I have a question on how to do multi-baudrate handshaking:
That is, this radio seems to require me to send a null-byte at 300 baud, then switch to 1200 baud for regular programming. The radio is unresponsive to anything unless I handshake/reset with this.

So question - is it possible to switch baudrates, and how could I approach this?

On a few side notes - a developer wiki page for basic getting started would be welcome, e.g., for programming a new driver, look at template.py and chirp_common.py.. This wasn't obvious and even then, some things arent fully explained. A wiki page outlining a high-level approach to writing a new driver would be awsome.
Also, was thinking it would be helpful to have a wiki page on techniques for reverse engineering radio programming protocols, such as using "serial port monitor" etc.


-Jens
_______________________________________________
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/20130726/4e198322/attachment-0001.html