Selective output test refused by module, status 03?

Jeff V. · Nov 30, 2015

This is related to my output test discovery work here: http://forums.ross-tech.com/showthread.php?3927-No-selective-output-tests-for-B8-S5-module-46

I figured this was generic enough to warrant it's own thread though. I wasn't able to find much in my Google searches.

When I run some of the tests, the module accepts them but then hangs. If I manually stop the test, VCDS comes back with a red "Refused by control module. Status 03" error.

Does anyone have a definition of what this means? My guess is that it's a valid test for that module's hardware, but the option you're trying to test isn't installed and/or coded. Like doing rear door lock tests on an A5 coupe, or testing a power sunshade that doesn't exist.

Some of my searches showed that the raw CANbus code might be 7F 22 22. Which is a negative response to mode $22, with the reason code being "conditions not correct or sequence error". I couldn't find anything saying this was the same as a Status 03 however.

Any light that can be shed on this would be greatly appreciated.

Eric · Nov 30, 2015

There can be a few places where that error message gets called. The best would be to generate a debug 1024 of that specific output you're trying to run and send it to support, and then I'll see what can be seen and try to explain if I can

This isn't going to be top-priority though.

Jeff V. · Nov 30, 2015

I'll try and get something tonight. I understand it's not a priority. It's not one for me either. It's mostly to satisfy my curiosity and help me with mapping out these test channels in a way that'll be beneficial to more than just owners of 2008 S5s.

Jeff V. · Dec 1, 2015

I sent over a brief debug file. Any light you can shed would be appreciated. If you don't have time or can't comment due to fears of exposing some secret ingredients or something, I understand. Thanks.

Eric · Dec 2, 2015

Got your debug. This is a weird situation where we start the output test, module is happy. Ask for output test status, the module tells us "you need to activate the output test". Not unusual, so we do that, but then we get a conditions not correct or request sequence invalid error. So we go back to asking status and it tells us the same thing, need to activate. Normally we'd get "output test running" and optionally some measuring values. It keeps doing that until you abort, and that goes smoothly. Luckily we now have a car with a similar 46, so I'll see if that happens here as well, and if ODIS/VAS PC handle it any different. Still low priority

Jeff V. · Dec 2, 2015

Let me know if I can do anything to help. The -064 part I used for the debug is strictly for bench testing, so I can mess with it without fear of messing up my car.

You guys ever try running a Hex-Net across a WAN? I can set up some port forwarding to it and you can log in and test it yourselves if you want.

Eric · Dec 7, 2015

Well the good news is I reproduced this on my car; the bad news is, ODIS isn't doing much better.

ODIS starts the output but then says "Advancing required";

Once you do that (click Next), the test terminates. I have not seen the left rear interior locking indicator lamp come on at any time.

Sequential output tests is even better, it runs through a few things (not the 113), alarm being first, then gets stuck in a loop between the two rear lights

mabnz · Oct 7, 2016

Sorry to drag up an old thread, but was anything resolved here? I'm trying to test my 'alarm horn for anti-theft system' and output tests are 'refused by control module (7F 2F 22). In fact all the output tests I try are refused..

Uwe · Oct 7, 2016

mabnz said:
Sorry to drag up an old thread, but was anything resolved here? I'm trying to test my 'alarm horn for anti-theft system' and output tests are 'refused by control module (7F 2F 22). In fact all the output tests I try are refused..

Details from the module you're experiencing this on would probably be useful here.

-Uwe-

MartinsX · Oct 7, 2016

In general, output test is refused if some conditions for testing are not fulfilled. Bad thing is, that often noone knows what are those conditions and no info can be find in any documentation...

mabnz · Oct 7, 2016

Uwe said:
Details from the module you're experiencing this on would probably be useful here.

-Uwe-

This is attempting on 09-Cent Elec, but I had errors on A5 too. Is there some debug I can provide which would help?

Uwe · Oct 7, 2016

In this case, I doubt a debug file would help. The pertinent part of the refusal message is already shown there.

