Unfortunately we do not accept new members for free, Now Registration cost 30€, if you are interesting Send Email to [email protected]
Traffic Sign Recognition issue after MIB2 retrofit
05-03-2019, 12:33 PM,
Post: #1
|
|||
|
|||
Traffic Sign Recognition issue after MIB2 retrofit
Hi,
I retrofitted a MIB2 High (8v1 035 035) unit into my PFL A3(factory fitted with MIB1 High, TSR, ACC with dome radar, Lane Assist,) , all works fine except some issue with Traffic Sign Recognition. Shortly after engine startup I get "Traffic Sign Recognition: Currently Restricted"-with the MIB1 unit I rarely seen that message-, but sign recognition appears to still work and I get posted speed limits or no overtaking signs on my instrument cluster. I also get this error on module A5, it reappears as soon as I clear it : Quote:"Databus missing message: PSD_01_TO_FAILURE" If I disable TSR from A5 coding, the error is gone. On module 5F: I tried disabling/enabling VZO, different settings for Car_Function_List_BAP_Gen2-traffic_sign_recognition_0x21_msg_bus, I tried to disable PSD from 5F coding byte24bit7, I tried PSD1.4/1.5 in 5F adaptations... but no luck getting rid of that error. I noticed that the A5 controller has a coding byte for MIB1/MIB2, but my unit doesn't accept changing the coding to any of the MIB2 settings(I tried with Ignition On/Engine Off): I noticed there's a 5Q0980653G H06 0060(mine's 5Q0980653E H05 0050) firmware available . Can I use this firmware on my module? Can this update affect ACC or any other front assist system? I know that I need to use VCP to parameterize the module afterwards. Calibration settings I assume I can just import my current calibration settings. To get rid of that error, do I need to update the A5 firmware or is just some coding/adaptation issue? Thank you! |
|||
09-03-2019, 10:49 AM,
Post: #2
|
|||
|
|||
RE: Traffic Sign Recognition issue after MIB2 retrofit
You have to update the A5 firmware to version G, and also add the right dataset to the Camera.
After flashing to index G A5 will ask for dataset. If you have VCP than it is not a probleme. If not than you have to find somebody arround you. After doing that change the Navigation system to PSD 1.5 |
|||
08-04-2019, 00:24 AM,
Post: #3
|
|||
|
|||
RE: Traffic Sign Recognition issue after MIB2 retrofit
I finally got my VCP cable so I updated the camera to G version. This allowed me to change the coding to MIB2 High with PSD1.5, but the error persisted. I then updated my CAN Gateway firmware from 5q0907530M to 5q0907530AJ and this fixed the error.
|
|||
11-04-2019, 13:12 PM,
Post: #4
|
|||
|
|||
RE: Traffic Sign Recognition issue after MIB2 retrofit
hi , when you flash 19ecu with new .frf file , you have to re-made the safeCp funcion by odis online?? or you just need to update zdc file for dataset and recoding?
thanks |
|||
27-04-2019, 09:03 AM,
Post: #5
|
|||
|
|||
RE: Traffic Sign Recognition issue after MIB2 retrofit
Hi,
You don't need to remove CP after flashing the gateway. You just need to upload the datasets for: (FPA)driving profiles, (MKE) Fatigue Recognition and for start/stop system. |
|||
06-08-2019, 23:39 PM,
Post: #6
|
|||
|
|||
RE: Traffic Sign Recognition issue after MIB2 retrofit
Hello
I have this issue too after retrofit A5 camera What can i do since i have MIB1? Thanks |
|||
07-08-2019, 07:07 AM,
Post: #7
|
|||
|
|||
RE: Traffic Sign Recognition issue after MIB2 retrofit
And about calibration, if you flash A5 , you lost calibration or you need only to update zdc file ?
|
|||
« Next Oldest | Next Newest »
|
Users browsing this thread:
1 Guest(s)
1 Guest(s)
Return to TopReturn to Content