As for the CAN distance value, the value is indeed coming in according to the logs, but the device is filtering it out right now (don't show this screenshot to the client):
​
​

​
"err cnt" needs to reach 1000 until the new value will be updated on the mileage parameter. This will happen eventually and this always happens when a significant change in a CAN parameter is noticed, it is filtered for the first 1000 reads of it.
​
This is how our devices always worked up to the 4th generation and there is no way going around this step, old data will be saved in the device and then compared until it reaches the 1000 count, the ID of the parameter is shown in the log as well (114 is CAN high resolution distance in the FMIO document). You can always see these entries with the "CAN.val.filter" keyword in the logs. If you're interested in checking this, I've attached the log here.
​
Regardless, if there will be questions about mileage being shown incorrectly after it starts showing, then simply mention that we do not support this vehicle with Pro4 devices, HCV5 or Pro5 devices need to be used.
​
​So overall, everything seems to work from what I can see, it should take some time until the value is updated but installing device into different vehicle will always result in this behaviour.
​
Please give a basic explanation of this to the client, tell the client that the data should come in later (the vehicle needs to drive a decent amount first) and it should be fine.