no logging after first cal-flash

[dian]

a few days ago i managed to do my first cal-flash, i didnt change much, just the maf delete prodedure, fan temp and a mod in the trans management. it seems to have worked well, car drives o.k. and engine light is off. now i tried to do some logging and it doesnt work. it loggs normally (tp) untill i crank the engine. then it quits after 3-4 frames, generating errors 12 and 22. (logging worked before the flash, using firmware 2.07.82 and v7.5.7/283.)

what to do?

[joecar]

Download and install V7 and V8 from here: Sep-2015-EFILive-Public-Pre-Release (https://forum.efilive.com/showthread.php?25922-Sep-2015-EFILive-Public-Pre-Release)

then update V2 firmware (start V8 S&T and click Check Firmware...).

[dian]

thanks. i intalled all that stuff 2 months ago and had great trouble making it work. so i really have to do it all again? why? what happened?

[Chevy366]

Get use to it it is common practice with EFILive, kind of gets old after a while.
Great product, just screwy development execution.

[joecar]

thanks. i intalled all that stuff 2 months ago and had great trouble making it work. so i really have to do it all again? why? what happened?Paul wants to avoid mixing old firmware with new software (because he has fixed a bug or improved something or for some other reason)...

the steps are easier now than ever:
1. install V7,
2. install V8,
3. start V8 S&T and click Check Firmware, the rest is fairly obvious (if the firmware needs updating you will see a button "Update Firmware", click it),
4. and it also shows you if the V2/BBx config files need updating (you will see a button to update the files).

[joecar]

thanks. i intalled all that stuff 2 months ago and had great trouble making it work. so i really have to do it all again? why? what happened?If you do the update, you could have the following outcomes:
1. problem solved;
2. problem persists;
3. new problem shows up;

for 2 and 3, Paul cannot (and really should) repair an old version of software/firmware... any repairs must be done on the current version (otherwise you end up with umpteen different current versions, and nobody will be sure which version is for which situation);

it is far better to update to latest version and if problem persists Paul will fix it.

[joecar]

Get use to it it is common practice with EFILive, kind of gets old after a while.
Great product, just screwy development execution.I understand what you're saying, but that will limit the software's ability/correctness/quality/features without having exponential current versions.

( show us some other tuning packages that have the features you see here... )

:)

[joecar]

a few days ago i managed to do my first cal-flash, i didnt change much, just the maf delete prodedure, fan temp and a mod in the trans management. it seems to have worked well, car drives o.k. and engine light is off. now i tried to do some logging and it doesnt work. it loggs normally (tp) untill i crank the engine. then it quits after 3-4 frames, generating errors 12 and 22. (logging worked before the flash, using firmware 2.07.82 and v7.5.7/283.)

what to do?If the problem persists with the new software/firmware, then here are some questions:
- what are you using to log (V7 scantool, V8 scantool, V2 BBL)...?
- can you post any of those logs...?
- what file did you cal flash (post it here)...?

[dian]

so i updated all the stuff and this time it went well. the logging works again. can you explain what happened? i have a working software/hardware system and it quits because of a cal-flash? or was it something else?

btw, you say "v8 scantool". i was unaware v8 worked for scanning.

edit: well, logging doesnt really work. after 3-4 frames it stops for 3-4 seconds and then resumes. so when doing startup/idle tuning you mis the first seconds. no good i reckon.

[joecar]

so i updated all the stuff and this time it went well. the logging works again. can you explain what happened? i have a working software/hardware system and it quits because of a cal-flash? or was it something else?
I don't know exactly what happened, but one of the software builds earlier this year had a bug related to EXT pid logging.


btw, you say "v8 scantool". i was unaware v8 worked for scanning.
Yes, this is fairly new and still being developed (does not yet do some things like maps and DVT).


edit: well, logging doesnt really work. after 3-4 frames it stops for 3-4 seconds and then resumes. so when doing startup/idle tuning you mis the first seconds. no good i reckon.I presume this is with V7 scantool... can you post this log file.

[dian]

i will try. iv never done it before. could take a while before i find out how its done.

[joecar]

i will try. iv never done it before. could take a while before i find out how its done.
See post #2 here (start at step 5): Hosting-an-Image (https://forum.efilive.com/showthread.php?3064-Hosting-an-Image&p=38410&viewfull=1#post38410)

[dian]

thanks. around frame 80.

[dian]

so no ideas about the missing 3 seconds?

[joecar]

I see at frame 80 the time jumps by about 4 seconds... I sent a pm to Paul.

[dian]

well, today it started acting up again, im often getting " ERR_Response/5, response $01:." after i start logging/monitoring, but sometimes not. also gm.mapboost_dma is dead when ignition is on, while gm.map in volts is active. sae.map is also active. however after shutting angine off it seems to show ambient pressure. do i have some kind of hardware issue?

[Blacky]

The log you posted shows 3 places where data was skipped for more than 1 second.



Frame 80: skipped 3.11 seconds
Frame 3880: skipped 1 minute and 03.319 seconds
Frame 5177: skipped 4 minutes and 04.002 seconds


I'm pretty sure the second two skips were when the log file was deliberately paused. Please let me know if you did not deliberately pause the log file at those frames.

The first one at startup on frame 80 may be caused by a voltage drop during cranking. The pause occurs immediately after the RPM goes above zero - i.e. as soon as cranking starts. When starting the vehicle, can you watch FlashScan to see if it reboots (due to lack of voltage).

The error response $05 is an old issue in an old version of the V7.5 Scan Tool software. If it is happening in the latest software, that needs to be addressed. If you get that error again, then immediately stop the data log (if it doesn't stop automatically on that error) and then save a "User error report" by selecting the menu option: File->Generate error report. Then save the report and email it to me at paul@efilive.com. Include a link to this thread so I know what its about.

One last thing that may be relevant, some laptops have a hard drive protection scheme that disables reading/writing to the hard drive if/when excessive vibration or acceleration is detected. A laptop sitting in a vehicle can experience such vibration and/or acceleration. During the time the hard drive is disabled some data may not be logged.

There are a few ways to get around that:

Disable the protection - although I don't recommend doing that as the hard drive may actually end up being physically damaged if/when it attempts to write while there is excessive vibration or acceleration.
Log to a USB thumb drive - to do that you need to change the "Temporary cache" folder to point to your thumb drive in the Properties->Folders setting.
Use FlashScan's black box logging features to log your data.


Regards
Paul

[dian]

18922
18923

these are two logs of startup. in the second i have conected a second, big battery so voltage stays above 10v. the laptop is on the seat on a piece of foam and i dont have a cam, so i think acceleration/vibration issues can be excluded. it skips 3 seconds on every start up. and yes, the last two pauses were intentional.

18924
18925

these are two bug reports showing the #05 error. i have figured out this only happens when the analog inputs are pluged in, so i connect, take out plugs, start logging, start engine and plug them in. then it works. what to do?

[Blacky]

Thanks for the trace files and log files and for this description of the problem:

these are two bug reports showing the #05 error. i have figured out this only happens when the analog inputs are pluged in, so i connect, take out plugs, start logging, start engine and plug them in. then it works. what to do?

Once I realized it only occurred when the AD was connected it made it much easier to track down the issue. I have located the error. I'll get it fixed asap.

Can you confirm whether or not the delay at the start of the log is related to having a voltage above about 1V input into AD1 or AD2? I.e. does the delay ONLY occur when you have a voltage input into AD1 or AD2? Or does the delay happen regardless of whether anything is connected or not?

Regards
Paul