Ok course, everything can help.
Send it to applagapp@gmail.com
Thanks!
BETA test for 29bit init protocol
-
chameleoncyber
- Posts: 2
- Joined: Mon Feb 23, 2026 10:51 am
Re: BETA test for 29bit init protocol
Hello,
Thank you for this excellent app. This is my first time owning a diesel vehicle, and managing the DPF has been a bit challenging.
My car is a Passat B9 (2026 model year, likely manufactured around November 2025).
The engine code is DXPB?, and I have selected Group 97.
When the app starts and connects to the Bluetooth adapter(=ODBLink MX+), an error message pops up.
If I close the error message, the data itself can be retrieved without any issues.
Looking through past threads, it seems that this error message for Group 97 was supposed to be suppressed during the app’s development.
The update notes on the Google Play Store also mention improvements related to this in the latest version.
However, the error message I see every time does not appear to be controlled by the app.
I’ve attached the log that corresponds to the error message.
Is it possible to suppress this message?
**INIT LOG**
4154505046464F4646I2LATPPFFOFF\rOK\r\r>Y
41545AI2LATZ\r\r\rELM327 v1.4b\r\r>Y
415444I2LATD\rOK\r\r>Y
41545043I2LATPC\rOK\r\r>Y
41544530I2LATE0\rOK\r\r>Y
41545330I2LOK\r\r>Y
41544C30I2LOK\r\r>Y
4154415431I2LOK\r\r>Y
41544D30I2LOK\r\r>Y
41544831I2LOK\r\r>Y
4154535036I2LOK\r\r>Y
30313030G1HNO DATA\r\r>X
30313030G1HNO DATA\r\r>X
30313030G1HNO DATA\r\r>X
30313030G1HNO DATA\r\r>X
4154535037I2LOK\r\r>Y
415443503137G1HOK\r\r>X
41545348464330303736G1HOK\r\r>X
41544352413137464530303736G1HOK\r\r>X
4154464353483137464330303736G1HOK\r\r>X
415446435344333030303030G1HOK\r\r>X
41544643534D31G1HOK\r\r>X
4154414CG1HOK\r\r>X
31303033M3NNO DATA\r\r>Z
31303033M3NNO DATA\r\r>Z
31303033M3NNO DATA\r\r>Z
31303033M3NNO DATA\r\r>Z
323246313837M3N17FE0076100E62F18730354C\r17FE0076213930363032324E\r17FE00762250AAAAAAAAAAAA\r\r>Z
323246313839M3N17FE00760762F18934343532\r\r>Z
323246313931M3N17FE0076100E62F19130354C\r17FE00762139303733303941\r17FE00762248AAAAAAAAAAAA\r\r>Z
323246314144M3N17FE00760762F1AD44584E42\r\r>Z
323246313937M3N17FE0076101062F197523420\r17FE007621322E306C205444\r17FE007622492020AAAAAAAA\r\r>Z
30393032M3N17FE00761014490201575657\r17FE0076215A5A5A434A3354\r17FE00762244303230343234\r\r>Z
323246383032M3N17FE0076101562F802015756\r17FE007621575A5A5A434A33\r17FE00762254443032303432\r17FE00762334AAAAAAAAAAAA\r\r>Z******************************
Thank you for this excellent app. This is my first time owning a diesel vehicle, and managing the DPF has been a bit challenging.
My car is a Passat B9 (2026 model year, likely manufactured around November 2025).
The engine code is DXPB?, and I have selected Group 97.
When the app starts and connects to the Bluetooth adapter(=ODBLink MX+), an error message pops up.
If I close the error message, the data itself can be retrieved without any issues.
Looking through past threads, it seems that this error message for Group 97 was supposed to be suppressed during the app’s development.
The update notes on the Google Play Store also mention improvements related to this in the latest version.
However, the error message I see every time does not appear to be controlled by the app.
I’ve attached the log that corresponds to the error message.
Is it possible to suppress this message?
**INIT LOG**
4154505046464F4646I2LATPPFFOFF\rOK\r\r>Y
41545AI2LATZ\r\r\rELM327 v1.4b\r\r>Y
415444I2LATD\rOK\r\r>Y
41545043I2LATPC\rOK\r\r>Y
41544530I2LATE0\rOK\r\r>Y
41545330I2LOK\r\r>Y
41544C30I2LOK\r\r>Y
4154415431I2LOK\r\r>Y
41544D30I2LOK\r\r>Y
41544831I2LOK\r\r>Y
4154535036I2LOK\r\r>Y
30313030G1HNO DATA\r\r>X
30313030G1HNO DATA\r\r>X
30313030G1HNO DATA\r\r>X
30313030G1HNO DATA\r\r>X
4154535037I2LOK\r\r>Y
415443503137G1HOK\r\r>X
41545348464330303736G1HOK\r\r>X
41544352413137464530303736G1HOK\r\r>X
4154464353483137464330303736G1HOK\r\r>X
415446435344333030303030G1HOK\r\r>X
41544643534D31G1HOK\r\r>X
4154414CG1HOK\r\r>X
31303033M3NNO DATA\r\r>Z
31303033M3NNO DATA\r\r>Z
31303033M3NNO DATA\r\r>Z
31303033M3NNO DATA\r\r>Z
323246313837M3N17FE0076100E62F18730354C\r17FE0076213930363032324E\r17FE00762250AAAAAAAAAAAA\r\r>Z
323246313839M3N17FE00760762F18934343532\r\r>Z
323246313931M3N17FE0076100E62F19130354C\r17FE00762139303733303941\r17FE00762248AAAAAAAAAAAA\r\r>Z
323246314144M3N17FE00760762F1AD44584E42\r\r>Z
323246313937M3N17FE0076101062F197523420\r17FE007621322E306C205444\r17FE007622492020AAAAAAAA\r\r>Z
30393032M3N17FE00761014490201575657\r17FE0076215A5A5A434A3354\r17FE00762244303230343234\r\r>Z
323246383032M3N17FE0076101562F802015756\r17FE007621575A5A5A434A33\r17FE00762254443032303432\r17FE00762334AAAAAAAAAAAA\r\r>Z******************************
Re: BETA test for 29bit init protocol
You're right, it should have been removed in the latest release, but I modified the code incorrectly.
Now I'm working on some improvement in the initialization routine to make the engine group selection fully automated also for newer 29-bit init engines like yours. The new release will solve also the unwanted error message issue, you just have to wait a little.
Thanks for the positive feedback for your engine.
Now I'm working on some improvement in the initialization routine to make the engine group selection fully automated also for newer 29-bit init engines like yours. The new release will solve also the unwanted error message issue, you just have to wait a little.
Thanks for the positive feedback for your engine.
-
chameleoncyber
- Posts: 2
- Joined: Mon Feb 23, 2026 10:51 am
Re: BETA test for 29bit init protocol
Thank you very much. I appreciate your wonderful work!