1 minute ago, SashaGrace said:

This is how it works on the MIB1 Amundsen, the only MIB1 that doesn’t have the restriction message is the Columbus.

 

thanx but what is the problem in amundsen than? comunication between amundsen - camera -mib or something else?

and it would work if i remove Amundsen and retrofit Columbus... columbus works on MIB1 with no problems?

does it need any activation or is it only plug and play ? found some on german ebay for 300€... here in croatia prices are around 1000 euro, which is way too much for me.

No idea, but it’ll cost as much to install a MIB1 Columbus as it’ll cost to install a MIB2 Columbus and it’s the same coding and component protection rigmarole anyway. I’ve installed a MIB2 Amundsen in my car and it’s going to Skoda on Wednesday to try and have the firmware on the camera updated to communicate with the MIB2.

34 minutes ago, SashaGrace said:

No idea, but it’ll cost as much to install a MIB1 Columbus as it’ll cost to install a MIB2 Columbus and it’s the same coding and component protection rigmarole anyway. I’ve installed a MIB2 Amundsen in my car and it’s going to Skoda on Wednesday to try and have the firmware on the camera updated to communicate with the MIB2.

Will you let me know how you get on Sasha?

would like to update the firmware on mine, if it’s worth the €€€ to do it

@seanbrady49 Will do. Hopefully it’ll all go well and the TSR will work without the restriction warning.

 

@ShokreKTM The unit in the glovebox is different as you mention. This is the brains of the media system. If you bought a MIB1 Columbus on eBay it’ll need Component Protection removing and then coding for the radio to work in the car done outside the dealer network. You’ll also need the 8 inch screen. The same amount of coding is needed on the MIB2 unit and you’ll gain SmartLink and a nicer UI out of the deal. With VCDS you shouldn’t get a restriction warning from a factory MIB1 Columbus but I don’t know about a retrofit. MIB2 wise you’ll need to update the firmware on the camera to get it to talk to the navigation system. My MIB2 Amundsen system shouldn’t have a restriction warning on a car with it installed at the factory so mine should work with the updated firmware on the camera. Fingers crossed

Edited 10 September, 20187 yr by SashaGrace

45 minutes ago, SashaGrace said:

No idea, but it’ll cost as much to install a MIB1 Columbus as it’ll cost to install a MIB2 Columbus and it’s the same coding and component protection rigmarole anyway. I’ve installed a MIB2 Amundsen in my car and it’s going to Skoda on Wednesday to try and have the firmware on the camera updated to communicate with the MIB2.

ok.. now you got me confused
how can it cost the same if I allready have MIB1 main unit in the glove compartment 

is the Columbus main unit different than the Amundsen?
so if I lets say purchase Columbus from ebay and replace it only I should not have any more restriction message?
seems to me that i have read somewhere on this forum that even on somebodys Columbus it was giving restriction message

 

EDIT:
copy paste from OBDELEVEN forum concerning MIB1

If you are updating Just for this, save your time.

The MIB1 low headunit is and will ever be unable to provide predictive route data, which is needed for traffic sign recognition.

