How to Replace and Improve the Sea Ray Systems Monitor (Re-Deux)

ttmott

PhD in OCD
GOLD Sponsor
TECHNICAL Contributor
Apr 3, 2012
8,154
Space Coast Florida
Boat Info
2006 52 Sedan Bridge
Engines
Cummins QSM11
It seems that the all-important graphics have been deleted in our original thread replacing the SR Systems Monitor so this is a supplement by popular demand. For reference here is the original thread -
https://clubsearay.com/index.php?th...nd-improve-the-sea-ray-systems-monitor.91270/

Part Deux -
Sea Ray has a unique stand-alone system called the Systems Monitor that continuously monitors critical elements of the boat and notifies the helmsman of a change in state. Depending upon the boat model and year the things that are monitored vary. Common to all are bilge and sump pumps. In pre-electronic engines Sea Ray also monitored engine coolant temperature, oil pressure, and exhaust temperature. In all cases monitored items are discrete; that means a state of either ON or OFF.
Sea Ray had two generations of the monitor systems. One was LED lamps on a boat outline on the helm and another a digital display. The model year of transition to the digital system was 2000 plus or minus. The issue today is when a part of the system fails the components either aren't available or hideously expensive. There is another solution besides the Sea Ray OEM which not only replicates the messages but provides another world of capabilities. Read on -

