Help please, can't seem to get speedo to work in adx dash.

[37chevrod]

Hi everyone, Thanks to this fantastic site I've been able to get my streetrod running quite well,not that it's been easy or that it's finished, but getting closer. I'm using a dakota digital dash with a digital speed interface on a 700r4, the digital dash is working great, but I can't seem to get the interface to communicate with the 7730 ecm using $8D bin or get the interface to communicate to the dash that I've built in the adx file. The digital interface has signals of 8k 4k and 2k available. I've tried hooking up the 4k signal to the ecm terminal B10 still nothing. also I'm using an autoprom, and everything else on the adx dash is working. Any insight would be greatly appreciated. Thanks in advance

[RobertISaar]

B10 is used with a magnetic VSS(or at least that type of signal, which is AC). for an optical signal(or DC), you need to connect to pin C6.

[37chevrod]

Thanks for the quick responce Robert. I repinned from B10 to C6,and still no data on the adx dash. Do I need to edit the vehicle speed conversion settings in the adx editor, if so can anyone tell me what they should be. Thanks

[RobertISaar]

is your BIN setup for a 4K PPM signal coming from the optical circuit?

[37chevrod]

In the Scalars list under Vehicle speed Sensor, its set at 4006.96 p/mile. is that what you meant ?

[RobertISaar]

yes, that covers the calculation portion. is the flag set to read an optical sensor?

[37chevrod]

is switch 18 bit 6 the one you mean, if so it was not set, I set it and tryed it but still no speedo.

[RobertISaar]

that's the correct one.

at least a communication issue is ruled out since the rest of the dash is working... can you post a XDL log and the ADX you're using? i'm wondering if there is something odd going on there.

[37chevrod]

I'll have to figure out how to post my xdl, hav'nt done that before.

[RobertISaar]

it's an accepted attachment, so you should be able to directly attach it.

[EagleMark]

I'll have to figure out how to post my xdl, hav'nt done that before.When you reply look at bottom right for Go Advanced, then under that box is Add attachments.

[37chevrod]

Here's the adx and xdl file Ive been working with.

[EagleMark]

Vehicle speed output format is set to hex... change to floating point, it's in conversion tab.

[RobertISaar]

the equation is also odd.... should be just X, the * may mess with it. integer format will also work nicely, since there is no need for any decimal places unless you convert over to metric.

[37chevrod]

Tried both floating point and intreger format along with and without deleting the *, still no speedo:mad1:

[RobertISaar]

hmm... can you verify that the signal is making it out of the guage(i'm assuming the guage does the conversion and signal generation)?

[37chevrod]

there is actually a stand alone interface with a choice of 8k 4k or 2k and when i mistakenly hooked the digital dash which takes a 8k signal to the 4k terminal the dash speedo read half speed so I have assumed it's working all along.

[RobertISaar]

interesting.

is there any documentation provided that states what kind of signal is created for the 4K PPM output or even better, some kind of functional test?

if the signal is making it all the way to the ECM pin, i would suspect the ECM as possibly being the problem. i've heard of it happening before, but i've never experienced it myself.

[37chevrod]

I will look for some documentation and verify the signal, might take a few days, thank you both for your help so far.

[EagleMark]

Robert, are you sure the bin he has is set for ALDL output like this with no changes? If there is a signal like he is assuming, then the data should at least show something? Even if wrong?

37chevrod, is this a seperate signal going to ECM? Not split from something? Any documents, diagrams or pictures?

[RobertISaar]

MPH is a value the factory BIN transmits over ALDL, i'm not certain why anyone would want to remove it.

when i looked at the log, MPH stayed at 0 the entire time. after the engine was shutoff, it jumped up to 4MPH for some reason, lasted a couple of seconds until the log was ended.

[EagleMark]

OK that I understand but you said:


B10 is used with a magnetic VSS(or at least that type of signal, which is AC). for an optical signal(or DC), you need to connect to pin C6.

So VSS pin in has changed?

[RobertISaar]

pin changes for optical vs magnetic, but the way the code works, regardless of which is selected, either can get written to the RAM location that is used for MPH.

in this case, "optical" meaning if the VSS signal is basically the interface switching the signal to ground at a rate of 4000 pulses per mile. the ECM provides a current limited +12V via a 1.2K resistor, the U13 portion of the circuit is i think an inverter, but then it makes it's way to the U10(SCI Output) chip. there are a couple of logic gates there, eventually turns into "VSS", which goes to sheet#1.

magnetic works a bit differently. VSSHI goes into U24 which contains a zero crossing detector. when the voltage on that circuit rises above, then falls below 0 volts, the output of it toggles. you can see it branch down to the divider portion of the circuit, but it's not relevant so i'll skip past it. anyways, the signal makes its way to the U10 chip, where it runs through some logic(i think the first portion is a flip-flop?), but you can see that one of the outputs runs through more of the logic gates. anyways, there 3 AND and 1 OR gate in there. lets call the AND gates 1, 2 and 3 going from top to bottom. the logic works like this:

if optical VSS is selected: the signal simply runs through AND1, then into OR, where it becomes the VSS signal that the U2 chip creates the VSS period value for. U2 directly interfaces with U1, which is the processor. anyways, following the signal, it goes through U13 which inverts the signal(causing low to be high and high to be low). i imagine this is also done for voltage level matching(since 12V to some of these chips would probably kill them). then it goes to AND1. for an AND gate to go to logical 1, both inputs must be high. since the magnetic VSS signal will switch on it's own, let's look at the other input. it comes out of AND3, which has its state determined by "OUT4" and by a signal that comes from the limp-home hardware. OUT4 is controlled by the magnetic vs optical bit being set in the calibration. if it's not set toward optical, the AND3 causes it's output to change. note that AND2 inverts a signal, so it becomes active when AND1 is disabled.

so when optical is disabled, the magnetic signal is allowed to pass through AND2 and then OR.



it's kind of confusing unless you've dealt with logic gates before.

[37chevrod]

I was able to hook up an occilliscope and establish that its a magnetic vss ac pulse signal 4000 pp/m. so along with reattaching ecm input to pin B10, what else do I need to change.

[37chevrod]

sorry I did'nt see your post Robert before I sent My Last

[RobertISaar]

not a problem, its really just an explanation of why the pin needs to change based on the different signals. in the end, it comes down to "if switched DC, use this pin and have flag set to optical, if not, use other pin and set to magnetic".

[37chevrod]

Thanks Robert I'll repin and reset the flag tomorrow morning and see what happens.