You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I got a Polo Volkswagen car. And trying to test this libs with OBD bluetooth connector. But I got message "Invalid or short line '83' found". No valid data come out. I don't know how to handle with this error message. The protocol this car using is OBD2VehicleProtocolKWP2000_5KBPS with implementation for this protocol is [LTOBD2ProtocolISO14230_4 protocol].
Here is some log about that:
[LTOBD2AdapterInternalCommand didCompleteResponse:protocol:protocolType:] (LTOBD2Adapter.m:58) <LTOBD2PID_VEHICLE_SPEED_0D:0x282bf60a0 = '010D'> complete [487 ms] => '83 - F1 - 1A - 41 - 0D - 00 - DC'
-[LTOBD2ProtocolISO14230_4 decode:originatingCommand:] (LTOBD2ProtocolISO14230_4.m:55) Invalid or short line '83' found
-[LTOBD2ProtocolISO14230_4 decode:originatingCommand:] (LTOBD2ProtocolISO14230_4.m:55) Invalid or short line 'F1' found
-[LTOBD2ProtocolISO14230_4 decode:originatingCommand:] (LTOBD2ProtocolISO14230_4.m:55) Invalid or short line '1A' found
-[LTOBD2ProtocolISO14230_4 decode:originatingCommand:] (LTOBD2ProtocolISO14230_4.m:55) Invalid or short line '41' found
-[LTOBD2ProtocolISO14230_4 decode:originatingCommand:] (LTOBD2ProtocolISO14230_4.m:55) Invalid or short line '0D' found
-[LTOBD2ProtocolISO14230_4 decode:originatingCommand:] (LTOBD2ProtocolISO14230_4.m:55) Invalid or short line '00' found
-[LTOBD2ProtocolISO14230_4 decode:originatingCommand:] (LTOBD2ProtocolISO14230_4.m:55) Invalid or short line 'DC' found
Hi Mr.Mickeyl
I got a Polo Volkswagen car. And trying to test this libs with OBD bluetooth connector. But I got message "Invalid or short line '83' found". No valid data come out. I don't know how to handle with this error message. The protocol this car using is OBD2VehicleProtocolKWP2000_5KBPS with implementation for this protocol is [LTOBD2ProtocolISO14230_4 protocol].
Here is some log about that:
[LTOBD2AdapterInternalCommand didCompleteResponse:protocol:protocolType:] (LTOBD2Adapter.m:58) <LTOBD2PID_VEHICLE_SPEED_0D:0x282bf60a0 = '010D'> complete [487 ms] => '83 - F1 - 1A - 41 - 0D - 00 - DC'
-[LTOBD2ProtocolISO14230_4 decode:originatingCommand:] (LTOBD2ProtocolISO14230_4.m:55) Invalid or short line '83' found
-[LTOBD2ProtocolISO14230_4 decode:originatingCommand:] (LTOBD2ProtocolISO14230_4.m:55) Invalid or short line 'F1' found
-[LTOBD2ProtocolISO14230_4 decode:originatingCommand:] (LTOBD2ProtocolISO14230_4.m:55) Invalid or short line '1A' found
-[LTOBD2ProtocolISO14230_4 decode:originatingCommand:] (LTOBD2ProtocolISO14230_4.m:55) Invalid or short line '41' found
-[LTOBD2ProtocolISO14230_4 decode:originatingCommand:] (LTOBD2ProtocolISO14230_4.m:55) Invalid or short line '0D' found
-[LTOBD2ProtocolISO14230_4 decode:originatingCommand:] (LTOBD2ProtocolISO14230_4.m:55) Invalid or short line '00' found
-[LTOBD2ProtocolISO14230_4 decode:originatingCommand:] (LTOBD2ProtocolISO14230_4.m:55) Invalid or short line 'DC' found
Command Response
purpose: Vehicle Speed
formattedResponse: No data
rawResponse: ["83", "F1", "1A", "41", "0D", "00", "DC"]
rawCommand: false
commandString: 010D
protocol: OBD2VehicleProtocol(rawValue: 4)
cookedResponse: [:]
failureResponse: [:]
answer: true
validAnswer: false
CAN: false
The text was updated successfully, but these errors were encountered: