Date   

First time updating of WSJT-X & GridTracker

Jay Lijoi
 

Good evening,

I have been running WSJT-X and GridTracker on a Window 10 computer for a number of years. when I updated on that computer all I needed to do was to run the install executable and all of my other data was retained, including my LOTW info.
 
Several months ago I switched to Raspberry PI Linux and I would like to upgrade these programs.
 
Before I screw it all up:
  • What do I need to do to upgrade to the latest versions?
  • Do I have to enter all of my info again, i.e. LOTW info?
  • Do I have to do a complete install from scratch as though I was using for the first time?
  • ETC.....
 
 
Any advice is welcome,
Jay WB2QQJ
 


Re: qsstv - Anyone have it running on Pi 4?

David Ranch
 


Hello Larrie,

I installed qsstv 9.4.4, building from source as directed by the qsstv web site.  The program runs, but is extremely slow and will not connect to the radio, but gives no error messages.

Hmmm.. that doesn't sound right.  The GUI should operate at a reasonable speed as a Rpi4 isn't really that slow of a device.  I will say I don't run Qsstv on an Rpi but I do use it on a X86 machine w/o any issues.


 I have it set for a slow computer and limited images displayed to only 1 (get same issue when program initially started with it default settings).  What happens is that it takes about 2 minutes to boot and whenever you select an option it takes 1 min to respond

When you say "boot", do you mean the time to start the Qsstv program after you booted your Rpi and logged into it?  If so, there is something seriously wrong.  A few questions:

   - Do you see slow loading times on other programs as well? 
   - What are you using for your storage? 
   - An SD card?  What is the Make, Model, size, and AGE of that card?


After a slow loading time event, open a terminal and run the "dmesg" command.  At the bottom of the output, are there any specific errors that you think are related to the slow loading times?


This for all operations within the program from selecting menu items to entering data (if type in a number, it takes a minute before the number appears in the entry box).  Even shutting down the program (File - exit - confirm quit) takes several minutes to complete.

Very surprising.  My first guess would be a DNS issue.  Can you web browse from this system w/o any issues?


 I am running a Raspberry Pi 4 with 4 Gb ram and the radio is an Icom IC-7000.  Any thoughts as to what the issue may be?  When running the "make" command in building the program I observed took 15-20 min to complete, which seemed much longer than any other program that I have installed.  Is this program too much for the Pi?  I did have qsstv 9.2.X running earlier.  It was better but still slow to respond. 

Building things on the Raspberry Pi will be slower than say an X86 system.  In my Centos documentation, I captured:

   #  Takes 4m7sec on a i5-2430-2.4Ghz 2 physical core laptop with 4GB RAM and a SSD HD


I have the same program installed on a machine running Ubuntu 20.04 and it works fine.

Is that machine also a Raspberry Pi?

--David
KI6ZHD


qsstv - Anyone have it running on Pi 4?

Larrie
 

Hi

I installed qsstv 9.4.4, building from source as directed by the qsstv web site.  The program runs, but is extremely slow and will not connect to the radio, but gives no error messages.  I have it set for a slow computer and limited images displayed to only 1 (get same issue when program initially started with it default settings).  What happens is that it takes about 2 minutes to boot and whenever you select an option it takes 1 min to respond.  This for all operations within the program from selecting menu items to entering data (if type in a number, it takes a minute before the number appears in the entry box).  Even shutting down the program (File - exit - confirm quit) takes several minutes to complete.  I am running a Raspberry Pi 4 with 4 Gb ram and the radio is an Icom IC-7000.  Any thoughts as to what the issue may be?  When running the "make" command in building the program I observed took 15-20 min to complete, which seemed much longer than any other program that I have installed.  Is this program too much for the Pi?  I did have qsstv 9.2.X running earlier.  It was better but still slow to respond.  

I have the same program installed on a machine running Ubuntu 20.04 and it works fine.
--
Larrie
AF7NU


Re: Pi 4 Ubuntu 20.20 FLDIGI Alpha build problems

Eric
 

I *THINK* these two options are valid only for x86 and x86 compatible processors....which is definitely not a Pi.

If the above is correct, then it sounds like the build process isn't being told (or "realizing") that the build is happening on the RPi

I did notice some stuff on the sourceforge page about building on a RPi at  https://sourceforge.net/p/fldigi/wiki/debian_howto/
It says debian in the link, but it talks about Ubuntu in there as well.

I'm just making some SWAGS as to what might be happening, so all of this info comes with the "if it breaks, you get to keep it" warranty! :-)   

Eric
WB6TIX

On Sun, Nov 8, 2020 at 10:22 AM Bill Studley <aa1oc@...> wrote:

