Realdash connection KMS MD35 & KMS XML description file

r6b6c6p · December 19, 2023, 11:16pm

Hello,

I am trying to connect twin turbo Vmax with KMS md35 and which is equipped with KMS CAN-Bluetooth dongle.
CAN-Bt dongle working with KMS own Android Dash app, but that dash is very limited and i do not like to use it.

Now i am not sure if i have issue with connection itself or maybe xml description file which is missing causing connection problems.
I have been trying with android & windows devices, both can “connect” to bluetooth device “KMS Dongle_81C3”, but from there everything is quite unclear.

F.e. Windows device says while running Realdash “Device KMS Dongle_81C3 is not available” even though Vmax is next to windows device and bluetooth says connected.
Android will not give any feedback after text “connecting…” disappears.

While going to “garage” and setting up connection, bluetooth kms dongle can be found and everything seems to be fine from connection point of view.

But after going to Dash and trying to see some online “input & values” linked to gauges etc, nothing data will update.

It might be so that i need to build XML description file, because i could not find any reference from internet or googling around, maybe someone here has some reference XML file to setup?

I found from AiM (hmi supplier) some documentation about available channels, but i do not know how to build XML description file for KMS even having this data…

Data for IOs from AiM www-pages documentation for interoperatibility with KMS.
(Funny part here is that KMS themself does not have any CAN IO-list, or atleast i do not know from whom to ask it…)

Available channels
Channels received by AiM devices connected to “KMS” “MD35” protocol are:

ID — CHANNEL NAME — FUNCTION

ECU_1 — K_RPM — RPM
ECU_2 — K_ECT — Engine coolant temperature
ECU_3 — K_IAT — Intake air temperature
ECU_4 — K_MAP — Manifold air pressure
ECU_5 — K_OILP — Oil pressure
ECU_6 — K_TPS_ENG_LOAD — Throttle position sensor engine load
ECU_7 — K_BOO_ENG_LOAD — Booster engine load
ECU_8 — K_BATT_VOLT — Battery supply
ECU_9 — K_EXH_TEMP1 — Exhaust temperature 1
ECU_10 — K_EXH_TEMP2 — Exhaust temperature 2
ECU_11 — K_CRANK — Teeth per rev of crank sensor
ECU_12 — K_GEAR — Engaged gear
ECU_13 — K_ACC_RPM_CH — Acceleration RPM channel
ECU_14 — K_INJ1_PULSE — Injector group 1 pulse width
ECU_15 — K_INJ1_CORR — Injector group 1 correction
ECU_16 — K_LAMBDA1 — Lambda sensor 1
ECU_17 — K_LAMBDA2 — Lambda sensor 2
ECU_18 — K_LAMBDA1_STAT — Lambda sensor 1 status
ECU_19 — K_LAMBDA2_STAT — Lambda sensor 2 status
ECU_20 — K_INJ2_PULSE — Injector group 2 pulse width
ECU_21 — K_INJ2_CORR — Injector group 2 correction
ECU_22 — K_IGNIT_CORR — Ignition correction %
ECU_23 — K_IGNIT_BTDC — Ignition point BTDC
ECU_24 — K_AUX2_ACT — Auxiliary 2 active
ECU_25 — K_AUX3_ACT — Auxiliary 3 active
ECU_26 — K_FUELPUMP_ACT — Fuel pump actuator
ECU_27 — K_AUX1_ACT — Auxiliary 1 active
ECU_28 — K_LAMBDA_ACT — Lambda Active
ECU_29 — K_LAMB_ERR_ACT — Lambda error active
ECU_30 — K_BOOST_ACT — Boost active
ECU_31 — K_SUPP_ERR_ACT — Battery supply error active
ECU_32 — K_POWER_SW_ACT — Power switch active
ECU_33 — K_LAUNCHSW_ACT — Launch switch active
ECU_34 — K_RPM_LIM — RPM limiter
ECU_35 — K_BOOST_LIM — Boost limiter
ECU_36 — K_FUEL_CUT_LIM — Fuel cut limiter
ECU_37 — K_IDLE_VALVE — Idle valve
ECU_38 — K_BOOST_VALVE — Boost valve position
ECU_39 — K_ATM_PRESS — Atmospheric pressure

These

Best regards
Henri

realdashdev · December 21, 2023, 10:44am

