OK, I've finally decided to try and get this nailed, as it's annoying me that the Bolero's sat back in a box, taunting me

My coding, as it stands - Stream fitted. I have these incorrect coding issues in any case, which concern me, but doesn't seem to have caused any Stream operation issues. I believe the previous owner may have had a Columbus installed. I don't know to what extent this was coded correctly though, which may explain the coding errors:

Address 56: Radio Labels: 1K0-035-1xx-56.lbl

Part No SW: 1Z0 035 161 B HW: 1Z0 035 161 B

Component: Radio FO3 013 0028

Revision: 00013000 Serial number: <removed>

Coding: 0010400

Shop #: WSC 00000 000 00000

VCID: 2D5ABE4DCD97

2 Faults Found:

01044 - Control Module Incorrectly Coded

000 - -

01042 - Control Module; Not Coded

000 - -

And looking at the info below, it would seem that my pre-existing coding should read 402, not 10400.

Info from another Octy2, with Stream:

Address 56: Radio Labels: 1K0-035-1xx-56.lbl

Part No SW: 1Z0 035 161 B HW: 1Z0 035 161 B

Component: Radio FO3 013 0028

Revision: 00013000 Serial number: <removed>

Coding: 0000402

Shop #: WSC 17016 576 00589

VCID: 2D5ABE4DCD97

So basically what I'm after is a coding export from someone with VCDS, who's retrofitted a Bolero to a non-FL. Please don't post up coding for cars that have had the Bolero factory fitted

Screenshots from the long coding screens would be very helpful too, if possible.

Hopefully then I can get to the bottom of why I got battery drain from fitting it, even with a later revision gateway. I'm dearly hoping it was down to a coding mis-match!

Thanks,

Steve.

You can take a look at my coding if you want - happy to meet up early one evening?

Mike Holroyd may have kept a copy of the coding on mine as it has had Nexus, Stream MP3 and now Bolero fitted.

But my Bolero is a really late model one so I have the dreaded dim screen and the volume controls on the MFSW don't work with it (but the next/prev track do!)

I had battery drain until I fitted the later gateway in mine.

Nexus

Address 56: Radio Labels: 1T0-035-095.lbl

Part No: 1T0 035 095

Component: Radio 0311

Coding: 0003400

Shop #: WSC 01324 785 00200

VCID: EBDE435CB3F7

No fault code found.

Stream MP3

Address 56: Radio Labels: 1K0-035-1xx-56.lbl

Part No SW: 1Z0 035 161 C HW: 1Z0 035 161 C

Component: Radio FO3 019 0040

Revision: 00019000 Serial number: SKZ7Z3G0159294

Coding: 0000402

Shop #: WSC 17023 123 94146

VCID: 2E580A48C091

No fault code found.

Don't seem to have a log from the Bolero coding though - it didn't seem that hard to do when Mike coded mine!

Can someone sort the formatting out!

Copying and pasting from Wordpad did the trick

Edited 5 July, 201114 yr by andyvee

Thanks Andy. I never needed to change any coding with my old Octy when I put a Bolero in, so hoping that now I've changed the gateway and correct those incorrect coding problems present, it should work as intended :yes:

Thought Mike might have some coding saved from a Bolero coding actually, so I'll give him a shout. I can have the car safely off the road later this week, so might alter the coding, see if I can get rid of the errors, then re-fit the Bolero. Then at least if it goes 'Pete Tong' again, I'm near a trickle charger and mains power

Cheers,

Steve

OK, put Bolero back in tonight. Checked for fault codes directly within 56 once it was in and it came up with 4 issues. AUX-IN, antenna, parking aid and module incorrecly coded.

I corrected the first three in coding, as I don't have an AUX port so disabled that option, disabled the parking aid option as I know I won't get the info on-screen and I've fitted the Fakra dual aerial adaptor so was confident that won't re-appear when I cleared down the codes.

That all went to plan, but I'm still left with one error code, the annoyingly vague 'incorrectly coded module' issue :S

Address 56: Radio Labels: 5M0-035-1xx-56.clb

Control Module Part Number: 1Z0 035 156 F HW: 1Z0 035 156 F

Component and/or Version: BOLERO 007 0040

Software Coding: 010004000001

Work Shop Code: WSC 73430 790 00999

VCID: 356A962D25D1

1 Fault Found:

01044 - Control Module Incorrectly Coded

000 - -

Freeze Frame:

Fault Status: 01100000

Fault Priority: 5

Fault Frequency: 1

Reset counter: 66

Anyone have any bright ideas on that one. And crucially, whether it will cause any issues - mainly battery drain?!

I noticed a 1044 was logged against the radio section when I ran a scan on VCDS before removing the Stream. Don't know if that has any relevance.

Will wait 24hrs with the Bolero in the car, and see what life there is then - and whether it's taken all the battery charge

