$kodillac

You cant be to careful... can you? Arent you guys also using allways 2 rubbers? ...to be honest i have had some dead battery episodes last year so just playing safe. Another piece of fact. My unit was bfore 1Z0 035 680 A and became 3T0 035 680 A after the upgrade. Not upgraded to B -unit as said on my-gti.com information.

Ebay bargain... straight from Czech Republik. No seals broken. Sold as new unit. There even was a shield membrane on the display. Zero marks of usage (fingerprints wiped clean ). No original code card included though. Thinking that it is maybe a refurb or some factory leftower unit. I heard those are made also in Czech so maybe it got smugled out of the factory back door or something. I guess i´m one of the lucky&inglorious basterds... :crown: I was paranoid about the battery power so i went and connected a smart battery charger bfore the firmware upgrade. I think it is the F-gateway which just gannot work rite with Columbus. I think i had errors on 19 and 37. It whined about wrong coding. My unit is HW04 and 1004 was the starting point.

Quote: Originally Posted by Keith Lard Has anyone got the MFSW working properly with this? Mine currently only operates the volume buttons, might chnaging the F/W help? Guess who wrote that on my-gti? I´ll have to add this comment on the topic. First when i installed my Columbus over a month ago i only got volume and mute buttons working on the driving wheel. After that i upgraded the CAN-gateway box from F--> S -version. I could not code the columbus in right bfore that wit VCDS. After that all the fault codes went away and all the steering wheel buttons started to work. So it was only this 2664 FW-upgrade which killed the buttons without editing the filenames on FW-image. So Keith L. i guess you might either have too old CAN-gateway or the Columbus is not coded right to the gateway. Do you have any fault codes when you check with the VCDS? BtW.... firmwarewise i could not get Verbatim CD/R to work so i used DVD+R instead which worked like a charm.