Maretron J1939 to N2K

The friendliest place on the web for anyone who enjoys boating.
If you have answers, please help by responding to the unanswered posts.

Arthurc

Guru
Joined
Sep 24, 2016
Messages
752
Location
USA
Vessel Name
Sea Bear
Vessel Make
Kadey-Krogen 54
Hi,
I’m wrapping up my new engine/gen install (sea trial monday!) and bought a Maretron J1939 to N2K Box to get my JD instruments onto my NMEA and ultimately TCP network.
I had the engine shop do the J1939 connector and splice but the Maretron is seen on my network but seems to be pushing jibberish. Engine is a new JD6068.
Attached is a picture of what it’s outputting. Any thoughts on if the j1939 splice is incorrect or if it’s something else?

Thanks!
Arthur
 

Attachments

  • 2A1542DD-1695-47C8-A1A0-75252F664E53.jpg
    2A1542DD-1695-47C8-A1A0-75252F664E53.jpg
    192.4 KB · Views: 64
What is the display in the picture from? And it is supposed to be showing the N2K data coming out of the J2K100?

The last two are management PGNs used by N2K for config etc.

Do you have N2KAnalyze or one of the Maretron displays to configure the J2K100? My first guess would just be that you need to configure it. It needs to be listening to the correct device number on the J1939 side.

I'm using the same device with a Deere 4045 and a Deere 6090, so can confirm it works once set up.
 
I unfortunately don’t have any maretron displays, and was hoping it wouldn’t need one as in the manual it said it was preconfigured to work out of the box.

This was captured by the RosePoint NEMO box which takes N2K and 0183 and broadcasts it over TCP. I know that box it working as all the other devices on my Nmea networks are.

I also have Furuno TZTs on the N2K network and they see the maretron devices but no sentences.
 
TwistedTree, do you know if I can configure the Maretron from a DSM410 display? I have been considering one.
 
When its working correctly, NEMO will show PGNs 126448 and 126449 coming in from the J2K100. At least that's what I get.

Aside from wiring issues, the most likely cause seems to be a J2K config issue.
 
Thanks! Will let you know what I find out.
 
Back
Top Bottom