Duh , thanks that was it , how do you say moron , oh yeah like that !Quote:
Originally Posted by Hyper99
Did not dawn on me to set the COMs , I was like the V2 has only one RJ45 connection why two COMs , must be for Analog .
Many thanks .
Printable View
Duh , thanks that was it , how do you say moron , oh yeah like that !Quote:
Originally Posted by Hyper99
Did not dawn on me to set the COMs , I was like the V2 has only one RJ45 connection why two COMs , must be for Analog .
Many thanks .
No problem
I remembered it because I missed it the first time around:doh2:
Glad I could help
Make sure you turn DFCO off when logging bens.Quote:
Originally Posted by Black02SS
Here is a thought , make the default setting be WBO2 for COM1 and COM2 , I can see the need for a selectable WBO2 controller , i,e, Innovate , PLX etc ... , but default the COMs to a on state .:doh:Quote:
Originally Posted by Hyper99
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)
I have all the above symptoms also except for the LLY auto not working. I use LLY auto for my logs. Do you see any weird frames when playing back your log on the PC?Quote:
Originally Posted by Lennart
I did have one log file that was filled with notes rather than data.Quote:
Originally Posted by lakingslayer
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?Quote:
Originally Posted by lakingslayer
Send to [email protected]
Thanks
Paul
Yes, they will be defaulted to WBO2 in the "public" release.Quote:
Originally Posted by tunedbyGM
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