Is your adapter one of the RealDash supported adapters:

RealDash | Manuals | Supported CAN/LIN Adapters

If not, it is possible to implement support if its protocol info is available.

r6b6c6p · December 22, 2023, 7:34pm

Hello,
Adapter could not be found from RealDash supported adapters.

Anyhow, adapter is from Van Kronenburg KMS pages:

Basically what it does converts CAN to Bluetooth.

I contacted to KMS and luckily i was able to get *.DBC file from them.
Seems i can not add file here because of supported files, and i could not convert file to xml.

So instead of trying to convert it, i open it with notepad++ and copy & paste it here, i hope it is ok…

File md35.dbc begin ****

VERSION “HIPBNYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYY/4/%%%/4/'%**4YYY///”

NS_ :
NS_DESC_
CM_
BA_DEF_
BA_
VAL_
CAT_DEF_
CAT_
FILTER
BA_DEF_DEF_
EV_DATA_
ENVVAR_DATA_
SGTYPE_
SGTYPE_VAL_
BA_DEF_SGTYPE_
BA_SGTYPE_
SIG_TYPE_REF_
VAL_TABLE_
SIG_GROUP_
SIG_VALTYPE_
SIGTYPE_VALTYPE_

BS_:

BU_:

BO_ 40 md35_1: 8 Vector__XXX
SG_ OilPressure : 55|16@0+ (1,0) [0|1250] “KPA” Vector__XXX
SG_ RPM : 7|16@0+ (10,0) [0|20000] “Rev/Min” Vector__XXX
SG_ Coolant_Temp : 23|8@0+ (1,-20) [-20|135] “Deg C” Vector__XXX
SG_ Intake_Temp : 31|8@0+ (1,-20) [-20|135] “Deg C” Vector__XXX
SG_ Boost_Pressure : 39|16@0+ (1,0) [0|2000] “KPA” Vector__XXX

BO_ 41 md35_2: 8 Vector__XXX
SG_ CrankSignal : 47|8@0+ (1,0) [0|0] “Teeth_per/rev” Vector__XXX
SG_ EGT_2 : 39|8@0+ (5,0) [0|1250] “Deg_C” Vector__XXX
SG_ EGT_1 : 31|8@0+ (5,0) [0|1250] “Deg_C” Vector__XXX
SG_ Supply_Voltage : 23|8@0+ (0.25,8) [8|22] “Volt” Vector__XXX
SG_ Load_MAP : 15|8@0+ (0.1,0) [0|15.9] “Load_Site” Vector__XXX
SG_ Load_TPS : 7|8@0+ (0.1,0) [0|15.9] “Load_Site” Vector__XXX
SG_ Acceleration : 63|8@0+ (0.1,-10) [-10|10] "%per/rev" Vector__XXX
SG Gear : 55|8@0+ (1,0) [0|13] “Nr” Vector__XXX

BO_ 42 md35_3: 8 Vector__XXX
SG_ Lambda2_Status : 63|8@0+ (1,0) [0|0] “” Vector__XXX
SG_ Lambda1_Status : 55|8@0+ (1,0) [0|0] “” Vector__XXX
SG_ Lambda2 : 47|8@0+ (0.005,0.65) [0.65|1.455] “Lambda” Vector__XXX
SG_ Lambda1 : 39|8@0+ (0.005,0.65) [0.65|1.455] “Lambda” Vector__XXX
SG_ Correction_Inj_grp_1 : 23|16@0- (0.1,0) [-300|600] “%” Vector__XXX
SG_ Injection_grp_1 : 7|16@0+ (0.001,0) [0|65] “Ms” Vector__XXX

BO_ 43 md35_4: 8 Vector__XXX
SG_ Ignition : 55|16@0+ (-0.1,54) [0|0] “DEG adv.” Vector__XXX
SG_ Correction_Ignition : 39|16@0+ (0.1,0) [-300|600] “%” Vector__XXX
SG_ Correction_Inj_grp_2 : 23|16@0- (0.1,0) [-300|600] “%” Vector__XXX
SG_ Injection_grp_2 : 7|16@0- (0.001,0) [0|65] “Ms” Vector__XXX

