[TG] [TG11] e125 intergration with smartcraft
|
04-10-20, 07:30 PM
(This post was last modified: 04-13-20 09:52 AM by Chuck - Raymarine - Moderator.)
Post: #1
|
|||
|
|||
[TG11] e125 intergration with smartcraft
Hi,
i have e125 hybrid touch MFD with stng connected to Mercury Marine Engine Gateway NMEA2000. i can see can-p multi adapter on raymarine screen, but no engine data. running cummins qsc with smartcraft. any tips would be appreciated. thanks Giuseppe |
|||
04-13-20, 07:59 PM
Post: #2
|
|||
|
|||
RE: [TG11] e125 intergration with smartcraft
Hello Giuseppe,
If you record some of the NMEA2000 traffic that the e125 is receiving and post that recorded log-file back here, we can take a look and see what the problem is. Usually, if the physical connection is ok, the problem is the Instance numbers within the data that identify which engine the data is coming from. The NMEA2000 specification says that 0=Port, 1=Starboard (for a twin-engine system) but they are very often configured incorrectly and we can see whether that is the case or not in your recorded 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. |
|||
04-15-20, 10:18 PM
Post: #3
|
|||
|
|||
RE: [TG11] e125 intergration with smartcraft
Hi Tom,
Please find attached record of NMEA200 traffic. Regards, Giuseppe |
|||
04-19-20, 12:29 AM
Post: #4
|
|||
|
|||
RE: [TG11] e125 intergration with smartcraft
Hi Tom,
Please find attached record of NMEA2000 from can bus for mercury marine engine gateway. Thanks, Giuseppe |
|||
04-19-20, 08:47 PM
Post: #5
|
|||
|
|||
RE: [TG11] e125 intergration with smartcraft
Hi Giuseppe,
That log doesn't contain any standard NMEA2000 engine data PGNs (127488 and 124789.) It contains a range of standard navigational (GPS, heading, rudder, cross-track error, time etc.) data PGNs and a handful of proprietary ones which all have the Raymarine manufacturer code in them (not Mercury.) Was the gateway connected/powered and the engines running at the time the log was taken? It doesn't look like you were getting any data at all from the gateway at that time. Thanks, 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. |
|||
04-27-20, 06:16 AM
Post: #6
|
|||
|
|||
RE: [TG11] e125 intergration with smartcraft
Hi Tom,
thanks for you response. The gateway was connected, had power on, both can lights and nmea lights were on, with engines running. Regards, Giuseppe |
|||
04-27-20, 08:47 PM
Post: #7
|
|||
|
|||
RE: [TG11] e125 intergration with smartcraft
Hello Giuseppe,
I've had a more in-depth look at your log and there is after all a very little data on the network from the gateway, but no valid engine data. This is all of the message-types that are in your log: Quote: You can see that Proprietary message about a third of the way down that list where the manufacturer is Mercury. That message is transmitted from device with address number 0x72. Address 0x72 is sending that one proprietary PGN (65310) every 5 seconds but nothing else. This a capture of the same data filtered to show only data from address 0x72: Quote: I am sorry to say that I think that you'll need to contact Mercury support to ask them why their gateway is only transmitting that one PGN 65310. It's not something simple like the gateway being connected the wrong way round though is it? 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. |
|||
04-28-20, 02:55 AM
Post: #8
|
|||
|
|||
RE: [TG11] e125 intergration with smartcraft
Hi Tom,
thanks for your response. please find attached diagram of how things are currently setup. i just added 5-way seatalk ng connecting engine gateway to it only. i have attached another N2k file with this new setup. If you could have a look and let me know if ok. Regards, Giuseppe |
|||
04-28-20, 08:57 PM
Post: #9
|
|||
|
|||
RE: [TG11] e125 integration with smartcraft
Hi Giuseppe,
The drawing looks fine, and we're definitely receiving data from the Gateway, just no engine data: this is what's in the latest log, still just the same proprietary PGN 65310 every 5 seconds: Quote: At this point I am afraid I can only really suggest you ask your Mercury dealer why the gateway isn't outputting anything more than that one PGN. That NMEA2000 log may help them diagnose the problem too. I've had a quick look online and at the gateway manual and the manual doesn't list that PGN as far as I can see. 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. |
|||
04-29-20, 02:52 PM
Post: #10
|
|||
|
|||
RE: [TG11] e125 intergration with smartcraft
I had this same problem with a Merc gateway and Cummins engines. What I found was
Mercury had changed something on the newer gateways and the defective gateways need to go back to the Mercury to be re-flashed. I just sent mine back to the seller and ordered one from the company that identified the problem and had the correct gateways in stock. Works fine now. |
|||
« Next Oldest | Next Newest »
|
User(s) browsing this thread: 2 Guest(s)