Page 39 of 57
Re: OSE 12P V111
Posted: Sun Aug 18, 2013 3:20 am
by Six_Shooter
My adapter is pretty much done (I'd say 92%ish mark). Just need to bench test it later, then set up a bin for my car, to test in car using the modified flash tool.
Sorry for the delay, life has been busy. :/
Re: OSE 12P V111
Posted: Mon Aug 19, 2013 5:46 am
by Six_Shooter
So I'm bench testing this now, I have a few issues to sort out before testing what happens with the flash tool it seems.
Lets back up for a minute when it comes to data logging. The '165 has the hardware for the 8192 comms. This is what I am using to see data with. Pin A8 FWIW.
The issue seems to be that there is no change in some of the displayed parameters, and incorrect changes in others.
I.E.:
Engine speed doesn't change, just stays at 180 RPM, even though the injector LEDs on my JimStim show a change in RPM, like I am used to with other ECMs.
When I sweep the MAP input the TPS data changes, and the MAP data changes when the TPS is swept.
I have verified with a multimeter that the inputs are indeed correct, according to the pinout chart included in the download, and the ose12p-wiring-1-2.pdf included in the first post of this thread.
Is it possible that the data words are different when using a '165 vs the 8192 comms board that is added to the '808?
I am using a Moates Ostrich, and ALDL Xtreme, with TPRT V5.
I am also using a MEMCAL adapter and a V6 MEMCAL from a North American 2.8L V6. It has a knock board attached, could this be causing some of the issue?
On the topic of knock boards. The $12P pdf doesn't show a pin for a knock filter/sensor input, is this something that has been removed in $12P?
I have tried both the 1 BAR and 3 BAR ADXs included in the $12P download, which I assume the only difference is the scaling of the MAP data and related items between the two ADXs.
Re: OSE 12P V111
Posted: Mon Aug 19, 2013 6:17 am
by Six_Shooter
After some research it seems that knock sensing is still possible with $12P, it just needs to be turned on (and pinned for it).
I have thought about trying the custom mode 6 set-up, but I would think that the stock ALDL comms should work with the ADX out of the box.
Any insight would be great. I'd really like to try this in my car.
BTW, I have tried both a completely stock $12P bin as included in the download and a modified bin for flex ooutputs, both have the same result when it comes to ALDL data.
Re: OSE 12P V111
Posted: Mon Aug 19, 2013 9:28 am
by VL400
A '165 works the same for the ALDL data stream as the local '808 does, and I know of a number of people using them both here and in the US. Check that echo is set correctly for your type of interface - as RPM is 180 (0xB4, the checksum of the message packet being sent and echo'd by the interface) id say its just the echo setting is wrong.
Re: OSE 12P V111
Posted: Mon Aug 19, 2013 11:36 am
by Six_Shooter
VL400 wrote:A '165 works the same for the ALDL data stream as the local '808 does, and I know of a number of people using them both here and in the US. Check that echo is set correctly for your type of interface - as RPM is 180 (0xB4, the checksum of the message packet being sent and echo'd by the interface) id say its just the echo setting is wrong.
Ok, how would I go about doing that?
I looked through the ADX parameters and didn't see anything about echo.
Re: OSE 12P V111
Posted: Mon Aug 19, 2013 11:59 am
by antus
Its in the 'adx header data' section, 'RS232 Echo'. The default setting for $12p is off because most people are running '808s with full duplex serial links hacked in, but you will need to change it.
If you use the plugin with an NVRAM, then plugin has its own setting too. But I dont think you are using that so its just the adx setting.
Re: OSE 12P V111
Posted: Mon Aug 19, 2013 12:52 pm
by Six_Shooter
Thanks, found it, it's cleared up most of the issues, I think I need to do some repairs to my test bench to rectify most of the rest.
The only one that I can't figure out yet, is the TPS doesn't change on the dash, even though the input is definitely changing.
Re: OSE 12P V111
Posted: Mon Aug 19, 2013 12:59 pm
by antus
Check the DTCs and see if it has logged a fault with the circuit. If it faults it will generate a fake TPS signal based on RPM. You can also view the TPS voltage on a monitor to verify the input.
Re: OSE 12P V111
Posted: Mon Aug 19, 2013 1:52 pm
by Six_Shooter
Yep, sure enough DTCs were set for the TPS and a number of other things.
So far I have not been able to get either of the flex table outputs to function. I have one set up as a wastegate control output, RPM, vs KPH at this point, but I think I will change that when it comes time to actually run on the car, maybe RPM vs TPS...
The other I have set for shift light, as a digital on/off output, and have used TPS vs RPM.
I believe I have one set to be active only with engine run, I believe I set the shift light this way.
--==EDIT==--
I pulled a brain fart, I forgot about reading in the tuning guide that in a digital set-up for the flex table, that values between 0 and 100 were still required, up to 49.9 is off, and 50.1 and up is on. I was using 1 and 0, what I'm used to for digital to try and get it to work. So that output works.
I need to modify the wastegate output to not use the VSS, since I don't have one on my test bench. I'm not sure why I set it up that way initially. lol
Re: OSE 12P V111
Posted: Mon Aug 19, 2013 2:16 pm
by Six_Shooter
Well, both flex outputs that I have set up seem to be responding correctly to the inputs.
So I would say the modified flashtool works.
