i got my tune files saved to my auto cal but when i go to prog 1 or 2 either one i get a $0502 code can anyone help
Printable View
i got my tune files saved to my auto cal but when i go to prog 1 or 2 either one i get a $0502 code can anyone help
You have to program all the necessary files to your AutoCal's config space;
from the V8 S&T program, goto BBx, click the down arrow next to the Program button and click Program All.
I am having the same issue. I did what you said, and still have the problem. Starting to get annoyed with this...
Many of us are having this issue...i believe Paul is working on it.
Glad to hear this is getting fixed. I can pull my tune from the car via the pass-through capability only. The tuner never worked by itself. I sent the file to my tuner, he adjusted it, and I tried uploading it. Now I get "*.ctd files is not registered to this Autocal device". How can this be since it is the tune I sent him?
He needs to "save tune file for remote flashing"...Also, the autocal needs to be "linked" to his V2... Passthrough works properly on ours in house as well.
We keep getting $050B over here. Done everything possible to correct it. Waiting to see if Paul has a fix for it yet.
Hi Everyone,
The errors $0502 and $050B reported in this thread are not being worked on by me or anyone. Those errors are almost certainly caused by incorrect AutoCal setups.
$0502 is "Script file not found". That simply means the *.obj file required to flash the selected controller has not been downloaded to the AutoCal device.
You can use the EFILive Scan And Tune software to automatically update your AutoCal or you can download the appropriate file(s) manually.
I'll describe the manual process, because if you have a good understanding of the process and what is required you will be able to easily solve any future occurrences.
For FlashScan or AutoCal to flash a controller in standalone mode it needs at least three files to be copied onto it:
1. A script file (*.obj) which contains all the instructions required to reprogram a controller. These script file are not to be confused with the scripts that you may use to apply changes to your tunes in the PC based V7.5 software.
2. A bootloader file (*.blx) which contains the software required to reprogram the flash memory chip(s) in the controller. Note: not all controllers require bootloader files. LBZ, LMM, CMB and CMC controllers do not require boot loaders.
3. A tune file (*.ctz) which contains your calibration changes.
Script files are named like this: XXX_T.obj where
- XXX is the controller code such as LBZ or CMB,
- T is the type of script and is one of: R for reading, W for cal flashing and F for full flashing.
So if you were attempting to full-flash a Cummins 5.7 controller the script file would be CMB_F.obj
The bootloader files are named like this: XXX_T.blx where
- XXX is the controller code such as LBZ or CMB,
- T is the type of script and is one of: R for reading, W for cal flashing and F for full flashing.
So if you were attempting to cal-flash an E38 controller the script file would be E38_W.blx
The *.obj and *.blx files can be found on your PC in the folder:
\Program Files\EFILive\V8\Config (for WinXP and Win2K)
or
\Program Files (x86)\EFILive\V8\Config (for Vista and Win7)
You can copy them to FlashScan or AutoCal using EFILive Explorer. They must be copied into the [F9: Config] tab page.
Attachment 12615
The tune file is named whatever you like but should be short enough to be displayed in AutoCal's display (i.e. 8 or less characters).
Note: there is currently a bug that causes extremely short file names (1 or 2 characters) to not show up on FlashScan's screen - that bug is being worked on).
Tune file names should also be less than 63 characters in total, including the \EFILive\Tune path prefix.
Tune files should be copied onto FlashScan/AutoCal in the [F3: Data Files] tab page to the folder: \EFILive\Tune
Error $050B means the script file is the wrong version for the firmware in the FlashScan or AutoCal device.
Make sure your software is up to date and the the FlashScan/AutoCal firmware is up to date prior to copying any *.obj files to FlashScan or AutoCal.
If anyone is absolutely certain they have copied the correct files to their FlashScan/AutoCal devices and they are still getting $0502 or $050B errors, please post more details in this thread and I will investigate.
Regards
Paul
Thanks for the help Paul. I had to update update bootblock and Firmware via EFILive Explorer and the $050B is no longer the issue. What's weird is EFILive control panel said both BB and FW were up to date, but in Explorer the FW was still from back in December. Anyway I'm at the $0549 since I don't have a truck to test on, but looks like we are good to go. If the customer reports back with any problems I'll let you know. Thanks again.
Until the release candidate software officially goes "public" the EFILive_HAPI software will not recognize that the firmware needs updating. You must always manually update the firmware using EFILive Explorer.Quote:
Originally Posted by dansdieselp
The EFILive_HAPI software only detects and reports new firmware if/when the new firmware files have higher version numbers that what is in the FlashScan/AutoCal devices.
Because yo can never program FlashSCan or AutoCal with an earlier version firmware, the firmware version is kept at V2.07.22 during the release candidate process. That means you can move back/forward between the various firmware updates for each release candidate - just in case something goes horribly wrong when you do an update. The only way to know that you have the latest firmware is to check the date of the firmware.
The main thing to understand is that when the release candidate goes public the firmware version will jump to V2.07.23 (or maybe higher). Only then will EFILive_HAPI detect that a new firmware version is available. And once you update to that version there is no going back - so we have to get it 100% right before then. Until then you must manage the release candidate firmware updates manually using EFILive Explorer.
Regards
Paul
Boy I wish I knew that a couple weeks ago. lol. Makes perfect sense now and seems so simple. Just a side question Paul what is the situation for dsp5 full flashing the LB7 and LLY controllers?
All that info is written up on the software update thread.
Working on it right now...Quote:
Originally Posted by dansdieselp
Regards
Paul
I assume .BLX is now .BIX correct?
*.blx is the file extension for V7.5 read/flash trace files.Quote:
Originally Posted by ls1mike
*.bix is the file extension for V8 read/flash boot loader files.
The V8 equivalent of *.blx is *.htx.
*.htx files can be found in the folder: \My Documents\EFILive\V8\Trace
Regards
Paul
so I go to load config files because im getting this error and I have none in the config folder? where do I get them?Quote:
Originally Posted by Blacky
The config files should be installed when the V8 software is installed. If you install the V8 software again any missing files will be installed.Quote:
Originally Posted by DieselMafialb7
Also, for setting up AutoCals, you should now be using use the V8 option: [F5: BBX]->[F6: Quick Setup].
Regards
Paul
Trying to get one that was supposed to be setup already to work...... ill try re installing v8 I guess see what that does
uninstall and reinstall still nothing but text doc in the config folder.....
this is what I have in there?
Ok, now do this (from V8 S&T):
Quote:
Originally Posted by Blacky
Didnt fix it for me?
heres where I went and hit program did I do something wrong?
I think I know whats wrong the lml isn't in anywhere in the tune area how do I add it? its in scan but says unknown after e86 lml? that help anyone as to my issue? and before you ask or say I have the latest versions and am completely up to date
What year LML? 2011-2014 is E86A and 2015 is E86B. Open V8>F5 BBX>F3 Tune>Left click on the green + icon>Right click on engine controller box and select the correct ecm then program the autocal.
2013 I got to work I just need the damn files for some reason I didn't have them and efi didn't either but got the files and did all the same stuff again and worked like a charmQuote:
Originally Posted by IdahoRob