BB Logging beta update: May 06, 2008

Printable View

Show 40 post(s) from this thread on one page

May 5th, 2008
Blacky

BB Logging beta update: May 06, 2008

IMPORTANT
IF YOU HAVE NOT ALREADY DONE SO,
YOU MUST UPDATE FLASHSCAN'S BOOT BLOCK TO V2.05.08(0426)
BEFORE
YOU ATTEMPT TO UPGRADE THE FIRMWARE TO V2.05.16 OR LATER.

Under no circumstances should you attempt to use boot block V2.05.06 (released March 26, 2008).
See this link for more info on what is wrong with V2.05.06
http://forum.efilive.com/showthread.php?t=7804

Download here: http://download2.efilive.com/Softwar...ay_06_2008.zip (19Mb)
This download includes and supersedes all previous BBL beta downloads.

The Readme_First.pdf file included in the zip file has not been updated, except to reflect the new version numbers.

The FlashScan AutoCal V2.5 Release Notes _beta_.pdf file has some important "Known Issues" documented for EFILive_Explorer.exe. Please read them.

The FlashScan AutoCal V2.5 Quick Reference _beta_.pdf file has been updated to reflect the new "System Readiness Tests Status" option.

Make sure you update your FlashScan (and/or AutoCal) firmware and boot block using the latest *.ffw files from the \Program Files\EFILive\V8\EFILive_Hapi\ folder.

For those of you waiting for the AutoCal beta test firmware, I have been waiting for the boot block and firmware to be stable. I am confident the firmware is now stable and I will be releasing the AutoCal boot block and firmware in the next update.

Note: To all AuotCal beta testers, I have not shipped the updated AutoCal units yet. I expect to ship them this week, now that the boot block is stable.

Regards
Paul
May 6th, 2008
ScarabEpic22

Glad the VIN licenses on the V2 work properly now, but still in the Tune tools' FS V2 Licensing window the flash counters are still flipped...
May 6th, 2008
Blacky

Quote:

Originally Posted by ScarabEpic22

Glad the VIN licenses on the V2 work properly now, but still in the Tune tools' FS V2 Licensing window the flash counters are still flipped...

Ahhhh that is annoying, I originally noticed they were back to front, so I swapped them around. Then I got a report that said they were back to front, so I just assumed I had got it wrong and so I swapped them back again.
I will get it right next time...

Regards
Paul
May 6th, 2008
Ninety8C5

1 Attachment(s)

V2 got tthe right VIN but wrong OS (19980200). My car has OS 19980400, however I was able to log DMA PIDs. :banana:

I've attached a trace file in case you want to look at it. I realize that it is not a problem now as logging works, but I was wondering about down the line when reading and writing is implemented.
May 6th, 2008
Blacky

Quote:

Originally Posted by Ninety8C5

V2 got tthe right VIN but wrong OS (19980200). My car has OS 19980400, however I was able to log DMA PIDs. :banana:

I've attached a trace file in case you want to look at it. I realize that it is not a problem now as logging works, but I was wondering about down the line when reading and writing is implemented.

This explains why:
http://forum.efilive.com/showpost.ph...5&postcount=28

However, some DMA PIDs will be wrong because of the OS mismatch.

The following PIDs will not return correct results for you PCM:

Code:

GM.LTFT_DMA GM.EST_BASE_DMA GM.EST_ECT_DMA GM.EST_EGR_DMA GM.EST_IAT_DMA GM.EST_CAT_DMA GM.EST_EQR_DMA GM.EST_SMT_DMA GM.EST_IDLE_DMA GM.EST_TRQ_DMA GM.EST_KRB_DMA GM.EST_CRANK_DMA GM.EST_RUN_DMA GM.IAC_STD_DMA GM.IAC_STPN_DMA GM.IAC_STDAC_DMA GM.IAC_STPNAC_DMA GM.IAC_FRICTION_DMA GM.IAC_TC_DMA GM.IAC_TF_DMA GM.IAC_OT_DMA GM.IAC_PARK_DMA GM.IAC_WD_DMA GM.IAC_WPN_DMA GM.IAC_DFCO_DMA GM.IAC_FAN_DMA GM.IAC_CATL_DMA GM.IAC_AC_DMA GM.CYLAIR_DMA GM.DYNCYLAIR_DMA

The following PIDs will return correct results for your PCM:

Code:

