GUI for new Freematics OBD-II Emulator
Re: GUI for new Freematics OBD-II Emulator
What happen with this?? Any updates? About simulate the status of monitors?? .readiness??.
Re: GUI for new Freematics OBD-II Emulator
Halide wrote:What happen with this?? Any updates? About simulate the status of monitors?? .readiness??.
+1
Re: GUI for new Freematics OBD-II Emulator
Already added long ago.
-
- Posts: 3
- Joined: Mon Aug 17, 2015 9:49 am
Re: GUI for new Freematics OBD-II Emulator
yes it was working but with the new update its stopped working. it solved the mil off issue but the monitors are not supported
Re: GUI for new Freematics OBD-II Emulator
Have the readiness monitors been fixed in the last update?
I am excited
Thank you to get going with this project
I am excited
Thank you to get going with this project
-
- Posts: 4
- Joined: Tue Nov 24, 2015 5:06 pm
Re: GUI for new Freematics OBD-II Emulator
I think I found a way MIL is off and readiness is send!!
you have to use the firmware from 20150726 (only one the MIL is off) and readiness works after plugging the emulator to power. when you open the gui and connect it stops working. this happens with the guis back to 20150516. so do not use them.
the gui from 20150506 works fine. you can connect and readiness stays.
tell me if it works for you, too.
you have to use the firmware from 20150726 (only one the MIL is off) and readiness works after plugging the emulator to power. when you open the gui and connect it stops working. this happens with the guis back to 20150516. so do not use them.
the gui from 20150506 works fine. you can connect and readiness stays.
tell me if it works for you, too.
-
- Posts: 4
- Joined: Tue Nov 24, 2015 5:06 pm
Re: GUI for new Freematics OBD-II Emulator
i played a lot last days. tried to use at commands with win10 but i didn't get it to work. so i worked on the defaults.xml file in the htdocs folder. added a lot of params to change the values set by the firmware. (e.g. obd type from california... to eobd and obd2). got full readiness for petrol and diesel (with different defaults files). it is the 0101. for petrol use 0007FF00. for diesel use 000FFF00.
this is my defaults.xml:
<?xml version="1.0" encoding="utf-8"?>
<defaults>
<param id="0101" value="0007FF00"/>
<param id="0151" value="0"/>
<param id="011C" value="7"/>
<param id="0130" value="76"/>
<param id="0131" value="251"/>
<param id="0142" value="12"/>
<param id="014E" value="2351"/>
<param id="0145" value="22"/>
<param id="0147" value="24"/>
<param id="0148" value="23"/>
<param id="0149" value="25"/>
<param id="014A" value="22"/>
<param id="014B" value="24"/>
<param id="014C" value="26"/>
<param id="015A" value="23"/>
<param id="0152" value="5"/>
<param id="0123" value="77"/>
<param id="012C" value="7"/>
<param id="012E" value="11"/>
<param id="0132" value="10"/>
<param id="013C" value="281"/>
<param id="013D" value="295"/>
<param id="013E" value="260"/>
<param id="013F" value="275"/>
<param id="011F" value="230"/>
<param id="0104" value="25"/>
<param id="0105" value="90"/>
<param id="010A" value="150"/>
<param id="010B" value="100"/>
<param id="010C" value="2000"/>
<param id="010D" value="0"/>
<param id="010F" value="20"/>
<param id="0110" value="80"/>
<param id="0111" value="20"/>
<param id="0122" value="205"/>
<param id="012F" value="75"/>
<param id="0133" value="101"/>
<param id="0143" value="26"/>
<param id="0146" value="25"/>
<param id="015C" value="95"/>
<param id="015E" value="9"/>
<param id="0161" value="36"/>
<param id="0162" value="26"/>
<param id="0163" value="240"/>
<param id="0168" value="372"/>
</defaults>
this is my defaults.xml:
<?xml version="1.0" encoding="utf-8"?>
<defaults>
<param id="0101" value="0007FF00"/>
<param id="0151" value="0"/>
<param id="011C" value="7"/>
<param id="0130" value="76"/>
<param id="0131" value="251"/>
<param id="0142" value="12"/>
<param id="014E" value="2351"/>
<param id="0145" value="22"/>
<param id="0147" value="24"/>
<param id="0148" value="23"/>
<param id="0149" value="25"/>
<param id="014A" value="22"/>
<param id="014B" value="24"/>
<param id="014C" value="26"/>
<param id="015A" value="23"/>
<param id="0152" value="5"/>
<param id="0123" value="77"/>
<param id="012C" value="7"/>
<param id="012E" value="11"/>
<param id="0132" value="10"/>
<param id="013C" value="281"/>
<param id="013D" value="295"/>
<param id="013E" value="260"/>
<param id="013F" value="275"/>
<param id="011F" value="230"/>
<param id="0104" value="25"/>
<param id="0105" value="90"/>
<param id="010A" value="150"/>
<param id="010B" value="100"/>
<param id="010C" value="2000"/>
<param id="010D" value="0"/>
<param id="010F" value="20"/>
<param id="0110" value="80"/>
<param id="0111" value="20"/>
<param id="0122" value="205"/>
<param id="012F" value="75"/>
<param id="0133" value="101"/>
<param id="0143" value="26"/>
<param id="0146" value="25"/>
<param id="015C" value="95"/>
<param id="015E" value="9"/>
<param id="0161" value="36"/>
<param id="0162" value="26"/>
<param id="0163" value="240"/>
<param id="0168" value="372"/>
</defaults>
Re: GUI for new Freematics OBD-II Emulator
On which ECU do i have to request to get a respond?. i have been trying
7DF CAN identifier for functionally addressed request messages sent by external test equipment
7E0 Physical request CAN identifier from external test equipment to ECU #1
7E8 Physical response CAN identifier from ECU #1 to external test equipment
7E1 Physical request CAN identifier from external test equipment to ECU #2
7E9 Physical response CAN identifier from ECU #2 to external test equipment
7E2 Physical request CAN identifier from external test equipment to ECU #3
7EA Physical response CAN identifier from ECU #3 to external test equipment
7E3 Physical request CAN identifier from external test equipment to ECU #4
7EB Physical response CAN identifier ECU #4 to the external test equipment
7E4 Physical request CAN identifier from external test equipment to ECU #5
7EC Physical response CAN identifier from ECU #5 to external test equipment
7E5 Physical request CAN identifier from external test equipment to ECU #6
7ED Physical response CAN identifier from ECU #6 to external test equipment
7E6 Physical request CAN identifier from external test equipment to ECU #7
7EE Physical response CAN identifier from ECU #7 to external test equipment
7E7 Physical request CAN identifier from external test equipment to ECU #8
7EF Physical response CAN identifier from ECU #8 to external test equipment
7DF CAN identifier for functionally addressed request messages sent by external test equipment
7E0 Physical request CAN identifier from external test equipment to ECU #1
7E8 Physical response CAN identifier from ECU #1 to external test equipment
7E1 Physical request CAN identifier from external test equipment to ECU #2
7E9 Physical response CAN identifier from ECU #2 to external test equipment
7E2 Physical request CAN identifier from external test equipment to ECU #3
7EA Physical response CAN identifier from ECU #3 to external test equipment
7E3 Physical request CAN identifier from external test equipment to ECU #4
7EB Physical response CAN identifier ECU #4 to the external test equipment
7E4 Physical request CAN identifier from external test equipment to ECU #5
7EC Physical response CAN identifier from ECU #5 to external test equipment
7E5 Physical request CAN identifier from external test equipment to ECU #6
7ED Physical response CAN identifier from ECU #6 to external test equipment
7E6 Physical request CAN identifier from external test equipment to ECU #7
7EE Physical response CAN identifier from ECU #7 to external test equipment
7E7 Physical request CAN identifier from external test equipment to ECU #8
7EF Physical response CAN identifier from ECU #8 to external test equipment