BB Logging beta update: March 20,2008

Ok, to expand on my previous post regarding LLY issues, LBZ doesn't either. If I try to display data (After selecting a vehicle), I got:

Unsupported PID
_____________
Node: ECM
PID: FRPDES
is not supported,
please de-select it.

so I removed it from the ini. Now I get:

Unsupported PID
_____________
Node: ECM
PID:
is not supported,
please de-select it.


Edit: Also, it seems like copying files to the FS is MUCH slower than before.

Quote:

---

Originally Posted by Highlander

All you need to do is open up efilive explorer and drag all the config files to the config portion... Later you connect to the vehicle, select the vehicle in V2 and then record. You cannot choose as of now like you could with v1.

---

Any feedback Kevin......

As Highlander pointed out you cant select pids freely.

Did you put in the config files or did you go through the F2 instead of F1.

cheers

Quote:

---

Originally Posted by SV8346

have you upgraded to the latest bootblock and are you now using EFILive explorer.

---

i am using the efilive explorer, i think i tried everything, i ticked the bootblock check box (in efilive explorer) then hit program, error message came up $0023.

the boot block version (read directly from the v2) 2.05.04 oct 16 2007 firmware is 2.05.15 mar18 2008.

the trouble is that i cant update the boot block, when i try to program v2470.ffw error message comes up "no reply from flashscan", i must have my wires crossed some where :Eyecrazy: .
any help is much apreciated.

Girch.

Did you do the final firmware update 70 (the last of the old ways)

I hate to ask, but where is the E67 stuff?
It's not listed under "Select Vehicle" so I modified my Options.ini
Then I wanted to add some pids, but the auto generated E67_PIDs.txt contains only MONDTC and the FlashScan V2 hardware inputs/outputs.

Can I just hijack the E38.pmm and pretend/assume all is kosher? I'd like to, but we're having Ham for Easter tomorrow... Help..


also in the E38_PIDs.txt for the E38.pmm is found this:

Code:

---

INPHAB2      [1] Intake Cam Phase Actual Angle Bank 2 (°)
EXPHDB1      [1] Exhaust Cam Phase Desired Angle Bank 1 (°)
INPHDB1      [1] Intake Cam Phase Desired Angle Bank 1 (°)
EXPHDB2      [1] Exhaust Cam Phase Desired Angle Bank 2 (°)
INPHDB2      [1] Intake Cam Phase Desired Angle Bank 2 (°)
EXPHEB1      [1] Exhaust Cam Phase Error Angle Bank 1 (°)
INPHEB1      [1] Intake Cam Phase Error Angle Bank 1 (°)
EXPHEB2      [1] Exhaust Cam Phase Error Angle Bank 2 (°)
INPHEB2      [1] Intake Cam Phase Error Angle Bank 2 (°)

---

What/which one (where) is supposed to be:
Intake Cam Phase Actual Angle Bank 1 (°)
Exhaust Cam Phase Actual Angle Bank 1 (°)

you wont be able to use the ....70.ffw firmware if you have already installed the bootblock.

You are meant to update it before installing the boot block.

Quote:

---

Originally Posted by Cougar281

I installed the new firmware (After formatting the config FS), copied the new PMM files to the FS, and now I can select the vehicle, but if I try to display data, it does nothing; If I try to log, the screen will flash, then go back to the "Record", "Display", "W02". Any suggestions? Do we still add PIDs by editing the options.ini?

---

I have the same problem on my lb7 i even tried removing all pid's
except -, TEMP1
And still no luck.:nixweiss:
If you a trace let me know.


jim t,

Quote:

---

Originally Posted by Cougar281

I installed the new firmware (After formatting the config FS), copied the new PMM files to the FS, and now I can select the vehicle, but if I try to display data, it does nothing; If I try to log, the screen will flash, then go back to the "Record", "Display", "W02". Any suggestions? Do we still add PIDs by editing the options.ini?

---

Yes, you can edit the Options.ini file. The Pid description files have been updated with the full ist of supported PIDs per controller.

After the logging fails, Select the Scan Tool->Scan Options->Sace Trace File. Then copy the saved trace file and send it to me at [email protected].

Include a link to this thread so I can correlate the trace file with this thread. Also please send the Options.ini file and the model-year of the vehicle being logged.

Regards
Paul

Quote:

---

Originally Posted by JezzaB

Anyone got the Serial O2 logging in pass thru???

---

Anyone???

Quote:

---

Originally Posted by JezzaB

Anyone???

---

It was working when I tested it, I'll test it again in case it got broken before/during the release.

Regards
Paul