BB Logging beta update: May 19, 2008

Printable View

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

May 20th, 2008
Blacky

BB Logging beta update: May 19, 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_19_2008.zip (20Mb)
This download includes and supersedes all previous BBL beta downloads.

ALL *.pmm files have been updated. you MUST delete ALL *.pmm files from FlashScan (before upgrading the firmware) and from the folder: \Program Files\EFILive\V8\config (before unzipping the downloaded zip file). Failure to do so will cause unpredictable results when you restart FlashScan after updating the firmware to 2.05.17(0519).

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

The FlashScan AutoCal V2.5 Release Notes _beta_.pdf file has some important "Known Issues" asnd updates. Please read them.

The FlashScan AutoCal V2.5 Quick Reference _beta_.pdf file has not been updated.

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

Regards
Paul
May 20th, 2008
Lennart

Not sure if this has been posted before, but even though I flashed the latest bootloader 2.05.08(0426) the Explorer and V2 show a date of Apr. 25, 2008.
May 20th, 2008
Blacky

You also need to update FlashScan with the latest firmware file: FSProgV2.05.17(0519).efw (from the Firmware folder).

Regards
Paul
May 20th, 2008
joecar

VPW mode $06 still says "Mode $06 Data Not Retrieved".
May 20th, 2008
Blacky

Quote:

Originally Posted by joecar

VPW mode $06 still says "Mode $06 Data Not Retrieved".

