[TG] [TG11] ECI-100 & STW

[Tom - Raymarine - Moderator]

Thanks Bernie.

There are two different sources of 128259 in that log, from devices with addresses 0 and 1 (the engines), one with no/invalid data and one with zeroes:

Line 15: Rx 297247 09 f5 03 01 ff ff ff ff ff ff ff ff From:01 Speed STW:--kts
Line 28: Rx 297340 09 f5 03 02 ff 00 00 ff ff ff ff ff From:02 Speed STW:0.00kts
Line 41: Rx 297447 09 f5 03 01 ff ff ff ff ff ff ff ff From:01 Speed STW:--kts
Line 54: Rx 297540 09 f5 03 02 ff 00 00 ff ff ff ff ff From:02 Speed STW:0.00kts
Line 69: Rx 297647 09 f5 03 01 ff ff ff ff ff ff ff ff From:01 Speed STW:--kts
Line 80: Rx 297740 09 f5 03 02 ff 00 00 ff ff ff ff ff From:02 Speed STW:0.00kts
Line 100: Rx 297847 09 f5 03 01 ff ff ff ff ff ff ff ff From:01 Speed STW:--kts
Line 114: Rx 297940 09 f5 03 02 ff 00 00 ff ff ff ff ff From:02 Speed STW:0.00kts


I would guess that the ECI may be not handling well the situation of two different Speed sources, one with invalid data, and bridging the wrong one (perhaps because of lower source address?) or bridging neither. I'll log a report on this.

The unexpected engine alarms you are seeing when connected bypassing the ECI are because Yamaha engines have a quirk where the set all of the Reserved bits in the Engine Status fields in 127489 Engine Parameters Dynamic to 1 instead of 0 (1 is the value for reserved bit fields in almost every other place in the NMEA2000 spec, but in this particular field the spec says they should be 0.) Our MFD interprets these reserved bits as flagged alarm states for alarm types that we don't yet know about (e.g. from a device programmed for a later version of the NMEA2000 spec.)
The ECI100 knows about this quirk and works around it, setting all those reserved bits back to 0.

Regards,
Tom