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'm currently trying to request some non-standard OBD Modes/Service IDs using the Custom Command feature, the "OBDCommand" object.
I'd like to be able to get the response back I get from the vehicle without any sort of decoding, however this does not seem to be possible. Using a decoder function within the OBDCommand object that just returns the same input, the only output I get when I query the custom command is "<obd.OBDResponse.OBDResponse at 0x1fc7ac58130>", which I assume is just the memory address of the object. However, if I enable debugging I can see that I am actually able to see the byte array response from the vehicle, but since this is not a part of the actual output I am unable to manipulate it further.
The text was updated successfully, but these errors were encountered:
peszaber
changed the title
Passing Through Raw CAN Info In Custom Commands
Passing Through Raw Vehicle Response Info In Custom Commands
Feb 17, 2023
I'm currently trying to request some non-standard OBD Modes/Service IDs using the Custom Command feature, the "OBDCommand" object.
I'd like to be able to get the response back I get from the vehicle without any sort of decoding, however this does not seem to be possible. Using a decoder function within the OBDCommand object that just returns the same input, the only output I get when I query the custom command is "<obd.OBDResponse.OBDResponse at 0x1fc7ac58130>", which I assume is just the memory address of the object. However, if I enable debugging I can see that I am actually able to see the byte array response from the vehicle, but since this is not a part of the actual output I am unable to manipulate it further.
The text was updated successfully, but these errors were encountered: