Search results

got all you need?

deep look into our 5F adaptation session, when we captured a lot of UDS errors like read: 7F 22 31 (request out of range) write: 7F 2E 31 (roor as well) BTW: the requests are huge and nearly fourty CAN frames : 0x103 bytes payload in case of 22 0B 1D * and only once 7F 22 33 (security...

ok, I just sent you adp maps and debug data from a different ECU that is not accepting my logins.

you need an adaptation map run without security access but debug level 1024? My fault, too many try and errors for me at once. :)

I'd love to see more threads with a happy end :) I now face exactly the same issue with a 2021 Taycan: Module 09 BCM1, I want to retrofit Ugdo. 2018 Cayenne Part No SW: 971 907 063 E HW: 4N0 907 063 D 2021 Taycan Part No SW: 971 907 063 M HW: 4N0 907 063 D I tried all the same stuff like...

SW:4K4-907-108-H HW:4K4-907-108 --- Frt Sens. Drv. Assist --- SA: 20103 Component:zFAS Var B H09 0371, Coding:042784000000000000F8060000D44C24319E5600000000F80000000000000000000000000000000000000000000000000000000000000000D2804000000000000000729000A000B00080008000000000008040008000...

did not survived very long? (link)

typo...I am not talking about a wrong login/SA but failing init of $27 secure access. I'd like to understand what happens. Is the requested SA level too high? I do not use coding but adaption channels. See my initial post.

I tried like 20301 and that special S12345, but as the ECU refuses the Seed-Generation (which comes before checking SA correctness), it does not matter what I try!

here you go: Sunday,04,September,2022,12:49:53:42831 VCDS -- Windows Based VAG/VAS Emulator Running on Windows 10 x64 VCDS Version: 22.9.0.0 (x64) HEX-V2 CB: 0.4622.4 Data version: 20220830 DS341.0 www.Ross-Tech.com Chassis Type: Y1-N/A (9J1) Scan: 01 03 06 08 09 13 15 16 17 19 23 32 36 3C...

this is my main goal: to understand why is MIB3 saying "Controller refused to send a seed" Err:12. If you google it, it's quite common for ABS access and other ECUs, but it has been fixed somehow or the error subcode wasn't 12. If it's clearly pointing to a SFD* topic okay, I would accept, and...

it's an Aptiv MIB3 Premium device J794 under the hood having the same bugs and behaviors like Audi, when they introduced it in the A4 2019 Is the refusal of a seed really unknown in the rest of the supported VAG world?

I retried with open front hood but still the same error with seed refusal.

how can I bulk upload or insert pics without a URL? more pics zipped: https://1drv.ms/u/s!AusSfX-lypiPhpwjlu-OWuUuG5-7PA?e=VyQHuC

is it possible that a diagnostic firewall is enabled and therefore the strange seed refusal? I compared the above procedure with an Audi 2022 Q5 with MIB3 infotainment and I was able to read all adaption channels without any "secure access" warnings after disabling the firewall.

After having good success with different MLBEvo based ECUs in the unsupported Porsche, I am trying to add Homelink functions to the MIB3 based ECU, before installing the actual physical stuff. some Info from the controller: Address 5F: Information Electr. (J794) Labels: None Part...

is there any reason to place the retrofit ECU in the rear, rather than to find a position close to the BCM in the front of the car? why the heck did Audi place it at the rear?

tested with an extension cable and 👍 true, works on first try (LHD)

-> https://forums.ross-tech.com/index.php?threads/28904/ what part numbers are needed btw?

debug=2 is only valid for Auto scan? So basically the same as doing a controller channel map scan for "whole vehicle" UDS/CAN? https://www.ross-tech.com/vcds/tour/controller-channels-map.php