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.

 

Colby already sent me one for free

+ I need this one

+ Colby already sets the voltage for pin8 somehow, but its not available to the J2345 API..

 

Can you follow the PIN8 to FTDI chip at OP2 PCB?

 

nope hehehe

best bet is to just ask Colby how to activate pin8 on the obd connector.

 

yes if Colby is willing to share that information.
Or simply setting every FTDI output port and observe PIN8.

 

I guess you could jack the back of the OBD plug.

I dunno if its needs to be grounded OR +12v

 

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)?

 

Hi guys,
I have AUS Evo X SST romid 53050006.
Has anyone got a config file for, or can someone tell me the 3 memory addresses so i can setup my Mode23 logging.

Thanks,

 

email me the rom - i'll look it up for you

@gmail.com

 

Just sent my Rom to your email @gmail.com'
Thanks heaps for helping me

 

please dont quote my email address on the forums

spam bots pick it up

 

53050006 XML update on 1st post.

 

I will check with Colby what the pin8 ADC code is, I think I already know it though because I've used it before.

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.

 

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)

 

thats interesting, but I can't access ALDL, MUTII, and OBDII on the EvoX using existing init routines. perhaps they just killed the init access to them and left behind the code