NavCoder v2.8.15 Released 24 December 2009
 

v2.8.15 released 24 December 2009 - Get it here:

NavCoder Website

(NavCoder website available in multiple languages)

Changes:
2.8.15 24 December 2009
Merry Christmas!
Fixed some PT language errors
Fixed some LT language errors
Fixed problem where the From/To filter didn't work correctly when reading log files (was OK with live data)
Fixed problem where coding of TCU emergency number didn't clear all previous data
Fixed problem where update info wasn't being read correctly if verInfo file had >1 line
Added Catalan CA to the Setup program
Added decode of commands 0x86 and 0x87 (Aux Heater status)
Added extra debugging info to Updates routine to help find problem on LT machine
Removed some test code


2.8.8 14 December 2009
Fixed problem where TEL dialog was too small (only if user used beta 2.7.88 - .129)
Fixed RTE13 error when retrieving update file version (failed if version info was wrong)
Fixed COM port message position problem on main GUI
Fixed bug where NavCoder would read TCU identity twice
Fixed bug where NavCoder would not show TCU emergency number correctly sometimes
Fixed some FR French language errors
Fixed lots of LT language errors

2.8.0 12 December 2009
Added better Win7 and Vista support through better font use
Added Catalan language CA
Added Lithuanian language LT
Added Windows build version & language to Logfile and About dialog
Added ignition-on check to make sure user has ign on when reading / coding devices
Added decode of Diagnostic error 0xB2 "Diagnostic command not supported / Wrong command"
Added support for TCU ECE Ci04
Added download speed and remaining time indicator to downloading bargraph
Added TCU success message when successfully coded TCU
Added TCU language coding functionality
Added and verified TCU-GSM coding functionality
Added activation of activity LED in simulation mode
Added false positive checker to ibus parser
Added download speed when downloading updates
Added Verbose Debug Mode (-dd switch) to assist in debugging
Added TCU-GSM Reading (same as TCU-US at the moment)
Added decoding of 0x05 Backlight Control (for rear monitor)
Added decoding of Aux Heating LED
Added auto usage of Windows default font for correct display on XP, Vista and Win7
Added View Change History file to help menu
Added saving/restore of all windows (size + position)
Added PDC Test function
Changed (Updated) list of supported US-TCU units
Changed (Re-wrote) the ibus COM-buffer parser and fixed a bug
Changed ibus activity LED to 100ms illumination (shorter)
Changed ibus msg timeout to default 300ms
Changed idle-time-before-Tx to 10ms (was 50ms)
Changed many dialog sizes to cater for larger font in Vista / Win7
Changed Show File dialogs (Readme.txt etc) to show just file name in frame caption
Changed Ibus Message Test dialog to be resizable and to auto-size (wip)
Changed behaviour when switching languages: now changes immediately, restart no longer needed
Changed Options dialog to autosize to font size, regardless of language
Changed Options dialog Close button to OK and Cancel to be Windows consistant
Changed DebugMode behaviour: BetaVersion always has DebugMode on, but a -d switch can now turn it off
Changed email templates
Changed many language texts
Fixed bugs in many language files
Fixed bug where no error message displayed when starting with no free Com ports
Fixed bug where TEL "control Unit Type" was always in English
Fixed bug where TEL control unit type dropdown list was always in English
Fixed bug where ULF VR status was not being read with "Read ULF"
Fixed bug where ULF VR was not coded (introduced when TCU added)
Fixed bug where the not-registered nag screen showed %%
Fixed bug where NavCoder crashed when starting on machine with no internet connection
Fixed bug on Win2K systems where MsgBox Yes/No was not displayed in resource text
Fixed bug with error 35756 when no Internet connection exists


2.7.25 25 September 2009
Added "Add Comment to Log File" capability (Tools menu)
Added extra decoding of 0x3A "Recirculating air control" button on the steering wheel
Added extra decoding of 0x72 "ChkCtrl Remote Central Locking"
Added Translation of "unknown" in device selection dropdown list
Added disply of "Adr_XX" and "Cmd_XX" for unknown DIA commands
Added ASCII display of DIA data
Added new ChangeHistory.txt file and removed change history from ReadMe file
Fixed detection of LCMs with CI<14 to appear as LCM_I
Fixed LCM with CI17 from type LCM1 to LCM2
Fixed display of "ü" for IKE CCM messages (was appearing as "¦")
Fixed RunTimeError when no lng directory found
Updated all OCX files to 6.1.98.16 (OCX date 24.03.09)
Reduced size of Email body by removing "NavCoder language" text


2.7.0 18 July 2009
Added installer packager with .exe distribution file (finally!)
Modified auto-update and auto-install function to work with zip and exe files
Added AND/OR function to device filter in main ibus window
Fixed bug where primary-sub languages were being detected as primary lng only eg EN-US
Fixed spelling and updated text in many language files
Changed CDC message 00 00 to Status_Request
Updated Readme file (removed OCX references)


v2.6.68 27 June 2009
Added DRL
Added BG and EL languages
Fixed bug in Code TV preventing reading of TV coding


v2.6.60 07 June 2009
Added Scan - Vehicle ID, which displays VIN numbers from IKE, LKM and NAVE
Added disabling of Code Output Mode controls for Mk1/Mk2 (not supported by these navs)
Added disabling of phone numbers for Mk1. Mk2, Mk3 navs (not supported by these navs)
Fixed bug where Progress Dialog shows "Form1" as caption
Fixed bug where Mk2 nav was showing verification error after coding


v2.6.51 03 June 2009
Fixed Telephone dialog - I had mistakenly included a test version in the reelase version of NavCoder.


v2.6.50 02 June 2009
Added scheduled auto update feature to regularly check for updates upon startup. Interval can be
set in Tools Options dialog, default is 14 days.
Improved check for Updates routine.
Improved pasting of text from clipboard to ibus msg test (now ignores CR and LF and TAB)
Improved size of Progress Bar to show all text
Updated lots of LNG files, especially FR and NL
Corrected many formatting errors in LNG files
Fixed bug where downloading updates would crash when cancelled


v2.6.40 04 May 2009
Fixed bug where Set Distance was not properly decoded
Fixed bug where Checksum Error was appearing in the ibus log
Fixed bug where Cd changer control (00 00) was not decoded properly
Added all known language files to zip file


v2.6.30 28 March 2009
Fixed bug where NavCoder would not start on Win98 machine
Fixed bug where Online Updates would cause Runtime Error if no internet connected
Fixed bug where %% was shown in title of restart message when changing languages
Added link to elektronik-idee BMW interfaces eBay Shop in Help menu
Adjusted timestamp to show milliseconds
Adjusted ibus transmission parameters to fix problem with K1200 motorbike
Corrected LCM type detection, now using Coding Index
Corrected spelling and text in german & turkish language files
Improved Online Updates routine a lot
Improved decoding of CD changer control and status messages
Improved decoding of audio control messages
Adjusted display of clock dialog text


v2.6.10 21 February 2009
Fixed bug where CodeTV dialog was incorrectly reading identity from TEL, not TV
Fixed bug where ReadBT was hanging when reading the emergency number
Fixed bug where CodeBT was not coding the ULF name
Improved upgrade sequence from previous versions. If OCX files not found, prev
version can now still be used

v2.6.1 17 February 2009
Fixed bug where Status messages were not resetting to "Ready"
Fixed Registration bug

v2.6.0 16 February 2009
Added multi-lingual capability with many languages.
Added checking for required LNG and OCX files on startup
Added "Help - NavCoder Online" to Help menu
Added "Help - Go to Resler I-Bus Interface Website" capability
Added "Help - Contact Author" capability
Added "Help - Check for Updates" capability
Added "File - Export log file" capability. Exports as CSV file.
Added Moneybookers.com as payment method
Added Code BT to the Telephone dialog. You can code name, passkey, and emerg number
To display nicely in Excel, use custom format of "00", and left-aligned for all cells.
Fixed many small bugs and tidyed up error handling code a lot
Fixed bug where failed headlight left & right were swapped
Adjusted a lot of dialog layout to cater for multi-lingual text
Added decoding of ibus command 0x31 "Buttons" for use with K1200 motorbike
Built NavCoder website

v2.5.40 30 November 2008
Added ability to re-parse an older log file and generate a new log file with the
freshly re-parsed content (useful to me to review older log files).
Added decoding of (some) TMC data. Needs verifying
Fixed parsing of map scales (200, 500 & 1000km scales)
Fixed bug where Mk3 voice coding did not correctly detect the nav results

v2.5.32 18 November 2008
Fixed small bug where all longitudes would display as E, instead of E or W
Fixed bug where 750iL consumption was showing as 0x0A instead of mpg

v2.5.31 20 October 2008
Fixed small bug where saving of scan results to a new file didn't work.

v2.5.30 19 September 2008
Added much easier registration process, with registration reminders

v2.5.22 15 September 2008
Added "Register NavCoder now!" button to main dialog
Added decoding of msg 0x2D "Dial number"
Added decoding of msg 0xAA "Nav control"
Updated decoding of time & date (msg 0x1F) to include radio-controlled clock
Fixed bug where saving an info scan caused "run-time error 52"

v2.5.20 26 August 2008
Added scan - Service Information
Fixed bug where ProgressLog was not being closed after coding nav languages & boot mode
Fixed coding nav bug (verification was failling)
Fixed display of msg 0x23, 0x24 where control byte wasn't interpreted properly

Enjoy!

Thanks, keep up the good fight mate :)

Hi Jochen, mail sent regarding post http://www.xoutpost.com/508063-post18.html


Thanks in advance!
Manu.

Hi Jochen. I have the exact same problem as Manu. In addition to that, none of the LCM coding changes the burnt bulb lights for my rear LED taillights. I have emailed you twice already about this and haven't received a reply.

Haven't got on to that yet, it's really hard when a) I don't have a car to test on and b) there are so many different types of LCM / LSZs out there....

Hi, if you'd like to iterate, I'd be happy to do any debugging you might need!

Thanks Jochen

I just formatted my laptop, and the key that i got off you, is not working anymore. I believe the registration code has changed.
What to do?

You send me the new registration code by email.

Email sent KiwiJochen

Any idea on when i would expect the reply?

Is it possible to code monochrome MK2 to color version?

No, the Mk2 has different internal hardware for Mono or Colour.

Is there going to be a newer Nav coder out soon?
Also if I buy a activation key, will this work for all new futire release?

I am witing for my Resler to come through the post, there is a slight delay on it at the moment but looking forward to trying it out :)

Jochen updates the software frequently - when he finds out how to do new cool things :D

The activation key will work on all updates - once registered just download the latest version when he posts it.

Well worth the wait and more than worth the registration fee.

Amen to that!

aldo - using one small aspect of Jochen's NavCoder as an example, ie enabling TV in motion, you can buy an ugly ass TV in motion lead from the internet for £50 or so, or activate it with a simple tick in a box in NavCoder for €20 and have a whole lot of other functions to play with.

It's all you'll ever need, no question. :thumbup:

MKII monos have different P/Ns I think from color ones. Solution, upgrade to MKIII or MKIV.

Thanks trapdoor. What you say is 100% correct :-)

The best feature it enabled for me was the voice control. I think that cost several hundered(£s) as a dealer option. I use it all the time now.

