[chirp_users] Trying to use chirp via ser2net and socat
Hi, I wonder if anybody has tried this and can offer advice: I have chirp running on a laptop in my apt, but an FT8900 is in a boiler room one the roof. The remote control head for the radio is down in the apartment.
I can connect to the FT8900 by running a ser2net service up there and socat down here. With this setup and permissions all set OK using /dev/pts/5, I can see the FT8900 send a character when I put it into clone mode. But chirp will not recognise anything and gives me "Failed to communicate with radio: Failed to read header (0)"
I am using SuSE linux here and CentOS upstairs. I have tried setting the serial port up there to 1200, 4800, 9600 and 19200. I assume that chirp uses autobauding to communicate with the radio but that is obviously not available over a tcp connection.
Any help would be appreciated!
73 de Nigel ve3id
On 05/11/14 21:23, Nigel Johnson, MIEEE wrote:
I am using SuSE linux here and CentOS upstairs. I have tried setting the serial port up there to 1200, 4800, 9600 and 19200. I assume that chirp uses autobauding to communicate with the radio but that is obviously not available over a tcp connection.
I had a quick look in the source code and it appears to use 9600: class FTx800Radio(yaesu_clone.YaesuCloneModeRadio): """Base class for FT-7800,7900,8800,8900 radios""" BAUD_RATE = 9600
What you could do is to unplug the cable from the radio and connect the TX and RX pins together. (I don't know what the cable is so I don't know which pins this or how easy it would be to do.)
Once you do that any data you manage to send to the serial port will come straight back again, so you can test that the link is working, and it works at any baud rate.
On Wed, Nov 5, 2014 at 1:37 PM, Andrew ziltro@ziltro.com wrote:
What you could do is to unplug the cable from the radio and connect the TX and RX pins together. (I don't know what the cable is so I don't know which pins this or how easy it would be to do.)
Once you do that any data you manage to send to the serial port will come straight back again, so you can test that the link is working, and it works at any baud rate.
The Yaesu cable does this internally, so no modification necessary.
Tom KD7LXL
Hmmm, I am not seeing my characters come back if I telnet to it. Seems like I will have to take laptop up to boiler room and see if chirp will talk directly.
Thanks es 73 Nigel ve3id
On 11/05/2014 05:33 PM, Tom Hayward wrote:
On Wed, Nov 5, 2014 at 1:37 PM, Andrew ziltro@ziltro.com wrote:
What you could do is to unplug the cable from the radio and connect the TX and RX pins together. (I don't know what the cable is so I don't know which pins this or how easy it would be to do.)
Once you do that any data you manage to send to the serial port will come straight back again, so you can test that the link is working, and it works at any baud rate.
The Yaesu cable does this internally, so no modification necessary.
Tom KD7LXL _______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users
Hmm, interesting. I didn't realise it was half duplex. I have tried telnetting to the port and the only echo I get is the carriage return, then nothing. Time to get the scope out :-)
73 NIgel ve3id
On Wed, Nov 5, 2014 at 1:23 PM, Nigel Johnson, MIEEE nw.johnson@ieee.org wrote:
Hi, I wonder if anybody has tried this and can offer advice: I have chirp running on a laptop in my apt, but an FT8900 is in a boiler room one the roof. The remote control head for the radio is down in the apartment.
I can connect to the FT8900 by running a ser2net service up there and socat down here. With this setup and permissions all set OK using /dev/pts/5, I can see the FT8900 send a character when I put it into clone mode. But chirp will not recognise anything and gives me "Failed to communicate with radio: Failed to read header (0)"
I am using SuSE linux here and CentOS upstairs. I have tried setting the serial port up there to 1200, 4800, 9600 and 19200. I assume that chirp uses autobauding to communicate with the radio but that is obviously not available over a tcp connection.
Any help would be appreciated!
73 de Nigel ve3id
The FT-8900 uses 9600 serial, but it can't actually receive data that fast. It's picky about timing. Chirp sends it 64 bytes of data, waits for an ACK, then waits another 50 ms for the radio to finish before sending the next block. Your network link may be messing up this timing.
First step is to try again at 9600.
Tom KD7LXL
Thanks for that. At least if I know to start at 9600 I can try other things without worrying that one problem is masking another.
73, Nigel ve3id
On 11/05/2014 04:50 PM, Tom Hayward wrote:
On Wed, Nov 5, 2014 at 1:23 PM, Nigel Johnson, MIEEE nw.johnson@ieee.org wrote:
Hi, I wonder if anybody has tried this and can offer advice: I have chirp running on a laptop in my apt, but an FT8900 is in a boiler room one the roof. The remote control head for the radio is down in the apartment.
I can connect to the FT8900 by running a ser2net service up there and socat down here. With this setup and permissions all set OK using /dev/pts/5, I can see the FT8900 send a character when I put it into clone mode. But chirp will not recognise anything and gives me "Failed to communicate with radio: Failed to read header (0)"
I am using SuSE linux here and CentOS upstairs. I have tried setting the serial port up there to 1200, 4800, 9600 and 19200. I assume that chirp uses autobauding to communicate with the radio but that is obviously not available over a tcp connection.
Any help would be appreciated!
73 de Nigel ve3id
The FT-8900 uses 9600 serial, but it can't actually receive data that fast. It's picky about timing. Chirp sends it 64 bytes of data, waits for an ACK, then waits another 50 ms for the radio to finish before sending the next block. Your network link may be messing up this timing.
First step is to try again at 9600.
Tom KD7LXL _______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users
participants (4)
-
Andrew -
Nigel Johnson -
Nigel Johnson, MIEEE
-
Tom Hayward