Basis of OEM operation -
Regardless of the system generation, the monitored item (bilge pump for example) has a single wire that provides a positive or negative voltage to the Systems Monitor input module. Positive voltages would be a bilge pump coming on and negative voltages would be an oil pressure switch going to ground on low oil pressure - as examples. Some generators have a signal wire that goes to ground should the generator shut down and others use an oil pressure switch that goes to ground at loss of oil pressure indicating shutdown or worse. What this all means is the SR Systems Monitor requires both a Battery ground wire to sense differential to things changing state to battery positive (like bilge pump turning on) and conversely an Engine Ignition battery positive for things that change state to battery ground (like engine oil pressure).
So, there are a host of wires to the Systems Monitor control module accounting for each item on the boat being monitored and wires for the battery ground and Ignition Positive to bias the monitored items as applicable. Sea Ray did a good job color coding these wires in that Brown was for bilge/sump pumps, Purple is engine ignition, Black with white stripe is generator, black is battery ground, and Red is battery positive, etc. Additionally, printed on the wire is the actual function with a unique number that ties to the boat's electrical schematic drawing in the owner's manual. In the first generation of the Systems Monitor (helm LED's) all of the wires were routed to the helm and the input module was located somewhere inside of the helm. In the later generation (digital display) the input module was located in the engine room and a single coaxial data cable communicated to the helm display. As a side note, routing parallel to the later generation coaxial data cable are the positive and negative power wires for the helm display power.

Enter Maretron and NMEA 2000 -
To replace the Sea Ray systems monitor we need a device that can detect a change in electrical state then note that change in state on a digital marine network (NMEA 2000). And, we need a device to interpret the signal on the NMEA 2000 network and display / alarm as required. There are several manufacturers that have devices to detect a change in state and get that data on a NMEA 2000 network but in my experience Maretron does this function most seamlessly and provides the most flexibility to display precisely what that change in state is. So, here wel'll focus on the Maretron solution.

The Maretron RIM100; this device has six channels in that, six items (bilge pumps, oil pressure switch, etc) can be simultaneously monitored for a change in state. The RIM 100 has two wire terminals for each channel so a change in state (positive or negative) can be monitored with an appropriate positive or negative bias as explained earlier. The RIM 100 codes the data onto the NMEA 2000 network. The RIM100 is powered and programmed through the NMEA 2000 network and programming simply done through one of Maretron's displays or if the correct adapters and software are purchased through a laptop computer; it is all menu driven. Additionally, the RIM100 is powered through the NMEA 2000 network. Multiple RIM100 can be added to increase the number of channels; to differenciate between and the channels a unique NMEA 2000 instance is assigned to each RIM100. One thing about Maretron is their manuals and instructions are second to none on how to wire and configure their products. To go any further on the specifics of NMEA 2000 one needs to understand the basics of a NMEA 2000 network and how it must be arranged, powered, and configured so we'll stop here on the NMEA 2000 network specifics; a subject for another thread.

The second part of the system is to view and control the data and that is a display like the Maretron DSM410. Maretron has others but the DSM410 is what I used. The digital signal on the NMEA2000 network from the Maretron RIM100 is propriety and must be configured / viewed on another Maretron device like the DSM410. The DSM410 is essentially the control center for a Maretron based network. It is used in this application to program and control all the devices on the NMEA 2000 network.

Short Circuit Protection - to protect the Maretron source devices (RIM100), any wiring that inputs a battery positive must be fused so we need a fuse for each of the signals that are battery positive to the RIM100. The RIM100 requires zero current so a 1 amp to 5 amp fuse is appropriate to protect the device.

Programming and Setup - Essentially, there are two levels of setup / programming in a Maretron based NMEA 2000 network. The first is to setup the end devices like the RIM100. In this case the RIM100 needs to have each channel labeled and set the alert state (On or Off). If more than one RIM100 in in the system then each one must be assigned a unique instance so every channel is unique on the NMEA 2000 network (Instance 1 Channel 4 or Instance 2 Channel 4 for example). There are a host of variables to be configured on the end device but all are pull down menu driven. The second level is to set up the display (like DSM410) and view the data provided on the network as you desire. Things like screen colors, screen configurations, how alerts and alarms are visually displayed are all possibilities and again managed through pull down menus. One important essential thing is to read the DSM instruction manual so the concept of how Maretron operates is understood. It's a long read (like 140 pages) but nonetheless essential.

Powering the system - One thing of importance from my aspect is the OEM Sea Ray Systems Monitor always monitored bilge pumps wither ignition or battery power was on or off. So, when you think about setting up the NMEA 2000 system and it's power, consider this and how power is sourced to the system. A boat taking on water doesn't care if the power is on or off. In my configuration where there are multiple DSM displays and multiple independently powered segments of the NMEA 2000 network I consider one display as the Master; it is used to configure each end item (this is an important aspect to systems configuration) as well as being on the part of the NMEA 2000 network that is always powered up. Just as importantly the end device (RIM100) that is monitoring the bilge pumps (for example) is always powered up. With this configuration the Maretron solution is truly mimicking the OEM Systems Monitor.

There you have it, essentially, there are four components to replace the Sea Ray Systems Monitor - a fuse block, a Maretron RIM100, a NMEA 2000 network, and a Maretron DSM410. Here is the real benefit of this system - the DSM410 can display just about anything on the NMEA2000 network as well as monitoring the Sea Ray systems. Things like heading, trim tab position, steering position, GPS location, fluid tank levels, pressures, RPM, generator voltage and current - the list is just about endless. Heck, I even monitor how many times the Vacuflush head system cycles. There are 13 pages available on the DSM410 in which up to six items can be monitored per page.

Here is a schematic of the Systems Monitor wiring using a Maretron RIM100 that I implemented for my 2006 52 Sedan Bridge. My engines are all electronic and fault/gauge data is on a separate (Smartcraft) data network so in my configuration it's not a component of the SR Systems Monitor.
Detwork Diagram 17 Nov 2019SRSystems Monitor.jpg

This shows the Maretron devices integrated into the NMEA 2000 network on my boat. I have a couple of RIM100 and DSM410's as shown circled in red. - The RIM100 shown in the engine room is specifically for the Sea Ray Systems Monitor functions.
MaretronforSystems Monitor.jpg


And here is a view of one of the pages on the DSM410 that I have displaying the systems monitor data. Each monitored item is labeled and shown in normal state with green background then when the state changes to "Alarm" the background changes to red and an alarm is noted as flashing as well as audible. All of this is simple programming in the Maretron menu driven protocol and well delineated in their instruction manuals. Here I show that the Fwd Bilge pump came on then off showing there was an alarm. If it was active the green background on the monitored item would be red and flashing. There are a hundred ways the data can be viewed; this is just how I did it.
IMG_6092.jpg
 
I've edited to add some narrative on programming a Maretron based network and logic on powering.
Here is how the systems power is wired in my configuration -
Systems Monitor Power.jpg
Detwork Diagram 17 Nov 2019NegBuss.jpg
Detwork Diagram 17 Nov 2019DCPower.jpg
 
First, great summation of the other thread.

But I am curious why you are using two NBE100's instead of just using power blocks? The NBE's can only transmit a max of 32 PGN's at one time and they don't support buffering. I would think if you have more then 32 devices that you would see packet loss. Bad design on their part, because of the NMEA 2000 fifty device per network limitation.

The N2K cable length limitation is also a bit, well, limiting. 200m total backbone length and 78m total drop cable length. I use this guideline as a total cable length or 278m total cable length. There should be no difference between the two if all devices have equal resistance, which they should have. That's over 900' of cable length, more then enough for 40 device(s) (my device count) to have a 22.5' average cable length, or the max device count of 50 having an 18' average length. It looks like you have ~28, round up to 30 and that gives you an average length of 30'.

Sorry if this is off topic. Respond in another thread and I'll remove this post if that is so.
 
I think I remember he added these more for network isolation for lighning strike protection. They are optically isolated so would offer some protection in that event.
 
First, great summation of the other thread.

But I am curious why you are using two NBE100's instead of just using power blocks? The NBE's can only transmit a max of 32 PGN's at one time and they don't support buffering. I would think if you have more then 32 devices that you would see packet loss. Bad design on their part, because of the NMEA 2000 fifty device per network limitation.

The N2K cable length limitation is also a bit, well, limiting. 200m total backbone length and 78m total drop cable length. I use this guideline as a total cable length or 278m total cable length. There should be no difference between the two if all devices have equal resistance, which they should have. That's over 900' of cable length, more then enough for 40 device(s) (my device count) to have a 22.5' average cable length, or the max device count of 50 having an 18' average length. It looks like you have ~28, round up to 30 and that gives you an average length of 30'.

Sorry if this is off topic. Respond in another thread and I'll remove this post if that is so.
I think I remember he added these more for network isolation for lighning strike protection. They are optically isolated so would offer some protection in that event.
Power blocks are a great inexpensive solution to separate power zones in the network. One of the areas my little engineering firm was adept in was lightening protection for missile launch systems. There are two principal elements in protection - Isolate the asset from the effects of a strike and design the system so everything comes up equally in potential then drops to ground equally in potential; this eliminates the killer electrical current between things. It's not the voltage (potential) that kills things but the current that differential potential enables. When in 2019 my boat was subject to the effects of a direct strike on the sailboat slipped next to me, we found many areas it could be better protected. One was in the sensitive data network systems. We are dead center in the lightening capital BTW. The Maretron NBE isolator/extenders serve to help isolate systems on the boat from current surges. The second thing we did as a side note was go through the boat's bonding system and verify to the best extent possible the entire boat can equally come up in potential then equally drain down in potential as a cohesive unit. Lightning is insidious and it's behavior is difficult to predicted but we do the best technology provides.
 
@ttmott Tom I forgot you had gone through this back then. Now I see why you have the two installed. It makes a lot of sense especially where you are located.
 
I have replaced the Sea Ray systems monitor twice with Sea Ray parts at marine max and they have no Warranty on this part:mad::mad::confused::confused:, the first replacement worked for literally one season, 3 months then died. So another $1000 later, ( price went up) I now keep the circuit breaker off in the engine room and prior to starting engines flip on circuit breaker, when I am back at dock it is off.
Next is Maretron set up.
 
I followed your lead and did basically the same thing. System monitor replaced by two RIM 100s and I also added Maretron temp and pressure modules to monitor engine boost and EGT, Trans pressure/temp and raw water pressure. It was a fun project, primarily because your guide was invaluable and very much appreciated.

My only complaint is that I have SeatalkNG network and Raymarine does not make a backbone power isolator. I would love to be able to shut down the entire network with the exception of a single DSM410 and the RIM100s. That way I can monitor the bilge pumps as well as bilge pump on/off cycles...
 
I followed your lead and did basically the same thing. System monitor replaced by two RIM 100s and I also added Maretron temp and pressure modules to monitor engine boost and EGT, Trans pressure/temp and raw water pressure. It was a fun project, primarily because your guide was invaluable and very much appreciated.

My only complaint is that I have SeatalkNG network and Raymarine does not make a backbone power isolator. I would love to be able to shut down the entire network with the exception of a single DSM410 and the RIM100s. That way I can monitor the bilge pumps as well as bilge pump on/off cycles...

You need a SeatalkNG to NMEA 2000 cable, then you can use N2K power isolators.

I do this with my Raymarine Autopilot. But use this cable: https://defender.com/en_us/raymarin...Srha7Y-_IU4vq3tBx3tF7xoCDoEQAvD_BwE#493=43506
and you can use standard N2K products.
 
You need a SeatalkNG to NMEA 2000 cable, then you can use N2K power isolators.

I do this with my Raymarine Autopilot. But use this cable: https://defender.com/en_us/raymarin...Srha7Y-_IU4vq3tBx3tF7xoCDoEQAvD_BwE#493=43506
and you can use standard N2K products.

YThanks. Have to mix and match to cobble together. Two devicenet to STNG backbone cables and a Devicent isolator should do the trick. PITA. Why won't Raymarine just make asimple backbone isolator...Sigh
 

Forum statistics

Threads
113,205
Messages
1,428,529
Members
61,109
Latest member
Minnervos
Back
Top