v2 still only logging for a few minutes..

[ringram]

I am all software'd and flashed up with the latest files from the downloads page. fw_02_05_19

When BBL I only get maybe 30min max. Normally 10Mb files, today with the new FW only 5Mb or around 20min

My trip is 2hrs.

Am I doing something wrong...?

[Chuck CoW]

I am all software'd and flashed up with the latest files from the downloads page. fw_02_05_19

When BBL I only get maybe 30min max. Normally 10Mb files, today with the new FW only 5Mb or around 20min

My trip is 2hrs.

Am I doing something wrong...?

Hmmmmmmmmmm..... Well, interesting.....I just upgraded to the latest stuff and it seems that with E67 controllers (or maybe can controllers in general) I go logging for 10 to 15 mins and then the EFI LIVE scantool just locks up....

I'm still connected, but....the screen freezes and nothing happens.....

Anyone else??

Chuck CoW

[XLR8NSS]

I am not upgrading to the latest then if it's doing this again. :p

I am on the update before the latest and it works fine. Mine was doing this on a couple of the previous updates and Paul fixed it.

E38/T43 controllers for me.

[ringram]

Yeah mine was doing it on an older firmware, hence why I upgraded! :(
Not good for doing VE tables.

Paul Help! E38 here. HSV OS E Series R8

[swingtan]

Guys, have you checked the number of PID's you are logging? I can log for a good 25 minutes and end up with a log file of 2MB in size ( E38 ). I've also performed a few extended log sessions where I've turned the engine off and allowed the V2 to enter suspend mode, then restarted the log the next time I've driven the car. Any chances you can post a log from one of these sessions where the V2 has locked up?

Simon

[ringram]

Its too big to attach to the message, so you can DL it here.
This is from a 1hr45min log session

http://www.systemsup2.plus.com/BBL00047.zip

[swingtan]

OK, you have a PID count of 19 and a channel count of 25, so I doubt that's an issue. I usually log with 22 PID's and 34 channels with no issues. Was this a log when the V2 hung or a normal log?

I take it you have checked the Firmware version in the V2?

Simon

[ringram]

Latest version as noted above squire with a reformatted config file system.
The copied the files from the new 8.1.1 over and the options.ini as well

[swingtan]

Have you tried wiggling the main ODB-II cable to see if there is an intermittent connection? I know with mine that if I wiggle the cable just near the RJ45 plug, the V2 will reboot, indicating a bad connection. You may be getting a bad power feed into the V2, causing it to lock up.

[hrthsv]

Ringman I am using the latest release firmware version 19 same as you and have logged 500km in one day where the car was switched off twice and still got it all on 1 log. Must be something going wrong with your V2. I was logging on E 40 PIDs for Ls2.

[ringram]

Hmmm... interesting. Ill do some more checking then. Maybe the cable is dodgy, It does fall on the floor and generally thrown around at times.. the v2 that is.

[ringram]

Ok retested. On file close there was 348,000 frames done over about 90min
Saved file was only 6mb and only has the magic number of exactly 50,000 frames! The same as the last log...

V2 was still logging on the display when I closed the file off onto SD.

So looks like max file size is 50,000 frames. Firmware is dated 7 July as above.

http://www.systemsup2.plus.com/BBL00048.zip (http://www.systemsup2.plus.com/BBL00047.zip)

Any news on this Paul?

[hrthsv]

I just checked my BBL log, the 500km one and it had 239,660 frames on the log, went from 9.30am to 4.06pm (with stops). For example 43.1 map at 1600rpm had 33,461 hits. So something is wrong with a setting somewhere. I am using a PLX WB without the digital upgarde maybe there is a difference with that?

[ringram]

No WB here yet, just 50k frames max. I cant see any settings anywhere regarding max frames, so Im at a loss to figure it out.

[swingtan]

I just checked your log file......

FRAMECOUNT=00178353

This was taken from the log metadata.

I can open the log in Scan-Tool and see the very last frame, 178352

Open the Scan-Tool and go to the following menu option,

Edit - Properties - Logging

In the box for "Frames (x1000)" enter something like 500, then click on "OK"

See if you get the results you are looking for ;)


Simon

Edit: The reason this appears for E38 controllers is the increased frame fate over the LS1. The E38 will do 40FPS vs 10FPS for the LS1, so you get 4 times more frames for the same period of time.

[hrthsv]

Yes, I bet that's it when I was using the V2 as a pass through to the laptop I had to increase the frames or it wouldn't log more than 1 1/2 hours. Your V2 is probably BBL logging it but your scan tool when you download on the computer isn't displaying it.

[ringram]

Nice detective work!
That allows me to see 99,900 but it looks like there is a hard limit on that now. I tried all sorts of values. Im using 7.5.4 build 65. What are you using Swingtan?

[swingtan]

You are correct. there is a 1,000 (x 1000) limit to the number of frames to display. I queried this a while ago and then forgot about it, but the limit was supposed to be raised. RE: this thread.... http://forum.efilive.com/showthread.php?t=8103&page=3

I think it got missed in the final release though. I don't believe that there is a way to "split" a log file before displaying, but you should be able to select the section of the log not being displayed and "crop" the unselected porting from the log file. Once done, a "re-plot" should show the data, but don't forget to "save as" a new log file so you don't overwrite the original file.

The new ScanTool V8 should be much better at handling these big log files.

Simon

[XLR8NSS]

http://forum.efilive.com/showthread.php?t=8521

Check the link above about the 99,900 frame display deal.

[ringram]

Ok, good, so it crunches all the numbers, but only shows 99,900 in the display? I can live with that if thats the case.