@upstart are you logging data connections? Make sure it is not checked in as those logs can grow very fast. Saillogger is efficient with its storage and won't need those log files.
Thank you, that's brilliant. i noticed it did record correctly engine hours but I wasn't seeing this reflected when playing back the trip. have now added a monitoring section to include RPM so hopefully this will show up.
so much great information, its brilliant.
Hi @mshulman sorry for the delay in responding. Is there a possibility that there were multiple GPS sources at the time this is happening? If multiple sources report slightly different positions it may trigger a movement. If so, and this is happening frequently you can consider limiting your position reports to a single device. It is explained in FAQs.
@Voodoo I don't really need to integrate my 2 old yanmar 4jh4 with the nav system.
Im happy with old fashioned analogue control panels, no need to monitor Bar and Celsius in NMEA or sailllogger. All I would like to achieve is engine status monitoring (running/not running) for trip's logs and statistic.
In my current setup I already have a Victron shunt for engines' alternators (separate 24v 110A alternators) that tiggers "motoring" path in SignalK when minimum 1 engine is running (and alternator charging the house batteries. I can also try using digital inputs of Cerbo to get on/off status control of each engine (we are a catamaran).
Hi everyone, we just released native support for engine sensors! They are now logged automatically, along with statistics for your sailing and motoring time. Check out the announcement here: https://community.saillogger.com/topic/142/saillogger-plugin-5-x-native-engine-logging