mmm ok...

well hopefully its ok..

good luck!

 

I feel your pain Jon, it sure does sound like a serious bust-up.

 

Best answer to the file count problem is the same as what most camera's do. They either create a new folder for every day, or a new folder for every power cycle. It also helps immenesly with organization.

 

FYI I started adding a page to the Wiki. Feel free to add to it:

http://evoecu.logic.net/wiki/Standalone_Logging

 

Can someone help me out with the proper script to trigger logging only when the car is running? I've tried multiple attempts including cut and paste from what others have done, as well as trying to create my own formula and have failed miserably. Thanks!

 

Doesn't it automatically log when the car is on? Do you have the car on for long periods without it running?

 

yeh...

u get a new log when you start the engine...

 

Yes. And, yes. However, unless I was reading incorrectly, I thought there was a way to make it log only when the car was running. Having a bunch of files on there when the engine isn't running isn't something I really want, if for nothing else, just to avoid all the hassle of mining through all the useless files.

With that being said, if it's not something that has been figured out at this point, I'm certainly okay with the current setup. In fact, many thanks to those who figured this out. It will save me from having to figure out a way to strap in a laptop on the track.

 

Oh, it could easily be done. Use a trigger of RPM > 0. But... Why the hell are you turning your car on and off without starting it? Isn't the point of a car to turn it on, drive it somewhere and shut it off?

 

Take a look at the wiki link I posted or the config file I posted. Just make sure your RPM pointer in the logstart / logstop commands is the same as the logged item above it (and as noted, I recommend adding speed too).

 

So my concern is the split second I go beyond the "on" location to start... I want to avoid it creating a log of this split second before I start the engine.

 

Okay... not sure why, but I got it working. I think I overcomplicated it earlier. Anyway, for those that are code-challenged like myself, it was a simple copy and paste from Fosty, and then substitute my nomenclature ("RPM") for what he had.

Now it only logs when engine is running. Yay. Here's what the code looks like, should this be able to help anyone in the future:

;-------------triggers---------------
;
; note that parameters must be previously defined
; before defining triggers using them
;
; triggers allow you to control when logging starts and stops
; this example sets up triggers such that logging only occurs
; when the engine is running (RPM > 0)
;
; triggers consist of some evaluation of the form [trigparam] [condition] [value]
; and a resulting action which is done if the evaluation is true

;paramname=CruiseLight
;paramid= 0x8045C5
;databits=1
;offsetbits=5
;isvisible=0
;priority=2

;conditionrpn = CruiseLight,1,==
;action = start

;conditionrpn = CruiseLight,0,==
;action = stop




; only log when the engine is running
conditionrpn = RPM,0,>
action = start
;
conditionrpn = RPM,0,==
action = stop

 

Anyone know if the conditionrpn can only do multiple/chained comparisons? I want to have it start a new file whenever I go WOT and come out of WOT but only if I have logging activated. Trying to do this:

If CruiseLight==1 && TPS>92 && #TPS<=92
"start a new file"

If CruiseLight == 1 && TPS <92 && #TPS >=92
"start a new file"

So I thought that would look like this:
conditiorpn = CruiseLight,1,==,TPS,92,>,&&,#TPS,92,<=,&&
action = newfile

conditiorpn = CruiseLight,1,==,TPS,92,<,&&,#TPS,92,>=,&&
action = newfile

But it doesn't seem to work. Any ideas?

Thanks!
verkion

 

https://www.evolutionm.net/forums/8914442-post120.html

;conditionrpn = CruiseLight,1,==,2ByteRPM,1500,>,&&
;action = start

;conditionrpn = CruiseLight,0,==,2ByteRPM,1500,<,||
;action = stop

; start logging to a new file when the throttle goes from previously below 80 to above 80
; #throttle refers to the previous throttle sample
;conditionrpn = TPS,80,>,#TPS,80,<=,&&
;action = newfile

-----

You might try excluding the cruiselight condition if you are already logging, or use a start stop command instead of the newfile command if you only want to log when WOT (and exclude your third condition with the previous value variable). I'd also recommend lowering the TPS threshold since you want to make sure it is logging during spool and your max TPS might only be 93.

 

Thanks for moving the thread!

That's a good point regarding the Cruiselight condition. It should only generate/increment the file number when it is ALREADY logging right? i.e. the action = newfile won't do anything anyways when its not logging.

Thanks!
verkion