My Interface is being shipped tomorrow, so hopefully by end of week I will have and then it will just be a case of working to get it connected to the IBUS cable itself and playing about with the software :)

Bug fixes and some small improvements:

v2.5.22 15 September 2008
Added "Register NavCoder now!" button to main dialog
Added decoding of msg 0x2D "Dial number"
Added decoding of msg 0xAA "Nav control"
Updated decoding of time & date (msg 0x1F) to include radio-controlled clock
Fixed bug where saving an info scan caused "run-time error 52"

Get it here:
http://www.bimmerboard.com/members/k...l/NavCoder.zip

:thumbup:

Regards,
Manu.

Hi do you or anyone else know if this works on the 2007 models
"enabling TV in motion"

It works on the 2007 X3 and the 2007 Z4 (ibus based cars)

It will not work on any car with "i-Drive" due to the totally different computer networking architecture in these vehicles.

v2.5.30 released 19 Sept 2008 - Get it here:

http://www.bimmerboard.com/members/k...l/NavCoder.zip

Changes:
v2.5.30 19 September 2008
Added much easier registration process, with registration reminders

Good job Jochen, you're always the best !!!!

just on equestion: in the TV code function you added the possibility to make factory bmw tv tuner accept a PAl rear camera? does that work well?

thankx

Yes, that feature was added in one of the most recent releases.

Current NavCoder version is 2.5.30

Another question, I think might have been covered elsewhere but I can't find the thread.
If I wanted to put LED sidelights in the front headlamps, would disabling the blow bulb alert let me do this , I don't really want to mess about with resistors etc. I think someone might of tried it but they said it still showed the failed bulb indicator.

v2.5.31 released 20 Oct 2008 - Get it here:

http://www.bimmerboard.com/members/k...l/NavCoder.zip

Changes:
v2.5.31 20 October 2008
Fixed small bug where saving of scan results to a new file didn't work.

Hi, Jochen! I am having problems with my mkIII unit, it won't go into sleep mode after the car is turned off (posted a separate thread on this, but no replies yet). I was wondering if this problem can be fixed using the NavCoder?

NavCoder will allow you to observe the ibus adatabus activity and make further informed diagnosis.

eg: You may have another ibus device not going to sleep which is keeping the nav awake.

two questions
 

Hi,

i received my key for the software and am waiting on the interface from Reslers.

The only thing that I want to change is to activate the estimated time of arrival. Is it possible to selectively change only this parameter.

Is there a cable that connects the the Reslers interface to ibus? Can anyone describe what the place to connect to the ibus in the car looks like and where it is? Anyone have a picture? :dunno: i have a 2002 525i station wagon.

Thank you,

Bob

Thank you,

Bob

Yes, read the coding, then change that one item, then write the coding (code the nav)

However, if that one item is wrong, then the nav will guarranteed not be coded for your car. So take a moment to enter the VIN number, and set the other parameters to match the type of vehicle you have.

The Resler interface is designed to connect to the CD changer cable
Unplug the power/ibus/ground (3-wire) plug from the CD changer, and connect to the resler interface

Note that the brown wire = ground, make sure the plug orientation is correct.

Thanks for your quick response. :thumbup: It sounds easy enough. Will re-read the readme.txt before firing things up.

Cheers,

Bob

v2.5.40 30 November 2008
Added ability to re-parse an older log file and generate a new log file with the
freshly re-parsed content (useful to me to review older log files).
Added decoding of (some) TMC data. Needs verifying
Fixed parsing of map scales (200, 500 & 1000km scales)
Fixed bug where Mk3 voice coding did not correctly detect the nav results

Get it here:
http://www.bimmerboard.com/members/k...l/NavCoder.zip

Great Jochen!!!
thank you as always!!!
just one question: with the TMC function that you started to decode...can we be able one day to add a poi warner to our navigator using the tmc alert function??

just dreaming......

No, because TMC has nothing to do with POI data

And anyway, a POI warning can only be implemented by adding it into the operating system. You need to edit the operating system to do that - anyone know how to write code for OS9000...??

Hi Guy's,

I have purchased navcoder in the past (about 6 months ago) and have now had to format my laptop...

Am I able to get the key for it for free with me already purchasing it???

THanks

ASH

I cannot understand why you ask this question in a international public forum, instead of sending an email to the NavCoder author directly.

The author of NavCoder offer excellent and rapid email support, and is the only person that can answer such question with authority, and I believe he prefers to answer these questions by email.

The TMC can trigger and place an icon on screen though, I think that it will trigger a voice alert "traffic queing ahead" something like that, the TMC must have a hookin to the OS to be able to do this, if the POI DB is already there modding one of the TMC waring icons with navtweak and sound with navspeak then it sounds possible.

I assume that the TMC works like so;

Car know where it is (GPS),
TMC broadcasts data on problems (with GPS loctaion)
TMC enabled Map discs listen and store TMC info,
If car GPS location and TMC info GPS location are close then
Trigger correct display icon and audio alert.

Somewhere in the OS the TMC signal carries the info for the correct icon and the correct audio alert,

Hmmm I see, the problem is the camera DB, how will the TMC part be able to access the POI db on the map disc...

Yes, based on pre-defined locations, as stored in the TMC database on the map disc, and as managed by each countries authority.

The TMC data protocol provides a numeric location ID. One of 64,000 for the country. There is no lat/long transmitted.

Nope, it broadcasts a numeric location ID with a problem ID and problem extent, and a few other details.

Essentially. A map disc doesn't listen or store the data, that's what the nav OS does.

Yep.
A location ID from 0 to 64,000 is broadcast over the radio.
The correlation between location ID and lat/long is held on the TMC database on the map disc.
The location IDs are specified by the countries authority
An event ID is broadcast - also from 0 to I think 30,000. The correlation between event ID and event type is defined by the TMC standard and the text is held on the TMC database on the map disc and then displayed in the appropriate user language.

It cannot. It's not part of the TMC standard.

Anyway, to do what you want requires the operating system to be re-written.
You'd have to translate between the POI lat/long and the nearest known predefined TMC location ID. What if there is no location ID? What if the POI location lies 2km from the closest location ID?

And who can modify the operating system of the nav computer?

And that is not something I can do. It's something only the original software designers can do.

Indeed, thanks for the detailed info, very informative.

Hello @ all,

first i'd like to say that i'm a newbee with NavCoder but i really wanna try it. The only thing i want to know is: Where can i buy the ibus adapter to use with navcoder? Btw: It is possible to get an ibus adapter for use with carsoft 6.5 and novcoder?? That would be great!!

Hi again,

does NavCoder also have the ability to change a TV module from 4:3 to 16:9

Navcoder --The Budget Saver--
 

Thanks for all Jochen.

I was shocked to see that the MK4 bought trough ebay was Monocrom and the only possible program to change it to Color ( in the world I guess ) was the celeverly designed Navcoder.:thumbup:

Not only for the program but also thanks for your fast and detailed support ( on how to connect the interface and use the program ) I solved the problem with the Navcoder and also had an oppartunity to enable the TV.:D

Hi,
I have read through this and a few other pages and have a few beginner questions, so please excuse my ignorance on your system...

I have a 2001 325 (e46) w/o OEM Navigation. My main interest in NavCoder is to disable the headlight out warnings on my dash (my car has a taillight and headlight listed as being out, yet all bulbs are fully functional). It is my understanding that with Navcoder, i can turn off these indicators, correct?

Can I connect to the iBus via the OBC port in the car--or do I have to connect via the CD changer cable? I purchased a copy of PA Soft that came with an interface cable--can I just use this to connect? Cable on far right:

http://i9.ebayimg.com/06/i/001/0b/72/c6a2_1.JPG

If I can't use the above cable, I will need an adappter to connect to my laptop and the CD changer input in the trunk, correct? This 30 Euro interface kit from Reslers seems like the way to go:


http://www.reslers.de/IBUS/img/board_2.jpg


My first question is with how to connect the CD changer cable to this interface. There appear to be two connectors to the CD changer, and I want to make sure that I'm using the right connector, and also have the positive / negative correct.

Thanks!

OK, just tried using the PA Soft interface and I didn't get any communication... I'm guessing I need the Resler adapter...

No, You can not use PA Soft scanner to connect to I-Bus. Use PA only to modify LSZ directly to EEPROM or coding data block 00 to switch off bulb warning for Your lights. You have to know what to change to proceed. I verified some pre-facelift E46 coding data and I will post them to KiwiJochen. NavCoder will know soon how to do it for pre-facelift E46.


Check, if PAscanner contacts with engine (and gearbox if You have automatic) module. If it does and other modules show no communication, You must connect pins 7 and 8 inside OBD2 connector as the chinese replica is connected just to pin 7. I had to do this modd to make my interface working.

Correct, but the Warning Messages are telling you there is something wrong. Fix the fault, do not mask it!
You will have a bad bulb contact or an old bulb with high-resistance.

You are much better off to fix instead of hiding the fault


NavCoder requires a direct ibus connection, the OBDII connector does not have ibus. Ibus is on the CD changer cable as well as many other devices.

No.

Yes, Resler interface is the easiest.

Only one connector fits. Plug it in!

Thank you! Perfect... ordering the adapter now!

As for the bulb out thing... I've replaced every headlight--and taken it to 2 dealrs... No one can figure out what the heck is wrong with it... I'm open for any other ideas, but the damn light indicator just wont go away. =)

sna77 - Rolf's interface (as pictured) is what you need. Your picture is of the RS232 version and there is also a USB version.

At the rear of your CD player it is the 3-pin connector you need. The red wire is +12v, the brown wire is GND and the white/grey/yellow wire is the i-Bus feed.

Connect to the interface pins as labelled in your picture, the NTSC pin will obviously be unsused.

The following page on Rolf's website explains it further : Interface Installation

Maybe then the monitoring circuit is faulty, will be interesting to see if NavCoder can turn it off.

Or else a poor connection between LKM and the bulb.

Are you saying that right now NavCoder cannot turn off the warning lights on a prefacelift e46?

Thx

Hoping so... The dealer replaced the LCM and instrument cluster already and still couldn't figure it out...

I'm currently solving the issue with the "electric tape mod"

haaa... and yes I realize this is beyond ghetto... The damn light was driving me insane
http://www.bigpatsfans.com/bmwcluster/cluster3.JPG

I'm saying that as no-one can diagnose his fault, maybe the monitoring circuit is faulty, and if so, I don't know how the LCM will react in this situation

NavCoder CAN turn off the warning message.

OK, then its worth a shot for sure... Spending 30 euro on the interface kit is a lot cheaper than paying the clowns at the dealer to poke around aimlessly at my car for hours...

Great, So I have LED bulbs that fire off the bulb warning lights. I'm pretty sure I disabled these yet they still flicker and fire off the bulb warning system. I will try again at weekend.

Anyone know how long it takes to get the registration code after you pay for NavCoder?

My serial port to ibus interface just came in and I ripped apart the trunk, fired up the software (it read the LCM properly!) and then I hit "code" and I got a need to pay for the software message... Oops.

Anyhow, just paid via PayPal... anyone know how long it takes to get a key? Is it a minutes, hours or days thing? Want to know if I should call it a night and reassemble my car or if I should wait...

thx!