As the camera itself is too unreliable (for example, its not able to distigunish between the varities of City boundary signs (Entering, leaving,...) Or Timed Limits. These Data have to be provided by the nav.
So they designed the system to never Work standalone I am afraid.
 

Edited 10 September, 20187 yr by ShokreKTM
copy paste something relevant from another foru

What traffic signs is this meant to display? Mine only every shows speed limits and occasionally a no overtaking sign. That’s it. 

Just now, SC03OTT said:

What traffic signs is this meant to display? Mine only every shows speed limits and occasionally a no overtaking sign. That’s it. 

so does mine
seems to me that i"ve read somewhere here that it is able to read some other signs, but I havent found that option in VCDS.. but honestly I didnt even know that it is a possibility

On 10/09/2018 at 22:07, SashaGrace said:

@seanbrady49 Will do. Hopefully it’ll all go well and the TSR will work without the restriction warning.

 

@ShokreKTM The unit in the glovebox is different as you mention. This is the brains of the media system. If you bought a MIB1 Columbus on eBay it’ll need Component Protection removing and then coding for the radio to work in the car done outside the dealer network. You’ll also need the 8 inch screen. The same amount of coding is needed on the MIB2 unit and you’ll gain SmartLink and a nicer UI out of the deal. With VCDS you shouldn’t get a restriction warning from a factory MIB1 Columbus but I don’t know about a retrofit. MIB2 wise you’ll need to update the firmware on the camera to get it to talk to the navigation system. My MIB2 Amundsen system shouldn’t have a restriction warning on a car with it installed at the factory so mine should work with the updated firmware on the camera. Fingers crossed

hey.. @SashaGrace.. couple more questions...

1..who did your camera firmware update? skoda service or?

2.. is component protection something that can be done via VCDS or must I visit official service,and should they be "in frienly mood" when asked to remove component protection

 

Edited 16 September, 20187 yr by ShokreKTM

Camera update was a failiure at Skoda, they couldn’t do it so am waiting for some other people to get back to me on that.

 

Component Protection can’t be done on VCDS, it is as you say, go to Skoda and ask nicely

i get the same error after trying this 

in 17 instruments you cannot change it to mib2 standard either if the mib2 is retro fitted 

I traded in my Octy I VRS with 190k miles a couple of weeks ago, for an Octy III Scout 150.  Very pleased with it so far, although the diesel is noisier than I'm used to.  I also took delivery of an OBDeleven adaptor yesterday so have been playing with it.

 

I've carried out a couple of adaptations with some degree of success, so thought I'd try the traffic sign recognition.  Followed the instructions found in various places, and got the expected popup message on the Maxidot reporting restricted functionality.  I checked the fault codes and there was one in controller A5 (Front Sensors Driver Assistance System) reporting an unreceived data message.  Checked the long coding for this module and there is a field labelled VZE_NavigationType which was set to "MIB2 Standard".  Now the Information Control Unit (5F) shows, in adaptation Vehicle_configuration that PSD_Protocol_Version is "PSD_1.5".  So I changed the field VZE_NavigationType in A5 to "MIB2 High PSD 1.5" (in the hope that the two controllers will now speak the same language!).

 

After one short test drive the 'restricted functionality' popup hasn't recurred yet, so fingers crossed. 

 

NB I can't find a reference to this field anywhere in this topic, so I don't know if anyone else has tried it; and if they have, whether it worked or not.

Does the car have a MIB2 Columbus with the 8 inch screen? This is MIB2 High, the 6.5 inch screen is MIB2 Std (PFL screen sizes, 9.2 and 8 inches on the FL respectively) the PSD1.5 protocol is sometimes set to PSD1.4. My replacement A5 camera was set to 1.4 instead of 1.5 so I had the same problem until that data value was changed.

Hi Sasha,

 

It's an Amundsen (with the smaller screen).  I assume it's MIB2 as that's how it's coded.  I don't suppose it matters too much what protocol is set as long as all controllers use the same one.

For the TSR to be at its best you should set the A5 camera back to MIB2 Std if it’s an Amundsen. The map data is different to the Columbus. PSD1.4 won’t work in the uk, has to be PSD1.5

Sasha,

When I had the A5 camera coded to MIB2 Std (original setting) it kept raising fault U112100 (Databus missing message).  I assume that is because the Amundsen is transmitting PSD 1.5 while the camera was expecting a different set of messages. 

 

I drove about 15 miles tonight after changing the A5 camera to PSD1.5, without any fault or message on the Maxidot.  Sign recognition appears to be working correctly: the Navi is showing one speed rather than two which it had before coding TSR (e.g. 60 and 50); and the Maxidot is showing the same speed limit.  The only oddity was that the speed limit was shown as 20mph in the centre of town, although there is no 20mph sign; the speed limit reverted to 30mph later, again without passing a sign.  Otherwise it worked faultlessly.

 

If I code the camera back to MIB2 Std then I will presumably also have to recode the Amundsen to MIB2 Std to avoid the error messages.  However, if I understand correctly then won't this mean that the speed data from the Amundsen's map won't be made available to the camera?  If the Amundsen doesn't support PSD1.5 why is it set? 

 

Module information (from OBDeleven):

5F Information Control Unit

    System description: MU-S-ND-ER  
    Software number: 5Q0035874A
    Software version: 0245
    Hardware number: 5Q0035874A
    Hardware version: H24
    Serial number: xxxxxxxxxxxxxxxx
    ODX name: EV_MUStd4CTSAT
    ODX version: 001022
    Long coding: 03734201FF00000011111201008800002F0202C601208100C6

    Subsystems:
        System description: ABT_Std-2_Nav
        Software version: 1028
        Hardware version: H41
        Serial number: xxxxxxxxxxxxxxx     

        System description: ECE AS 19/20
        Software version: 1115
        Hardware version: ---
        Serial number: --------------------

Amundsen does support PSD1.5. There’s the TSR coding in 5F for the map data side of things and the A5 camera should be coded to match, with PSD1.5 and map fusion switched on. If your setup is working fine as it is, leave it alone, however the correct coding for an Amundsen is MIB2 Std, a Columbus is MIB2 High, it doesn’t make a great deal of difference but there are differences in the base mapping between Amundsen and Columbus setup as the maps are different in how they are loaded onto the radio and this may include speed limit data. My camera is set to MIB2 High to match my Columbus radio unit and when the PSD value was altered from 1.4 to 1.5 the roadsign restricted warning went away. The MIB value in the Amundsen doesn’t change, it’s the PSD value that counts. It’s the A5 camera coding that dictates the majority of how TSR works, this is why I had to have 0060 firmware on my camera either by a software flash or a G revision camera with the nav dataset pre loaded for the TSR to work correctly on my car as I have retrofitted the MIB2.5 radio unit.

11 hours ago, SashaGrace said:

Amundsen does support PSD1.5. There’s the TSR coding in 5F for the map data side of things and the A5 camera should be coded to match, with PSD1.5 and map fusion switched on. If your setup is working fine as it is, leave it alone, however the correct coding for an Amundsen is MIB2 Std, a Columbus is MIB2 High, it doesn’t make a great deal of difference but there are differences in the base mapping between Amundsen and Columbus setup as the maps are different in how they are loaded onto the radio and this may include speed limit data. My camera is set to MIB2 High to match my Columbus radio unit and when the PSD value was altered from 1.4 to 1.5 the roadsign restricted warning went away. The MIB value in the Amundsen doesn’t change, it’s the PSD value that counts. It’s the A5 camera coding that dictates the majority of how TSR works, this is why I had to have 0060 firmware on my camera either by a software flash or a G revision camera with the nav dataset pre loaded for the TSR to work correctly on my car as I have retrofitted the MIB2.5 radio unit.

 

My camera needs the software flash but i dont have the tools, its restricting a few other things as well like lane assist and HBA all now dont work after the VC upgrade. Have to get VAG Com 

1 hour ago, JohnnyType2 said:

 

My camera needs the software flash but i dont have the tools, its restricting a few other things as well like lane assist and HBA all now dont work after the VC upgrade. Have to get VAG Com 

That’s really odd, my VC install didn’t affect the camera. When I get ODIS all up and running I’ll try and get a scan done so we can work through the errors.

check this manual I prepared some time ago

Hello, 

 

I recently bought obd II cabel and vcds for my skoda octavia III and yesterday I tried to enable sign notification (I didn't know I needed front camera to work) and now I can not erase the error, when I turn the ignition on. I have turned everything back to standard (as it was before) and it still pops up an error. Does anybody know how to erase that error or disable the function? I have tried scanning and then deleting all dtc codes, but error is still there. 

 

Thank you. 

Looks like the maxidot is still set for tsr enabled.  Double check the settings to ensure you have reset them all, particularly controllers 5f and 17.  

I wouldn't bother with it, I find it more of an irritation than useful, blocks out the VC clock.

22 hours ago, NMcK said:

Looks like the maxidot is still set for tsr enabled.  Double check the settings to ensure you have reset them all, particularly controllers 5f and 17.  

I have tried several times to check and uncheck (in 5f and 17 channel) but the function is still "on". Is there any other option? 

On 27/11/2019 at 05:17, alesek86 said:

I have tried several times to check and uncheck (in 5f and 17 channel) but the function is still "on". Is there any other option? 

 

Still haven't solved the issue. Does anyone have a clue? Any reset of the ECU? 

2 hours ago, alesek86 said:

 

Still haven't solved the issue. Does anyone have a clue? Any reset of the ECU? 

One thing occurs to me...  When enabling traffic sign recognition using OBDeleven or VAGCOM, after all the adaptations are complete the function is still not active.  It is necessary to enable it through the menu in the Columbus or Amundsen menu.  If it isn't set on though the menu, then it won't appear in the maxidot.

 

So I suggest that you could check whether the menu item appears in the Columbus/Bolero menu.  If it does, then uncheck the option.  If it doesn't appear, use OBDeleven or VAGCOM to add the menu item back, and then uncheck the option.  

 

Once you have done this the traffic sign recognition is disabled and shouldn't appear on the maxidot.  You should now be able to undo the controller adaptations if you wish, and the menu item associated with it will disappear.

 

Try this and see how it goes.