[Edited Message Follows]

I'm trying to build the latest FLDIGI alpha release and I get build errors around the optimizations for the PI 4.  I can build the release without the optimizations but I wonder if I'm compromising performance if I do not include the compile optimizations.
Do I assume that the Gcc compiler included with the release of Ubuntu 20.20 has the optimizations include, or do I need to track down missing libraries and or use a different compiler?
The error that I'm getting is:
g++: error: unrecognized command-line option ‘-mno-3dnow’
g++: error: unrecognized command-line option ‘-mfpmath=sse’
From what I've been able to track down that these are errors that are normally seen by cross compilers. I've trying to build natively on the PI, so now I confused as to my path forward.
Any help or suggestions would greatly be appreciated.

Correction, the release that I'm using is the 20.10 release of Ubuntu.
--  Bill, AA1OC


Pi 4 Ubuntu 20.20 FLDIGI Alpha build problems

Bill Studley
 
Edited

I'm trying to build the latest FLDIGI alpha release and I get build errors around the optimizations for the PI 4.  I can build the release without the optimizations but I wonder if I'm compromising performance if I do not include the compile optimizations.
Do I assume that the Gcc compiler included with the release of Ubuntu 20.20 has the optimizations include, or do I need to track down missing libraries and or use a different compiler?
The error that I'm getting is:
g++: error: unrecognized command-line option ‘-mno-3dnow’
g++: error: unrecognized command-line option ‘-mfpmath=sse’
From what I've been able to track down that these are errors that are normally seen by cross compilers. I've trying to build natively on the PI, so now I confused as to my path forward.
Any help or suggestions would greatly be appreciated.

Correction, the release that I'm using is the 20.10 release of Ubuntu.
--  Bill, AA1OC


Re: JTDX screen size too large - how to correct? #jtdx #pi

Alf Blomqvist
 

Good Morning and tnx fer advice,

I finally change config.txt to force Hdmi with nano.

I found Raspberry Pi resolution settings in Preferences.

So I solved the issue.

73 Alf
OH6IH



Skickat från min Samsung Galaxy-smartphone.


-------- Originalmeddelande --------
Från: David Ranch <rpi4hamradio-groupsio@...>
Datum: 03-11-2020 18:27 (GMT+02:00)
Till: RaspberryPi-4-HamRadio@groups.io
Ämne: Re: [RaspberryPi-4-HamRadio] JTDX screen size too large - how to correct? #jtdx #pi


Hello Alf,

One thing you can try is to force the HDMI port always on.  To do this, edit the /boot/config.txt and enable the following feature:

   hdmi_force_hotplug=1

Save the file and reboot.  Does that help?  If not, I would then research how to force the desired screen resolution that your current monitor supports and also put that into the config.txt file.

Ultimately, there is probably a more elegant way to achieve what you're looking for without forcing the HDMI port to be on and maybe someone on the list can offer that up.

--David
KI6ZHD


On 11/03/2020 07:31 AM, Alf Blomqvist wrote:
Hi,

I got problems when I set up my remote station headless.

With a monitor connected at the remote qth there is no problems with the size of JTDX main screen.

I have tried both Raspberry Pi 3B and Raspberry Pi 4B with same problem - the screen is too large and I'm not able to make the text on the screen smaller - I cannot press ok on setting screen!!

I don't no if this is a Raspberry Pi problem or a JTDX problem.

73 Alf
OH6IH


Re: JTDX screen size too large - how to correct? #jtdx #pi

Alf Blomqvist
 

Good Morning !

Now I have got my size issue solved.

I found Raspbery Pi settings for resolution and now I may handle the size of screens.

Thank you for all advices!

73 Alf
OH6IH



Skickat från min Samsung Galaxy-smartphone.


-------- Originalmeddelande --------
Från: N5XMT <dacooley@...>
Datum: 03-11-2020 21:55 (GMT+02:00)
Till: raspberrypi-4-hamradio@groups.io
Ämne: Re: [RaspberryPi-4-HamRadio] JTDX screen size too large - how to correct? #jtdx #pi

Put sudo in front of the command

On Nov 3, 2020, at 09:30, Alf Blomqvist <oh6ih@...> wrote:
Hi David 

tnx fer advice.

An other problem is that I don't have permission to change the file you mention.

So how do I get permission?

73 Alf
OH6IH



Skickat från min Samsung Galaxy-smartphone.


-------- Originalmeddelande --------
Från: David Ranch <rpi4hamradio-groupsio@...>
Datum: 03-11-2020 18:27 (GMT+02:00)
Till: RaspberryPi-4-HamRadio@groups.io
Ämne: Re: [RaspberryPi-4-HamRadio] JTDX screen size too large - how to correct? #jtdx #pi