It takes around 5 minutes, provided I am awake and online :-)

thanks! Didn't know if it was some automated process or not... heading out to the garage now... ;)

Jochen... Good news... Got the code and registered the software OK and connected to my CD changer input in the trunk... The software reads the LCM as the LCMII (not e46)... Anyhow... I have a warning light out, so I unchecked all the warning lights, hit "code," got the message that everything was successful, turned the car off for 10 seconds etc...

Unfortunately, when I turned it back on, the warning lights where still there...

Any suggestions?

Thx

What model/year car?

What LCM part number & indexes?

2001 325i sedan.

My LCM was replaced by the dealer a few years back when I retrofitted OEM bi-xenon headlights...

I'll get back to you with the part #'s in a few... Need to run out and grab the garage laptop with the screen shots.

Show us the part of navcoder.log where is I-BUS messages between LSZ and KMB, and you will get definitive answer about your light fault.
Regards!!!

blah. the file from this AM didn't save automatically. Will have to redo it tonight...

Should I get the log of just reading the LCM or trying to code it?

where do I buy this nad how do i install it on my laptop
I download it the latest version but it wont let me put it on my laptop

First link of this thread:
http://www.siegenthaler.co.nz/NavCoder/

You need to follow the instructions and install the DLL files before you can get it to run...

To KiwiJochen, question please:

Is NavCoder capable of adjusting the audio mixing volume from different audio sources?

My issue is - ever since I removed the stock DSP amp and upgraded my amp to a more powerful amp -the Nav volume is now too loud. I have already set the nav volume to its bare minimum but it is still too loud compared to other audio sources (CD, AM, FM, etc.)

Thanks in advance.

BTW, I have an E39 M5.

Dan

That function doesn't exist in the radio hardware, sorry.

Add a good old fashioned potentiometer to the nav audio lines, and adjust the level to what you like.

i get the following message
http://img.photobucket.com/albums/v4...co90/error.jpg

got it thanks

Thanks for the info and prompt reply!

Can you kindly send me a link showing which wires I need to tap to for the Nav audio line out?

And what value potentiometer you recommend I should use?

Many many thanks!

Dan

Where did you adjust the volume? Adjusting it via Settings-menu is not enough, you need to adjust it via Info-button's nav-min adjustment. If you already did that, then using a potentiometer or fixed resistors is the way to go.

Easy: there is a twsted pair of wires on the nav blue plug. Normally blue/ brown and blue/red. On some cars yellow/brown & yellow/red

red stripe is signal
brown stripe is ground

Fit around a 1 to 10k-Ohm potentiometer

solder one end of pot to brown stripe wire
Cut red stripe wire, solder nav end to other side of pot
Solder radio module end to wiper of pot.

You get the message stating no LNG language files can be found, because no LNG language files can be found !!

Copy all files in the NavCoder zip file into the same directory

Make sure at least one LNG file exists

If it still doesn't work, email me.

Hi TJJ,

Yes, I have done both already.

1) Adjusted to bare minimum via Nav Volume settings. Done.
2) Adjusted volume via Radio Service Mode Info Button. Done.

Still too loud : (

Looks like potentiometer is the way to go.

Thanks.

Dan

Excellent info. Thank you!

Wow, you folks are just like the nice people we have on our M5board.
Very helpful!

Many many thanks!!!!!!!!

I will order the NavCoder next week so I can turn off the light bulb fault messages on my M5 and my wife's 330ci (I converted my license plate bulbs and 3rd brake light bulbs to LED's.)

Thank you folks again for everything.

Dan

got it working

ok got the software
1. I know I have to buy a key
2. where do I buy a ibus interface besides owners web site can some one post picts of the parts I need thanks Franco
I am missing anything else

Just buy this:
http://www.reslers.de/IBUS/index.html

If your laptop has a serial port, the serial port one is easy to use...

Mine took about 9 days to come in. He only ships Sunday nights so make sure to order before the weekends over...

ok I will now how do you connect this to the car? pictures please

NavCoder log. No LSZ or KMB listed???


