Page 5 of 17 FirstFirst ... 3456715 ... LastLast
Results 41 to 50 of 166

Thread: Testbench setup?

  1. #41
    Verified VCDS User
    Join Date
    Apr 2016
    Location
    United Kingdom
    Posts
    152
    Post Thanks / Like
    1048574 km!!! What's happening there? I can't believe the donor vehicle really did cover that distance?

    Thanks for your suggestion about the BCM, I shall give it a go! When I tested mine directly with my CAN analysing kit the BCM was alive and sending no stop data, so I'm confident it's powered correctly and alive.

    On the VCDS bench setup I also had the parking aid module connected to the CAN Gateway, this is also on the convenience CAN and I had the same result of not being able the connect via VCDS. So I think the problem is the resistance on the convenience CAN.

    I go away soon so it will be awhile before I start bench testing again.

    This is a great thread, love it

  2. Likes DV52 liked this post
  3. #42
    VCDS Distributor
    Join Date
    Feb 2014
    Location
    Denmark
    Posts
    1,774
    Post Thanks / Like
    Quote Originally Posted by DV52 View Post
    (not sure where the DTC is getting the mileage number-from)?
    My guess is, it is from some default values in the processor/program.
    Dec 1048574
    Hex FFFFE
    Bin 11111111111111111110
    There are no mileage/date values available in your CAN communication data.

    There are a few DTC's, that probably are from when the BCM was installed in a car.
    Mileage: 10430 km
    Date: 2015.09.06
    Time: 12:14:30

  4. Likes Eric, mattylondon, Uwe, DV52, Zenerdiode, Sebastian, _Val liked this post
  5. #43
    Verified VCDS User
    Join Date
    May 2014
    Location
    Melbourne, Australia
    Posts
    2,876
    Post Thanks / Like
    OK, discovering new stuff about this wierd thing called OBDII! Is anyone able to help with my latest conundrum (sorry to be a pest, but this is the best place to seek advice IMO). I've attempted to reduce the DTC's in the BCM on my testbench as much as possible and I'm down to a more respectable number (22 DTCs)

    But in the process of deleting DTCs, I've now exposed the anticipate Component Protection message which was entirely missing from the autoscan report on my previous post (see below)

    Code:
    Thursday,28,April,2016,09:20:11:03521
    VCDS -- Windows Based VAG/VAS Emulator Running on Windows 10 x64
    VCDS Version: 16.3.1.1 (x64)
    Data version: 20160325
    www.Ross-Tech.com
    
    
    VIN:    License Plate: TEST BENCH
    Mileage: No Lamp DTCs   Repair Order: CAN G'way+BCM
    
    
    
    --------------------------------------------------------------------------------
    --------------------------------------------------------------------------------
    
    
    Chassis Type: 5Q0
    Scan: 09 19
    
    
    09-Cent. Elect. -- Status: Malfunction 0010
    19-CAN Gateway -- Status: OK 0000
     
    -------------------------------------------------------------------------------
    Address 09: Cent. Elect. (J519)       Labels: 5Q0-937-08X-MV1.clb
       Part No SW: 5Q0 937 084 N    HW: 5Q0 937 084 N
       Component: BCM MQBAB M   H14 0106  
       Serial number: 00011309901220
       Coding: 030000000000000303200002000000000000000000000000000000000000
       Shop #: WSC 73430 790 00104
       ASAM Dataset: EV_BCMCONTI 010001
       ROD: EV_BCMBOSCH_VW37.rod
       VCID: 4385A3B4CA981924E9-8016
    
    22 Faults Found:
    135432 - Terminal S 
              B11A5 11 [009] - Short to Ground
              Confirmed - Tested Since Memory Clear
                 Freeze Frame:
                        Fault Status: 00000001
                        Fault Priority: 6
                        Fault Frequency: 1
                        Reset counter: 238
                        Mileage: 1048574 km
                        Date: 2000.00.00
                        Time: 00:00:00
    
    136458 - Terminal 15 
              B1148 15 [009] - Open or Short to Plus
              Confirmed - Tested Since Memory Clear
                 Freeze Frame:
                        Fault Status: 00000001
                        Fault Priority: 2
                        Fault Frequency: 1
                        Reset counter: 238
                        Mileage: 1048574 km
                        Date: 2000.00.00
                        Time: 00:00:00
    
    395273 - Control Circuit for Signal Horn 
              B1344 14 [009] - Open or Short to Ground
              Confirmed - Tested Since Memory Clear
                 Freeze Frame:
                        Fault Status: 00000001
                        Fault Priority: 2
                        Fault Frequency: 1
                        Reset counter: 238
                        Mileage: 1048574 km
                        Date: 2000.00.00
                        Time: 00:00:00
    
    533269 - Databus 
              U1121 00 [009] - Missing Message
              Confirmed - Tested Since Memory Clear
                 Freeze Frame:
                        Fault Status: 00000001
                        Fault Priority: 6
                        Fault Frequency: 1
                        Reset counter: 238
                        Mileage: 1048574 km
                        Date: 2000.00.00
                        Time: 00:00:00
    
    539925 - Databus 
              U1121 00 [009] - Missing Message
              Confirmed - Tested Since Memory Clear
                 Freeze Frame:
                        Fault Status: 00000001
                        Fault Priority: 6
                        Fault Frequency: 1
                        Reset counter: 238
                        Mileage: 1048574 km
                        Date: 2000.00.00
                        Time: 00:00:00
    
    541973 - Databus 
              U1121 00 [009] - Missing Message
              Confirmed - Tested Since Memory Clear
                 Freeze Frame:
                        Fault Status: 00000001
                        Fault Priority: 6
                        Fault Frequency: 1
                        Reset counter: 238
                        Mileage: 1048574 km
                        Date: 2000.00.00
                        Time: 00:00:00
    
    542229 - Databus 
              U1121 00 [009] - Missing Message
              Confirmed - Tested Since Memory Clear
                 Freeze Frame:
                        Fault Status: 00000001
                        Fault Priority: 6
                        Fault Frequency: 1
                        Reset counter: 238
                        Mileage: 1048574 km
                        Date: 2000.00.00
                        Time: 00:00:00
    
    549141 - Databus 
              U1121 00 [009] - Missing Message
              Confirmed - Tested Since Memory Clear
                 Freeze Frame:
                        Fault Status: 00000001
                        Fault Priority: 6
                        Fault Frequency: 1
                        Reset counter: 238
                        Mileage: 1048574 km
                        Date: 2000.00.00
                        Time: 00:00:00
    
    549909 - Databus 
              U1121 00 [009] - Missing Message
              Confirmed - Tested Since Memory Clear
                 Freeze Frame:
                        Fault Status: 00000001
                        Fault Priority: 6
                        Fault Frequency: 1
                        Reset counter: 238
                        Mileage: 1048574 km
                        Date: 2000.00.00
                        Time: 00:00:00
    
    552213 - Databus 
              U1121 00 [009] - Missing Message
              Confirmed - Tested Since Memory Clear
                 Freeze Frame:
                        Fault Status: 00000001
                        Fault Priority: 6
                        Fault Frequency: 1
                        Reset counter: 238
                        Mileage: 1048574 km
                        Date: 2000.00.00
                        Time: 00:00:00
    
    554517 - Databus 
              U1121 00 [009] - Missing Message
              Confirmed - Tested Since Memory Clear
                 Freeze Frame:
                        Fault Status: 00000001
                        Fault Priority: 6
                        Fault Frequency: 1
                        Reset counter: 238
                        Mileage: 1048574 km
                        Date: 2000.00.00
                        Time: 00:00:00
    
    555029 - Databus 
              U1121 00 [009] - Missing Message
              Confirmed - Tested Since Memory Clear
                 Freeze Frame:
                        Fault Status: 00000001
                        Fault Priority: 6
                        Fault Frequency: 1
                        Reset counter: 238
                        Mileage: 1048574 km
                        Date: 2000.00.00
                        Time: 00:00:00
    
    555285 - Databus 
              U1121 00 [009] - Missing Message
              Confirmed - Tested Since Memory Clear
                 Freeze Frame:
                        Fault Status: 00000001
                        Fault Priority: 6
                        Fault Frequency: 1
                        Reset counter: 238
                        Mileage: 1048574 km
                        Date: 2000.00.00
                        Time: 00:00:00
    
    555541 - Databus 
              U1121 00 [009] - Missing Message
              Confirmed - Tested Since Memory Clear
                 Freeze Frame:
                        Fault Status: 00000001
                        Fault Priority: 6
                        Fault Frequency: 1
                        Reset counter: 238
                        Mileage: 1048574 km
                        Date: 2000.00.00
                        Time: 00:00:00
    
    556053 - Databus 
              U1121 00 [009] - Missing Message
              Confirmed - Tested Since Memory Clear
                 Freeze Frame:
                        Fault Status: 00000001
                        Fault Priority: 6
                        Fault Frequency: 1
                        Reset counter: 238
                        Mileage: 1048574 km
                        Date: 2000.00.00
                        Time: 00:00:00
    
    558101 - Databus 
              U1121 00 [009] - Missing Message
              Confirmed - Tested Since Memory Clear
                 Freeze Frame:
                        Fault Status: 00000001
                        Fault Priority: 6
                        Fault Frequency: 1
                        Reset counter: 238
                        Mileage: 1048574 km
                        Date: 2000.00.00
                        Time: 00:00:00
    
    558869 - Databus 
              U1121 00 [009] - Missing Message
              Confirmed - Tested Since Memory Clear
                 Freeze Frame:
                        Fault Status: 00000001
                        Fault Priority: 6
                        Fault Frequency: 1
                        Reset counter: 238
                        Mileage: 1048574 km
                        Date: 2000.00.00
                        Time: 00:00:00
    
    559125 - Databus 
              U1121 00 [009] - Missing Message
              Confirmed - Tested Since Memory Clear
                 Freeze Frame:
                        Fault Status: 00000001
                        Fault Priority: 6
                        Fault Frequency: 1
                        Reset counter: 238
                        Mileage: 1048574 km
                        Date: 2000.00.00
                        Time: 00:00:00
    
    559637 - Databus 
              U1121 00 [009] - Missing Message
              Confirmed - Tested Since Memory Clear
                 Freeze Frame:
                        Fault Status: 00000001
                        Fault Priority: 6
                        Fault Frequency: 1
                        Reset counter: 238
                        Mileage: 1048574 km
                        Date: 2000.00.00
                        Time: 00:00:00
    
    919560 - Light Switch 
              B126A 29 [009] - Signal Implausible
              Confirmed - Tested Since Memory Clear
                 Freeze Frame:
                        Fault Status: 00000001
                        Fault Priority: 3
                        Fault Frequency: 1
                        Reset counter: 238
                        Mileage: 1048574 km
                        Date: 2000.00.00
                        Time: 00:00:00
    
    947204 - Control Module for Wiper Motor 
              U10A3 00 [009] - No Communications
              Confirmed - Tested Since Memory Clear
                 Freeze Frame:
                        Fault Status: 00000001
                        Fault Priority: 2
                        Fault Frequency: 1
                        Reset counter: 238
                        Mileage: 1048574 km
                        Date: 2000.00.00
                        Time: 00:00:00
    
    15360256 - Component Protection 
              U1101 00 [009] - Active
              Confirmed - Tested Since Memory Clear
                 Freeze Frame:
                        Fault Status: 00000001
                        Fault Priority: 4
                        Fault Frequency: 1
                        Reset counter: 238
                        Mileage: 1048574 km
                        Date: 2000.00.00
                        Time: 00:00:00
    
    
    -------------------------------------------------------------------------------
    Address 19: CAN Gateway (J533)       Labels: 5Q0-907-530-V1.clb
       Part No SW: 5Q0 907 530 E    HW: 5Q0 907 530 E
       Component: GW MQB Mid    121 1109  
       Revision: --------    Serial number: 0000073193
       Coding: 000000342B086400EF0006481C0F00000001000000000000000000000000
       Shop #: WSC 01357 011 00200
       ASAM Dataset: EV_GatewLear 006010
       ROD: EV_GatewLear.rod
       VCID: 3365F3749A38A9A479-8066
    
    No fault code found.
    
    End-------------------------(Elapsed Time: 00:36)-------------------------
    There are some different Databus error messages in the latest auto-scan report, which I assume result from the fact that I have had to make coding changes to delete some of the DTCs from non existent equipment, but the latest emergence of the CP message (when none appeared previously) is baffling - to me at least!

    Does anyone have a hypothesis for this revelation - for example, is there an upper limit in the number of DTCs that can be reported by ODBII, or RT's software for a single control module- and If so, which DTCs are prioritised?

    Don

    PS: for anyone with an MQB platform vehicle, the way to delete bulb-out errors is to change the setting on the appropriate Leuchte channel (3)-Leuchte ****** -Fehlerort mittleres Byte DTC-DFCC * to Hex00
    Last edited by DV52; 04-27-2016 at 07:54 PM.
    VW Golf MkVII (MY13) - A3 8V hatch (MY17)

  6. #44
    Ross-Tech Employee Eric's Avatar
    Join Date
    Jan 2014
    Location
    Lansdale, PA, USA
    Posts
    2,789
    Post Thanks / Like
    Quote Originally Posted by DV52 View Post
    for example, is there an upper limit in the number of DTCs that can be reported by ODBII, or RT's software for a single control module- and If so, which DTCs are prioritised?
    Blasphemy! Out of two systems, one with gigabytes of addressable memory, and the other one being an embedded controller, you're asking if our software is the limiting factor? Granted, some embedded systems do have tons of memory (probably navigation), but I don't think that's the case for 09. I could be wrong and you could have a 64bit ARM in there with 8GB of RAM, but I somehow doubt it
    I checked our code and it looks like it should be able to buffer just about 75 UDS DTCs for processing (that's of course per control module). We could no doubt make that many times bigger, but it seems so far either control modules just hang in the middle of giving their DTCs, or don't have enough room reserved in their EEPROM for this (a supposition on my part). I don't see a limiting factor on the OBDII (really, VAG) protocol side either, and in any case the first one to hit would be 255, and then 65535.
    You ain't metal till you got a clutch pedal

  7. Likes DV52, Uwe, Jack@European_Parts liked this post
  8. #45
    Verified VCDS User
    Join Date
    May 2014
    Location
    Melbourne, Australia
    Posts
    2,876
    Post Thanks / Like
    Quote Originally Posted by Eric View Post
    Blasphemy! Out of two systems, one with gigabytes of addressable memory, and the other one being an embedded controller, you're asking if our software is the limiting factor? Granted, some embedded systems do have tons of memory (probably navigation), but I don't think that's the case for 09. I could be wrong and you could have a 64bit ARM in there with 8GB of RAM, but I somehow doubt it
    I checked our code and it looks like it should be able to buffer just about 75 UDS DTCs for processing (that's of course per control module). We could no doubt make that many times bigger, but it seems so far either control modules just hang in the middle of giving their DTCs, or don't have enough room reserved in their EEPROM for this (a supposition on my part). I don't see a limiting factor on the OBDII (really, VAG) protocol side either, and in any case the first one to hit would be 255, and then 65535.
    Eric: Thanks for the reply - I guess then that hidden CP message might have been a consequence of the unusual configuration of the BCM in a test-jig (i.e. perhaps the CP test process in the CAN Gateway needs a certain amount of data from other modules (which aren't present) before it signals the error message - granted this is a wild supposition on my uninformed part)!

    Don

    PS: I will seek absolution and do serious penance for my sacrilegious and thoroughly reprehensible inference about RT software limitations!!
    VW Golf MkVII (MY13) - A3 8V hatch (MY17)

  9. Likes Eric, Uwe liked this post
  10. #46
    Verified VCDS User
    Join Date
    May 2014
    Location
    Melbourne, Australia
    Posts
    2,876
    Post Thanks / Like
    I really do recommend building a test-jig to anyone who is on the "OBDII learning curve" (like me) - it's an informative and convenient way of finding-out how the network topology works on these vehicles! But alas it's not all beer-and-skittles as is evidenced by my latest conundrum for which I seek help!

    A good use of the test-jig is to trial Leuchte programming scenarios - without the need for an actual car! This can be easily done by adding a string of LEDs (with suitable ballast resistors) to the BCM pins to simulate the lamps and small PCB switches to emulate the car's lighting switches. This is all simple until I try to simulate the turn signal switch!

    The WD for the mk7 shows that the turn-signal switch is connected to the steering column control module (unfortunately the inside switch contacts aren't shown on the WD) and there appears to be no physical wire connection to the BCM. The network arrangement for the control modules on a mk7 shows that both the BCM and the steering column control module share the convenience CAN bus, so I assume that this is the way that the turn signal message is passed-onto the BCM (and the door control modules - for the repeater lamps on the mirrors) - see diagram below:



    So my question is this: Assuming that my understanding above is correct (and I hope that it isn't correct), is there any way to simulate the turn signal in the absence of any physical blinker switch pins on the BCM - without having a bulky J527 control module connected to the test jig? I'm aware that the turn-signal can be enabled through the "Output test" screen, but this only lights-up the specific blinker lamps- it doesn't engage any Leuchte commands that are applied to additional lamps.

    Thanks in advance for any advice

    Don
    VW Golf MkVII (MY13) - A3 8V hatch (MY17)

  11. Likes mattylondon liked this post
  12. #47
    Benevolent Dictator Uwe's Avatar
    Join Date
    Jan 2014
    Location
    Earth
    Posts
    25,072
    Post Thanks / Like
    Blog Entries
    1
    Quote Originally Posted by DV52 View Post
    So my question is this: Assuming that my understanding above is correct (and I hope that it isn't correct), is there any way to simulate the turn signal in the absence of any physical blinker switch pins on the BCM - without having a bulky J527 control module connected to the test jig?
    I doubt it.

    Well, I suppose one could monitor a real J527 to see what CAN telegrams it produces that correspond to the various turn signal switch states (or change of states) and then substitute something some smaller device capable of simulating them, but that seems like far more work than just wiring up a real J527.

    -Uwe-
    The engineering problems are likely insurmountable. It would be like proposing to land a rocket booster section on a barge floating in the middle of the ocean.

  13. Likes DV52, Jack@European_Parts liked this post
  14. #48
    Verified VCDS User
    Join Date
    May 2014
    Location
    Melbourne, Australia
    Posts
    2,876
    Post Thanks / Like
    ^^^ Uwe: Advice appreciated and accepted - Thanks. I've sourced a second-hand J527 locally - I'll see if I can strip everything that's superfluous from the control module to get it down to its bare-bones)
    Don
    VW Golf MkVII (MY13) - A3 8V hatch (MY17)

  15. #49
    NostraJackAss Jack@European_Parts's Avatar
    Join Date
    Jan 2014
    Location
    1001 State Route 17K Montgomery New York 12549
    Posts
    17,015
    Post Thanks / Like
    I doubt it.

    Well, I suppose one could monitor a real J527 to see what CAN telegrams it produces that correspond to the various turn signal switch states (or change of states) and then substitute something some smaller device capable of simulating them, but that seems like far more work than just wiring up a real J527.

    -Uwe-
    Well I sure wish someone would turn on the recorder for the ESCL command authorization packets, and build an emulator already for these old A8 and T-rigs.
    Last edited by Jack@European_Parts; 05-06-2016 at 03:38 PM.
    European Parts Emporium/Performance / Immobilizer Solutions EPE
    Certified Master Trained NY/BAR/BAD 7076062/ASE/SAE/NASTF Legal Factory Authorized/Licensed GeKo/FaZit # 403738
    Specializing in Custom Services IE: "welding-fabrication" / EPA-SMOG Update or Pass-Thru-Programming / Data Transfer / Immobilizers & OEM Quality Parts
    Above Magic! No Written record, AUTO-SCAN or Appointment = NO HELP!
    www.FixMyEuro.com <<<<<CLICK HERE! or vwemporium@aol.com ( JPPSG & Unverified members need not PM me & Please don't email or call facility for free tech support...use the forum )
    Getting you CONTROL again of your property - TAKE IT! In Conjunction with.........

  16. Likes Eric liked this post
  17. #50
    Verified VCDS User
    Join Date
    May 2014
    Location
    Melbourne, Australia
    Posts
    2,876
    Post Thanks / Like
    OK, its been some time since I first contemplated the concept of a test bench (thanks again to those here who helped me take my fledgling steps) and my embryonic musings have matured somewhat. Because of a local interest down here in Leuchte adaptation channels, the focus of the test bench has been somewhat hijacked towards this direction. It's now a purpose-built training tool for the occasional tutorial to forum members that happen to wonder down this way and are crazy enough to express an interest in wanting to learn about Leuchte programming!! Works quite well for this purpose because all errors are trivial - hasn't been broken yet!!

    Here's what it looks like (I had to raid the LED junk-box to make-up the simulated taillight/headlight board and the simulated rotary light switch still needs more work):


    But my real purpose in writing is to ask a couple of perhaps "cheeky" questions.
    Question 1: I'm interested in understanding more about the VIN that's recorded in these control modules. It seems that the number is held no where else but in the CAN Gateway (at least this appears to be the case in the limited number of control modules in my test bench). Is this true?.
    Question 2: is there any way that I can get access to the memory location that holds this number in the CAN Gateway. I assume that this isn't a firmware matter, so it must be held in accessible memory (I would think). I'm comfortable trying anything on the CAN Gateway on the test bench that might not be prudent on my actual car - so all suggestions welcomed


    Don
    VW Golf MkVII (MY13) - A3 8V hatch (MY17)

  18. Likes mattylondon, Zenerdiode, Sebastian liked this post

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •