Failing analog inputs?

[Phasmatis568]

Has anyone else had any issues w/ the analog inputs reading a constant value no matter what you do w/ them? To the best of my knowledge, we have a defective controller. But i dont want to go a week w/o the controller while they replace it, unless i'm absolutly sure.

[KenWittlief]

I havent looked at the code for this year too much yet, but last year, if you wanted to use an analog or digital input on the RC there were TWO places where you had to 'enable' it.

maybe this is why you are not seeing the input in the variable you are looking at?

[Jay Lundy]

Make sure you do Get_Analog_Value(rc_ana_in01);

rc_ana_inxx are just the channels on the ADC, not the actual value. Get_Analog_Value() takes an ADC channel and returns the (10-bit) value on that channel.

We just modified the #defines for all the rc_ana_inxx to include the function call.

#define rc_ana_in01 Get_Analog_Value(ADC_CH0)

[Rickertsen2]

Originally Posted by Phasmatis568

Has anyone else had any issues w/ the analog inputs reading a constant value no matter what you do w/ them? To the best of my knowledge, we have a defective controller. But i dont want to go a week w/o the controller while they replace it, unless i'm absolutly sure.

It is HIGHLY unlikley that you are experiencing a hardware problem. A user error is much more likley. Could you post your code and i can prolyl help you? Specifically could you post your User_Initialization() function, as well as whatever code you wrote that uses the Analog input?

[Dave Campbell]

Originally Posted by Rickertsen2

It is HIGHLY unlikley that you are experiencing a hardware problem. A user error is much more likley. Could you post your code and i can prolyl help you? Specifically could you post your User_Initialization() function, as well as whatever code you wrote that uses the Analog input?

Problem fixed. You were all correct. Main problem was advisor error, second problem - code error.
Thanks

[KenWittlief]

HW and SW people always seem to be at odds with each other, esp when something is not working like it seems it should.

There is something I call "computer science 101 syndrome" typically when a student takes their first programming class in college, they are given a very simple program to write, like add three numbers and print the result.

half the students will make a mistake in the syntax or control language or something (esp when using a mainframe) and they wont be able to see the problem in the code, so at some point they exclaim:

"THAT STUPID COMPUTER IS NOT WORKING RIGHT!"

You are in good company, and you are not the first!

:c)