Hello Mark and thank you for the post.
I have been experimenting today with the ELM 327 Bluetooth device and I have to say I have managed to connect to the vehicle and obtain engine and road speed data, but it was not as simple as it may sound.
I do like the idea of a Bluetooth device for OBDII data capture as it removes cables around the pedal box area which is a blessing in itself.
I have been using a Windows 8.1 Laptop with PicoScope version 6.11.5 (Beta)
Could you confirm you are using the same beta version?
Could you confirm the ELM device to be installed correctly along with the relevant driver in the device manager of your PC?
Could you remove any devices that are using COM Ports lower than COM Port 6. (E.g. Other Bluetooth devices)
If all the above are OK, could you open the NVH software and enable OBD Logging
(See image below)
Could you then run through the connection procedure as you have mentioned above to generate the identical symptom?
Once you have confirmed the OBD II connection error could you close the NVH program and PD?
This will generate a trace file containing detailed information about the connection to the OBD socket and enable the engineers to assist with an explanation.
The trace file is located here at:
Windows Vista/7/8: C:\Users\<User name>\AppData\Local\Pico Technology\Pico Diagnostics
With the Pico Diagnostics folder open, you will find a larger folder identified by a long alpha numeric title (E.g. a6f37be2-ef55-40fe-914d-ddbe5251)
Open the above alpha numeric folder and locate the “trace xml” file for the last NVH connection attempt. (Identified by the date and time alongside)
Could you then email this file across to me here at firstname.lastname@example.org
I hope this information is of some help, take care.....Steve