Sorry I haven’t got back to you sooner. I was unable to keep a connection to my laptop. It would connect at first and if I didn’t touch anything else it would stay connected. If I tried to change to different area’s of Torque it would do it’s disconnection dance. I recorded some debug lines for you. Again if hooked back up on the USB cable everything worked great. Here are the debug lines:
I JUST REALIZED THAT THE 2 ATTEMPTS TO CONNECT TO MY LAPTOP WAS WITH THE PROGRAM “OBDwiz” PROGRAM THAT CAME WITH THE ADAPTER. DOES THIS MAKE THE INFO USELESS. PLEASE LET ME KNOW IF THERE IS A WAY TO USE “TORQUE” ON THE LAPTOP IF NEEDED.
This is the bluetooth attempt to my laptop:
Version: 2.11.2.217
Product: OBDwiz
Opening communications: COM6, 115200
Port Open
Flushing communications buffer
?: []
ATZ: [->Timeout]
System.TimeoutException – The operation has timed out.
Command timed out
Opening communications: COM6, 115200
Port Open
Flushing communications buffer
?: []
ATZ: [->Timeout]
System.TimeoutException – The operation has timed out.
Command timed out
ATI: [->Timeout]
System.TimeoutException – The write timed out.
ATI: [->Timeout]
System.TimeoutException – The write timed out.
ATI: [->Timeout]
System.TimeoutException – The write timed out.
ATI: [->Timeout]
System.TimeoutException – The write timed out.
ATI: [->Timeout]
System.TimeoutException – The operation has timed out.
ATI: [->Timeout]
System.TimeoutException – The operation has timed out.
ATI: [->Timeout]
System.TimeoutException – The operation has timed out.
ATI: [->Timeout]
System.TimeoutException – The operation has timed out.
And just for the heck of it, this is when it successfully hooks up with my laptop via USB:
Version: 2.11.2.217
Product: OBDwiz
Opening communications: COM6, 115200
Port Open
Flushing communications buffer
?: [->Timeout]
System.TimeoutException – The operation has timed out.
Command timed out
Opening communications: COM6, 115200
Port Open
Flushing communications buffer
?: [->Timeout]
System.TimeoutException – The operation has timed out.
Command timed out
Above was when I was switching the software over from bluetooth to USB. Below is a few seconds sample when it connected to the adapter by USB
ELM327 v1.3a]
Interface connected
ATE0: [ATE0
OK]
ATL0: [OK]
STI: [STN1100 v2.2.2]
ATRV: [11.7V]
Trying Protocol: SAE J1850 PWM (41.6 Kbaud)
ATSP 1: [OK]
01 00: [NO DATA]
Trying Protocol: SAE J1850 VPW (10.4 Kbaud)
ATSP 2: [OK]
01 00: [NO DATA]
Trying Protocol: ISO 9141-2 (5 baud init, 10.4 Kbaud)
ATSP 3: [OK]
01 00: [BUS INIT: …OK
41 00 BE 3F F8 00 ]
Protocol detected: ISO 9141-2 (5 baud init, 10.4 Kbaud)
ATH1: [OK]
01 00: [48 6B 01 41 00 BE 3F F8 00 EA ]
Detected PIDs:
ECU: 01
0x00 – SupportedPIDs0
0x01 – MonitorStatus
0x03 – FuelSystemStatus
0x04 – EngineLoad
0x05 – EngineCoolantTemp
0x06 – ShortTermFuelTrimBank1
0x07 – LongTermFuelTrimBank1
0x0B – IntakeManifoldPressure
0x0C – EngineRPM
0x0D – VehicleSpeed
0x0E – TimingAdvance
0x0F – IntakeAirTemperature
0x10 – MassAirFlowRate
0x11 – ThrottlePosition
0x12 – SecondaryAirStatus
0x13 – OxygenSensorsPresent
0x14 – OxygenSensorDataBank1Sensor1
0x15 – OxygenSensorDataBank1Sensor2
01 01: [48 6B 01 41 01 80 07 6D 00 EA ]
09 02: [NO DATA]
01 00: [48 6B 01 41 00 BE 3F F8 00 EA ]
01 0D: [48 6B 01 41 0D 00 02 ]
STMFR: [ScanTool.net LLC]
STI: [STN1100 v2.2.2]
01 10: [48 6B 01 41 10 00 00 05 ]
STDI: [OBDLink r2.7]
01 05: [48 6B 01 41 05 30 2A ]
STSN: [110010033841]
01 0C: [48 6B 01 41 0C 00 00 01 ]
01 03: [48 6B 01 41 03 01 00 F9 ]
01 00: [48 6B 01 41 00 BE 3F F8 00 EA ]
01 04: [48 6B 01 41 04 00 F9 ]
01 0D: [48 6B 01 41 0D 00 02 ]
01 10: [48 6B 01 41 10 00 00 05 ]
01 0C: [48 6B 01 41 0C 00 00 01 ]
01 00: [48 6B 01 41 00 BE 3F F8 00 EA ]
|