Cheers,

Steve

Nope, battery drain again!

Back the drawing board, but running out of options. Maybe the Bolero upgrade is just not meant to be.....

Seems a bit odd if you have upgraded the gateway?

Had no battery drain issues at all with mine on a 2006 MY that originally had a Rev F gateway after the gateway upgrade - is the CAN gateway coded correctly?

Have you got anything else fitted that integrates with the HU that might be causing it? (Hands Free, MDI, Fiscon, Dension etc)

I removed my CDC as we couldn't code the 'new' (2010) Bolero to accept a CDC - it just kept throwing up an incorrect coding error or something like that.

Happy to meet up next Sunday if you want to take a look at my coding.

Here is mine from 6/2010

Address 56: Radio (J503) Labels: None

Part No SW: 1Z0 035 156 G HW: 1Z0 035 156 G

Component: BOLERO 013 0029

Revision: -----27S Serial number: SKZ4Z3K1102933

Coding: 0D0004000001

Shop #: WSC 73430 790 00000

VCID: 366824867E1D6BAC

Hope can help

Seems a bit odd if you have upgraded the gateway?

Had no battery drain issues at all with mine on a 2006 MY that originally had a Rev F gateway after the gateway upgrade - is the CAN gateway coded correctly?

Have you got anything else fitted that integrates with the HU that might be causing it? (Hands Free, MDI, Fiscon, Dension etc)

I removed my CDC as we couldn't code the 'new' (2010) Bolero to accept a CDC - it just kept throwing up an incorrect coding error or something like that.

Happy to meet up next Sunday if you want to take a look at my coding.

Thanks Andy. I'm left baffled as the only issue remaining is that 'controller incorrectly coded' message. I cannot see an issue anywhere.

Nothing else additional fitted - for exactly that reason, to prevent further complications. I do still have my CD changer connected up, and that was working fine when I test-fitted the Bolero again last week and left it to see if battery drain would occur. Played correctly from the changer, came up as CD7-12 on the display etc.

On the gateway upgrade, I carefully took screenshots and current coding from the existing, before swapping them over. And I checked through the coding again last week. But I suppose I could have missed something.

Will give you a shout later in the week, thanks for the offer. Just don't know if I'll be free next Sun or not.

Here is mine from 6/2010

Address 56: Radio (J503) Labels: None

Part No SW: 1Z0 035 156 G HW: 1Z0 035 156 G

Component: BOLERO 013 0029

Revision: -----27S Serial number:

Coding: 0D0004000001

Shop #: WSC 73430 790 00000

VCID: 366824867E1D6BAC

Hope can help

Thank-you

Steve, looking at the problem with regard to your suspicions that the previous owner may have had a Columbus fitted, I swapped the Bolero for the columbus and it did not need any coding, it was just a straight swap. You are more thn welcome to have a look at the coding on mine if that would be of any help to you

That did cross my mind, but seeing as it was an old revision CAN gateway fitted, I suspect that it was running the old firmware and map versions on the Columbus, which avoided battery drain on the older modules.

Doesn't help me much now unfortunately...

Plus yours is an FL, so yes - straight swap

Steve

Here was my scan retro fitted Bolero into my old 2008 Octavia vRS.

Address 56: Radio (J503) Labels: 5M0-035-1xx-56.clb

Part No SW: 1Z0 035 156 F HW: 1Z0 035 156 F

Component: BOLERO 008 0053

Revision: 0A001001 Serial number: SKZ1Z3I81XXXXX

Coding: 050004000001

Shop #: WSC 73430 790 00000

VCID: 356A313425C7

But it was a straight swap as the gateway was a Q

#Address 19: CAN Gateway Labels: 1K0-907-530.lbl

Part No SW: 1K0 907 530 Q HW: 1K0 907 951

Component: J533__Gateway H16 0202

Revision: H16 Serial number: 2700K086090CF6

Coding: E9807F0E0002021303

Shop #: WSC 73430 790 00000

VCID: 356A313425C7

Had the dim screen issues tho

HTH

Andy

Thanks

Taking another look at it tomorrow :yes:

I have access to VCDS at the mo so can take a look tomorrow.

Although I have been playing with my Bolero a bit, and also I have one of the later Delphi? models where the screen is dim unless you turn the headlights on. I am seriously considering activating Scandinavian DRLs just so I can read the stereo screen

Can staging be activated on the instruments on a 55 plate L&K???? - I know this is off topic

Think mine might be a later unit too, but not had it in long enough to confirm the 'dimness'

Staging - no, only FLs.

Damn - flicking the sidelights on and off will have to do then!

Remind me again Mike - where did you get the Columbus from? How good is the TMC traffic on it?

Columbus came from Multims in Manchester. Their website seems to be down at the minute but I'll PM the phone numbers to you.

