Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
|
wiki:opconfig:tabs:lightsio [2017/07/24 22:35] opadmin [Lights and General Input/Output] |
wiki:opconfig:tabs:lightsio [2019/02/21 03:51] opadmin [General Purpose Input/Output Ports A & B] |
||
|---|---|---|---|
| Line 47: | Line 47: | ||
| Check this box to blink every light (L1, L2, BRK, MG, APPLE hit LEDs, and the onboard red and green LEDs) when the TCB detects a loss of radio signal. If you uncheck this option, the onboard red and green LEDs will still blink on loss of radio signal, but the others will not. | Check this box to blink every light (L1, L2, BRK, MG, APPLE hit LEDs, and the onboard red and green LEDs) when the TCB detects a loss of radio signal. If you uncheck this option, the onboard red and green LEDs will still blink on loss of radio signal, but the others will not. | ||
| - | **Note:** the TCB may not be able to detect a loss of signal in all cases. If your receiver is set to continue transmitting data even when the signal is lost (" | + | **Note:** the TCB may not be able to detect a loss of signal in all cases. If your receiver is set to continue transmitting data even when the signal is lost (" |
| + | == Blink Apple when Cannon Reloaded == | ||
| + | If checked the LEDs in the IR Appple will blink briefly after the cannon reload time has expired, this can be useful in IR battle to let you know the instant when you are able to fire once more. The cannon reload time is dependent on your selected weight class, discussed on the [[wiki: | ||
| ===== High Intensity Flash Unit ===== | ===== High Intensity Flash Unit ===== | ||
| Line 83: | Line 85: | ||
| ===== General Purpose Input/ | ===== General Purpose Input/ | ||
| - | {{ wiki: | + | {{ wiki: |
| The A & B ports are general purpose, logic-level ports that can set to input or output depending on your needs. | The A & B ports are general purpose, logic-level ports that can set to input or output depending on your needs. | ||
| Line 105: | Line 107: | ||
| - External Output A/B - Turn Off\\ | - External Output A/B - Turn Off\\ | ||
| - External Output A/B - Pulse\\ | - External Output A/B - Pulse\\ | ||
| + | - External Output A/B - Blink\\ | ||
| You can then assign a trigger to these functions and in so doing control the output of these ports. The first three functions are self-explanatory, | You can then assign a trigger to these functions and in so doing control the output of these ports. The first three functions are self-explanatory, | ||
| - | What you do with these outputs is up to you, but remember these are logic-level outputs! That means they can //not source// enough current to actually power something, not even an LED! Instead consider | + | The fifth function will cause the output |
| - | If you want to use these outputs to turn on a lamp, or a relay, or some other object that draws current, you will need to use a driver circuit. You can find a schematic for a MOSFET driver adapter on the [[wiki: | + | What you do with these outputs is up to you, but remember these are logic-level outputs! That means they can not source enough current to actually power something, not even most LEDs! Instead consider the outputs like signals, and the signals can tell some other more powerful circuit to do something, or they could be used as direct inputs into another microcontroller (such as another Arduino). (If you know what you are doing, and you are certain your LEDs do not draw more than 20mA, you can connect them directly to the port). |
| + | |||
| + | If you want to use these outputs to turn on a lamp, or a relay, or some other object that draws more than 20mA of current, you will need to use a driver circuit. You can find a schematic for a MOSFET driver adapter on the [[wiki: | ||