Is the firmware wrong ?
Says May 12th, 2008 .
Just re-flashed and now says May 19th, 2008
Thanks , for the help that was it .
Printable View
Is the firmware wrong ?
Says May 12th, 2008 .
Just re-flashed and now says May 19th, 2008
Thanks , for the help that was it .
Did you check these things?Quote:
Originally Posted by Blacky
May 19 is the latest firmware.
(My screen shot says May 22 because I am using the next update that has not been released yet.)
Regards
Paul
Yes I figured the May 22 was next unreleased update date , see above .
Thanks
Don't know how I missed and selected the wrong update .
Man have to many things going at once !
That's it... May 12th didn't connect to VPW. May 19th does. :cheers:Quote:
Originally Posted by tunedbyGM
When i try the latest update to BB log. i choose pids eg LS1B A and then go to start logging and it says no pids selected. I notice that after i select pids it changes whats displayed as VPW to ALDL.
Is there something wrong with the update or something i can do at my end.??
Steve, are you using the May 19th update...?Quote:
Originally Posted by oztracktuning
Yes I am
I was just wondering if logging serial wideband in pass through mode is up and running. I was keen to see how this operates with RTACS?
Is this something that is currently being worked on or tested?
Serial input and output for Dyno's, has anybody tested this yet, as I see it is selectable in flashscan next to the wideband?
I have a little testing to do on a Superflow Engine Dyno that I have been working on for the last couple of months and it's all starting to come together. Support for this Dyno and serial input and output, is there any chance?
Do you require Dyno information? Will this help any?
Hummm I do ask a little, but the time has come....:angel_innocent:
Cheers
Mick
last week i got a mainline dyno outputing serial in to my V2 cable , i have installed a second rs232 port on the dyno PC in ready for the update from Andrew . i have not had and news from Paul or Andrew in the last 3 weeks so i take it there still working on it
That sounds great Geoff!
Thanks for the update on the Dyno setup at your end.
Were you able to log data from the Dyno into flashscan in a usable sense were you could review the log file?
I would guess that Dyno protocol is much the same if not more complicated than wideband and support for various Dyno's will be something further in the future.
Good work!
Cheers
Mick
All i can do at this stage is use serial wideband data out of the wideband built in to the dyno
We just need craig to make a E38 Roadrunner ECM
Maybe he already has and it's being tested, I see that there are RR lines under E38 in the cal link txt file on the beta software?
I asked the question but he did not answer me, so we can only imagine..:)
Cheers
Mick
I asked a week ago and got not at this stage sorry , but if more people ask we may get oneQuote:
Originally Posted by MICK
Dyno integration is currently being worked on.
The first stage is done and if you select dyno output for the serial port on FlashScan then it will output ALL the PID data to the serial port.
I have not released the format of the data yet, but once it is released it will be readable by any device (i.e. dyno controller computers).
The second stage: reading dyno data and the third stage: providing dyno controllers with the ability to control FlashScan's DVT options will require working closely with dyno manufacturers.
RoadRunner for E38 is not trivial, it would be a *lot* of work to implement. Orders of magnitude more difficult than LS1.
Regards
Paul
Most E38 DVTs don't seem to be working on any vehicle I've tested. CASE learn yields a no reply, try again message. The only thing that I've been able to confirm is working properly is the MIL on/off light.
Thanks Blacky I will try that today.Quote:
Originally Posted by Blacky
cheers
I got all excited thinking that final spark for e38 might be there now.. I guess Ill need to wait longer :)Quote:
Originally Posted by dc_justin
I found the same as you with the idle speed control.
I am currently getting an Error $0281 when deleting DTCs on VPW vehicles. The DTC will be reset, though.
See this: showthread.php?t=8147&highlight=%240281Quote:
Originally Posted by Lennart
Cheers
Joe
:cheers:
With this update my BBL logging is not working? I used the files in the zip and did the upgrade flashes??
Tried the JAW wide-band and get "Controller Not Found" message .
Made sure cable is correct and that it was selected in V2 as well (LC-1 works and just changed controller to JAW) .
The serial on the JAW is working correctly (serial 2 , 3 , 5) , because I can use it's software and it registers correct data .
This is how I have the Serial to RJ25 (12) cable pins assigned :
DB9 RJ25 (12)
5 > 5
3 > 1 Switched rather than using Null Modem cable .
2 > 2
FlashScan could be misinterpreting the JAW data.
In the next update I have added the serial data to the trace capture. After the next update is available (in a day or two), please retry connecting to the JAW and then save a trace file and send it to me. Then I can see what data is being sent/received on the serial connection.
Regards
Paul
Quote:
Originally Posted by tunedbyGM
Thanks , will do .Quote:
Originally Posted by Blacky
If the RJ25(12) is the FS2 cable, then the following worked for me:Quote:
Originally Posted by tunedbyGM
DB9 RJ12
5>5
3>2
2>1
I made the switch using an old serial cable M/F so I did not need to tamper with the FS2 cable.
Quote:
Originally Posted by swingtan
Hey Simon....Having seen what you're looking at, I'd say that the one that is smoother is "filtered" or smoothed because the pcm is quite quick in these vehicles and rather than have guy operating the throttle (whose had too much coffee and might be shaking and vibrating a bit) I could see the "coffee guy's" erratic throttle transitions resulting in unwanted throttle transitions which could be avoided by "filtering" the TPS measured voltages.
Follow?
Chuck CoW
I'm not sure I follow Chuck.....
If you are referring to my image, the "smoother" ( yellow ) line is simply a logarithmic trend line of the data I had measured ( green Line ). Given this was back in Jan, when it took nearly 3 min to do a calibration flash on the car, I didn't do all the possible settings. But the trend line seemed to match up very closely. So a tune setting of 4% TPS is actually 27% TPS when measured by the PID ETCTP. If you want to control PE via MAP pressure with a low TPS% setting, then this table is very handy.
My original query was really regarding B2009 as it's another TPS% setting. Given the differences I found in the PE tables, I was wondering if this setting also would suffer from the offset. If it did, it would make fine tuning the wall wetting a bit "hit and miss".
I'm pretty sure that Dynamic fueling in the E38 is tightly coupled with the MAF though. I tried some tests with turning off wall wetting with the MAF disabled and there was no discernible difference measured AFR's. Once I turned wall wetting back on and re-enabled the MAF, there was a difference.
I have mine set at 6% simon which equates to 30% throttle, but when the car is idling Throttle is at 15% and WOT is 88%, but WOT is 100% when logging the alternate Throttle pid.
When will the update become available to repair the e38 pids.(to save going into hex edit each log)
Cheers
Joel
Quote:
Originally Posted by swingtan
TPS is very important..... I've been playing with the throttle with Ross a while ago and if you mess with loging throttle enough, there are a number of things happening like you described....
What I was saying was that you should not just assume the throttle parameter you're logging is the one that the pcm is using....I'm quite sure the actual pedal TPS is filtered and when you studs the tps stuff, there seems to be more than necessary.... They're doing LOTS of stuff with the different TPS values....
Chuck CoW
Will the dma e38 pids be a permanent fix(in hex edit) for the next update?
Cheers
Joel
They should be ok in the next update.Quote:
Originally Posted by hymey
Please let me know if they are not.
Regards
Paul
WHere do I find the latest update? my may 19th update is not allowing pass through or when Viewing my file on scantool, my wide band serial is not showing. I dont have serial Calc Ben 1 pids. and not able to look at my wideband on scantool while replaying logs from bbl.
I forwarded JoeCarr my log and he was able to see my air fuel ratio on his computer.
What am I missing?
At the moment you can do either of passthru or BBL but not both at the same time.
I can view your log just fine on my two laptops... I can see your serial AFR and BEN.
There must be something missing on your setup... I pm'd Tech Support.
I will try it again in pass though. SHould it work with the wideband hooked up in serial to the v2 and show on the laptop in pass though?
Don't have FlashScan displaying the wideband O2 screen or BBL logging when trying to log data in passthrough from the PC. Those three tasks are mutually exclusive. (I may need to force FlashScan to cancel BB logging and/or WO2 display when passthrough logging is started).Quote:
Originally Posted by Aint Skeered
Just leave FlashScan displaying a menu (not logging or displaying any data) when you want to log passthrough data.
You can log serial wideband in passthrough mode simply by having the wide band serial plugged into FlashScan.
As long as the left orange LED is on or flashing, then serial data is being received by FlashScan. The PC will automatically retrieve that serial data from FlashScan when you have the EXT.WO2AFR1 and/or EXT.WO2AFR2 PIDs selected.
Regards
Paul
How stable is the BB Logging, I have been waiting to try
OK. So I followed the directions in the Read Me file and put the latest version of V7.5 on my computer. I downloaded the files and they were not unzipped into a folder named \Program Files, they were unloaded into a temporary IE file. I tried several times and it always opened in a temporary file. So I went ahead and upgraded boot block and now I'm in dead poll mode. So how do I get out of dead poll mode?
you must install the firmware now.
I would, but you can't install the firmware in dead poll mode can you? I get a $0024 error or something like that which plasters across my screen and ad infinatum. What am I missing?
To update the firmware the unit must be in dead pollQuote:
Originally Posted by SOMhaveit
For a step by step read this:
http://www.ls2.com/boggs/efilive_fir...structions.htm
Hope it helps.
FlashScan and AutoCal are designed to be field upgradeable and have been configured with two
distinct software modules:
1. The boot block.
2. The firmware.
The boot block is a small, simple program that only has enough power to communicate with the
host PC, to perform various “power on self tests” (POSTs) and to erase and reprogram the
firmware. The boot block cannot erase or reprogram itself.
The firmware is the main program that controls the keypad, the screen and performs various data
logging and diagnostic scan tool duties. The firmware cannot erase or reprogram itself.
How to tell which mode is executing:
• When FlashScan is in dead poll mode, i.e. under boot block control, the two orange LEDs
will flash alternately.
• When AutoCal is in dead poll mode, i.e. under boot block control, the LCD backlight will
flash.
• When FlashScan or AutoCal are operating normally, i.e. under firmware control, the LCD
screen will display the normal menu options.
To be able to program new firmware into FlashScan or AutoCal, it MUST be in dead poll mode.
When you click the [Program] button in EFILive_Explorer, dead poll mode will be requested prior
to beginning the firmware update.
You may select dead poll mode manually by holding down the Ctrl key on FlashScan’s keypad or
the Ok key on AutoCal’s keypad while connecting the USB cable from the PC to the FlashScan or
AutoCal device.
To be able to program a new boot block into FlashScan or AutoCal, it MUST be operating
normally under firmware control. When you click the [Program] button in EFILive_Explorer, the
boot block will be updated, and then the first sector of the firmware will be deliberately erased.
The deliberate erasure forces FlashScan or AutoCal into dead poll mode until new firmware is
programmed. So after a successful boot block upgrade, FlashScan or AutoCal will enter and stay
in dead poll mode until new firmware is programmed into it.
Attempting to program the boot block when in dead poll mode DOES NOT WORK. Even
though FlashScan or AutoCal may indicate that the boot block has been successfully
updated.