Downloading now!
Printable View
Downloading now!
the version you are downloading has a serious bug in it...
I'll have to play with it some more when connected to a car
The first thing I've notice that I don't really like is the lack of a "Primary Table" field when setting up histograms. I used to use this to quickly get units/break points setup to match up with what I need in VCM Editor.
Is there a way to do this that I'm just missing?
Yes that version crashed while I was connected using it.
Do we need to call the Orkin man?
Anybody else get this in 2.25 trying to flash?
http://i.imgur.com/gN4LNi5.png
I've already sent an email to support, just thought I would post up here as well. 2.24 doesn't seem to have this issue.
I couldn't get it to flash on mine earlier either.. worked fine when I went back to 2.24 though
(I don't recall that particular error though)
Sorry, it will be a day or two before I can get more info
Going from memory.. sometimes it gave me an error about not connecting to the vehicle, then sometimes it would get a little further then eventually give me some kind of time out error about the ECM not responding. I reset the interface / switched car on and off several times trying to get it to work
I then switched back to 2.24 and it worked first try. I tried to use both the scanner and editor, neither worked
Sorry, I know from an engineering level that isn't going to help much. I'll get some screenshots in a day or two when I'm back at the car
Are there any log files I can send you to help once I am back at the car?
(it was def. NOT the data integrity error the previous user had)
This new firmware breaks the MPVI standalone data logging functionality.
We're working on a solution. It will likely require another firmware upgrade.
I always forget to click disconnect in the scanner...and I've grown very used to remembering right before I write calibration only in the tuner...and then watching it say required security delay not expired and waiting 10 seconds...so I've been pleasantly surprised to see this doesn't seem to happen to me anymore since the firmware update and using 2.24.
For the people getting errors working on Gen 4 GM V8 cars using 2.25...why not just use 2.24?
because using 2.24 isn't going to help improve 2.25.
2.24 is history. use it if needed.
Same here, Writing fails, scanner crashes.