Intravee Latest Firmware 6.02-7035

X MAN · Post by **X MAN** » Sat Jul 20, 2013 11:54 pm

[quote="RichardP"]
Do both upper and lower rear lights work, or just the upper ones?
[/quote]

On mine if selected both upper and lower illuminate together or individually with firmware - V6.02-7044

RichardP · Post by **RichardP** » Sun Jul 21, 2013 7:18 am

[quote="psychosis"]
One (possibly silly question) - Is it possible to only have these lights come on if its dark? I'm sure the intravee shows the status of the light sensor somewhere. No big deal but for me would be the finishing touch.
[/quote]
It is possible, but there is a big problem.

The message that controls the lights has a part the sets the cluster illumination level. When this is set using the message it's then impossible (at least with current knowledge) to determine what the level should be and adjust it. So, while the lights are under Intravee control the cluster brightness is fixed.

RichardP · Post by **RichardP** » Sun Jul 21, 2013 7:22 am

[quote="jaynana"]
Richard, any chance of getting the Auto Close to work on the facelift?

It still doesn't work..
[/quote]
As it's not been tried it is disabled for the X5.

You could try setting the car type to E38/E39 and see if it works. It is quite 'fussy', so you would need to make sure the ignition has been fully on shortly before trying it. Best to disable other things before trying it too, E39 mirror folding commands cause the windows to open on the X5!

If E38/E39 does not work then it will require someone with an X5 to find out what the commands are either by trial and error (which can cause all sorts of odd things to happen) or by logging INPA using an OBD port splitter and NavCoder.

RichardP · Post by **RichardP** » Sun Jul 21, 2013 7:23 am

[quote="X MAN"]
On mine if selected both upper and lower illuminate together or individually with firmware - V6.02-7044

[/quote]
Is that a facelift or pre facelift X5?

X MAN · Post by **X MAN** » Sun Jul 21, 2013 10:06 am

[quote="RichardP"]
[quote="X MAN"]
On mine if selected both upper and lower illuminate together or individually with firmware - V6.02-7044

[/quote]
Is that a facelift or pre facelift X5?
[/quote]

Facelift X5 (2005)

jaynana · Post by **jaynana** » Sun Jul 21, 2013 10:28 am

[quote="RichardP"]
[quote="jaynana"]
Richard, any chance of getting the Auto Close to work on the facelift?

It still doesn't work..
[/quote]
If E38/E39 does not work then it will require someone with an X5 to find out what the commands are either by trial and error (which can cause all sorts of odd things to happen) or by logging INPA using an OBD port splitter and NavCoder.
[/quote]

Richard, i'm all in for a bit of research - no clue on how to though, so you'll have to tell me what to do..

i do have the software, happy to buy a port slitter if that's not obscene money.

safe to give it a try?

psychosis · Post by **psychosis** » Sun Jul 21, 2013 10:44 am

Just checked to make sure I'm not giving duff info. This is with 7044

Entry/exit with intravee setting - top part lit.

Car lights on - both parts lit

And finally parking light on with indicator - only top lit.

This is with a facelift 04 (Manufactured Dec2003 according to sticker under bonnet)

RichardP · Post by **RichardP** » Sun Jul 21, 2013 12:26 pm

[quote="jaynana"]
Richard, i'm all in for a bit of research - no clue on how to though, so you'll have to tell me what to do..

i do have the software, happy to buy a port slitter if that's not obscene money.

safe to give it a try?
[/quote]
Trying speculative commands can cause odd things to happen, but should not have any permanent effect.

Logging INPA commands will not cause any problems, but you will need the splitter, two OBD USB cables, INPA and NavCoder.

This is a splitter http://www.ebay.co.uk/itm/16-pin-OBDII- ... 2c6dfcabc3

You then connect one port to NavCoder and set it to log, the other port to INPA. Use INPA to test the comfort closing feature or the key buttons. The NavCoder log will then contain the commands that are used on the main K-Bus for comfort closing, these can then be used to determine the possible iBus commands.

jaynana · Post by **jaynana** » Sun Jul 21, 2013 5:07 pm