2/19/2009 8:51:05 PM: NavCoder v2.6.1 logging started
2/19/2009 8:51:06 PM: 80 05 BF 18 00 00 22
2/19/2009 8:51:06 PM: IKE --> GLO : Speed/RPM: Speed 0 km/h, 0 RPM
2/19/2009 8:51:08 PM: 80 05 BF 18 00 00 22
2/19/2009 8:51:08 PM: IKE --> GLO : Speed/RPM: Speed 0 km/h, 0 RPM
2/19/2009 8:51:10 PM: 80 05 BF 18 00 00 22
2/19/2009 8:51:10 PM: IKE --> GLO : Speed/RPM: Speed 0 km/h, 0 RPM
2/19/2009 8:51:12 PM: 80 05 BF 18 00 00 22
2/19/2009 8:51:12 PM: IKE --> GLO : Speed/RPM: Speed 0 km/h, 0 RPM
2/19/2009 8:51:14 PM: 5B 05 80 83 00 08 55
2/19/2009 8:51:14 PM: IHK --> IKE : Air conditioning compressor status:
2/19/2009 8:51:14 PM: 80 0A BF 13 03 00 00 00 00 00 1E 3B
2/19/2009 8:51:14 PM: IKE --> GLO : IKE sensor status: Handbrake_On Oil_Pressure_Low
2/19/2009 8:51:14 PM: 80 05 BF 18 00 00 22
2/19/2009 8:51:14 PM: IKE --> GLO : Speed/RPM: Speed 0 km/h, 0 RPM
2/19/2009 8:51:14 PM: 80 06 BF 19 FE 4F 00 91
2/19/2009 8:51:14 PM: IKE --> GLO : Temperature: Outside -2°C, Coolant 79°C
2/19/2009 8:51:16 PM: 80 05 BF 18 00 00 22
2/19/2009 8:51:16 PM: IKE --> GLO : Speed/RPM: Speed 0 km/h, 0 RPM
2/19/2009 8:51:16 PM: D0 08 BF 5B 00 04 08 18 00 28
2/19/2009 8:51:16 PM: LKM --> GLO : Lamp status: All_Off Tail Faulty: High_Beam Tail_Left Low_Beam_Right
2/19/2009 8:51:17 PM: D0 07 BF 5C FF 3F FF 00 0B
2/19/2009 8:51:17 PM: LKM --> GLO : Light dimmer: Data="FF 3F FF 00"
2/19/2009 8:51:18 PM: 80 05 BF 18 00 00 22
2/19/2009 8:51:18 PM: IKE --> GLO : Speed/RPM: Speed 0 km/h, 0 RPM
2/19/2009 8:51:20 PM: 80 05 BF 18 00 00 22
2/19/2009 8:51:20 PM: IKE --> GLO : Speed/RPM: Speed 0 km/h, 0 RPM
2/19/2009 8:51:22 PM: 80 05 BF 18 00 00 22
2/19/2009 8:51:22 PM: IKE --> GLO : Speed/RPM: Speed 0 km/h, 0 RPM
2/19/2009 8:51:24 PM: 5B 05 80 83 00 00 5D
2/19/2009 8:51:24 PM: IHK --> IKE : Air conditioning compressor status: Off
2/19/2009 8:51:24 PM: 80 0A BF 13 03 00 00 00 00 00 1E 3B
2/19/2009 8:51:24 PM: IKE --> GLO : IKE sensor status: Handbrake_On Oil_Pressure_Low
2/19/2009 8:51:24 PM: 80 05 BF 18 00 00 22
2/19/2009 8:51:24 PM: IKE --> GLO : Speed/RPM: Speed 0 km/h, 0 RPM
2/19/2009 8:51:24 PM: 80 06 BF 19 FE 4F 00 91
2/19/2009 8:51:24 PM: IKE --> GLO : Temperature: Outside -2°C, Coolant 79°C
2/19/2009 8:51:26 PM: 80 05 BF 18 00 00 22
2/19/2009 8:51:26 PM: IKE --> GLO : Speed/RPM: Speed 0 km/h, 0 RPM
2/19/2009 8:51:26 PM: 3F 03 D0 00 EC
2/19/2009 8:51:26 PM: DIA --> LKM : Read identity
2/19/2009 8:51:26 PM: D0 0F 3F A0 06 93 68 38 25 35 30 14 17 05 09 36 9C
2/19/2009 8:51:26 PM: LKM --> DIA : Diagnostic command acknowledged, Data="06 93 68 38 25 35 30 14 17 05 09 36"
2/19/2009 8:51:27 PM: 3F 04 D0 08 00 E3
2/19/2009 8:51:27 PM: DIA --> LKM : Read coding data, Data="00"
2/19/2009 8:51:27 PM: D0 23 3F A0 00 72 FF 77 EF EF 3C 20 20 21 22 22 40 72 72 21 21 20 21 D7 D7 20 20 72 72 BB 5B B6 00 17 E0 41 2A
2/19/2009 8:51:27 PM: LKM --> DIA : Diagnostic command acknowledged, Data="00 72 FF 77 EF EF 3C 20 20 21 22 22 40 72 72 21 21 20 21 D7 D7 20 20 72 72 BB 5B B6 00 17 E0 41"
2/19/2009 8:51:27 PM: Read LCM - LCM coding successfully read. NavCoder has been updated with the current LCM settings.
2/19/2009 8:51:28 PM: 80 05 BF 18 00 00 22
2/19/2009 8:51:28 PM: IKE --> GLO : Speed/RPM: Speed 0 km/h, 0 RPM
2/19/2009 8:51:30 PM: 80 05 BF 18 00 00 22
2/19/2009 8:51:30 PM: IKE --> GLO : Speed/RPM: Speed 0 km/h, 0 RPM
2/19/2009 8:51:32 PM: D0 07 BF 5C FF 3F FF 00 0B
2/19/2009 8:51:32 PM: LKM --> GLO : Light dimmer: Data="FF 3F FF 00"
2/19/2009 8:51:32 PM: 80 05 BF 18 00 00 22
2/19/2009 8:51:32 PM: IKE --> GLO : Speed/RPM: Speed 0 km/h, 0 RPM
2/19/2009 8:51:34 PM: 5B 05 80 83 00 08 55
2/19/2009 8:51:34 PM: IHK --> IKE : Air conditioning compressor status:
2/19/2009 8:51:34 PM: 80 0A BF 13 03 00 00 00 00 00 1E 3B
2/19/2009 8:51:34 PM: IKE --> GLO : IKE sensor status: Handbrake_On Oil_Pressure_Low
2/19/2009 8:51:34 PM: 80 05 BF 18 00 00 22
2/19/2009 8:51:34 PM: IKE --> GLO : Speed/RPM: Speed 0 km/h, 0 RPM
2/19/2009 8:51:34 PM: 80 06 BF 19 FE 4F 00 91
2/19/2009 8:51:34 PM: IKE --> GLO : Temperature: Outside -2°C, Coolant 79°C
2/19/2009 8:51:36 PM: 80 05 BF 18 00 00 22
2/19/2009 8:51:36 PM: IKE --> GLO : Speed/RPM: Speed 0 km/h, 0 RPM
2/19/2009 8:51:38 PM: 80 05 BF 18 00 00 22
2/19/2009 8:51:38 PM: IKE --> GLO : Speed/RPM: Speed 0 km/h, 0 RPM
2/19/2009 8:51:42 PM: 80 05 BF 18 00 00 22
2/19/2009 8:51:42 PM: IKE --> GLO : Speed/RPM: Speed 0 km/h, 0 RPM
2/19/2009 8:51:42 PM: 80 05 BF 18 00 00 22
2/19/2009 8:51:42 PM: IKE --> GLO : Speed/RPM: Speed 0 km/h, 0 RPM
2/19/2009 8:51:42 PM: 3F 04 D0 08 00 E3
2/19/2009 8:51:42 PM: DIA --> LKM : Read coding data, Data="00"
2/19/2009 8:51:42 PM: D0 23 3F A0 00 72 FF 77 EF EF 3C 20 20 21 22 22 40 72 72 21 21 20 21 D7 D7 20 20 72 72 BB 5B B6 00 17 E0 41 2A
2/19/2009 8:51:42 PM: LKM --> DIA : Diagnostic command acknowledged, Data="00 72 FF 77 EF EF 3C 20 20 21 22 22 40 72 72 21 21 20 21 D7 D7 20 20 72 72 BB 5B B6 00 17 E0 41"
2/19/2009 8:51:43 PM: 3F 23 D0 09 00 72 FF 77 EF EF 3C 20 20 21 22 22 40 72 72 21 21 20 21 D7 D7 20 20 72 72 BB 5B B6 00 17 E0 41 83
2/19/2009 8:51:43 PM: DIA --> LKM : Write coding data, Data="00 72 FF 77 EF EF 3C 20 20 21 22 22 40 72 72 21 21 20 21 D7 D7 20 20 72 72 BB 5B B6 00 17 E0 41"
2/19/2009 8:51:43 PM: D0 03 3F A0 4C
2/19/2009 8:51:43 PM: LKM --> DIA : Diagnostic command acknowledged
2/19/2009 8:51:43 PM: Code LCM - The LKM has confirmed the coding was successful. Please switch the ignition off, wait 10s, then on to reset the LKM. Please check the function that you changed is working properly.
2/19/2009 8:51:44 PM: 5B 05 80 83 00 00 5D
2/19/2009 8:51:44 PM: IHK --> IKE : Air conditioning compressor status: Off
2/19/2009 8:51:44 PM: 80 0A BF 13 03 00 00 00 00 00 1E 3B
2/19/2009 8:51:44 PM: IKE --> GLO : IKE sensor status: Handbrake_On Oil_Pressure_Low
2/19/2009 8:51:44 PM: 80 05 BF 18 00 00 22
2/19/2009 8:51:44 PM: IKE --> GLO : Speed/RPM: Speed 0 km/h, 0 RPM
2/19/2009 8:51:44 PM: 80 06 BF 19 FE 4F 00 91
2/19/2009 8:51:44 PM: IKE --> GLO : Temperature: Outside -2°C, Coolant 79°C
2/19/2009 8:51:46 PM: 80 05 BF 18 00 00 22
2/19/2009 8:51:46 PM: IKE --> GLO : Speed/RPM: Speed 0 km/h, 0 RPM
2/19/2009 8:51:46 PM: D0 08 BF 5B 00 04 08 18 00 28
2/19/2009 8:51:46 PM: LKM --> GLO : Lamp status: All_Off Tail Faulty: High_Beam Tail_Left Low_Beam_Right
2/19/2009 8:51:47 PM: D0 07 BF 5C FF 3F FF 00 0B
2/19/2009 8:51:47 PM: LKM --> GLO : Light dimmer: Data="FF 3F FF 00"
2/19/2009 8:51:48 PM: 80 05 BF 18 00 00 22
2/19/2009 8:51:48 PM: IKE --> GLO : Speed/RPM: Speed 0 km/h, 0 RPM
2/19/2009 8:51:50 PM: 80 05 BF 18 00 00 22
2/19/2009 8:51:50 PM: IKE --> GLO : Speed/RPM: Speed 0 km/h, 0 RPM
2/19/2009 8:51:52 PM: 80 05 BF 18 00 00 22
2/19/2009 8:51:52 PM: IKE --> GLO : Speed/RPM: Speed 0 km/h, 0 RPM
2/19/2009 8:51:52 PM: 80 0C FF 24 01 00 20 38 3A 34 38 50 4D 65
2/19/2009 8:51:52 PM: IKE --> LOC : Update Text: Time Btn0_Bkgd_update_EndTx=" 8:48PM"
2/19/2009 8:51:54 PM: 5B 05 80 83 00 08 55
2/19/2009 8:51:54 PM: IHK --> IKE : Air conditioning compressor status:
2/19/2009 8:51:54 PM: 80 0A BF 13 03 00 00 00 00 00 1E 3B
2/19/2009 8:51:54 PM: IKE --> GLO : IKE sensor status: Handbrake_On Oil_Pressure_Low
2/19/2009 8:51:54 PM: 80 05 BF 18 00 00 22
2/19/2009 8:51:54 PM: IKE --> GLO : Speed/RPM: Speed 0 km/h, 0 RPM
2/19/2009 8:51:54 PM: 80 06 BF 19 FE 4F 00 91
2/19/2009 8:51:54 PM: IKE --> GLO : Temperature: Outside -2°C, Coolant 79°C
2/19/2009 8:51:56 PM: 80 05 BF 18 00 00 22
2/19/2009 8:51:56 PM: IKE --> GLO : Speed/RPM: Speed 0 km/h, 0 RPM
2/19/2009 8:51:58 PM: 80 05 BF 18 00 00 22
2/19/2009 8:51:58 PM: IKE --> GLO : Speed/RPM: Speed 0 km/h, 0 RPM
2/19/2009 8:52:00 PM: 80 05 BF 18 00 00 22
2/19/2009 8:52:00 PM: IKE --> GLO : Speed/RPM: Speed 0 km/h, 0 RPM
2/19/2009 8:52:02 PM: D0 07 BF 5C FF 3F FF 00 0B
2/19/2009 8:52:02 PM: LKM --> GLO : Light dimmer: Data="FF 3F FF 00"
2/19/2009 8:52:02 PM: 80 05 BF 18 00 00 22
2/19/2009 8:52:02 PM: IKE --> GLO : Speed/RPM: Speed 0 km/h, 0 RPM
2/19/2009 8:52:04 PM: 5B 05 80 83 00 00 5D
2/19/2009 8:52:04 PM: IHK --> IKE : Air conditioning compressor status: Off
2/19/2009 8:52:04 PM: 80 0A BF 13 03 00 00 00 00 00 1E 3B
2/19/2009 8:52:04 PM: IKE --> GLO : IKE sensor status: Handbrake_On Oil_Pressure_Low
2/19/2009 8:52:04 PM: 80 05 BF 18 00 00 22
2/19/2009 8:52:04 PM: IKE --> GLO : Speed/RPM: Speed 0 km/h, 0 RPM
2/19/2009 8:52:04 PM: 80 06 BF 19 FE 4F 00 91
2/19/2009 8:52:04 PM: IKE --> GLO : Temperature: Outside -2°C, Coolant 79°C
2/19/2009 8:52:06 PM: 80 05 BF 18 00 00 22
2/19/2009 8:52:06 PM: IKE --> GLO : Speed/RPM: Speed 0 km/h, 0 RPM
2/19/2009 8:52:08 PM: 80 05 BF 18 00 00 22
2/19/2009 8:52:08 PM: IKE --> GLO : Speed/RPM: Speed 0 km/h, 0 RPM
2/19/2009 8:52:10 PM: 80 05 BF 18 00 00 22
2/19/2009 8:52:10 PM: IKE --> GLO : Speed/RPM: Speed 0 km/h, 0 RPM
2/19/2009 8:52:12 PM: 80 05 BF 18 00 00 22
2/19/2009 8:52:12 PM: IKE --> GLO : Speed/RPM: Speed 0 km/h, 0 RPM
2/19/2009 8:52:14 PM: 5B 05 80 83 00 08 55
2/19/2009 8:52:14 PM: IHK --> IKE : Air conditioning compressor status:
2/19/2009 8:52:14 PM: 80 0A BF 13 03 00 00 00 00 00 1E 3B
2/19/2009 8:52:14 PM: IKE --> GLO : IKE sensor status: Handbrake_On Oil_Pressure_Low
2/19/2009 8:52:14 PM: 80 05 BF 18 00 00 22
2/19/2009 8:52:14 PM: IKE --> GLO : Speed/RPM: Speed 0 km/h, 0 RPM
2/19/2009 8:52:14 PM: 80 06 BF 19 FE 4F 00 91
2/19/2009 8:52:14 PM: IKE --> GLO : Temperature: Outside -2°C, Coolant 79°C
2/19/2009

Mine connects to the CD changer line in the trunk (2001 325i sedan).

I took a standard serial cable, connected it to the back of my laptop, then ran the other end to the adapter I bought linked above. Then I connected the CD changer cable to the adapter. You need to verify the correct pin nout of the CD changer cable.



https://www.mycablemart.com/store/im.../861_small.jpg

http://www.bigpatsfans.com/navcoder1.JPG


http://www.bigpatsfans.com/navcoder2.JPG


Detail of the connection to CD changer input. Notice which wires line up with the Ibus serial interface:

http://www.bigpatsfans.com/navcoder3.jpg

Ok... back to my car... results from the full scan:


NavCoder v2.6.1 - Scan Results
File written 2/19/2009 9:35:13 PM

All Modules scan conducted on 2/19/2009 8:53:40 PM

Following devices were found and are communicating:

GM Body module:
Part number 6 907 663, version HW 11, SW 16, made by 27 on 43/00 (October 2000)
Diagnostic index 40, Bus index 10, Encoding index 02

SHD Sunroof:
Part number 6 910 471, version HW 05, SW 27, made by 25 on 43/00 (October 2000)
Diagnostic index 02, Bus index 78, Encoding index 01

EWS EWS III immobiliser control unit:
Part number 6 905 670, version HW 03, SW 08, made by 6 on 42/00 (October 2000)
Diagnostic index 81, Bus index 07, Encoding index 81

MFL Multi-function steering wheel:
Part number , version HW 01, SW 11, made by 2 on 00/00 (No date entered)
Diagnostic index 03, Bus index 78, Encoding index 00

IHK Climate control:
Part number 6 931 604, version HW 35, SW 14, made by 55 on 17/03 (April 2003)
Diagnostic index 33, Bus index 0E, Encoding index 16

RAD Radio:
Part number 6 941 505, version HW 44, SW 43, made by Alpine on 28/04 (July 2004)
Diagnostic index 35, Bus index 11, Encoding index 01

SM Seat memory:
Part number 8 099 069, version HW 04, SW 08, made by 2 on 07/99 (February 1999)
Diagnostic index 01, Bus index 01, Encoding index 01

IKE Integrated instrument cluster:
No identification data available for this device


ACM Airbag control module:
Part number 6 912 123, version HW 10, SW 30, made by 8 on 43/00 (October 2000)
Diagnostic index 08, Bus index 00, Encoding index 31

SES Voice recognition unit:
No identification data available for this device


TEL Telephone:
Part number 6 980 130, version HW 13, SW 81, made by Visteon on 38/06 (September 2006)
Diagnostic index 15, Bus index 13, Encoding index 06

