Pre-Release Update July 29, 2011

[Redline Motorsports]

Isn't it the same issue #1 noted under KNOWN ISSUES?

Seems like quite often I either go to read or write and I need to unplug everything and try to reconnect...it always will at least by the second unplugging....at worse I need to close the software and re open...

Thought it was "normal" with Build 170 and was getting looked at.

Howard

[Blacky]

Isn't it the same issue #1 noted under KNOWN ISSUES?

Seems like quite often I either go to read or write and I need to unplug everything and try to reconnect...it always will at least by the second unplugging....at worse I need to close the software and re open...

Thought it was "normal" with Build 170 and was getting looked at.

Howard

Did you see this part? We are trying to find a set of actions that can reliably reproduce that situation. If you know of any way to cause that error to occur reliably, please let us know at support@efilive.com
Right now, I can't reliably reproduce the problem here. If you can make it happen reliably, every time, please let me (paul@efilive.com) know the exact steps to cause it to happen.

I need some help from customers that are seeing this problem happen regularly.
If I can't make it happen here, I can't fix it.
Regards
Paul

[Boost]

Well I downloaded the new V8 and seems to work great, I already sent two E83 files. The only issue is that when you click on Read, the Go button on the bottom is blocked by a scroll bar but this may be just an issue on my screen. However, the V7 update doesn't extract from the setup file. It extracts way too quick and then it's nowhere to be found. So I will try downloading that one again.

[Redline Motorsports]

Did you see this part? We are trying to find a set of actions that can reliably reproduce that situation. If you know of any way to cause that error to occur reliably, please let us know at support@efilive.com
Right now, I can't reliably reproduce the problem here. If you can make it happen reliably, every time, please let me (paul@efilive.com) know the exact steps to cause it to happen.

I need some help from customers that are seeing this problem happen regularly.
If I can't make it happen here, I can't fix it.
Regards
Paul

I did see that part......I was just wondering if any solutions where found.......

[swingtan]

Had a bit of a strange one today. Last weekend I was logging with an Innovate with serial I/O and all was OK. Then I swapped back to my Techedge and was gettign very weird data in my logs. The process I used was...

1. Plugged V2 into laptop via the serial port.
2. Used V8 BBL to set the V2 serial port to Innovate WB.
3. Logged data via BBL. All was OK.
4. Swapped the V2 back to my car and plugged in the TechEdge.
5. Forgot to swap the V2 back to "TEdge 2.0", so the first log had bad WB data.
6. Swapped the WB type back to "Tedge 2.0" via the menu options.
7. Logged a couple more tunes and the WB data was still off. Not as bad as when it was set to Innovate, but still useless.
8. Upgraded to this version of firmware, which reset the V2 and it's all back to normal.

I don't think it was the firmware that fixed it, more likely just the reset. Note the details on the attached image, EQR = 1.016 but it says AFR = 9.15:1. This is with the car idling in CL....



It's not an ongoing issue, I just wanted to bring it up in case someone else sees this. I don't think people are swapping WB types that often and I don't have access to the Innovate to try it again. If I get the chance, I'll try a few tests though.

Simon.

[Boost]

Happy to report that the issue with my V7 extracting has been resolved by re-downloading the setup file with a better connection.