[TG] [TG11] Axiom - Crash to boot screen - Vesper AIS NMEA2000 data
|
05-13-19, 06:08 PM
(This post was last modified: 05-21-19 12:12 PM by Chuck - Raymarine - Moderator.)
Post: #1
|
|||
|
|||
[TG11] Axiom - Crash to boot screen - Vesper AIS NMEA2000 data
I have looked but cannot find a similar issue on the forum.
Axiom 9 and 7, (9 is Master) wind, and speed instruments via ITC5 and NEMA 2000, depth direct to Axiom 9 (installed in November 2018 by dealer). Raymarine ST6000 autopilot on NEMA2000 Vesper Marine XB8000 AIS sending data on NEMA2000. All systems working fine. After February update of the Axiom I woke at anchor one morning to find the Axiom 7 stuck in boot screen. Shortly after the same happened to the Axiom 9. So no chart plotter, depth, wind or speed available to navigate back to safety of a marina. I was anchored off a small island east of Phuket Thailand. Once back in the safety of a marina. Started investigation. Recycled power and both MFD still in boot screen. Recovered by factory reset. However after a few hours same happens. Numerous attempts made. Dealer removed both MFD and found nothing wrong. Re-wired all 12vdc supply to separate supplies through a dc/dc converter in case fault was due to noise. Still encountered same issue. Powering up the system in a certain sequence allows the system to function normally. Cold Boot up (12vdc turned on) sequence AIS, Axiom 9 then Axiom 7. In any other sequence MFD fail to boot screen after a few minutes. Indicators of failure are depth going erratic from 4M to 390M+, GPS signal lost. Same issue with soft (turning off at MFD 12vdc supply still on). I am now very good at factory reset and rebuilding the preferences of the Axiom. April update installed and now both Axiom fail to boot screen regardless of power on sequence. AIS removed and tested by dealer. No faults found. Dealer changed NEMA200 network supply cable but system still fails after a few hours. Finally I (yes I and not the dealer) went into the AIS system and turned off the NEMA2000 outputs except the AIS data. NEMA2000 inputs into the AIS not inhibited as I use the data across the AIS WiFi system to other displays. Since then the system is stable with numerous restarts tested. It took nearly 6 weeks, considerable inconvenience and extra financial outlay to come to this resolution. So one question is why The NEMA 2000 data from the AIS, which is repeating the AXiom data, cause both Axiom to fail to boot screen? Second question is can I trust my Axiom MFD to work reliably when sailing remote locations or should I have just stuck to paper charts, wet finger and a plumb line? |
|||
05-21-19, 01:49 AM
(This post was last modified: 05-21-19 12:13 PM by Chuck - Raymarine - Moderator.)
Post: #2
|
|||
|
|||
RE: [TG11] Crash to boot screen
Hello Sailboat Anahi,
I think I know what's happening here. I was involved in the diagnosis of a system with a very similar-sounding problem in New Zealand. In that case the problem was that the Vesper AIS was outputting invalid/corrupted (and badly so) NMEA2000 data. The distribitor in NZ logged some NMEA2000 traffic for us and sent it over and the Vesper's PGN 129029 GNSS Position Data message was - well, I think mangled is perhaps the best description. I'll copy and paste the reply I sent to the tech in NZ, rather than write it all out again: Quote:I think I have found the cause of both the Axiom and CANKing/NMEA2000 crashes: there seems to be something very strange in the Vesper’s PGN 129029 GNSS Position Data. Here’s an extract of the raw data, where if you look carefully you’ll see the same sequence of bytes (c0 e0 44 03 3f 00 c3 78) repeated in different positions in the frame sequence, separated by blocks of ff ff ff ff ff ff ff ff fc ff ff ff ff. Look at the second and third message blocks below for a good example. I’ve highlighted the first instance of the sequence in the first message block. Remember that this is a multi-frame message separated over 7 CAN frames (lines.) (sample data not in bold below due to forum formatting limitations, but you can see the pattern ...78 c0 e0 44 03 3f 00 c3... repeating throughout the data: this should never happen!) Code: Di Time---| PGN----|Src|Sq|------Data---------| If you want to be sure that your AIS is subject to the same problem then you'd need to record some of the NMEA2000 data using one of the methods other than your Axiom listed in the middle of this post and send that log-file to me for examination, but I am pretty confident. Unfortunately this is one of those cases where only looking at the raw data will identify the problem. Here in Australia we now strongly encourage all of our technical service dealers to have a PC-based 'raw data' NMEA2000 diagnostic tool, which is where the above data came from. In summary, I think you should probably push the manufacturer of the AIS for a software update, but in the meantime I think that you can trust the Axiom to work reliably with all reasonable NMEA2000 data. Regards, Tom Raymarine since 1999. Interests: Diagnosis of problems in sonar/fishfinders, NMEA2000, ethernet comms, autopilots, thermal cameras Location: Sydney, Australia. Please don't PM me asking for direct support, please ask a public question instead so that others can see the question and answer. Forum posts will always be answered before PM requests. |
|||
05-21-19, 08:36 AM
(This post was last modified: 05-21-19 12:13 PM by Chuck - Raymarine - Moderator.)
Post: #3
|
|||
|
|||
RE: [TG11] Axiom - Crash to boot screen - Vesper AIS NMEA2000 data
Tom
Many thanks for the response. I believe you have confirmed my suspicions that the data across the NEMA is causing the issue. So just one address? I have over the last week had no issues with crashing when starting up in different sequences. Just a shame that it has taken so long to find a resolution even with the assistance of the local Raymarine agent. Especially when I requested at the beginning the network be checked for just such an issue. It might have saved me a lot of money as well. I can live with the Vesper AIS outputs inhibited so with your confirmation I will say this case is closed and hope for some happy sailing memories with my Axiom system. I have been very happy with them apart from this issue but would like a way of trending points such as wind speed and STW if that is possible. Best regards Gavin |
|||
05-27-19, 10:22 PM
Post: #4
|
|||
|
|||
RE: [TG11] Axiom - Crash to boot screen - Vesper AIS NMEA2000 data
Hello Gavin,
Yes, we're trying (here in Australia) to educate dealers about NMEA2000 diagnosis, tools, understanding the raw data and things to look for, but it's a bit of a struggle. As you can see from the extract I posted, it's not as simple as old NMEA0183 was and for many dealers it seems overly daunting. We have field tools that can help them, but it's a task to persuade them to use them and understand the results. Understood about the trend feature, I believe that's something that's been reported as a feature request but I will make sure that that's the case. I definitely see the benefit. Regards, Tom Raymarine since 1999. Interests: Diagnosis of problems in sonar/fishfinders, NMEA2000, ethernet comms, autopilots, thermal cameras Location: Sydney, Australia. Please don't PM me asking for direct support, please ask a public question instead so that others can see the question and answer. Forum posts will always be answered before PM requests. |
|||
« Next Oldest | Next Newest »
|
User(s) browsing this thread: 2 Guest(s)