RoboSavvy Forum

Input values on AD(x)

2008-03-13T18:05:07+01:00

I did see the electrical scheme in the manual assuming it was already integrated on the board. Clear case, it isn't. I used two 48K resitors (both measured 48K5), they do the job. Thanks again!

Other inconsistant AD(x) readings I mentioned are caused by low battery voltage. At second tought I remembered that those NiMh packs (as well as NiCad) gain their full capacity after a few charge/discharge cycles.

At this moment I play with the tilt sensor input, want RN to react on back/forward tilting when he's moving. Code snippets in some posts are great help.

Gerry

Statistics: Posted by Gerry52 — Thu Mar 13, 2008 6:05 pm

Input values on AD(x)

2008-03-07T22:29:11+01:00

While you look to the posting of the code.

The AD(x) command reads the voltage on the ADx pins. The value returned is between 0 and 256 over the input range 0 to 5Volts.

To measure the battery voltage which is greater than 5 Volts, you need to divide the battery voltage by two with a pair of resistors.

The battery voltage is on the connectors down the side of the board which feed the servos. Battrey voltage is on the middle pin. You need a pair of resistors in series between the battery voltage and ground ( the pin towards the edge of the board. The two resistors should be of equal value ( between 22K to 47K ohms each)

The point between the two resistors is at half the battery voltage and is fed to the AD6 connector (pin nearest center of the board). The middle pin of the AD connectors is not battery, it is regulated 5 Volts.

Now the value read by AD(6) will be the 256 * (battery voltage/ (5Volts * 2(voltage divider)), which is what you want.

Note when the battery voltage drops below about 5.5 volts, the reference in the processor starts to drop, since this is also driven by the battery, so values are no longer valid.

Statistics: Posted by i-Bot — Fri Mar 07, 2008 10:29 pm

Input values on AD(x)

2008-03-07T21:15:44+01:00

Once again...

Trying to get warnings on several voltage levels with this code. “robot_voltage” is called from MAIN by “GOSUB robot_voltage”

robot_voltage:' [10 x Value / 256 = Voltage]
DIM v AS BYTE
DIM n AS BYTE

A = AD(6)
IF A > 148 AND A <150> 146 AND A <= 148 THEN n = 2
IF A <146> 15, 148 --> 13, 146 --> 10. With this setting the led won’t blink at all. I tried other values as well, when I compare “A” with <25> 0 AND Rn <10> 10 AND Rn <= 20 THEN MUSIC “B”

RETURN

Sometimes RN won’t respond at all by this setting. Changing 10 to 20 and 20 to 30 will help sometimes, but not in all cases. I’ve experienced that 40 and 50 sometimes also do the job. I know the sensor readings can shift a bit when the battery is exhausting, but I also noticed this behavior when the battery is fully charged. So there seemed to be no relation between the inconsistent reading and the battery voltage.

From the tilt sensor I get the same inconsistent readings.

For me it looks like there no pattern in this behavior. Maybe it has to do with interference by other signals but often it’s a knowledge issue. Can someone help with this?

Gerry

Statistics: Posted by Gerry52 — Fri Mar 07, 2008 9:15 pm

Input values on AD(x)

2008-03-07T21:10:40+01:00

The message seemed to be ok evrey time, the code is messed up everytime. In the "post a reply" box the code seemed to be ok, in the preview it's messed up.

HELP!!!

Statistics: Posted by Gerry52 — Fri Mar 07, 2008 9:10 pm

Input values on AD(x)

2008-03-07T20:57:52+01:00

Sorry, Guess I'm not be able to post my code the right way...

Statistics: Posted by Gerry52 — Fri Mar 07, 2008 8:57 pm

Input values on AD(x)

2008-03-07T20:54:38+01:00

Trying to get warnings on several voltage levels with this code. “robot_voltage” is called from MAIN by “GOSUB robot_voltage”

robot_voltage:' [10 x Value / 256 = Voltage]
DIM v AS BYTE
DIM n AS BYTE

A = AD(6)
IF A > 148 AND A <150> 146 AND A <= 148 THEN n = 2
IF A <146> 15, 148 --> 13, 146 --> 10. With this setting the led won’t blink at all. I tried other values as well, when I compare “A” with <25> 0 AND Rn <10> 10 AND Rn <= 20 THEN MUSIC “B”

RETURN

Sometimes RN won’t respond at all by this setting. Changing 10 to 20 and 20 to 30 will help sometimes, but not in all cases. I’ve experienced that 40 and 50 sometimes also do the job. I know the sensor readings can shift a bit when the battery is exhausting, but I also noticed this behavior when the battery is fully charged. So there seemed to be no relation between the inconsistent reading and the battery voltage.

From the tilt sensor I get the same inconsistent readings.

For me it looks like there no pattern in this behavior. Maybe it has to do with interference by other signals but often it’s a knowledge issue. Can someone help with this?

Gerry

Statistics: Posted by Gerry52 — Fri Mar 07, 2008 8:54 pm

Input values on AD(x)

2008-03-07T20:50:47+01:00

Sorry again,

Guess I first have to find how to post a question you can read...

Gerry

Statistics: Posted by Gerry52 — Fri Mar 07, 2008 8:50 pm

Input values on AD(x)

2008-03-07T20:48:17+01:00

Statistics: Posted by Gerry52 — Fri Mar 07, 2008 8:48 pm

Input values on AD(x)

2008-03-07T20:41:24+01:00

Sorry,

Copied the code from robobasic and pasted it in robosavvy but it all seemed to be messed up. Will try it again.

On AD(6) are no wires connected, guess thats my battery voltage problem, should I connect the battery voltage to the AD(6) pins?

Gerry

Statistics: Posted by Gerry52 — Fri Mar 07, 2008 8:41 pm

Input values on AD(x)

2008-03-07T20:34:38+01:00

It would be easier to help if you posted the actual code you have a problem with.

Also what are the components you have wired to input AD6 ?

Statistics: Posted by i-Bot — Fri Mar 07, 2008 8:34 pm

Input values on AD(x)

2008-03-07T20:17:21+01:00

Hi,

Trying to get warnings on several voltage levels with this code. “robot_voltage” is called from MAIN by “GOSUB robot_voltage”

robot_voltage:' [10 x Value / 256 = Voltage]
DIM v AS BYTE
DIM n AS BYTE

A = AD(6)
IF A > 148 AND A <150> 146 AND A <148> 144 AND A <146> 15, 148 --> 13, 146 --> 10. With this setting the led won’t blink at all. I tried other values as well, when I compare “A” with <25> 0 AND Rn <10> 10 AND Rn <= 20 THEN MUSIC “B”

RETURN

Sometimes RN won’t respond at all by this setting. Changing 10 to 20 and 20 to 30 will help sometimes, but not in all cases. I’ve experienced that 40 and 50 sometimes also do the job. I know the sensor readings can shift a bit when the battery is exhausting or temperature, but I also noticed this behavior when the battery is fully charged. So there seemed to be no relation between the inconsistent readings and the battery voltage.

From the tilt sensor I get the same inconsistent readings.

For me it looks like there no pattern in this behavior. Maybe it has to do with interference by other signals but often it’s a knowledge issue. Need some help with this...

Gerry

Statistics: Posted by Gerry52 — Fri Mar 07, 2008 8:17 pm