Maretron DSM410 / J2K100 / J1939 Onan programming

[Shaps]

@ttmott re:the OP,
Correct me if I am wrong, but I think if @Spark600 N2K network is powered correctly and the J2K100 is connected to it, he should see the instance of the J2K100 on the network regardless of the functional state of the NIM. That is what I found.

 

[alnav]

I think you will find the NIM does not interface with the Onan external instrumentation. That instrumentation works right off the generator's data feed. Take a close look at the wire harness from the generator to the NIM; It is an adapter harness that taps off to both the NIM and the Onan external instrumentation.

I don't disagree but, as I said, I think the odds favor there being a Maretron problem. It could certainly also be a NIM problem but not seeing the J2K100 on the network would be the first issue I would try to tackle. I think the J2K100 should be visible on the network, NIM or not.

 

[ttmott]

@ttmott re:the OP,
Correct me if I am wrong, but I think if @Spark600 N2K network is powered correctly and the J2K100 is connected to it, he should see the instance of the J2K100 on the network regardless of the functional state of the NIM. That is what I found.

I agree he should see the device.

 

[ttmott]

I don't disagree but, as I said, I think the odds favor there being a Maretron problem. It could certainly also be a NIM problem but not seeing the J2K100 on the network would be the first issue I would try to tackle. I think the J2K100 should be visible on the network, NIM or not.

It should provided it has power; he should see the instrument on all NMEA2000/Seatalk NG component lists. However don't assume that because the Onan external instrumentation is operational that the NIM is, they are independent; that's what I was trying to say.

 

[Spark600]

I want to thank all of you that help me figure this problem out, It is fixed.
I had no power at the J2K100 so I traced out the wire to the next connection and found a lose wire on the Tee.

 

[Dunigan]

OK, I have a weird question. What if you have a Smartcraft NIM. Can you connect it to a Mercury Vessel View Mobile Adapter and see your genset data on the mobile app? I believe you would need the cable that connects to the 12 pin port on the NIM and has the Mercury 10 pin connector on the other end. Connect that to the adapter.

 

[alnav]

OK, I have a weird question. What if you have a Smartcraft NIM. Can you connect it to a Mercury Vessel View Mobile Adapter and see your genset data on the mobile app? I believe you would need the cable that connects to the 12 pin port on the NIM and has the Mercury 10 pin connector on the other end. Connect that to the adapter.

I'm afraid this won't work. I believe all Smartcraft components stopped supporting generator CAN data which was Smartcraft (similar to but not the same as the engine data). This happened in the early 2010's and before any of the adapters were deployed. Luckily the NIM's were both Smartcraft and J1939 capable and it is the J1939 signal that can be read by an appropriate converter and viewed on N2K.

 

[Dunigan]

OC Grant:

On Jan 30, 2021, you posted a pic of your J2K1000 'Cummins version' that displayed Source ID: 234, Engine Instance: 10, Alternator Instance: 10, and AC/Diagnostics Instance:10. Did you keep these settings? Did these settings appear in the DSM410 device config area? I am finishing my install tomorrow morning and plan to use these settings. It appears that others have used different 'instance' settings without issue (as long as 234 is set as the source). TIA.

 

[ttmott]

OC Grant:

On Jan 30, 2021, you posted a pic of your J2K1000 'Cummins version' that displayed Source ID: 234, Engine Instance: 10, Alternator Instance: 10, and AC/Diagnostics Instance:10. Did you keep these settings? Did these settings appear in the DSM410 device config area? I am finishing my install tomorrow morning and plan to use these settings. It appears that others have used different 'instance' settings without issue (as long as 234 is set as the source). TIA.

You can use any except for 0 or 1. However, as Grant will tell you most of us organize instances logically to make sense for documentation and future growth and probably why he uses 10. I use 3 for the generator engine.

 

[ocgrant]

You can use any except for 0 or 1. However, as Grant will tell you most of us organize instances logically to make sense for documentation and future growth and probably why he uses 10. I use 3 for the generator engine.