GM.LTFT_RPM_DMA GM.LTFT_MAP_DMA GM.TRANS_DMA GM.VSSLIMIT_DMA GM.FAN1ON_DMA GM.FAN1OFF_DMA GM.FAN2ON_DMA GM.FAN2OFF_DMA GM.FANTYPE_DMA GM.4WD_DMA GM.IAC_LTD_DMA GM.IAC_LTPN_DMA

We are working on a solution...

Regards
Paul
May 6th, 2008
Ninety8C5

I will make sure I only log the ones that will log correct data. I assume that none DMA PIDs are okay.

Will the DMA PIDs that are incorrect for my car be okay for a friend's car that is OS 19980200 or is the problem with all 1998 C5's?
May 6th, 2008
ScarabEpic22

Quote:

Originally Posted by Blacky

Ahhhh that is annoying, I originally noticed they were back to front, so I swapped them around. Then I got a report that said they were back to front, so I just assumed I had got it wrong and so I swapped them back again.
I will get it right next time...

Regards
Paul

Whatever, I dont really mind as its not a HUGE thing. Just something Ive noticed and this is a beta testing period, right?:banana:
May 6th, 2008
Cougar281

Don't know if you meant it, but it looks like my BRFRP and BRFPR PSLs for the LB7 where left in. :)
May 6th, 2008
Kevin Doe

I missed the last two updates. Someone with a 99+ LS1 Manual using this update? Everything still working, DMA pids and all?
May 6th, 2008
Blacky

Quote:

Originally Posted by ScarabEpic22

Whatever, I dont really mind as its not a HUGE thing. Just something Ive noticed and this is a beta testing period, right?:banana:

Correct, it should be done right and beta testing is the right time to do it right.
Paul
May 6th, 2008
Blacky

Quote:

Originally Posted by Ninety8C5

I will make sure I only log the ones that will log correct data. I assume that none DMA PIDs are okay.

Yes.

Quote:

Originally Posted by Ninety8C5

Will the DMA PIDs that are incorrect for my car be okay for a friend's car that is OS 19980200 or is the problem with all 1998 C5's?

If, after you read the *.tun file form the PCM, the tuning tool shows 19980200, then the DMA PIDs will be ok.

If, after you read the *.tun file form the PCM, the tuning tool shows 19980400, then the DMA PIDs will NOT be ok.

In both cases, the Scan Tool will show the OS to be 19980200. The problem is the EFILive Scan Tool can't (yet!) identify the 19980400 operating system without reading out the PCM contents - so it incorrectly assumes it is a 19980200 OS and the DMA PIDs defined for a 19980200 OS won't match your 19980400 OS.

We are working on a fix...

Regards
Paul
May 6th, 2008
Blacky

Quote:

Originally Posted by Wolfie

I,m sure I missed it somewhere else, but...
Is there a pid for the plx serial when logging via computer?

ALL serial wideband controllers report their AFR and Lambda via the same PIDs:

Code:

EXT.WO2ST1 F408 SED-16-900 . External "External Wideband Sensor State" EXT.WO2ST2 F409 SED-16-900 . External "External Wideband Sensor State" EXT.WO2LAM1 F40A UNM-16-913 "lambda" External "External Wideband Lambda" EXT.WO2LAM2 F40B UNM-16-913 "lambda" External "External Wideband Lambda" EXT.WO2AFR1 F40C UNM-16-914 "AFR" External "External Wideband AFR" EXT.WO2AFR2 F40D UNM-16-914 "AFR" External "External Wideband AFR"
May 6th, 2008
Blacky

Quote:

Originally Posted by Cougar281

Don't know if you meant it, but it looks like my BRFRP and BRFPR PSLs for the LB7 where left in. :)

Oops, sorry, I will put it back to how it should be :crash:.
I must learn not to run testing in the production system...:music_whistling_1:

Regards
Paul
May 6th, 2008
Blacky

Quote:

Originally Posted by Kevin Doe

I missed the last two updates. Someone with a 99+ LS1 Manual using this update? Everything still working, DMA pids and all?

Should be fine on an LS1, the first line of testing has always been a trusty LS1. Although that will be changing as we are getting an E38, 6 speed, vehicle next week.

Regards
Paul
May 6th, 2008
ringram

Nice one Paul, same as me . LS3 or LS2?
The LS2 goes pretty well stock.
May 7th, 2008
Kevin Doe

Quote:

Originally Posted by Blacky

Should be fine on an LS1, the first line of testing has always been a trusty LS1. Although that will be changing as we are getting an E38, 6 speed, vehicle next week.

Regards
Paul

I just confirmed it for a 2004 GTO PCM. All looks well!

Edit:
I did find a small bug when trying to set an alarm for a gauge in the scan tool. I clicked on the "..." button to select a sound to play for the alarm high.

http://i93.photobucket.com/albums/l5...FILiveBug1.jpg

Here is what happens. The lower window is what pops up for me to select the .wav file I want to choose. It automatically comes up with *.wav as the file type. However there is nothing to choose. So I pulled up a windows explorer window (top window) and see that there are plenty of .wav files to choose from. To ensure they are a .wav file I pulled up the properties of one of the files. It is in face a .wav file.

http://i93.photobucket.com/albums/l5...FILiveBug2.jpg

I am unable to choose a .wav file to use for the alarm sound. BUT, if I type the path and file in myself it works. In the screen shot below I manually typed in the path and file. And it works.

http://i93.photobucket.com/albums/l5...FILiveBug3.jpg
May 7th, 2008
Blacky

In the open file dialog change the *.wav to *.* and it will show the files.
I must have missed that dialog box when converting the software over to be "vista compatible".
The dialog will also not automatically open in the "Sounds" folder, you'll need to navigate there manually, I'll fix that too.

Regards
Paul
May 7th, 2008
Kevin Doe

Quote:

Originally Posted by Blacky

In the open file dialog change the *.wav to *.* and it will show the files.
I must have missed that dialog box when converting the software over to be "vista compatible".
The dialog will also not automatically open in the "Sounds" folder, you'll need to navigate there manually, I'll fix that too.

Regards
Paul

Paul, I am unable to chnage the dropdown box from "*.wav" to "*.*" or "all files". The dropdown box only contains "Wave Files (*.wav)". I even tried manually adding the .wav extension to the file name. That didn't work either.
May 7th, 2008
lakingslayer

Paul, I've tried the last two updates and I cannot get my V2 to recognize my truck for BBlogging. When I hit "Select PIDs" I get a message saying "None Loaded". I've reformatted the SD card and also used the "Format" button on the "config" tab. After I load all the config and .pmm files I check the used space for the internal memory and there is only 4K used. The SD memory says there is 20K used. The Beta release from April 26th worked fine.

All other features seem to work such as diagnostic codes and getting the VIN numbers.

Any clues? I'm going to re-format and try to install the firmware update again to see if that fixes anything.
May 7th, 2008
lakingslayer

I guess I just needed to talk out loud about this. After the post I thought about it and realized I didn't re-format the internal memory. Then I re-installed the firmware update. It worked after that. One thing is I re-formatted both the SD card and internal memory but the config files were still there. I thought they should have gotten erased. Anyway thanks for listening.
May 7th, 2008
Blacky

Quote:

Originally Posted by Kevin Doe

Paul, I am unable to chnage the dropdown box from "*.wav" to "*.*" or "all files". The dropdown box only contains "Wave Files (*.wav)". I even tried manually adding the .wav extension to the file name. That didn't work either.

Where you type in the filename is the default text "*.wav", change that text to *.* and all files will show up.

Regards
Paul
May 7th, 2008
Blacky

Quote:

Originally Posted by lakingslayer

I guess I just needed to talk out loud about this. After the post I thought about it and realized I didn't re-format the internal memory. Then I re-installed the firmware update. It worked after that. One thing is I re-formatted both the SD card and internal memory but the config files were still there. I thought they should have gotten erased. Anyway thanks for listening.

There are two internal memory file systems: "Config" and "Data".

You can only format the "Data" filesys from FLashScan's menu.
You can only format the "Config" filesys from EFILive_Explorer's [Config] tab page.

On tab pages: Scan, Tune and Config, is a button called [Properties]. That shows you the space on each of the file systems.
Note: Scan and Tune refer to the same file system (Data) and so will always be the same.

We made the config file system non-formatable without a PC because there is no point formatting it unless you can replace the config files and that requires a PC. It just stops you accidentally erasing the config file system while out in the field. While still allowing you to format the data file system if required.

Regards
Paul
May 7th, 2008
joecar

Config space: formated from EE (under Config Files tab) as Paul said.

Data space:
- Internal: formated from V2 (first select internal option),
- External: formated from V2 (first select SD option).
May 7th, 2008
joecar

LS1B_A connected to V2...

On V2:
- System readiness tests show readiness states, looks to be correct.
- Mode 6 says "Mode $06 not retrieved" (or similar), I take it it's not there yet.

Key off, no laptop: V2 detects 1 PCM.
Key off, laptop: V2 detects 2 PCM's (but there's only 1 PCM).

BTW: in system readiness tests, what is CCM (is this EVAP)...?
May 7th, 2008
XLR8NSS

I think I might have the same problem as before with BBL cutting off early with my E38. Morning trip was about 40 minutes and only got 5 minutes of logged data. Afternoon trip was probably 60 minutes and only got about 20 minutes of data.

I will investigate a little further tomorrow morning and post up more details. I wasn't thinking this morning/afternoon and did not get a trace file.
May 7th, 2008
Blacky

Quote:

Originally Posted by joecar

LS1B_A connected to V2...
On V2:
- System readiness tests show readiness states, looks to be correct.
- Mode 6 says "Mode $06 not retrieved" (or similar), I take it it's not there yet.

Not implemented for VPW vehicles yet - only CAN so far.

Quote:

Originally Posted by joecar

Key off, no laptop: V2 detects 1 PCM.
Key off, laptop: V2 detects 2 PCM's (but there's only 1 PCM).

I have seen that and am trying to fix it...

Quote:

Originally Posted by joecar

BTW: in system readiness tests, what is CCM (is this EVAP)...?

MIS "Misfire Monitoring"
FUEL "Fuel System Monitoring"
CCM "Comprehensive Component Monitoring"
CAT "Catalyst"
HCAT "Heated Catalyst"
EVAP "Evaporative Purge System"
AIR "Secondary Air System"
ACRF "A/C System Refrigerant"
O2S "Oxygen Sensor"
HTR "Oxygen sensor Heater"
EGR "EGR System"

CCM: is a "catch all" for electronic systems not covered by the other 10 tests that can affect emissions. On most vehicles I've seen it is either not supported or always ready.

Regards
Paul
May 7th, 2008
nevinsb

Would it be possible to save active DTCs for a vehicle on the SD/internal memory?
May 7th, 2008
Blacky

Quote:

Originally Posted by nevinsb

Would it be possible to save active DTCs for a vehicle on the SD/internal memory?

Yes, try this:
F2 Scan Tool -> F2 Diagnostics -> F4 Record All Diags.
That will create a text file called DTCxxxxx that you can copy to your PC and open/view with Notepad.

Regards
Paul
May 7th, 2008
swingtan

Quote:

Originally Posted by XLR8NSS

I think I might have the same problem as before with BBL cutting off early with my E38. Morning trip was about 40 minutes and only got 5 minutes of logged data. Afternoon trip was probably 60 minutes and only got about 20 minutes of data.

I will investigate a little further tomorrow morning and post up more details. I wasn't thinking this morning/afternoon and did not get a trace file.

X2.

I have a few logs that seem to just end mid stream.

I've also had times when the V2 will log fine, then other times it appears to go into "pause" mode ( left hand green LED flashing slowly ) but you can't take it out of pause mode. Sometimes the displayed data also seems to freeze when this occurs, but not always. Pressing the <cancel> key will terminate the logging session and save the file. When I check the log files in ScanTool, the file is only 2KB in size and only the meta-data appears in the log.

Simon.
May 7th, 2008
Blacky

Quote:

Originally Posted by XLR8NSS

I think I might have the same problem as before with BBL cutting off early with my E38. Morning trip was about 40 minutes and only got 5 minutes of logged data. Afternoon trip was probably 60 minutes and only got about 20 minutes of data.

I will investigate a little further tomorrow morning and post up more details. I wasn't thinking this morning/afternoon and did not get a trace file.

Can you email me the log files at [email protected] and include a link to this thread, thanks.
Paul
May 7th, 2008
joecar

1 Attachment(s)

Quote:

Originally Posted by nevinsb

Would it be possible to save active DTCs for a vehicle on the SD/internal memory?

Quote:

Originally Posted by Blacky

Yes, try this:
F2 Scan Tool -> F2 Diagnostics -> F4 Record All Diags.
That will create a text file called DTCxxxxx that you can copy to your PC and open/view with Notepad.

Regards
Paul

Here's an example I pulled from my LS1B... it shows the states of the continuous/non-continous monitors (I xxx'd out my VIN).

Cheers
Joe
:cheers:

Edit: I had the wrong attachment, now corrected.
May 7th, 2008
joecar

Paul,

You may have to post what all the characters in "M-PHX-CS" mean in regards to the state of a DTC.

