Electronic controlled engines NMEA2000 warning policy & experiences please!

vas

Well-Known Member
Joined
21 Jun 2011
Messages
8,217
Location
Volos-Athens
Visit site
evening all,

finalising the routines that will run the Mase generator now that the old control box is caput and following the rebuilt of the engine and addition of a linear actuator to operate the governor.

Have come up with an "interesting" issue, re warnings.

Say, I get a blocked inlet/damaged impeller of failed pipe somewhere there and engine temp goes up.
When it reaches say 90C (ok, I'll establish that once I get to install and run it in summer water temps) then I instruct the governor to shut the thing off and save it from further damage.
All fine, done that.
Since the control box is a N2K custom device, I may as well pop a message to the N2K bus to warn whoever is in charge wherever he/she is that there's an issue and generator is turning off.

I can do that easily and broadcast a Warning message on engine check or Overheat, fine! This message goes to all N2K devices as a pop up, extremely annoying at it and devices start beeping like there's no tomorrow!
Now my options are:

A. run this message on everywhere with the annoying beeping emitting from each device for 10-20secs and then I stop it
B. run it indefinitely till temp goes below the set limit and the reason for the message is removed from the system (could take long!)
C. as B but with a timer between each beep being say 2 or 5 mins, gives you time to think, work out something and still be able to look at the plotter or whatnot
D. run it till engine turns off (less than 15sec lowering rpm to killing the engine, with the annoying thing being that if you don't notice it you wont know why the generator turned off in the first place

Of course throughout all this process, you have RPM, Oilpressure, s/wpressure, coolant temp, egt all presented in the dedicated fin/gen touchscreen display. There you get a big red ERROR and the off limit values in red!

D seems to be the sensible thing to do, but I'm wondering what el. engines do in this respect since I cannot figure out a way to acknowledge and STOP the bleeding beeping and pop-up window!
Hitting OK, stops the current beep, but in x secs the next loop with the next beep turns up and you get a new pop up blocking practically all info on the display.
I do remember drag alarm, low water alarm etc on my Garmins can be shut up/off with a press of the cancel button, not in my routine though.
That's probably due to different NMEA2000 standard layout or company policy (in my case Garmin) dunno!

Ideas welcomed!

cheers

V.
 
D seems a reasonable option to me on the basis that the plotter keeps a log of fault messages you could refer back to after the event to see what had happened.
 
D seems a reasonable option to me on the basis that the plotter keeps a log of fault messages you could refer back to after the event to see what had happened.
hm, didn't know that MFD keep logs, have to check, thanks for the pointer!

well, turns out it was a silly s/w (or logic) mistake on my behalf, where I was switching between two different messages on the bus regarding this PGN effectively confusing the N2K devices into thinking that every .5sec there was a new event. Corrected it (1min job) now works fine.
Next issue is to establish at what oil pressure and at what coolant temp I should have them setup up to warn.
Currently 90C and 1.5bar oil but probably should lower the C and up the bar say 85 and 2.5, will test on the spot in the summer with 25+C water temp and decide

cheers

V.
 
Top