Ds3 Crossback OBD connection issue
,
I am opening this ticket to report a bug in the OBD connection initialization process with the DS3 Crossback profile.
When trying to test the PIDs with the vehicle profile set to "DS3 Crossback", the initialization fails systematically with the following error in the logs:
Erreur: could not get commands for type init from [object Object] ds:3crossback:20:48
It seems like the application is trying to fetch custom initialization commands from your servers for this specific vehicle profile, but it receives a poorly serialized JavaScript object instead of a text string, which crashes the initialization process.
Even though the "Custom init commands" field in my OBD PID Editor is completely empty (0), the app still tries to look for this object.
As a temporary workaround, switching the vehicle profile to a Peugeot e-208 completely solves the issue and the OBD connection goes through perfectly, which confirms that the hardware is working fine and the bug is strictly related to the DS3 Crossback profile configuration on your backend.
Could you please check the data or the initialization script associated with the ds:3crossback profile?
Thank you for your help!
Best regards,
M cuaz
- Where does this happen?
- ABRP version number (found at bottom of settings menu)
Log in to comment and vote
Comments1
Jun 24
PinnedHello @ABRP User #2815462,
We do not have an option for the DS 3 Crossback currently as you can see in this website here when searching for your vehicle:
https://abetterrouteplanner.com/compare/livedata/
Is it in the PID editor that you have tried testing your PIDs?