Thanks,
Joe
:cheers:
May 7th, 2008
swingtan

Quote:

Originally Posted by swingtan

X2.

I have a few logs that seem to just end mid stream.

I've also had times when the V2 will log fine, then other times it appears to go into "pause" mode ( left hand green LED flashing slowly ) but you can't take it out of pause mode. Sometimes the displayed data also seems to freeze when this occurs, but not always. Pressing the <cancel> key will terminate the logging session and save the file. When I check the log files in ScanTool, the file is only 2KB in size and only the meta-data appears in the log.

Simon.

I have another update for this. I stated logging this afternoon and very quickly the V2 dropped into "pause" mode. I tried pressing the pause button a few time and found that if I held it down, it would drop out of pause mode and start to log, but go straight back to pause mode as soon as I let go.

I then reset the V2 and started logging again but some time down the road it again went into pause mode. Hitting <cancel> saved the log file, but it is just the first 2K of the meta-data.

Simon.
May 8th, 2008
rcr1978

Pids when logging (LMM)

I know that the main focus is DVT & Standalone logging but I found some weird things some have gone on for a while the first one is GM.EGR this is the actual position of the egr. When logging with the egr enabled I beleived it worked a long time ago. Now if I use it with the EGR tuned out it shows 100% all the time if it was actualy at 100% the truck would smoke real bad but all is well with the truck. The other ones are SAE.MAP and GM.MAP2 these don't read the same wich one is the best to use for reading boost? Usualy wich ones are better for logging also SAE. or GM. ?

Thanks
May 8th, 2008
joecar

Quote:

Originally Posted by joecar

Here's an example I pulled from my LS1B... it shows the states of the continuous/non-continous monitors (I xxx'd out my VIN).

Cheers
Joe
:cheers:

Edit: I had the wrong attachment, now corrected.

Paul,

In the file attached to that post, the freeze frame data contains this entry: $119E=$8B
May 8th, 2008
Blacky

Quote:

Originally Posted by joecar

Paul,

In the file attached to that post, the freeze frame data contains this entry: $119E=$8B

The values that show up like that in the freeze frames are just data items in the freeze frame that we have not defined yet. We'll get there :)

Regards
Paul
May 8th, 2008
Blacky

Quote:

Originally Posted by joecar

Paul,

You may have to post what all the characters in "M-PHX-CS" mean in regards to the state of a DTC.

Thanks,
Joe
:cheers:

Code:

S: Supported DTC is supported on this vehicle. C: Current DTC is currently set. N: Not Passed The test for this DTC has never passed since it was last cleared. X: Failed The test for this DTC has failed at least once since it was last cleared. H: Freeze frame Freeze frame data exists for this DTC. P: Passed ign The test for this DTC has passed this ignition cycle. F: Failed ign The test for this DTC has failed this ignition cycle. M: MIL MIL is illuminated for this DTC.
May 8th, 2008
Blacky

Quote:

Originally Posted by rcr1978

I know that the main focus is DVT & Standalone logging but I found some weird things some have gone on for a while the first one is GM.EGR this is the actual position of the egr. When logging with the egr enabled I beleived it worked a long time ago. Now if I use it with the EGR tuned out it shows 100% all the time if it was actualy at 100% the truck would smoke real bad but all is well with the truck. The other ones are SAE.MAP and GM.MAP2 these don't read the same wich one is the best to use for reading boost? Usualy wich ones are better for logging also SAE. or GM. ?

Thanks

I'll check the GM.EGR PID. Which vehicle/controller are you logging?

I would always use the SAE PIDs where possible. They must be provided in a defined manner by the manufacturers by law. They will usually be the most reliable PIDs.

Regards
Paul
May 8th, 2008
XLR8NSS

Quote:

Originally Posted by Blacky

Can you email me the log files at [email protected] and include a link to this thread, thanks.
Paul

Trace and log file sent! :cheers:
May 8th, 2008
rcr1978

Quote:

Originally Posted by Blacky

I'll check the GM.EGR PID. Which vehicle/controller are you logging?

I would always use the SAE PIDs where possible. They must be provided in a defined manner by the manufacturers by law. They will usually be the most reliable PIDs.

Regards
Paul

LMM OS 12617103

The GM.MAP2 matches my boost table and the SAE.MAP is nowhere even close.

Thanks
Robert

Show 40 post(s) from this thread on one page

All times are GMT -12. The time now is 06:07 AM.