¿ªÔÆÌåÓý

ctrl + shift + ? for shortcuts
© 2025 Groups.io

Re: Teensy

 

You still should see the Teensy directory off the hardware directory.

Jack, W8TEE

On Monday, February 4, 2019, 3:19:56 PM EST, PeteWK8S via Groups.Io <pmeier@...> wrote:


You may have to do a quick compile of any sketch and that will cause the Teensy app to launch then you can see the Teensy in the Tools,

Pete WK8S

On Feb 4, 2019, at 1:14 PM, Bob Miller <bobrmiller@...> wrote:

Okay, I just reinstalled Teensy and it still isn't showing up in the tools are of Ardunio.

Bob -wb6kwt

On 2/4/2019 10:15 AM, John Galway via Groups.Io wrote:
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


Pete Meier
pmeier at
Amateur Radio Callsign: WK8S
|| I never lose. If I don't win, I learn. -?unknown author ||


Re: Teensy

 

Bob:

Actually, that's a good thing, since it shouldn't show up in the Tools directory. If you installed it as I said on drive C:, this is what you should see:

C:\Arduino1.8.8\hardware\arduino
???????????????????????????????????????? \teensy
???????????????????????????????????????? \tools
???????????????????????????????????????? // some additional files

You should see the Teensy folder (in yellow). If you did not, then you did not install the Teensyduino correctly.

Jack, W8TEE


On Monday, February 4, 2019, 3:15:18 PM EST, Bob Miller <bobrmiller@...> wrote:


Okay, I just reinstalled Teensy and it still isn't showing up in the tools are of Ardunio.

Bob -wb6kwt

On 2/4/2019 10:15 AM, John Galway via Groups.Io wrote:
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


Re: Teensy

PeteWK8S
 

¿ªÔÆÌåÓý

You may have to do a quick compile of any sketch and that will cause the Teensy app to launch then you can see the Teensy in the Tools,

Pete WK8S

On Feb 4, 2019, at 1:14 PM, Bob Miller <bobrmiller@...> wrote:

Okay, I just reinstalled Teensy and it still isn't showing up in the tools are of Ardunio.

Bob -wb6kwt

On 2/4/2019 10:15 AM, John Galway via Groups.Io wrote:
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


Pete Meier
pmeier at
Amateur Radio Callsign: WK8S
|| I never lose. If I don't win, I learn. -?unknown author ||


Re: Teensy

 

¿ªÔÆÌåÓý

Okay, I just reinstalled Teensy and it still isn't showing up in the tools are of Ardunio.

Bob -wb6kwt

On 2/4/2019 10:15 AM, John Galway via Groups.Io wrote:

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


Re: CW Operators: Something to think about before you drill your case

 

There are, and you can see these in the JackAl.h header file, around line 86:

#define FREEUSERPIN1?????????????? 6??????????????????????????????????? //=====================================================
#define FREEUSERPIN2?????????????? 8??????????????????????????????????? // Free Pins for Users. Probably use new symbolic names
#define FREEUSERPIN3????????????? 10??????????????????????????????????? //=====================================================
#define FREEUSERPIN4????????????? 15
#define FREEUSERPIN5????????????? 17
#define FREEUSERPIN6????????????? 20
#define FREEUSERPIN7????????????? 25
#define FREEUSERPIN8????????????? 26
#define FREEUSERPIN9????????????? 28
#define FREEUSERPIN10???????????? 39
#define FREEUSERPIN11??????????? A10? (from bottom of board)
#define FREEUSERPIN12??????????? A11


Jack, W8TEE

On Monday, February 4, 2019, 12:51:01 PM EST, James Zdunic <james_zdunic@...> wrote:


Jack,

This seems as good a time as any to ask...

Are there any unused cpu pins available for experimenting other that the 3 CW switch pins you mentioned?

Jim ?KM4TXR

On Feb 4, 2019, at 11:58 AM, jjpurdum via Groups.Io <jjpurdum@...> wrote:

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


Re: Teensy

 

Yes, I believe I did but I'll reinstall to make sure.

Thanks

Bob -wb6kwt


Re: CW Operators: Something to think about before you drill your case

eyelessmisfit
 

¿ªÔÆÌåÓý

