Everything posted by SuperSkodab
-
Fault codes P2563 and P0299 - 170bhp 2.0 CR TDI
Thanks for the suggestions. Garage mechanic said that the system holds a vacuum, which in his view suggests that the valve needs replacing. Since the issue is intermittent at the moment and is easily reset, I haven't gone ahead with the replacement.
-
Fault codes P2563 and P0299 - 170bhp 2.0 CR TDI
The P2563 Implausible signal in the turbo boost control position sensor circuit occurs when the car is idling or low revs, typically when waiting to turn right, or otherwise in a queue of traffic. The engine is usually warm. The engine management light flashes and a warning appears on the dot matrix display, but only for a handful of seconds and then stops, as if nothing had happened. The car appears to drive normally. This has happened between 5 and 10 times in the last 2 months. The P0299 error has occurred twice, on both occasions within 2 minutes of starting the car on a cold (for the UK) morning (<5C) whilst driving up a steep hill at (I think) 2,500 to 3,000 rpm, again flashing engine management light. The car went into limp mode and on both occasions I was able to pull over turn the car off and restart. The car restarted without the error and I could continue up the hill driving as normal, without apparent issue. I've done my background research on here and have noted all the comments about vacuum lines and the car is booked into a local mechanic after Christmas to investigate. I shared the pointer about leaking vacuum pipes and he commented that he thought that this engine has an electric boost controller, not vacuum. The engine is the 170PS 2.0 turbo diesel and the year is 2010. Is he right, or does this engine have the same vacuum lines as others? He will realise once he opens the bonnet, but I wanted to check whether their might be different issues at play if the controller is electric. Are the two different codes likely to be symptoms caused by the same fault? Does the existence of both codes point to a particular fault, or at least narrow down the range of possible causes? Do the circumstances of when the faults occur help with diagnosis? I would welcome any hints or tips that I can pass onto my mechanic, he is genuinely receptive to guidance from user forums. Thanks, Ian
-
Tyres and wheels
I'd be seeking new insurance quotes come renewal time
-
Tyres and wheels
Given that the tyre pressures for 205/55x16 are printed on the car (inside fuel flap), it would be particularly hard for an insurance company to claim that they are not a standard fitment; they might be optional, but they are still standard. Personally I have never bothered informing my insurer when I fit this size; for the winter. My personal experience (recent claim) is that the loss assessor never batted an eyelid at them, even though he had acknowledged their presence on the car.
-
Tyres and wheels
I would add that you don't identify the offset of your wheels. The standard offset for a 2017 Superb is not the same as for a 2012 model, this may have implications for the suspension and steering operation, although I note that they are not original wheels and the previous owner of the wheels may not have taken care over this.
-
Tyres and wheels
It's the winter tyre option that is listed in the owner's manual. You should also find tyre pressures for 205/55x16 on the inside of the fuel flap, confirming that it is a standard tyre size.
-
Tyres and wheels
I run my 2012 Superb Elegance on 17" rims, with the standard 17" tyre fitment, and that improved the ride over the 18" rims. With the added bonus that the tyres are cheaper. My rims came off a later Octavia, so were the correct et fitment and look very similar to the original Thermisto wheels. So much so that my wife didn't notice the difference!
-
Colombus unit - are there different versions?
Thanks pab567 Given the information that I have shared in this thread, is it possible to diagnose why our phones aren't connecting? Or which component isn't working correctly? Thanks
-
Colombus unit - are there different versions?
Curious, I never had an issue with accessing the Internet with my previous car when the phone was connected. I guess that this means that I wasn't using rSAP, but just 'hands free'? Would you please check what BT unit was fitted in my previous car? VIN in attached photo.
-
Colombus unit - are there different versions?
Nope, nothing.
-
Colombus unit - are there different versions?
Ah, the penny has dropped, I hadn't understood what your were saying before - sorry. The Bluetooth settings do not exist in my menu. Under Phone I only have: Help - basically an instruction to RTFM Phone search Media player SOS I remember seeing Bluetooth settings in the menu of my previous car, but I don't recall exactly where in the sequence. It might have been under a paired phone, which makes sense because you would set each phone separately. Unfortunately since I can't pair a phone, I'm somewhat stuffed. Also, when using the phone as a BT media player, I don't see the info. or controls to pause/play on the Columbus screen. I had these on my previous car.
-
Colombus unit - are there different versions?
I don't think that either of these are active, because the phone is unable to connect to the car as a phone, only as a BT media device. I have unsuccessfully tried to connect 2 x Samsung Galaxy and 1 x iPhone 12. In every case the sequence is the same with the following messages shown in the Maxidot display: 1. Select Phone Search > "Searching for mobile phones..." 2. The car finds the phone and lists it in the Device List 3. Select the named phone > "Enter password in phone:nnnn nnnn nnnn nnnn" 4. Enter the displayed password in phone > "Connecting..." 5. Then after a short delay > "No Bluetooth connection to mobile phone" 6. Then, after a short delay, back to > "no paired phone found" 7. If you then choose to add a Media player > "Searching for players..." 8. The car finds the phone and lists it in the Device List 9. Select the named device > "Enter password in phone:nnnn nnnn nnnn nnnn" 10. Enter the displayed password in phone > "Connecting..." 11. Then after a short delay > "Media player [ OK ] <phone name>" 12. Select OK > "Name stored." 13. Then briefly "Connection not possible" - I think at this point the phone is trying to connect to the car as a BT phone. 14. Then, after a short delay, back to > "no paired phone found" If I then immediately start the sequence again, we get to step 3 at which point the system in the car freezes. It's not possible to select 'Cancel' and the only way out is to turn the car off and remove the key. When you turn the power on again you see the message "no paired phone found". How is it possible to determine where the fault lies, Head unit or BT unit, or somewhere else?? - I get the impression that there are multiple boxes that make up the infotainment system! I don't mind replacing the BT unit, if that is definitively the location of the problem. Regarding which version to buy, I'm not sure that having WLAN in the car is an advantage, it just means that my sons will consume my mobile data allowance in preference to using their own!! Thanks for your guidance.
-
New seat base and backs ???
Did your local dealer come good on this?
-
Colombus unit - are there different versions?
Did you mean 5K0035730D/E? This other thread talks of installing the 3C8035730A-E units into a Superb, in place of the incumbant unit. What are the pros/cons of the 3C80 box versus the 5K00 box please?
-
Colombus unit - are there different versions?
The phone is a Galaxy Note 10, which connected perfectly well to my previous Superb. The car sees the phone OK and offers up a PIN for the phone, which I enter. At that point I either get an error message to say "No bluetooth connection to mobile phone" or the whole process stalls with the PIN still showing and the Cancel option not working. This is repeatable and is the same for my older phone, a Note 8. Having played around a little more, I discover that I can connect my phone as a media device. That plays content successfully and the Bluetooth button now shows on the media screen, to the right of the MDI button shown above. There are now 5, slightly smaller, buttons, not 4. The phone automatically connects as a media player when the ign* is turned on. In the bluetooth settings on the phone for BT_Skoda there is a toggle for Calls, which is off, and a toggle for Audio, which is on. If I move the Calls toggle to on, it slides back and I get a msg on the Maxidot saying that "Connection is not possible". This is starting to sound like a fault in either the Head unit or the BT unit... * Yes it's a diesel but...
-
Colombus unit - are there different versions?
- Colombus unit - are there different versions?
It hadn't occurred to me that there might be a Lightning/USB to 3.5mm jack cables - Thanks- Colombus unit - are there different versions?
- Colombus unit - are there different versions?
I have just replaced my 61 plate Superb 170 Elegance, built in 2011, with an 11 plate version of the same spec. (+ DSG), possibly built in 2010. The car seems pretty much identical except for the operation of the Colombus unit and the options on the Maxidot display. The 11 plate car has the option to display the current speed in big digits, I don't recall having this option on the 61 plate car. Were there different versions of the Colombus unit? because there is no button on the Media display and we can't connect our phones using bluetooth. We can no-longer use the Aux connection as our phones no longer have audio jacks, so listening to audio books on long journeys seems to be out of the question. This is going to make things very tedious 😞 . - Is my new (older) unit faulty? - What is an MDS connector (I didn't have this on the 61 car) and what connects to it? - Has anyone replaced the Colombus unit with a Bolero head unit, as found in newer Octavias? Or the Composition system that I have seen in Octavias and Passats, this seems to offer all the same functionality as found in my 61 plate Superb, but with a nicer user interface. Is it a plug'n'play swap? All help guidance and suggestions welcome please- Superb estate rear window wiper
Hi, I had a similar issue and it was traced to worn insulation on a wire to the rear wiper, allowing the wire to short out occasionally. This would trigger the rear wiper to wipe. The affected wire was in the tailgate, near where it comes from the main body. I would investigate this possibility soon, since in my case it was only diagnosed after the wiper stopped working entirely; because the circuit board in the control unit burnt out. It appears that the supply to this ECU is not fused!! It became a rather expensive repair. - Colombus unit - are there different versions?
Important Information
Welcome to BRISKODA. Please note the following important links Terms of Use. We have a comprehensive Privacy Policy. We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.