BBL - Take Two

[TAQuickness]

Got my second shot at BBL Beta... It's come a long way in a short time I managed to get 7 logs and a DTC dump. This was purely a BBL test and no pass-thru attempts.

OS:
02020005

BBL FW:
FW: 12


Anomalies
Firmware Update:

1. None

BBL:

1. I don't recall if this feature is supposed to be available yet, but I attempted to clear the DTC's (P0102, P0103, & a Bxxxx [can't remember the number]) and I get a $0311.

EE:

1. While attempting to move my logs via EE, I opted to use Windoze Explorer to create a new folder: default\V7\Logged data\BBL Beta. EE's tree browser did not pick up the new folder, but the content browser did. Tried double clicking the folder in the content browser and the tree browser refused to acknowledge the existence of the new folder. Must close and respawn EE to get the new folder acknowledgement.

2. I thought I remembered reading that EE would now remember the last folder accessed upon respawning. No worky.

3. Something falls asleep... I let V2 and my laptop sit idle for about 30 minutes (no screen savers or low-power modes) while EE was viewing "Scan Files". I clicked "Tune Files", "Refresh (F5)" and got an $0101. I immediately clicked refresh again and got nothing (as anticipated).

4. F5 to refresh scan, tune, config, & firmware does not work



Suggestions

Firmware:

1. Updating the firmware tends to reset the splash screen and configured settings. Not sure if it's possible, but it would be nice for V2 to retain user-defined settings when new firmware is applied. Perhaps suck them out [UD settings] , apply new firmware, and then restore the settings.

Edit: Does not seem to be a problem with FW14... Thanks Paul

BBL:

1. Setting the PIN (F4-F3-F4) - I would have anticipated this option to appear under settings.

2. When starting a log, if no vehicle or PID's are selected, automagically navigate to the vehicle selection menu, then start logging
When attempting to write to an SD card that is not properly formatted (NTFS as opposed to one of the FATs), prompt user "SD card not formatted, do you wish to format?" then "Are you sure you're sure?"

3. At the moment, I'm not sure what could possibly be done about an accurate or meaningful file attribute time stamp, but it would be nice to have.

4. When the choice of PID's to be logged is available, the ability to choose which will be viewable. ;)

EE:

1. When viewing V2 scan files, and assuming tune files will work similarly, an option should exist for you to select internal or SD memory. It should also have an intuitive indication that you are looking at SD or internal memory.

2. I'm thinking EE could use a connectivity window and message zone. See the first attachment. Hopefully the end product could look a lot better than my photochop


Honorable Mention


Firmware:

1. I like it a lot better than pre-BBL beta testing. The procedure is much more intuitive.

BBL:

1. I like the deletion of the pause option. When I first noticed it missing, it caused me to pause and recollect of a time that I ever needed to pause a pass thru log. Never done it.

2. Audibles kick ass. I chose to use the default TPS audible as my test, cranked up the box to about 103db, and WOT [straight pipes mind you], I could hear that TPS = 100%.

EE & Hapi:

1. I really like the autodetect in this release.

2. Diggin the status bar on EE

[Blacky]

Got my second shot at BBL Beta... It's come a long way in a short time I managed to get 7 logs and a DTC dump. This was purely a BBL test and no pass-thru attempts.
Thanks for taking the time to document your testing - makes my job a lot less stressful :cheers:


1. I don't recall if this feature is supposed to be available yet, but I attempted to clear the DTC's (P0102, P0103, & a Bxxxx [can't remember the number]) and I get a $0311. Whenever you see a $03xx error it is an error being returned from the vehicle's controller. In that case, can you please generate a trace file and send it to me. You can generate a trace file using the Scan Tool->Options->Trace menu option.


1. While attempting to move my logs via EE, I opted to use Windoze Explorer to create a new folder: default\V7\Logged data\BBL Beta. EE's tree browser did not pick up the new folder, but the content browser did. Tried double clicking the folder in the content browser and the tree browser refused to acknowledge the existence of the new folder. Must close and respawn EE to get the new folder acknowledgement. Fixed now


2. I thought I remembered reading that EE would now remember the last folder accessed upon respawning. No worky. Works fine here, what steps does it require to reproduce the problem?
Note: the last used forlder is stored in EFILive_Explorer.ini in the same folder as the exe.


3. Something falls asleep... I let V2 and my laptop sit idle for about 30 minutes (no screen savers or low-power modes) while EE was viewing "Scan Files". I clicked "Tune Files", "Refresh (F5)" and got an $0101. I immediately clicked refresh again and got nothing (as anticipated). This one is still a mystery - any info you can add would help.


4. F5 to refresh scan, tune, config, & firmware does not work Works fine here, what steps does it require to reproduce the problem? Or do you mean the refresh button works ok, just not the F5 hotkey?


1. Setting the PIN (F4-F3-F4) - I would have anticipated this option to appear under settings. Good call, I have changed it to be under Settings.


2. When starting a log, if no vehicle or PID's are selected, automagically navigate to the vehicle selection menu, then start logging I'm still thinking about the best way to handle it. I would like to have the most recently used vehicle be pre-selected when FlashScan starts. That would eliminate not having a vehicle selected. Unless the *.pmm or Options.ini files are not set up correctly - but then the "problem" is on a whole different level.


When attempting to write to an SD card that is not properly formatted (NTFS as opposed to one of the FATs), prompt user "SD card not formatted, do you wish to format?" then "Are you sure you're sure?" If the FAT file system library I was using would return *valid* error numbers to me I would. All I get back is "file not found" - even when the file system is not formatted. If it was just a missing folder, then formatting the file system is overkill. I may need to hack into the FAT library and add more detailed error feedback.


3. At the moment, I'm not sure what could possibly be done about an accurate or meaningful file attribute time stamp, but it would be nice to have.
This is what I plan to do:
Whenever EE connects to FlashSCan or AutoCal it will set the date/time from the PC. THere will be an option in EE to save the current date/time to flash memory. So just before you head out to the vehicle, select that option, then when you plug into the vehicle the date/time will be read from flash memory and will only be a minute or two behind the real time. For log file time stamps that should not matter.
The real solution is to have a battery backed clock (its in the design specs for FlashScan V3).


4. When the choice of PID's to be logged is available, the ability to choose which will be viewable. ;) Yes.


1. When viewing V2 scan files, and assuming tune files will work similarly, an option should exist for you to select internal or SD memory. It should also have an intuitive indication that you are looking at SD or internal memory. Yes.


2. I'm thinking EE could use a connectivity window and message zone. See the first attachment. Hopefully the end product could look a lot better than my photochop Yes, EE will have a lot more info and functionality added.
Note: a lot of the info you show is available in EFILive_Hapi.


1. I like it a lot better than pre-BBL beta testing. The procedure is much more intuitive. With lots of feedback it will slowly get more steamlined and easier to use.


1. I like the deletion of the pause option. When I first noticed it missing, it caused me to pause and recollect of a time that I ever needed to pause a pass thru log. Never done it.
THe pause option is still there (ok button). But the messages do not display. The left green LED shows whether the log is paused or not. Its useful when sitting at a red traffic light for 3-4 minutes - if you're not interested in logging idle.


2. Audibles kick ass. I chose to use the default TPS audible as my test, cranked up the box to about 103db, and WOT [straight pipes mind you], I could hear that TPS = 100%. Should be good for a shift buzzer too :)


1. I really like the autodetect in this release. It was always the goal.

Regards
Paul

[TAQuickness]

Thanks for taking the time to document your testing - makes my job a lot less stressful :cheers: Always a pleasure.


Whenever you see a $03xx error it is an error being returned from the vehicle's controller. In that case, can you please generate a trace file and send it to me. You can generate a trace file using the Scan Tool->Options->Trace menu option.
Will do. Safe to assume then that the clear DTC functionality should be there?



Works fine here, what steps does it require to reproduce the problem?
Note: the last used forlder is stored in EFILive_Explorer.ini in the same folder as the exe. Now that you've stated it should work, it does. I opened/closed EE 3 or 4 times yesterday and each time I had to drill back down to my Live folder... :bash:


This one is still a mystery - any info you can add would help. Can't too much more. Something between V2 and whats on my laptop screen falls a sleep. The first time I try to refesh the contents of the file system, I get an error. Immediate subsequent attempts work fine.


Works fine here, what steps does it require to reproduce the problem? Or do you mean the refresh button works ok, just not the F5 hotkey? Sorry, F5 hotkey was not working for me. I tried placing focus to several different areas of EE and I could not get the hot key to work (clicking the refresh button causes a brief green LED flash on V2)


I'm still thinking about the best way to handle it. I would like to have the most recently used vehicle be pre-selected when FlashScan starts. That would eliminate not having a vehicle selected. Unless the *.pmm or Options.ini files are not set up correctly - but then the "problem" is on a whole different level.

I would like for it to remember the last used vehicle, but then I thought it might be a problem for tuner shops. If V2 remembers the vehicle, can it scan to make sure the vehicle type is correct, and if not, present the PID/Vehicle selection list?


If the FAT file system library I was using would return *valid* error numbers to me I would. All I get back is "file not found" - even when the file system is not formatted. If it was just a missing folder, then formatting the file system is overkill. I may need to hack into the FAT library and add more detailed error feedback.
:notacrook:


This is what I plan to do:
Whenever EE connects to FlashSCan or AutoCal it will set the date/time from the PC. THere will be an option in EE to save the current date/time to flash memory. So just before you head out to the vehicle, select that option, then when you plug into the vehicle the date/time will be read from flash memory and will only be a minute or two behind the real time. For log file time stamps that should not matter.
The real solution is to have a battery backed clock (its in the design specs for FlashScan V3).

Could the user selectable option be to not save the date and time? I can see myself forgetting to check that box already.


Yes, EE will have a lot more info and functionality added.
Note: a lot of the info you show is available in EFILive_Hapi.
I did notice that in Hapi. But I'm lazy :D


With lots of feedback it will slowly get more steamlined and easier to use.



THe pause option is still there (ok button). But the messages do not display. The left green LED shows whether the log is paused or not. Its useful when sitting at a red traffic light for 3-4 minutes - if you're not interested in logging idle.

Cool. I'll give it a shot.

[SV8346]

Should be good for a shift buzzer too :)

Regards
Paul


yeah thats exactly what i have set mine up to do. beeps at me 200rpm before rev limit.

[Garry]

I'm still thinking about the best way to handle it. I would like to have the most recently used vehicle be pre-selected when FlashScan starts. That would eliminate not having a vehicle selected. Unless the *.pmm or Options.ini files are not set up correctly - but then the "problem" is on a whole different level.

Many folks will probably work with one car for a while, so saving the type last used would be a help ... maybe you can store the VIN of the vehicle last scanned, and only require the user to re-enter the type if there's a mismatch, or if reading the VIN fails ...

[Garry]

yeah thats exactly what i have set mine up to do. beeps at me 200rpm before rev limit.
Nice idea, but I like my EFILife-configured Stock PCM shift light ;) Would be worth trying out the audible version, though ...

[SV8346]

unfortunately the holden commodore SV8's dont get the factory shift light.

[Garry]

If it's the regular Gen III LS1 PCM, you can add it, just as I did on my Firehawk ;) All it takes is a line to the unused pin on the PCM, half a dozen 2V LEDs, a resistor, and 12V link ... oh, and a changed entry in the PCM via EFILive ;)

[SV8346]

sounds good, where do i find some more info on how to do this.

[Garry]

There's two threads that contain just about anything you need ...
http://forum.efilive.com/showthread.php?t=3333 and http://forum.efilive.com/showthread.php?t=4160 ...

[XLR8NSS]

Tried to BBL on my truck today with no luck at all. I selected E38 manual from the list and when I hit F1 to start recording V2 said I did not have any PIDS selected. No Trace file is produced for this.

I then tried selecting E38 Auto. When I hit F1 to record all goes well until the data page comes up. The timer starts counting. The frame counter just sits at 0. The data doesn't display anything at all. I have a trace file for this that I will send.

[XLR8NSS]

Ok, I just looked in the V2 to retrieve the .efx file and there was a log file in there. So, the V2 was scanning but, not displaying any data on the screen or updating the frame counter.

[Blacky]

If you have not already, please try turning the ign on before connecting FlashScan.

Regards
Paul

[Blacky]

I found a potential fault that will cause cause the problem shown in the trace file. It will be fixed in the next firmware update.

Regards
Paul

[Blacky]

Tried to BBL on my truck today with no luck at all. I selected E38 manual from the list and when I hit F1 to start recording V2 said I did not have any PIDS selected. No Trace file is produced for this.

I can see in the trace file your truck is an auto. Is it an Allison transmisison?

Regards
Paul

[XLR8NSS]

I can see in the trace file your truck is an auto. Is it an Allison transmisison?

Regards
Paul
No, it is a 6L90E(6 speed) with the T43 controller.

I am going out to try the turning the ignition on first. I THINK it was on when I connected last time but, can't say for sure.

Be back in a bit. :)