What *might* be useful is actual scan data from the version you're currently using (16.8.2) so we can see exactly what ROD file VCDS is using for that BCM of yours. If found an older scan from what looks to be the same car, but that was from before our recent revisions to how some of that is done.

I was going to say that we'll try to reproduce this on one of our MQB based cars, but none of them have a BCM with the same last three digits in the main part number as yours. One of ours is a Conti as opposed to your Bosch. The two from Bosch are 085 and 087 as opposed to your 086, and neither of those have a separate Alarm Horn sub-system.

-Uwe-

mabnz · Oct 7, 2016

Uwe said:
In this case, I doubt a debug file would help. The pertinent part of the refusal message is already shown there.

What *might* be useful is actual scan data from the version you're currently using (16.8.2) so we can see exactly what ROD file VCDS is using for that BCM of yours. If found an older scan from what looks to be the same car, but that was from before our recent revisions to how some of that is done.

I was going to say that we'll try to reproduce this on one of our MQB based cars, but none of them have a BCM with the same last three digits in the main part number as yours. One of ours is a Conti as opposed to your Bosch. The two from Bosch are 085 and 087 as opposed to your 086, and neither of those have a separate Alarm Horn sub-system.

-Uwe-

So just an adaption map of the module? I'll grab it now. Where do I send the full output?

Here's a snippet:

Code:

;SW:5Q0-937-086-AK   HW:5Q0-937-086-AK ---  Cent. Elect.
;Component:BCM PQ37BOSCH 028 0162, Coding:0F011B46C24722FB0FA44086B10C17280800000000000000000000000000
;EV_BodyContrModul1UDSBosc,015002,EV_BCMBOSCH_015_SK37.rod
;Saturday,08,October,2016,15:16:48:10108
;VCDS Version: Release 16.8.2 (x64)  Data version: 20160926 DS261.0

IDE00001-ENG99061-Production mode-Access control,not active 
IDE00001-ENG115730-Production mode-Aussenbeleuchtung,not active 
IDE00001-ENG116710-Production mode-Frontwischer deaktivieren,not active 
IDE00001-ENG112304-Production mode-Heckwischer,not active 
IDE00001-ENG98647-Production mode-Interior lighting,not active 
IDE00001-ENG115729-Production mode-Scheinwerferreinigung,not active 
IDE00001-ENG115731-Production mode-Virtuel_pedal,not active 
IDE00002-Transport mode,active 
IDE00820-Activating and deactivating all development messages,not active 
IDE01268-ENG115835-Windshield wiper-Adaptives Nachwischen bei SRA,not active 
IDE01268-ENG116609-Windshield wiper-Anzahl Betaetigungen Frontwaschanlage pro SRA Aktivierung,10 
IDE01268-ENG115836-Windshield wiper-Frontwischer Notlaufprogramm,active 
IDE01268-ENG116614-Windshield wiper-Frontwischer Referenzlauf,active 
IDE01268-ENG02322-Windshield wiper-Frontwischer_Abtauposition,not active 
IDE01268-ENG116617-Windshield wiper-Geschwindigkeitsabhaengige Wischstufenrueckschaltung,active 
IDE01268-ENG116615-Windshield wiper-Menuesteuerung Frontwischer,not active 
IDE01268-ENG115771-Windshield wiper-Regensensor aktivieren,Deactivating 
IDE01268-ENG115769-Windshield wiper-SRA bei Waschwassermangel,not active 
IDE01268-ENG115767-Windshield wiper-SRA Einweichpausenzeit,2000 ms
IDE01268-ENG115768-Windshield wiper-SRA Nachwaschzeit,1100 ms
IDE01268-ENG116611-Windshield wiper-SRA Pausenzeit,0 ms
IDE01268-ENG116610-Windshield wiper-SRA Verzoegerungszeit,0 ms

Uwe · Oct 8, 2016

mabnz said:
So just an adaption map of the module?

No, I'm not sure why you think Adaptations are related to SOTs.