thanks, that cable is ok, but then i need another OBD USB cable? i presume this type which is for the vw family wouldn't work. it's got to be one of these?, which is packaged with software and is more expensive >:(

RichardP · Post by **RichardP** » Sun Jul 21, 2013 5:28 pm

To be quite honest, I don't know exactly what the spec of the second cable needs to be, I've used BMW specific cables but the VAG one may be good enough for the 2nd cable.

I believe it is quite easy to modify the VAG cable to a BMW version.

http://forums.m3cutters.co.uk/showthread.php?t=24898

RichardP · Post by **RichardP** » Mon Jul 22, 2013 10:04 pm

I've set up a DropBox folder into which I'll put Intravee firmware which you can access without joining BMW5.

The link is here.

I'll create a new sub-folder for each release which will contain the firmware and various documentation.

Newest version is 6.02-7045.

Let me know if you have any problems with the link.

DoubleM · Post by **DoubleM** » Sun Mar 02, 2025 1:49 pm

Hello @RichardP,

I registered to just "unbury" this thread and hope you are still here.

First I want to thank you for the effort and the Link to the newest Firmware, which after all these years, still works.
I got my Intravee updated to the latest one (6.02-7059)

All the new functions work (especially the automatic rear Parking distance view is very helpful beside the other new things.)

But:
I want to report an issue with the actual speed (which is also saved in the "latest trips log").
It is way to high (like ~200km/h when the real speed is like 50km/h)

My car is a 2005 E46 M3 (car type setting shall be correct) - may it be, the "Ms" are handling the actual speed differently to the "normal" ones?

Is there any chance to further investigate or even fix this? - I am willing to help with everything I might provide.

Another question:
Do we need to bother because of additional writings to the Intravees Memory?
Logs and so on, which did not be there in the original version ...just thinking of issues if the maximum write circles are reached and the internal memory might break (see early tesla issues a couple of years before)

Best regards!

RichardP · Post by **RichardP** » Sun Mar 02, 2025 6:50 pm

DoubleM wrote: Sun Mar 02, 2025 1:49 pm I want to report an issue with the actual speed (which is also saved in the "latest trips log").
It is way to high (like ~200km/h when the real speed is like 50km/h)

My car is a 2005 E46 M3 (car type setting shall be correct) - may it be, the "Ms" are handling the actual speed differently to the "normal" ones?

Is there any chance to further investigate or even fix this? - I am willing to help with everything I might provide.

That's quite strange, nothing has changed in decoding the speed pretty much since it was implemented and I know that it has worked in other E46 M3's. I can take a look at an iBus log to see if I can figure out why it might be coming up with the wrong speed, but can't guarantee anything. It's been quite a while since I last compiled the firmware, with several computer changes along the way, so I'd have to try and remember how to do it!

DoubleM wrote: Sun Mar 02, 2025 1:49 pm Another question:
Do we need to bother because of additional writings to the Intravees Memory?
Logs and so on, which did not be there in the original version ...just thinking of issues if the maximum write circles are reached and the internal memory might break (see early tesla issues a couple of years before)

You are quite right that flash memory does have a finite number of writes, and eventually some of the bits will fail. From memory I think the flash in the ATMEL CPU in the Intravee was rated at 10,000 cycles which is not a lot, but the amount of information written to the log is not a lot either, certainly many orders of magnitude less than the Tesla logs. The log entry is only written once per journey, off the top of my head I can't remember how many entries there are, but if there were 20, that would be 200,000 journeys worth. Even then some of the data would be the same, so the bit value would not change and thus would not count as a cycle. So I think it's likely to see the car out!

X5Sport · Post by **X5Sport** » Sun Mar 02, 2025 8:12 pm

Thank you for responding Richard. It’s fantastic when old faces resurfaceto help newbies.

DoubleM · Post by **DoubleM** » Mon Mar 03, 2025 12:20 pm

Thanks a lot, happy to see you resopond - I am settled a bit for the write cycle topic.

Got my Intravee already in ~2012 or so - mainly to integrate the Alpine CD Changer, but updated to your latest version only a couple of weeks before.

I will be happy to provide a log.
I remember some setting in the diagnostics menu to activate debug info logging.
If you might instruct me, how to export / get it from the intravee once I did a trip with log activated?
(Since I am newly registered I can not yet write any PN messages or at least not initiate one, to keep this thread nice and clean)

But dont feel forced to help or have a look into it.
Being a SW Developer too, I know the time effort may quickly "explode", especially for such legacy stuff.
If you say: "go away, I will not support anymore" I could accept that.

XSeries-forum

XSeries-forum