Still not implemented. :(
May 20th, 2008
swingtan

1 Attachment(s)

Excellent work! I'm now trying to get my head around the "Dynamic" section in the E38 Fuel group. It's early days yet but the excitement is growing.

It did prompt me to remember something that I worked out way back in January and may have forgotten to pass on.

In the PE tables, B0156 provides a TPS% level to enable PE. I found that measured TPS% was vastly different to the PE% displayed in the table. I had all sorts of troubles trying to work it out so I started remapping the measured TPS% vs TuneTool TPS%. The results showed that there was a logarithmic offset between the 2 values, as shown in the attached image.

While there are differing thoughts on weather PE should be controlled by TPS%, MAP or both, there is a question as to what other TPS% settings may be effected by this offset?

Simon.
May 20th, 2008
joecar

Quote:

Originally Posted by Blacky

Still not implemented. :(

Paul,

That's ok, take your time... I was going by the quick reference guide...

I'm having some cat codes so I am playing around with mode 6.

Cheers
Joe
:cheers:
May 20th, 2008
swingtan

1 Attachment(s)
I did a couple of logs this afternoon. Replaying them in ScanTool has dropped a couple of the PIDs off. They exist in the log file but do not display. I copied the previous options.ini file back into the config filesystem as I didn't see any info in the readme to say there were changes and it was fine before.

The following PIDs no longer show up in the ScanTool...
- ECM, INVLVTMP_M
- ECM, OCTSCL_M
- ECM, AFRATIO_M
Sample log file is attached.
May 20th, 2008
hymey

Has anyone tried pass thru logging yet?
May 20th, 2008
Blacky
Quote:
Originally Posted by swingtan

I did a couple of logs this afternoon. Replaying them in ScanTool has dropped a couple of the PIDs off. They exist in the log file but do not display. I copied the previous options.ini file back into the config filesystem as I didn't see any info in the readme to say there were changes and it was fine before.

The following PIDs no longer show up in the ScanTool...

ECM, INVLVTMP_M
ECM, OCTSCL_M
ECM, AFRATIO_M

Sample log file is attached.
Is it possible you've exceeded the channel count?
24 for VPW, 42 for CAN?

Regards
Paul
May 20th, 2008
Blacky

Quote:

Originally Posted by hymey

Has anyone tried pass thru logging yet?

Is there a problem, or are you just curious?
If you've found a problem or something that looks like a problem please let me know.
Regards
Paul
May 20th, 2008
02Z06

Just got done trying VPW Inovate LM1 logging. Using Firmware 2.05.17 (0519) and the newest bootblock. I double checked FS2 for settings W02 com in + Out and inovate checked as WB and still shows (no controller found) I have the inovate and FS cable connected with null-modem M/M adapter? BTW I tried VPW with my truck and CAN with my Z06.
May 20th, 2008
swingtan

Quote:

Originally Posted by Blacky

Is it possible you've exceeded the channel count?
24 for VPW, 42 for CAN?

Regards
Paul

I don't think so. I haven't changed the channel count from the previous version and it was fine there. I just did a recount and I have 26 channels, but eh E38 is a CAN BUS isn't it?
May 20th, 2008
hymey

Quote:

Originally Posted by Blacky

Is there a problem, or are you just curious?
If you've found a problem or something that looks like a problem please let me know.
Regards
Paul

I have problems with this current bootblock with passthrough logging, I have tried all the firmware bar this version. I was just wondering as I have a drag meet on Friday and if there are any minor issues with logging WB02 I will hang out till after the meet.

I sent to an error report last week.

Cheers

Joel
May 20th, 2008
hymey

Quote:

Originally Posted by swingtan

but eh E38 is a CAN BUS isn't it?

Surely is:hihi:
May 21st, 2008
Lennart

Quote:

Originally Posted by Blacky

You also need to update FlashScan with the latest firmware file: FSProgV2.05.17(0519).efw (from the Firmware folder).

Regards
Paul

Did that.
May 21st, 2008
joecar

Quote:

Originally Posted by Lennart

Not sure if this has been posted before, but even though I flashed the latest bootloader 2.05.08(0426) the Explorer and V2 show a date of Apr. 25, 2008.

I see the same thing... I think that's ok.
May 21st, 2008
Blacky

Quote:

Originally Posted by Lennart

Not sure if this has been posted before, but even though I flashed the latest bootloader 2.05.08(0426) the Explorer and V2 show a date of Apr. 25, 2008.

Oh, you mean the date of the boot loader still shows as Apr 25. I thought you meant the date of the firmware.

Hmm, looks like I've got a mismatch between the filename (0426) and the date 25 Apr, 2008. What you are seeing is ok, I'll fix the date in the file name next release.

Regards
Paul
May 21st, 2008
swingtan

E38 Missing PID Issue

OK, I've found the issue.

It seems the PID names have changed in the latest firmware but don't get translated back to the correct PID in ScanTool. Here's a quick breakdown of the 3 PIDs I noticed.

Code:

PID Names for FW Versions FW-(0512) FW-(0519) E38.INVLVTMP_M GM.INVLVTMP_M E38.APCYL_M GM.APCYL_M E38.AFRATIO_M GM.AFRATIO_M

Using the previous trick of editing the log file and changing the "GM" to "E38" returns the data in ScanTool.

regards,

Simon
May 21st, 2008
swingtan

1 Attachment(s)

Log Tuncation After 50,000 Frames

Hi Guys,

I've performed 2 logs today that are over 50,000 frames long. Both load in ScanTool after fixing the PIDs and both are truncated at 50,000 frames. The scroll bar allows you to scroll past the end of the data in ScanTool, but the lines just stop at the 50,000 frame mark. The Metadata indicates that there are a lot more than 50,000 frames....

FRAMECOUNT=00092371
FRAMECOUNT=00057076

I've attached a screen shot to show the screen.

By the way, is there any chance we can get the "Auto Replot" limit raised? It seems to have an internal limit of 30,000.

Simon.
May 21st, 2008
Blacky

You can raise the 50,000 frame limit in the Properties window on the Logging tab page.
I'll change the auto re-plot to be x1000 (the same as the frame limit in the Logging tab page). i.e. that will turn the 30,000 limit into 30,000,000.

Regards
Paul

Quote:

Originally Posted by swingtan

Hi Guys,

I've performed 2 logs today that are over 50,000 frames long. Both load in ScanTool after fixing the PIDs and both are truncated at 50,000 frames. The scroll bar allows you to scroll past the end of the data in ScanTool, but the lines just stop at the 50,000 frame mark. The Metadata indicates that there are a lot more than 50,000 frames....

FRAMECOUNT=00092371
FRAMECOUNT=00057076

I've attached a screen shot to show the screen.

By the way, is there any chance we can get the "Auto Replot" limit raised? It seems to have an internal limit of 30,000.

Simon.
May 21st, 2008
swingtan

Excellent! Sorry I missed that.

I take it that the reason was to prevent overly long "re-plot" times for large logs. In this case, it would be good to have a process where the re-plot is done in the background for the data outside the current window. Then as you scroll across, the additional data is plotted "on the fly".

I'll settle for a detailed explanation on the "dynamic fueling" options though.... :cheers:

Simon.
May 21st, 2008
Blacky

Quote:

Originally Posted by swingtan

Excellent! Sorry I missed that.

I take it that the reason was to prevent overly long "re-plot" times for large logs. In this case, it would be good to have a process where the re-plot is done in the background for the data outside the current window. Then as you scroll across, the additional data is plotted "on the fly".

I'll settle for a detailed explanation on the "dynamic fueling" options though.... :cheers:

Simon.

Given the speed of today's PCs the replot times should only be a second or two at most for 100,000 frames. Unfortunately when the scan tool software was designed one of the goals was to keep the logged data on disk at all times - not in memory. That is what slows it down and why the auto-replot option (kludge) was added.

Version 8 has all new strip charts (with data purely in memory) and I have benchmarked them plotting 50,000 frames in less than a second on a 1.8GHz Pentium. So it should not be be an issue in version 8.

Can't help on the dynamic fueling right now :(

Regards
Paul
May 21st, 2008
swingtan

Version 8 is sounding great..... ;)
May 21st, 2008
Blacky

Quote:

Originally Posted by swingtan

Version 8 is sounding great..... ;)

