AutoProm ADC Interface Channels Set up in TunerPro!

[RobertISaar]

i get the feeling..... that payload and body size may need to be tweaked to have their information saved to the XDL.

just a thought.

MM would know best. i'm still not 100% certain how the autoprom knows WHEN to transmit it's data, unless it reads the packet logic as it comes along, recognizes the checksum and immediately starts injecting data.

[EagleMark]

Tried making adjustments to payload size and all data from car and AutoProm goes bad!

Mark at TunerPro and David and Craig from Moates are looking into it. Just did 2 test logs for them to verify while hooked to Suburban running and sent them logs and ADX file.

Same on car with data flowing as on bench, AutoProm data shows fine either way, but does not show up in data log?

[T2000]

Hi guys, sorry for the late reply - I have done a fair amount of troubleshooting in the hope that I can resolve my own problems as well as trying to help with yours.

Good news for me!
I have managed to resolve my spikes (or glitches) by simply adding a non polarised capacitor to filter a noisey signal from the wideband controller caused when it tries to heat the sensor.
I can also confirm that when I record a log the ADC data sometimes trys to disappear... it is weird, I have noted the behaviour that you guys have described but when I restarted TP5 and opened my logs the ADC data was there! It has always been available in my logs as dash data and History tables but has sometimes disappeared from my monitors.

Anyway... here is some more stuff for you to look over, hopefully it helps with your issues.

[T2000]

Try increasing Payload size by 6 and leave everything else unchanged - worked for me ;)

[EagleMark]

Hmmmm? Does not work on $42 which is old 160 Baud, messed up all other data... what ECM mask did this work on?

Moates and TunerPro were working on this when I left and I have not could up to email yet for a reply. Will update when I do...

[T2000]

Hmmmm? Does not work on $42 which is old 160 Baud, messed up all other data... what ECM mask did this work on?Moates and TunerPro were working on this when I left and I have not could up to email yet for a reply. Will update when I do...

Hi Mark;

As per my earlier post the XDF is http://www.gearhead-efi.com/Fuel-Inj...6&d=1337727128"OSE12P V111 - 1,2 and 3 bar.xdf"which is an enhanced version of $12

I am running this on an old '808 ECM http://www.techedge.com.au/vehicle/1227808/which natively only supports 160 Baud.

I have added the SXR chip to get 8192 baud ALDL...The ALDL data is going directly from my SXR upgrade board to the APU1 and not via the vehicles ALDL connector (although that is possible it was just undesirable for my application)

I have successfully tested the APU .adx upgrade for ADC data on the following combo's so far:

ECM: 16176424 with $11 (Native 8k ALDL)
304 cu in V8 (Holden)
$11 based mask with a bin based on BPMN9322

ECM: 1227808 with $12 (Native 160b ALDL but with SXR upgrade delivering 8k)
231.3 cu in V6 (Buick/Holden L27 - similar to the Buick LN3)
$12 based mask with a bin based on "OSE $12P V111 APNX V6" - which is in that OSE$12P zip I posted

ECM: 1227808 with $12 (Native 160b ALDL but with SXR upgrade delivering 8k)
304 cu in V8 (Holden)
$12 based mask, $12 based mask with a bin based on "OSE $12P V111 BLCF V8" - which is also in that OSE$12P zip.

All 3 tests have worked great for me.

[EagleMark]

Well that's good news! I've had one other person say that raising payload by the 6 also worked, but it to was a 8192 Baud system, this has not worked for me on a 160 Baud... yet...