Hello Alf,

One thing you can try is to force the HDMI port always on.  To do this, edit the /boot/config.txt and enable the following feature:

   hdmi_force_hotplug=1

Save the file and reboot.  Does that help?  If not, I would then research how to force the desired screen resolution that your current monitor supports and also put that into the config.txt file.

Ultimately, there is probably a more elegant way to achieve what you're looking for without forcing the HDMI port to be on and maybe someone on the list can offer that up.

--David
KI6ZHD


On 11/03/2020 07:31 AM, Alf Blomqvist wrote:
Hi,

I got problems when I set up my remote station headless.

With a monitor connected at the remote qth there is no problems with the size of JTDX main screen.

I have tried both Raspberry Pi 3B and Raspberry Pi 4B with same problem - the screen is too large and I'm not able to make the text on the screen smaller - I cannot press ok on setting screen!!

I don't no if this is a Raspberry Pi problem or a JTDX problem.

73 Alf
OH6IH


Re: JTDX screen size too large - how to correct? #jtdx #pi

N5XMT
 

Put sudo in front of the command

On Nov 3, 2020, at 09:30, Alf Blomqvist <oh6ih@...> wrote:
Hi David 

tnx fer advice.

An other problem is that I don't have permission to change the file you mention.

So how do I get permission?

73 Alf
OH6IH



Skickat från min Samsung Galaxy-smartphone.


-------- Originalmeddelande --------
Från: David Ranch <rpi4hamradio-groupsio@...>
Datum: 03-11-2020 18:27 (GMT+02:00)
Till: RaspberryPi-4-HamRadio@groups.io
Ämne: Re: [RaspberryPi-4-HamRadio] JTDX screen size too large - how to correct? #jtdx #pi


Hello Alf,

One thing you can try is to force the HDMI port always on.  To do this, edit the /boot/config.txt and enable the following feature:

   hdmi_force_hotplug=1

Save the file and reboot.  Does that help?  If not, I would then research how to force the desired screen resolution that your current monitor supports and also put that into the config.txt file.

Ultimately, there is probably a more elegant way to achieve what you're looking for without forcing the HDMI port to be on and maybe someone on the list can offer that up.

--David
KI6ZHD


On 11/03/2020 07:31 AM, Alf Blomqvist wrote:
Hi,

I got problems when I set up my remote station headless.

With a monitor connected at the remote qth there is no problems with the size of JTDX main screen.

I have tried both Raspberry Pi 3B and Raspberry Pi 4B with same problem - the screen is too large and I'm not able to make the text on the screen smaller - I cannot press ok on setting screen!!

I don't no if this is a Raspberry Pi problem or a JTDX problem.

73 Alf
OH6IH


Re: JTDX screen size too large - how to correct? #jtdx #pi

Fred Hillhouse
 

There are settings for both.

 

VNC Viewer:

Go to Properties (gear icon) and then the Scaling section.

 

Raspberry Pi:

Go to Preferences, Display Settings. Select your Default Monitor. I use 1920x1080. You may have to reboot.

 

Fred N7FMH

 

 

 

From: RaspberryPi-4-HamRadio@groups.io [mailto:RaspberryPi-4-HamRadio@groups.io] On Behalf Of Alf Blomqvist
Sent: Tuesday, November 03, 2020 12:50 PM
To: RaspberryPi-4-HamRadio@groups.io
Subject: Re: [RaspberryPi-4-HamRadio] JTDX screen size too large - how to correct? #jtdx #pi

 

Hi Fred and tnx fer the answer!

I also use VNCviewer.

I understand you talking of VNCviewer settings?

73 Alf

OH6IH

On 03/11/2020 19:43, Fred Hillhouse wrote:

I use VNC Viewer for headless operation. In it, I set the scaling to Scale to fit window”. Go to Properties (gear icon) and then the Scaling section.

 

In the RPi, go to Preferences, Display Settings. Select your Default Monitor. I use 1920x1080. You may have to reboot.

 

On my 4:3 monitor, I can see the whole 1920x1080 display regardless of how large the window is.

 

Fred N7FMH

 

 

From: RaspberryPi-4-HamRadio@groups.io [mailto:RaspberryPi-4-HamRadio@groups.io] On Behalf Of Alf Blomqvist
Sent: Tuesday, November 03, 2020 10:32 AM
To: RaspberryPi-4-HamRadio@groups.io
Subject: [RaspberryPi-4-HamRadio] JTDX screen size too large - how to correct? #jtdx #pi

 

