EFILive Version 8 (Black Box Logging) is now available

Quote:

---

Originally Posted by Blacky

I see that here sometimes as well. Still trying to figure out why.

---

Good, at least it's not just the V6 then.

Quote:

---

Originally Posted by Blacky

That sounds like the time limit for displaying alerts/errors is set too high. Check in "Edit Settings" that the times for Alerts and Errors are set to reasonable values.

---

Ahh.... yes. Slight case of PEBCAK at this end. I didn't see the new setting for the message timeouts. All fixed now.

Thanks,

Simon

Quote:

---

Originally Posted by ringram

When saving settings F6 stuff to the V2 unit I get a "Error: $010A Recieved data message contained unknown command action"
This was after setting serial IO

---

i fixed this upgrading the firmware.

Firstly :thankyou2: for releasing the BBL software with a more user friendly interface. Takes a bit of getting used to compared to the relative simplicity of V1 BBL but it's an awesome achievement.:thumb_yello:

The only things not working properly for me logging E38 and T43 are:

1. My serial wideband is in my PID list and appears on the V2 but is not recorded in the BBL.
2. I can't find a PID for BEN1_E38.
3. PID GEAR thinks I'm in 1st when I'm actually reversing and P indicated either 1st or 3rd.
4. PID PRNDL only displays Drive 6 for all forward gears.

Is there something else I need to do to get my serial wideband to appear in the BBL?

Cheers.

Quote:

---

Originally Posted by Blacky

The file system can easily get corrupted, same as if you pulled power from a PC while it was writing to disk.
That is a real show stopper if you don't have immediate access to a PC to reformat the Config file system.

What I have been working on is a way to maintain a backup of the Config file system on an SD card. That way if the corruption happens, you can plug in the "Recovery SD Card" and get FlashScan to reformat the Config file system and restore the Options.txt, Settings.dat and *.pmm files.

Regards
Paul

---

Yeah it might have happened without too much user error either. Is it time for a basic journaling file system instead?

Quote:

---

Originally Posted by ringram

Yeah it might have happened without too much user error either. Is it time for a basic journaling file system instead?

---

Something like this... http://www.hcc-embedded.com/en/produ...ystems/safefat

Alternatively I've been investigating into not having a Config FAT file system but just storing the Config data in an internal fail-safe format. There's no reason to store the Config data in a FAT file system as it is not removable and no other device/computer will ever need to access it.

Regards
Paul

Could you change the serial BEN PIDs format to .2 in the sae.generic.txt?
I like to see .2 precision for this PID on the data tab
and this is the only way I have found to adjust it.

Quote:

---

Originally Posted by mr.prick

Could you change the serial BEN PIDs format to .2 in the sae.generic.txt?
I like to see .2 precision for this PID on the data tab
and this is the only way I have found to adjust it.

---

Sure.
Paul

:phatyo:
Thank you

lol... is 2 enough...? I like 3 better...:D...same with the AFR and EQ pids.

Would it be possible to have WO2EQR1 and WO2EQR2 pids...?

(where WO2EQR = 1/WO2LAM).

Quote:

---

Originally Posted by Blacky

Something like this... http://www.hcc-embedded.com/en/produ...ystems/safefat

Alternatively I've been investigating into not having a Config FAT file system but just storing the Config data in an internal fail-safe format. There's no reason to store the Config data in a FAT file system as it is not removable and no other device/computer will ever need to access it.

Regards
Paul

---

Yeah, either or.
You could almost steal all the internal memory for system use and force people to use SD Cards, they are almost free now anyway. (Then save DTC code info in there too ;)

Quote:

---

Originally Posted by ringram

Yeah, either or.
You could almost steal all the internal memory for system use and force people to use SD Cards, they are almost free now anyway. (Then save DTC code info in there too ;)

---

Hmm, except AutoCal has no external memory. So I need to support all the functions on the internal memory anyway.
Paul

:help2:
I'm being dense....how do I get my log file off the V2 with the new software?

I just know this is going to be obvious and I'll feel silly.....but I just can't see it?

Thanks

Jim

I have not used BBL for awhile but IIRC,
you can drag and drop it from EE.

Quote:

---

Originally Posted by mr.prick

I have not used BBL for awhile but IIRC,
you can drag and drop it from EE.

---

I was OK doing that with the old EE, but with the new Carlos Fandango one.....I can't see how to (I know this is me just being thick!!)

It should be the same.
FWIW the old EE short cut opens EFILive scan and tune now.
You will need to navigate to C:\Program Files\EFILive\V8 and
create a new shortcut for EE, it has a new look.

Quote:

---

Originally Posted by mr.prick

It should be the same.
FWIW the old EE short cut opens EFILive scan and tune now.
You will need to navigate to C:\Program Files\EFILive\V8 and
create a new shortcut for EE, it has a new look.

---

OK, had a look in there and the cupboard was bare......zapped everything and started again. Bingo EE staring me in the face, I must have biffed something up during the install (in my defence I was rushed/didn't bother reading anything :hihi:)

Thanks

Jim

Quote:

---

Originally Posted by Biodiesel66

Paul,

Couldn't get the TEMP1 or TEMP2 to work with build 51 or 52. When using EFI S&T, adding TEMP2 External Temperature to the Selected PID list, changing the properties to custom. Default ID Properties: Node: is empty!
Custom ID Properties: Quick set is empty, should have °F or °K ? Had to change the Factor, Offset, and Units. Click OK. Saved the PID and programed to F/S with S&T. The selected PID will not view or record. If I go and Edit the Options txt file and change ( ) to (-,) for the controller and save the file. View it in EFI S&T for that selected PID and check the properties the Node: has - and is not empty. Program the changed Options txt to F/S. It will view in °F and play back in °F. WHY does it work this way and not the other way?

The 3 PIDs should have logged in IMPERIAL from the Options txt setting.
The PIDs that are listed are from F8 in the log and from the customized PID list that can be viewed in Imperial from F/S or A/C. The log has them as metric. F/S can't change 2 of the PIDs to IMPERIAL because the UNITS are set by default to metric. Its just like FRP_C. F/S has the UNITS set to PSI, Default Metric or Imperial. The recorded log will only play back in PSI never metric. Until it's changed in F/S.

---

Did you get anything on this? I'm having the same problem and wondered if there was a work around so I could log my EGT, please? :welcome:

I'm looking at this now...
Follow in this thread:
http://forum.efilive.com/showthread....5334#post95334
Paul

Quote:

---

Originally Posted by Blacky

I'm looking at this now...
Follow in this thread:
http://forum.efilive.com/showthread....5334#post95334
Paul

---

Thank you - This new release is INCREDIBLE!!!:fluffy: I LOVE the new BBL! :cucumber:

I think we may have missed signals...that thread looks like the hardware is missing. My thread was about the software itself... in the parameters of options.txt there is nothing. for temp2 and temp1
Sorry if i mis-lead you!

Quote:

---

Originally Posted by Jasondt2001

I think we may have missed signals...that thread looks like the hardware is missing. My thread was about the software itself... in the parameters of options.txt there is nothing. for temp2 and temp1
Sorry if i mis-lead you!

---

I understand. However, I see the TEMP1 and TEMP2 PIDs in the Options.txt after using the BBL software to select them.
Which controller are you trying to select them for?

Anyway, back to the reason I linked to this thread...
http://forum.efilive.com/showthread....5334#post95334

While trying to reproduce the problems with AD2, I saw an anomaly with the TempX PIDs. Temp1 appears to remain static at 3degC while TEMP2 appears to contain one of the AD values - that's what I am working on at the moment.

Regards
Paul

LBZ controller - in my options ...well here it is...

Quote:

---

Originally Posted by options.txt W/ temp1 selected

; (LBZ|Auto)
*PSL_20
;
;Node PID Custom (Cap:Units:Prec:Fact:Offs:Inv) Alarm (min:max:style:time*10ms:hold*sec)
;---- ---------------- ----------------------------------------- -----------------------------------------
ECM, LOAD_PCT
ECM, EGR_PCT
ECM, EGRCMD
ECM, FUELRCALC
ECM, EQ_RAT
ECM, VPWR
ECM, MAIN1Q_M
ECM, FRPDES, :psi:0:1450.376953:0.000000:N
ECM, FRP_C, :psi:0:1450.376953:0.000000:N
ECM, MNINJTIM
ECM, MAIN1T_M
TCM, TP_A
TCM, RPM
ECM, TCVDES
ECM, TCVPOS
ECM, BOOST2_M, :psi:1:0.145038:0.000000:N
ECM, ECT, :°F:0:1.800000:32.000000:N
ECM, ENGTRQREF_M, :ftlb:1:0.737600:0.000000:N
ECM, IAT, :°F:0:1.800000:32.000000:N
TCM, TIS
TCM, TOS
TCM, TCCDC
TCM, TCCSLIP
TCM, GEAR
TCM, SELGEAR
TCM, CMDGEAR
TCM, TFT, :°F:0:1.800000:32.000000:N
TCM, REQTRQR, :ftlb:1:0.737600:0.000000:N
ECM, ENGOILP, :psi:1:0.145038:0.000000:N
ECM, VSS, :mph:0:0.621371:0.000000:N
TEMP1,
ECM, MAP2, :psi:1:0.145038:0.000000:N
ECM, MAP, :psi:1:0.145038:0.000000:N
ECM, WIFV
TCM, TSTATE07

---

It won't work that way and i don't know how to manually do it... it just puts in the temp1 in options.txt but I don't see it on the flashscan and it logs nothing.
I see the other PIDS have 'variables" or other options to them... This one does not.

THe external PIDs should have a dash for the controller type.
i.e.
-,TEMP1
instead of just
TEMP1

When you save the PID selections from the BB logging setup window it should create the Options.txt file correctly with the dashes.

Make sure you are using the latest V8.1 release because an older version of the software had a problem that caused it to leave off the dash.

The latest version V8.1.2 is available here:
http://www.efilive.com/index.php?opt...=48&Itemid=133

Regards
Paul

Quote:

---

Originally Posted by Jasondt2001

Did you get anything on this? I'm having the same problem and wondered if there was a work around so I could log my EGT, please? :welcome:

---

If you go into the Options.txt file and add the - that is missing that's the work around.

- , TEMP2, :°F:0:1.800000:32.000000:N

Quote:

---

Originally Posted by Blacky

THe external PIDs should have a dash for the controller type.
i.e.
-,TEMP1
instead of just
TEMP1

When you save the PID selections from the BB logging setup window it should create the Options.txt file correctly with the dashes.

Make sure you are using the latest V8.1 release because an older version of the software had a problem that caused it to leave off the dash.

The latest version V8.1.2 is available here:
http://www.efilive.com/index.php?opt...=48&Itemid=133

Regards
Paul

---

I went ahead and deleted both of the temp PID's and then saved. I then reselected them and saved it again - Here's what I came up with:

Quote:

---

Originally Posted by options.txt

; __________________________________________________ _______________________
; (LBZ|Auto)
*PSL_20
;
;Node PID Custom (Cap:Units:Prec:Fact:Offs:Inv) Alarm (min:max:style:time*10ms:hold*sec)
;---- ---------------- ----------------------------------------- -----------------------------------------
ECM, LOAD_PCT
ECM, EGR_PCT
ECM, EGRCMD
ECM, FUELRCALC
ECM, EQ_RAT
ECM, VPWR
ECM, MAIN1Q_M
ECM, FRPDES, :psi:0:1450.376953:0.000000:N
ECM, FRP_C, :psi:0:1450.376953:0.000000:N
ECM, MNINJTIM
ECM, MAIN1T_M
TCM, TP_A
TCM, RPM
ECM, TCVDES
ECM, TCVPOS
ECM, BOOST2_M, :psi:1:0.145038:0.000000:N
ECM, ECT, :°F:0:1.800000:32.000000:N
ECM, ENGTRQREF_M, :ftlb:1:0.737600:0.000000:N
ECM, IAT, :°F:0:1.800000:32.000000:N
TCM, TIS
TCM, TOS
TCM, TCCDC
TCM, TCCSLIP
TCM, GEAR
TCM, SELGEAR
TCM, CMDGEAR
TCM, TFT, :°F:0:1.800000:32.000000:N
TCM, REQTRQR, :ftlb:1:0.737600:0.000000:N
ECM, ENGOILP, :psi:1:0.145038:0.000000:N
ECM, VSS, :mph:0:0.621371:0.000000:N
ECM, MAP2, :psi:1:0.145038:0.000000:N
ECM, MAP, :psi:1:0.145038:0.000000:N
ECM, WIFV
TCM, TSTATE07
, TEMP2
, TEMP1

---

Quote:

---

Originally Posted by Biodiesel66

If you go into the Options.txt file and add the - that is missing that's the work around.

- , TEMP2, :°F:0:1.800000:32.000000:N

---

Thank you both!! I'll do that!:fluffy::fluffy:

Quote:

---

Originally Posted by Jasondt2001

I went ahead and deleted both of the temp PID's and then saved. I then reselected them and saved it again - Here's what I came up with:
, TEMP2
, TEMP1

---

Are you sure you're not using an older version of the software?
Check the version you are using on the very first screen when EFILive Scan and Tune is first started. It should show V8.1.2 Build 55 or higher.

Regards
Paul

Yeah Paul, I'm using V8.1.2 build 55 actually.

Once I put in the slash like above it works, but it thinks the temp probe 1 shows on both temp 1 and 2 probe. So another words it says temp2 is listed as temp1 if that makes sense. :)

Quote:

---

Originally Posted by Blacky

THe external PIDs should have a dash for the controller type.
i.e.
-,TEMP1
instead of just
TEMP1

When you save the PID selections from the BB logging setup window it should create the Options.txt file correctly with the dashes.

Make sure you are using the latest V8.1 release because an older version of the software had a problem that caused it to leave off the dash.

The latest version V8.1.2 is available here:
http://www.efilive.com/index.php?opt...=48&Itemid=133

Regards
Paul

---

Paul,

I can't verify if the LB7 external PID works.
I noticed that when saving the file in S/T. PCM is added for the node not the - and a description for the PID is added on the LB7. The LMM and LBZ is missing that information when setting up the Custom settings to use the two Temp PIDs.
The Options txt file has the - added for the LB7 and LLY when saving S/T. Could the problem be that the set-up information for the LMM and LBZ in custom properties is missing. If that is added I think it would work.

Hi guys, EFILive BBL etc: fabulous capability taking shape there.

PID editor is right out there! It was all kinda hard before this great tool!

A few issues come to light today as I wade through the learning curve of using build 55 capabilties etc.

These may have been reported already and already be on the to do list, so I will keep it short:

A/. For BBL display or log pids, V2 Selects both WB02 sensors on BBL. i.e. in options select one sensor, on scan/log two are presented. Seems that they always use 3 lines each too. Could do with just Lambda.

