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)