Date   

Re: Compatible case, heat sink, and fans?

Fred Meier <fsmeier@...>
 

IMHO, every microprocessor benefits from improved cooling. The more the processors are enclosed in cases and by add ons, the more important supplemental cooling becomes.

 

From: udrc@nw-digital-radio.groups.io <udrc@nw-digital-radio.groups.io> On Behalf Of Robert Sears
Sent: Monday, December 17, 2018 8:53 AM
To: udrc@nw-digital-radio.groups.io
Subject: Re: [udrc] Compatible case, heat sink, and fans?

 

[Edited Message Follows]

I don't see the need for a fan on a R-Pi,  even the need for a heatsink is debatable.

You are limited by the Pi-Hat as far as heat sink height.


Re: Compatible case, heat sink, and fans?

Robert Sears
 
Edited

I don't see the need for a fan on a R-Pi,  even the need for a heatsink is debatable.

You are limited by the Pi-Hat as far as heat sink height.


Re: Compatible case, heat sink, and fans?

Fred Meier <fsmeier@...>
 

Good morning Patrick.

Good one, ‘Warm regards’. Great question, good humor.

Merry Christmas all.

73, Fred VE7FMN

 

From: udrc@nw-digital-radio.groups.io <udrc@nw-digital-radio.groups.io> On Behalf Of Patrick - KJ4MUB
Sent: Sunday, December 16, 2018 7:09 PM
To: udrc@nw-digital-radio.groups.io
Subject: [udrc] Compatible case, heat sink, and fans?

 

What Raspberry Pi 3B+ case do you use with the DRAWS HAT?

Also, what heat sinks/fan fits?

Warm regards,

 

73’s Patrick


K3BBG - Branson, Missouri
Tri-Lakes ARC Member

 

 

 

 

 


Re: Compatible case, heat sink, and fans?

Gayland Gump
 

Make sure it has room for a fan!

Gayland
KG7GCF


On Sun, Dec 16, 2018 at 10:29 PM John D Hays - K7VE <john@...> wrote:
A custom case is under development, it will be available after the new year.

On Sun, Dec 16, 2018 at 10:25 PM Patrick - KJ4MUB <ptwaugh@...> wrote:
What Raspberry Pi 3B+ case do you use with the DRAWS HAT?

Also, what heat sinks/fan fits?

Warm regards,

73’s Patrick

K3BBG - Branson, Missouri
Tri-Lakes ARC Member








--


John D. Hays
Edmonds, WA
K7VE

   


DRAWS GPS Altitude limit #draws #gps

Dave N2OA
 

I'm looking into launching a high altitude balloon for one of the local schools and am considering using the DRAWS platform for APRS and data. Is there a altitude limitation on the GPS used?

Thanks,

Dave
N2OA


 

Basil recommends 

Look at these 3 scripts in ~/bin for controlling direwolf & ax.25
ax25-start
ax25-stop
ax25-status 

Rather than starting direwolf from the command line.
Though if you were to use the command line, you should use the full path name

direwolf -c /etc/direwolf.conf


 

On Sun, Dec 16, 2018 at 10:26 PM <jgindc1@...> wrote:
Running beta5.

I have used ./app_config.sh core

In /etc/direwolf.conf, for Channel 0 PTT is set by
   PTT gpio 12

However, when invoking direwolf as in
  direwolf -c /etc
direwolf responds with
"Note: PTT not configured for channel 0. (Ignore....)"

  With the radio tuned to 144.390 digital, APRS packets are received and successfully decoded.

With n7nix/debug
  sudo ./btest.sh -p
  response says a beacon has been sent, but the radio PTT is not triggered.

I am wondering if the problem is that the DRAWS connection between gpio 12 need to be routed to the correct pin on the right DIN-6 connector, pin 5 for 1200 baud. I believe there are configurable switches on DRAWS.

Suggestions much appreciated

I must say I am enjoying working through the various configuration details as an early adopter.

gpsd is working and I have successfully installed PAT on an earlier Compass version (Sending and receiving Winlink messages via Telnet).