[Wasted Income]

(its in the design specs for FlashScan V3).



:eek:

Maybe this was covered somewhere else, but can I change the PIDs to log via the config.ini file?

[XLR8NSS]

Well, now it says it's saving the trace files but, there is nothing on the internal memory or the SD card. :( I will wait until tomorrow to mess with it again.

Anything you want me to try tomorrow?

[Blacky]

:eek:

Maybe this was covered somewhere else, but can I change the PIDs to log via the config.ini file?

In the folder EFIlive_Hapi\PID Descriptions are a bunch of *.txt files that show you the PIDs that are available. The PID lists are only a small subset of what will be available as soon as I get time to enter the rest of the PID definition data.

See the Readme.txt file in that folder for more info.

Regards
Paul

[Blacky]

Well, now it says it's saving the trace files but, there is nothing on the internal memory or the SD card. :( I will wait until tomorrow to mess with it again.

Anything you want me to try tomorrow?

Wait until I post up the updated firmware. It has a number of bug fixes that may solve the problems you are seeing.

If, with the new firmware, the problems still persist, please save a trace file after any problem occurs and send it to me paul@efilive.com. Include a brief description of what you were trying to do, what you expected to happen and what actually happened.

Regards
Paul

[XLR8NSS]

Ok Paul, when might we see the new firmware update? :D

