S100 Remote

[[email protected]]

I have a Raymarine EV0 autopilot with S100 remote connected to it via a ST to STng converter. The S100 is unreliable at best. It will miss course alterations using the left or right arrow keys upwards of 20% of the time even though the S100 beeps acknowledging the input. On occasion it will miss two consecutive 1 degree course corrections and then the EVO will do a 20 degree course correction in the same direction. When doing a long key press for a 10 degree course change, it will accept the input move 10 degrees and then promptly cancel the course change and revert to the previous heading. Also on occasion when giving it a one degree course correction it will do the 1 degree and then do another 10 degrees. I have restricted my use of the S100 to course corrections of only a couple of degrees and then only in full view of the P70R.

The network is configured as:
Seatalk: S100, Autohelm Speed Instrument, Autohelm GPS, Autohelm Depth Instrument, ST to STng converter (Version 1.21)
Seatalk NG: EV-1 Course Computer (Version 2.17 ) , ACU-400 (Version 2.17)
NMEA 2000: Garmin 4212 MFD, Raymarine a68 (Version 17.45), AMEC AIS, Actisense NGT-1, Garmin GPS-17, Raymarine P70R (Version 3.05)
The EV-1 and ACU-400 are connected to the device ports on the ST-STng converter and the backbone port is connected via a backbone cable to the NMEA 2000 network backbone. The NMEA 2000 network provides power to the ST and STng networks.
The S100 remote shows 3 bars on the signal meter even when only inches from the base station. The actual distance in operation is less than 7 feet.
I have been unable to update the ST-STng converter to the latest software listed on the Raymarine web site as the a68 does not recognize the files I have downloaded as software. It recognized all other files in the a68 update.

My impression is the ST-STng converter doesn’t have the processing power to handle the autopilot inputs, in other words it misses the inputs.

Tom