BO_ 44 md35_5: 8 Vector__XXX
SG_ Aux_Out_2 : 8|1@0+ (1,0) [0|0] “” Vector__XXX
SG_ Aux_Out_3 : 9|1@0+ (1,0) [0|0] “” Vector__XXX
SG_ FuelPump : 10|1@0+ (1,0) [0|0] “” Vector__XXX
SG_ Aux_Out_1 : 11|1@0+ (1,0) [0|0] “” Vector__XXX
SG_ Lambda_Control : 12|1@0+ (1,0) [0|0] “” Vector__XXX
SG_ Lambda_Error : 13|1@0+ (1,0) [0|0] “” Vector__XXX
SG_ Boost_Controll : 14|1@0+ (1,0) [0|0] “” Vector__XXX
SG_ Sensor_Supply : 15|1@0+ (1,0) [0|0] “” Vector__XXX
SG_ Power_Shift_Input : 0|1@0+ (1,0) [0|0] “” Vector__XXX
SG_ Launch_Input : 1|1@0+ (1,0) [0|0] “” Vector__XXX
SG_ OverRun : 21|1@0+ (1,0) [0|0] “” Vector__XXX
SG_ Boost_Limit : 22|1@0+ (1,0) [0|0] “” Vector__XXX
SG_ Soft_Rpm_Limit : 23|1@0+ (1,0) [0|0] “” Vector__XXX
SG_ Idle_Pwm : 39|8@0+ (0.5,0) [0|100] “%” Vector__XXX
SG_ Boost_Pwm : 47|8@0+ (0.5,0) [0|100] “%” Vector__XXX
SG_ Baro_Pressure : 55|16@0+ (1,750) [750|1200] “Mb” Vector__XXX
SG_ Als_active : 2|1@0+ (1,0) [0|0] “” Vector__XXX
SG_ Traction_Ctrl : 3|1@0+ (1,0) [0|0] “” Vector__XXX
SG_ Speed_Limiter : 4|1@0+ (1,0) [0|0] “” Vector__XXX
SG_ Pit_Limiter : 5|1@0+ (1,0) [0|0] “” Vector__XXX
SG_ Traction_Main_SW : 20|1@0+ (1,0) [0|0] “” Vector__XXX

BO_ 45 md35_6: 8 Vector__XXX
SG_ kmh : 7|16@0+ (0.01,0) [0|0] “kmh” Vector__XXX
SG_ LaunchRpm : 23|16@0+ (1,0) [0|0] “rpm” Vector__XXX
SG_ wheelSlip : 39|16@0+ (0.1,0) [0|0] “%” Vector__XXX
SG_ Var_ALS : 55|8@0+ (1,0) [0|0] “%” Vector__XXX

