Serial connection hangs after 10 seconds (TS-570)

[pa4m]

Hi,

I have been using remoterig successfull with a TS-480. But now I want to get my TS-570 working with remoterig. I made all the cables and did the configurations. Everyting is working except the CAT control via remoterig.

When I connect the TS-570 directly to my computer cat control does work fine (9600, 8, 1, N). But with remoterig in between HRD gives a disconnect message after +/- 10 seconds. I am using COM2 on remoterig.

When the disconnect message appears in HRD there are 2 ways to get the connection run again:
1. switch off and on the TS-570, the connection is working again for +/- 10 seconds
2. Remove both serial cables from radio RRC  and control RRC and put them together (remoterig is bypassed).

When the connection drops out  "CTRL" is not longer displayed in the TS-570 display, but after switching off and on the TS-570 CTRL is displayed again. (CTRL indicates the radio is controled via serial).

It looks like the TS-570 does not like the delay? Both remoterig boxes are on my desk connected to a switch.

Iam using COM mode 4, 9600  baud, 8, 1 , 0 ,00

I also tried COM1 but it did not help.

2 standard RS-232 cables are used (male-female), 1 with a gender changer (between radio-rrc and radio).

[dj0qn]

Just to make sure: did you change the RRC's to program mode 4 from 5?

73,
Mitch DJ0QN / K7DX

[pa4m]

Just checked.

Both RRC's: Radio settings> program mode> 4 - Yaesu, Kenwood, Elecraft.

[pa4m]

Settings

Unit ID (Banner)   Control RRC in shack
DHCP   0
IP   192.168.178.3
Netmask   255.255.255.0
Gateway   192.168.178.1
Dns server   212.54.44.54
Eth-type   5
IP-interface   0
Web page user   
Web page pwd   
Web page user(saving)   
Web page pwd(saving)   
Program mode   4
Control panel   1
Sip password   
Sip contact(Radio RRC IP/hostname)   192.168.178.2
Auto connect   0
Audio quality   5
Audio dual-rx   0
Audio left/right ch swap   0
Codec out gain   255
Codec inp gain   18
Codec inp HPF Hz   3
Codec inp preamp   1
Codec inp attenuation   0
COM0 baudrate   57600
COM0 data bits   8
COM0 stop bits   1
COM0 parity   0
COM0 Program mode 3 char timeout   2
Use USB Com Port as COM0   0
COM1 mode   0
COM1 baudrate   9600
COM1 data bits   8
COM1 stop bits   1
COM1 parity   0
COM1 rts/cts   0
COM1 terminator (hex)   00
Use USB Com Port as COM1   0
COM2 mode   4
COM2 baudrate   9600
COM2 data bits   8
COM2 stop bits   1
COM2 parity   0
COM2 terminator (hex)   00
Use USB Com Port as COM2   0
COM3(Extra) mode (USB-COMFSK)   0
UDP cmd port   13002
UDP audio port   13001
SIP port   13000
Web server port   80
Telnet server port   23
Rx jitter buffer size   4
Rx jitter delay   3
Audio packet size (ms)   20
RTP tx mode   0
Disable audio tones   0
Audio tones -db [70-0]   30
IP identification (morse)   0
Full duplex   0
PTT-off mute delay   0
IP Type-of-Service (dec)   0
Yaesu power-on/off   0
UDP antenna-switch port   13010
UDP cmd min-data-size   0
Use common network settings   0
Check interval   0
DDNS Host name   0
Own host name   

[dj0qn]

The only thing I see that should probably be changed is COM0 to 9600, otherwise it looks OK to me
If that doesn't solve it, then maybe there is a bug in the firmware. We should let the Microbit guys
answer that one.

They will need to know which firmware version you are using, so please send that.

73,
Mitch DJ0QN / K7DX

[pa4m]

Thanks for your help Mitch, it is much appreciated.

I changed com0 to 9600. Iam using the latest firmware.


Info

Name   Value
Company   Microbit
Product   1258
PID   4
Version   7
HW   8
Software   2.90
Bootloader   1.10
Compiler   4.6.2
Build   Feb 17 2016 10:16:14
ROM/RAM   481192/44080
ETH-RAM   2944 (max 3kB)
USB-RAM   15352 (max 16kB)
Battery-RAM   4
ResetSrc   0 [3]
Last WD Reset   9
Uptime   0 Days, 0 Hours, 0 Mins, 8 Secs
    
Serial number   7331
MAC address   00:1e:fd:01:93:43
IP address   192.168.178.3
Netmask   255.255.255.0
Gateway   192.168.178.1
DNS   212.54.44.54
Wi-Fi network   module not present

[sm2o]

Hi

I don't think there is anything that can be done in the Remoterig boxes which makes any improvement, They send the data the same way over com2 independent of which radio is in use, probably the TS-570 firmware is more critical than other. You can always try with mode 1 or 3 to see if it's any difference. Also test with an other PC-software, they may also be different.

73 de mike

[pa4m]

Hi Mike,

I tried mode 1 and 3. Mode 3 is a bit better and mode 1 is very slow and puts the TS-570 to wrong frequencies. 
I also installed a USB to RS-232 converter. It works better/longer now but after 5 minutes or so the connection goes down again. Will try another PC later.

If I switch over the cable to my TS-480 it all works fine with this setup and settings. So I agree with you the problem could be in the TS-570 firmware. Probably Iam the first person who is using a TS-570 with remoterig.

Mark.

[pa4m]

Ok. I tried another PC (win8)  with a Startech USB to RS232 converter. But still the same problem. My conslusion, the TS-570 is not suitable to work with remoterig unfortunately . 

[W1UE]

Mark

Have you tried using the USB cable and one of the Comports created by that cable to use for radio control?  I was leaving the USB cable connected all the time, as I do RTTY using RR, so I was leaving it connected all the time.  I configured whatever Comport was Microbit Com1 for radio control, and eliminated the serial cable.

Dennis W1UE

[pa4m]

Hi Dennis,
Iam not sure if I do understand your question completely but I tried the onboard comport (com1) on my laptop and 2 different USB to RS-232 converters (com9 and com10) and another laptop. The serial connection is needed to control the transceiver because the TS-570 does not have a separate front panel.

[Jan (Microbit)]

I think Dennis is referring to one of the virtual COM ports that are created when you connect the RRC to a PC via USB. They can be used(after enabling them) instead of the physical COM ports on the RRC.

[pa4m]

Ok got it know.
Will try to control the TS-570 via USB on control-rrc.

[pa4m]

It was worth trying it but com2 via USB did not solve this issue.
Thanks for your help anyway.

[Jan (Microbit)]

It was worth trying it but com2 via USB did not solve this issue.
Thanks for your help anyway.

Too bad, though mostly expected. We would need a TS-570 in order to be able to have a look if something could be changed, but it sounds like some kind of timing issue, which might not be possible to overcome.