The TMC traffic seems really good, never seen a problem with it so far, and it has always flagged up a traffic problem if it finds one on route. Just coming back from Whitby yesterday it detected a 6 mile queue near York, and immediately recalculated a diversion route without prompting.

Mike

Cheers Mike - this might be on the cards then in the not too distant

Thanks

Taking another look at it tomorrow :yes:

Thanks again for your help on this yesterday Mike. Will keep the thread updated as to whether the coding alterations have worked

Least I have a confirmed way forward, if it turns out the Rev K gateway is NOT suitable long-term

Cheers,

Steve.

P.S. rear arch still rattling... will try to have the wheel off one night this week and see if I need to replace the arch liner.

What did you have to change? And did you sort out the dim screen issue? I have been digging through VCDS and can't see anything that might help with it - in fact if I turn the headlights on and then off I can see the screen dimming value change from 0 to 100% (or the other way round) so the HU is aware that the headlights are off. It looks like it is trying to take an ambient light measurement from somewhere in the day, but my car obviously doesn't provide it!

The later Bolero's also look like they have an extra set of CAN Bus connections on the back??? There is no pin out label on mine so can't confirm 100%, but I did find a post on a VW forum somewhere showing the connections to the newer units.

Then again, trying to get a HU out of a 2010 MY car to work 100% in a 2006 MY was always going to be a challenge......

Was getting a module incorrectly coded error... but even with the Stream back in. Seemed that once we'd altered the Stream coding and the car/gateway was happy with that, it then didn't have a problem with the Bolero! I think the overall issue has been made worse by the fact that previous owner had a Columbus unit in, and I don't think that was coded properly.

So a case of tryng to fix issues before even starting really...

Didn't make any progress or discoveries with the screen dimness issue I'm afraid. Like Mike says, headlight position makes no difference. We both swear the screen brightness improved as we tested CD and SD card playback though! It's a minor niggle in my book though, and it was a worst case scenario really when we re-fitted, as the sun was nearly directly on the unit. But day-to-day I can live with it the way it is.

Where's this percentage value for the dimming value though? Through Bolero or VCDS?

Have you got a photo of these extra connectors? Don't recall seeing anything unusual on mine, but then not 100% sure what MY mine has come out of.

Keeps us busy and out of mischief these sorts of challenges doesn't it?!

I still do have a 01305 - Databus for Infotainment 004 - NoSignal/Communication error that remains. This seems to be the final hurdle, and remains to be seen whether this will cause a drain! We've confirmed this is caused by the Rev K gateway though, as the error can be cleared and doesn't re-appear when the Rev AD gateway from Mike's motor is used in mine :yes:

Cheers,

Steve

The extra connectors are in the standard connector block.

The screem brightness was in measuring blocks (I think) in VCDS, the one where you can tick various things and see what changes. My screen is very dim (no backlight at all) on daytime setting, turn headlights on and a backlight comes on at a night time setting. Turn headlights off and the screen stays illuminated at the night time setting. Weird or what!

Pins 13 and 14 here

http://www.my-gti.co...pin-assignments

labelled as

13 – Display HV CAN bus low

14 – Display HV CAN bus high

There are no connections to these pins in my wiring loom, and I am not brave enough to connect to anything to see what happens!

I assume HV stands for High Voltage or 12v, so it looks like it needs 12v connecting to it, but the fact it mentions CAN bus worries me.................

or maybe it is pins 11 and 12 that need looking at, as I have just found this

11 – Display voltage supply, positive, optional for radio module low version only

12 – Voltage supply, negative, terminal 31

13 – Display HV CAN bus low, optional for radio module low version only, not for midline

14 – Display HV CAN bus high, optional for radio module low version only, not for midline

The extra connectors are in the standard connector block.

The screem brightness was in measuring blocks (I think) in VCDS, the one where you can tick various things and see what changes. My screen is very dim (no backlight at all) on daytime setting, turn headlights on and a backlight comes on at a night time setting. Turn headlights off and the screen stays illuminated at the night time setting. Weird or what!

Ah OK - with you (on both counts).

Don't recall seeing anything additional or unusual within the block, but then I wasn't really looking either

Yes, that will be measuring blocks. Again, wouldn't have thought there would be anything interesting in there under '56', so didn't go looking

Have probably asked this before, but what Rev gateway are you running?

Rev AD or AE, can't remember, I will do a scan tomorrow and let you know - have a look at the post I did as you were posting your reply regarding the connectors

Rev AD or AE, can't remember, I will do a scan tomorrow and let you know - have a look at the post I did as you were posting your reply regarding the connectors

Certainly new enough to get you over most 'normal' problems; that lighting one is strange though!

Agreed on those pinouts, I wouldn't be experimenting either! :S