BO_ 143 md35_7: 8 Vector__XXX
SG_ Speed_Front_Cal m1 : 40|16@1+ (0.1,0) [20|0] “mm/p” Vector__XXX
SG_ Speed_Rear_Cal m1 : 24|16@1+ (0.1,0) [20|0] “mm/p” Vector__XXX
SG_ mode_1 M : 56|8@1+ (1,0) [0|0] “” Vector__XXX
SG_ PH_Inj_Type m5 : 48|8@1+ (1,0) [0|0] “” Vector__XXX
SG_ PH_Phase1 m6 : 40|8@1+ (0.04,0) [0|0] “Sec” Vector__XXX
SG_ PH_Phase2 m5 : 32|8@1+ (0.02,0) [0|0] “Msec” Vector__XXX
SG_ PH_Peak_Current m5 : 40|8@1+ (0.08,0) [0|0] “Amp” Vector__XXX
SG_ PH_Phase3 m5 : 24|8@1+ (2,0) [0|0] “Usec” Vector__XXX
SG_ PH_Hold_Current m5 : 8|8@1+ (0.016,0) [0|0] “Amp” Vector__XXX
SG_ PH_TempHoldCurrent m5 : 0|8@1+ (0.016,0) [0|0] “Amp” Vector__XXX
SG_ PH_TempHoldCurrentTime m6 : 48|8@1+ (0.02,0) [0|0] “Msec” Vector__XXX
SG_ PH_Demag_mode m5 : 16|8@1+ (1,0) [0|0] “” Vector__XXX
SG_ Injector_Test_Nr m4 : 48|8@1+ (1,0) [0|0] “Inj_NR” Vector__XXX
SG_ Injector_Test_Time m4 : 40|8@1+ (1,0) [0|0] “Msec” Vector__XXX
SG_ SegInj1AtOutput m2 : 48|4@1+ (1,0) [0|0] “” Vector__XXX
SG_ SegInj2AtOutput m2 : 40|4@1+ (1,0) [0|0] “” Vector__XXX
SG_ SegInj3AtOutput m2 : 32|4@1+ (1,0) [0|0] “” Vector__XXX
SG_ SegInj4AtOutput m2 : 24|4@1+ (1,0) [0|0] “” Vector__XXX
SG_ SegInj5AtOutput m3 : 48|4@1+ (1,0) [0|0] “” Vector__XXX
SG_ SegInj6AtOutput m3 : 40|4@1+ (1,0) [0|0] “” Vector__XXX
SG_ SegInj7AtOutput m3 : 32|4@1+ (1,0) [0|0] “” Vector__XXX
SG_ SegInj8AtOutput m3 : 24|4@1+ (1,0) [0|0] “” Vector__XXX
SG_ SegInj1UseGroup m2 : 54|1@1+ (1,1) [0|0] “” Vector__XXX
SG_ SegInj2UseGroup m2 : 46|1@1+ (1,1) [0|0] “” Vector__XXX
SG_ SegInj3UseGroup m2 : 38|1@1+ (1,1) [0|0] “” Vector__XXX
SG_ SegInj4UseGroup m2 : 30|1@1+ (1,1) [0|0] “” Vector__XXX
SG_ SegInj5UseGroup m3 : 54|1@1+ (1,1) [0|0] “” Vector__XXX
SG_ SegInj6UseGroup m3 : 46|1@1+ (1,1) [0|0] “” Vector__XXX
SG_ SegInj7UseGroup m3 : 38|1@1+ (1,1) [0|0] “” Vector__XXX
SG_ SegInj8UseGroup m3 : 30|1@1+ (1,1) [0|0] “” Vector__XXX

BO_ 144 md35_8: 8 Vector__XXX
SG_ InjectionTimeGroup1 m1 : 15|16@0+ (0.002,0) [0|0] “Msec” Vector__XXX
SG_ InjectionTimeGroup2 m1 : 31|16@0+ (0.002,0) [0|0] “Msec” Vector__XXX
SG_ Mode M : 7|8@0+ (1,0) [0|0] “” Vector__XXX
SG_ InjectionStartPulsIndirect m2 : 15|16@0+ (0.002,0) [0|0] “Msec” Vector__XXX
SG_ InjectionStartPulsDirect m3 : 15|16@0+ (0.002,0) [0|0] “Msec” Vector__XXX

CM_ SG_ 143 Speed_Front_Cal “”;
CM_ SG_ 143 mode_1 “mode signal must be 1 hex”;
VAL_ 42 Lambda2_Status 0 “No Errors” 1 “Sensor To Cold Signal Valid” 2 “Sensor To Hot Signal Valid” 9 “WarmUp Fase Singnal Invalid” 4 “WarmUp Fase Singnal Valid” 8 “Temperature error Signal Invalid” 24 “Heater Ground Open” 40 “Sensor not Connected” 56 “sensor wires open” 72 “Unknown error or no sensor selected” ;
VAL_ 42 Lambda1_Status 0 “No Errors” 1 “Sensor To Cold Signal Valid” 2 “Sensor To Hot Signal Valid” 4 “WarmUp Fase Singnal Valid” 9 “WarmUp Fase Singnal Invalid” 8 “Temperature error Signal Invalid” 24 “Heater Ground Open” 40 “Sensor not Connected” 56 “sensor wires open” 72 “Unknown error or no sensor selected” ;
VAL_ 44 Aux_Out_2 0 " " 1 “Aux 2 On” ;
VAL_ 44 Aux_Out_3 0 " " 1 “Aux 3 On” ;
VAL_ 44 FuelPump 0 " " 1 “FuelPump On” ;
VAL_ 44 Aux_Out_1 0 " " 1 “Aux 1 On” ;
VAL_ 44 Lambda_Control 0 " " 1 “Lambda Controll Active” ;
VAL_ 44 Lambda_Error 0 “No Lambda Error” 1 “Lambda Error” ;
VAL_ 44 Boost_Controll 0 " " 1 “Boost Control Active” ;
VAL_ 44 Sensor_Supply 0 " " 1 “Sensor Supply Error” ;
VAL_ 44 Power_Shift_Input 0 " " 1 “Power SHift Input Active” ;
VAL_ 44 Launch_Input 0 " " 1 “Launch Input Active” ;
VAL_ 44 OverRun 0 " " 1 “Overrun FuelCut Active” ;
VAL_ 44 Boost_Limit 0 " " 1 “Boost Limiter Active” ;
VAL_ 44 Soft_Rpm_Limit 0 " " 1 “Soft RPM Limiter Active” ;
VAL_ 44 Als_active 0 " " 1 “Als_active” ;
VAL_ 44 Traction_Main_SW 0 “Traction Ctrl Disabled” 1 “traction Ctrl Enabled” ;
VAL_ 143 PH_Inj_Type 0 “userdefined” 1 “Default_1_Injector” 2 “Default_2_Injectors” 3 “Default_3_Injectors” 4 “Default_4_Injectors” 5 “Default_5_Injectors” ;
VAL_ 143 PH_Demag_mode 0 “slow” 1 “Fast” ;

