|
||||||||
| Xoutpost server transfer and maintenance is occurring.... |
| Xoutpost is currently undergoing a planned server migration.... stay tuned for new developments.... sincerely, the management |
![]() |
|
|
LinkBack | Thread Tools | Display Modes |
|
|
|
#1
|
|||
|
|||
|
Quote:
Hence setting Region=USA may disable the TMC options in the nav. I've never tried Region=USA, so don't have any experience. First thing to do is set Region back to Europe As for assist, did you check the box in NavCoder? Quote:
Set your Region back to Europe. Regardless of what happened, NavCoder always records the current configuration in the nav before it changes anything. To be sure, you should make a backup of the Navcoder.log file, and keep it. If you are still stuck, you can send me the log file and I can look at the old original settings. Regards, Jochen |
|
#2
|
|||
|
|||
|
Hi Jochen.
As I wrote in my other thread, the problem is partially fixed now. I also thougt about the USA config causing the problem. If USA doesn't use TMC then this is probably the case. Will try to switch back to USA and see what happens. Is it possible to enable the "nagscreen" in European mode? It is pretty funny when displaying a customized text... And yes, I checked "Assist" -option in Navcoder together with "Auto Emergency call" I have noticed some odd behaviour in Navcoder: 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.) Will try some more in a little while and post back my findings! ///M |
|
#3
|
|||
|
|||
|
Quote:
Quote:
Quote:
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 |
|
#4
|
|||
|
|||
|
Quote:
ASSIST still missing, but haven't set the telematics settings yet. Upgraded to my "Custom" ver 29.1 and verified that everyting works. (Still in European mode). Everything works fine, except Assist, but still haven't fixed the telematics settings. Will try some more with Navcoder this afternoon and post my findings and some log snippets if there is some strange behaviour. Car as in my signature. Interface is homebuilt from schematics in your release, heavily shielded, installed permanently in trunk, and attached to the CD-changer cable loom. The cable to the computer is also shielded and connects to the car with a high quality "medical" type locking connector... Kind regards ///M
__________________
BMW e46 330d Individual -02 Every possible option installed. Nav upgraded to Mk IV. |
|
#5
|
|||
|
|||
|
Quote:
Now you know the difference between different region settings. Quote:
When a new version of software is loaded, the nav often resets to factory-default empty settings. which means vehicle type etc is emtpy, and Assist is switched off. All you have to do is code the nav properly. Very simple. Jochen (in Bern, Switzerland) |
![]() |
| Bookmarks |
|
|
|
|