LKM Light control module:
Part number 6 936 838, version HW 25, SW 36, made by Loewe on 17/05 (April 2005)
Diagnostic index 30, Bus index 14, Encoding index 35


The following devices did not respond:
They are either not fitted, not turned on, or not communicating on the I-bus.
0x01 Adr_0x01
0x02 Adr_0x02
0x03 Adr_0x03
0x04 Adr_0x04
0x05 Adr_0x05
0x06 Adr_0x06
0x07 Adr_0x07
0x09 Adr_0x09
0x0A Adr_0x0A
0x0B Adr_0x0B
0x0C Adr_0x0C
0x0D Adr_0x0D
0x0E Adr_0x0E
0x0F Adr_0x0F
0x10 Adr_0x10
0x11 Adr_0x11
0x12 Adr_0x12
0x13 Adr_0x13
0x14 Adr_0x14
0x15 Adr_0x15
0x16 Adr_0x16
0x17 Adr_0x17
CDC CD changer
0x19 Adr_0x19
0x1A Adr_0x1A
0x1B Adr_0x1B
0x1C Adr_0x1C
0x1D Adr_0x1D
0x1E Adr_0x1E
0x1F Adr_0x1F
0x20 Adr_0x20
0x21 Adr_0x21
0x22 Adr_0x22
0x23 Adr_0x23
HKM Boot lid control unit
0x25 Adr_0x25
0x26 Adr_0x26
0x27 Adr_0x27
FUM Radio-controlled clock
0x29 Adr_0x29
0x2A Adr_0x2A
0x2B Adr_0x2B
0x2C Adr_0x2C
0x2D Adr_0x2D
0x2E Adr_0x2E
0x2F Adr_0x2F
CCM Check control module
0x31 Adr_0x31
0x32 Adr_0x32
0x33 Adr_0x33
0x34 Adr_0x34
0x35 Adr_0x35
0x36 Adr_0x36
0x37 Adr_0x37
0x38 Adr_0x38
0x39 Adr_0x39
0x3A Adr_0x3A
GT Graphics driver
0x3C Adr_0x3C
0x3D Adr_0x3D
0x3E Adr_0x3E
DIA Diagnostics
FBZV Remote control & central locking
0x41 Adr_0x41
0x42 Adr_0x42
GTF Rear graphics driver
0x45 Adr_0x45
CID Central information display
FMBT Read monitor controls
0x48 Adr_0x48
0x49 Adr_0x49
0x4A Adr_0x4A
0x4B Adr_0x4B
0x4C Adr_0x4C
0x4D Adr_0x4D
0x4E Adr_0x4E
0x4F Adr_0x4F
MML Mirror memory Left
0x52 Adr_0x52
0x53 Adr_0x53
0x54 Adr_0x54
0x55 Adr_0x55
0x56 Adr_0x56
0x57 Adr_0x57
0x58 Adr_0x58
0x59 Adr_0x59
0x5A Adr_0x5A
0x5C Adr_0x5C
0x5D Adr_0x5D
0x5E Adr_0x5E
0x5F Adr_0x5F
PDC Park distance control
0x61 Adr_0x61
0x62 Adr_0x62
0x63 Adr_0x63
0x64 Adr_0x64
0x65 Adr_0x65
0x66 Adr_0x66
CDCD Adr_0x67
0x69 Adr_0x69
DSP Digital signal processor amplifier
0x6B Adr_0x6B
0x6C Adr_0x6C
0x6D Adr_0x6D
0x6E Adr_0x6E
0x6F Adr_0x6F
RDC Tyre pressure monitoring system
0x71 Adr_0x71
SDRS Satelite digital radio
0x74 Adr_0x74
0x75 Adr_0x75
CDCD CD changer DIN
0x77 Adr_0x77
0x78 Adr_0x78
0x79 Adr_0x79
0x7A Adr_0x7A
0x7B Adr_0x7B
0x7C Adr_0x7C
0x7D Adr_0x7D
0x7E Adr_0x7E
NAVE Navigation
0x81 Adr_0x81
0x82 Adr_0x82
0x83 Adr_0x83
0x84 Adr_0x84
0x85 Adr_0x85
0x86 Adr_0x86
0x87 Adr_0x87
0x88 Adr_0x88
0x89 Adr_0x89
0x8A Adr_0x8A
0x8B Adr_0x8B
0x8C Adr_0x8C
0x8D Adr_0x8D
0x8E Adr_0x8E
0x8F Adr_0x8F
0x90 Adr_0x90
0x91 Adr_0x91
0x92 Adr_0x92
0x93 Adr_0x93
0x94 Adr_0x94
0x95 Adr_0x95
0x96 Adr_0x96
0x97 Adr_0x97
0x98 Adr_0x98
0x99 Adr_0x99
0x9A Adr_0x9A
MMR Mirror memory Right
CVM Cabrio folding top module
0x9D Adr_0x9D
0x9E Adr_0x9E
0x9F Adr_0x9F
FMID Rear multi-info display
0xA1 Adr_0xA1
0xA2 Adr_0xA2
0xA3 Adr_0xA3
0xA5 Adr_0xA5
0xA6 Adr_0xA6
FHK Rear climate control
NAVC Navigation Control
0xA9 Adr_0xA9
0xAA Adr_0xAA
0xAB Adr_0xAB
EHC EHC
0xAD Adr_0xAD
0xAE Adr_0xAE
0xAF Adr_0xAF
0xB1 Adr_0xB1
0xB2 Adr_0xB2
0xB3 Adr_0xB3
0xB4 Adr_0xB4
0xB5 Adr_0xB5
0xB6 Adr_0xB6
0xB7 Adr_0xB7
0xB8 Adr_0xB8
0xB9 Adr_0xB9
0xBA Adr_0xBA
NAVJ Navigation (Japan)
0xBC Adr_0xBC
0xBD Adr_0xBD
0xBE Adr_0xBE
GLO Global
MID Multi-info display
0xC1 Adr_0xC1
0xC2 Adr_0xC2
0xC3 Adr_0xC3
0xC4 Adr_0xC4
0xC5 Adr_0xC5
0xC6 Adr_0xC6
0xC7 Adr_0xC7
0xC9 Adr_0xC9
0xCA Adr_0xCA
0xCB Adr_0xCB
0xCC Adr_0xCC
0xCD Adr_0xCD
0xCE Adr_0xCE
0xCF Adr_0xCF
0xD1 Adr_0xD1
0xD2 Adr_0xD2
0xD3 Adr_0xD3
0xD4 Adr_0xD4
0xD5 Adr_0xD5
0xD6 Adr_0xD6
0xD7 Adr_0xD7
0xD8 Adr_0xD8
0xD9 Adr_0xD9
SMAD Seat memory assistant driver
0xDB Adr_0xDB
0xDC Adr_0xDC
0xDD Adr_0xDD
0xDE Adr_0xDE
0xDF Adr_0xDF
IRIS Integrated radio information system
0xE1 Adr_0xE1
0xE2 Adr_0xE2
0xE3 Adr_0xE3
0xE4 Adr_0xE4
0xE5 Adr_0xE5
0xE6 Adr_0xE6
ANZV Front display
ISP ISP
0xE9 Adr_0xE9
0xEA Adr_0xEA
0xEB Adr_0xEB
0xEC Adr_0xEC
TV Video module
0xEE Adr_0xEE
0xEF Adr_0xEF
BMBT On-board monitor controls
0xF1 Adr_0xF1
0xF2 Adr_0xF2
0xF3 Adr_0xF3
0xF4 Adr_0xF4
CSU Centre switch control unit
0xF6 Adr_0xF6
0xF7 Adr_0xF7
0xF8 Adr_0xF8
0xF9 Adr_0xF9
0xFA Adr_0xFA
0xFB Adr_0xFB
0xFC Adr_0xFC
0xFD Adr_0xFD
0xFE Adr_0xFE

Tips for devices that do not communicate:
--> Check device is fitted to vehicle
--> Check ignition is turned on
--> Check device is switched on

BTW, Cool tool! My build date was 11/2000, so everything looks right, including the components I had replaced:

- Steering wheel (M3 wheel)
- LCM (when bi-xenons wired)
- Radio (from 2004--OEM Sirius support)
- Climate controls (grabbed the newer style one from an 04+ at junkyard)
- Sport seats (retrofit power seats from a 1999 e46 sport)
- Telephone (bought a newer Bluetooth ULF about a year ago)

The only thing that it didn't properly identify is my instrument cluster (mine died about 6 months ago, so i bought a new, uncoded ZHP cluster and had the dealer flash the car with it)

To KiwiJochen:

Thanks for creating and offering the NavCoder!

I have ordered the USB interface and will try your NavCoder program once the USB interface arrives.

Question: FYI, I am a member of the M5board.com. Can I let our members know about your NavCoder program?

Dan

I have purchased the version, from a friend of yours in Germany,
Got reg.code, but what when a new version is out and i downloaded the new version, can i use the same reg.code ?

I used my 2.5 code on 2.6 and it worked. As long as its the same computer I believe it works...

Sure, spread the word

sir thanks you for the pics I can do this as well Franco

Yes, reg key stays valid when upgrading.

[QUOTE=sna77]NavCoder log. No LSZ or KMB listed???

LSZ is another name for LKM

KMB ??

Jochen,
This is everything from the log pertaining to the LSZ. Any ideas?

Thanks,
Steve



LKM Light control module:
Part number 6 936 838, version HW 25, SW 36, made by Loewe on 17/05 (April 2005)
Diagnostic index 30, Bus index 14, Encoding index 35



2/19/2009 8:51:16 PM: LKM --> GLO : Lamp status: All_Off Tail Faulty: High_Beam Tail_Left Low_Beam_Right
2/19/2009 8:51:17 PM: D0 07 BF 5C FF 3F FF 00 0B
2/19/2009 8:51:17 PM: LKM --> GLO : Light dimmer: Data="FF 3F FF 00"
2/19/2009 8:51:18 PM: 80 05 BF 18 00 00 22

2/19/2009 8:51:26 PM: DIA --> LKM : Read identity
2/19/2009 8:51:26 PM: D0 0F 3F A0 06 93 68 38 25 35 30 14 17 05 09 36 9C
2/19/2009 8:51:26 PM: LKM --> DIA : Diagnostic command acknowledged, Data="06 93 68 38 25 35 30 14 17 05 09 36"
2/19/2009 8:51:27 PM: 3F 04 D0 08 00 E3
2/19/2009 8:51:27 PM: DIA --> LKM : Read coding data, Data="00"
2/19/2009 8:51:27 PM: D0 23 3F A0 00 72 FF 77 EF EF 3C 20 20 21 22 22 40 72 72 21 21 20 21 D7 D7 20 20 72 72 BB 5B B6 00 17 E0 41 2A
2/19/2009 8:51:27 PM: LKM --> DIA : Diagnostic command acknowledged, Data="00 72 FF 77 EF EF 3C 20 20 21 22 22 40 72 72 21 21 20 21 D7 D7 20 20 72 72 BB 5B B6 00 17 E0 41"
2/19/2009 8:51:27 PM: Read LCM - LCM coding successfully read. NavCoder has been updated with the current LCM settings.
2/19/2009 8:51:28 PM: 80 05 BF 18 00 00 22

