I would like to express my sincere appreciation for all the tech support that Azure Dynamics has provided. Beth Silverman, the support person, has been very quick to respond with whatever information she can provide from the controller designers. Here's the e-mail:
From: Tim Kutscha [mailto:firstname.lastname@example.org]
Sent: Monday, September 17, 2007 8:34 PM
To: Beth Silverman
Subject: Re: tapping into the encoder signals to drive the RPM gauge
I hope you had a good two days off last week. Thanks for the info on the SPEEDO_BUF output on the controller. Since this wasn't listed in the Pedal_Controlled_DMOC445_User_Manual_v3.pdf file, I didn't think it was active. From your e-mail, it sounds like the SPEEDO_BUF output is active on my pedal-controller DMOC.
From one document it says the signal is 12V open-emitter. I'm guessing its a PWM (pulse width modulated signal) that pulls an external resistor up to 12V through a transistor. Is this true?
Is the SOC_BUF signal also active on my DMOC445? What is the format of its output? PWM? Does it get its state from the battery voltage or does it require the amp-hour counter to be attached?
Do the amp-hour counter input/outputs work? If so, do you sell a device that I can connect to them?
Do the BRAKE_PEDAL,BRAKE_LO inputs work? If so, what is the proper potentiometer to attach to them?
Is there any customer useful behavior on the ANAIN3/LED_OVERTEMP, ANAIN2/LED_MALFN, NONISO_ADIO1, NONISO_ADIO2, ANAIN1 or ANAIN0 signals?
LEDs are 3.3V (unfused outputs). If an LED is connected to it, a current limiting resistor is needed.
Have a great week!
From: Beth Silverman
To: Tim Kutscha
Sent: Monday, September 17, 2007 10:26:05 AM
Subject: RE: tapping into the encoder signals to drive the RPM gauge