VVE epic struggle.

[Hib Halverson]

No worries... post some log files so I can play along.

Uh, well....I tried to upload the log file twice and each time it failed, so I sent it to you in an email. Is there a file size restriction for attached files in a forum post?

[Blacky]

I'm thinking I can use {GM.INJPWB1} in a similar expression and get duty cycle so I tried it and got this error when opening Scanner with that PID in my calc_pid file..

List index out of bounds (4).

What does that mean?

It means there's a fault in the EFILive software that is not handling the text in the calc_pids.txt file correctly. Do you still have the calc_pids.txt file that causes the error? If so can you please send me the file (paul@efilive.com) and I'll try and figure out why that error occurs (and fix it).

Regards
Paul

[Hib Halverson]

It means there's a fault in the EFILive software that is not handling the text in the calc_pids.txt file correctly. Do you still have the calc_pids.txt file that causes the error? If so can you please send me the file (paul@efilive.com) and I'll try and figure out why that error occurs (and fix it).

Regards
Paul

I fixed it. I found out I had some of the text on the wrong line. First, I had it as:

*CLC-00-003 0.0 100 0.1 "{GM.INJPWB1} * {SAE.RPM} / 1200"

%

...but it should have been...

*CLC-00-003
% 0.0 100 0.1 "{GM.INJPWB1} * {SAE.RPM} / 1200"



While I got ya, I have another geeky quesiton. Twice now, when I've updated the software, I forget to reload my file length spec into properties. As a result, when I data log, I run to the end of the specified file length and that locks-up my machine, I get the "not responding" message and I have to force Scanner to quite.

Isn't there a way to allow the user to save then quit when he/she hits the file length limit?

Of course...the solution is to change that in properties, but I keep forgetting.

[joecar]

The scantool should remember the properties across software updates.

[Hib Halverson]

The scantool should remember the properties across software updates.

I'd have thought so, too, but last week, I had problem with the 50,000 frame limit and lost a whole test session. So, I set properties at 250,000 frames. No problems after that, until today, which is after I installed the 27 Aug update. I lost another test session of data when it, once again, hit the 50,000 frame limit. This time I set it at 500,000 frames.

Hopefully, the next time I update the software, I'll remember to check properties before I take data.
(sigh)

[joecar]

I'll bring this to Paul's attention.

[Blacky]

I'd have thought so, too, but last week, I had problem with the 50,000 frame limit and lost a whole test session. So, I set properties at 250,000 frames. No problems after that, until today, which is after I installed the 27 Aug update. I lost another test session of data when it, once again, hit the 50,000 frame limit. This time I set it at 500,000 frames.

Hopefully, the next time I update the software, I'll remember to check properties before I take data.
(sigh)

Updating the software does not (or should not) alter the property settings. If you change any settings and the software crashes (or you kill it using Task Manager or by switching off or rebooting the PC) then the changes won't be saved because the changes are only saved when the software exists cleanly.

FYI the maximum data log size setting is stored in the registry here:


Regards
Paul