Closed michalzahor closed 1 year ago
Look like an ELM clone issue. Could you send your log files and report result of ELM benchmark ?
attaching logs, ELM bench. was described in another post
using Carista Bluetooth module
The ELM seems to work, are you sure you're using the right XML file for your ECU (did you scan your vehicle ?)
Yes, I did.
It shows few red info that xml is not present for ECU and about 2 are not fully ok. But ABS was not mentioned there.
I'll post result of the scan tomorrow.
Try to increase CAN timeout in the bottom of the application window, and be careful when working on the ABS ECU of your vehicle, safety before all :)
Actualy I don’t understand why is there (ABS) status of ACC deacrivated by diag.
What I’m tesing to achieve is to enable ACC and DW ( I’ve koleos where this functionality was available for 0€ but it must be checked during order and it wasn’t ).
I have enabled DW and it is working. But ACC not - I have enabled it every where I found it, except ABS ecu.
Is there some special diag ecu that can keep holding this disabled or is it just diag function of ABS ecu ?
Will try to increate timeout tomorrow and see if I’ll be able to change this setting in ABS ecu.
Thank you
Michal
On 2 Jan 2019, at 22:02, Cedric PAILLE notifications@github.com wrote:
Try to increase CAN timeout in the bottom of the window, and be careful when working on the ABS ECU of your vehicle, safety before all :)
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or mute the thread.
How old is your koleos? 1 or 2 months? Does it have a radar or advanced camera under the windshield? One of them are required for activating ACC. Simple camera is not enough.
Koleos is from end of september 2018. It has RaCam. I’ve enabled distance warning and is working correctly.
I don’t have steering wheel with a button to change a distance for ACC but I think it should work without it.
After I have setup ACC is most ecus ( expect abs there is still “deactivated by diag” ) I’m not able use tempomant ( even basic CC ).
Michal Zahor
On 2 Jan 2019, at 22:41, shrlnm notifications@github.com wrote:
How old is your koleos? 1 or 2 months? Does it have a radar or advanced camera under the windshield? One of them are required for activating ACC. Simple camera is not enough.
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or mute the thread.
Result of ECU scan
Each recognised ECU with relevant XML should be there listed ? Then the list is kind of short :-)
In the terminal I see Some Warnings during scan process
I've tried to increase timeout ( from Auto, to 600ms ) and I was able to write data.
But then check ESP, check hill assist, warning in indicated . When I deactivate ACC in ABS/ESP, then the warning is done.
Seems like somewhere is ACC still considered as not active or prohibited.
After setting ACC activated in (ABS/ESP )
How the parameter looks before activation in ABS/ESP
Which changes did you do in radnav?
I have modified Rlink fw 7.x only using development menu. In DDT4ALL there is only radnav 2.x and 3.x and I was worried about applying changes using DDT4ALL.
In dev mod I have just enabled ACC in one place - don't remenber now where but it was in the same place where DW ( distance warning ) and DW is working.
Can you suggest other changes ? Is it safe to use radnav in DDT4ALL if my ecu database doesn't have radnav 7.x ?
The changes have to be made in Claster, RadNav, ABS/ESP and main changes in RaCam
These changes for RaCam
state_management_mph.P_sys_mph_ACCOFFToACCSpeedThresholdLow < 0x1c
0xa0
AEBS_ACC_config_2.P_sys_x_ACCEnable < 0x01 0x00
state_management_mph.P_sys_mph_MinimalSpeedRequestLow < 0x1e 0xa0
state_management_mph.P_sys_mph_ACCToACCOFFSpeedThresholdLow < 0x19 0xa0
AEBS37_VectorFeedBack.P_tng_m_DistVectorFeedBack_1_1 < 0x01 0x03
AEBS37_VectorFeedBack.P_tng_m_DistVectorFeedBack_1_2 < 0x03 0x04
state_management_kmh.P_sys_kmh_ACCOFFToACCSpeedThresholdLow < 0x2f 0xfa
state_management_kmh.P_sys_kmh_ACCToACCOFFSpeedThresholdLow < 0x28 0xfa
state_management_kmh.P_sys_kmh_MinimalSpeedRequestLow < 0x32 0xfa
Using ddt4all is preferable to change configuration in radnav then thru DeveloperSide. And do not remember to reset radnav after changes
RadNav_2*.xml is safe for your car
Is it safe to use for example RAdNat 3.x v3.3 in DDT4ALL if I have RLINK2 firmware 7.xx ? [ I see now your comment about RadNav_2* - ok I'll try use that ]
Rlink reset - long press on RLINK ( will go black for few seconds ) is the same as Hard reset ?
On 3 Jan 2019, at 09:47, shrlnm notifications@github.com wrote:
Using ddt4all is preferable to change configuration in radnav then thru DeveloperSide. And do not remember to reset radnav changes
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/cedricp/ddt4all/issues/126#issuecomment-451083148, or mute the thread https://github.com/notifications/unsubscribe-auth/AEwYdPLqEAnuHd770fsc9ex8sUB10etsks5u_cOOgaJpZM4ZnLTw.
Yes, long press on power button next to screen is equal to hard reset of radav
Don't know anything about resetting racam. Some ECUs require hard reset for changes take effect.
I suggest to save configuration before change something.
Is it possible to save current ECU config or just write down original value ?
The last version creates a file named screens.txt in the log directory. Here you can find old read values.
Here's a sample of a session :
ECU : UCT_E84_SERIE_3.json
@ 14:05:16.137
Screen : Misc Values and Timings Request : ReadDataByLocalIdentifier: general system infos
{"Status EEPROM": "Writing"}
@ 14:05:16.144
Screen : Misc Values and Timings Request : ReadDataByLocalIdentifier: misc timings and values
{"Voltage High 1": "193", "Timeout Button Windows": "60", "Voltage High 3": "181", "Voltage Low 1": "92", "Timeout Supply Voltage Range 3": "1000", "Voltage Low 3": "103", "Voltage Low 2": "97", "Timeout Runtime Stop Mode": "60000", "Voltage High 2": "187", "Timeout Window Button Short Push": "220", "Maximum Veh. Speed": "3", "Timeout Supply Voltage Range 5": "1000", "Timeout Supply Voltage Range 4": "1000", "Timeout Supply Voltage Range 1": "6000", "Multiplier Thermo Prot.": "10", "Timeout Supply Voltage Range 2": "1000", "Timeout Button Roof": "60", "Timeout Roof Button Window Close": "500", "Tolerance Window Button Open Timer": "5000", "Timeout Runtime Hydr. Pump": "18000", "Timeout Buzzer Alert": "30"}
@ 14:05:23.714
Blocked writing parameter :
{"Timeout Roof Button Window Close": "500", "Voltage High 1": "193", "Timeout Button Windows": "60", "Voltage High 3": "181", "Maximum Veh. Speed": "3", "Timeout Supply Voltage Range 3": "1000", "Voltage Low 3": "103", "Voltage Low 2": "97", "Timeout Runtime Stop Mode": "60000", "Voltage High 2": "187", "Timeout Window Button Short Push": "220", "Timeout Supply Voltage Range 5": "1000", "Timeout Supply Voltage Range 4": "1000", "Timeout Supply Voltage Range 1": "6000", "Multiplier Thermo Prot.": "10", "Timeout Supply Voltage Range 2": "1000", "Timeout Button Roof": "60", "Voltage Low 1": "92", "Tolerance Window Button Open Timer": "5000", "Timeout Runtime Hydr. Pump": "18000", "Timeout Buzzer Alert": "80"}
@ 14:05:26.941
Screen : Settings Request : ReadDataByLocalIdentifier: traceability data
{"Traceability Data": "\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000"}
@ 14:05:26.942
Screen : Settings Request : ReadDataByLocalIdentifier: general system infos
{"Status EEPROM": "Writing"}
@ 14:05:26.943
Screen : Settings Request : ReadDataByLocalIdentifier: endurance mode
{"Endurance Mode": "00"}
@ 14:05:26.944
Screen : Settings Request : ReadDataByLocalIdentifier: rollbar, montage
{"Rollbar Present": "00", "Montage Mode": "00", "Window Mode": "00"}
@ 14:05:31.938
Blocked writing parameter :
{"Endurance Mode": "Normal Mode"}
@ 14:05:34.618
Blocked writing parameter :
{"Rollbar Present": "Rollbar present", "Montage Mode": "Montage Mode", "Window Mode": "after 1s"}
@ 14:06:02.105
Screen : Timouts & Tolerances Request : ReadDataByLocalIdentifier: times latches
{"Tolerance Right Latch": "0", "Tolerance Left Latch": "0"}
@ 14:06:02.106
Screen : Timouts & Tolerances Request : ReadDataByLocalIdentifier: general system infos
{"Status EEPROM": "Writing"}
@ 14:06:02.107
Screen : Timouts & Tolerances Request : ReadDataByLocalIdentifier: tolerance values 2
{"Tolerance Start Hydraulic (close roof)": "0", "Tolerance Close Trunklid (close roof)": "0", "Tolerance Close Roof (close roof)": "0", "Tolerance Open Trunklid (close roof)": "0"}
@ 14:06:02.108
Screen : Timouts & Tolerances Request : ReadDataByLocalIdentifier: tolerance values 1
{"Tolerance Open Trunklid (open roof)": "0", "Tolerance Open Roof (open roof)": "0", "Tolerance Start Hydraulic (open roof)": "0", "Tolerance Close Trunklid (open roof)": "0"}
@ 14:06:02.109
Screen : Timouts & Tolerances Request : ReadDataByLocalIdentifier: timeout values 1
{"Timeout Open Trunklid 1 (open roof)": "0", "Timeout Close Trunklid 2 (open roof)": "0", "Timeout Unlock Trunklid 1 (open roof)": "0", "Timeout Close Trunklid 1 (open roof)": "0", "Timeout Unlock Trunklid 2 (open roof)": "0", "Timeout Open Roof 1 (open roof)": "0", "Timeout Open Roof 2 (open roof)": "0"}
@ 14:06:02.111
Screen : Timouts & Tolerances Request : ReadDataByLocalIdentifier: timeout values 2
{"Timeout Unlock Trunklid 1 (close roof)": "0", "Timeout Close Trunklid 1 (close roof)": "0", "Timeout Unlock Trunklid 2 (close roof)": "0", "Timeout Close Trunklid 2 (close roof)": "0", "Timeout Open Trunklid 1 (close roof)": "0", "Timeout Close Roof 1 (close roof)": "0", "Timeout Close Roof 2 (close roof)": "0"}
@ 14:06:09.967
Writing parameter :
{"Timeout Open Trunklid 1 (open roof)": "0", "Timeout Close Trunklid 2 (open roof)": "0", "Timeout Unlock Trunklid 1 (open roof)": "0", "Timeout Close Trunklid 1 (open roof)": "56", "Timeout Unlock Trunklid 2 (open roof)": "0", "Timeout Open Roof 1 (open roof)": "0", "Timeout Open Roof 2 (open roof)": "0"}
@ 14:06:10.092
Screen : Timouts & Tolerances Request : ReadDataByLocalIdentifier: times latches
{"Tolerance Right Latch": "0", "Tolerance Left Latch": "0"}
@ 14:06:10.093
Screen : Timouts & Tolerances Request : ReadDataByLocalIdentifier: general system infos
{"Status EEPROM": "Writing"}
@ 14:06:10.094
Screen : Timouts & Tolerances Request : ReadDataByLocalIdentifier: tolerance values 2
{"Tolerance Start Hydraulic (close roof)": "0", "Tolerance Close Trunklid (close roof)": "0", "Tolerance Close Roof (close roof)": "0", "Tolerance Open Trunklid (close roof)": "0"}
@ 14:06:10.095
Screen : Timouts & Tolerances Request : ReadDataByLocalIdentifier: tolerance values 1
{"Tolerance Open Trunklid (open roof)": "0", "Tolerance Open Roof (open roof)": "0", "Tolerance Start Hydraulic (open roof)": "0", "Tolerance Close Trunklid (open roof)": "0"}
@ 14:06:10.097
Screen : Timouts & Tolerances Request : ReadDataByLocalIdentifier: timeout values 1
{"Timeout Open Trunklid 1 (open roof)": "0", "Timeout Close Trunklid 2 (open roof)": "0", "Timeout Unlock Trunklid 1 (open roof)": "0", "Timeout Close Trunklid 1 (open roof)": "0", "Timeout Unlock Trunklid 2 (open roof)": "0", "Timeout Open Roof 1 (open roof)": "0", "Timeout Open Roof 2 (open roof)": "0"}
@ 14:06:10.099
Screen : Timouts & Tolerances Request : ReadDataByLocalIdentifier: timeout values 2
{"Timeout Unlock Trunklid 1 (close roof)": "0", "Timeout Close Trunklid 1 (close roof)": "0", "Timeout Unlock Trunklid 2 (close roof)": "0", "Timeout Close Trunklid 2 (close roof)": "0", "Timeout Open Trunklid 1 (close roof)": "0", "Timeout Close Roof 1 (close roof)": "0", "Timeout Close Roof 2 (close roof)": "0"}
I have do changes but:
Claster - changed 2 values ( don't know name of param, will write down tomorrow )
RadNav - changed 1 value, hard reset
RaCam - using XZG_RaCam_V1_2_20160805T115937.xml
ABS/ESP - changing to Activated -> I see on dashboard "Check ESP"
Except
AEBS37_VectorFeedBack.P_tng_m_DistVectorFeedBack_1_2, AEBS37_VectorFeedBack.P_tng_m_DistVectorFeedBack_1_1 and mph values
all was changed but doesnt work.
Is it possible that system knows I don't have distance button on the steering wheel and that's why it is blocking activation ?
Try to use RaCam_V4_20170703T152858.xml but I not sure that these parameters are available here. If not then you may try to write own script, make own screen in ddt4all or use a pyren it has synthetic screens for every command.
About distance button not sure that ECU may know. These buttons usually made as a resistive set and only two wires toward ECU but I may be wrong
In the cluster you need to change only one parameter CCSLACCServiceCustomer_CF from "1" Text="CC/SL" to "2" Text="ACC/SL"
I have made custom screens and do the whole process one more time:
ddt4all using connected mode
choosing XZG - KOLEOS 2
RaCAM v4
I have created custom screen also for MPH values and changed ( forget to make a photo ). Just in MPH there is not defined last one variable - DistanceControllerMaxSpeedCommand
Those values are different from you suggested - I'm little bit worried to mess with that - do you think it is related to ACC not operating ?
RadNav 2.x
Cluster
I have found 2 values in cluster mentioning ACC ( the first one should be not set to ACC ? )
I'm thinking about the text - Deactivated by diag - like in this ABS ecu it should be auto activated if in other ECUs is all ok or some diagnostic returns that ACC can be activated. Maybe can I use function in ddt4all - DTC reset to reset errors if any without any harm ?
Did you reload the TDB after changing "1" Text="CC/SL" to "2" Text="ACC/SL" ?
I tried to activate ACC on my Scenic IV. But without success. It seems that missing some hardware part( different ABS sensors). Look onto previews threads.
Yes I have reloaded TDB after change and there was ACC/SL
I have part number of RaCam and I'll try get info if it is the same as in the version with ACC enabled.
@Banana009 - can be so, courious if there is some possibility to get info from ECUs why ABS ECU is indicating that ACC was deactivated by diag. - which diag, reason ,etc.
@michalzahor your ddt4all version seems to be the last one (5.20 with ecu dec2018) and on it I've had a lot of problem to go inside the ABS ecu!! I've disinstalled that version and installad again the "older 5.02 and now is working fine
I'm running V1.02 - latest version for WinXP ( from 2017 ) and ECU dec2018.
I've turned now off all ACC related, I'll be visiting service :-)
But I was able to enable other small tweaks - cornering off, DL inhibit by flasher, ANC, ...
Will try go get info about my RaCam version and after service visit will try ACC again
@shrlnm - you were right with TDB ( cluster ) that only one item should be changed ( I though that I have enabled 2 items but first one was enabled from the factory ). When I now was changing back from ACC to CC mode I have disabled also ACC in the first screen of cluster and I was getting "STOP" warning and message "Program Err". When I enabled back ACC on the cluster frst screen then error is gone and CC is working properly.
We need to explore BVMEXTRACTION database for understanding witch option may be activated on which firmware. You have still very rare option AEBS05. It appeared in second half of 2018 and not too many koleoses have it. The number of koleoses with AEBS05 and RVDIST (it is ACC option) is even more rare.
Will try. This Koleos has AEBS with pedestrian recognition. As I know, koleos before doesn’t have this functionality.
On 6 Jan 2019, at 17:07, shrlnm notifications@github.com wrote:
We need to explore BVMEXTRACTION database for understanding witch option may be activated on which firmware. You have still very rare option AEBS05. It appeared in second half of 2018 and not too many koleoses have it. The number of koleoses with AEBS05 and RVDIST (it is ACC option) is even more rare.
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/cedricp/ddt4all/issues/126#issuecomment-451753218, or mute the thread https://github.com/notifications/unsubscribe-auth/AEwYdCfyEooEl-8SbdhpYfoPQbHxSah9ks5vAh89gaJpZM4ZnLTw.
@shrlnm seems like BVMEXTRACTION is not part of ddt2000 database I have downloaded.
I have database from
BVMEXTRACTION is a part of clip database, it contains all VINs and ecu configurations
On my new Scenic IV is Racam, pedestrian protection, also LKA , but ACC can not be activated. The first step is to find out if a hardware part is needed . This is possible after a discussion with an authorized service center. Nobody can activate the ACC even after replacing the steering wheel with the button.
Waiting for some info and will try end of the week
What information are you waiting for?
part number of my racam if is the same as for koleos with activated acc from factory
Michal Zahor mzahor@dtech.sk
On 8 Jan 2019, at 17:42, Banana009 notifications@github.com wrote:
What information are you waiting for?
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.
Michale, for Scenic IV are 2 types of RaCam. Part numbers 284629358R and 284628548R. You can see on allegro: https://allegro.pl/oferta/renault-grand-scenic-iv-kamera-radar-legalny-z-vat-7395071700 https://allegro.pl/oferta/renault-scenic-iv-2017-kamera-radar-sensor-szyba-7658649540 Unfortunately, I don't know if it is the reason why ACC can not be activated. Interesting is that the software 5.2.2 is the same.
I suppose that for Koleos it is the same. But the RaCam has different software SW 2.1.0 I found out only part number 284625670R https://allegro.pl/renault-koleos-ii-2017-radar-kamera-284625670r-i7662479894.html
I have RaCam SparePart: 284625816R, SW 2.2.1 I 2018 they added Pedestrian recognition
Seems that I'm not able to get further - guy in the authorised service said that it is not possible to activate because there is missing radar in the front bumper etc. As I know, new version doesn't use radar in bumper as RaCam is able to do the work. Didn't wanted to ask too much and I can not argue with more data from obd as car is under warranty and .... Maybe just it needs time to let somebody discover the way.
I added a little tool to send requests that are not on screens :
Just next to the hex icon. Not fully tested, though
@cedricp - is there something related to acc :-) ? I've tried PyRen to compare screens and parameters. Found that ABS is different and I haven't find ACC related settings for ABS in PyRen.
Also there was memorised error in ABS related to ACC - I've cleared error but ACC not working.
Also on one RaCam screen in ddt4all I saw live data while driving about ACC (parameter name contains ACC) - distance, speed, ... so I believe that RaCam is capable of ACC. The only question is what is blocking the functionality.
@michalzahor you have chosen wrong xml in pyren when run ddt for a first time, used old version (actual is 9n) or were not connected to car. Now you need to remove "cache" folder and scan ECUs again.
When you first run ddt from pyren, the screen should be like this
Starting DDT process
Getting ID from 2180
IdRsp: 61 80 38 35 37 30 52 09 30 33 37 38 36 32 32 52 43 66 1E 30 00 13 02 01 00 88 00
Address:"01" DiagVersion:"9" Supplier:"037" Soft:"4366" Version:"1E30"
Loading eculist
01 # ABS
########################################
0 - ESC___1540_HFE_XZG_Version_2.2_20170620T142139.xml
15213 - ESC___1540_HFE_XZG_Version_1.9_20170620T141226.xml
14034 - ESC___1540_HFE_XZG_Version_2.5_20180502T151847.xml
########################################
You may enter the file name by yourself or left empty to exit
File name [ESC___1540_HFE_XZG_Version_2.2_20170620T142139.xml]:
This is example from my koleos and pyren found exact match with version 2.2
@michalzahor I have checked part numbers of RaCam for Koleos with ACC (RVDIST option) Your koleos VIN:VF1RZG................. racam SW part number is 284A61717R. The same PN have all koleos with options AEBS05 and RVDIST
Try to monitor system frames on a CAN, are there something related to racam data?
My VIN was in log file ? [ deleted it just for the case - car is still under warranty ].
Hm will try that tomorrow.
I have noted today that when ACC is activated in RaCam, then I'm not able to use CC ( ACC of course not too )
Hi,
I'm unable to change ACC to active in ABS / ESP . [ using WinXP latest DDT4ALL version ]
Seems like data are writtencorrectly but the value is still "deactivated".
Is the error in the screenshot related to failed write operation ?