[CA] [CA11] Software Glitch - Axiom 12

[Chuck - Raymarine - Moderator]

David,

Bump. Our engineering team has requested a NMEA 2000 log from the system in support of this investigation. The diagnostic NMEA 2000 logging feature may be accessed via the command sequence HOME->SETTINGS->NETWORK->DIAGNOSTICS->NMEA DEVICES & MESSAGES. Please capture approximately 1 minute of data with the system fully up and engines operating. Please attach the resulting NMEA 2000 log to this thread.

[[email protected]]

Here is the layout of my network. I will upload a log later during the week-end.
David

[Chuck - Raymarine - Moderator]

Thanks David,

We'll be looking forward to receiving the logs. Typically, the Mercury NMEA 2000 gateway would have been interfaced directly to the marine electronics backbone including the Raymarine products. Should you have installed the Yacht Devices NMEA Bridge YDNB-07 for any specific filtering purpose, then please elaborate.

[[email protected]]

Hello Chuck,
Connecting the Mercruiser Gateway directly to the electronics backbone was giving errors such as:
1- Conflicting Trim tabs position reading
2- Intermitent false water temp reading
3- Engine Transmission error (No transmission on my boat, only gear mode is valid...)
4- J1939 Message creating error on the Logs (Axiom & I70s)

Here is the custom filters I have loaded in the YatchD device:

# Current configuration of Yacht Devices NMEA 2000 Bridge
# Firmware: 1.31 17/07/2019
# Serial: 000xxxxx, Password level: 0
# CAN1 connected to the Mercruiser Gateway
# CAN2 connected to the Raymarine SeatalkNG Network

PGNS_TO_ASSEMBLY=
FW_CAN1_TO_CAN2=ON
FW_CAN2_TO_CAN1=OFF
CAN1_HARDWARE_FILTER_1=0x00000000,0x00000000
CAN2_HARDWARE_FILTER_1=0x00000000,0x00000000
CAN2_SPEED=250

match(CAN1, 0x01FE1000, 0x01FFFF00)
{
# Block message about TrimTab from CAN1
}

match(CAN1,0xEF,0xFF)
{
# Block message for Engine with EF in J1939
}

match(CAN1,00,0xFF)
{
# Block message for Engine with 00 in J1939
}

match(CAN1,01,0xFF)
{
# Block message for Engine with 01 in J1939
}

match(CAN1, 0x1F20500, 0x1FFFF00)
{
a=get(DATA,UINT8)
if (a < 0x11) {
send(CAN2)
}
# Block message with transmission data except gear mode
}

match(CAN1, 0x01FD0600, 0x01FFFF00)
{
a=get((DATA + 1),UINT32)
if (a > 0xffff5d07) {
send(CAN2)
}
# Block Negative temperature (Bad reading) on Water Temp
}

Let me know if additionnal info is required.
Kind Regards,
David

[Chuck - Raymarine - Moderator]

David,

Were you able to collect the requested logs over the weekend.

[[email protected]]

Unfortunately not, the weather was not so great here... Will definitely do it during next week-end. Season is almost over here...
Sorry for the delay.

[Chuck - Raymarine - Moderator]

Thanks David,

Our final boating day was this past Sunday morning and the weather was obsimal in New Hampshire's Lakes Region. Your logs will aid greatly in solving this issue. As you can see from this and another similar thread within the Forum, we presently have three others reporting problems with the Fuel Manager feature in conjunction with the Mercury engine gateway. Logs have been requested from them as well. Hopefully, all will respond with the requested logs to support this investigation.

[[email protected]]

Hello Chuck,
Here is couple log I was able to get. This include engine start and cruising at 30mph. I'm including the diagnostic file that outlilne all peripheral on my network. Keep in mind that my Mercruiser Gatway is filtered by my YATCHD bridge preventing some data to be transfer to the electronic network. (J1939 engine data...See list on the other post)
The boat is going out of the water on Wednesday night (oct 16). Let me know before if additional test is required to help.
David

[[email protected]]

Hello Chuck,
Here is another interesting snapshot I took on my way back. I also did another log but the fuel manager was already corrupted when I start logging.
Kind Regards,
David

[Chuck - Raymarine - Moderator]

David,

Thanks for the requested data. I have added them to the engineering problem report accordingly and have notified the engineering team of that the request for logs has been answered.