B/. Some items that are selected, are in log, do not appear on V2 BBL screen.

C/. Some items that are selected, are not in log, do not appear on V2 BBL screen - examples:

TCM VSS PID when selected has gone missing from V2 and log....it worked before.

PID's SCALCORVE_M & it uncorrected partner while listed in the FS V2 PID list, do not appear on the V2 or log.

Probably a few others to come.... :0

D/. Selecting Lambda in Flashscan and Autocal Device Settings "F7" sees EQR on the V2. (can be changed in V2 options.)

E/. De-selecting "Auto Select all digital PID's", turns all digital off. (i.e.needs 0,1,2 option ?)

F/. Selecting 1 Wideband sets in the editor or in the V2 selects both WB PIDs. Techedge WB. (see also A....I may be stuttering....:) )

G/. In FS/AC PID selections, ECM PID descriptions come and go, and descriptions get out of order.

H/. Sometimes V2 will notify writing log file, but nothing ends up on the SD card.

:)

Back to the grind.....

Cheers, Ian :cheers:

PS - For those of us with 64k row limits in XL, it would be good when exporting large logs if they produce a seperate file (auto) for every 64k rows or so. Not the end of the world of course.

Hi Ian,

Thanks for the detailed write up. It is taking me a while to go through and investigate the points you raised. I'll post my results/updates in this thread. Feel free to post a reminder if I have not posted by end of next week.

Regards
Paul

