Megasquirt Support Forum (MSEXTRA)

I'm having trouble with "Triggered Logging" and the "Stop Logging When" function. My goal is to manually start the datalogging when I want to, but when I shut the car off I want the datalog session to be automatically stopped.

I currently use the function of Simple: rpm<500. It works as long as you dont go offline.

Question: Do I have the correct trigger or is there a better configuration?

I tried triggered logging today too and it wouldn't stop...

Start: tps > 95
Stop: rpm < 3500

Started logging no probs, but because I changed from button to trigger I couldn't stop the log.

Sent from my SM-G930F using Tapatalk

You should be able to change the log length limit to say 2 min and then have it not start a new log.

I understand you could do a time based one stop trigger...

I like to make different datalog lengths:
- Commute to and from work - 30-45 minutes
- Quick trips to the gas station/grocery store 5-15 minutes
- etc

I dont want to have to stop the datalog each time, but also not be limited to a set time as well. Is there another stop trigger that can be used to stop the datalog upon turning off the engine?

Unfortunately it will not be possible to stop logging based on the connection status or the ignition state, and using a runtime variable will not work either because if the ECU looses connection the output channels no longer get updated and so the RPM limit will never read below 500 even though it technically now reads zero on the gauge. That is why it works when you do not go offline, TS gets a read that the RPM has gone below the set limit.

We are going to look into another solution for a future release.

Yes, I played with this today.
There are a couple options if you use an expression that includes AppEvent channels like controllerOnline, so I thought this should be doable.
However, the trouble is, the evaluation only takes place when runtime data is read. So, when it does go offline from a key off, there are not more runtime evaluations. In the beta, I will be adding some mechanism to trigger a re-evaluation of the expression.

Thank you for looking into this as I believe this would be a great feature that I know more than I would be using.

Please let me know if this able to be added to TS, and I will try it out immediately.

I was curious if there has been any additional expressions added to trigger the "Stop Logging"?

Any update and/or timeframe for this?

I do have it set to at least reevaluate upon going online or offline for the next beta.

So if you stop expression contains !isOnline() , it will stop logging.

LT401Vette wrote:I do have it set to at least reevaluate upon going online or offline for the next beta.

So if you stop expression contains !isOnline() , it will stop logging.

Hi, I just test the expression you said "!isOnline()" and seem to not working. I have the newest beta version of TS.


Thanks,

Martin

Hmm, I just tested it with 3.0.60.55 against an MS3 using a start condition of:
RPM > 2000

Stop condition:
!isOnline()
and rpm == 0 || !isOnline()

It seems to be working here.

What is your full start and stop condition?

I just saw this and will test it out to see if it works on my MS2 Platform.

This would address my issue of stopping the datalog on the event of turning off the vehicle