EvoScan v2.6 And New EvoScan GPS/Logger/Reflashing Touchscreen Review
Jul 9, 2010, 02:41 PM
#1430
Jul 13, 2010, 04:52 PM
#1432
IDK if this has been answered but I used v2.7 for the first time tonight to set the BISS on an evo8 and I tried entering the Custom Request: 0xC3 in the box but I couldn't get the SAS Mode actuator test to engage. I'm not talking about using the actuator test BUTTON but manually engaging it so I can datalog the actual idle RPM value with Evoscan while I adjust it. I used this all of the time on previous versions. Am I just doing something wrong?
Also, is there already a list of custom request ID's for any of the actuator tests?
Also, is there already a list of custom request ID's for any of the actuator tests?
Last edited by Jack_of_Trades; Jul 13, 2010 at 06:55 PM.
Jul 13, 2010, 08:30 PM
#1434
Evolving Member
For some reason i am unable to activate SAS mode with Evoscan it just says no resonse everything else works fine though, its annoying i cant set my idle grrrr
Jul 13, 2010, 09:18 PM
#1435
yes there is a list of the requestids for the actuators on my website www.evoscan.com under Tech info.
Originally Posted by www.Evoscan.com
http://www.evoscan.com/technical-veh...hi-diagnostics
To run a custom request in Evoscan, press the start logger. during logging you can type a 2 letter custom request code inthe the custom request box at the bottom of the EvoScan main screen. Leave repeat unticked, unless you want to continually run the custom request.
Custom Request
Action
F1
?
F2
?
F3
?
F4
?
F5
Canister purge
F6
Turn on fuel pump
F7
Disable injector #6
F8
Disable injector #5
F9
Disable injector #4
FA
Disable injector #3
FB
Disable injector #2
FC
Disable injector #1
F1 to F6 only work with engine stopped. After ECU any of theese commands it invokes corresponding relay/solenoid for about 6 seconds. After that it answers in the Response box with 0x00. If engine is running ECU returns 0xFF immediately as completed.
F7 to FC disable injector for about 6 seconds and returns a response of 0x00.
Diagnostic fault codes are stored as bitmaps in two 8-bit cells. There're two kinds: active and stored (accumulated).
You can use the windows calculator in programmer mode (Alt-3) to convert between hex (0x??) numbers (don't need to type the 0x part, just the ?? part) and you can use the calculator to then switch to the 8-bit binary (bin) numbers for trouble code bit analysis.
Also you can use the EvoScan DTC option "MUTII EFI" from the dropdown, and select DisplayDTC and it will do the conversion for you automatically and look up the diagnostic codes. If your vehicle doesn't support
Custom Request: CA will clear the DTS / Diagnostic Trouble Code CEL (check engine light) fault memory.
Custom
Request Description
38 (4C) Faults, low byte
39 (4D) Faults, high byte
3B (4A) Stored faults, low byte
3C (4B) Stored faults, high byte
CA Clear faults, returns 0x00
Bit # Code Fault
1 11 Oxygen sensor
2 12 Intake air flow sensor
3 13 Intake air temperature sensor
4 14 Throttle position sensor
5 15 ISC motor position sensor
6 21 Engine coolant temperature sensor
7 22 Engine speed sensor
8 23 TDC sensor
9 24 Vehicle speed sensor
10 25 Barometric pressure sensor
11 31 Knock sensor
12 41 Injector circuit
13 42 Fuel pump relay
14 43 EGR
15 44 Ignition coil
16 36 Ignition circuit
I also wondered if I could manually trigger the 'Radiator Fan HIGH' actuator and tick the checkbox so it stayed on until it was manually disabled? An Auto-X guy asked me if it was possible to do so since it would greatly aid in managing cooling temps while the car is being taxed so much in insanely high Air Temp situations.
Last edited by Jack_of_Trades; Jul 13, 2010 at 09:21 PM.
Jul 14, 2010, 04:13 PM
#1436
Evolving Member
