|
|
Post by shiawa on Mar 2, 2019 23:45:08 GMT
Hey Guys. Is there any way to lower the activation speed of the automatic high beam lights?
The standard setting is that it activates at 60 KM/H
|
|
|
|
Post by ofektal8 on Mar 3, 2019 11:31:34 GMT
Hey Guys. Is there any way to lower the activation speed of the automatic high beam lights? The standard setting is that it activates at 60 KM/H Yea i just did it. Go into A5 Module, Adaptations, and click "activation speed for high beam assistant" . There you will be able to change it to whatever you want.  |
|
|
|
Post by newty on Mar 4, 2019 8:17:45 GMT
Activation speed is a 5Q0 Adaption and not avaliable anymore in the facelift's 3Q0-Type cameras. In 3Q0 no change is possible, it either hardcoded or parametrised. Either way, no real chance of changing this
|
|
|
|
Post by vwjap on Mar 4, 2019 15:08:33 GMT
Was going to put up it wasn’t there in the newer a5 module
Control unit: A5 Front Sensors Driver Assistance System
System description: MQB_B_MFK
Software number: 3Q0980654G
Software version: 0231
Hardware number: 3Q0980654
Hardware version: H06
Serial number: 22011712P21805
ODX name: EV_MFKBoschMQBB
ODX version: 001001
Backup name: park
Long coding:
000307000000040100022355C050A90098000E300040
Adaptations:
Road sign detection fusion mode:
Road sign fusion
Adaptation_tsr:
Par_country_mode:
Automatic
Par_relevance_mode:
enabled
Par_country_code_RSR:
0
Par_country_code_VZF:
0
Deactivate production mode:
Deactivating
Calibration target position:
Target 1, calibration mark 1, x-coordinate:
2565 mm
Target 1, calibration mark 1, y-coordinate:
825 mm
Target 1, calibration mark 1, z-coordinate:
1530 mm
Target 1, calibration mark 2, x-coordinate:
2565 mm
Target 1, calibration mark 2, y-coordinate:
-825 mm
Target 1, calibration mark 2, z-coordinate:
1530 mm
Target 1, calibration mark 3, x-coordinate:
2565 mm
Target 1, calibration mark 3, y-coordinate:
825 mm
Target 1, calibration mark 3, z-coordinate:
870 mm
Target 1, calibration mark 4, x-coordinate:
2565 mm
Target 1, calibration mark 4, y-coordinate:
-825 mm
Target 1, calibration mark 4, z-coordinate:
870 mm
BAP personalization:
activated
Body height wheel house edge:
Body height left front wheel house edge:
673 mm
Body height right front wheel house edge:
675 mm
Body height left rear wheel house edge:
673 mm
Body height right rear wheel house edge:
674 mm
Direct. stab. assist speed threshold during towing mode:
300 km/h
System mode, lane depart. warn,:
Steering wheel vibration not active
standstill_mode:
Not activated
Warning intensity, lane depart. warning:
Medium
Activating and deactivating all development messages:
Activation_of_development_messages_reserved:
Not activated
Activation_of_development_messages_lane:
Not activated
Activation_of_development_messages_WLA:
Not activated
Activation_of_development_messages_VZF/TSR:
Not activated
Activation_of_development_messages_EHR:
Not activated
Activation_of_development_messages_HCA_lane:
Not activated
Activation_of_development_messages_HCA_state:
Not activated
Activation_of_development_messages_internal:
Not activated
Xcp_interface:
Not activated
Mask_error_reactions_for_development:
Not activated
Initial calibration, result:
Pitch angle:
1.020 °
Yaw angle:
-0.155 °
Roll angle:
-0.020 °
Camera height:
1319 mm
Production mode:
Deactivating
Roller test bench mode, functional:
Not activated
Personalization of intervention moment at T. 15 on:
Last setting
Distance to calibration field:
1500 mm
Axle offset:
Front axle transverse position:
7 mm
Rear axle transverse position:
-0 mm
Switch-on condition, lane depart. warn.:
on (setting via menu)
Masked_fault_classes:
255
255
255
255
WLA_adjustment:
BrightnessThreshold_active:
0
BrightnessThreshold_passive:
0
|
|
|
|
Post by dv52 (Australia) on Mar 4, 2019 23:39:47 GMT
Activation speed is a 5Q0 Adaption and not avaliable anymore in the facelift's 3Q0-Type cameras. In 3Q0 no change is possible, it either hardcoded or parametrised. Either way, no real chance of changing this newty: I suspect that the facility was removed because the sensing equipment/software is not accurate at these lower speeds! It should be remembered that HBA really is a high-speed function - stuff starts to get a bit "iffy" when the range of operation is extended into the lower lower speeds - I reckon
Don
|
|
|
|
Post by heihei12345 on Mar 28, 2020 18:44:14 GMT
Anyone have a solution for this? Has the same problem on my e-golf 2019
|
|
|
|
Post by Carolco on Mar 28, 2020 21:54:09 GMT
The cameras mounted in golf after mk7 dont have this option. In the mk7.5 no. The mk8 .... don’t know
|
|
|
|
Post by neil543 on Apr 16, 2020 16:25:18 GMT
Can you code a new hba module this way?
|
|
henno
Closed beta tester
Posts: 33 
|
Post by henno on Apr 19, 2020 6:37:20 GMT
Speed value is in dataset.
With the right dataset it even works while stand still
|
|
|
|
Post by strata on Apr 11, 2021 22:52:04 GMT
Activation speed is a 5Q0 Adaption and not avaliable anymore in the facelift's 3Q0-Type cameras. In 3Q0 no change is possible, it either hardcoded or parametrised. Either way, no real chance of changing this I have these settings available in my mk 7.5, are you saying they wont be affective? 3G0857511AE software version 0003 |
|
|
|
Post by dv52 (Australia) on Apr 12, 2021 4:24:46 GMT
Speed value is in dataset. With the right dataset it even works while stand still henno: I've absolutely no doubt that you can get HBA to operate at low speeds (like standstill) by changing the appropriate dataset value (if you can find it)- but this doesn't mean that it will actually work at low-speeds. As I said previously the reaction speed of the shutters and the ability of the HBA to track the oncoming vehicle(s) becomes much more difficult as the speed is lowered. I suspect that the removal of the tweak channel was driven at least in part by these difficulties.
Don
|
|
|
|
Post by newty on Apr 12, 2021 15:22:41 GMT
Activation speed is a 5Q0 Adaption and not avaliable anymore in the facelift's 3Q0-Type cameras. In 3Q0 no change is possible, it either hardcoded or parametrised. Either way, no real chance of changing this I have these settings available in my mk 7.5, are you saying they wont be affective? 3G0857511AE software version 0003 As we are talking about the full feature camera (triangle shape, capable of HBA, LA, DLA, TSR) all this info is not applicable to the light sensor only capable of HBA. Give it a try! |
|
|
|
Post by strata on Apr 12, 2021 19:02:10 GMT
Aha! Very interesting, thank you! - In that case I have a lot of questions regarding settings for my HBA, but I should be starting a new thread for that right? On a side note I will probably be getting the full feature camera if a new windshield is ever required.  |
|
xarisp
Junior Member
Posts: 85
|
Post by xarisp on Feb 12, 2022 6:36:07 GMT
Speed value is in dataset. With the right dataset it even works while stand still henno: I've absolutely no doubt that you can get HBA to operate at low speeds (like standstill) by changing the appropriate dataset value (if you can find it)- but this doesn't mean that it will actually work at low-speeds. As I said previously the reaction speed of the shutters and the ability of the HBA to track the oncoming vehicle(s) becomes much more difficult as the speed is lowered. I suspect that the removal of the tweak channel was driven at least in part by these difficulties.
Don
I don't think that there would be such a problem if someone lowered the speed. The manual says that in most countries the speed for light assist is set at 30 and for some countries its set at 60 |
|
|
|
Post by dark5had0w on Feb 22, 2022 1:04:10 GMT
when i had High Beam Assist - the activation speed was 60 km/h.
i then retrofitted Smart Light Assist (Skoda's version of Dynamic Light Assist, i.e. high beam masking/shaping), and now the activation speed is 40 km/h.
i did have a parameter file, specific for SLA, uploaded to my 4B module, after the retrofit. it must've had the lower activation speed somewhere in the parameter dataset.
|
|
