70016 Parallax Inc, 70016 Datasheet - Page 47

• Manufacturer Part Number: 70016
• Description: TEXT INFRARED REMOTE FOR BOE-BOT
• Manufacturer: Parallax Inc

Specifications of 70016

• Accessory Type: Manual
• Product: Microcontroller Accessories
• Lead Free Status / RoHS Status: Contains lead / RoHS non-compliant
• For Use With/related Products: Boe-Bot®
• For Use With: 29122 - KIT PARTS IR REMOTE FOR BOE-BOT
• Lead Free Status / RoHS Status: Lead free / RoHS Compliant, Contains lead / RoHS non-compliant

If the
searches for a high pulse will keep testing for pulses and waiting for one that's longer
than 1000. Eventually, maybe 80 or so ms later, the loop will detect the resting state after
the next repeat of the IR message. Finally, at that point, it will move on to the
and
between servo pulses goes up to 90 ms because the
rest between messages, the servos won't work well at all.
The solution for this problem is to use
17. While
RCTIME
the resting state until after it has started, it will still be able to recognize it.
Example Program – 3BitRemoteBoeBot.bs2
This program makes the Boe-Bot respond when you press and hold a given digit key on
the remote. The directions for each key are shown in Figure 1-16. The 9 key does not
work right, but you will fix that in the Your Turn section. It's better to make sure the 1 - 8
keys work right before tackling the 9 key.
√
√
PULSOUT
PULSIN
only needs a falling edge. So, even if the program doesn't start monitoring for
Enter and run 3BitRemoteBoeBot.bs2.
Test the keys and have fun driving the Boe-Bot around for a while.
PULSIN
commands. This time delay causes a problem for the servos. If the time
command does not detect the rising edge of the resting state, the loop that
needs both a rising and falling edge to complete its time measurement,
RCTIME
Chapter 1: Infrared Remote Communication · Page 37
instead. Take a second look at Figure 1-
PULSIN
command can't catch the first
Figure 1-17
PULSIN vs.
RCTIME for
Detecting the
Resting State
Between
Messages
IF…THEN