Quote:
Originally Posted by GMPX
Please let me know. That shop put in a switch for the dsp5 already.
Printable View
Quote:
Originally Posted by GMPX
Please let me know. That shop put in a switch for the dsp5 already.
Bobo, sorry but I was wrong, the Van OS does not support DSP5 (or DSP2). The Van's OS had different table structures to the trucks, yet it retained the same OS number, I'll try to explain the issue.
The problem with that was a couple of the DSP tables in the trucks (just as examples) may have been defined as say 17 x 17 in size, the van OS for the same table used 14 x 17, or 14 x 14, something along those lines. So we couldn't put the DSP tables in the Vans OS because they didn't match in size. This would not have been a problem IF GM had given the Van a different OS number, but they didn't, it's the same as the trucks and so we could not distinguish what maps would need to be used when the DSP upgrade patch was done, truck style or van style. Sorry Bobo.
I found a problem. When I tried to use V8 it crashed my HP laptop which wouldnt recover. I bought a brand new HP and V8 crashes it also, but it was able to re-boot. I have to use the old drivers or it wont recognize my V2 but every time I try V8 it goes instantly to blue screen of death.
Is that anytime you plug it in, or only when Windows is booting up with the V2 plugged in?
I have an HP Elitebook 8730 which also blue screens when booting up or when connecting to a docking station if multiple FTDI devices are connected. The same is probably true if a hub with multiple devices was connected. It is a fault in the FTDI drivers which does not occur when using the new drivers. However, the V7.5 software is not 100% compatible with the new drivers on some platforms so you have to use the old drivers and just remember not to have multiple FTDI devices connected when performing actions that cause drivers to get activated/deactivated.Quote:
Originally Posted by minytrker
Can you please confirm the exact details that are present when it crashes.
Regards
Paul
Anytime I open V8 with my V2 plugged in.Quote:
Originally Posted by GMPX
On both laptop's I was running on laptop battery and the only thing plugged in was my V2 into a usb plug on the laptop. I had already been using EFI with V7.5 for a couple hours on the 1st laptop then desided to flash a E38 with V8 and soon as I opened V8 the laptop when to blue screen. It has yet to ever come back on.Quote:
Originally Posted by Blacky
The brand new laptop I did a fresh install off efilive.com and the laptop would instantly go to blue screen as soon as I plugged in V2. I then installed the older driver as a administrator and could open efi and my laptop recognized my v2. I used it like that for a day or two and then desided to try V8 again since I had another E38 car. Same thing again, V8 blue screened my brand new laptop. After 30 mins of trying to get it to re-boot it finally came back on. I have since re-installed everything and am using the older driver but I have not tried V8 in fear or bricking another laptop. I have a couple really old laptop I can try it on but they are all dell where all 3 of my new laptops are HP so not sure it will be a apples to apples test.
It may be worth removing the FTDI drivers and associated driver software, then reinstalling the drivers.
Open the Windows Device Manager and uninstall all FlashScan/AutoCal devices with the option to delete driver software.
Attachment 12887
If you don't have FlashScan/AutoCal connected, you can still see/remove the drivers if you set the environment variable:
DEVMGR_SHOW_NONPRESENT_DEVICES=1 before opening the Windows Device Manager. And select the device manager menu option: View->Show Hidden Devices.
Attachment 12888
Re-install the drivers using the program Start->All Programs->EFILive->V8->EFILive USB Manager
Reconnect FlashScan, wait for the drivers to load.
Start the V8 software. Hopefully that fixes the problem.
Regards
Paul
I'd guess that if you disconnect the FlashScan device, it should boot up without blue screening.Quote:
Originally Posted by minytrker
Can you confirm that when the laptop was failing to boot after the blue screen that the FlashScan was still connected?
Regards
Paul
I was going to start a new thread the other day, but did some more "playing" and got my flashscan working again but seeing as i fixed it, thought i should atleast mention it in here, incase it happens again.
I have 2 x V2 Units, 1 blue, 1 black.
2 x Techedge 2j9 wideband using serial
blue was loaded with firmware .23
black had the latest .26
Problem: I couldnt get afr to come up the scanner or v2 unit's. lambda was working fine, just no afr.
Solution: Upgrading the firmware on the blue one got the afr working straight away, yet it took a reloading of the firmware on the black for it to come good again. this included me powering up/down both units multiple times.
Anyway they are working again now but it was a WTF is going on moment for a while. (I even have a log from a car where lambda is changing but afr is at 0 jumping up to 25, 6 etc)
In one of the RC versions we added the option to specify a stoich value that is used to convert from Lambda (i.e. the value from the WO2) into AFR. It had a bug that caused the stoichiometric value to default to 0 instead of 14.7 IT was corrected in a later firmware version.Quote:
Originally Posted by Tre-Cool
You should check that the stoich value is set correctly in the settings for FlashScan for the fuel you are using - as shown below:
Attachment 12889
If it is/was set to 0 (i.e. has never been set by you) it will now correctly default to, and show up in the settings, as to 14.7 instead of 0.
Regards
Paul
Quote:
Originally Posted by Blacky
I always unplug the V2 if the laptop crashes, and I never boot up the laptop with anything plugged in. I always wait until the laptop is done booting up before plugging in the v2 or anything else.
There is some way to distinguish between a van and a truck. The van os says no DSP 5 upgrade available and the same os in a truck config allows a dsp5 upgrade.Quote:
Originally Posted by GMPX
When a dsp5 upgrade is done, the operating system is changed. Why can't the van dsp5 os be different than the truck dsp5 os even if they originate from the same stock os?
Bobo, it's subtle but the .calz file number isn't the same. I remember back when we first saw this problem and couldn't believe Bosch would designate the same OS number to tunes that are different. I had (and still haven't) ever seen any other GM controller do this.
In the end we had to look for specific markers in the file to know that we had to load an alternate .calz file that showed the right tables to match the Van.
Notice how the OS number is 12632483, but the .calz file we load is called 12632484.
http://download.efilive.com/Staff/GMPX/OS_Calz.png
Unfortunately though V7.5 still see's both files as 12632483, so we can't Upgrade the OS to DSP to match the Van because the patch can't pick the difference between them.
There is also an LMM OS we don't do DSP for, 12620015, this is used on Motorhomes and the 5500's.
Hi,
I have tried to down load the latest V8 software, but the link seems to be down. I have tried on two different computers.
Cheers,
Laychut
Try downloading builds 201 and 192 from here: EFILive downloads page
The EFILive drivers are FTDI's drivers. They are digitally signed by Microsoft and certified to be identical to FTDI's drivers. In fact FTDI supplied the drivers to EFILive that we get digitally signed by Microsoft under our own name. EFILive does not make any modifications to the drivers -we are not allowed to or Microsoft will not and cannot sign them. We just package them and have them re-signed under our own name.Quote:
Originally Posted by Wolfie
Regardless, I think the problem is a conflict between the old and new drivers supplied by FTDI. EFILive V7.5 must use the older drivers, EFILive V8 can use the older or newer drivers. However, if you have other devices that use the newer drivers and you install the older drivers (for V7.5) then the FTDI driver set gets messed up. I've tried contacting FTDI support about it but they are not much help, they just tell me to upgrade the drivers to the newer ones. That's understandable from their point of view, but that breaks the V7.5 software.
In other news, once EFILive V7.5 is retired and V8 takes over the scanning and tuning duties then the old/new driver conflict will no longer be a problem.
Regards
Paul
Is there a way to make v7.5 default to check the try alt keys and use high speed boxes when tuning. Also default V8 to check try alt keys, assume lock is faulty, and use high speed. I think it might be a good idea to move those check boxes to a settings button and only make it show up if a flash fails kind of like the vin unlock button shows up after a failed flash. I guess what I'm getting at, is why would you not use try alt keys and why is the check box there? I have my customers check it all the time on the diesel stuff. Some new customers get confused or forget/accidentally uncheck it. It's not a big deal, but having software that defaults to the most common settings when it is first downloaded would make it easier to use for a new customer.
If v7.5 can't tell the difference, can I get a separate tab that can make a dsp5 van os?Right now it gives a dsp2 and a dsp5 option, how about a dsp5-van option?Quote:
Originally Posted by GMPX
Hi Bob,Quote:
Originally Posted by bobo
If your customers cannot read/flash their controllers without using the alt keys or assume lock is faulty options, then you should be telling your customers to use the unlock option to set up a standard GM seed/key in their controller. That way in future they won't need to select that option.
As for the factory default settings for those settings, t takes 10 seconds per failed key to unlock an ECM. Trying the alternate keys can slow down the process by as much as 30-50 seconds for stock controllers. The alt keys and "assume lock is faulty" are for the very small number of ECMs that have had their locking systems messed up somehow. The vast majority of controllers can be unlocked without using those options.
I might be missing something on the "use high speed" option, but are you saying that your customers cannot read/flash their controller unless the "use high speed" option is off? In that case it is most likely a rogue module that is not switching to high speed. In that case pulling the module's fuse would help. Using low speed mode is 4 times slower, so I guess its a trade off between how long it takes to pull/replace a fuse compared to how much longer it takes to read/flash in low speed mode.
Regards
Paul
How do we manually check for software updates now? I found the tab in the V7 tune tool to check for updates with it and found there was an update for it above the first public release I downloaded, but I can't find a way to do it with the V8. I used to go under start, EFILIVE, and then select the check for updates under teh tools tab, but I see that option is no longer available.
I do not think they have implemented the check for updates yet, They turned that feature off.Quote:
Originally Posted by THEFERMANATOR
I do not remember reading the it was available to use yet.
As has been discussed in previous thread, we changed software installers on this new version. If you have older software then you must manually uninstall that software first.
Once the software versions from this thread are installed you can check for updates by doing the following:
V7
Go to 'Help' then click the 'check for updates' option.
V8
On the main page, the big Icon that says "Install Updates" (probably should say Check rather than install).
And yes, there has been an update already, so feel free to give it a go.
Cheers,
Ross
Thanks.Quote:
Originally Posted by GMPX
The main web page links also have the latest versions as well.
Just updated to the latest public v7.5 and v8 software release, and checked for updates. Firmware: 2.07.26 (Mar 28, 2012). Bootblock: 2.07.04 (Dec 12, 2011). Config files: cummins cm849 (apr 16 2012), options (apr 16 2012). Getting a $502 error (something about script files) when trying to flash using just the v2. Any ideas?
Thanks,
Mike
I recommend doing this:Quote:
Originally Posted by 2006Cummins
1. Start the V8 Scan and Tune software.
2. Open the BBX settings window.
3. Click on read to read your V2's current configuration.
4. Select "Format CONFIG File System" from the [Program] button's drop down menu.
5. Click on the [Program] button to program all required files.
If that still does not work, use the "Program all Required Data (slower)" option on the drop down menu. Sometimes, within 24 hours of an update (due to crossing the international date line) the date/time stamps on the config files can confuse the algorithm that decides if a file is older or newer than what's on the device. Using the "all" option overrides that algorithm and copies all files.
Regards
Paul
I will give that a try, thanks.
I tried the method above and it still wouldn't work. I found I had to go into the EXPLORER program and manually delete the files from the options tab and then format and program all to get mine to work.Quote:
Originally Posted by Blacky
Worked for me. Thanks!
There are two file systems that can be formatted. If you format the DATA file system, that will have no effect on your config files. You'd need to format the CONFIG file system. If the CONFIG file system was formatted then there would be no files left in the CONFIG file system (i.e on the [F9: Config Files] tab page) for you to delete. It may be possible that you formatted the DATA file system, thinking it was formatting the CONFIG file system.Quote:
Originally Posted by THEFERMANATOR
Some background info that may help...
You can only format the CONFIG file system from a PC, using either the drop down menu format option of the [Program] button in the BBX setup window, or from the [Format] button on the [F9: Config Files] tab page in EFILive Explorer.
You can only format the DATA file system using FlashScan's or AutoCal's on-board file system format option.
The reason you cannot format the CONFIG file system from the FlashScan or AutoCal device is so that you do not accidentally format it while away from a PC (i.e. at the track). If you did that then your device is useless until you can reload the config files from your PC.
Regards
Paul
No you can't install without the drivers, they are automatically installed during installation.Quote:
Originally Posted by Wolfie
Regards
Paul
I tried to upload a new file into my truck today. .. I keep getting EFI Live script exited with code $312 Sub Function not supported or invalid.... I have updated everything to the newest version and firmware.. If someone could help me out I would appreciate it... Thanks.
There's a bunch of information we'd need to collect from you to help track down the problem, it would be best if you logged a help desk ticket here: http://support.efilive.com/Quote:
Originally Posted by hhrecovery
Regards
Paul
Has there been any previous programmers loaded on to this truck?Quote:
Originally Posted by hhrecovery
Are you able to read the tune out of the truck ok?
Nothing else ever used... It has a tune in it now and I have been running it for a couple weeks like this... I had a new tune made to make some minor changes and now it won't upload or read the current tune...Quote:
Originally Posted by GMPX
Did your tuner lock it?
Sorry, as in read. I meant it won't read the tune that is currently in the truck..Quote:
Originally Posted by GMPX
If your tuner locked it. You can't read the file that's in the truck. Or view the file in the Tune software. All you can do is flash over it.. Only if the tune that is currently on your truck is locked. Not the tune your trying to flash in.. COurse if that ones locked too. You'll have the same issue with it.
can i ask when the accessory power flicker at about the 46kb mark on the e38's happened?
i only flash with the 7.5 program and it's annoying as all hell when programming and it resets anything powered up by the accessory power circuits, including the stereo and lights. (in ve commodores).