File md35.dbc end ****

Br.
Henri

realdashdev · December 27, 2023, 8:27am

This tool can be used to convert DBC to RealDash XML:

wjcloudy/DBCtoRDXML: File converter from DBC to RealDash XML (github.com)

You still need to use a RealDash compatible CAN adapter though.

r6b6c6p · December 27, 2023, 10:47pm

Ok,
So i am not so familiar with python language, but managed get xml-file out.
Here attached (if someone else is too wrestling with KMS ecu), i hope i did something right here.
I assume i need to edit realdash xml-file with this my xml-file, not so sure how things work…

What about compatible CAN adapter?
My issue will be that i am running Realdash app in Android phone which is connected through Bluetooth/Can dongle (which i linked earlier) to KMS MD35 can-bus.

KMS MD35 can-bus has its own cabling for bus itself and only way to connect Android phone with RealDash app is using wireless connection.

I am now just wondering if it needs to be really compatible CAN adapter because now CAN messages are just converted Bluetooth datapacket frames.
Realdash app can see my adapter bluetooth dongle from garage site side, so am i really missing some other key points here?

-Henri-
md35.xml (7.6 KB)

realdashdev · December 28, 2023, 7:50am

CAN adapters send the frames using serial connection. Unfortunately there is no standard protocol on which format the adapter sends the data, but each adapter has their own way of packing the CAN frames into serial stream.

Its very unlikely that RealDash will be able to read the frames from your adapter. Of course you can easily try, Create the connection in the Garage and in connection settings tap CAN Monitor button to see if data is flowing in.

r6b6c6p · December 29, 2023, 1:03pm

Ok, thank you for reply.
If the case is that RealDash can not read data and can not communicate, is there any possibility / way to make connection working?

F.e.
change serial data speed etc. communication settings?
Get information from Kms about adapter and CAN frame packing, what else?

Please let me know what information you need if we want to get this adapter and communication working?

Next thing is about xml-file itself, please see xml-file generated RealDash.
Based on my md35.xml former DBC-file which i sent earlier, what kind of line code i need to add to xml-file (twinturbovmax.xml) to try out read oil pressure?

Also do i need to add i/o information somehow to RealDash too? (generate new input/output variable)

Br.
Henri
twinturbovmax.xml (7.3 KB)

realdashdev · December 29, 2023, 1:56pm

Sure, use one of the supported CAN adapter:

RealDash | Manuals | Supported CAN/LIN Adapters

Connect CAN H and CAN L wires to the adapter and your ECU. Then connect adapter to device running RealDash.

I will check the XML for you once you have established the CAN connection.

realdashdev · December 29, 2023, 2:16pm

Actually I forgot, as there is so few KMS MD35 users, there is a direct USB connection type available in RealDash:

Connect your ECU and device running RealDash with USB cable.
In RealDash, go to Garage, open vehicle door and tap the instrument cluster to open connections list. Tap ‘Add’.
Scroll down to 'MKS (MP25 and MD35) and select that.
Select ‘Serial/USB’
Select your serial device name (ECU must be powered on)
Use default baud rate and tap ‘Done’ until you are back in dashboard.

r6b6c6p · January 1, 2024, 8:09am

Hello and Happy New Year 2024!

Well using your recommended adapters might come an issue.
I am using Kms oem CAN cabling and all devices are special cabling in bus and Kms oem bus devices.