Hi,

I got problems when I set up my remote station headless.

With a monitor connected at the remote qth there is no problems with the size of JTDX main screen.

I have tried both Raspberry Pi 3B and Raspberry Pi 4B with same problem - the screen is too large and I'm not able to make the text on the screen smaller - I cannot press ok on setting screen!!

I don't no if this is a Raspberry Pi problem or a JTDX problem.

73 Alf
OH6IH

 


Avast logo

This email has been checked for viruses by Avast antivirus software.
www.avast.com




Re: JTDX screen size too large - how to correct? #jtdx #pi

 

Put sudo in front of the editor command. 


On Tue, Nov 3, 2020, 09:30 Alf Blomqvist <oh6ih@...> wrote:
Hi David 

tnx fer advice.

An other problem is that I don't have permission to change the file you mention.

So how do I get permission?

73 Alf
OH6IH



Skickat från min Samsung Galaxy-smartphone.


-------- Originalmeddelande --------
Från: David Ranch <rpi4hamradio-groupsio@...>
Datum: 03-11-2020 18:27 (GMT+02:00)
Ämne: Re: [RaspberryPi-4-HamRadio] JTDX screen size too large - how to correct? #jtdx #pi


Hello Alf,

One thing you can try is to force the HDMI port always on.  To do this, edit the /boot/config.txt and enable the following feature:

   hdmi_force_hotplug=1

Save the file and reboot.  Does that help?  If not, I would then research how to force the desired screen resolution that your current monitor supports and also put that into the config.txt file.

Ultimately, there is probably a more elegant way to achieve what you're looking for without forcing the HDMI port to be on and maybe someone on the list can offer that up.

--David
KI6ZHD


On 11/03/2020 07:31 AM, Alf Blomqvist wrote:
Hi,

I got problems when I set up my remote station headless.

With a monitor connected at the remote qth there is no problems with the size of JTDX main screen.

I have tried both Raspberry Pi 3B and Raspberry Pi 4B with same problem - the screen is too large and I'm not able to make the text on the screen smaller - I cannot press ok on setting screen!!

I don't no if this is a Raspberry Pi problem or a JTDX problem.

73 Alf
OH6IH


Re: JTDX screen size too large - how to correct? #jtdx #pi

Mark Griffith
 

Use raspi-config from the command line to set the resolution. 

Mark 
KD0QYN 


On Tue, Nov 3, 2020 at 11:50 AM, Alf Blomqvist
<oh6ih@...> wrote:

Hi Fred and tnx fer the answer!

I also use VNCviewer.

I understand you talking of VNCviewer settings?

73 Alf

OH6IH

On 03/11/2020 19:43, Fred Hillhouse wrote:

I use VNC Viewer for headless operation. In it, I set the scaling to Scale to fit window”. Go to Properties (gear icon) and then the Scaling section.

 

In the RPi, go to Preferences, Display Settings. Select your Default Monitor. I use 1920x1080. You may have to reboot.

 

On my 4:3 monitor, I can see the whole 1920x1080 display regardless of how large the window is.

 

Fred N7FMH

 

 

From: RaspberryPi-4-HamRadio@groups.io [mailto:RaspberryPi-4-HamRadio@groups.io] On Behalf Of Alf Blomqvist
Sent: Tuesday, November 03, 2020 10:32 AM
To: RaspberryPi-4-HamRadio@groups.io
Subject: [RaspberryPi-4-HamRadio] JTDX screen size too large - how to correct? #jtdx #pi

 

Hi,

I got problems when I set up my remote station headless.

With a monitor connected at the remote qth there is no problems with the size of JTDX main screen.

I have tried both Raspberry Pi 3B and Raspberry Pi 4B with same problem - the screen is too large and I'm not able to make the text on the screen smaller - I cannot press ok on setting screen!!

I don't no if this is a Raspberry Pi problem or a JTDX problem.

73 Alf
OH6IH




Avast logo

This email has been checked for viruses by Avast antivirus software.
www.avast.com



Re: JTDX screen size too large - how to correct? #jtdx #pi

Alf Blomqvist
 

Hi Fred and tnx fer the answer!

I also use VNCviewer.

I understand you talking of VNCviewer settings?

73 Alf

OH6IH

On 03/11/2020 19:43, Fred Hillhouse wrote:

I use VNC Viewer for headless operation. In it, I set the scaling to Scale to fit window”. Go to Properties (gear icon) and then the Scaling section.

 

In the RPi, go to Preferences, Display Settings. Select your Default Monitor. I use 1920x1080. You may have to reboot.

 

On my 4:3 monitor, I can see the whole 1920x1080 display regardless of how large the window is.

 

