2005 1500 HD , Custom OS3 SD tune .
2006 Trailblazer
Dinosaurs and Plants gave their lives so that we may drive , long live fossil fuel .
No problem
I remembered it because I missed it the first time around
Glad I could help
99 Silverado 2500 Extracab Longbed
33" BFG's - American Racing Rims
Custom Dual Upper console gauge mount w/Autometer Sport Comp - Pyro, Oil Temp
Autometer Sport Comp Boost/Vac in Custom Hypersonic Gauge Mount in dash
LS-1 6.0L w/AFR 205cc Street Heads
Vortech V2 blower
42# Injectors
Comp Cam - Custom Street Grind
TTS Catback Exhaust
Innovate LC-1 Wideband O2
Tune and Trans mods via EFILive V1-V2
2005 1500 HD , Custom OS3 SD tune .
2006 Trailblazer
Dinosaurs and Plants gave their lives so that we may drive , long live fossil fuel .
From todays experiments:
LLY TP PID does not work on the V2 but TP_A does!
The TP PID does display on the PC correctly.
When logging data it will overwrite existing files without any notice!
(after a reflash to the latest FW I might add)
What are the rules to the names, when is the counter reset?
Selecting LLY Auto does not work, no frames will be logged or updated data displayed.
DVT is pretty sweet! Turning on/off is a little weird sometimes as the setting will remain on even when shutting off the feature (e.g. idle speed)
2005 RCSB 2500HD GMC Sierra DURAMAX LLY
1955 Chevy Truck 1st series, being restored
2002 Mercedes C270 CDI
Lennart and lakingslayer, the "weird frames or "logs full of notes" sounds like the problem I'm having as well. I've found that repeated tries at opening the file eventually seems to get a clean read and displays "sane" data. I have no idea if the data is actually correct though.
The way the logs look when they open in "corrupted" form reminds me of the first BBL logs I tried on the E38 when the V2 would cause I/O problems between the ECM and other modules, bringing up dash alerts and dropping corrupted data into the log file. This was back around the start of this year. When opening these files in ScanTool, I'd get the same weir looking data displayed as I get now. It's almost like the BBL files don't have an <EOF> character and ScanTool ends up with random data at the end of the log.
Simon.
Can you send me a *.efi file that has the random data problems?
Send to paul@efilive.com
Thanks
Paul
Before asking for help, please read this.
Yes, they will be defaulted to WBO2 in the "public" release.
There are two COM settings, one for in and one for out. For example, you may be reading COM data from a wideband, but outputting data to a dyno controller. You can do that from FlashScan's single RS232 connector if you make up a custom Y serial cable.
P.S. The dyno data is output on the serial port now. I will publish the data spec soon.
Regards
Paul
Before asking for help, please read this.