Bob

Did you install the Teensy a second time and select the 1.8.8 directory?

On Monday, February 4, 2019, 12:12:03 PM CST, Bob Miller <bobrmiller@...> wrote:

Jack, can you suggest a reason I'm not seeing the Teensy, in the tools drop down in Arduino 1.8.8? I had this all sorted using 1.8.7
but switching to 1.8.8 it's not listed.

Thanks,

Bob -wb6kwt

All:
I realize most of you don't use CW, and while that's fine, I think you're missing out on a lot of fun. Anyway, one of the features JackAl provides is the ability to associated 3 externally-mounted NO SPST push button switches to any of the 50 pre-stored messages you may want to send. The messages that I use begin their definitions around line 588 in the JackAlV095.ino file. Feel free to edit these, but make sure you don't "overflow" the 27 character limit for each message.

I added these 3 switches as a result of my participation as a CW operator in club FD's over the years. We used a WinKeyer which had the same feature and it one reason my wrist could last through a contest. So, the switches are a good idea if you use CW and work a lot of contests. If you don't work CW, there's no reason to add the switches. But, assuming you want to use this feature, where do you put the switches?

If you opt to put them on the front or sides of the case, the ?BITX doesn't have enough mass to keep it from sliding around the table surface. A brick would solve that problem, as would any one of a dozen other "non-skid" solutions.

If you put the switches on the top of the case, that solves the sliding problem, but means you can't place anything on top of the case. That may or may not be an issue for you.

Most of the time, I don't use the switches at all...they are dormant except for contests. So, I think I'm going to mount my 3 CW switches in a very small plastic case and run a 4-conductor cable to a mating 4 conductor jack mounted on the back of the case. I'll make the cable long enough for the small case to sit near my keyer paddles, If you have your key or paddles anchored to a metal base, perhaps glueing a small magnet in the case and placing the case on your base would make sense...just a thought. The ability to place the case close to the paddles/key means minimal hand movement to send the pre-stored CW message(s) plus it will give me a little more flexibility as to where the ?BITX/JackAl sits because it no longer needs to be within easy arm's reach.

BTW, we have dedicated three pins for triggering the CW messages:

#define CWMESSAGEPIN1???????? 20?????? // These are the pin numbers tied to the external CW message switches
#define CWMESSAGEPIN2???????? 25
#define CWMESSAGEPIN3???????? 26

These are found around line 198 in the JackAl.h header file. If you are certain that you will never use them, you could use those three Teensy pins for your own experiments. If you're absolutely, positively, 100% sure you will never use them, then you can save a few bytes of memory and a couple of nanoseconds by commenting out the code block in loop() that reads them:

/*????????????????????? // ADD OPEN COMMENT CHARACTERS
? if (digitalRead(CWMESSAGEPIN1) == LOW) {?????? // Did the user press external CW switch 1?
??? SendCWMessage(cwSwitchIndex[0]);
? }
? if (digitalRead(CWMESSAGEPIN2) == LOW) {?????? // Did the user press external CW switch 2?
??? SendCWMessage(cwSwitchIndex[1]);
? }
? if (digitalRead(CWMESSAGEPIN3) == LOW) {?????? // Did the user press external CW switch 3?
??? SendCWMessage(cwSwitchIndex[2]);
? }
*/????????????????????? // ADD CLOSE COMMENT CHARACTERS

The if statement blocks above start around line 1085 in the JackAlV095.ino source code file.

Perhaps someone else has an even more elegant solution?

Jack, W8TEE

All:
I realize most of you don't use CW, and while that's fine, I think you're missing out on a lot of fun. Anyway, one of the features JackAl provides is the ability to associated 3 externally-mounted NO SPST push button switches to any of the 50 pre-stored messages you may want to send. The messages that I use begin their definitions around line 588 in the JackAlV095.ino file. Feel free to edit these, but make sure you don't "overflow" the 27 character limit for each message.

I added these 3 switches as a result of my participation as a CW operator in club FD's over the years. We used a WinKeyer which had the same feature and it one reason my wrist could last through a contest. So, the switches are a good idea if you use CW and work a lot of contests. If you don't work CW, there's no reason to add the switches. But, assuming you want to use this feature, where do you put the switches?

If you opt to put them on the front or sides of the case, the ?BITX doesn't have enough mass to keep it from sliding around the table surface. A brick would solve that problem, as would any one of a dozen other "non-skid" solutions.

If you put the switches on the top of the case, that solves the sliding problem, but means you can't place anything on top of the case. That may or may not be an issue for you.

Most of the time, I don't use the switches at all...they are dormant except for contests. So, I think I'm going to mount my 3 CW switches in a very small plastic case and run a 4-conductor cable to a mating 4 conductor jack mounted on the back of the case. I'll make the cable long enough for the small case to sit near my keyer paddles, If you have your key or paddles anchored to a metal base, perhaps glueing a small magnet in the case and placing the case on your base would make sense...just a thought. The ability to place the case close to the paddles/key means minimal hand movement to send the pre-stored CW message(s) plus it will give me a little more flexibility as to where the ?BITX/JackAl sits because it no longer needs to be within easy arm's reach.

BTW, we have dedicated three pins for triggering the CW messages:

#define CWMESSAGEPIN1???????? 20?????? // These are the pin numbers tied to the external CW message switches
#define CWMESSAGEPIN2???????? 25
#define CWMESSAGEPIN3???????? 26

These are found around line 198 in the JackAl.h header file. If you are certain that you will never use them, you could use those three Teensy pins for your own experiments. If you're absolutely, positively, 100% sure you will never use them, then you can save a few bytes of memory and a couple of nanoseconds by commenting out the code block in loop() that reads them:

/*????????????????????? // ADD OPEN COMMENT CHARACTERS
? if (digitalRead(CWMESSAGEPIN1) == LOW) {?????? // Did the user press external CW switch 1?
??? SendCWMessage(cwSwitchIndex[0]);
? }
? if (digitalRead(CWMESSAGEPIN2) == LOW) {?????? // Did the user press external CW switch 2?
??? SendCWMessage(cwSwitchIndex[1]);
? }
? if (digitalRead(CWMESSAGEPIN3) == LOW) {?????? // Did the user press external CW switch 3?
??? SendCWMessage(cwSwitchIndex[2]);
? }
*/????????????????????? // ADD CLOSE COMMENT CHARACTERS

The if statement blocks above start around line 1085 in the JackAlV095.ino source code file.

Perhaps someone else has an even more elegant solution?

Jack, W8TEE

James, Did you get your 1.8.8 issues worked out??
Remember, when you install IDE 1.8.8, you need to install Teensyduino too.? The way the instructions recommend you managing libs, you need to also install the custom + additional supporting libs also.
If you are still having issues, please send the error log.
Rgds,
Gary

James, Did you get your 1.8.8 issues worked out??
Remember, when you install IDE 1.8.8, you need to install Teensyduino too.? The way the instructions recommend you managing libs, you need to also install the custom + additional supporting libs also.
If you are still having issues, please send the error log.
Rgds,
Gary