Unfortunately, sounding great and actually delivering it are two very different things :( But we'll get there as soon as we can.
Regards
Paul
May 22nd, 2008
hymey

Hi fellas, I still can't get pass-through to work..With BBL all the dma pids are recording and displaying in the scan tool but They are not showing up on the PC when I upload them. The coil temp and inlet valve temp have GM in front of them instead of E38(unsure where to change this). They show up with red crosses in the log. The rest of the dma pids do not show up at all. Only time the BBL has not worked for me.

Cheers

Joel
May 22nd, 2008
Bruce Melton

Serial WB pass through for AutoVE etc?

All hooked up and displaying on V2 for serial WB (LM-1) and External pids found in 7.5 but invalid and not supported when trying to pass through to 7.5 build 56?

Are there canned instructions for the BBL and pass through?
May 22nd, 2008
Blacky

I will be working on the pass through problem today and over the weekend if necessary.
Regards
Paul
May 22nd, 2008
Bruce Melton

Sure works swell at the V2 level, now if we can just stuff it up the wire to the MAPS/dash!
May 22nd, 2008
swingtan

Quote:

Originally Posted by hymey

Hi fellas, I still can't get pass-through to work..With BBL all the dma pids are recording and displaying in the scan tool but They are not showing up on the PC when I upload them. The coil temp and inlet valve temp have GM in front of them instead of E38(unsure where to change this). They show up with red crosses in the log. The rest of the dma pids do not show up at all. Only time the BBL has not worked for me.

Cheers

Joel

Joel, I mentioned this a couple of posts back and I think you may be confusing the issue a little bit. I don't think the Pass-through issue and the DMA PID issue are related.

The BBL issue where DMA PID's don't display is just that the Meta-Data in the log file is using the wrong PID names. You can get a copy of HEXEdit which is a free download to alter the log files and make the DMA PID's work again. After installing HEXEdit, open a log file and scroll down a little to find the meta-data. In the right hand side of the HEXEdit page, it will look like this... ( surplus removed data shown as | )

Code:

[FILE],2..VERSIO N=7.1..DECSEP=.. .[VEHICLE],2..VI N=6G1ZK54H26LXXX XXX..OS=12607218 ..[PID],23..SAE. ECT=0..SAE.IAT=1 ..GM.INVLVTMP_M= 2..SAE.MAP=4..GM .APCYL_M=5..SAE. RPM=7..SAE.SPARK ADV=9..GM.ETCTP= 10..SAE.VSS=12.. GM.KR=13..GM.OCT SCL_M=14..GM.AFR ATIO_M=16..EXT.W O2ST1=18..EXT.WO | | | TE=2454610..STAR TTIME=18436..[En d_Of_Meta_Data],

Find the PIDs that don't show up and note the "GM" prefix, highlighted in BLUE above. HEXEdit will be in "Over Write" mode by default, so press the <Insert> button on the keyboard to enter "Insert" mode ( check the bottom right hand corner of the screen ). Place the cursor just in front of the "GM" by clicking with the mouse, then press <DEL> twice to remove the "GM". Then type in "E38" to insert the "E38" prefix. Do this for each PID that is named incorrectly in the log file. When done, it should look like this...

Code:

[FILE],2..VERSIO N=7.1..DECSEP=.. .[VEHICLE],2..VI N=6G1ZK54H26LXXX XXX..OS=12607218 ..[PID],23..SAE. ECT=0..SAE.IAT=1 ..E38.INVLVTMP_M =2..SAE.MAP=4..E 38.APCYL_M=5..SA E.RPM=7..SAE.SPA RKADV=9..GM.ETCT P=10..SAE.VSS=12 ..GM.KR=13..E38. OCTSCL_M=14..E38 .AFRATIO_M=16..E XT.WO2ST1=18..EX | | | .[End_Of_Meta_Da ta],

Click <file>-<save as> and choose a new file name so you don't overwrite the original ( just in case something went wrong... ). Opening the file in ScanTool should now display the DMA PIDs correctly.

I'm not sure about the pass-through issue, I haven't tried it. I'll give it a go later and see if I can log in pass-through.

Simon.
May 22nd, 2008
hymey

Sorry Simon,

I miss informed you, the pass thru and the dma pids are seperate problems. I will have a go at the hex edit now.

Thanks mate.

Joel
May 23rd, 2008
Chevy366

Keep getting this error when I try to read a guys 2004 GMC truck :
http://i71.photobucket.com/albums/i1...iliveerror.jpg
Can read the PCM with Tune Tool , just can't connect with Scan Tool .
May 23rd, 2008
joecar

You're connecting to FlashScan only... tell it to connect to the PCM.
May 23rd, 2008
joecar

May 19th update, testing on LS1B:
- scantool connects/logs ok in passthru mode (OBD-II stuff and DVT stuff works),
- BBL mode logs ok,
- Diagnostics displayed/saved ok.
- Clear DTC: V2 says "Error $0281" but it does clear the DTC.
May 23rd, 2008
Chevy366

Quote:

Originally Posted by joecar

You're connecting to FlashScan only... tell it to connect to the PCM.

? , I selected the correct PCM from the drop down list , like a thousand times before .
Was default set to "FlashScan/AutoCal only" this update ?
May 23rd, 2008
Blacky

1 Attachment(s)

Quote:

Originally Posted by tunedbyGM

? , I selected the correct PCM from the drop down list , like a thousand times before .
Was default set to "FlashScan/AutoCal only" this update ?

If FlashScan cannot communicate with the vehicle, it will report back to the EFILive software that only a connection to FlashScan was made. That has the same effect on the rest of the software as if you had selected "FlashScan only" from the list of controllers to connect to.

If you're not getting a connection to the vehicle, watch the [Console] tab page and note what is displayed when FlashScan is attempting to communicate with the ECM, PCM and TCM modules.

Regards
Paul
May 23rd, 2008
Chevy366

I just tried it again , and made for certain that the correct controller was selected , same error .
This is what happened , plugged to ODBII port , then Laptop opened Scan Tool , selected correct PCM controller , pressed the "green" button , Scan Tool appeared to load , hit "yellow" button and got the error reported .
May 23rd, 2008
Chevy366

Quote:

Originally Posted by Blacky

If FlashScan cannot communicate with the vehicle, it will report back to the EFILive software that only a connection to FlashScan was made. That has the same effect on the rest of the software as if you had selected "FlashScan only" from the list of controllers to connect to.

If you're not getting a connection to the vehicle, watch the [Console] tab page and note what is displayed when FlashScan is attempting to communicate with the ECM, PCM and TCM modules.

Regards
Paul

O-k , will go try again and see .
May 23rd, 2008
Blacky

The ignition is on right?

Press Ctrl+Ok on FlashScan. Do you get the VPW or CAN message in the lower right corner of the FlashScan display?

Does the right hand side orange LED flash when you cycle the ignition off then on?

Regards
Paul
May 23rd, 2008
Chevy366

Screen Shot :
http://i71.photobucket.com/albums/i1...ILive_data.jpg
Help any ?

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