73, John KM7LJ


On Sun, Dec 16, 2018 at 4:28 PM Basil Gunn <basil@...> wrote:

The way the image is intended to be used is to follow these instructions:

https://github.com/nwdigitalradio/n7nix/blob/master/DRAWS_CONFIG.md

From those instructions when you run:
./app_config.sh core
it will setup direwolf/ax.25/systemd so that it all starts at boot time.
It also makes you change your password, sets your time zone, and changes
your hostname.

You should NOT try to start direwolf from the console or the menu system
because it is already running. If you run
pidof direwolf
you will see that direwolf has a process id which means it is running.

Then use the following instructions to verify things are working properly.
https://github.com/nwdigitalradio/n7nix/blob/master/VERIFY_CONFIG.md

direwolf is started via systemd. The correct way to stop direwolf &
ax.25 is to use: ax25-stop in your local bin directory.

Look at these 3 scripts in ~/bin for controlling direwolf & ax.25
ax25-start
ax25-stop
ax25-status

Do NOT use systemctl to start & stop direwolf
Do use ax25-start & ax25-stop

Please read these pages:

https://github.com/nwdigitalradio/n7nix/blob/master/DRAWS_CONFIG.md
https://github.com/nwdigitalradio/n7nix/blob/master/VERIFY_CONFIG.md

/Basil

John D Hays - K7VE <john@...> writes:

> On Sun, Dec 16, 2018 at 12:49 PM David [kg5eiu] via Groups.Io <dcappello=
> aol.com@groups.io> wrote:
>
>> Okay - I am going to try my 991 in packet mode - BTW with the Beta 5 image
>> I try and run dire wolf and I get a permission problem:
>>
>>
>>
> As I noted, in another post.  The menu item does not work (it is setup by
> the direwolf install)  ... Basil has systemd scripts to start and stop
> direwolf
>
> See if it is running:
> sudo systemctl status direwolf
>
> Then
> sudo systemctl start direwolf
> or
> sudo systemctl stop direwolf
>
> And you can tail -f the log to see what is happening.
>
> The configuration file is in /etc





--


John D. Hays
Edmonds, WA
K7VE

   


Re: Compatible case, heat sink, and fans?

 

A custom case is under development, it will be available after the new year.

On Sun, Dec 16, 2018 at 10:25 PM Patrick - KJ4MUB <ptwaugh@...> wrote:
What Raspberry Pi 3B+ case do you use with the DRAWS HAT?

Also, what heat sinks/fan fits?

Warm regards,

73’s Patrick

K3BBG - Branson, Missouri
Tri-Lakes ARC Member








--


John D. Hays
Edmonds, WA
K7VE

   


jgindc1@...
 

Running beta5.

I have used ./app_config.sh core

In /etc/direwolf.conf, for Channel 0 PTT is set by
   PTT gpio 12

However, when invoking direwolf as in
  direwolf -c /etc
direwolf responds with
"Note: PTT not configured for channel 0. (Ignore....)"

  With the radio tuned to 144.390 digital, APRS packets are received and successfully decoded.

With n7nix/debug
  sudo ./btest.sh -p
  response says a beacon has been sent, but the radio PTT is not triggered.

I am wondering if the problem is that the DRAWS connection between gpio 12 need to be routed to the correct pin on the right DIN-6 connector, pin 5 for 1200 baud. I believe there are configurable switches on DRAWS.

Suggestions much appreciated

I must say I am enjoying working through the various configuration details as an early adopter.

gpsd is working and I have successfully installed PAT on an earlier Compass version (Sending and receiving Winlink messages via Telnet).

73, John KM7LJ


On Sun, Dec 16, 2018 at 4:28 PM Basil Gunn <basil@...> wrote:

The way the image is intended to be used is to follow these instructions:

https://github.com/nwdigitalradio/n7nix/blob/master/DRAWS_CONFIG.md

From those instructions when you run:
./app_config.sh core
it will setup direwolf/ax.25/systemd so that it all starts at boot time.
It also makes you change your password, sets your time zone, and changes
your hostname.