When i asked what serial data communication or protocol specific, i meant is there something to ask from Kms?

(Information needed to get/convert data in right format out, or readable contect to RealDash)

So if we can then figure out how they in KMS are packing serial data CAN to bluetooth etc… and modify some settings to get it working with Kms oem bluetooth dongle with RealDash.

Br
Henri

SandHillsHillbilly · January 2, 2024, 2:06am

If you can identify the 2 can bus wires you can bypass or eliminate the OEM adapter.

Use a MeatPi WiCAN adapter. It is Wifi and USB to RealDash and listed as compatable with RealDash. They offer two models one with OBD connector and one with wired connections to CAN Bus. You want the USB one.
$42 USD on Crowd Supply.

r6b6c6p · January 8, 2024, 4:46pm

Hi, i can identify CAN bus wires since i have built all electrical wirings by myself. The main thing is that i would like to get this project working with existing products and not so willing to add more products to CAN bus…

realdashdev · January 10, 2024, 7:36am

If you do not want to use direct USB connection or any of the RealDash compatible CAN adapters, there is no way to connect your ECU to RealDash, sorry.

r6b6c6p · January 21, 2024, 10:06pm

Ok.
Let’s approach the topic from another direction…

So if i am using serial usb can adapter what baudrate settings i should have using?

If i have connection working, how should my "realdash> xml file look like?

I fetched mine xml file from Android device under RealDash app and it looks like this.
(i needed to take out < from beginning of the xml script other ways it would not show anything):

—xml file start—
"

<?xml version="1.0" encoding="utf-8"?>

