1
General discussion forum / Re: FT8900 and proper settings
« on: 2019-03-11, 04:36:00 »
Been awhile since my previous post on this but I've done a lot of tinkering with the screen flickering and TX/RX dropping when remoting the FT-8900. Hope this follow-up helps anyone else trying to use the FT8900 from afar.
I have numerous pairs of RRC1258MkIIs units and tried both hardware v7 units and v5 units.
Same results, the screen flickers and the TX drops, but only for the duration of the flicker.
All units are running 2.90 firmware.
Other radios (TS-480 & FT-857) across the very same VPN don't exhibit any appreciable problems but there are other posts discussing the FT-8900 screen flicker so it's gotta be something specific about that model of radio. My guess is the head and body exchange data frequently and there's some watchdog timer (in either the radio body's CPU or the control head micro) kicking in when it does not see the data for more than a few tens of milliseconds.
All that said when the radio and control units are plugged into the same Ethernet switch (or even on the same LAN anywhere in the building) there are no problems, so the FT-8900 must be very unforgiving when the latency between the heard and body increases beyond a certain level.
After a lot of experimenting I managed to minimise (but not eliminate) the problem by moving that particular radio/control RRC pair to a second tunnel connection (3G on one end, ADSL2+ on the other) and then going to the advanced section of both the radio and control units and setting the UDP cmd min-data-size to 50. Putting the units on the secondary connections alone helped a little but increasing the minimum UDP packet size seems to help a lot. I also set the radio side's RTP tx mode to Squelch and the control side RTP tx mode to Normal. The flickers and TX dropouts have gone from every few seconds to one or two every couple of minutes or so. The "screen blank or dark" duration is now very short, as in blink and you'll miss it. So it's not a fix, but the problem is almost negligible for casual repeater chatter.
73,
Pat
I have numerous pairs of RRC1258MkIIs units and tried both hardware v7 units and v5 units.
Same results, the screen flickers and the TX drops, but only for the duration of the flicker.
All units are running 2.90 firmware.
Other radios (TS-480 & FT-857) across the very same VPN don't exhibit any appreciable problems but there are other posts discussing the FT-8900 screen flicker so it's gotta be something specific about that model of radio. My guess is the head and body exchange data frequently and there's some watchdog timer (in either the radio body's CPU or the control head micro) kicking in when it does not see the data for more than a few tens of milliseconds.
All that said when the radio and control units are plugged into the same Ethernet switch (or even on the same LAN anywhere in the building) there are no problems, so the FT-8900 must be very unforgiving when the latency between the heard and body increases beyond a certain level.
After a lot of experimenting I managed to minimise (but not eliminate) the problem by moving that particular radio/control RRC pair to a second tunnel connection (3G on one end, ADSL2+ on the other) and then going to the advanced section of both the radio and control units and setting the UDP cmd min-data-size to 50. Putting the units on the secondary connections alone helped a little but increasing the minimum UDP packet size seems to help a lot. I also set the radio side's RTP tx mode to Squelch and the control side RTP tx mode to Normal. The flickers and TX dropouts have gone from every few seconds to one or two every couple of minutes or so. The "screen blank or dark" duration is now very short, as in blink and you'll miss it. So it's not a fix, but the problem is almost negligible for casual repeater chatter.
73,
Pat