Quote:

---

Originally Posted by Blacky

Hi Ian,

Thanks for the detailed write up. It is taking me a while to go through and investigate the points you raised. I'll post my results/updates in this thread. Feel free to post a reminder if I have not posted by end of next week.

Regards
Paul

---

No worries Paul. Please let me know if you know need more details.

Also came across another one today:

I have EQ_RAT and AFRATIO_M as selected PID's in BBL. They both appear on the list in the LCD on the V2, but EQ_RAT does not make it into the log.

Cheers, Ian

And another...though am sure this is not a bug, but by design intent, and that is:

When VSS for example is selected from ECM and also from TCM, only one will "stick" in the Scan and Tune editor.

Similar if the options.txt is edited to add in what the editor wont, V2 BBL uses the first VSS PID and ignores the second.

Previously both could be used.

I can see the editor and the V2 are doing the right thing as two may be selected by accident, and they uses channels, but there are times when both are relevant.

Maybe an option ?

Thanksyou!

Quote:

---

Originally Posted by gmh308

And another...though am sure this is not a bug, but by design intent, and that is:

When VSS for example is selected from ECM and also from TCM, only one will "stick" in the Scan and Tune editor.

Similar if the options.txt is edited to add in what the editor wont, V2 BBL uses the first VSS PID and ignores the second.

Previously both could be used.

I can see the editor and the V2 are doing the right thing as two may be selected by accident, and they uses channels, but there are times when both are relevant.

Maybe an option ?

Thanksyou!

---

By design, PIDs with the same name form different controllers can be selected. however, the BBL firmware in FlashScan V2 is currently set up to emulate the *.efi log file format for the V7 software. That *.efi log file format cannot handle PIDs with the same name from different controllers so only the first one is used, the second one is ignored.

Once the V8 scan tool softwar eis ready, the FlashScan firmware will be switched over to the V8 style log files which will allow multiple PIDs with the same name.

I had overlooked the fact that you can still select 2 PIDs with the same name in the BBL setup software. Even though they can't be logged - yet.

Regards
Paul

Quote:

---

Originally Posted by Blacky

By design, PIDs with the same name form different controllers can be selected. however, the BBL firmware in FlashScan V2 is currently set up to emulate the *.efi log file format for the V7 software. That *.efi log file format cannot handle PIDs with the same name from different controllers so only the first one is used, the second one is ignored.

Once the V8 scan tool softwar eis ready, the FlashScan firmware will be switched over to the V8 style log files which will allow multiple PIDs with the same name.

I had overlooked the fact that you can still select 2 PIDs with the same name in the BBL setup software. Even though they can't be logged - yet.

Regards
Paul

---

Thanks Paul.

Quick question re: the latest firmware. has any one else noticed that the "auto pause" function no longer works? Previously, if you turned off the ignition, the V2 would sense the engine shutdown and pause the log. Now it seems to continue logging.

Simon.

Quote:

---

Originally Posted by swingtan

Quick question re: the latest firmware. has any one else noticed that the "auto pause" function no longer works? Previously, if you turned off the ignition, the V2 would sense the engine shutdown and pause the log. Now it seems to continue logging.

Simon.

---

I checked this a couple days ago and thought it did pause on engine off. Will re-check now that you raise this.

Cheers, Ian

It will only pause if the ECM stops sending data after ignition off.

I've seen vehicles stop sending data 5-10 seconds after ignition off (mostly VPW vehicles).
I've seen vehicles continue to send data after ignition off until I got bored waiting for it to stop (mostly CAN vehicles).

The only way to be sure is to press the Ok button of FlashScan to manually pause recording.

I guess something that would be nice (I've thought about doing this for a while) is to have two triggers that control pausing.

1. If VSS is zero for at least "n" seconds, then stop recording until VSS is greater than zero again.
2. If RPM is zero for at least "n" seconds, then stop recording until RPM is greater than zero again.

I think that would help take a lot of dead data out of road logs. I would also make the scanner insert flags into the log file when the data was automatically paused and re-started to avoid surprises when analyzing the data later.

Regards
Paul

Hmmm.... this is what happened to me, see post #18: showthread.php?p=96099