Jump to content


  • Content Count

  • Joined

  • Last visited

1 Follower

About dv52

  • Rank
    Certified R Fan

Profile Information

  • Location
    Melbourne Australia

Personal Information

  • Name

Recent Profile Visitors

2,383 profile views
  1. hmm........the Black colored circle means that the hex22 module has been added to the Gateway list, but it hasn't responded when polled by the hex19 module. If it was my car I would be checking the wiring loom and the connector - pay particular attention to the CAN high/Low wires/pins on the 8 x pin connector - and the power supply terminals (especially earth). Don
  2. @Markt hi First thing is to get the installation list in the Gateway module fixed. OBD11 has an automatic fix for this called AUTOCODE - see testeronline post about two-thirds down the thread HERE After this, clear the errors and re-post another copy of your scan report - unedited please Don
  3. @CosR. hmm......... thanks for the kind words, but I very much doubt that anyone outside the VW mother-ship really knows about Leuchte-programming. Problem is that this stuff seems to be commercial in confidence and there's nothing official that I can find in the public domain - so my understanding is all guess work!! 😀 As to your wants - now I understand what you are after! Try this: on Leuchte2SL VLB10 and Leuchte3SL VRB21 for the adaptation channel Lichtfunktion B, ONLY if the current value on your car is not active, change to Standlicht vorn (Positionslicht; Begrenzungslicht) But a word of caution if you implement this tweak - the reason why these lamps are dimmed to a low level when used other than as DRLs is because they have no cut-off characteristics in their reflectors (called a "luminaire"). If you use these lamps during low ambient light conditions, or at night-time at full illumination, they will have the tendency to blind oncoming traffic, So -be considerate to drivers coming the other way before deciding to move the rotary light switch to the PL position -please! Don
  4. hmm........... OK - there might be a slight misunderstanding regarding how Leuchte-sets operate on MQB platform vehicles. So, the first thing is definition of terms: when these lamps illuminate WITHOUT low-beam lights, they are called "Daytime Running Lights" (DRLs) - when they illuminate WITH low-beam lights, let's call them "Parking Lights" (PLs) If your car is a UK Golf R with LED specs, then likely VLB10 would have been factory coded as shown at the end of this post and VRB21 would have been the same with the exception of the channel in the second insert below. Note is that the DRL function happens on Lichtfunktion A - therefore the illumination level for this function is determined by Dimmwert AB. The factory set value is 100 as shown - which is already at maximum illumination. Now, you may have seen some Dimmwert values for LED lamps as high as 127- but this value only applies to specific Lasttyp settings (like 1 - LED Tagfahrlichtmodul Versorgung). However, just because 127 is a higher number than 100 doesn't mean that the illumination level of the LED is higher. Your Lasttyp setting as shown below uses what's called "analogue control" for the Pulse Width Modulation waveform (PWM-google it) to the LEDs. The other Lasttyp settings that allow a maximum value of 127, use "digital control". BUT, both Dimmwert values produce maximum illumination for their respective Lasttyp settings. So, bottom line = Your DRL function is already factory set to its maximum illumination value - which kind-of makes sense IMO (why wouldn't the factory do this as the default value?). If you want the DRL illumination to decrease - simply reduce the value of Dimmwert AB. The PL function happens on Lichtfunktion C and therefore its illumination is determined by Dimmwert CD. Changing this channel ONLY effects the PL illumination function (and the Lichtfunktion D function which is single-side PL) Don Lasttyp > 4 - LED Tagfahrlichtmodul Signal Lampendefektbitposition > 48 Fehlerort mittleres Byte DTC-DFCC > 4A Lichtfunktion A > Daytime running lights Lichtfunktion B > not active Dimmwert AB > 100 Lichtansteuerung HD AB > Always Lichtfunktion C > Standlicht allgemein (Schlusslicht; Positionslicht; Begrenzungslicht) Lichtfunktion D > Parklicht links (beidseitiges Parklicht aktiviert li & re) Dimmwert CD > 26 Dimming Direction CD > maximize Lichtfunktion E > not active Lichtfunktion F > not active Dimmwert EF > 0 Dimming Direction EF > maximize Lichtfunktion G > not active Lichtfunktion H > not active Dimmwert GH > 0 Leuchte3SL VRB21-Lichtfunktion D 3 > Parking light right
  5. @CosR What you need to do is to alter the Leucte-set values for the DRLs on your car. Problem is that the identity of the Leuchte-sets varies depending on what type of lamps are fitted into the headlight assemblies and it also depends on how the Leuchte-sets on your car were factory programmed (this varies with mk7 model and country of sale). So, first question: does your car have incandescent DRL lamps, or LED type? Second question: if incandescent, please post-up the complete Leuchte-set values on your car for Leuchte4TFL LB4, or for Leuchte5 TFL RB32 if LED, please post-up the complete Leuchte-set values on your car for either Leuchte2SL VLB10 , or for Leuchte3SL VRB21 Don
  6. dv52

    VagCom for £55?

    hmm............ I'm amazed and appalled at the casual way that those who have knowingly purchased fake VCDS devices either simply don't care that they have supported IP theft, or they believe that it's OK to do so. I wonder how these same individuals would feel if it was their ideas that were being stolen and passed-of as the genuine product. It's easy and somewhat convenient for purchasers of these fake cables to believe that it's not them that has stolen from Uwe Ross - doubtless these individuals believe that the theft was perpetrated by the sellers (not the purchasers - so it's OK). But the reality is that the only reason why this market for fake VCDS devices exist at all is because there are willing buyers. Take a good look at yourselves people - IP theft is real theft; as real as if purchasers stole money directly from Ross-Tech!! Amazing!!! Don
  7. @BRK: Hi. I have no idea how the inner tail lights are factory programmed on an ATLAS Sel Premium - if you post-up a copy of the 2 x Leuchte-sets in my instructions (which to be fair were intended for a Golf mk7) I will take a look. As for your problem and based on not much information - my hunch is that you might have incorrect settings on the fault monitoring channels below: Lampendefektbitposition Fehlerort mittleres Byte DTC-DFCC As I have said, it's a guess really, but check that the values for these channels on the left side (i.e. Leuchte23SL HLC10) have not changed Don
  8. Ben: Hi It's going to be impossible to be precise about your "van" because all we know about it is that it's a "van"!! However, if the "van" was built on a MQB platform (as is the Golf mk7) - here's what could happen: Assuming that the car has the requisite physical equipment installed, the first task would be to make an auto-scan of the vehicle with VCDS. This tells you the starting position for coding purposes. You would then need to investigate the long-code strings in the control modules. For MQB cars, the specific modules would be @ address: hex01 (Engine), hex03 (ABS), hex09 (Gateway), hex17 (Instrument cluster), hex5F (Infotainment), hexA5 (front facing camera) and finally hex13 (front radar). So, if you aren't familiar with the term "long-code" - this is a feature that every module has; it's basically a number that's attached to the module and VCDS reports this number in hexadecimal (hex) nomenclature. As you may be aware, hex numbers can be translated into binary numbers in which each digit is expressed as either one, or zero. These one/zero states are like a string of software switches which are either ON, or OFF. Each of these software switches has a specific purpose related to the various available options on the car (like ACC) This is a long winded way of explaining that the long-code value tells the control module what peripherals are installed in the car and therefore what functions to operate (and which function to not-operate). On your van, it sounds like some of the software switches for ACC are enabled at the factory, but some are not. So, the first task is to look at the long-code strings that are reported by the auto-scan report related to the ACC function and to ascertain which software switches have not been enabled at the factory. Fortunately, VCDS helps in this task by describing the function of lots (but not all) of the software switches in their "Long Code Helper" screens - so this is where you should start the investigation! The general long-code instructions for enabling ACC for MQB platform cars (not necessarily your "van") are as follows (note-some of these software switches will already be set in your "van" from the factory): 01 – Engine – for manual gearbox, tick ACC – PR-8T5 – for DSG gearbox, set ACC with Front Assist (PR-8T3, PR-8T8) 03 – ABS (coding for 29 bit) you ned to edit bit 24: – for manual gearbox, set: 14 (or 16) – for manual gearbox and Lane Assist, set F4 – for DSG gearbox, set F8 09 – Gateway – Add 13 – Auto Dist. Reg on the installation list – Under Adaptation change steering wheel type to ACC 17 – Instrument – On the cluster set all the ticks for Front Assist and Distance Regulation 5F – Radio – Set all the ticks for Front Assist, ACC and PreCrash A5 – Front Camera – Set presence of ACC 13 – Radar – Set presence of ACC After this, it's then a matter of reviewing what (if any) errors appear and possibly changing the values of adaptation channels in various modules. Adaptation channels are a different feature of control modules - once a software switch in long-code is turned-on to enable a particular function, adaptation channels then tell the module how to operate that function. Herein endeth the introductory VCDS lesson!! Don
  9. dv52

    Headlight range

    @bigearmuffs: Hi. Why do you believe that the Golf R has a throw problem? Does the car have any errors on the auto-scan? I assume that we are dealing with HID lamps - if so, you could try resetting the car's understanding of level-ground - see the procedure below. Headlight - basic setting Don
  10. ^^^^^ @TheBlondeFella hmm........ I'm not convinced that the calculation of differential wheel speed as a surrogate for temperature should be discounted in your instance. It really all depends on what you mean by " reasonably gentle 10-15 minute track session". Clearly the blue-ing of the disks suggests a moderately aggressive use of the brakes -so perhaps the same principle was at play - maybe? My suspicion is that the calculation of temperature uses both the aggregated time period between successive brake applications and brake pedal pressure (these are able to be recorded by the controlling module) AND differential in peripheral speed of the individual wheels. Don
  11. @Paulius: Hi. very interesting, thanks for sharing. As you say "I suspect that "there are no brake temperature sensors at all" - so, clearly the error is based on a calculation (the term "elaboration" in the fault message also kind-of supports this hypothesis). My hunch is that the surrogate for actual Brake temperature is measured via the individual wheel speed sensors - the assumption being that as the brakes heat-up, the peripheral wheel speed increases slightly due to metal/rubber expansion. By using the same principle as is used in the determination of indirect tire pressure (which also doesn't have pressure sensors) individual wheel speeds can be compared to reliably measure slight variations. 225/45-R17 tires are 1.34 inches (34 mm) smaller in diameter than 215/55-R17 tires. My hunch (guess really) is that this may have caused the error - maybe? Don
  12. @8BallAddict: Hi - very clear reason to explain your tweak outcome; you used the same "Blinken links aktiv (beide Phasen)" command on the 16 Leuchte3SL VRB21-Lichtfunktion G 3 channel ; which should have the value "Blinken rechts aktiv (beide Phasen)". "Links" in German means "left" and "rechts" means "right". 16 Leuchte3SL VRB21 controls the right-side lamp (notice "R" in the name) - so you need to use the right-side Leuchte command. That's why both DRLs dimmed when indicating left and neither DRL dimmed when indicating right!! QED Don
  13. dv52

    Stop start

    Booth: Hi - the reason why the light on the Start Stop button isn't illuminated is because neither the "voltage", or the "temperature" method tweaks actually disable the SS function! Both of these tweaks work by fooling the SS system to not switch-off the engine - but the SS system is still always active with these tweaks (if the SS switch on the center console isn't pressed). For the "voltage" tweak, increasing the adaptation channel value effectively says to the SS decision making algorithm that there is insufficient capacity in the battery to restart the engine - because there is not enough head-room between the actual battery voltage and the increased threshold voltage in the changed adaptation channel. Don
  14. dv52

    DRL help

    Jazz, it really depends on what country you are from but for UK models, try this: Leuchte3SL VRB21 and Leuchte2SL VLB10 ONLY IF Lichtfunktion C = Standlicht allgemein (Schlusslicht; Positionslicht; Begrenzungslicht), change Dimmwert CD to 100 (value should be 26 as factory set) Don
  15. ^^^Donny: with DV52 tails, the inner lights will illuminate to 28% when the PL is switch-on and this illumination level will change to 100% when the brakes are applied. So the tweak already does this! Don
  • Create New...