The CPS for the XTS3000 only runs on Windows XP. Darn. So why not reverse the serial protocol? 
My physical setup:
Win XP <--FTDI crossover to another FTDI --> Linux Box <--USB to Serial--> XTS3000
I set the CPS to point to COM2, which is the FTDI in the WinXP box. The Linux code should receive the data, and transmit it to the Linux box, which should then send that over to the XTS3000.
I wrote some C code on the Linux box that should transmit/logging data between the two parties. It seems to work for 30 seconds and is transferring data. Then suddenly fails. WHY???
Let me share my code and perhaps someone can give me some insights. Code here:
https://github.com/FarhansCode/serialsnooper/blob/master/snoop.c
You would run it as
./snoop /dev/ttyUSB0 /dev/ttyUSB1
Clearly data is transmitted back and forth, and then suddenly there's a non-descriptive "Unable to read radio" error.
Any ideas? This is my first real attempt at hardware reverse engineering.
My physical setup:
Win XP <--FTDI crossover to another FTDI --> Linux Box <--USB to Serial--> XTS3000
I set the CPS to point to COM2, which is the FTDI in the WinXP box. The Linux code should receive the data, and transmit it to the Linux box, which should then send that over to the XTS3000.
I wrote some C code on the Linux box that should transmit/logging data between the two parties. It seems to work for 30 seconds and is transferring data. Then suddenly fails. WHY???
Let me share my code and perhaps someone can give me some insights. Code here:
https://github.com/FarhansCode/serialsnooper/blob/master/snoop.c
You would run it as
./snoop /dev/ttyUSB0 /dev/ttyUSB1
Clearly data is transmitted back and forth, and then suddenly there's a non-descriptive "Unable to read radio" error.
Any ideas? This is my first real attempt at hardware reverse engineering.