Paul,
If I haven't already mentioned this:
- on V2 display, SW2 is not mentioned;
- on scantool PIDs tab, TEMP2 is disabled.
Printable View
Paul,
If I haven't already mentioned this:
- on V2 display, SW2 is not mentioned;
- on scantool PIDs tab, TEMP2 is disabled.
Paul, BALRCYL1 is missing from the LLY txt file, and I noticed it didn't appear on the V2 (but 2-8 are there). Just FYI.
If I connect V2 to vehicle with key off, V2 powers on;
then when I turn key on, V2 does not detect any controllers...
how do I get it to detect controllers (other than re-connecting it...?)...?
Otherwise the sequence is to connect V2 to vehicle after key on.
Build 46 scantool seems to only do one level of calc pids in calc_pids.txt...
i.e. it displays only the calc_pids that do not depend on other calc pids.
Is Serial WB Data pass thru working?`
The V2 doesn't reconnect to the Module it was logging when you start the vehicle again; IIRC, one of the earlier releases did. Also, if paused, it won't unpause once it has lost contact with the module.
This is weird... it does this on my PC at work... and on my PC at home it works correctly. :nixweiss:Quote:
Originally Posted by joecar
I forgot to end a log before removing the V2 from the vehicle... so now I can't view that particular log using the scantool, is there a way to "terminate" the log file so it can be viewed...?
Profound! Glad you could take the time out of our busy day to offer your input on issues found in the Beta during your testing.Quote:
Originally Posted by 9secVette
Well so far what I have found is that PIDs for the pass thru are always invalid but this time you can log them and it will transfer data correctly.
The software hangs a lot with "conflicting" drivers (RR+v2) and when the software hangs you simply have to shut down the pc the hard way most of the time because you cannot kill the process... I was using a different laptop today and it was a real pill until I found the drivers it liked, somehow they are different for different computers.