Evo X Logging
Jul 16, 2009, 11:10 PM
#556
Evolved Member
Join Date: Mar 2008
Location: Lattitude 48.38°, Longitude 17.58°, Altitude 146m = Slovakia, for common dude
Posts: 730
Likes: 0
Received 3 Likes
on
2 Posts
If you are willing to open up OP2 there should be one FTDI chip, now one has to find free ouput port pin, connect it to some general purpose transistor apply the voltage at the collector, follow it at emmitor and connect emmitor to PIN8 of OBD plug.
the rest is simple setting it FTDI output via FTDXX library.
I believe that guys here would be more than willing to get you one for free in case of damage.
the rest is simple setting it FTDI output via FTDXX library.
I believe that guys here would be more than willing to get you one for free in case of damage.
Last edited by acamus; Jul 16, 2009 at 11:23 PM.
Jul 16, 2009, 11:29 PM
#560
Evolved Member
Join Date: Mar 2008
Location: Lattitude 48.38°, Longitude 17.58°, Altitude 146m = Slovakia, for common dude
Posts: 730
Likes: 0
Received 3 Likes
on
2 Posts
yes if Colby is willing to share that information.
Or simply setting every FTDI output port and observe PIN8.
Or simply setting every FTDI output port and observe PIN8.
Jul 16, 2009, 11:35 PM
#562
Evolved Member
Join Date: Mar 2008
Location: Lattitude 48.38°, Longitude 17.58°, Altitude 146m = Slovakia, for common dude
Posts: 730
Likes: 0
Received 3 Likes
on
2 Posts
I do not have OP2 yet as I do not need it, nor the ECU.
I can only help you with remote assistance
You can try what Colby is doing at that PIN
Maybe you can email me some picture of OP2 PCB.
Are you referring to PassThruSetProgrammingVoltage function in op20pt32.dll (Ordinal 9, EntryPoint 0x0001A20)?
I can only help you with remote assistance
You can try what Colby is doing at that PIN
Maybe you can email me some picture of OP2 PCB.
Are you referring to PassThruSetProgrammingVoltage function in op20pt32.dll (Ordinal 9, EntryPoint 0x0001A20)?
Last edited by acamus; Jul 16, 2009 at 11:55 PM.
Jul 17, 2009, 11:37 PM
#568
Yes Tephra has already worked it out in detail depth. hence where we are today
There was debug mode10 in the last data.xml in EvoScan, but there was no response from the ecu without the init line toggled.I too can only do remote testing on EvoX's
I am willing to give it another go if you can come up with some more info to get us over this hurdle, because the ram addresses are killing me, and is not a very nice solution for the users hehe. but also I don't think the OP2 hardware is capable without some hardware changes. i.e obd2 pin12 is the one that goes to the init line on the evox ecu, and needs to be switched over to pin8 for the op2 voltage capability.
So basically we are screwed
I think a few byte changes in a flashable rom is easier than swapping over a pin12 on the OBD vehicle port.
Jul 18, 2009, 11:15 AM
#569
Evolved Member
Join Date: Mar 2008
Location: Lattitude 48.38°, Longitude 17.58°, Altitude 146m = Slovakia, for common dude
Posts: 730
Likes: 0
Received 3 Likes
on
2 Posts
I even believe we do not need OP2 to get the communication going (we need it for flashing, but probably not for logging).
I would play with OP1.3 just small HW update for X, handling pin 8. Hamish, I bet you remember that you had
to ground OBD PIN1 to get EVO4-6 MUT communication going, maybe it is as easy as doing same for OBD PIN8
with CAN ECU's.
OK If I will sort the SH2 timers, pre-scalers and dividers out I will probably come to
correct initialization. Then I will compare to X.
I know you are always speaking Mode 0x10, but this is needed for CAN not for MUT I believe.
What I have seen so far even main serial routine is the same, Mitsu has retained ALDL 1953 communication,
they have retained MUTII, they have retained OBDII communication in the code, they have only extended it for CAN,
I believe it is because servicemen are not forced to used MUTIII, but can use MUTII tool with proper cartrige.
And I have also seen that Mode 0x10 check (that tephra is talking about few posts back) is behind #h'C3 check, which is done in all ECU's (SH or m32r and possibly H8, but I have not checked - maybe Ceddy can have a look)
I would play with OP1.3 just small HW update for X, handling pin 8. Hamish, I bet you remember that you had
to ground OBD PIN1 to get EVO4-6 MUT communication going, maybe it is as easy as doing same for OBD PIN8
with CAN ECU's.
OK If I will sort the SH2 timers, pre-scalers and dividers out I will probably come to
correct initialization. Then I will compare to X.
I know you are always speaking Mode 0x10, but this is needed for CAN not for MUT I believe.
What I have seen so far even main serial routine is the same, Mitsu has retained ALDL 1953 communication,
they have retained MUTII, they have retained OBDII communication in the code, they have only extended it for CAN,
I believe it is because servicemen are not forced to used MUTIII, but can use MUTII tool with proper cartrige.
And I have also seen that Mode 0x10 check (that tephra is talking about few posts back) is behind #h'C3 check, which is done in all ECU's (SH or m32r and possibly H8, but I have not checked - maybe Ceddy can have a look)
Last edited by acamus; Jul 18, 2009 at 12:11 PM.