I see you guys snuck in the new EFILive logo into the V7.5 splash screen...very sneaky! (Hope this or RC7 was the first time this happened, otherwise I obviously havent been paying attention!)
Printable View
I see you guys snuck in the new EFILive logo into the V7.5 splash screen...very sneaky! (Hope this or RC7 was the first time this happened, otherwise I obviously havent been paying attention!)
I tried tuning a 6.7 today that was a 08. I have the latest version downloaded (I think) Auto scan worked but it took 30 minutes to read the stock tune and im sure thats not right cause i read somewere that they sped that up a bunch. I couldn't license or tune the truck so im guessing something i did with software isn't right. Any help would be greatly appriciated thanks, Eric
Eric, we have been playing around a bit with the 6.7L read times, on first release it was just on 30 minutes, but it was stable. Since then we've sped things up with one release down to about 18 minutes, again there didn't seem to be any issues with stability. The current RC8 release should read one in about 11 minutes, but this is pushing the ECM to it's limits as far as how fast the Dodge read routines will allow us to get the file. I don't think there has been any reports of failures which is a good sign. Quite often what works on a test bench doesn't play as nice in the vehicle.
Anyway, the release this thread is for is indeed the latest, if this is what you are running then perhaps you didn't update the V2's firmware as well, that must be done as it has a necessary update for the faster read times.
It did need updated. it autp updated to this but i still don't think its the latest version and it won't let me type it in manually. The bootblock is 2.07.02 and the firmware is 2.07.12 Now on a different screen looking at the same stuff it says bootblock is 2.07.03 and firmware is 2.07.22? Im not computer stuipid but somethings kinda stump me lol. Thanks for being patient with me. Ok, I refreshed the first page i read the old version from. Now it is stating the new boot/firmware. As i stated above.
BootBlock needs to be DEC 12th or 13th, and Firmware Jan 6th. DO NOT AUTO UPDATE till further notice from EFILive!!! Note: when downloading this RC8, you will need to manually program BootBlock and Firmware files to FlashScan as well as Format Config file system and program all files for the controller you want to BBL or BBF. See previous posts in this thread for more info.
Where do I find the January bootblock? I've got the January firmware, but the bootblock is from Dec 12th. Didn't see it in my bootblock folder. Also, I'm not sure what you mean by. I see the format button under the config files tab - there is no info in there now. What files do I need to program in there?Quote:
as well as Format Config file system and program all files for the controller you want to BBL or BBF.
Mike
You're right. My mistake. DECEMBER 12th.
And what I mean by Format Config Files is to Format Config in V8 and select CMB849 (for example if you want to flash with just the V2 without the laptop) and program all files slower.
Thanks. I think I've got it.Quote:
And what I mean by Format Config Files is to Format Config in V8 and select CMB849 (for example if you want to flash with just the V2 without the laptop) and program all files slower.
Ok, I'm having a little issue with my customers getting their autocals and it not working on the truck. I load the tunes using this release and firmware ect..and it just will not flash the truck. My scripts are from a previous release...do i need to rewrite the tunes?
Thanks,
Kory
Kory I had the same issue a few weeks ago, I Just rewrote the tunes so far so good. I since then have not used a script so I cant confirm or deny that was for sure the issue. Im pretty sure but its been crazy around here. Ill look back through my notes and see if I can refresh my memory.
They are not perfect, but the Autocal instructions here may help. The same procedure is used to set up a V2 as an Autocal, so just ignore the fact that it talks about an Autocal.
Ira
Has any one had issues with serial WB data with this RC?
I upgraded last Friday and now can't display the serial WB data in Scantool. I know the PID's are selected ( it automatically selects all serial data PID's ) and the config is correct for my WB ( Techedge 2.0 ). Yes, I formatted the config filesystem after the firmware upgrade and everything else seems to be working OK. I have valid data for both EQ and Lambda, just nothing coming up for AFR. The live display on the V2 also has no AFR data, but it does show valid EQ ratio data.
Any idea's on this one ?
Simon.
Thanks Paul, I've made a Calc PID to generate AFR from Lambda, so it's not a huge issue ATM ( providing the data is accurate, which it seems to be ).
Actually I've just figured out it was the test harness that was wrong. I've corrected the test harness and the FlashScan firmware is working properly and showing AFR correctly.
If you've got time, can you connect up the Tech Edge and display the Wo2 data on FlashScan's screen. Let it display for 5-10 seconds, then save a trace file and send me the trace file?
That way I can see exactly what if any, serial data is coming from the Tech Edge.
Also let me know what you expected to see on the FlashScan screen (i.e. what AFR/Lambda) and what you actually saw on the screen.
Regards
Paul
Interesting.....
I get EQ and Lambda data, just no AFR. I did the display test before posting to confirm something was there ( V2 configured to display AFR and EQ Ratio ). The AFR data remained at "0" while the EQ changed value. If I pull apart a log file, I see the following.....
and if I look at a few frames....Quote:
EXT.WO2ST1=42
EXT.WO2LAM1=44
EXT.WO2AFR1=46
EXT.WO2EQR1=48
EXT.WO2ST2=50
EXT.WO2LAM2=52
EXT.WO2AFR2=54
EXT.WO2EQR2=56
I'll go get a trace for you though.Quote:
00 01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66
37 35 e4 21 52 03 86 51 88 75 71 87 88 00 8c 00 8e 80 00 00 00 11 0e 08 45 01 f9 05 39 1b 94 af 0e 42 fb 73 55 02 f5 35 fc 89 00 01 03 f1 00 00 03 df 00 00 06 a5 09 c4 02 4b 00 00 00 00 89 10 81 01
37 35 e4 21 52 03 86 51 88 75 71 87 88 00 89 00 8b 80 00 00 00 11 02 08 33 01 f7 05 41 1b 9b b6 0c 42 fb 73 55 02 f5 36 2e 8a 00 01 03 f1 00 00 03 df 00 00 06 a5 09 c4 02 4b 00 00 00 00 ae 10 81 01
37 35 e4 21 52 03 86 51 8d 75 71 87 88 00 8a 00 8c 80 00 00 00 11 0e 08 45 01 f7 05 37 1b 8e b8 16 42 fb 73 56 02 f5 36 15 8a 00 01 03 e2 00 00 03 ee 00 00 06 a5 09 c4 02 4b 00 00 00 00 d4 10 81 01
37 35 e4 21 52 03 86 51 8d 75 71 87 88 00 8d 00 8e 80 00 00 00 11 15 08 50 01 f5 05 36 1b 83 bb 12 42 fb 73 56 02 f5 36 15 89 00 01 03 e2 00 00 03 ee 00 00 06 a5 09 c4 02 4b 00 00 00 00 f9 10 81 01
37 35 e4 21 52 03 86 51 8d 75 71 87 89 00 8c 00 90 80 00 00 00 11 02 08 33 01 f7 05 32 1b 92 bb 18 42 fb 73 56 02 f5 36 47 8a 00 01 03 e2 00 00 03 ee 00 00 06 a5 09 c4 02 4b 00 00 00 00 1f 11 81 01
37 35 e4 21 52 03 86 51 8d 75 71 87 89 00 8c 00 8f 80 00 00 00 11 15 08 50 01 f9 05 41 1b 94 bd 21 42 fb 73 53 02 f5 36 15 8a 00 01 03 de 00 00 03 f2 00 00 06 a5 09 c4 02 4b 00 00 00 00 45 11 81 01
Simon
here you go.....
Attachment 12640
And an image of the TE display with the V2 display....
Attachment 12639
Simon.
Ahh, now I see the screen shot I can see what the problem is.
One of the updates that went through recently was to allow you to specify the stoichiometry for the fuel that is in use.
Yours is probably set at zero which means the conversion from lambda (or EQR) to AFR is failing.
Go into settings on the V2 device and set stoich to the value you need/want it at.
Or change it in the Device settings of the V8 software.
It is supposed to default to 14.7 if the user does not set it - I'll need to figure out why its not doing that.
Attachment 12641
Ahh, that sounds like what's happening. I was really confused that I was getting EQ and Lambda but not AFR. I'll give it a test and report back, thanks again.
Simon
That was it! I must have cleared it by accident when reapplying all the settings.
Simon.
No it wasn't something you did. The config value will always be zero until you explicitly go in and set it for the first time.
The firmware was meant to cater for that by checking for zero and defaulting to 14.7
The default was not being handled correctly for some WO2 controllers.
Basically each controller type has a separate function that computes the lambda value from the raw serial data and also converts it to AFR.
The code was reading the config value and initializing it to 14.7 if it was zero.
However in some of the routines the stoich value was being re-read from the original config value (and getting set back to zero) instead of using the default that had already been set to 14.7.
Regards
Paul
Ahh, OK then. All fixed now though, I wish I got service like this from the vendors at work! It took us 2 months to get a patch for an application that was leaking 5MB of memory per hour.
Simon.
Ugh, that doesn't seem like that bad of a memory leak...but after a few days it turns into a LOT!
Glad you got this figured out guys, I was confused when I read it yesterday, but with my Innovate LC1 the controller handles the stoich programming.
Sorry, yes you're correct, it is in the Edit Settings option on board FlashScan even if Innovate is selected (however it is ignored when computing AFR when Innovate is selected).
It is not available in the V8 software Device Settings option when you have Innovate selected.
Regards
Paul
Cummins 5.9 "timing coolant temp multiplier" ECT axis points and first column values change after closing and opening with tune tool
For some reason I cannot retrieve the Log file from V2 or autocal EE shows no file?? . I see I should up date the Script files... how do i do that??
No I mean drastic change I set axis values top to bottom as follows -20 -10 0 10 20 and so on it might stay our it might change to and this is what happens most of the time, 64 at top decreasing to zero then back up to 64 at the bottom, and first column I set top 4 cells to 1.00 and they change to .2 up to .8 I think
Ah, ok, thanks (I was wondering if he saw the Scan folder).
Any news when this RC will be commercially available with the ability to disable egr, dpf and all emissions systems? Thanks.