RealDash>
settings>
value name=“UserName” v=“Default”>
value name=“GridSize” v=“100”>
value name=“VehicleWeight” v=“320”>
value name=“DataSource” v=“100”>
value name=“DataloggingFormat” v=“0”>
value name=“RpmInputMode” v=“0”>
value name=“VehicleMake” v=“NuclearWinterVmax”>
value name=“VehicleModel” v=“”>
value name=“Gear1” v=“2.529000043869019”>
value name=“Gear2” v=“1.771999955177307”>
value name=“Gear3” v=“1.347000002861023”>
value name=“Gear4” v=“1.075999975204468”>
value name=“Gear5” v=“0.927999973297119”>
value name=“Gear6” v=“0.000000000000000”>
value name=“Gear7” v=“0.000000000000000”>
value name=“Gear8” v=“0.000000000000000”>
value name=“FinalGearRatio” v=“2.851000070571899”>
value name=“TireCircumferenceInMeters” v=“2.049261093139648”>
value name=“UserNickname” v=“r6b6c6p”>
value name=“EngineCC” v=“1200”>
value name=“NumCylinders” v=“4”>
value name=“InjectorSizeCC” v=“840”>
value name=“LanguageCode” v=“en”>
value name=“Fuel” v=“0”>
value name=“EngineVE” v=“75.000000000000000”>
value name=“UserRpmWarningLevel” v=“8500.000000000000000”>
value name=“UserRpmCriticalLevel” v=“9000.000000000000000”>
value name=“MaxRpm” v=“11000.000000000000000”>
value name=“MaxSpeed” v=“350.000000000000000”>
value name=“IdleRpm” v=“900”>
value name=“DatalogRowsPerSecLimit” v=“100”>
value name=“DatalogLocalFileCountLimit” v=“0”>
value name=“FuelCapacityLiters” v=“60.000000000000000”>
value name=“FuelConsumptionCorrectionFactor” v=“1.000000000000000”>/value>
value name=“FuelConsumptionUnits” v=“0”>
value name=“FuelPricePerLiter” v=“1.450000047683716”>
value name=“VehicleType” v=“0”>
value name=“EngineType” v=“1”>
value name=“VehicleColor” v=“4279054869”>
value name=“KilometersToNextService” v=“15000”>
value name=“WheelSize” v=“17.000000000000000”>
value name=“DriveType” v=“0”>
value name=“TireWidth” v=“245”>
value name=“TireAspect” v=“45”>
value name=“FrontalAreaM2” v=“1.000000000000000”>
value name=“DragCoefficient” v=“0.119999945163727”>
value name=“RollingResistance” v=“0.019999980926514”>
value name=“MechanicalEfficiency” v=“0.949999988079071”>
value name=“NumInjectionsPerCycle” v=“1”>
value name=“SpeedLimitWarningThreshold” v=“20”>
value name=“GPSTimeZone” v=“0”>
value name=“ShutdownDelaySeconds” v=“5”>
value name=“CruiseAutoSpeedThreshold” v=“5”>
value name=“DistanceUnits” v=“0”>
value name=“SpeedUnits” v=“0”>
value name=“RecentlyUsedColors1” v=“1996488704”>
value name=“RecentlyUsedColors2” v=“4294967295”>
value name=“RecentlyUsedColors3” v=“4278215777”>
value name=“RecentlyUsedColors4” v=“4278215468”>
value name=“RecentlyUsedColors5” v=“4278190335”>
value name=“RecentlyUsedColors6” v=“4294901760”>
value name=“RecentlyUsedColors7” v=“4285414144”>
value name=“RecentlyUsedColors8” v=“4283957289”>
value name=“RecentlyUsedColors9” v=“4278237352”>
value name=“RecentlyUsedColors10” v=“4278232142”>
value name=“RecentlyUsedColors11” v=“4294539520”>
value name=“RecentlyUsedColors12” v=“4290969685”>
value name=“RecentlyUsedColors13” v=“4278461229”>
value name=“RecentlyUsedColors14” v=“4291684863”>
value name=“RecentlyUsedColors15” v=“4283256141”>
value name=“RecentlyUsedColors16” v=“4284022974”>
value name=“RecentlyUsedColorIndex” v=“1”>
value name=“Toggles” v=“235161855”>
value name=“Toggles2” v=“0”>
value name=“EditBarPosX” v=“0.161458373069763”>
value name=“EditBarPosY” v=“0.208002746105194”>
value name=“DateFormat” v=“1”>
value name=“TimeFormat” v=“2”>
value name=“TileType” v=“2”>
value name=“MainMenuLocation” v=“0”>
value name=“PressureUnits” v=“1”>
value name=“NavApp” v=“0”>
value name=“CurrentDashFile” v=“%C2%85%3D%hgff%3A%3D%3ggDBOB%3F%C2%87”>
/settings>
datalog>
valueId>33
valueId>37
valueId>31
valueId>64
valueId>38
valueId>30
valueId>42
valueId>27
valueId>12
valueId>14
valueId>0
valueId>1
valueId>17
valueId>18
valueId>35
valueId>36
valueId>44
valueId>45
valueId>119
valueId>120
valueId>5
valueId>83
valueId>84
valueId>22
valueId>23
valueId>24
valueId>1339001838
valueId>145333042
valueId>-183438969
valueId>-1459291124
valueId>-393596958
valueId>1826797470
valueId>2023310975
valueId>-2075142816
valueId>-773339300
valueId>-994124257
valueId>-1083769741
valueId>-2116777741
valueId>670637746
valueId>-836914063
valueId>-1190640099
valueId>-69753175
valueId>648978917
valueId>-1160350423
valueId>335780938
valueId>420755556
valueId>-2042611096
valueId>-910069557
valueId>-910069558
/datalog>
valueMapping>
map key=“14” value=“12”>
map key=“27” value=“151”>
map key=“31” value=“254”>
map key=“64” value=“24”>
map key=“151” value=“391”>
map key=“170” value=“223”>
map key=“173” value=“269”>
map key=“200” value=“25”>
map key=“310” value=“78”>
map key=“311” value=“79”>
map key=“356” value=“355”>
/valueMapping>
connections>
connection source=“24” type=“1” deviceName=“KMS Dongle_81C3” deviceGuid=“BluetoothLE#BluetoothLEdc:fb:48:50:f7:93-e8:eb:1b:75:81:c3” ipAddress=“” ipPort=“0” baudRate=“115200” connDelay=“0” dtr=“0” rts=“0” ble=“0”>/connection>
/connections>
/RealDash>

"
—xml file end—

Thank you in advance.

Br.
Henri

realdashdev · January 22, 2024, 7:34am

The XML you have exported is the app settings, not a connection specification.
KMS Dongle_81C3 is not a supported CAN adapter, it will not work.

As I mentioned before, you have two options:

Use direct USB connection with ECU.
Use one of the supported CAN adapters.

See supported CAN adapters here:

RealDash | Manuals | Supported CAN/LIN Adapters