Quote:
|
Originally Posted by Marc-x
As I wrote in my other thread, the problem is partially fixed now.
|
How? what did you do to fix it?
Quote:
|
Originally Posted by Marc-x
Is it possible to enable the "nagscreen" in European mode?
|
No.
Quote:
|
Originally Posted by Marc-x
If you repeatedly use "READ NAV" the read telematics data occationally seems to move arround. That is the "SMSC Centre" number sometimes become the "SMS Number" or vice versa. (I don't recall att the moment EXACTLY which way arround it went, but I noticed the problem. Also "Navcoder" often gives an error message saying something like "error verifying SMSC / SMS Number" (or something similar with that meaning.)
|
If you do things too quickly, you can confuse the information.
This is because everything on the databaus is serial, and there is no way no tie a response to a command.
If you issue a 3 x commands, you will get 3 x responses.
But if you send 3 x commands straight after one another, you won't know which response belongs to which command.
Also, a very busy databus makes it even harder.
To reduce this problem:
1. Ensure the timeout value is set to something like 1000 ms
2. Wait for one command to timeout before you send another, otherwise confusion will result
3. Switch off the radio - it reduces the databus traffic enormously and thus makes bus communication more reliable.
4. Leave ignition at Pos1, not Pos2. This also reduces the data traffic.
And as for NavCoder error messages, I need a logfile, plus you need to tell me what car and what interface you have, and what you were doing when the error happened.
Regards, Jochen