I put it near the pedals. Because I got the 12v from the fuses. OP?Read the OPs.
Mine is behind the glovebox.
I put it near the pedals. Because I got the 12v from the fuses. OP?Read the OPs.
Mine is behind the glovebox.
What is the BCM part number. My understanding is facelift BCM (no long coding) can have software upgraded to go from 10 color slider to 30 color slider.Hey, Just wanted to know Is it possible to flash the BCM to a newer software and get the color slider in the MIB, then you can just use a kit like IWMTom Used and set it to work via the MIB slider.
5Q0937084ABWhat is the BCM part number. My understanding is facelift BCM (no long coding) can have software upgraded to go from 10 color slider to 30 color slider.
But there was no way to get the slider on my pre-facelift BCM (high). Contrary to what is always said, it did actually support RGB lighting (with a drop down) but overall RGB ambient functionality is limited compared to a facelift BCM... see my now (somewhat abondoned) thread here... https://www.golfmk7.com/forums/inde...ighting-hopes-dreams-pre-facelift-mk7.392316/
In the end I opted to retrofit the facelift BCM.
No pin 29 unfortunately, I Attached an old admap of my 09 module, made a lot of changes since but it was on my pc so it was easier to just upload it.So you don't have pin 29 on plug C, is that correct? If you have VCDS post and adaptation map of your BCM. I'll be able to see if you can enable the slider.
Also the BCM has no parameters. It's just long coding and adaptations for a pre-facelift. And it's all adaptations on a facelift BCM, the long coding will be all zeros.
I see, But with the decoder they sell on aliexpress, why would you retrofit a facelift BCM, If i'm not mistaken I read that your Pre facelift one has the slider and areas, just use the decoder and skip all the hassle.I assume this is from OBDEleven... their "ad-map" format is formatted so poorly that's practically useless (not saying that's your fault, it's their fault, haha). Is this a highline BCM?
Anyway, quite a few things that suggest no RGB ability with your current BCM
Looks like you'll be retrofitting a facelift BCM, welcome to the club
- No LIN slave module channels, which makes sense if you don't have Plug C pin 29, because there would be no place to connect the LIN modules (LED's) anyway.
- There is no RGB/LIN-RGB color lists which means no slider (like my pre-facelift BCM).
- No verbauionformation_HMI or ambienteumfang_mehrfarbig_HMI which means there is no way for you to set different zones to show lighting.
- Best explained here... https://www.drive2.ru/l/600455120752220083/
- You also don't have parameter-p_farbauswahl_HMI which let me enable a color drop down on my pre-facelift BCM
- That BCM could not do the slider but could do the dropdown... but I also had Plug C pin 29 and the above mentioned channels
- This is the coding for the drop-down channel... https://golfmk7.com/forums/index.ph...s-dreams-pre-facelift-mk7.392316/post-7775656
https://www.golfmk7.com/forums/index.php?threads/retrofit-of-facelift-bcm-into-pre-facelift-mk7-in-progress-please-help-.397618/
Are you sure about the pre facelift BCM not being able to be used with a decoder in the OEM style?(Through the MIB screen)As to why retrofit a facelift BCM...
- I suppose there's some hassle there, although it's made much easier if you have a bench setup and can do all the adaptations sitting at a desk/table instead of in the car.
- Beyond the adaptations, BCM only has component protection to consider. No parameters or FEC/SWAP codes.
- I like doing things as OEM-ish as my ability allows (one thing we didn't mention is that the screen with lighting/colors has to be supported in your in mib firmware as well)
- For this retrofit the door card modifications were/are the biggest hassle, to me, and is a requirement no matter which way you go.
- if you decide to waste some of your time looking at my build thread, you'll see that "hassle" hasn't stopped me from doing anything yet
Well, I will give It a shot, BCMs are pretty inexpensive on ebay so after the backup arrives I will try what the seller says.I'm on my 4th BCM. The BCM has no dataset or parameters. It does of course have a firmware. And later firmware will have different options. All firmware is of course not compatible with all BCMs. And firmware that depends on certain hardware being present in the BCM is not going to be compatible with a BCM that doesn't have that hardware.
For example, the BCM that came in my car did not have the pins for heated seats or fog lights. And so it also did not have those adaptations. Firmware with those adaptations was not applicable.
On the other hand, firmware updates to early facelift BCMs increased the number of possible colors from 10 to 30... but those early facelift BCMs already had the hardware.
All that being said, trust and believe whoever you want. I don't know what is meant by "unlocked" adaptations using ODIS-E. You can set ODIS to ignore the hardware number of a module when trying to load firmware to it. This will let you load any firmware you choose, which may or may not brick that unit. I can't say I have any interest in that. But I suppose that could let you load firmware that has adaptations for functions your BCM doesn't actually have.
My prefacelift BCM had the latest software available for its hardware. And as I mentioned in my thread, I had most of the adaptations for RGB lighting, although I did not have the ability to use the slider. Just the drop-down with a selection of set colors (from memory, white, warm white, red, blue, green, orange, turquoise). Maybe I could have loaded "incompatible" firmware (incompatible in this case meaning firmware not intended for my BCM ) and got the slider. Maybe it would have worked because my BCM did have the hardware. That's an unsolved mystery.