2/19/2009 8:51:32 PM: LKM --> GLO : Light dimmer: Data="FF 3F FF 00"
2/19/2009 8:51:32 PM: 80 05 BF 18 00 00 22

2/19/2009 8:51:42 PM: DIA --> LKM : Read coding data, Data="00"
2/19/2009 8:51:42 PM: D0 23 3F A0 00 72 FF 77 EF EF 3C 20 20 21 22 22 40 72 72 21 21 20 21 D7 D7 20 20 72 72 BB 5B B6 00 17 E0 41 2A
2/19/2009 8:51:42 PM: LKM --> DIA : Diagnostic command acknowledged, Data="00 72 FF 77 EF EF 3C 20 20 21 22 22 40 72 72 21 21 20 21 D7 D7 20 20 72 72 BB 5B B6 00 17 E0 41"
2/19/2009 8:51:43 PM: 3F 23 D0 09 00 72 FF 77 EF EF 3C 20 20 21 22 22 40 72 72 21 21 20 21 D7 D7 20 20 72 72 BB 5B B6 00 17 E0 41 83
2/19/2009 8:51:43 PM: DIA --> LKM : Write coding data, Data="00 72 FF 77 EF EF 3C 20 20 21 22 22 40 72 72 21 21 20 21 D7 D7 20 20 72 72 BB 5B B6 00 17 E0 41"
2/19/2009 8:51:43 PM: D0 03 3F A0 4C
2/19/2009 8:51:43 PM: LKM --> DIA : Diagnostic command acknowledged
2/19/2009 8:51:43 PM: Code LCM - The LKM has confirmed the coding was successful. Please switch the ignition off, wait 10s, then on to reset the LKM. Please check the function that you changed is working properly.
2/19/2009 8:51:44 PM: 5B 05 80 83 00 00 5D

2/19/2009 8:51:46 PM: LKM --> GLO : Lamp status: All_Off Tail Faulty: High_Beam Tail_Left Low_Beam_Right
2/19/2009 8:51:47 PM: D0 07 BF 5C FF 3F FF 00 0B
2/19/2009 8:51:47 PM: LKM --> GLO : Light dimmer: Data="FF 3F FF 00"
2/19/2009 8:51:48 PM: 80 05 BF 18 00 00 22

Thanks for this post sna77, it was very helpful. Just to clarify, all you had to do was remove the connection from the CD Changer, check the connections were in fact GND, +12v and IBUS and plug it directly to the Resler interface pins? No soldering required at all? If so, this makes the whole process even easier for me as I'm absolutely useless with a soldering iron!

KiwiJochen, thank you very much for offering the NavCoder software to the public. I would be more than happy to pay the €20 to register the software if it can do what I want.

I'm aware that if I replace my standard incandescent bulbs with LEDs I can turn off the bulb warning/checking in your software (i.e. rear center stoplamp, brake lights etc.). However in relation to the front and rear turn signals, if I replace these with LEDs, the flash rate increases x2 to make me aware of the "blown" bulb. So for the turn signals, the fast flashing is the warning as opposed to the warning on my dash for the other bulbs.

- Is there a way in your software, to disable the double speed flashing of the turn signal bulbs (when I fit LEDs) through the LCM?

Many thanks,
Richard

Correct. It takes about 2 seconds to connect once you have unplugged the CD changer cable. No soldering at all.

[QUOTE=sna77]Jochen,
This is everything from the log pertaining to the LSZ. Any ideas?

Thanks,
Steve



LKM Light control module:
Part number 6 936 838, version HW 25, SW 36, made by Loewe on 17/05 (April 2005)
Diagnostic index 30, Bus index 14, Encoding index 35
2/19/2009 8:51:16 PM: LKM --> GLO : Lamp status: All_Off Tail Faulty: High_Beam Tail_Left Low_Beam_Right


Hi Steve!
As i seen in your log you need to check :High Beam lamp(cannot define from log which side), Tail lamp left side, Low Beam lamp right side.Are you checked all bulbs and wiring? May be you need to recode LKM.

[quote=Vitalik]
Right... everything works, but they can't figure out whats wrong... (i.e all bulbs work etc)... I just want to disable the warning lights on the dash, which is what I thought NavCoder did for me...

[QUOTE=sna77]Try to read new log from car with all lights on and off,in your log only
COLD monitoring faults ,because all lights was off.Also do not delete from
log hex string which have D0 in the beginning,its important for correctly
decoding lamp status bits.

[QUOTE=KiwiJochen]KMB is KOMBI , instrument cluster in E46.

Ive tried to change languages to dutch with navcoder on a mk3 with v31 disc.
But it wont change the languages, if i read the nav its saying dutch language. But it still is in Germany. OS was updated when i code it.
There is i think nothing wrong with the V31 disc, i used it a couple off time to code mk4.
Any ideas?

EDIT: Found it, mk3 doesn't support dutch language.

Correct, Mk3 doesn't support Ducth as is, you have to alter it to support Dutch. Like rename a Dutch language file to German, and change all Text from German to Dutch

i want to put together a navigation retrofit on my e46/2002, for now, i have mk4(mono coded), bm54 (back version) , a/c relocation unit and wiring loom, my question is: can i use navcoder with all navigation system (including 16:9 navigation monitor) powered by a DC source (on required pins on wiring loom) to try the system and recode all modules (connected)?...i already check the bm54, it works, but i don't want to recode the mk4 on other car, i don't want to make some mistake and crash someone else's car's navi system(or else)...

thank you in advance

You don't need to code following items:
BM54
16:9 Monitor
The nav will have to be coded from Mono to COlor to drive the screen
But the nav won't boot up properly unless it is connected to a car, so you have to wait until the nav is in the car before you recode it.

And NavCoder can code it for you

Regards, Jochen

ok, i understand, thank you very much for your answer

Help please!

I already eMailed Jochen but perhaps someone here can help me too?

I am trying to install NavCoder on my laptop with Windows Vista.

I have followed the instructions on installing and registering the missing OCX files but when I try to run Navcoder - I get this error message:

Runtime error '339'
Component 'msinet.ocx' or one of its dependencies not correctly registered: a file is missing or invalid.

I have already tried reinstalling msinet.ocx three times but I still get the same error.

HELP PLEASE!

Thanks in advance.

Dan

Find somewhere in the internet (Google for example is you friend) this file msinet.ocx, put it into System folder and then install it using regsvr32 comand (regsvr32 msinet.ocx)

don't forget to use "run as administrator" when use command prompt for reg. those ocx, won't work otherwise (registering using regsvr32)

Thanks! NavCoder now works!

I had two issues:

1) I was at the command prompt but didnt select "run as administrator".

2) One of the ocx file was corrupted. Downloaded a new file, re installed, re-registered and everything now works!

Thanks to all of you.

Now I just need to make sure Vista selected the correct driver for the iBus USB interface card.

The instructions for driver installation at the seller's website is for Windows XP only. I have eMailed Rolf already asking for instructions on driver installation for Vista.

Anyone here have info for me on how to load USB card driver for Vista?

Thanks in advance.

Hi whatheheck,

If it will make help, I had no problems with the driver when I first started to use it with vista. After installing the software to the laptop and connecting it with the car it didn't even asked for a driver. When I opened the NavCoder I had a good communication with the car at Com5.

Excellent! Thanks for the info.

I will hook it up to my M5 tonight and see if it works.

Thanks again.

You are absolutely correct! I plugged in the USB interface to the iBus and it worked perfectly. Looks like Vista loaded the correct USB driver.

Navcoder now works great! I was able to recode my LCM and turn off all the light fault reporting. Now I can replace my exterior lights with LED's.

NavCoder worked perfectly recoding my LCM on my 2001 M5, but it didnt work on my wife's 2002 330ci. I recoded the LCM on my wife's E46 330ci but the rear brake light still reported a fault on the on board display.
(I replaced my wife's brake light with OEM Hella LED tail lights.)
Recoding didnt turn off the fault light.

I will eMail the Navcoder author soon.

Jochen,

I have a couple of questions about your software, 1) If I do the trick to get rid of my accept screen (in USA) by changing it to the UK, will Navcoder allow me to flash it back to a USA unit? Thus avoiding a trip to the dealer for a 10 minute fix that they would charge me and hour for @ $100 USD per.

Second, can I have Navcoder set up my Angel Eyes to run as my daytime running lights?

Thanks!

It is simply changing of a configuration setting. No reflashing is needed at all.

The Regional setting (USA, Canada, Europe, Australia) can be changed any time, and any amount of times.

Not yet...

if i dont have a cd changer or the wiring for the cd changer where do i look to connect the interface(trunk??)

x3 2005 x3 retrofit navigation is all i have plus the dietz interface

thanks

I've been a member of x5 world for awhile now, I usually use this site to update/customize my navigation system (when updates are available).

Looking to soon get a TCU and work on activating Bluetooth since its much less expensive than going the ULF route...

Will any future updates allow voice-commands to be turned on for TCU units? Or does it already do this?

What about programming of "presets" for keys?
Thank goodness my original owner already had the DRL's turned off.
Auto door-lock/unlock?

I also think that would be cool, like the poster said at the top of the page, to be able to hook up some halo's to the DRL function. I would be interested in that too.

More questions...
I'm not sure if they are a sponsor of this website, but there is a sponsor of e46fanatics.com that offers a "kit" which you can program you key to do windows-up, the upgraded kit allows you to also program your mirrors to fold in, and do a few other things. Can this software do that? Or might it be able too in the future?

Sorry for the 20 questions, thanks in advance!

How? AFAIK, only the ULF supports bluetooth.
But tell us what car and radio/nav you have so we know more.

I enable as much as I can. Voice commands works on ULF modules, I've not had much feedback on how it works with TCUs. If people help me with vehicke data/info then I can add more features.

As soon as I figure out how and have time I'll do it.

No, because the "kit" insludes a hardware device with a microprocessor.
NavCoder allows you to change settings and reconfigure your car, it cannot magically make extra hardware and processors appear out of thin air :-)

I'm still new to this as well, sorry I did not provide more information. My 3/03 build 2003 330i ZHP has the HK/Navigation 16:9 (with CD not tape) running a modded version of the latest software. I currently have an earlier DICE unit hooked into the CD changer to run my 2nd gen iPod nano.

Let me run and grab the the links I've been doing my TCU research on. The later TCU units (as I understand) allow for bluetooth function without a ULF. The cost to install a re-manufactured unit from tischer and the necessary other parts run under $400, as opposed to $750+ going the ULF way...

Having scoured many BMW boards and ebay every few weeks for someone parting a 13th gen ULF bluetooth kit since I bought my iPhone (almost two years ago) see'ing that post (linked through a post on e46 fanatics) really perked me up. Thats about 1/2 price of going the ULF way from certain websites that sell the ULF bluetooth kits...

In another linked thread on e46fanatics to bimmerboard.com it looks like someone has already been in contact with you about finding a way to activate voice commands on these TCU units.

Paging kiwijochen: we have a new NavCoder challenge for you...

While not being able to use voice commands will not keep me from doing this mod (as soon as I get the cash together) it would be cool to be able to activate down the road...

