Jump to content

Sarivan

Finding my way
  • Posts

    11
  • Joined

  • Last visited

Profile Information

  • Gender
    Male
  • Location
    Bucharest, Romania

Car Info

  • Model
    Octavia 3

Recent Profile Visitors

364 profile views

Sarivan's Achievements

Apprentice

Apprentice (3/17)

  • First Post
  • Collaborator
  • Conversation Starter
  • Week One Done
  • One Month Later

Recent Badges

0

Reputation

  1. @Rustynuts thanks for bringing the BT issue in my attention. I've checked now the VIN to a dealer and it seems the BT is built in in the Amundsen for my model. So no BT after Columbus upgrade ! @andrehj your comparison is very detailed and pointing to real life experience. Some disatvanges presented i was not aware about them. The only strong reason while i would upgrade to a Columbus is because VW stopped the East E updates for both of them in 2016 i think but for Columbus some third parties compiled the 2018 BMW maps for Columbus and they are working great. Nothing for Amundsen yet... Google is alway the best choise but as long as i don't have an Android Auto at least i prefer using the NAV instead of having the phone in the window... Thank you both for your input. Really appreciated
  2. No i haven't. But is this the main issue? I understood there is a recoding to be done with VCDS to let the ECU know the car has now a rns510 and not a rns315. This i want to know how to do it. If there is something in addition for BT to be done of course also this one. Thank you
  3. Hi, I intend to replace my Amundsen+ with a Columbus RNS510 unit. The car is a Superb MK2 2012. The Columbus unit is also MK April 2012. Does anybody know the steps for performing this action? I am interested more in VCDS coding if there is something special. For the physical replacement i saw a couple of movies and it doesn't seem so complicated. But i want to know if there are some parameters to be modified and which ones. I forgot to mention the car is also equipped with bluetooth and phone set but i don't think think this could be a problem for the new Columbus... I don't know if this topic has been already discussed. I've searched for it but without a result.
  4. It's clear now. It's better to be careful when you buy a new car what options you chose from the beginning. Because afterwards it's more difficult and expensive to change them. I will close the topic. Thank you.
  5. Ok. So no MIB 2. But are this problems applying to Amundsen MIB 1 also? If i change my Bolero with an Amundsen from the same generation (2013) it should work right? I understood that even from the same generation you must to some VCDS encoding for starting navigation but not so complicated. About the price... of course i am not thinking to buy it from the dealers. They have a huge price. It can be found cheaper at retailers like Augsburg Int. Thank you for your support
  6. I am investigating the necessary parts for changing the standard Bolero MIB with Amundsen navigation. My car is an Octavia 2013 model. 1. Is it possible to replace a 2013 MIB1 Bolero with a MIB2 Amundsen? Of course including changing everything: control unit, display, connectors, antena... 2. Can somebody help me with the original PN for all the Amundsen pieces? I found this ones for MIB 1 but i wanted to be sure they are the good ones: - control unit: 5E0035864A or 5E0035874A. I really couldn't find anywhere the difference between this PNs. - display: 5E0919605D BIO. Again a lot of options here with A, B, C, D , E, J, H letters in the end. I assume BIO is coming from the satin black color and aluminium insertions. - cable connector: 5E5035572A - antena: 5Q0035507B Thank you
  7. I had the same error message when using a usb stick of 8GB formatted NTFS. After re-format it with FAT32 file system it worked great. My media system is a Bolero MIB1
  8. Ok, so it seems that this can be a normal behavior. I will ask the dealer to check for any firmware upgrades when i will have my next revision.
  9. Dear all, My car is an Octavia 2013 Elegance and I have an intermittent problem with my Infotainment. The car was delivered with the Bolero MIB1 option. Last year i had the first problem with my Bolero's screen. It remained black after the ignition for a couple of hours. After this it came back to normal. The service said i have to capture the problem and they will change it. After this first occurrence my Welcome to Skoda logo also started to behave strange. Meaning that it was not displaying anymore everytime i switched the ignition. Anyway the problem with the screen reappeared this year, i managed to capture it with my phone, and the Bolero (media + screen) was replaced. But still the Welcome Logo is not displaying all the time. In the beginning i thought it's a revision problem. But the old and the new Boleros have different revisions and the problem persists. Does any of you faced the same issue? Is there a coding with VCDS to make the logo display every time? All the best, Razvan
  10. I am Razvan from Romania and i am the happy owner of a Skoda Octavia 2013 1.4 TSI. Since more than 10 years i've experienced different VAG cars like Golf 4 ALH, Passat B6 and in 2013 i decided to try the new Octavia 3 which proved to be a very good decision. I found about your community last days, when i first tried some tweaks with Ross-Tech VCDS and the information posted here was very helpful for me. I hope i can also improve your community with advises from my personal experience and continue to find solutions to my issues. All the best
×
×
  • Create New...

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.