First crack at adding keyer code. It is sending a constant signal (key down) as soon as the board is powered and boots up. Does not send a constant signal without board power, so I think (hope) this is a code issue, not a hardware issue.
Unless board power alone is causing the transistor to switch. But I feel like the delay from board power to board boot before key down indicates that it isn't board power alone.
First crack at adding keyer code. It is sending a constant signal (key down) as soon as the board is powered and boots up. Does not send a constant signal without board power, so I *think* (hope) this is a code issue, not a hardware issue.
Unless board power alone is causing the transistor to switch. But I feel like the delay from board power to board boot before key down indicates that it isn't board power alone.
Swapping these shows that keyer is on all the time...
const int keyer = LED_BUILTIN;//32; //LED_BUILTIN for on-board (dev);//26 for LED; //32 for transmitter keyer
const int blinker = 32;//LED_BUILTIN;
..and I can hear code from the transmitter!
Swapping these shows that `keyer` is on all the time...
```
const int keyer = LED_BUILTIN;//32; //LED_BUILTIN for on-board (dev);//26 for LED; //32 for transmitter keyer
const int blinker = 32;//LED_BUILTIN;
```
..and I can hear code from the transmitter!
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Closes #43.
Follows #24.
First crack at adding keyer code. It is sending a constant signal (key down) as soon as the board is powered and boots up. Does not send a constant signal without board power, so I think (hope) this is a code issue, not a hardware issue.
Unless board power alone is causing the transistor to switch. But I feel like the delay from board power to board boot before key down indicates that it isn't board power alone.
Swapping these shows that
keyeris on all the time.....and I can hear code from the transmitter!