Title: CREATING XDF (DAMOS) Post by: phila_dot on August 23, 2010, 10:33:07 PM I am missing something. I have gone through every bit of information that I can find and spent a small amount of time playing around with Tunerpro with no progress. How do I create an XDF (XDF and DAMOS are the same thing right?) for my 2001 S4 L box? The only useful XDF that I can come across is for an M box. I have a stock L box bin and a GIAC X L box bin that I want to work with. If I open them in Tunerpro and attempt to create an XDF the only function that I can really manipulate is the HEX editor. If I use the difference tool to compare the M box to the L box all I get is the values and M box associations correct? How can I correlate the L box values to the M box definition? If this rambling makes sense to anyone can you please point me in the right direction. Once I get an idea of what I need to do I should be able to run with it. Thank you.
Title: Re: CREATING XDF (DAMOS) Post by: RaraK on August 24, 2010, 09:25:17 AM the maps are located in different spots on all the different ecu's, so you must find where these different addresses are and modify the xdf.
i would use the mbox xdf as a base to modify off of. Good luck. Title: Re: CREATING XDF (DAMOS) Post by: Rick on August 27, 2010, 05:07:22 AM You have to find the maps, usually by dissasembling. This is the hardest part of all sadly.
Rick. Title: Re: CREATING XDF (DAMOS) Post by: audi_skydiver on August 28, 2010, 09:19:47 PM How do you go about doing the disassembling??? I need to code out my EGT's on my AA box and don't know how to see where they are. I am using tunerpro and have already downloaded the .bin file from my car.
josh EDIT here is my bin file if anyone wants to play with it... this is also a GIAC-X tuned ECU. Title: Re: CREATING XDF (DAMOS) Post by: phila_dot on August 31, 2010, 11:24:43 PM Let me start by explaining my current method. I have started two projects in WinOLS, one for the L box and one for the M box. This allows me to use the potential maps as a starting point. I am identifying the M box potential maps by comparing it to the xdf that I have. Then finding a matching L box potential map. Then I am editing my M box xdf in Tunerpro to the L box addresses that I have found in WinOLS. This is the best method that I have come up with. It seems that all of these programs have a lot of weaknesses so the only way to accomplish anything is to use the strengths of each one. Does this seem logical at all to anyone? Is there a simpler path? One problem that I have is that some of the M box potential maps are not defined in my xdf and some of the addresses defined in the xdf are not resident as a potential map. Any advice greatly appreciated. I also downloaded idapro and only messed with it briefly. I have not found a way to add that piece to the puzzle yet. Also, where do the motronic abbreviations come into play? I see them referenced all the time, but I haven't come across anything like this in the code. Where is all of the documentation?
Title: Re: CREATING XDF (DAMOS) Post by: TWiST on September 01, 2010, 01:00:46 PM I posted all the info for removing the EGT's on an AA box ecu in another thread. With all the memory offsets and what not.
Title: Re: CREATING XDF (DAMOS) Post by: EuroXs4 on September 01, 2010, 04:59:46 PM Im currently working on just a basic txt file that will have the mbox ecu locations of maps and location of the same maps on a Abox ecu.Winols currently found 40 potential maps.I will post file when im finished going through all 40.I only have addresses as I am not using tunerpro.Ok I finished the txt file.Basically its only for refernce.A baisc text file written in notepad that give address in mbox and the corresponding addresses in a abox ecu.IF anyone can tell me which maps are what.That would be even better.The file is finished If you want a copy please email me.Also to confirm that the abox has 40 potential maps and the mbox has 42.
Title: Re: CREATING XDF (DAMOS) Post by: RaraK on September 03, 2010, 08:32:21 AM I thought i already modded your file for you at some point no?
anyways, i have a AA box def file started. and i thought i sent it to you? or less someone else had the same request at some point. Id have to dig up those mods. And the method i use for finding maps in Winols since tunerpro is garbage to me. I load up a stock euro .bin with the a2l file for it, I then search through code comparing and finding maps. pretty easy for the larger maps, single values can be a pain at times. and if you cannot find the maps, then off to dissas. the file :) ive only had trouble with maybe 10-15% of my def file so far. Ive only got maybe 40-50 maps found though, but they are the important ones you need to tune. in all honesty, its easier to use the euro file with the a2l if you dont want to find the maps. I loaded it up and it works fine, its all in german, but you will quickly learn german and the terms as they are re-used tons in the file. And having some bosch documentation on me7 helps ;) Title: Re: CREATING XDF (DAMOS) Post by: Tony@NefMoto on September 03, 2010, 01:51:20 PM Here is how I go about finding maps in different versions of the S4.
First I start with the known maps in my 2001.5 MBox ECU. For each map I am trying to find in a different ECU, I look for some unique pattern in the map data. I usually look for 4 to 16 bytes. Then I do a search for that same byte pattern in the other ECU file I am looking at. After finding what looks like a match in the byte sequences, try loading the possible map up in a map viewer and compare the possible map in the new ECU to the known map in the old ECU. Really the only way to find maps is to disassemble the code in the ECU. Most people don't want to do this, and the ones that do discovered it takes a VERY VERY long time to learn enough to be able to accomplish anything. Title: Re: CREATING XDF (DAMOS) Post by: EuroXs4 on September 04, 2010, 06:53:57 AM Yeah I would like to compare the maps and see whats different.But there is not descriptions or information on what maps are at what addresses and what function they perform.I have no problem going through the maps problem is comparing maps,not knowing what each map does.Anyone have a list???Or at least a few??I believe to successfully tune only about 8-10maps need to be adjusted if i remember correctly.
Title: Re: CREATING XDF (DAMOS) Post by: Tony@NefMoto on September 05, 2010, 06:45:26 PM Here is what Nyet has publicly posted on his website: http://s4wiki.com/wiki/Tuning
Otherwise, you need to get a copy of the ME7 documentation. Title: Re: CREATING XDF (DAMOS) Post by: spen on September 22, 2010, 09:02:32 AM What is it you are looking for? A list of L box data offsets?
Title: Re: CREATING XDF (DAMOS) Post by: phila_dot on September 22, 2010, 09:16:24 PM I am looking to define and understand as much of the L box as I can. Right now I am modifying an M box xdf with the corresponding L box addresses that I am finding in WinOls. With this method I am limited to what is defined in the M box xdf. I am still trying to figure out the disassembly at the same time. Any way you could help with either would be greatly appreciated.
Title: Re: CREATING XDF (DAMOS) Post by: spen on September 23, 2010, 05:48:48 AM Right, here it is:
Format: Description (Bosch Name), bytes of axes before data starts, internal address of object These addresses are where the program starts reading data and there may be additional axis data in front of the actual map. My code looks at it from the ME7 binary perspective, and if ME7 reads the axis at the same time so do I. You should be able to see in winols, axis often have a length followed by the axis. Axes and maps can be 8 or 16 bits wide, if the axis is 16bit then so are the lengths. To change the internal address to a file offset just remove the most significant 8 bits, ie the 0x8 at the start. When there are axis data points that my code has recognised, just add them to the offset to skip over the axis. *NB* The axis information is a new feature and as such it only deals with a handful of situations - so there are some zeros when there should be additional data. Above all else please remember that this is machine generated data. I've not checked it, not even looked at it. Please look in winols and verify each one before you rely upon it. The program is usually right, but if it's wrong any constructive feedback would be appreciated. SLOGIN (preceed login with a 0),0,0x812122 KLOGIN (preceed login with a 0),0,0x812120 Table:Normalized mass flow over DK (KFMSNWDK),48,0x811198 Correction factor for combustion chamber pressure at NWS active (KFPBRKNW),44,0x81b976 Correction factor for combustion chamber pressure (KFPBRK),44,0x81b882 Table: target load KFMIRL,60,0x811950 Inverse pedal map for cruise control (KFWPFGR),60,0x81b510 Cold start enrichment factor (FKSTT_1_A) NON STANDARD ACCESS, MANUAL DECODE REQUIRED,0,0x811d6c Delta pressure for overboost protection diagnosis (KFDLULS),18,0x819781 Lambda - driver desired LAMBDA,0,0x81c05c MAF_correction_table_KFKHFM,30,0x814edb Pedal angle threshhold for compressor shutoff,0,0x816171 delta lambda for component protection DLBTS,0,0x81c13f Desired idle engine speed while cat heating with drive engaged KFNFSKHM,0,0x81c330 Characteristic curve for continuous limit value control (fr) (FQTEFR),0,0x81e891 Injection correction during RLFS (FRLFSDP),0,0x81bfb8 Maximum specified load IAT correction factor map (KFTARX),0,0x81d820 Maximum engine speed on speed signal error detection (automatic transmission)? (NMAXDVG),0,0x817036 Weighting factor for slow boost pressure intervention on rlmax via KR (KFFWLLDE),0,0x81d7a0 Factor for rapid LDR intervention (reduction) (KFFSLDE),0,0x81d720 Factor for slow LDR intervention on rlmax via KR (KFFLLDE),0,0x81d6a0 Factor for boost pressure intervention through KR (KFFLDEO),0,0x81d620 LDR-control parameter Q1 in stationary operation (integration coefficient) (LDRQ1ST),0,0x81d5e8 LDR-control parameter Q1 in dynamic operation (integration coefficient) (LDRQ1DY),0,0x81d5c8 LDR-control parameter Q0 (LDRQ0DY),0,0x81d5a6 LDR-control parameter Q2 (KFLDRQ2),0,0x81d53c Map for linearization of boost pressure N75? (KFLDRL),0,0x81d3fc LDR I-Regulator limit (KFLDIMX),0,0x81d2aa Enrichment on ignition retard (KFLAMKRL),0,0x818e12 RPM Axis for Timing (words),0,0x81009a Load Axis for Timing (words),0,0x8142b4 Optimal ignition angle (KFZWOP),0,0x815603 Axis: Ignition Timing(load),0,0x812f6e Optimal ignition angle variant2 (KFZWOP2),0,0x8156b3 Maximum engine speed for throttle body motor backup operation (NMXDAEF),0,0x815765 Allowable torque on afterstart extension (KFMIZUNS),0,0x8157ba Allowable indicated torque to torque limit before filter (KFMIZUFIL),0,0x81577a Map with permanent latest possible ignition angle (KFZWMS),0,0x815d8d Ignition angle map (KFZW),0,0x815f0f Ignition angle map (KFZW2),0,0x815e4f Axis: RPM (PID),0,0x810078 Axis: RPM (misfire detection),0,0x8100bc Maximum specified load IAT correction factor map under continuous knock (KFTARXZK),0,0x81d8a0 AXIS: Unknown, maybe IAT,0,0x814357 Maximum specified load during continuous knock (LDRXNZK),0,0x81d962 Maximum specified load (LDRXN_1_A),0,0x81d920 Load threshold for surge recognition for misfire recognition attenuation (RLSALUN),0,0x81469a Upper load curve for DKAT active _RLDKTSO_0_A,0,0x814bf8 *Rough running deviation (dluts) reference value (KFDLUR),0,0x814594 *Rough running deviation (dluts) reference value 2 (KFDLUR2),0,0x814614 *Rough running deviation (dluts) reference value 1 (KFDLUR1),0,0x8145d4 Misfire detection: RPM deviation fade-out threshold (NGALU),0,0x8101e8 map_Optimal_torque_under_monitoring_KFMI_UM,0,0x814098 Axis:for_KFMI_UM+KFZW_UM,0,0x81407d map_Optimal_ignition_angle_under_monitoring_KFZW_UM,0,0x8140d8 map_Offset_tolerance_depending_on_allowed_torque_KFMDZOF_UM,0,0x814129 Map for allowable torque from pedal position in the functions monitoring (KFMPED_UM),0,0x814169 Map for allowable torque from pedal position on cold motor (KFMPNS_UM),0,0x8141a9 MAF linearization (MLHFM),0,0x810d74 Table: Repeated cold start factor of start count reduction KFWKSTAB,0,0x811d92 Table: Delta ignition angle with tip engaged DZWTIN,0,0x811f38 Table: Desired pressure ratio DK dynamic KFVPDKSD,0,0x8121b2 Table: Desired pressure ratio stationary KFVPDKSE,0,0x8122d2 Axis: RPM for KFVPDKSD and KFVPDKSE,0,0x8100d8 Table: Starting torque (KFMDST_0_A),0,0x81251c Table: Relative torque request from pedal KFPED_0_A,0,0x812aba Table: Optimal engine torque map (KFMIOP),0,0x812e0e Table: Lambda linearization; sensor behind cat (LALIUSH),0,0x81321c Table: Minimum ignition angle KFZWMN,0,0x813436 Table: Minimum ignition angle for start and warm up KFZWMNST,0,0x81349c Axis: RPM(knock regulation),0,0x81825f Axis: Load (unknown use),0,0x81828a Axis: Load(EGT enrich),0,0x8182af EMBP correction of the secondary air mass (KFFMSML_0_A),0,0x818358 Weight of ftbr dependent on IAT (FWFTBRTA),0,0x818801 Weighting factor Tans/Tmot for combustion temperature model KFFWTBR,0,0x81881e Map for variable cam timing KFNW,0,0x8188f4 Map for variable cam timing during warmup KFNWWL,0,0x81896a Lambda map at partial load (KFLF),0,0x818a23 Injection cutoff angle (KFWEE),0,0x818b55 Injection cutoff angle (cold) (KFWEEK),0,0x818b95 Factor delta desired lambda for component protection (KFFDLBTS_0_A),0,0x818fac Desired Lambda for component protection (KFLBTS_0_A),0,0x81906c Delta angle knock regulation offset for average retard (DWKRMSN),0,0x819473 Knock regulation delta - angle safety (KRDWSN),0,0x8194b9 Ignition retard per knock event (KRFKLN),0,0x8194c9 Maximum ignition retard (KRMXN),0,0x8194d9 TV correction due to altitude effect on ambient pressure (KFLDIOPU),0,0x819597 Map for weighting factor of reference boost pressure as a function of IAT (KFWPLGTA),0,0x8195d7 LDR I-Regulator limit correction as a function of IAT (LDIATA),0,0x81961c Delta load (rl) under overboost condition (KFLDRXO),0,0x819642 Down regulation interval for LDR overboost (TABLDOBN),0,0x819670 Time for LDR overboost active (TLDOBAN),0,0x819678 Off time for overboost (TLDOBN),0,0x819680 LDR altitude limitation (maximum pressure ratio) (KFLDHBN),0,0x8196a4 Maximum load at E_ldo LDR (overboost error) (LDORXN),0,0x8196e4 LDR pressure limit at too high a temperature engine (LDPBN),0,0x8196ec rl threshold for slow LDR-intervention (adaptation) (RLKRLDA),0,0x8196f4 Map for LDR application without Md-coordination (KFLDRAPP),0,0x8196fc Maximum permissible pressure ratio DK for ldra diagnosis? (KFVPDKLD),0,0x8197d3 Motor temperature dependent delay time for drive in (R) (TVFSREM),0,0x819983 Characteristic curve for tmot; upper rL control limit for controller before Kat (RLLRTMO),0,0x819dfe closing time (from RPM; V) (KFSZT),0,0x81a282 closing time (from load; RPM) (KFTSRL),0,0x81a2d4 Threshold for B_minflr diagnosis HFM/HLM (KFMLDMN),0,0x81b71e Threshold for B_maxflr diagnosis HFM/HLM (KFMLDMX),0,0x81b7c2 Factor for maximum pressure ratio with auxilliary load signal (FPVMXN2),0,0x81b868 Internal exhaust partial pressure dependent on cam adjustment when sumode=0 (KFPRG),0,0x81ba6a Conversion constant for ps->rl dependent on cam adjustment when sumode=0 (KFURL),0,0x81bb06 Desired idle speed when in gear (NFSM),0,0x8198e6 Weighting map for cold start factor (KFWKSTT),0,0x815168 Warm up enrichment factor (KFFWL_0_A),0,0x818c7b Warm up enrichment factor (KFFWL_1_A),0,0x818d0b Default throttle plate angle from charge signal (KFWDKPP),0,0x814c4e Maximum throttle plate angle for plausibility with load signal (WDKPMXN),0,0x814d13 Min delta pressure before throttle plate for wastegate diagnosis (DPVDKDWG),0,0x816f9e Axis: for Min delta pressure before throttle plate for wastegate diagnosis (DPVDKDWG),0,0x816f95 Max delta plsol for wastegate diagnosis (DPLSDWG),0,0x816f84 Axis: for Max delta plsol for wastegate diagnosis (DPLSDWG),0,0x816f7b Delta timing during warmup,0,0x816018 Delta timing during warmup,0,0x816018 Correction factor for fuel supply system (FKKVS),0,0x81bd42 Desired idle speed (NLLM),0,0x8198e6 desired throttle plate angle (KFWDKMSN),0,0x8117f2 Afterstart enrich (FNSA_0_A),0,0x8144da Table:Hot start enrichment factor (KFHSTT),0,0x818bb2 Delta timing during warmup,0,0x816018 Max_indicated_torque_check,0,0x81f242 Max_indicated_torque_check,0,0x81f242 Max_indicated_engine_torque_MDIMX,0,0x815764 MAP_sensor_gradient,0,0x8116d4 MAP_sensor_offset,0,0x8116d6 Conversion_constant_from_MAF_to_relative_charge_KUMSRL,0,0x814fc4 MAF_offset_MLOFS,0,0x811176 Normalized_fuel_consumption_per_cylinder_for_DIS_KVNPZ,0,0x8143ff Min_RPM_for_misfire_recognition_fade_out_DMDDLU,0,0x814694 Min_RPM_for_acc_pedal_value_lockout_on_brake_operation_NWPMBBR,0,0x814c2d pedal_lockout_on_brakes_activation_speed_VWPMBBR,0,0x814c46 Delay_time_for_acc_pedal_value_lockout_on_brake_operation_TWPMBBR,0,0x814c37 Pedal_volts_for_full_throttle_UPWGVG,0,0x814c45 Speed_before_rpm_limit_raised,0,0x815773 Water_temp_before_rpm_limit_raised_TMOTNMX,0,0x812f9c Max_duration_of_raised_rpm_limit_TNMXH,0,0x812fa0 Main_RPM_Limit_NMAX,0,0x812f92 Time_under_rpm_limit_before_activating_raised_rpm_limit_ITNMXH,0,0x812f90 Max_rate_rpm_change_DNMAX,0,0x812f88 Max_RPM_with_doubled_ignition_detected_NMAXDZ,0,0x812f94 delta_for_rpm_limit_for_double_ignition_DNMAXDZ,0,0x812f8a Max_rpm_on_doubled_ignition_detection_NMAXDZ,0,0x812f94 Max_rpm_on_safety_fuel_cutoff_SKA_NMXDKPU,0,0x812f9a Max_rpm_on_rpm_gauge_fail_NMAXNL,0,0x812f96 rpm_deviation_above_limit_for_all_cyl_cut_DNMAXH,0,0x812f8c Dwell_time_in_NMAX_before_change_over_in_calibration_TNMAXP,0,0x812f9e Duration_for_active_alternative_calibration_of_maximum_rpm_ITNMAXP,0,0x812f8e Raised_rpm_limit_NMAXOG,0,0x81f4f2 Codeword_No_ROM_check_reset_CW_NOROMCHKRESET,0,0x815c03 Min_rpm_for_misfire_recognition_fade_out_NMIALU,0,0x814697 Load_threshold_for_surge_recognition_for_misfire_recognition_attenuation_during_idle_RLSALULL,0,0x814699 Min_idle_air_mass_adaption_for_exhaust_gas_MSALLMN,0,0x814fc7 CW_Lambda_coordination_during_cat_warmup_CWLAMKH,0,0x8150ab Speed_before_AC_control_active_VKO,0,0x81616e engine_temp_from_cluster_for_AC_cutoff_TKOMBKOA,0,0x816156 engine_temp_from_cluster_for_AC_activation_TKOMBKOE,0,0x816157 temp_limit_before_AC_cutoff_TMKOAO,0,0x816169 temp_limit_before_AC_activated_TMKOAU,0,0x81616a RPM_exceeded_threshold_for_cut_NMAXF,0,0x810ae8 Temp_during_start_for_requirements_adaption_TMSTMAD,0,0x81616b max_speed_before_AC_cutoff_VKOAO,0,0x81616f IAT_threshold_for_AC_cutoff_TANSKOB,0,0x816124 Speed_threshhold_for_AC_control_during_acceleration_VKOB,0,0x816170 SLOGIN,0,0x812122 GRAONLOGIN,0,0x81211e ADRLOGIN,0,0x81211a GRAOFLOGIN,0,0x81211c Default coding for varient coding,0,0x812124 Dwell_time_for_dynamic_BPV_N249_control_THLDUVD,0,0x8121b0 Down_control_time_constant_for_fmvp_w_factor_TDPDK,0,0x8123f2 Ramp_slope_during_devation_regulation_of_ASR_torque_RAMPASR,0,0x8101c2 Min_voltage_for_diagnosis_MAP_sensor_limp_UADPLMN,0,0x8187c4 Max_voltage_for_diagnosis_MAP_sensor_limp_UADPLMX,0,0x8187c5 Min_voltage_for_diagnosis_MAP_sensor_UADPUMN,0,0x8187c6 Max_voltage_for_diagnosis_MAP_sensor_UADPUMX,0,0x8187c7 Debounce_time_for_end_of_cat_heater_cycles_per_min_during_idle_TKHLLAB,0,0x819240 Knock_regulation_Load_hysteresis_KRALH,0,0x8194b3 Knock_regulation_RPM_hysteresis_KRANH,0,0x8194b8 Control_deviation_threshold_for_LDR_positive_deviation_diagnosis_EDLDRP,0,0x819780 Regulation_deviation_threshold_for_starting_LDR_overboost_active_timer_ELDOB,0,0x819780 Lower_regulation_deviation_threshold_for_negative_adjustment_LDEIAU,0,0x81961a Upper_regulation_deviation_threshold_for_negative_adjustment_LDEIAO,0,0x819617 Regulation_deviation_threshold_for_positive_adaption_I_Regulation_LDEIAP,0,0x819618 Regulation_deviation_threshold_for_rapid_positive_set_point_tracing_LDEIAPS,0,0x819619 Hysteresis_for_LDR_I_Adaption_curve_LDHIA,0,0x81961b Changeover_deviation_threshold_for_dynamic_LDR_UMDYLDR,0,0x819637 Minimum_charge_LDR_for_DIA_LDR_maximum_permitted_pressure_SDLDRL,0,0x81982a Time_threshold_for_Dia_LDR_control_deviation_TDLDRA,0,0x81982b Time_threshold_for_Dia_LDR_control_deviation_B_mxldra_TDLDRA2,0,0x81982c Delay_time_for_Dia_LDR_control_deviation_detection_cycle_flag_TLDRA,0,0x81982d Overboost_cutoff_delay_step_1_TULV1,0,0x81982e Delay_time_for_overboost_failure_recovery_TULV3,0,0x81982f Constant_for_fuel_consumption_display_KVB,0,0x81a348 Max_air_mass_b4_shutoff_secondary_air_injection_MLSLMX,0,0x81a4de min_airmass_for_diagnosis_MLWDSLMN,0,0x81a548 Airmass_threshold_for_dynamic_testing_behind_cat_MLLASH,0,0x81b392 Delta_pressure_value_for_signal_comparison_of_pressure_sensor_with_ambient_pressure_DPDSVLU,0,0x81bba4 max_airflow_for_load_calculation_MLMAX_SAE_J1979,0,0x81bc10 EGT_threshold_for_component_protection_TABGBTS,0,0x81c14a target_EGT_B1_TABGSS,0,0x81c1ac target_EGT_B2_TABGSS2,0,0x81c1ae EGT_sensor_error_limit_TDATSO,0,0x81bffe DTC_CONFIG_BITS1,0,0x818d96 EGT_threshold1_950,0,0x81bffc EGT_threshold2_940,0,0x81bff8 EGT_threshold3_1035,0,0x81bffa Tank_ventilation_time_for_basic_adaption_TTEGA,0,0x81c386 Supplemental_codeword__short_strip_reqs_display_group_195_CWFA195A,0,0x81ca56 LDR_control_param_Q0_in_stationary_operation_LDRQ0S,0,0x81d5c6 Upper_duty_cycle_limit_for_LDR_TVLDMX,0,0x81d61e Conversion_of_relative_fuel_mass_rk_to_effective_injector_time_te_KRKTE,0,0x818da8 EGT_SENSOR_CHECK,0,0x8592e6(pc) Engine Temp From Cluster,0,0x380bb8 Engine Load,0,0xf989 Title: Re: CREATING XDF (DAMOS) Post by: Tony@NefMoto on September 23, 2010, 10:32:15 AM Awesome contribution spen!
Most people including myself don't take the time to post detailed information. Title: Re: CREATING XDF (DAMOS) Post by: Rick on September 23, 2010, 01:09:00 PM You can thank me for getting him to come over lol....
Spen, I take it this has the issue with orphan axis as my C box output? Rick Title: Re: CREATING XDF (DAMOS) Post by: spen on September 23, 2010, 04:02:43 PM Yeah, the axes need to be looked at independently. I've got the basics of each axis covered, but as far as building an xdf it requires a little manual thought.
I will sort out the axis problem in time, then I'll be able to recreate any ME7 object given a lead address in any ME7 binary in xdf format. Title: Re: CREATING XDF (DAMOS) Post by: phila_dot on September 23, 2010, 08:11:31 PM Thanks alot. You went above and beyond. I can't wait to get home and implement this. Your PM box is going to fill up quick.
Title: Re: CREATING XDF (DAMOS) Post by: spen on September 24, 2010, 02:27:36 AM Let me know how you get on with those offsets and winols.
Title: Re: CREATING XDF (DAMOS) Post by: phila_dot on October 01, 2010, 12:26:52 AM Spen and all concerned,
I was out of town for a few days so I have not been able to try these out until tonight. I have only just started tonight and gotten a few done. So far all of the offsets with axis information listed that I have done have been accurate. I have found that every address so far has required this axis information, however some had a zero. I greatly appreciate your contribution. Once I get through it all I intend to publish an xdf and possibly a DAMOS file as well. Have you found a solution to the zeros from the axis information feature? Great work regardless. Will this software ever be made available? Thank you. Example Actual Address Table: target load KFMIRL,60,0x811950 // 0x81198C Title: Re: CREATING XDF (DAMOS) Post by: spen on October 01, 2010, 03:39:12 AM Thanks for the feedback. I will fix the axis problem that much I do know.
The software I have written can already do an xdf export, though it still requires the axis information to be manually discovered. I have been working quite hard on pulling together a list of ram addresses, hence no axis fix. The stuff I have written is unlikely to ever be published, only the output. The primary reason is that it can be used to break immos, show the impact of changes in a tuning company's work and hence can be used to cause harm and economic damage. I'm quite happy to evolve the software as my personal hobby and share a lot of the output. Title: Re: CREATING XDF (DAMOS) Post by: Rick on October 01, 2010, 04:53:01 AM Spen has created a Motronic Jailbreak lol
Title: Re: CREATING XDF (DAMOS) Post by: phila_dot on October 01, 2010, 05:29:24 PM Any way to have the axis information dynamically add to the the offset? Is this practical?
Title: Re: CREATING XDF (DAMOS) Post by: A4Nick on October 22, 2010, 10:07:27 AM Will all of those addresses and definitions be different from my 2000 a4 1.8t? or will the definitions of the map be the same and the adress be different? Sorry if this question has been covered already im new to this but it seems like it would make since to me. For example engine load is KXDFKJ (not actual id just saying) for the s4 wouldn't it be the same for the 1.8t? thanks guys
Title: Re: CREATING XDF (DAMOS) Post by: Rick on October 22, 2010, 11:47:00 AM The definitions will be the same, but addresses will be different.
Rick Title: Re: CREATING XDF (DAMOS) Post by: A4Nick on October 22, 2010, 01:04:26 PM Ok so for example for the m box according to the definitions posted earlier
MAF linearization (MLHFM),0,0x810d74 Now on my a4 maf linearization would still be MLHFM correct? and the adress would be listed next to that as well but different numbers from above? forgive me if im not making sense i haven't extracted my bin file quite yet. Title: Re: CREATING XDF (DAMOS) Post by: Rick on October 22, 2010, 02:46:44 PM yes, thats correct
Title: Re: CREATING XDF (DAMOS) Post by: A4Nick on October 22, 2010, 05:38:09 PM Alright awesome, thanks for the help and hopefully ill be contributing back sometime soon ;D
|