Have got the entire main setup now fully configured and working.
Vin,Serial,freeze frames, faults and PIDs available will all be detected on connection (On by default). This can be turned off for speed, or for unsupported cars.
I currently only did the CAN section as this seemed to be the harder part.. vpw is just alot easier to do. Most of the functions can be easily applied for VPW so 99% of the work is completed there.

- update1.PNG (65.83 KiB) Viewed 3900 times
So whats left to do?!? Well before the next release, I would like to complete:
-fully functioning engine data section for VPW
-Startup connection info for VPW as done on CAN
-Receive/Transmit filter working on VPW for raw logging
-Ensure Iv captured all possible fault codes for both LS1 and VZ V6 ecus
Also, I believe Iv managed to be able to detect Bluetooth devices. So.. hopefully.. if a bluetooth device is used, the application *should* automatically disable the fast baud update to prevent the bluetooth ELM from going spastic.
I will need some brave soles test that out, it wont need to be connected to the car, just need a variety of bluetooth devices connected to the program to see if I have solved that annoying issue. I still hate bluetooth devices...and could easily solve this issue by not updating the baud rate.. but I rather maintain speed and reliability with the usb versions.