How To Replace and Improve the Sea Ray Systems Monitor

ranger58sb said:
Our SM display crapped out circa May of this year, and I'm still pondering solutions. I've tried simple diagnostics and the reset procedures (for the "newer" SM part numbers than what we have), no joy so far. Not unexpected. And in the meantime, I've been trying to memorize :) what you've done to replace/upgrade.

In the meantime, some info on "simple" replacement is here:
http://clubsearay.com/index.php?thr...vailable-at-marine-max-brick-to-order.110932/

I haven't even put eyes on our bilge interface yet, and haven't tried bypassing existing coax to see if our issue is relatively minor. Not expecting it is...

Anyway, can you describe the physical connections at the RIM100? Are the existing sensor wires all connected to the original bilge interface module with ring terminals on studs? If so, are the Maretron connections using those same ring terminals on RIM100 studs? Off the old, onto the new?

Or...?

-Chris
Click to expand...
Sure - the wires from the things that are monitored (bilge pumps for example) all terminate into a single connector for the OEM Sea Ray Systems Monitor module. That connector can be removed via a single hex socket screw in the middle of the connector.
Those same wires will terminate onto screw terminals on the Maretron RIM100 box. So, that connector gets cut off then ring terminals get crimped onto the wires then the ring terminals get installed on the Maretron box. Some of the wires go +24 VDC (in your case) and some go -24VDC depending upon what device they come from. Most like your bilge pumps will go +24 however. So, back on the Maretron RIM 100, there are two screw terminals for each channel and there are six channels. One channel for each device to be monitored. Let's assume you want to know if a bilge pump comes on; the wire will go hot to +24 volts when that pump activates. The Maretron RIM100 will see that hot let's say on Channel 1 but it has nothing to bias it against so consequently, the second terminal on that channel needs to be connected to the battery -24 Volt (ground). If you have a device that goes to ground when shut down unplanned (like the generator's status wire) then obviously you need a +24 volt bias on that second screw terminal for that channel.
The only other connection on the RIM100 is to the NMEA 2000 network.
 
I know it was mentioned before but i cant find it. What part numbers do I need if I want to install boost pressure readings to the maretron?

Saverio
 
Saverio said:
I know it was mentioned before but i cant find it. What part numbers do I need if I want to install boost pressure readings to the maretron?

Saverio
Click to expand...
One Maretron FPM100 and two Maretron 0-50 PSIG PT-0-50PSI-01 transducers. No vacuum measurement here but with diesel engines boost is probably all needed.
If you wanted to see vacuum then you could find a commercial 4 bar sensor that outputted 4 to 20ma; Dwyer has a host of these.
 
Saverio said:
I know it was mentioned before but i cant find it. What part numbers do I need if I want to install boost pressure readings to the maretron?

Saverio
Click to expand...

Boost pressure is an extended engine parameter and that would need the FPM and proper sensor to read boost pressure AKA Compressed Air. No problem displaying the PGN on the 410 or any MFD supporting turbo boost pressure. This may be a good alternative as well: https://acrossoceansystems.com/index.php/nmea2000-pressure-sensors/
 
thank you
ttmott said:
One Maretron FPM100 and two Maretron 0-50 PSIG PT-0-50PSI-01 transducers. No vacuum measurement here but with diesel engines boost is probably all needed.
If you wanted to see vacuum then you could find a commercial 4 bar sensor that outputted 4 to 20ma; Dwyer has a host of these.
Click to expand...
for some reason I cant locate the 50 psi sensor on ebay or amazon?
 
Saverio said:
if i use this one is there any programing I have to do to make it talk to the maretron?
Click to expand...

All NMEA2000 devices for the most part need t be programed. An instance number is usually what needs to be changed. The device probably comes set to 0, so one will need to be set 1. Going forward just assume the port engine is 0 and the starboard is 1, that makes life easier.

In the DSM410, you just need to the set the instance number for the boost display as well. Just to clarify, NMEA2000 device either broadcast or listen. No one device "talks" to another device like in NMEA0183. Just like a PC network.
 
SKybolt said:
All NMEA2000 devices for the most part need t be programed. An instance number is usually what needs to be changed. The device probably comes set to 0, so one will need to be set 1. Going forward just assume the port engine is 0 and the starboard is 1, that makes life easier.

In the DSM410, you just need to the set the instance number for the boost display as well. Just to clarify, NMEA2000 device either broadcast or listen. No one device "talks" to another device like in NMEA0183. Just like a PC network.
Click to expand...
thanks that make sense
 
Saverio said:
thank you

for some reason I cant locate the 50 psi sensor on ebay or amazon?
Click to expand...
Any quality 0-50 transducer that operates on a 4-20 milli-amp loop will work. Here is a Dwyer one 628-09-GH-P1-E1-S1
It's like $120. As a note stay away from the cheap foreign knockoffs as they are horrible at the linearization and resolution.
Regarding programming - there two things requiring programming which are all executed on the Maretron display. One is setting up the FPM100 and the other is setting up the display to view the data. The FPM will require you to name the channel, set up the values, select the NMEA 2000 name / PGN, and set up the range; all menu driven. The display is to set up a page to view the data, and what the data is. There is no "programming" on any of the transducers - all they provide is a milli-amp value relative to the pressure sensed. The Maretron manuals are quite good so read them.
 
SKybolt said:
All NMEA2000 devices for the most part need t be programed. An instance number is usually what needs to be changed. The device probably comes set to 0, so one will need to be set 1. Going forward just assume the port engine is 0 and the starboard is 1, that makes life easier.

In the DSM410, you just need to the set the instance number for the boost display as well. Just to clarify, NMEA2000 device either broadcast or listen. No one device "talks" to another device like in NMEA0183. Just like a PC network.
Click to expand...
Orlando a single FPM100 provides six channels of which he needs two. He only needs a single instance for the FPM100 which, unless there are others on the network, would be 0. Channel 1 can be Starboard Boost and Channel 2 Port Boost. Separate PGN's can be identified to each channel - therefore not only the DSM will read and display the boost but any MFD that can read the PGN's will display - like the Garmin 8XXX ones.
 
ttmott said:
Orlando a single FPM100 provides six channels of which he needs two. He only needs a single instance for the FPM100 which, unless there are others on the network, would be 0. Channel 1 can be Starboard Boost and Channel 2 Port Boost. Separate PGN's can be identified to each channel - therefore not only the DSM will read and display the boost but any MFD that can read the PGN's will display - like the Garmin 8XXX ones.
Click to expand...

Yes, but the channels need to be changed to get them to display correctly. Sorry didn't go into that detail as the result is basically the same. It is obvious when your programming the DSM410 that you have to select the channel, much like the instance number.

The xx43 series will also display the engine PGN's same as the 86xx series will.
 
SKybolt said:
Yes, but the channels need to be changed to get them to display correctly. Sorry didn't go into that detail as the result is basically the same. It is obvious when your programming the DSM410 that you have to select the channel, much like the instance number.
Click to expand...
Right but only a device (FPM, RIM, DSM, etc) gets an instance not each channel on a device.
For the OP's clarification - if you had several FPM100 devices and each had six channels for instruments (total of 18 instruments) the NMEA network needs to know the device and channel. The channel is the PGN you are interested in seeing. So you would have instance 0 through 2 (or any number provided they are not duplicated) and each would have six PGN's. You also may have duplicate PGN's provided they are on separate instances.
 
ttmott said:
Right but only a device (FPM, RIM, DSM, etc) gets an instance not each channel on a device.
For the OP's clarification - if you had several FPM100 devices and each had six channels for instruments (total of 18 instruments) the NMEA network needs to know the device and channel. The channel is the PGN you are interested in seeing. So you would have instance 0 through 2 and each would have six PGN's.
Click to expand...

Yes I completely understand all of that. My bad, I was dumbing it down for easier understanding.

But to be honest, Maretron isn't the way to go if you want to display boost pressure correctly. They don't transmit the proper engine PGN (127488) for other MFD's to pick up and display.

The Boost pressure is published in the 127488 PGN field 3.

PGN 127488 Engine Parameters, Rapid Update
1 Engine Instance
2 Engine Speed
3 Engine Boost Pressure
4 Engine tilt/trim
5 Reserved Bits

Maretron only publishes the actual pressure in this case and not in the correct PGN for engine turbo boost. So only a Maretron display will display this boost pressure as you need to configure it to do so.
upload_2022-12-30_10-6-21.png
 
ttmott said:
... For the OP's clarification - if you had several FPM100 devices and each had six channels for instruments (total of 18 instruments) the NMEA network needs to know the device and channel. The channel is the PGN you are interested in seeing. So you would have instance 0 through 2 (or any number provided they are not duplicated) and each would have six PGN's. You also may have duplicate PGN's provided they are on separate instances.
Click to expand...

So this gets complicated quickly. The FPM100 has a device instance and a "channel" number is a source type. so the PGN it transmits is 130314 Actual Pressure defined as:
130314 Actual Pressure Field #
1 SID
2 Pressure Instance
3 Pressure Source
4 Pressure
5 Reserve Bits

Field 3 is the source or their "channel" number. This is not an instance number, it is a "type" or the source of the pressure. There is a list of types for pressures in the N2K standard.

I can explain it better using the temperature PGN 130312, I don't have the pressure types to reference but I do have the temperature ones, the concept is the same for both, and others.

Temperature for instance, all of the temperature devices can be set to the same instance number but the "type" setting needs to be different in order to be displayed correctly on any MFD. The types for temp's are 1-13, sea temp, inside temp, outside temp, engine room temp and so on. All of those options can have an instance number of 0 (or what ever number you chose 0-254) but the "type" must be different which makes the device PGN unique.

130312 Temperature
Field # Field Description Temperature as measured by a specific temperature source.
1 SID
2 Temperature Instance
3 Temperature Source
4 Actual Temperature
5 Set Temperature
6 Reserve Bits

So in this case fields 2 and 3 need to be set correctly, but the instance field 2 can be the same as long as field 3 changes. If field 3 (type) does not change then the instance number needs to be different. Meaning if you had two engine room temp sensors the first one would have field 2 (instance) set to 0 and field 3 (type) set to 3 (Engine Room) and the 2nd device would have field 2 set to 1 and field 3 set to 3 same as the 1st.

The above is why I didn't get into the channel explanation, because type becomes an instance number of sorts in this case.


.
 
Saverio said:
Is the USB 100 easy to use. I could program the dsm and the rim 100
Click to expand...

The USB100 will allow you to program the RIM100, which can also be programed through the DSM410 as well. It will not allow you to program the DSM410. All of those settings need to be completed manually. To use the USB100 you will be using N2KAnalyzer that connects to the USB100.

There is also another option of using the IPG100 which is a network device and will also allow the use of N2KView to view custom screens on your phone/tablet.

http://clubsearay.com/index.php?threads/remote-monitoring.102913/

upload_2023-1-3_10-54-15.png
 
Saverio said:
What exactly is that? Is it software?
Click to expand...

In case you don't know the USB100 is what connect's to the N2K network with one connection. And the usb connection connects to a PC where you need to run N2KAnalyzer and that is the software tool needed to configure things.
 
You must log in or register to reply here.

Forum statistics

Threads
113,193
Messages
1,428,284
Members
61,104
Latest member
Three Amigos
Back
Top