Fred N7FMH

 

 

From: RaspberryPi-4-HamRadio@groups.io [mailto:RaspberryPi-4-HamRadio@groups.io] On Behalf Of Alf Blomqvist
Sent: Tuesday, November 03, 2020 10:32 AM
To: RaspberryPi-4-HamRadio@groups.io
Subject: [RaspberryPi-4-HamRadio] JTDX screen size too large - how to correct? #jtdx #pi

 

Hi,

I got problems when I set up my remote station headless.

With a monitor connected at the remote qth there is no problems with the size of JTDX main screen.

I have tried both Raspberry Pi 3B and Raspberry Pi 4B with same problem - the screen is too large and I'm not able to make the text on the screen smaller - I cannot press ok on setting screen!!

I don't no if this is a Raspberry Pi problem or a JTDX problem.

73 Alf
OH6IH




Avast logo

This email has been checked for viruses by Avast antivirus software.
www.avast.com



Re: JTDX screen size too large - how to correct? #jtdx #pi

Fred Hillhouse
 

I use VNC Viewer for headless operation. In it, I set the scaling to Scale to fit window”. Go to Properties (gear icon) and then the Scaling section.

 

In the RPi, go to Preferences, Display Settings. Select your Default Monitor. I use 1920x1080. You may have to reboot.

 

On my 4:3 monitor, I can see the whole 1920x1080 display regardless of how large the window is.

 

Fred N7FMH

 

 

From: RaspberryPi-4-HamRadio@groups.io [mailto:RaspberryPi-4-HamRadio@groups.io] On Behalf Of Alf Blomqvist
Sent: Tuesday, November 03, 2020 10:32 AM
To: RaspberryPi-4-HamRadio@groups.io
Subject: [RaspberryPi-4-HamRadio] JTDX screen size too large - how to correct? #jtdx #pi

 

Hi,

I got problems when I set up my remote station headless.

With a monitor connected at the remote qth there is no problems with the size of JTDX main screen.

I have tried both Raspberry Pi 3B and Raspberry Pi 4B with same problem - the screen is too large and I'm not able to make the text on the screen smaller - I cannot press ok on setting screen!!

I don't no if this is a Raspberry Pi problem or a JTDX problem.

73 Alf
OH6IH




Avast logo

This email has been checked for viruses by Avast antivirus software.
www.avast.com



Re: JTDX screen size too large - how to correct? #jtdx #pi

Alf Blomqvist
 

Hi David 

tnx fer advice.

An other problem is that I don't have permission to change the file you mention.

So how do I get permission?

73 Alf
OH6IH



Skickat från min Samsung Galaxy-smartphone.


-------- Originalmeddelande --------
Från: David Ranch <rpi4hamradio-groupsio@...>
Datum: 03-11-2020 18:27 (GMT+02:00)
Till: RaspberryPi-4-HamRadio@groups.io
Ämne: Re: [RaspberryPi-4-HamRadio] JTDX screen size too large - how to correct? #jtdx #pi


Hello Alf,

One thing you can try is to force the HDMI port always on.  To do this, edit the /boot/config.txt and enable the following feature:

   hdmi_force_hotplug=1

Save the file and reboot.  Does that help?  If not, I would then research how to force the desired screen resolution that your current monitor supports and also put that into the config.txt file.

Ultimately, there is probably a more elegant way to achieve what you're looking for without forcing the HDMI port to be on and maybe someone on the list can offer that up.

--David
KI6ZHD


On 11/03/2020 07:31 AM, Alf Blomqvist wrote:
Hi,

I got problems when I set up my remote station headless.

With a monitor connected at the remote qth there is no problems with the size of JTDX main screen.

I have tried both Raspberry Pi 3B and Raspberry Pi 4B with same problem - the screen is too large and I'm not able to make the text on the screen smaller - I cannot press ok on setting screen!!

I don't no if this is a Raspberry Pi problem or a JTDX problem.

73 Alf
OH6IH


Re: JTDX screen size too large - how to correct? #jtdx #pi

David Ranch
 


Hello Alf,

One thing you can try is to force the HDMI port always on.  To do this, edit the /boot/config.txt and enable the following feature:

   hdmi_force_hotplug=1

Save the file and reboot.  Does that help?  If not, I would then research how to force the desired screen resolution that your current monitor supports and also put that into the config.txt file.

Ultimately, there is probably a more elegant way to achieve what you're looking for without forcing the HDMI port to be on and maybe someone on the list can offer that up.

--David
KI6ZHD


On 11/03/2020 07:31 AM, Alf Blomqvist wrote:
Hi,