You should NOT try to start direwolf from the console or the menu system
because it is already running. If you run
pidof direwolf
you will see that direwolf has a process id which means it is running.

Then use the following instructions to verify things are working properly.
https://github.com/nwdigitalradio/n7nix/blob/master/VERIFY_CONFIG.md

direwolf is started via systemd. The correct way to stop direwolf &
ax.25 is to use: ax25-stop in your local bin directory.

Look at these 3 scripts in ~/bin for controlling direwolf & ax.25
ax25-start
ax25-stop
ax25-status

Do NOT use systemctl to start & stop direwolf
Do use ax25-start & ax25-stop

Please read these pages:

https://github.com/nwdigitalradio/n7nix/blob/master/DRAWS_CONFIG.md
https://github.com/nwdigitalradio/n7nix/blob/master/VERIFY_CONFIG.md

/Basil

John D Hays - K7VE <john@...> writes:

> On Sun, Dec 16, 2018 at 12:49 PM David [kg5eiu] via Groups.Io <dcappello=
> aol.com@groups.io> wrote:
>
>> Okay - I am going to try my 991 in packet mode - BTW with the Beta 5 image
>> I try and run dire wolf and I get a permission problem:
>>
>>
>>
> As I noted, in another post.  The menu item does not work (it is setup by
> the direwolf install)  ... Basil has systemd scripts to start and stop
> direwolf
>
> See if it is running:
> sudo systemctl status direwolf
>
> Then
> sudo systemctl start direwolf
> or
> sudo systemctl stop direwolf
>
> And you can tail -f the log to see what is happening.
>
> The configuration file is in /etc




Compatible case, heat sink, and fans?

Patrick - KJ4MUB <ptwaugh@...>
 

What Raspberry Pi 3B+ case do you use with the DRAWS HAT?

Also, what heat sinks/fan fits?

Warm regards,

73’s Patrick

K3BBG - Branson, Missouri
Tri-Lakes ARC Member







Re: APRS digipeater doing fine with compass beta-5 version

Basil Gunn
 

Hi Bernard,

Thanks for bringing this up. I will fix measure_deviate.sh so that it
uses left & right to describe the connectors without regard to what
connector type they are.

I believe the card name comes from the udrc driver in
/usr/src/udrc-1.0.4 and installed with apt-get install udrc-dkms.
I also believe that driver supports all the NW Digital HATS including
DRAWS that use the tlv320aic32x4 sound codec.

I expect Anna to correct me if I am wrong.

When I grep that driver its name is ".name=udrc" and that's what gets
displayed with aplay -l & used in the direwolf config

ADEVICE plughw:CARD=udrc,DEV=0 plughw:CARD=udrc,DEV=0

So what you are seeing with udrc is a card or device name that supports
UDRC, UDRC II & DRAWS and that name is unlikely to change as long as the
tlv320aic codec is used by these Hats.

/Basil

Hi,
I downloaded last available compass beta version today and installed it (beta 5).
Just plugged DRAWS hat on RPi 3B+, connected Din6 cable into left din6 plug and YAESU FT-7900 and set APRS frequency.
Starting direwolf -t 0 allowed immediate display of APRS trafic.
After editing direwolf.conf for BEACON to advertize my location and direwolf started digipeating APRS packets.

Some remarks about CARD name and din6 identification labelling:

aplay -l displays harware plugHW: CARD=udrc, DEV=0

Same for direwolf and n7nix/deviation/measure_deviate.sh in the menu and at various places
instead of DRAWS.

measure_deviate uses by default LEFT din6 (audio channel 0) that he advertizes as connector hd15 and PTT gpio 12
Same with option measure_deviate -c hd15
Starting measure_deviate -c din6
activates RIGHT din6 plug (audio channel 1) using PTT gpio 23

Using HD15 may confuse new DRAWS customers for there is no such plug.

Bernard


Basil Gunn
 

The way the image is intended to be used is to follow these instructions:

https://github.com/nwdigitalradio/n7nix/blob/master/DRAWS_CONFIG.md

From those instructions when you run:
./app_config.sh core
it will setup direwolf/ax.25/systemd so that it all starts at boot time.
It also makes you change your password, sets your time zone, and changes
your hostname.

You should NOT try to start direwolf from the console or the menu system
because it is already running. If you run
pidof direwolf
you will see that direwolf has a process id which means it is running.

Then use the following instructions to verify things are working properly.
https://github.com/nwdigitalradio/n7nix/blob/master/VERIFY_CONFIG.md

direwolf is started via systemd. The correct way to stop direwolf &
ax.25 is to use: ax25-stop in your local bin directory.

Look at these 3 scripts in ~/bin for controlling direwolf & ax.25
ax25-start
ax25-stop
ax25-status

Do NOT use systemctl to start & stop direwolf
Do use ax25-start & ax25-stop

Please read these pages:

https://github.com/nwdigitalradio/n7nix/blob/master/DRAWS_CONFIG.md
https://github.com/nwdigitalradio/n7nix/blob/master/VERIFY_CONFIG.md

/Basil

John D Hays - K7VE <@john_hays> writes:

On Sun, Dec 16, 2018 at 12:49 PM David [kg5eiu] via Groups.Io <dcappello=
aol.com@groups.io> wrote:

Okay - I am going to try my 991 in packet mode - BTW with the Beta 5 image
I try and run dire wolf and I get a permission problem:


As I noted, in another post. The menu item does not work (it is setup by
the direwolf install) ... Basil has systemd scripts to start and stop
direwolf

See if it is running:
sudo systemctl status direwolf

Then
sudo systemctl start direwolf
or
sudo systemctl stop direwolf

And you can tail -f the log to see what is happening.

The configuration file is in /etc


Jack Spitznagel
 

Thanks John, and Basil,

 

I am trying to get my notes straightened out  - there seems to be stuff in the earlier emails that is deprecated in later Beta.

 

After stumbling around blindly because I did not read it in the emails or wiki correctly, the Direwolf related stuff in Beta 5 now works. I figured out that the DRAWS Left channel was selected by trial and error. I was using the Right channel in previous Betas and the pre-beta. Was there a particular reason for that choice?

 

So please confirm as I now understand it:

Right port is 0, PTT is GPIO 12

Left port is 1, PTT is GPIO 23

 

And the lines in direwolf.conf should be enabled depending on which you want (or both if doing 9600 too)

 

In Xastir then you would add the AGWPE interface and the INET server if you want to gateway.

I never had tried it before… YAAC is a different kettle of stew. The automagical configuration almost worked but caused it behave strangely for me at first. After poking around under the hood in expert setup, it is now working. I like the UI, but am not fond of the map handling (slow and memory hungry) and it is only loading limited size maps, so I zoom out and wind up with white space.

 

Will it be possible to add scripts that reliably disable and re- enable direwolf from the UI? Or are we stuck using terminal,  changing to a specific directory, then becoming SU to execute the existing script? I am trying to get caught back up on what is possible (or not) in Raspbian Stretch variant of Debian and get accurate notes put together.

 

You folks are all great! Thanks for the hard work.

 

Jack – KD4IZ

 

 

From: udrc@nw-digital-radio.groups.io <udrc@nw-digital-radio.groups.io> On Behalf Of John D Hays - K7VE
Sent: Sunday, December 16, 2018 17:02
To: udrc@nw-digital-radio.groups.io
Subject: Re: [udrc] Betas #setup #draws #beta #image #direwolf

 

Your AGWPE is probably defaulting to the left din 6. It depends on what is in your /etc/direwolf.conf 

 

On Sun, Dec 16, 2018, 13:53 David [kg5eiu] via Groups.Io <dcappello=g wrote:

Thanks Basil - I looked that over I am excited to see your updates for DRAWS 

I am still a little confused on which interface type to add for the radio I have hooked up (my 991) I have it in the right port as you look
at the radio ports:




Here are my TNC interface types that I can choose from:


--
J Spitznagel
Science River LLC
KD4IZ


 

Direwolf documentation is at https://github.com/wb2osz/direwolf/blob/master/doc/User-Guide.pdf 

Basic idea -- direwolf.conf sets up devices, eg. the udrc CODEC and under that channels (2 for the CODEC)
Each channel has modem (eg 1200) and other values.

When agwpe connects it is going, by default connect to the first channel.

Here is an example direwolf.conf

ADEVICE plughw:CARD=udrc,DEV=0
ARATE 48000
ACHANNELS 2

CHANNEL 0
#MYCALL N0CALL-0
MODEM 1200
PTT GPIO 12
#TBEACON delay=1 sendto=0 every=10 overlay=S symbol="digi" power=5 height=20 gain=6 comment="DRAWS 0 1200" via=WIDE1-1,WIDE2-1
 
 
CHANNEL 1
MYCALL  N0CALL-1
#MODEM 9600
PTT GPIO 23
#TBEACON delay=1 sendto=2 every=10 overlay=S symbol="digi" power=5 height=20 gain=6 comment="DRAWS 1 9600" via=WIDE1-1,WIDE2-1
 
 
IGSERVER noam.aprs2.net
#IGLOGIN <YOUR CALL> <YOUR PASSCODE>
#TBEACON sendto=IG delay=1 every=60:00 dest=APUDR1 symbol="igate" overlay=R
#IGTXLIMIT 6 10
AGWPORT 8000
KISSPORT 8001
GPSD localhost


David [kg5eiu]
 

Okay so I moved the radio to the left port - I have not touched the config file /etc/direwolf.conf  - only thing I did was run the script
I found in another post - I got the 991 radio on 144.390 and I think setup for the packet/data interface at 1200 baud.
I am still a little confused do  I need to a specific interface for the TNC (draws hat)  in Xastir ? 


 

Your AGWPE is probably defaulting to the left din 6. It depends on what is in your /etc/direwolf.conf 


On Sun, Dec 16, 2018, 13:53 David [kg5eiu] via Groups.Io <dcappello=aol.com@groups.io wrote:
Thanks Basil - I looked that over I am excited to see your updates for DRAWS 

I am still a little confused on which interface type to add for the radio I have hooked up (my 991) I have it in the right port as you look
at the radio ports:




Here are my TNC interface types that I can choose from:


David [kg5eiu]
 

Thanks Basil - I looked that over I am excited to see your updates for DRAWS 

I am still a little confused on which interface type to add for the radio I have hooked up (my 991) I have it in the right port as you look
at the radio ports:




Here are my TNC interface types that I can choose from:


 

Or connect using networked KISS or AGWPE under interfaces. 


On Sun, Dec 16, 2018, 13:36 David [kg5eiu] via Groups.Io <dcappello=aol.com@groups.io wrote:
I did setup GPSD as a daemon - and I now added it in interface control as Networked GPS (via GPSD)

Now I think I need to add the X.25 packet interface ?  


David [kg5eiu]
 

I did setup GPSD as a daemon - and I now added it in interface control as Networked GPS (via GPSD)

Now I think I need to add the X.25 packet interface ?  


Basil Gunn
 

Okay dire wolf running as a daemon - I think it is working.... Xastir
asked me for GPS info... have to read up on how to get that to read
the local GPS. Looks like I also attached to the aprsc server (
http://208.94.241.11:14501 )

Now have to go figure out the interface type and setup for Xastir....
These notes may help you. I still need to update them for the DRAWS Hat.

https://github.com/nwdigitalradio/n7nix/tree/master/xastir

/Basil


 

If you have gpsd running as a daemon, you can connect under interfaces. 



On Sun, Dec 16, 2018, 13:26 David [kg5eiu] via Groups.Io <dcappello=aol.com@groups.io wrote:
Okay dire wolf running as a daemon - I think it is working....  Xastir asked me for GPS info... have to read up on how to get that to read the local GPS.   Looks like I also attached
to the aprsc server 

Now have to go figure out the interface type and setup for Xastir....