Date   

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.
 


Re: Direwolf Software TNC version 1.6 released

David Ranch
 


Thank you for the new release John!

--David
KI6ZHD


On 10/28/2020 04:30 PM, WB2OSZ wrote:
The long awaited Direwolf Software TNC release 1.6 has finally arrived.


New Features include:

  • FX.25 - Forward error correction (FEC) added in a way that is completely compatible with an ordinary AX.25 frame. See new document AX25_plus_FEC_equals_FX25.pdf for details.

  • Receive AIS location data from ships.

  • Receive Emergency Alert System (EAS) Specific Area Message Encoding (SAME). A sample application is provided to convert these to APRS messages.

New Documentation:

 

More Details:

Direwolf runs on Linux (including Raspberry Pi), Windows, and Mac OSX.

https://github.com/wb2osz/direwolf/blob/master/README.md



Direwolf Software TNC version 1.6 released

 

The long awaited Direwolf Software TNC release 1.6 has finally arrived.


New Features include:

  • FX.25 - Forward error correction (FEC) added in a way that is completely compatible with an ordinary AX.25 frame. See new document AX25_plus_FEC_equals_FX25.pdf for details.

  • Receive AIS location data from ships.

  • Receive Emergency Alert System (EAS) Specific Area Message Encoding (SAME). A sample application is provided to convert these to APRS messages.

New Documentation:

 

More Details:

Direwolf runs on Linux (including Raspberry Pi), Windows, and Mac OSX.

https://github.com/wb2osz/direwolf/blob/master/README.md


Re: TNC-PI Troubleshooting

Mark Griffith
 

You need a program that decodes packet data.  I'm assuming you have it connected to a radio that is tuned to an active packet frequency?

Programs for the Pi can be John Wiseman's pilinbpq, or Pat, or PiGate.  Do some research on those.

Let me know if you have more questions.

Mark
KD0QYN


On Tuesday, October 27, 2020, 4:11:51 AM CDT, mail@... <mail@...> wrote:


I purchased a TNC-PI a few years ago and it ended up on the shelf "for when I have more time".
Well, now I have more time, and I can't get it to work.
I have made all the configuration changes to raspbian for the serial port configuration.
The pitnc_get/setparams works fine.   I can even trigger the test tones to check deviation.
There is no data being decoded by "cat /dev/serial0(or ttyAMA0)" or by minicom or any other com program.
Could it be a blown MX-614?   Does it use the MX-614 to generate the test tones?    What handles the actual decoding?   Where do I start with this?


TNC-PI Troubleshooting

Chris Tripp - KK4CT
 

I purchased a TNC-PI a few years ago and it ended up on the shelf "for when I have more time".
Well, now I have more time, and I can't get it to work.
I have made all the configuration changes to raspbian for the serial port configuration.
The pitnc_get/setparams works fine.   I can even trigger the test tones to check deviation.
There is no data being decoded by "cat /dev/serial0(or ttyAMA0)" or by minicom or any other com program.
Could it be a blown MX-614?   Does it use the MX-614 to generate the test tones?    What handles the actual decoding?   Where do I start with this?


Re: Pi-4, Dire Wolf and Signal Link---Where did the "Audio Device Settings" Go?

Mike Erstad
 

I've solved my crazy flashing problem:
I followed EtoTen's advice but, there still has been some changes since his posting in 2019...but the changes are right there in text during installation!
Thanks Again Members...I'm very weak in this area and appreciate all the help....
Mike


On Mon, Oct 26, 2020 at 6:49 PM David Ranch <rpi4hamradio-groupsio@...> wrote:

I might have partially jumped the gun and Mark is correct.  Using "-t 0" will turn off all colors and blinking but if you want color coding without blinking, there was a newer bug introduced in Raspberry Pi OS (buster) and a work around was added into Direwolf v1.6:

   https://github.com/wb2osz/direwolf/issues/270

--David
KI6ZHD


On 10/26/2020 04:28 PM, Mark Griffith via groups.io wrote:
And if you want it to run in the background without taking up a terminal:

/usr/local/bin/direwolf -t 0 -p > /var/tmp/dirwolf.log 2>&1 &

Then to stop direwolf, just do this command in any terminal:

pkill direwolf

This is all std Linux/Unix stuff.

Mark
KD0QYN



On Monday, October 26, 2020, 6:24:35 PM CDT, Mark Griffith via groups.io <mdgriffith2003@...> wrote:


Or, you can run Direwolf with some command line options:

/usr/local/bin/direwolf -t 0 -p