I got problems when I set up my remote station headless.

With a monitor connected at the remote qth there is no problems with the size of JTDX main screen.

I have tried both Raspberry Pi 3B and Raspberry Pi 4B with same problem - the screen is too large and I'm not able to make the text on the screen smaller - I cannot press ok on setting screen!!

I don't no if this is a Raspberry Pi problem or a JTDX problem.

73 Alf
OH6IH


Re: JTDX screen size too large - how to correct? #jtdx #pi

Jonathan Magee
 

Hi Alf
These are the steps I used. They may be different steps depending on the version of Raspbian you have installed.

Press Raspberry icon to get up the menu
Select menu option Preference -> Screen Configuration

In the Screen Layout application
Goto the Configure menu
Select Screens -> HDMI -> Resolution
Select the resolution you want and then press the green tick to apply the change
You will then be asked to Hit OK to keep the new setting

Hope this helps
73 Jonathan GI7KMC

On Tue, 3 Nov 2020 at 15:32, Alf Blomqvist <oh6ih@...> wrote:
Hi,

I got problems when I set up my remote station headless.

With a monitor connected at the remote qth there is no problems with the size of JTDX main screen.

I have tried both Raspberry Pi 3B and Raspberry Pi 4B with same problem - the screen is too large and I'm not able to make the text on the screen smaller - I cannot press ok on setting screen!!

I don't no if this is a Raspberry Pi problem or a JTDX problem.

73 Alf
OH6IH


JTDX screen size too large - how to correct? #jtdx #pi

Alf Blomqvist
 

Hi,

I got problems when I set up my remote station headless.

With a monitor connected at the remote qth there is no problems with the size of JTDX main screen.

I have tried both Raspberry Pi 3B and Raspberry Pi 4B with same problem - the screen is too large and I'm not able to make the text on the screen smaller - I cannot press ok on setting screen!!

I don't no if this is a Raspberry Pi problem or a JTDX problem.

73 Alf
OH6IH


Re: Unable to compile #tnc

KN6FOA
 

I think it is one of the dependencies...not sure what is going on.  I'm trying to reflash it to work on i2c as I want 2 attached to my pi to do HF and VHF.


Re: Unable to compile #tnc

John G8BPQ
 

The programs compile ok here using Arduino 1.8.9 and Teensyduino 1.47.

It may be something has changed in the latest versions - I suggest you try with the versions I'm using.

73,
John G8BPQ



On 31/10/2020 00:51, mskurnik@... wrote:
I am unable to get the teensy code to compile in Arduino.  I even did a clean install of the Arduino software.  I followed the instructions, installed arduino, installed the addon, copied the files, etc.  When I go to build it complained about not having the Adafruit GFX library so I added it but now it complains about another thing.  This isn't my first Arduino project but I've never had problems like this before.  I guess I'm missing something.

<command-line>:0:18: warning: ISO C++11 requires whitespace after the macro name
In file included from C:\Program Files (x86)\Arduino\hardware\teensy\avr\cores\teensy3/Printable.h:25:0,
                 from C:\Program Files (x86)\Arduino\hardware\teensy\avr\cores\teensy3/Print.h:39,
                 from C:\Program Files (x86)\Arduino\hardware\teensy\avr\cores\teensy3/Stream.h:24,
                 from C:\Program Files (x86)\Arduino\hardware\teensy\avr\cores\teensy3/HardwareSerial.h:252,
                 from C:\Program Files (x86)\Arduino\hardware\teensy\avr\cores\teensy3/WProgram.h:46,
                 from C:\Program Files (x86)\Arduino\hardware\teensy\avr\cores\teensy3/Arduino.h:6,
                 from C:\Users\me\AppData\Local\Temp\arduino_build_643498\sketch\SM_Teensy.ino.cpp:1:
C:\Program Files (x86)\Arduino\hardware\teensy\avr\cores\teensy3/new.h:41:6: warning: 'void operator delete(void*, size_t)' is a usual (non-placement) deallocation function in C++14 (or with -fsized-deallocation) [-Wc++14-compat]
 void operator delete(void * ptr, size_t size);
      ^
C:\Program Files (x86)\Arduino\hardware\teensy\avr\cores\teensy3/new.h:42:6: warning: 'void operator delete [](void*, size_t)' is a usual (non-placement) deallocation function in C++14 (or with -fsized-deallocation) [-Wc++14-compat]
 void operator delete[](void * ptr, size_t size);
      ^