But one part I wanted to see is there: "EV_BCMBOSCH_015_SK37.rod"

Have you done an Auto-Scan with 18.8.3? Look in your Scans sub-folder. If you've got one, please post the 09 module details from that.

Oh, and the first 10-12 digits of your VIN would be appreciated as well.

-Uwe-

mabnz · Oct 8, 2016

Uwe said:
No, I'm not sure why you think Adaptations are related to SOTs.

But one part I wanted to see is there: "EV_BCMBOSCH_015_SK37.rod"

Have you done an Auto-Scan with 18.8.3? Look in your Scans sub-folder. If you've got one, please post the 09 module details from that.

Oh, and the first 10-12 digits of your VIN would be appreciated as well.

-Uwe-

Sorry, still relatively new to VCDS :-)

Autoscan including VIN:

Code:

Friday,07,October,2016,15:53:53:10108
VCDS -- Windows Based VAG/VAS Emulator Running on Windows 8.1 x64
VCDS Version: 16.8.2.3 (x64)  HEX-NET CB: 0.4321.4
Data version: 20160926 DS261.0
www.Ross-Tech.com

Chassis Type: NE (5Q0)
Scan: 01 02 03 05 08 09 10 13 15 16 17 19 2B 36 42 44 52 55 5F 69
          6D A5 A9

VIN: TMBKE9NE5G0xxxxxx   Mileage: 3683km-2288miles

-------------------------------------------------------------------------------
Address 09: Cent. Elect. (J519)       Labels: 5Q0-937-08X-HV1.clb
   Part No SW: 5Q0 937 086 AK    HW: 5Q0 937 086 AK
   Component: BCM PQ37BOSCH 028 0162  
   Revision: --------    Serial number: 8658230416004Q
   Coding: 0F011B46C24722FB0FA44086B10C17280800000000000000000000000000
   Shop #: WSC 59986 001 104857
   ASAM Dataset: EV_BodyContrModul1UDSBosc 015002
   ROD: EV_BCMBOSCH_015_SK37.rod
   VCID: 8346C07C0A32E45A29-80D6

   Control Unit For Wiper Motor: 
   Subsystem 1 - Part No SW: 5E2 955 119     HW: 5E2 955 119   Labels: 5QX-955-119-V1.CLB
   Component: WWS371 160319  041 0570 
   Serial number:         160329162224
   Coding: 0E5DFD

   Rain Light Recognition Sensor: 
   Subsystem 2 - Part No SW: 5Q0 955 547 A    HW: 5Q0 955 547 A  Labels: 5Q0-955-547.CLB
   Component: RLHS  037 0059 
   Serial number: S5Y16M04D28H09M29S54
   Coding: 00885D

   Sensor For Anti Theft Alarm System: 
   Subsystem 3 - Part No SW: 5Q0 951 171     HW: 5Q0 951 171 
   Component: Sensor, DWA  005 0316 
   Serial number: 000000000ZY113040CK7

   Alarm horn: 
   Subsystem 4 - Part No SW: 5Q0 951 605 A    HW: 5Q0 951 605 A
   Component: Sirene, DWA  005 0313 
   Serial number: 00000000000064989964

   Relative Air Humidity Interior Sender: 

No fault code found.

mabnz · Dec 18, 2016

I've discovered today that before I was choosing 'on' with each output test, and being refused by the control module. Just for fun I tried 'off' today and it worked! Going to try with the horn now.

Selective output test refused by module, status 03?

Jeff V.

Verified VCDS User

Eric

Active Member

Jeff V.

Verified VCDS User

Jeff V.

Verified VCDS User

Eric

Active Member

Jeff V.

Verified VCDS User

Eric

Active Member

mabnz

Verified VCDS User

Uwe

Benevolent Dictator

MartinsX

Verified VCDS User

mabnz

Verified VCDS User

Uwe

Benevolent Dictator

mabnz

Verified VCDS User

Uwe

Benevolent Dictator

mabnz

Verified VCDS User

mabnz

Verified VCDS User