You know to be honest That is what came up and I just left it.

 

[Dunigan]

Project complete (I think). Thanks to all who have guided me via this post. The smart craft NIM, once converted to J1939 (cut W2, reconnect W5) was connected to the J2K converter via the Deutsch cable identified here. The J2k was connected to my NMEA2K Furuno network via the FI-5002 junction box and then configured to address 234. Instances were left at 0 since I have no other engines reporting on the NMEA. (They report via Smartcraft to the VV1.5 units.). Data appeared on my Furuno RD-33. I only get engine data as the Furuno only reports PGN 127488 & 127489 but this is enough for my purposes. I do not get engine hours. I have posted a pic of the data as seen on a Maretron N2K Analyzer. Observe the engine hours report....-1.#QNANO Hr...very odd. Maybe someone can decipher this info as a clue to why eng hours aren't coming off the NIM. Again, many thanks.

 

[Shaps]

see the prev post
Maretron DSM410 / J2K100 / J1939 Onan programming

"Is Generator"

 

[Dunigan]

Shaps, am not following you. Any chance you could expand on your reply. Are you saying that using the settings described in the previous post will allow engine hours to display? Sorry and thanks!

 

[alnav]

Project complete (I think). Thanks to all who have guided me via this post. The smart craft NIM, once converted to J1939 (cut W2, reconnect W5) was connected to the J2K converter via the Deutsch cable identified here. The J2k was connected to my NMEA2K Furuno network via the FI-5002 junction box and then configured to address 234. Instances were left at 0 since I have no other engines reporting on the NMEA. (They report via Smartcraft to the VV1.5 units.). Data appeared on my Furuno RD-33. I only get engine data as the Furuno only reports PGN 127488 & 127489 but this is enough for my purposes. I do not get engine hours. I have posted a pic of the data as seen on a Maretron N2K Analyzer. Observe the engine hours report....-1.#QANO Hr...very odd. Maybe someone can decipher this info as a clue to why eng hours aren't coming off the NIM. Again, many thanks.

Dunigan, it may be this setting. From the Maretron J2K manual:
2.5.6 Request Engine Hours Enable/Disable
Some J1939 ECU’s will not transmit engine hours unless they are requested to. If this setting is enabled, then the J2K100 will periodically transmit a request for the engine hours message to the J1939 ECU over the J1939 network. This is the only time the J2K100 will transmit messages over the J1939 network. If this setting is disabled, then the J2K100 will not transmit any messages over the J1939 network.

I didn't catch how you programmed but this setting is available as a toggle on the DSM410 config menu.

 

[Dunigan]

Thanks, alnav. My tech and I programmed via the Maretron N2K analyzer and did set the engine hours to 'enable'. I will mess with this some more only because I have really gotten into this project and want to learn as much as possible. Many thanks.

 

[alnav]

Thanks, alnav. My tech and I programmed via the Maretron N2K analyzer and did set the engine hours to 'enable'. I will mess with this some more only because I have really gotten into this project and want to learn as much as possible. Many thanks.

The generator hours thing seems to be unpredictable. I never have gotten it to work. But, others have. Hopefully you will uncover the secret as you continue to tinker with it.

 

[Shaps]

Shaps, am not following you. Any chance you could expand on your reply. Are you saying that using the settings described in the previous post will allow engine hours to display? Sorry and thanks!

Along with what @alnav said, I am saying that there may be a similar setting on your furuno as to what @alnav was highlighting we have on the vesselview. Somewhere buried in the guts of the menus on what the data is may be a flag to identify the source as a generator and then allow you to get/display those PGNs

 

[Shaps]

Gen hours along w other gen specific data

 

[ttmott]

I finally got the hours to display also. All changes done in the Vessel View; none required in the Maretron J2K100. Some screen shots on the Vessel View 7:

 

[ocgrant]

Nice… going to have to play with this on my 703 now. Add it to the list