Jack,
I will definately want to add!
(Though I'm not sure of the ethics of canned messages for straight key night!)
Lol,
Thanks much,
Ron W0QVJ



Sent from my Galaxy Tab? E

-------- Original message --------
From: "jjpurdum via Groups.Io" <jjpurdum@...>
Date: 2/4/19 9:58 AM (GMT-07:00)
Subject: [JackAl] CW Operators: Something to think about before you drill your case

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


Re: Teensy

 

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


Teensy

 

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


Can't change file error

 

All:

When you compile a program with the IDE, there are a lot of intermediate, or temporary, files (e.g., *.o) created during the process. After these are created, the linker pass gathers these files together and makes the executable file which is then uploaded to your Teensy via the USB cable. If you click the "compile only" icon (the check mark under the File menu option of the IDE) and navigate to your temporary file directory (you can determine the location by setting the File --> Preferences compile checkbox to Verbose), you can see these temporary files. If you click the compile/upload icon (i.e., the "right-arrow" icon), all of these temporary files are erased and you would not be able to see these temp files.

All of this can get screwed up if you don't have sufficient rights to write/erase temporary files. If you google "setting admin rights", you should find instructions for your op system. For Win 10, they are:

Change a user account type on User Accounts
  1. Use the Windows key + R keyboard shortcut to open the run command, type netplwiz, and press Enter.
  2. Select the user account and click the Properties button.
  3. Click the Group Membership tab.
  4. Choose the account type: Standard User or Administrator. ...
  5. Click OK.
Unless you have a good reason otherwise, you should set yourself with Admin privileges.

Jack, W8TEE


Re: CW Operators: Something to think about before you drill your case

James Zdunic
 

¿ªÔÆÌåÓý

Jack,

This seems as good a time as any to ask...

Are there any unused cpu pins available for experimenting other that the 3 CW switch pins you mentioned?

Jim ?KM4TXR

On Feb 4, 2019, at 11:58 AM, jjpurdum via Groups.Io <jjpurdum@...> wrote:

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


Re: CW Operators: Something to think about before you drill your case

 

Define a variable and then set it true or false.? Then put the ifdefine around the code so it is viable or not based on the define.

John KH6JTE

On Monday, February 4, 2019, 10:58:55 AM CST, jjpurdum via Groups.Io <jjpurdum@...> wrote:


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


CW Operators: Something to think about before you drill your case

 

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


Re: Arduino 1.1.8

 

If you are building the AA then you pick the Arduino Mega 2560.? If you are doing the JackAl then teensy 3.6? Also we are on either 1.8.7 or 1.8.8 version of Arduino

John? KH6JTE

On Sunday, February 3, 2019, 6:39:30 PM CST, Bob Miller <bobrmiller@...> wrote:


I was using Arduino 1.1.7 but notice Jack said go with 1.1.8 because he isn't sure the updates will work with earlier versions. I had a good compile with 1.1.7 but guess I've had a loss of memory, in tools which board do I select?

Bob.


Arduino 1.1.8

 

I was using Arduino 1.1.7 but notice Jack said go with 1.1.8 because he isn't sure the updates will work with earlier versions. I had a good compile with 1.1.7 but guess I've had a loss of memory, in tools which board do I select?

Bob.


Re: I totally Suck At compiling

 

James

If you are using the install from the app store you will have problems.? You need to download the .zip file and unzip it into the directory as laid out in the install directions.? There are updated version on the web site that clear up several install problems that have been encountered.? Also to let you know there is also an updated version of the software.

John KH6JTE

On Sunday, February 3, 2019, 12:06:40 PM CST, James Zdunic <james_zdunic@...> wrote:


Hi Gary,

Thanks for following up. ?I have 1.8.7 installed and compiling with no errors. ?

However I haven¡¯t been able to get 1.8.8 to work yet. ?I¡¯m going to delete the 1.8.8 one more time and try re-doing it. ?If that doesn¡¯t work I¡¯ll send you the error log. ?Thanks for your support.

Jim KM4TXR

On Feb 3, 2019, at 12:49 PM, Gary Anderson <gary.ag5tx@...> wrote:

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


Re: I totally Suck At compiling

James Zdunic
 

¿ªÔÆÌåÓý

Hi Gary,

Thanks for following up. ?I have 1.8.7 installed and compiling with no errors. ?

However I haven¡¯t been able to get 1.8.8 to work yet. ?I¡¯m going to delete the 1.8.8 one more time and try re-doing it. ?If that doesn¡¯t work I¡¯ll send you the error log. ?Thanks for your support.

Jim KM4TXR

On Feb 3, 2019, at 12:49 PM, Gary Anderson <gary.ag5tx@...> wrote:

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


Re: I totally Suck At compiling

 

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


Re: OpenAudio_ArduinoLibrary and manual updates

 

At this stage, I would not suggest printing out the manual. Simply load and read the sections you need as you need them until things stabilize.

Jack, W8TEE



On Saturday, February 2, 2019, 4:36:05 PM EST, Vince Loschiavo <vince320@...> wrote:


Jack,
Quick question re:
Library install instructions
It said:
#include <OpenAudio_ArduinoLibrary.h> //https:/github.com/chipaudette/OpenAudio_ArduinoLibrary
but there is a lib on your site...I didn't have issues compiling using the one from github..
should i load the one from the site??
i'm using arduino 1.8.8.
still gathering parts for the hardware..

Regarding Manual updates...It would be nice to have the revision marks next to the lines that have been updated from the previous version ...saves alot of paper..


Vince
N2AIE


Re: OpenAudio_ArduinoLibrary and manual updates

 

Vince:

If you look in the latest documentation manuals, or in the JackAl.h header file, you will see that we have changed the list of the #include files. One January 20 we changed the Open Audio library because of duplicate definition errors. You need to download and install our version from our web site.

Jack, W8TEE

On Saturday, February 2, 2019, 4:55:09 PM EST, John Galway via Groups.Io <jjgalway@...> wrote:


Vince You should use the on the JackAl site.? remember to delete the old library if it is in the directory.? If you don't you may get errors compiling.? Done that got the T-shirt.

John? KH6JTE

On Saturday, February 2, 2019, 3:36:05 PM CST, Vince Loschiavo <vince320@...> wrote:


Jack,
Quick question re:
Library install instructions
It said:
#include <OpenAudio_ArduinoLibrary.h> //https:/github.com/chipaudette/OpenAudio_ArduinoLibrary
but there is a lib on your site...I didn't have issues compiling using the one from github..
should i load the one from the site??
i'm using arduino 1.8.8.
still gathering parts for the hardware..

Regarding Manual updates...It would be nice to have the revision marks next to the lines that have been updated from the previous version ...saves alot of paper..


Vince
N2AIE