iBUS installation location

[PropellerHead]

Originally Posted by Crowz

So if a device at the middle of the bus is chattering there is a chance a device closer to the controller might get more data to the controller non corrupted vs being after the bad device. But the real solution is to fix the bad device to have a healthy bus.

This is why I want to move to the LCM. I mean, we're working on finding the offending device. Lord knows. But it's not a terribly tough itch to scratch (thanks to you guys in this thread) so I wanna see if it'll improve if relocated.

Or, if the guys figure out what the hell is happening and fix the chatty Kathy device, I'll probably just leave it the way it's worked for the past year.

[mr_robot]

Originally Posted by PropellerHead

Is the Avin set up to use the interface and is already tapped in to the harness? If it is, I'd say use that and see how it works. I'm only planning on the LCM connection to satisfy a curiosity and address a functional issue. If I got an Avin, and it's supposed to work the way they provide it, I'd hit that first. Unless I have the wrong idea of how it's designed.

Yes AVIN Harness comes already tapped in and has the connector plug on it already so for those without factory nav it would have been a true plug and play.

[V8 00USH]

I tapped into the connector behind the OE dash monitor for my IBUS connection - works flawlessly.

[bcredliner]

I had the MK4 unit and do have DSP. I now have the Android based Seicane unit still using DSP. I have the IBUS adapter connected to the USB port in the back of the unit. I had it connected to a USB hub that I have in the second USB port on the unit. Both setups work fine.

[PropellerHead]

Originally Posted by V8 00USH

I tapped into the connector behind the OE dash monitor for my IBUS connection - works flawlessly.

Well, I got the X5 back in play after a LOT of search and effort, but like all good E53 owners, we know the fat lady ain't sung. So, I am watching and waiting.

My theory evolved to proving a module on the bus was chatty and causing 'noise' that kept the IBus interface from talking to the LCM. While I did order ride height sensors, I only ordered one front and rear so we didn't put 'em on.

I decided not to change *anything* with the iBus connection for this next move so I could discern if a failing iBus interface was the *cause* of all the SLS errors I'd been having. I figured if the interface even worked, it would tell us that the pump we replaced was the chatty Kathy on the bus.

But the 'refurbished' eBay pump is in the truck. This may have been the culprit. The ride is now *much* more subtle, even lowered.

The radio had been disconnected this whole time. I simply pulled the fuse I'd tapped for the iBus Interface- it was the same as the radio. I'd ordered 2 Reisler's for this project before we picked up the white one. (or even *knew about* it) Turns out I didn't need either one of them. When I returned home this morning after all the work, I plugged in the radio, navigated to the app and attempted to register. While it had failed with the SLS errors, it went through today!

My iBus interface is back with full function! I was even able to connect and program the LCM. Also, the app is communicating to the LCM to power AEs and fogs as DRLs. And the only thing I changed was the OE EHC air pump. Let's see how long it lasts!

[Crowz]

Originally Posted by PropellerHead

Well, I got the X5 back in play after a LOT of search and effort, but like all good E53 owners, we know the fat lady ain't sung. So, I am watching and waiting.

My theory evolved to proving a module on the bus was chatty and causing 'noise' that kept the IBus interface from talking to the LCM. While I did order ride height sensors, I only ordered one front and rear so we didn't put 'em on.

I decided not to change *anything* with the iBus connection for this next move so I could discern if a failing iBus interface was the *cause* of all the SLS errors I'd been having. I figured if the interface even worked, it would tell us that the pump we replaced was the chatty Kathy on the bus.

But the 'refurbished' eBay pump is in the truck. This may have been the culprit. The ride is now *much* more subtle, even lowered.

The radio had been disconnected this whole time. I simply pulled the fuse I'd tapped for the iBus Interface- it was the same as the radio. I'd ordered 2 Reisler's for this project before we picked up the white one. (or even *knew about* it) Turns out I didn't need either one of them. When I returned home this morning after all the work, I plugged in the radio, navigated to the app and attempted to register. While it had failed with the SLS errors, it went through today!

My iBus interface is back with full function! I was even able to connect and program the LCM. Also, the app is communicating to the LCM to power AEs and fogs as DRLs. And the only thing I changed was the OE EHC air pump. Let's see how long it lasts!

Sounds like you found what was messing up the bus. Glad it worked out.

[PropellerHead]

Originally Posted by Crowz

Sounds like you found what was messing up the bus. Glad it worked out.

If only it were that easy.

Of course, after the 1st 20 minutes of use above, I see that all is not well. Obviously, I've changed the necessary setting to enable the features below that are custom. For example:

• Outdoor temp show correctly at startup- 59 degrees or so. After a little bit, it reports 146 degrees.
• MPG 1 and 2 are not reading on the display.
• No data on distance to empty on display.
• Custom welcome message on MID shows for a short second and disappears. It's set to max time- like 5 seconds I think. MID does not display after that until the stalk is pressed.
• PDC distance does not display in the MID like it did before.
• Doors are not unlocking when e Brake used nor car in park.

So, tomorrow, I will replace the Reisler interface to see what changes that affects.

[kiwicossie]

Hi All, New to the Xoutpost after purchasing an 03 4.6is Estoril beast.
I've been reading lots of your helpful posts trying to fix a bunch of things: floppy mirrors, broken window regulators, broken sunroof etc etc.
I have however recently fitted the Avant 4 into my machine and have been trying to get some of the issues you speak of sorted also.
The install took me two days which included wiring for a front and rear camera as I had Nav. I've found that some of the features dont quite work as advertised also. I have contacted the ibus peeps and have a reply for some of the issues but not yet all. I found that setting the code oem feature messed up the outside temp. I also have an issue with consumption. I wanted km/l. the stereo shows this, the car does not. If I code oem then the stereo shows the corrected value. If I dont code it then it shows the value for l/100 but with the km/l units. Strange. I have the ibus unit hooked into the previously mentioned main loom situated directly behind the stereo. I have had zero issues with it talking to the car.
So far I have found this stereo to be pretty good. While it was an aZZ to fit it was much less work than what I have done on my E39 which is relocate the factory stereo into the boot to keep the obc going.
Looking forward to reading more useful posts and perhaps contributing more as well.

[wpoll]

Welcome, kiwicossie !!

North or South?

I've noted that it isn't possible for the E53 BC to display fuel consumption figures in km/l, only in l/100km. It may be that you cannot get the car BC (now only on the dash) to display l/km, even if the iBus app can do so on the android H/U. It'll be hard coded this way in the IKE.

Took me a month or two to get used to thinking in l/100km rather than l/km but four years later I don't give it a second thought - in fact km/l are now nearly meaningless to me...

[Emory39]

I have it behind the dash. it works but sometimes it takes a while maybe 5 min for the data to pass to the screen