Undoubtedly finger trouble on my part, but I don't seem to be getting any logs in circumstances I really want them.
Just been out to test gear cut, but the only 3 logs are totally useless and just cover pootling around not the actual launch or through-the-gears runs.
Datalogging start speed = 2000rpm
start throttle = 20%
stop engine speed = 1900rpm
stop throttle position = 125% (seems to be the default, although maybe a bit odd)
stop timeout = 5000ms
What else determines when a log should be captured? Surely a full 5000 rpm 1st gear launch would start the log!!
Firmware version 1.29 if relevant. Think I've seen this before after flashing a new CAL - no logs, but then a few days later logs seem to start working properly, but not 100% confident of this or of the circumstances.
Logging - doesn't happen.
Re: Logging - doesn't happen.
Check your calibration switches/Logging Switches Enable.
Re: Logging - doesn't happen.
Also be sure your SCfg file is there
Re: Logging - doesn't happen.
As secure says, there is now a "logging switch" which can be defined in the I/O or you can use a cal switch position to define it, which is likely to be the issue.
Re: Logging - doesn't happen.
Logging enable switch is set to ON for all CALs.
I did get logs, just not triggered/captured for anything other than the pootling around. SCfg is there as the logs have all the data I have requested to be logged.
I did get logs, just not triggered/captured for anything other than the pootling around. SCfg is there as the logs have all the data I have requested to be logged.
Re: Logging - doesn't happen.
With "stop throttle" at 125% it will stop after 5000ms of TPS<125%
Try this, it will start once throttle goes above 20% and engine speed goes above 2000rpm, then continue until throttle is less than 8% and engine speed is less than 1300rpm for 10 seconds
Datalogging start speed = 2000rpm
start throttle = 20%
stop engine speed = 1300rpm
stop throttle position = 8% (seems to be the default, although maybe a bit odd)
stop timeout = 10000ms
Try this, it will start once throttle goes above 20% and engine speed goes above 2000rpm, then continue until throttle is less than 8% and engine speed is less than 1300rpm for 10 seconds
Datalogging start speed = 2000rpm
start throttle = 20%
stop engine speed = 1300rpm
stop throttle position = 8% (seems to be the default, although maybe a bit odd)
stop timeout = 10000ms
Re: Logging - doesn't happen.
Paul, many thanks for the input.
Not sure the 125% fully explains the lack of logs...if the log was started just prior to the launch and I launched within 5 seconds, then i would have captured at least part of the run. If the 5s expired before I launched, then a new log should have started as a result of the launch, even though I may have only got 5s worth?
Unless I'm missing the point *as always*
I've been back through my Calibration archive, and the 125% stop throttle position dates back to my first 1.24 firmware CALs when this feature was introduced. And it seems to be the default for new CALs.
Maybe earlier ecu firmware behaved differently with this value and a fix is in 1.29 onwards. It could explain why I saw inconsistent behaviour when first loading up a new CAL (or new firmware, not sure) and thereafter is seemed to work, although it perhaps shouldn't have done. I will change to 8% and report back...although suspect/faulty FPR has stopped play for now
Not sure the 125% fully explains the lack of logs...if the log was started just prior to the launch and I launched within 5 seconds, then i would have captured at least part of the run. If the 5s expired before I launched, then a new log should have started as a result of the launch, even though I may have only got 5s worth?
Unless I'm missing the point *as always*
I've been back through my Calibration archive, and the 125% stop throttle position dates back to my first 1.24 firmware CALs when this feature was introduced. And it seems to be the default for new CALs.
Maybe earlier ecu firmware behaved differently with this value and a fix is in 1.29 onwards. It could explain why I saw inconsistent behaviour when first loading up a new CAL (or new firmware, not sure) and thereafter is seemed to work, although it perhaps shouldn't have done. I will change to 8% and report back...although suspect/faulty FPR has stopped play for now
Re: Logging - doesn't happen.
Yes you are missing the point. The TPS needs to be below 125% AND the speed below 1900rpm for 5 seconds.
Also check you're not logging lots of info like some random channels at 1khz, I think a full datalog file is about 326kb compressed. Scfg will tell you your logging time per MB and you have 1 MB on the S6.
To work this out, get to the logging menu in Scal and on the RHS of the screen it will give you the logging status that will tell you what's missing.
Also check you're not logging lots of info like some random channels at 1khz, I think a full datalog file is about 326kb compressed. Scfg will tell you your logging time per MB and you have 1 MB on the S6.
To work this out, get to the logging menu in Scal and on the RHS of the screen it will give you the logging status that will tell you what's missing.
Re: Logging - doesn't happen.
I have 422 seconds of logging according to SCal, so that wouldn't explain logging issues.
My logging setup has not changed, yet a full LC launch was not captured. If TPS had to be <125% AND rpm <1900rpm, then basically my logging is only stopped by rpm not TPS. The launch and WOT run to 70mph would have been logged, but it wasn't.
I can't go and retest since I do appear to have both a knackered FP sensor and FPR - having replaced the sensor I'm now getting 10 bar+ static FP which will soon kill the sensor again until I fix the FPR fault. Possibly died through use of methanol although I thought Fuelab ones were OK - I will dismantle it tomorrow and see what's going on.
My logging setup has not changed, yet a full LC launch was not captured. If TPS had to be <125% AND rpm <1900rpm, then basically my logging is only stopped by rpm not TPS. The launch and WOT run to 70mph would have been logged, but it wasn't.
I can't go and retest since I do appear to have both a knackered FP sensor and FPR - having replaced the sensor I'm now getting 10 bar+ static FP which will soon kill the sensor again until I fix the FPR fault. Possibly died through use of methanol although I thought Fuelab ones were OK - I will dismantle it tomorrow and see what's going on.
Re: Logging - doesn't happen.
Then I would look at the logs to see why they ended, did you run the car for more than 422 seconds from time of launch? Is your TPS reading correctly? Did you program the changes? Do ALL your cals have logging switch set to "on"?
You can set the start RPM to 0 and the TPS start to less than your resting TPS and it will begin logging.
I would also check the ECU time, could it be that you've not set the RTC properly and your logs are there but not in the list where you expect them to be?
When looking at things like this, it pays to do it in Scal and test the setup looking at the output variables such as Logging state etc, obvious if the logging is suspect you can't log the variable to see what's happening.
I would have to say it is something you are doing, I've used a similar logging setup on all the 1.29 cars I ran at TOTB without issue.
Is your FPR dead or the sensor itself?
You can set the start RPM to 0 and the TPS start to less than your resting TPS and it will begin logging.
I would also check the ECU time, could it be that you've not set the RTC properly and your logs are there but not in the list where you expect them to be?
When looking at things like this, it pays to do it in Scal and test the setup looking at the output variables such as Logging state etc, obvious if the logging is suspect you can't log the variable to see what's happening.
I would have to say it is something you are doing, I've used a similar logging setup on all the 1.29 cars I ran at TOTB without issue.
Is your FPR dead or the sensor itself?