I thought this might be the case as the site stated whatever they were selling needed to be installed, but I thought I might ask as I'm not fully aware of what all can be done with ibus. I might look at getting that unit later, I believe the price might come down as time passes and there are a few things that the unit can do that my car cant (yet) like fold in the mirrors...

Thank you for your time!

OK, part 84109195454 (Rmfd Telematics Control Unit) was found on the following vehicles: (E46, E53, E83, E85, E86)....

Interesting, BMW write that:
"A TCU (telematic control unit) can only be ordered by specifying the vehicle identification number. The VIN is coded when the replacement TCU is delivered. Recoding is not possible. The TCU functions properly only with matching coding. Replacements TCUs cannot therefore be ordered in reserve! Retrofits and conversions to SA633 are not possible!"

I have no experience with this TCU.
I do not know if it supports Bluetooth or not.

You could use the same approach I use when learning about BMW systems: "Try and see" :-)

^ excellent information, as always...

I will be going this route reguardless of weather or not voice commands work at the time of installation, or could in the future be enabled to work.

It was just one, of my many, questions in starting to get familiar with your software. I would eventually like to add a back-up cam to my car (I always park backwards in our garage) so I'll be diving into that mess soon as well.

Well, as soon as the car is paid off, its coming quickly so I'm trying to make a list of all the things I would like to do and prioritize how they should be done...

Excellent, glad to see you'll do it rain or shine :-)

Backup cam is very easy, no mess at all.

will navcoder recode all units needed when you do a nav retrofit?
eg, DSP, OBC, MKx.. etc..

i have no sound now after doing a retrofit and need to recode DSP to work with mk3
i have pa-soft so i could write the vin to the new unit(s)
but it doesnt detect DSP etc.. (basically useless)

No, not all.

NavCoder can 100% fully recod the nav unit - that was it's original purpose in life :-)
It can also recode the TV tuner

DSP is something I'd like to add but haven't had time

And the IKE (which contains the OBC) can only be recoded via the OBDII port, so NavCoder cannot do that.

If you've done a retrofit, then you'll need to go to BMW or someon with the BMW software such as GT1 and use that to recode the car via the OBDII port.

thanks for the reply
Ive bought the pa-soft some time ago and it wont do it either
it will do the ike, do the video in motion and vin the nav computer.. but wont touch anything else, wont detect the DSP.
around here the BMW dealers are booked up for 2 weeks and ive called a bunch of indy's and their booked even longer.

i was hoping for another solution other than GT1, which i dont have.

on another note if you need a hand with french translations like it says on your webpage.. let me know, i can do it for you.

a stupid noob here from the uk :p:

Purchased this great program using paypal today

BUT how do i get the key to unlock it ?

Just read that i need to wait for an email from your goodself to activate program

I thought maybe paypal generated it :yikes:

The author sits down at his computer, reads the emails and then generates the key and sends it to you.

Turn signals to quick
 

Hi Guys,

Just purchased Navcoder from Jochen, and tested it on a 2001 325CI Cabrio!
The car had installed led taillights (oem) and whas giving messages (warnings) so i could fix that with this nice program!
The only problem i couldnt solve whas the interval from the turning signal, it goes to fast.
Anyone knows the solution for this problem?
Also the taillights flickr a bit, but i'm not the only one :(.

All advices are welcome

Regards

Joël

cheers KiwiJochen


i thought you were the author :dunno:

Any ideas how to contact him as i would love to get the program unlocked as still not got the key

The author :D sent you the registration key on Saturday, 2 May 2009 at 16:06, less than 2 hours after you paid for NavCoder.

To your Msn.com email address.

defo not got it just checked my inbox,junk and deleted emails folders

got the paypal thanking me for payment at 13.43 on 02/05/09


NavCoder v2.6.30 EN RegCode = 332733643346336533333


20.00 EUR
Subtotal20.00 EU
TotalPayment €20.00 EUR
Payment sent to [email protected]
amount £18.29 GBP To amount €20.00 EUR
Exchange rate: 1 GBP = 1.09349 EUR


obvioulsy deleted some of those digits

All sorted now


thanks for the great program :thumbup:

Any idea where can I buy I-Bus physical interface?

certify

try here

IBUS Interface for BMW cars

Thanks!

There are 2 versions? Should we just stick to serial Interface?

it depends on your laptop

i just got the usb version due to all of the new laptops having done away with serial connectors

but they work the same way

IBUS Interface for BMW cars

I find serial interfaces to be more reliable. My older laptop has a serial interface, so I bought the serial adapter... No need to mess with USB drivers etc...

So how would you configure NavCoder to use USB?

the usb version works perfectly

we have moved on from serial ports so why restrict yourself for the future by buying the serial port version

but as they say its your money so its YOUR choice

the site even points you to the website for the latest drivers for usb so you cannot go wrong

And they have used the best usb chipset they could get

I'm in IT so i tend to be pessimistic about anything with cables / connectors etc... I've heard we've "moved on" from many things, yet I still update firmware on RAID controllers with 3.5" floppy disks...

I'm sure the cable is great quality... I'm just a believer in KISS (keep it simple, stupid) and would rather not introduce another variable into the equation (USB to serial interface Windows driver). Haven't checked the link for the USB cable yet, but my immediate thoughts would be: what OS does it support? 32bit? 64bit OS? Win 7 support yet? If not yet, when? All of those questions don't need to be asked with a serial cable... ;)

Jochen,
Feature request:

Get rid of the seatbelt chime! I can't stand that thing... (yes, I wear my seat belt... no, I don't want an ear-piercing chime going off in my ear every time I start the car)...

Here:
Rolf Resler - Homepage

or here:
Elektronik-Idee

IBUS Interface for BMW cars

Hi jochen just purchased navcoder but I ran into trouble...

I used: a resler IBUS interface (serial)
the IBUS plug from the cd changer
an old laptop running xp pro
lastest navcoder

Problem: when I start navcoder and then connect the cable, the program either freezes completely (100% cpu load) or shuts down. Just before shutting down the statusbar says it's communicating with the IBUS ("IBUS status: busy" or "ready") I tried changing the baud rate to different values, changing IRQ of the port, disabling all other ports and hardware I don't need... I tried putting the key in pos 1, without the contact on and with a running car...

Does navcoder produce a crashlog of some sort? Maybe I could post it here for you then...

I'm really running out of ideas :dunno: hope you can help me out...

thx!

What version of NavCoder are you using?
Current version is v2.6.40

NavCoder will log all ibus activity to the Navcoder.log file - send me the log file.

Jochen

thx for the reply jochen...

I run on FW 2.6.40.

The navcoder log file is empty I'm afraid, the only way to get data in the logfile is to disconnect the cable and do a scan. The minute I connect the cable to the system navcoder freezes and crashes... I suppose it doesnt have the time to write a log :(

some pics :

http://i392.photobucket.com/albums/p...bucket/010.jpg

http://i392.photobucket.com/albums/p...bucket/011.jpg

http://i392.photobucket.com/albums/p...bucket/004.jpg


Here's a movie to illustrate wat's going on:

007.flv video

It kinda freezes there and makes a sound :confused: no message or errorcode whatsoever. When I pull the cable out navcoder dissapears and the logfile hasn't been altered...

Hope you can figure it out ;)

Looks like corrupt data being received and the buffer is overflowing, make sure the interface is connecting to a good ground - use a separate ground to the CD changer ground

Please get in touch via email for further diagnosis

Jochen,

Any ETA on when the release with ability to enable VR is coming out?

Thx!

Soon... rewriting the Bluetooth dialog at the mo- would be good if I had some testers....

I'd be happy to test... Unfortunately I don't have TCU to test with. ;) Although someone local in Boston might be buying one soon... I can grab his if need be...

What is the idea behind changing from NTSC to Pal for the reversing camera? Any reason for doing this?

What are the future plans for Navcoder, i.e. what are you looking at getting it to do?

[QUOTE=NBTBRV8;627852]What is the idea behind changing from NTSC to Pal for the reversing camera? Any reason for doing this?/QUOTE]

The function was built in to the video module. NavCoder simply enables it.

Recent work (% complete):
On-Board Monitor Emulator (80%)
TCU coding (60%)
Further LCM options (5%)
Bug fixes with Mk2 nav (0%)

[QUOTE=KiwiJochen;627914]Can I add some suggestions, even though I haven't used it yet (awaiting interface):

• Code CD stacker
• PDC testing of each sensor or look at which sensor is being triggered
• Code TV module
• Program the date format so 12hr clock can display the date in DD/MM/YYYY format.
• Clear phones in bluetooth memory and display phones paired
• Talk to MFSW, but I am not sure what you could do, other than test buttons?

Keep up the good work. When will you be branching out in to the other buses?

I like the idea of the clock as I like the 12h clock but hate having to use the USA date format, its a real pain.

Wish List
 

Interesting questions. Let's go through the wish list:

Code CD stacker
Nothing to code. NavCoder already does all that can be done.

PDC testing of each sensor or look at which sensor is being triggered
Possible. Need some PDC volunteers to supply me data. Will vary between active and passive PDC.

Code TV module
Already built in to NavCoder

Program the date format so 12hr clock can display the date in DD/MM/YYYY format.
Not possible, this function is not built in to the nav.
NavCoder can enable/disable functions, it cannot re-write the operating system!

Clear phones in bluetooth memory and display phones paired
Clear memory? Why? Don't know if this function exists
Paired phones? Maybe. Would need volunteers to send me Bluetooth data.

Talk to MFSW, but I am not sure what you could do, other than test buttons?
A MFL emulator would be possible, with display and emulation of buttons.
This would be quite easy. But won't be anything else than a graphical display of the data already displayed in NavCoder.

Keep up the good work. When will you be branching out in to the other buses?

Well, ibus=kbus...!!
I don't have any info on other busses, so I'll stay with what I know at the moment

KJ

Jochen,
Not sure if it is possible...

Enabling the clock button to toggle between full and split screen would be fantastic...

Yeah....like that idea. A quick means of switching between full & split.

Keep coding!

Not possible without extra hardware in the car!

Just FYI, "...through the normal means" is like this (from ULF user´s guide, p. 16):


The paired BluetoothTM mobile phones can only be deleted as a single group from the ULF control module.




Cheers, KamilFKH

Some notes to NBTBRV8's post:

Coding of MP3 changer: maybe the car simply needs the option code changed to indicate it now has the MP3 player fitted. As the dealer doesn't know what happens when the car is coded, they don't know what devices actually get programmed.

PDC: I've sent you a PM. Some data display would be possible here!

TV module: VIN is not stored in the TV module, AFAIK
Correct me if I am wrong.

Bluetooth clearing of phones: I cannot implement a function in the control unit that doesn't exist. If the control unit has no function to clear the phone memory via diagnostics, then I cannot do it!