[Blacky]

Ok Paul, when might we see the new firmware update? :D

Hopefully tonight (i.e. in about 6-8 hours).
Paul

[Cougar281]

Paul will the V2 be able to save codes from modules other than the ECM/TCM/PCM using the "Record All Diags"? Currently, it'll show them, but only records ECM/TCM/PCM DTCs.

[Blacky]

Paul will the V2 be able to save codes from modules other than the ECM/TCM/PCM using the "Record All Diags"? Currently, it'll show them, but only records ECM/TCM/PCM DTCs.

Ahh, yes it should - must have overlooked that.
Freeze frame data will only be collected for engine and trans.

Regards
Paul

[SV8346]

ok, something has gone really screwy with my BB log files. The whole log is just a jumbled mess.

[SV8346]

its all good now, for some reason when i log commanded AFR its when the log goes crazy.

[Blacky]

Hopefully tonight (i.e. in about 6-8 hours).
Paul

Sorry, it won't be ready tonight. Had a bit of drama here earlier with a flooded bathroom. Hopefully I'll get it done tomorrow.

Regards
Paul

[SV8346]

hi paul, what would cause the log to go to a jumbled mess if i logged commanded AFR.

[Blacky]

hi paul, what would cause the log to go to a jumbled mess if i logged commanded AFR.

I've got no idea. I haven't investigated that yet.
Paul