Editing MHD Logging

MHD's logger has a useful feature which allows you to add custom logging parameters, which we explain below.

You use this feature, you need the a2l file for your DME (see [[Useful_resources_for_getting_started#A2L_file_for_your_car|Resources for getting started]]).

The basic process is as follows
* Create a <prg>_UserChannels.xml file where <prg> is the value of ''Current PRG (hex)'' as shown by MHD flasher when you list the DME software versions.
* The file follows a format as follows

{{Codesample |name=ingress.yaml |lang=yaml |scheme=dark |line=1 |highlight=5,8 |code=
---
apiVersion: networking.k8s.io/v1beta1
kind: Ingress
metadata:
  name: foo-redirect
  namespace: tool-foo
  labels:
    name: foo-redirect
  annotations:
    kubernetes.io/ingress.class: nginx
}}

<code>

<?xml version="1.0" standalone="yes"?>
<ActualValues>
<ActualValue 
  ReqBlock="$measurement-hex-address-according-to-a2l" 
  Size="$size-in-bytes" 
  DataA="$x-coefficient" 
  DataB="$constant" 
  Prefix="$memory-segment-leading-digits-unused" 
  Units="$units" 
  RoundingDigits="$decimal-places" 
  signed="$1-if-signed-otherwise-skip-this-attribute">
</ActualValues>

</code>

Here's an example for Dzwt_pf1, the temperature correction component of an overall timing correction:

<ActualValue ReqBlock="51801f14" Size="2" DataA="0.1" DataB="0.0" Prefix="51" Units="°" RoundingDigits="1" signed="1">
<Text xml:lang="en">Dzwt_pf1</Text>
</ActualValue>


This is so because the a2l file declares:

/begin MEASUREMENT

Dzwt_pf1
"Temperaturkorrektur ZW-Klopfgrenze Pfad1"
SWORD
juwcFuc_Dtmczic_mCgfamd_q__aa0o
1
100.
-3276.8
3276.7
FORMAT "%6.1"
ECU_ADDRESS 0x51801F14


/end MEASUREMENT

and

/begin COMPU_METHOD

juwcFuc_Dtmczic_mCgfamd_q__aa0o
"juwcFuc_Dtmczic_mCgfamd_q__aa0o"
RAT_FUNC
"%6.3"
"°"

COEFFS 0. 10. 0. 0. 0. 1.

/end COMPU_METHOD