MFL: well, I could emulate the Vol-Up, Vol-Down, Search-Up, Search-Down, and R/T button. But not cruise control buttons (because cruise control doesn't go over the ibus).
But how useful would the MFL emulator be?
I think the full monitor emulator is intriniscally more useful, and there you have the Volume and Search controls as well.

Convienience Opening: Again, this is a matter of capturing data and experimenting, for which I need volunteer...

KJ

There must be an electronic switch to clear the paired phones though, as you can do it via the method quoted in an earlier post. I guess you'd need to see what messages the Ibus puts out when you go to clear the phones.

Convenience opening stuff isn't on the ibus though is it? It would be nice.

I think the TV must be coded in a bit more depth than that, as when you move a module from one car to the next you'd have to tell the module it is in a different car, other than the options you've included in Navcoder. I know that when I fitted my ULF before I had it coded to the car it displayed on my phone as "BMW ULF" and then once I got it coded it came up as "BMW XXXXX" with the Xs being the last 5 digits of my vin.

But I have no experience with this stuff, so could be wrong!

You're assuming that the pairing button works via the ibus.
It doesn't - it is a button directly wired to the ULF
You cannot assume that the buttons function can be emulated by the diagnostics.

Another assumption. Some convienience functions are on the ibus, some not.

Why?
NavCoder already codes all the available options (and more!) in the TV module.
what is there in the module that changes from car to car?
Nothing, as far as I know (speaking from experience and from coding memory analysis)

Correct. But that's the ULF, not the TV module.
Different modules, different specifications

I am a bit confused on something. Going to the website I see nothing about registration, but saw a post regarding paypal & registration...
Is the program at all useable without registering? I have no true need for it right now, other then curiosity... I don't want to dig up my dell laptop to find out I cant do anything without throwing the $ out (which I dont mind doing, if I had a reason).
Matt

You can open the app and play around with it, familiarize yourself with the menus etc. No reason not to download the trial version...

Navcoder is 80% free to use, some of the newer features require the software to be registered and TBH for what you get it's a bargain.

The registration is (to me) a thank you for producing and supporting the software, as well as adding new features.

Jochen,
How close are we to getting the TCU voice recognition put into NavCoder?

ibus ?
 

I have been using the v2.7.0 with good results in all my coding changes this is great software :thumbup:even changes to my lcm were flawless.
.My attempts to load some hex code in the ibus message text however was not successful .Do you have a guide to using this part of the software?My project is to find the hex codes for the e53 such as
1 close all windows and sunroof
2 lock doors and set alarm
3 etc etc
Will you help me to learn how to extract these sentences and then how to test them on my ibus with a resulting action?Is your software the right tool for my needs?.....cheers Rondo

Are you blindly reprogramming the car without any clue as to what bit and what byte of what memory location controls what function?

That is very dangerous!

You could upset the vehicle programming and make all sorts of things not work

You approach is similar to trying to change functions in the Windows system registry by using a hex editor to edit random bytes in random files of the PC's hard disc.

To save you and your car, I'm not going to give you the details :-)

Ah - but if you just want to monitor messages and then emulate the same message to emulate a function then that is easy, but be wary that many functions occur through sequences of messages.

But for eg Close all Windows, that should be easy. Just monitor the ibus when you send the "Close al Windows" command from your key's remote, and then analyse the ibus to see where the message was, who sent it to whom and what the devices said, and what the responses were.

Thanks for the reply and i will definitely try not to screw up my cars code registry by doing something wrong ..so far i have basically tried to do what you suggested above .I started the log of my ibus and pushed the remote close button to broadcast the command to"close all windows" .I looked over the log and found the sentences
(7/21/2009 7:38:59 PM.625: 00 04 BF 72 02 CB
7/21/2009 7:38:59 PM.625: GM --> GLO : ChkCtrl Remote Central Locking message: Bit1
7/21/2009 7:39:06 PM.078: 00 04 BF 72 22 EB
7/21/2009 7:39:06 PM.078: GM --> GLO : ChkCtrl Remote Central Locking message: Bit1 Bit5
7/21/2009 7:39:06 PM.109: 72 05 BF 78 00 01 B1
7/21/2009 7:39:06 PM.109: SM --> GLO : Seat Memory, Data="00 01"
7/21/2009 7:39:06 PM.734: 00 05 BF 7A 50 2F BF
7/21/2009 7:39:06 PM.734: GM --> GLO : Doors/flaps status: Open: WndwDvr WndwPgr WndwDvrRr WndwPgrRr Boot Ctrl_Locking: Unlocked
7/21/2009 7:39:07 PM.468: 00 04 BF 72 02 CB
7/21/2009 7:39:07 PM.468: GM --> GLO : ChkCtrl Remote Central Locking message: Bit1
7/21/2009 7:39:30 PM.140: 00 04 BF 72 22 EB
7/21/2009 7:39:30 PM.140: GM --> GLO : ChkCtrl Remote Central Locking message: Bit1 Bit5)
etc etc if i then copy and paste one of the command lines eg. 00 04 BF 72 02 CB then send this on the bus it seems to be acknowledged but no action to door locks? I am in need of more help to understand .....cheers Rondo

@kiwijochen: on what cars should DRL work? is there any limitation?

You're doing the right thing

You now need to analyse the sequence and determine what command is controlling the windows.

Keep analysing and testing until it becomes clear what does what.
That's exactly what I do.

I cannot offer any more advice without a full log file for analysis, supplied together with a timeframe of what you where doing when

eg:
prepare the car and NavCoder and a watch and notepad, maybe with a second person.
At a certain time, lock the car and close all windows. Note the time you pressed the button initially, and note the time the windows started closing. You need to note the time down to the second.
Wait a few minutes for the ibus to stop talking.
Then save the log file, and save your notes.

Do the same again for unlocking and opening the windows.

Then compare notes and logfile, look at what time you noted that you sent the command, what time the windows started closing, and match to the corresponding commands in the log file.

Look carefully at the sequence of events.

To emulate the Window Closing command, you may need to emulate a sequence of commands - I am not sure as I don't have a log of this.

And when you are finished, tell me the results and I'll update NavCoder :-)

Yes, there are limitations.

Cars with LCM_I have no DRL capabilities (CI 14...17)
This means cars prior to Sept 1998, I believe

Cars with LCM_II onwards can have DRL capabilities (CI18...)

But NavCoder only understands LDRL coding up to LCM coding index 30, because DRL was changed in CI31

Hi johan thanks for your advice this is my log as you suggested .I have edited the file and with some study begin to see some order to this.I would like to have your input as to what you think the complete sentence for #1 lock car and #2 close windows & sunroof
cheers Rondo

Unfortunately nowhere in your log file you identify the timestamp where the windows started opening.
Using the window switches to open windows does not send any control commands over the ibus, it just sends a status update of windows/doors.

You need to open the windows with the remote (and NOT with the window switches) - then, the GM should instruct the window module what to do.
HOWEVER: we may not see anything... because I think the window module is not connected to the ibus.

The remote operates in 2 stages:
Stage 1: unlock car
Stage 2: open windows (after a few seconds with the button remaining pressed all the time)
You need to identify in the log the times when Stage 1 occured (easy) and when Stage 2 occurs (take notes, use stopwatch...)

Try again...

PS: at least your log files helped somewhat. I have now added message 0x73 to my list of known ibus message types.
0x73 = "Immobiliser status request"

:-)

Hi Jochen, would it be possible to add support for the Intravee II so that we who have them can use it as an I-bus interface, I think that the serial interface speed would need to go up to 115,000 to be able to use it.

I'm happy to test it all for you.

What do you mean?

Use the intravee interface as an ibus interface, with COM port set to 115,200 baud?

PM me for details...

KiwiJochen,

I had this same question on the Intravee II forums. Is there a way to configure the SW?

Thanks,

Tee

PM please.

Hi,

I have a bmw m3 of 10/2001. I mounted the LED rear lights. is possible encoding the LCM and turn off the alarm?

The DRL on my car is available?

Hi Jochen, all.
Just FYI (E38 and E39 cars):

LCM with CI:16 is already LCM2 (no known DRL settings for me, rumours goes it can be set after algorithm change)
LCM with CI:17 and CI:18 are LCM3 (working DRL)
LCM with CI:20 is LCM4 (working DRL but different setting values than for CI:17-18)

KamilFKH

What about LCM with: 6907948, HW10, SW20, CI29, may 2001?The car is E46.

I tried to code DLR, but no success.

Thanks, CI29 must be the same as CI30, I'll ad that to my notes.

Light modules with CI:26 to CI:29 (CI:30 maybe as well I do not know right now) are not LCM (Light Check/Control Module) anymore but are called LSZ (I think it is Licht Steuerung Zentralle - Light Control Central but no warranty). There is a change to LCM in module behaviour according to taking some of the coding in account. When LSZ module is coded to ECE region no US setting works and vice versa when LSZ module is coded to US region no ECE setting works.

I have ECE E46 with the same LSZ (PN too) CI:29 as You have and ECE_DRL should work for You with ease. Definition: Light switch at pos. 2 and ignition OFF causes all lights go off (no position lights)

The only way to get US_DRL working (Def: High beam with 18% intensity) on ECE car it that the LSZ must be coded to US region, as far as I know. You must manipulate/change ZCS to code LSZ from ECE to US and the whole process takes me over an hour to do it.

For LSZ2 (CI:31 and up) it is again possible to code ECE and US DRL together.

How can i do this?
Do you mean to pay or is this doing for free?

Do what mate?

How can i have Navcoder for free?

Download it from the navcoder web site and install it, most of it will allow free use, only some things require you to register (and pay).

Clicky

If you are asking where to get a fully functioning copy "free" then I don't know (I'm happy to pay Jochen for his effort).

I can do this for you as follows in 3 easy steps:

1. You send me 20 Euros, just for fun

2. I'll send you a registration key free of charge, subject to Step 1

3. Voila! NavCoder for free!

@KiwiJochen, you made me laugh :)

Thanks a lot

You will need an interface, either a Resler or one you make yourself.

I was all excited to use NavCoder to program my LCM (LSZ) on my 2002 325ci but after getting the resler interface and hooking it all up, it said LCM coding index must be <= 28 and mine showed up as 31! :(

Is there any chance of getting this working or should I just give up?

Yes there is, but my friend with his E46 is very busy this week. I need to spend some time on his E46 to analyse his software and coding...

Ok, well if you need another tester let me know.

2.7.25 - User Interface changed a bit?
 

Hi Jochen,

Not sure I like some of the changes over 2.7.0 :(

In Code Telephone, the 'Read BT' doesn't read the SES coding status, nor does it read the SDV settings. And there is no longer a button to READ these settings. Is this a deliberate change or an issue?

Cheers.

Hi trapdoor,

Functionality is the same - but due to the differentiation between TCU and ULF I had to change the way it did things.

Now you Read ID, then it determines what TEL is fitted, then you can code accordingly.

Work OK for you?

J

Hi Jochen,

OK, understood. But the Read ID determines the module - doesn't populate any of the programmed fields though. The Read BT reads and populates the Bluetooth ID, pairing code and emerg. number, but doesn't read or display the SES status (enabled or disabled). Also doesn't read the SDV settings.

Is there a way that you can re-implement the READ coded settings? Was really handy to know what had been previously set.

Thanks,

Mark.

Sorry, My TEL dialog is very unfinished - I forgot because I was working on PDC functions, and my TEL testers deserted me....
I've been working furiously on it

The goal is as follows:
1. Read ID determines TEL type
2. Then you Read ULF / Read TCU to read all the settings
3. Only then can you edit settings and Code ULF / Code TCU

Jochen,

Just on the PDC, I haven't forgotten about you and will get to look at it again in early November. Also this thread's title is saying that 2.7.25 is out, however your website is still showing 2.7 as the download. Is this correct?