If you want a log of what was going on:

/usr/local/bin/direwolf -t 0 -p > /var/tmp/dirwolf.log 2>&1

Mark
KD0QYN


On Monday, October 26, 2020, 6:17:49 PM CDT, David Ranch <rpi4hamradio-groupsio@...> wrote:



Hello Mike,

Does anyone know why when I start Dire Wolf the text just keeps flashing On/Off/On/Off/On and it works fine but just keep flashing and driving me nuts…

Known issue with Raspbian Buster.  You need to upgrade to Direwolf 1.6 which requires you build it from source today (this is covered in the Direwolf User Guide).

--David
KI6ZHD


Re: Pi-4, Dire Wolf and Signal Link---Where did the "Audio Device Settings" Go?

David Ranch
 


I might have partially jumped the gun and Mark is correct.  Using "-t 0" will turn off all colors and blinking but if you want color coding without blinking, there was a newer bug introduced in Raspberry Pi OS (buster) and a work around was added into Direwolf v1.6:

   https://github.com/wb2osz/direwolf/issues/270

--David
KI6ZHD


On 10/26/2020 04:28 PM, Mark Griffith via groups.io wrote:
And if you want it to run in the background without taking up a terminal:

/usr/local/bin/direwolf -t 0 -p > /var/tmp/dirwolf.log 2>&1 &

Then to stop direwolf, just do this command in any terminal:

pkill direwolf

This is all std Linux/Unix stuff.

Mark
KD0QYN



On Monday, October 26, 2020, 6:24:35 PM CDT, Mark Griffith via groups.io <mdgriffith2003@...> wrote:


Or, you can run Direwolf with some command line options:

/usr/local/bin/direwolf -t 0 -p

If you want a log of what was going on:

/usr/local/bin/direwolf -t 0 -p > /var/tmp/dirwolf.log 2>&1

Mark
KD0QYN


On Monday, October 26, 2020, 6:17:49 PM CDT, David Ranch <rpi4hamradio-groupsio@...> wrote:



Hello Mike,

Does anyone know why when I start Dire Wolf the text just keeps flashing On/Off/On/Off/On and it works fine but just keep flashing and driving me nuts…

Known issue with Raspbian Buster.  You need to upgrade to Direwolf 1.6 which requires you build it from source today (this is covered in the Direwolf User Guide).

--David
KI6ZHD


Re: Pi-4, Dire Wolf and Signal Link---Where did the "Audio Device Settings" Go?

Mark Griffith
 

And if you want it to run in the background without taking up a terminal:

/usr/local/bin/direwolf -t 0 -p > /var/tmp/dirwolf.log 2>&1 &

Then to stop direwolf, just do this command in any terminal:

pkill direwolf

This is all std Linux/Unix stuff.

Mark
KD0QYN



On Monday, October 26, 2020, 6:24:35 PM CDT, Mark Griffith via groups.io <mdgriffith2003@...> wrote:


Or, you can run Direwolf with some command line options:

/usr/local/bin/direwolf -t 0 -p

If you want a log of what was going on:

/usr/local/bin/direwolf -t 0 -p > /var/tmp/dirwolf.log 2>&1

Mark
KD0QYN


On Monday, October 26, 2020, 6:17:49 PM CDT, David Ranch <rpi4hamradio-groupsio@...> wrote:



Hello Mike,

Does anyone know why when I start Dire Wolf the text just keeps flashing On/Off/On/Off/On and it works fine but just keep flashing and driving me nuts…

Known issue with Raspbian Buster.  You need to upgrade to Direwolf 1.6 which requires you build it from source today (this is covered in the Direwolf User Guide).

--David
KI6ZHD


Re: Pi-4, Dire Wolf and Signal Link---Where did the "Audio Device Settings" Go?

Mark Griffith
 

Or, you can run Direwolf with some command line options:

/usr/local/bin/direwolf -t 0 -p

If you want a log of what was going on:

/usr/local/bin/direwolf -t 0 -p > /var/tmp/dirwolf.log 2>&1

Mark
KD0QYN


On Monday, October 26, 2020, 6:17:49 PM CDT, David Ranch <rpi4hamradio-groupsio@...> wrote:



Hello Mike,

Does anyone know why when I start Dire Wolf the text just keeps flashing On/Off/On/Off/On and it works fine but just keep flashing and driving me nuts…

Known issue with Raspbian Buster.  You need to upgrade to Direwolf 1.6 which requires you build it from source today (this is covered in the Direwolf User Guide).

--David
KI6ZHD

921 - 940 of 13315