C:\Users\me\AppData\Local\Temp\arduino_build_643498\libraries\Wire\WireKinetis.cpp.o: In function `i2c0_isr':
C:\Program Files (x86)\Arduino\hardware\teensy\avr\libraries\Wire/WireKinetis.cpp:912: multiple definition of `i2c0_isr'
C:\Users\me\AppData\Local\Temp\arduino_build_643498\libraries\TeensyConfig\i2c_t3.cpp.o:C:\Users\me\Downloads\HAM Radio\TeensyProjects\libraries\TeensyConfig/i2c_t3.cpp:1387: first defined here
c:/program files (x86)/arduino/hardware/tools/arm/bin/../lib/gcc/arm-none-eabi/5.4.1/../../../../arm-none-eabi/bin/ld.exe: Disabling relaxation: it will not work with multiple definitions
C:\Users\me\AppData\Local\Temp\arduino_build_643498\libraries\Wire\WireKinetis.cpp.o: In function `Print::availableForWrite()':
C:\Program Files (x86)\Arduino\hardware\teensy\avr\libraries\Wire/WireKinetis.h:133: multiple definition of `i2c1_isr'
C:\Users\me\AppData\Local\Temp\arduino_build_643498\libraries\TeensyConfig\i2c_t3.cpp.o:C:\Users\me\Downloads\HAM Radio\TeensyProjects\libraries\TeensyConfig/i2c_t3.h:921: first defined here
C:\Users\me\AppData\Local\Temp\arduino_build_643498\libraries\Wire\WireKinetis.cpp.o: In function `Print::availableForWrite()':
C:\Program Files (x86)\Arduino\hardware\teensy\avr\libraries\Wire/WireKinetis.h:133: multiple definition of `Wire1'
C:\Users\me\AppData\Local\Temp\arduino_build_643498\libraries\TeensyConfig\i2c_t3.cpp.o:C:\Users\me\Downloads\HAM Radio\TeensyProjects\libraries\TeensyConfig/i2c_t3.h:921: first defined here
c:/program files (x86)/arduino/hardware/tools/arm/bin/../lib/gcc/arm-none-eabi/5.4.1/../../../../arm-none-eabi/bin/ld.exe: Warning: size of symbol `Wire1' changed from 20 in C:\Users\me\AppData\Local\Temp\arduino_build_643498\libraries\TeensyConfig\i2c_t3.cpp.o to 108 in C:\Users\me\AppData\Local\Temp\arduino_build_643498\libraries\Wire\WireKinetis.cpp.o
C:\Users\me\AppData\Local\Temp\arduino_build_643498\libraries\Wire\WireKinetis.cpp.o: In function `Print::availableForWrite()':
C:\Program Files (x86)\Arduino\hardware\teensy\avr\libraries\Wire/WireKinetis.h:133: multiple definition of `Wire'
C:\Users\me\AppData\Local\Temp\arduino_build_643498\libraries\TeensyConfig\i2c_t3.cpp.o:C:\Users\me\Downloads\HAM Radio\TeensyProjects\libraries\TeensyConfig/i2c_t3.h:921: first defined here
c:/program files (x86)/arduino/hardware/tools/arm/bin/../lib/gcc/arm-none-eabi/5.4.1/../../../../arm-none-eabi/bin/ld.exe: Warning: size of symbol `Wire' changed from 20 in C:\Users\me\AppData\Local\Temp\arduino_build_643498\libraries\TeensyConfig\i2c_t3.cpp.o to 108 in C:\Users\me\AppData\Local\Temp\arduino_build_643498\libraries\Wire\WireKinetis.cpp.o
collect2.exe: error: ld returned 1 exit status
Error compiling for board Teensy 3.6.
 


Unable to compile #tnc

KN6FOA
 

I am unable to get the teensy code to compile in Arduino.  I even did a clean install of the Arduino software.  I followed the instructions, installed arduino, installed the addon, copied the files, etc.  When I go to build it complained about not having the Adafruit GFX library so I added it but now it complains about another thing.  This isn't my first Arduino project but I've never had problems like this before.  I guess I'm missing something.

<command-line>:0:18: warning: ISO C++11 requires whitespace after the macro name
In file included from C:\Program Files (x86)\Arduino\hardware\teensy\avr\cores\teensy3/Printable.h:25:0,
                 from C:\Program Files (x86)\Arduino\hardware\teensy\avr\cores\teensy3/Print.h:39,
                 from C:\Program Files (x86)\Arduino\hardware\teensy\avr\cores\teensy3/Stream.h:24,
                 from C:\Program Files (x86)\Arduino\hardware\teensy\avr\cores\teensy3/HardwareSerial.h:252,
                 from C:\Program Files (x86)\Arduino\hardware\teensy\avr\cores\teensy3/WProgram.h:46,
                 from C:\Program Files (x86)\Arduino\hardware\teensy\avr\cores\teensy3/Arduino.h:6,
                 from C:\Users\me\AppData\Local\Temp\arduino_build_643498\sketch\SM_Teensy.ino.cpp:1:
C:\Program Files (x86)\Arduino\hardware\teensy\avr\cores\teensy3/new.h:41:6: warning: 'void operator delete(void*, size_t)' is a usual (non-placement) deallocation function in C++14 (or with -fsized-deallocation) [-Wc++14-compat]
 void operator delete(void * ptr, size_t size);
      ^
C:\Program Files (x86)\Arduino\hardware\teensy\avr\cores\teensy3/new.h:42:6: warning: 'void operator delete [](void*, size_t)' is a usual (non-placement) deallocation function in C++14 (or with -fsized-deallocation) [-Wc++14-compat]
 void operator delete[](void * ptr, size_t size);
      ^
C:\Users\me\AppData\Local\Temp\arduino_build_643498\libraries\Wire\WireKinetis.cpp.o: In function `i2c0_isr':
C:\Program Files (x86)\Arduino\hardware\teensy\avr\libraries\Wire/WireKinetis.cpp:912: multiple definition of `i2c0_isr'
C:\Users\me\AppData\Local\Temp\arduino_build_643498\libraries\TeensyConfig\i2c_t3.cpp.o:C:\Users\me\Downloads\HAM Radio\TeensyProjects\libraries\TeensyConfig/i2c_t3.cpp:1387: first defined here
c:/program files (x86)/arduino/hardware/tools/arm/bin/../lib/gcc/arm-none-eabi/5.4.1/../../../../arm-none-eabi/bin/ld.exe: Disabling relaxation: it will not work with multiple definitions
C:\Users\me\AppData\Local\Temp\arduino_build_643498\libraries\Wire\WireKinetis.cpp.o: In function `Print::availableForWrite()':
C:\Program Files (x86)\Arduino\hardware\teensy\avr\libraries\Wire/WireKinetis.h:133: multiple definition of `i2c1_isr'
C:\Users\me\AppData\Local\Temp\arduino_build_643498\libraries\TeensyConfig\i2c_t3.cpp.o:C:\Users\me\Downloads\HAM Radio\TeensyProjects\libraries\TeensyConfig/i2c_t3.h:921: first defined here
C:\Users\me\AppData\Local\Temp\arduino_build_643498\libraries\Wire\WireKinetis.cpp.o: In function `Print::availableForWrite()':
C:\Program Files (x86)\Arduino\hardware\teensy\avr\libraries\Wire/WireKinetis.h:133: multiple definition of `Wire1'
C:\Users\me\AppData\Local\Temp\arduino_build_643498\libraries\TeensyConfig\i2c_t3.cpp.o:C:\Users\me\Downloads\HAM Radio\TeensyProjects\libraries\TeensyConfig/i2c_t3.h:921: first defined here
c:/program files (x86)/arduino/hardware/tools/arm/bin/../lib/gcc/arm-none-eabi/5.4.1/../../../../arm-none-eabi/bin/ld.exe: Warning: size of symbol `Wire1' changed from 20 in C:\Users\me\AppData\Local\Temp\arduino_build_643498\libraries\TeensyConfig\i2c_t3.cpp.o to 108 in C:\Users\me\AppData\Local\Temp\arduino_build_643498\libraries\Wire\WireKinetis.cpp.o
C:\Users\me\AppData\Local\Temp\arduino_build_643498\libraries\Wire\WireKinetis.cpp.o: In function `Print::availableForWrite()':
C:\Program Files (x86)\Arduino\hardware\teensy\avr\libraries\Wire/WireKinetis.h:133: multiple definition of `Wire'
C:\Users\me\AppData\Local\Temp\arduino_build_643498\libraries\TeensyConfig\i2c_t3.cpp.o:C:\Users\me\Downloads\HAM Radio\TeensyProjects\libraries\TeensyConfig/i2c_t3.h:921: first defined here
c:/program files (x86)/arduino/hardware/tools/arm/bin/../lib/gcc/arm-none-eabi/5.4.1/../../../../arm-none-eabi/bin/ld.exe: Warning: size of symbol `Wire' changed from 20 in C:\Users\me\AppData\Local\Temp\arduino_build_643498\libraries\TeensyConfig\i2c_t3.cpp.o to 108 in C:\Users\me\AppData\Local\Temp\arduino_build_643498\libraries\Wire\WireKinetis.cpp.o
collect2.exe: error: ld returned 1 exit status
Error compiling for board Teensy 3.6.
 

861 - 880 of 13263