Date   

Re: Adding a second radio

Basil Gunn
 

And you can install either LinBPQ or JNOS to do packet without the
complexity of dealing with the Linux AX.25 stack. (Not saying that
LinBPQ or JNOS are less complex....)
The Linux AX.25 stack comes with the kernel and is installed on our
image and configured with my scripts taking the complexity out of
dealing with Linux AX.25 stack. Bill you should try it some time.

You can use LinBPQ or JNOS, I think they are good pieces of software but
I don't support them.

/Basil


Re: Adding a second radio

 

The two approaches meet different needs.

I use both, depending on what applications I am trying to support.

If the applications you are trying to support require the Linux AX.25 stack, then Basil's scripts and setup are the better solution. This tends to be a lot of historical applications for Keyboard to Keyboard, BBS, IP over AX.25, AX.25 over IP, ... and can also support newer applications in the Winlink and APRS world.

However, direwolf, in addition to being the modem can support many functions without the
And you can install either LinBPQ or JNOS to do packet without the
complexity of dealing with the Linux AX.25 stack. (Not saying that
LinBPQ or JNOS are less complex....)

Bill


Re: Adding a second radio

 

Jack, Jim, et al --

The two approaches meet different needs.

I use both, depending on what applications I am trying to support.

If the applications you are trying to support require the Linux AX.25 stack, then Basil's scripts and setup are the better solution.  This tends to be a lot of historical applications for Keyboard to Keyboard, BBS, IP over AX.25, AX.25 over IP, ... and can also support newer applications in the Winlink and APRS world.

However, direwolf, in addition to being the modem can support many functions without the need for the Linux AX.25 stack.  It can directly support digipeating, APRS®, Igating, beaconing (including GPS parsing), KISS, Network KISS/AGW, APRS® TouchTone™, and more.  All via configuration in direwolf.conf with fewer 'moving parts'. I consider it a simpler approach, if it meets your needs.

The choice is driven by application requirements and user preference.


On Fri, Oct 11, 2019 at 9:51 AM Jack Spitznagel <kd4iz@...> wrote:
Jim, Basil and John, All,

I would like to hear that explained as well. I started with John's approach early after DRAWS became available, then switched over to Basil's install script with the AX25 internals in Raspbian. They both work for me, but I was doing "quick and dirty" evals of the beta images when I set things up. I found that the Direwolf alone approach was easier for switching from AX.25 to HF modem function. I have to work at 'script-kiddie" level in Linux. I am busy with real work and I need to reconfigure it so very little that I have to go back and reference my notes (which are not great) each time I fire up. I would love to see an install choice be offered in the configuration scripts.

John, Basil, is that easily do-able without creating internal dissension or is it a philosophic divide you would rather not bridge?

No doubt there are good reasons for both approaches... however, I am a realist and know I will not get time to go "larval stage" with the OS until I retire, so as smooth and efficient as Basil's approach may be, it seems less flexible than having GUI access to Direwolf, being able to check its status and shut it down without bringing up a terminal or creating a bunch of icons linked to scripts that switch things for me. Typical lazy ham, I guess.

In the meantime I have a DRAWS in my "go-box" for portable digital work and one on the desk here running Xastir as a fill-in digi and inet gateway for local 144.39 users.

Thanks for all of your hard work supporting this little beast!
--
Jack - KD4IZ



--
John D. Hays
Kingston, WA
K7VE

 


Re: Adding a second radio

Jack Spitznagel
 

Jim, Basil and John, All,

I would like to hear that explained as well. I started with John's approach early after DRAWS became available, then switched over to Basil's install script with the AX25 internals in Raspbian. They both work for me, but I was doing "quick and dirty" evals of the beta images when I set things up. I found that the Direwolf alone approach was easier for switching from AX.25 to HF modem function. I have to work at 'script-kiddie" level in Linux. I am busy with real work and I need to reconfigure it so very little that I have to go back and reference my notes (which are not great) each time I fire up. I would love to see an install choice be offered in the configuration scripts.

John, Basil, is that easily do-able without creating internal dissension or is it a philosophic divide you would rather not bridge?

No doubt there are good reasons for both approaches... however, I am a realist and know I will not get time to go "larval stage" with the OS until I retire, so as smooth and efficient as Basil's approach may be, it seems less flexible than having GUI access to Direwolf, being able to check its status and shut it down without bringing up a terminal or creating a bunch of icons linked to scripts that switch things for me. Typical lazy ham, I guess.

In the meantime I have a DRAWS in my "go-box" for portable digital work and one on the desk here running Xastir as a fill-in digi and inet gateway for local 144.39 users.

Thanks for all of your hard work supporting this little beast!
--
Jack - KD4IZ


Hamwan / DRAWS / Fiber / HF / RMS Gateway

Alan Bush
 

Hello NWDR!

I have a hamwan link, a fiber connection, a really average dipole, and a DRAWS package. I'm looking for some step-by-step info to help get an RMS gateway established. preferably HF rather than 2M or higher. How can we make this happen?

Alan, KJ7BFC


Re: Adding a second radio

Jim Erickson
 

Thanks for these ideas everyone.  I’m just in the middle of setting up my DRAWS Pi with two radios, one doing APRS and the other running LinBPQ for a BBS.  Very interested to hear about APRX and LinFBB, neither of which I had heard of before.

I would also be interested to hear in the reasoning behind the two different philosophies, advantages and disadvantages.  I’m currently doing it all through Direwolf as that’s the only way I know how, but have been dipping my toes in to the AX.25 stack as I’ve been playing with LinBPQ.

So much to learn and so much to read.  I appreciate all the work done and would also appreciate any other resources regarding these two different methods of doing packet radio with a Raspberry Pi.

------
73,
Jim
VA7SHG - Phone
VE7TGZ - Other

On Oct 10, 2019, at 09:16, Basil Gunn <basil@...> wrote:


Hi J P,

Thank you for your reply. John Hays means well, but his reply did not
get me the traction that I expected.

John & I have 2 different philosophies regarding packet. He gave advice
on how to do everything in direwolf and I like to keep direwolf as a
sound modem only & use the AX.25 functionality of Linux.
John has done some great work on configuring virtual sound card interfaces so
that you can do 1200 baud & 9600 baud packet on the same radio.

And Yes I have a service monitor to set the deviation. It makes it alot easier :)

Yep.

Another Topic will be the FBB that is installed as part of the BETA14
Build. Where is the FBB documentation? The FBB install script?

So this is a project I briefly got working but don't use day to day. I
think BBS are useful so that is on my list of things for permanent
infrastructure. The latest version (7.08-beta8 from SourceForge) is
built & installed on the image.

The documentation I have been using is here:
https://sourceforge.net/projects/linfbb/files/

BTW we edited the URONODE config file and ran the install, an it appears to work.

Great to hear!

I think that direwolf.conf edits are all that are needed.

Depends on your philosophy.

How do we enable the APRS Gateway? I think it is just the list of attributes for “Channel 1"
Only on the second channel?

I use APRX for APRS embedded systems. ie. no monitor
See: 4.5 A Bi-Directional Cross-band Digipeater in this manual
https://thelifeofkenneth.com/aprx/aprx-manual.pdf

You can just use Direwolf but I won't be able to help you with that. The
direwolf documentation is very good & if you go that route I recommend
you read the entire manual carefully.

Our Statewide only will permit digipeating, winlink, FBB messaging on the first Channel. (FBB install another challenge that we will make later.)
They only support 1200baud on the first channel. Our club will support 9600baud on the other channel.

ADEVICE plughw:CARD=udrc,DEV=0
ARATE 48000
ACHANNELS 2
CHANNEL 0
MYCALL YOURCALLSIGN-7
MODEM 1200
PTT GPIO 12
CHANNEL 1
MODEM 9600
PTT GPIO 12
MYCALL YOURCALLSIGN-10
AGWPORT 8000
KISSPORT 8001
PBEACON delay=1 every=10 overlay=S symbol="digi" lat=41^20.68734N long=88^28.39224W power=100 height=20 gain=6 comment="UDRC" via=WIDE1-1,WIDE2-1
DIGIPEAT 0 0 ^WIDE[3-7]-[1-7]$|^TEST$ ^WIDE[12]-[12]$ TRACE
IGSERVER noam.aprs2.net
IGLOGIN YOURCALLSIGN 9147
PBEACON sendto=IG delay=0:30 every=60:00 symbol="igate" overlay=R lat=41^20.68734N long=88^28.39224W

One of the things that I don’t understand is how an instance running on a raspberry pi with two changes knows how to route traffic from Channel 0 (ie 1200 baud )
to Channel 1 ( 9600 baud ).

See: 4.5 A Bi-Directional Cross-band Digipeater in this manual
https://thelifeofkenneth.com/aprx/aprx-manual.pdf

At our tower site, we have a pair of radios one on 145.610 and 147.555 and a Raspberry PI running a DRAWS with 2 channels.
Our State Packet Team insists on 145.610 running 1200baud, and only Digipeating, FBB Access and Winlink Client access.
For the tower site
KB9SZK-7 X.25
KB9SZK-10 Winlink RMS (Telnet access to WinLink CMS servers)
KB9SZK-1 APRS and FBB
The Tower site has a Sprint internet connection to provide APRS Server access and Winlink Telnet access.

At our EOC we are running 147.555, a HF rig for ARDOP access to Winlink, and a raspberry PI

For the EOC site 9600baud on 147.555
KB9SZK-8 X.25
KB9SZK-11 Winlink RMS (Telnet access to WinLink CMS servers or ARDOP access via HF if needed)
KB9SZK-2 APRS and FBB

Questions are:
How do we configure routing such that a station connecting on 145.610 at 1200baud, digipeats the packets on the 147.555 so that the the station can find the FBB server at the EOC.

Need more detailed explanation (maybe a diagram) of what you want to do. Just describe a
scenario. I believe Uronode will provide the functionality that you want.

How do we limit the Raspberry PI’s so that we don’t have APRS traffic on the 145.610 channel. ie the Tower Site Raspberry PI.

And then how do we configure the FBB that is in the build. Can we install FBB so messages are automatically copied from the EOC raspberry PI to the Tower Site Raspberry PI,

There are ways available to sync BBS's. I haven't done it but I know
it's possible.

Again Thanks!!!!
An Extra Thank you for your efforts. Most do not have any idea of how hard you have to work to keep up with the masses. :)

..jpw J P Watters
KC9KKO
Morris, IL

On Oct 9, 2019, at 11:27 PM, Basil Gunn <basil@...> wrote:

I think you want a second ax.25 channel, which should already be
configured.

In a console run this:

ifconfig
or
ip a show

You should see ax0, your first ax.25 channel on the left connector & ax1
the second ax.25 channel on the right connector.
You need to set the baud rate you want (9600) in /etc/direwolf.conf
under "Channel 1 Properties". Change the MODEM 1200 line to MODEM 9600.

By default the left & right channels are always configured so it
shouldn't be too difficult to get the second channel going. The hard
part is that 9600 baud packet requires you to set deviation more
precisely than 1200 baud packet. Having access to a service monitor
helps.

Let me know how you make out.

/Basil

J P Watters via Groups.Io <kc9kko@...> writes:

Our club has a DRAWS using a single radio that we have configured to
run as a digipeater and Winlink X.25 access using telnet to the CMS
servers.

The single radio is configured for 1200 baud X.25 Packet Digipeating
with access to a Winlink RMS. Our affiliation with the statewide
packet network limits that channel to 1200 baud digipeating and
Winlink X.25 access. They also exclude APRS data on that channel. We
can specify in the Winlink client a VIA to connect to another site
with HF access to Winlink.

We would like to add a second radio on the second DRAWS interface to
support 9600 baud, APRS Data and possibly a FBB instance.

Is there information on adding a second interface?

..jpw J P Watters
KC9KKO
Morris, IL





Re: Adding a second radio

Basil Gunn
 

Hi J P,

Thank you for your reply. John Hays means well, but his reply did not
get me the traction that I expected.
John & I have 2 different philosophies regarding packet. He gave advice
on how to do everything in direwolf and I like to keep direwolf as a
sound modem only & use the AX.25 functionality of Linux.
John has done some great work on configuring virtual sound card interfaces so
that you can do 1200 baud & 9600 baud packet on the same radio.

And Yes I have a service monitor to set the deviation. It makes it alot easier :)
Yep.

Another Topic will be the FBB that is installed as part of the BETA14
Build. Where is the FBB documentation? The FBB install script?
So this is a project I briefly got working but don't use day to day. I
think BBS are useful so that is on my list of things for permanent
infrastructure. The latest version (7.08-beta8 from SourceForge) is
built & installed on the image.

The documentation I have been using is here:
https://sourceforge.net/projects/linfbb/files/

BTW we edited the URONODE config file and ran the install, an it appears to work.
Great to hear!

I think that direwolf.conf edits are all that are needed.
Depends on your philosophy.

How do we enable the APRS Gateway? I think it is just the list of attributes for “Channel 1"
Only on the second channel?
I use APRX for APRS embedded systems. ie. no monitor
See: 4.5 A Bi-Directional Cross-band Digipeater in this manual
https://thelifeofkenneth.com/aprx/aprx-manual.pdf

You can just use Direwolf but I won't be able to help you with that. The
direwolf documentation is very good & if you go that route I recommend
you read the entire manual carefully.

Our Statewide only will permit digipeating, winlink, FBB messaging on the first Channel. (FBB install another challenge that we will make later.)
They only support 1200baud on the first channel. Our club will support 9600baud on the other channel.

ADEVICE plughw:CARD=udrc,DEV=0
ARATE 48000
ACHANNELS 2
CHANNEL 0
MYCALL YOURCALLSIGN-7
MODEM 1200
PTT GPIO 12
CHANNEL 1
MODEM 9600
PTT GPIO 12
MYCALL YOURCALLSIGN-10
AGWPORT 8000
KISSPORT 8001
PBEACON delay=1 every=10 overlay=S symbol="digi" lat=41^20.68734N long=88^28.39224W power=100 height=20 gain=6 comment="UDRC" via=WIDE1-1,WIDE2-1
DIGIPEAT 0 0 ^WIDE[3-7]-[1-7]$|^TEST$ ^WIDE[12]-[12]$ TRACE
IGSERVER noam.aprs2.net
IGLOGIN YOURCALLSIGN 9147
PBEACON sendto=IG delay=0:30 every=60:00 symbol="igate" overlay=R lat=41^20.68734N long=88^28.39224W

One of the things that I don’t understand is how an instance running on a raspberry pi with two changes knows how to route traffic from Channel 0 (ie 1200 baud )
to Channel 1 ( 9600 baud ).
See: 4.5 A Bi-Directional Cross-band Digipeater in this manual
https://thelifeofkenneth.com/aprx/aprx-manual.pdf

At our tower site, we have a pair of radios one on 145.610 and 147.555 and a Raspberry PI running a DRAWS with 2 channels.
Our State Packet Team insists on 145.610 running 1200baud, and only Digipeating, FBB Access and Winlink Client access.
For the tower site
KB9SZK-7 X.25
KB9SZK-10 Winlink RMS (Telnet access to WinLink CMS servers)
KB9SZK-1 APRS and FBB
The Tower site has a Sprint internet connection to provide APRS Server access and Winlink Telnet access.

At our EOC we are running 147.555, a HF rig for ARDOP access to Winlink, and a raspberry PI

For the EOC site 9600baud on 147.555
KB9SZK-8 X.25
KB9SZK-11 Winlink RMS (Telnet access to WinLink CMS servers or ARDOP access via HF if needed)
KB9SZK-2 APRS and FBB

Questions are:
How do we configure routing such that a station connecting on 145.610 at 1200baud, digipeats the packets on the 147.555 so that the the station can find the FBB server at the EOC.
Need more detailed explanation (maybe a diagram) of what you want to do. Just describe a
scenario. I believe Uronode will provide the functionality that you want.

How do we limit the Raspberry PI’s so that we don’t have APRS traffic on the 145.610 channel. ie the Tower Site Raspberry PI.

And then how do we configure the FBB that is in the build. Can we install FBB so messages are automatically copied from the EOC raspberry PI to the Tower Site Raspberry PI,
There are ways available to sync BBS's. I haven't done it but I know
it's possible.

Again Thanks!!!!
An Extra Thank you for your efforts. Most do not have any idea of how hard you have to work to keep up with the masses. :)

..jpw J P Watters
KC9KKO
Morris, IL

On Oct 9, 2019, at 11:27 PM, Basil Gunn <@basil860> wrote:

I think you want a second ax.25 channel, which should already be
configured.

In a console run this:

ifconfig
or
ip a show

You should see ax0, your first ax.25 channel on the left connector & ax1
the second ax.25 channel on the right connector.
You need to set the baud rate you want (9600) in /etc/direwolf.conf
under "Channel 1 Properties". Change the MODEM 1200 line to MODEM 9600.

By default the left & right channels are always configured so it
shouldn't be too difficult to get the second channel going. The hard
part is that 9600 baud packet requires you to set deviation more
precisely than 1200 baud packet. Having access to a service monitor
helps.

Let me know how you make out.

/Basil

J P Watters via Groups.Io <kc9kko=mac.com@groups.io> writes:

Our club has a DRAWS using a single radio that we have configured to
run as a digipeater and Winlink X.25 access using telnet to the CMS
servers.

The single radio is configured for 1200 baud X.25 Packet Digipeating
with access to a Winlink RMS. Our affiliation with the statewide
packet network limits that channel to 1200 baud digipeating and
Winlink X.25 access. They also exclude APRS data on that channel. We
can specify in the Winlink client a VIA to connect to another site
with HF access to Winlink.

We would like to add a second radio on the second DRAWS interface to
support 9600 baud, APRS Data and possibly a FBB instance.

Is there information on adding a second interface?

..jpw J P Watters
KC9KKO
Morris, IL


Re: Adding a second radio

jdfiberops@...
 

Basil,

To take this one step further, can you add a HF rig as a second radio running ARDOP with the first radio running ax.25?

Thank you,
Jeff, N9JXN

On Oct 9, 2019, at 11:27 PM, Basil Gunn <@basil860> wrote:


I think you want a second ax.25 channel, which should already be
configured.

In a console run this:

ifconfig
or
ip a show

You should see ax0, your first ax.25 channel on the left connector & ax1
the second ax.25 channel on the right connector.
You need to set the baud rate you want (9600) in /etc/direwolf.conf
under "Channel 1 Properties". Change the MODEM 1200 line to MODEM 9600.

By default the left & right channels are always configured so it
shouldn't be too difficult to get the second channel going. The hard
part is that 9600 baud packet requires you to set deviation more
precisely than 1200 baud packet. Having access to a service monitor
helps.

Let me know how you make out.

/Basil

J P Watters via Groups.Io <kc9kko=mac.com@groups.io> writes:

Our club has a DRAWS using a single radio that we have configured to
run as a digipeater and Winlink X.25 access using telnet to the CMS
servers.

The single radio is configured for 1200 baud X.25 Packet Digipeating
with access to a Winlink RMS. Our affiliation with the statewide
packet network limits that channel to 1200 baud digipeating and
Winlink X.25 access. They also exclude APRS data on that channel. We
can specify in the Winlink client a VIA to connect to another site
with HF access to Winlink.

We would like to add a second radio on the second DRAWS interface to
support 9600 baud, APRS Data and possibly a FBB instance.

Is there information on adding a second interface?

..jpw J P Watters
KC9KKO
Morris, IL


Re: Adding a second radio

Basil Gunn
 

I think you want a second ax.25 channel, which should already be
configured.

In a console run this:

ifconfig
or
ip a show

You should see ax0, your first ax.25 channel on the left connector & ax1
the second ax.25 channel on the right connector.
You need to set the baud rate you want (9600) in /etc/direwolf.conf
under "Channel 1 Properties". Change the MODEM 1200 line to MODEM 9600.

By default the left & right channels are always configured so it
shouldn't be too difficult to get the second channel going. The hard
part is that 9600 baud packet requires you to set deviation more
precisely than 1200 baud packet. Having access to a service monitor
helps.

Let me know how you make out.

/Basil

J P Watters via Groups.Io <kc9kko=mac.com@groups.io> writes:

Our club has a DRAWS using a single radio that we have configured to
run as a digipeater and Winlink X.25 access using telnet to the CMS
servers.

The single radio is configured for 1200 baud X.25 Packet Digipeating
with access to a Winlink RMS. Our affiliation with the statewide
packet network limits that channel to 1200 baud digipeating and
Winlink X.25 access. They also exclude APRS data on that channel. We
can specify in the Winlink client a VIA to connect to another site
with HF access to Winlink.

We would like to add a second radio on the second DRAWS interface to
support 9600 baud, APRS Data and possibly a FBB instance.

Is there information on adding a second interface?

..jpw J P Watters
KC9KKO
Morris, IL


Re: Adding a second radio

 

You can add the second channel in direwolf.conf

Similar to udrc-ii


Use DRAWS™ Manager to set left and right radio channels. 

On Wed, Oct 9, 2019, 19:52 J P Watters via Groups.Io <kc9kko=mac.com@groups.io> wrote:
Our club has a DRAWS using a single radio that we have configured to run as a digipeater and Winlink X.25 access using telnet to the CMS servers.

The single radio is configured for 1200 baud X.25 Packet Digipeating with access to a Winlink RMS. Our affiliation with the statewide packet network limits that channel to 1200 baud digipeating and Winlink X.25 access. They also exclude APRS data on that channel. We can specify in the Winlink client a VIA to connect to another site with HF access to Winlink. 

We would like to add a second radio on the second DRAWS interface to support 9600 baud, APRS Data and possibly a FBB instance. 

Is there information on adding a second interface?

..jpw J P Watters
KC9KKO
Morris, IL


Adding a second radio

J P Watters <kc9kko@...>
 

Our club has a DRAWS using a single radio that we have configured to run as a digipeater and Winlink X.25 access using telnet to the CMS servers.

The single radio is configured for 1200 baud X.25 Packet Digipeating with access to a Winlink RMS. Our affiliation with the statewide packet network limits that channel to 1200 baud digipeating and Winlink X.25 access. They also exclude APRS data on that channel. We can specify in the Winlink client a VIA to connect to another site with HF access to Winlink. 

We would like to add a second radio on the second DRAWS interface to support 9600 baud, APRS Data and possibly a FBB instance. 

Is there information on adding a second interface?

..jpw J P Watters
KC9KKO
Morris, IL


Re: NWDR14 image release announcement #beta #support

K4KDR
 

Thanks a million for the secondary download location, William.

Pulled down a copy and just booted the Pi-3 / DRAWS to take a look and make sure I had followed the correct setup sequence.  Looks like the DRAWS is recognized & all ready to use.

Many thanks to Basil for putting v14 together!

Hopefully I won't fall too far behind, but for now I'll continue with the card I have fully setup from the last v13 image.  With everything configured & working so perfectly, I just want to keep using it as-is for the moment.  I've manually installed or configured the latest versions of everything I use (Direwolf, PAT Winlink for ax25 & ARDOP, JS8Call, WSJTx, and all the other stuff), so I really don't want to re-do everything on a new system at the moment.  I like to stay current as much as everyone else, but it's so nice to have a good portable system that "just works".

Appreciate everyone's effort on the project!

-Scott,  K4KDR

===================


On Mon, Oct 7, 2019 at 11:24 PM William Franzin <wfranzin@...> wrote:
Just downloaded this myself and it took a while so cloned it here: https://tor1.radiowaves.ca/nwdr14.zip

This is a Digital Ocean virtual in Toronto, set the limit at 900GB so go nuts. It gave me 42MB/sec to home.


Re: NWDR14 image release announcement #beta #support

 

As a reminder. 

Basil puts together these images as a favor and courtesy to the community.  NW Digital Radio is not the author of Linux/Raspbian or any of the applications that are preloaded on the beta images. Support for Linux/Raspbian, applications, and configurations belong to the respective authors and their support mechanisms. Some of which are listed via DRAWS™ Manager.

If you appreciate Basil's efforts in this regard, please let him know.  If you wish to build your own images, you are free to do so, but neither NW Digital Radio nor any of its team members are under any obligation to provide advice or support for making or debugging those images.

From http://nwdigitalradio.com/draws/
"What technical support is provided for DRAWS?

NW Digital Radio supports the DRAWS HAT hardware and its driver software.  All other applications are provided on an ‘as is’ basis, with support for configuration and operation of those applications provided by the authors and user community for those applications.  NW Digital Radio’s DRAWS HAT driver and configuration is Open Source Software and is free for amateur radio use."



John D. Hays
Director


Re: NWDR14 image release announcement #beta #support

Basil Gunn
 

David C Jenner - K7DCJ via Groups.Io <djenner8=mac.com@groups.io> writes:

Basil,

I have a Raspbian Buster RPi 4 running the desired kernel. I want to
install whatever is included in the standard DRAWS image over this.
Not sure why you would want to do this as the provided image has already
done the heavy lifting of the install but if you really want to, look at
this file for instructions:
https://github.com/nwdigitalradio/n7nix/blob/master/docs/CORE_INSTALL.md

Building an image will take a few hours to a half a day depending on how many
problems you run into. Then a few days of testing to confirm it works
the way you think it does.

I suspect there is no file n7nix/config/image_install.sh installed
anywhere on my system. Correct me if I a wrong, please.
Correct. Read CORE_INSTALL.md link above.

Your instructions in the Wiki under "Make your own Raspberry Pi image"
stop after creating the Raspbian image, much as I have done. There
are no instructions on how to proceed after that.
Correct. I really do not want to support making your own image.

In an earlier post I saw instructions that may be what I am looking
for, but they were prefaced by "off the top of my head." If those are
the instructions, I would prefer that they are a bit more verified and
part of the official Wiki instructions before I make trouble.
The CORE_INSTALL.md contains (most of) the instructions I use to build
an image. It is not as straight forward as you think. ie. gpsd in the
Raspbian repository has problems so I build the latest from source. Also
in order to build FLdigi you must increase swap space. There are
probably another half dozen or so things that you need to take care
of. This is why there is a provided image.

Having said all that I understand the reasoning behind making a more
minimal image for things that do not require a window manager like an
APRS digipeater or an RMS Gateway or if you just want to run HF programs
like js8call.

If you look at the config/image_install.sh script you should be able to
pick the things you want in an image that fits your requirements. If you
go this route please know I most likely will not answer your questions
but it is a forum so others might.

/Basil


Re: image update failure

Basil Gunn
 

John Spoonhower <jpspoonhower@...> writes:

Basil,
again thanks for the help.
I didn't bother to download the last image. I found the problem is fixed by
simply using alsamixer and the settings you mention.
Glad to hear you have things working!!

The ./btest.sh script runs OK (packets seen on aprs.fi) too on port
udrc 1.
I originally made this script as a quick test for packet using any of
the hats UDRC/UDRC II/DRAWS.

I still have to fix up the location finding via gps as on the udrc II I
have a BU-353S4 usb gps not the draws device. Although gpsd is running just
fine, the position data parsing provided in btest.sh is looking for NMEA
sentences, while I am fairly certain my device is not NMEA by default.
I wanted the btest.sh script to work for UDRC/UDRC II hats ie. without
the on board GPS so I just conditional'ed the GPS stuff based on hat
type. Please hack this script to make it do what you want. I have both
gpsd & nmea functions in that script.

After that I will takeon the APRX install....
Yes, APRX is the way to go for APRS gating/digipeating.

73, John

On Sun, Oct 6, 2019 at 8:02 PM Basil Gunn <@basil860> wrote:


John,
I verified that the following method also works.
Copy the following alsa control values from your working image,
you can read them by running alsa-show.sh.

LO Driver Gain
PCM
ADC Level

Boot your new image and run:
cd
cd bin
sudo su
./setalsa-udrc-din6.sh

Now run alsamixer and set LO Driver Gain, PCM & ADC Level. To make
things more convenient you could use an editor and set the 3 values in
the setalsa-udrc-din6.sh script. They are the first 3 levels set.

Verify by running alsa-show.sh one more time.

/Basil

John Spoonhower <jpspoonhower@...> writes:

Thanks. I will give this a try.
On a somewhat different topic...I notice in beacmin.sh that in the
comments
aprs symbols are listed. I do not see sending a symbol implemented in
this
script. Is this fairly straightforward to add ?

On Sun, Oct 6, 2019 at 11:17 AM Basil Gunn <@basil860> wrote:


I used a new image (nwdr14) with a UDRC II and it worked fine. I will
release that image today. The only thing I changed from the scripts was
to select discriminator out using the alsa commands. You can do it from
the alsamixer gui as well.

sset 'IN1_L to Left Mixer Positive Resistor' '10 kOhm'
sset 'IN1_R to Right Mixer Positive Resistor' '10 kOhm'

Since you have a working configuration why not save it to a file &
compare it with the configuration you are using with the new image.
ie. save /boot/config.txt, alsa-show, ax25-status -d

You could try a transmit test to see what that gives you
cd
cd n7nix/debug
./btest.sh -P udr1 -p

Remember that on a UDRC II the mDin6 connector is port 1 not port 0.

I notice that you have manually edited /boot/config.txt. I did not
manually edit any files for my UDRC II test.

/Basil


Re: image update failure

John Spoonhower
 

Basil,
again thanks for the help.
I didn't bother to download the last image. I found the problem is fixed by simply using alsamixer and the settings you mention.
The ./btest.sh script runs OK (packets seen on aprs.fi) too on port udrc 1. I still have to fix up the location finding via gps as on the udrc II I have a BU-353S4 usb gps not the draws device. Although gpsd is running just fine, the position data parsing provided in btest.sh is looking for NMEA sentences, while I am fairly certain my device is not NMEA by default.
After that I will takeon the APRX install....

73, John


On Sun, Oct 6, 2019 at 8:02 PM Basil Gunn <basil@...> wrote:

John,
I verified that the following method also works.
Copy the following alsa control values from your working image,
you can read them by running alsa-show.sh.

LO Driver Gain
PCM
ADC Level

Boot your new image and run:
cd
cd bin
sudo su
./setalsa-udrc-din6.sh

Now run alsamixer and set LO Driver Gain, PCM & ADC Level.  To make
things more convenient you could use an editor and set the 3 values in
the setalsa-udrc-din6.sh script. They are the first 3 levels set.

Verify by running alsa-show.sh one more time.

/Basil

John Spoonhower <jpspoonhower@...> writes:

> Thanks. I will give this a try.
> On a somewhat different topic...I notice in beacmin.sh that in the comments
> aprs symbols are listed. I do not see sending a symbol implemented in this
> script. Is this fairly straightforward to add ?
>
> On Sun, Oct 6, 2019 at 11:17 AM Basil Gunn <basil@...> wrote:
>
>>
>> I used a new image (nwdr14) with a UDRC II and it worked fine. I will
>> release that image today. The only thing I changed from the scripts was
>> to select discriminator out using the alsa commands. You can do it from
>> the alsamixer gui as well.
>>
>> sset 'IN1_L to Left Mixer Positive Resistor' '10 kOhm'
>> sset 'IN1_R to Right Mixer Positive Resistor' '10 kOhm'
>>
>> Since you have a working configuration why not save it to a file &
>> compare it with the configuration you are using with the new image.
>> ie. save /boot/config.txt, alsa-show, ax25-status -d
>>
>> You could try a transmit test to see what that gives you
>> cd
>> cd n7nix/debug
>> ./btest.sh -P udr1 -p
>>
>> Remember that on a UDRC II the mDin6 connector is port 1 not port 0.
>>
>> I notice that you have manually edited /boot/config.txt. I did not
>> manually edit any files for my UDRC II test.
>>
>> /Basil




Re: NWDR14 image release announcement #beta #support

William Franzin
 

Just downloaded this myself and it took a while so cloned it here: https://tor1.radiowaves.ca/nwdr14.zip

This is a Digital Ocean virtual in Toronto, set the limit at 900GB so go nuts. It gave me 42MB/sec to home.


Re: NWDR14 image release announcement #beta #support

David C Jenner - K7DCJ
 

Basil,

I have a Raspbian Buster RPi 4 running the desired kernel. I want to install whatever is included in the standard DRAWS image over this.

I suspect there is no file n7nix/config/image_install.sh installed anywhere on my system. Correct me if I a wrong, please.

Your instructions in the Wiki under "Make your own Raspberry Pi image" stop after creating the Raspbian image, much as I have done. There are no instructions on how to proceed after that.

In an earlier post I saw instructions that may be what I am looking for, but they were prefaced by "off the top of my head." If those are the instructions, I would prefer that they are a bit more verified and part of the official Wiki instructions before I make trouble.

Thanks,
Dave


Re: NWDR14 image release announcement #beta #support

Basil Gunn
 

Dave,

The "DRAWS specific software" are two codec drivers that are in the Linux
kernel and an overlay that loads at boot time.
The drivers are:
snd_soc_tlv320aic32x4_i2c
snd_soc_tlv320aic32x4

The overlays are either: udrc.dtbo or draws.dtbo depending on which hat
you have installed.

While there is some specific configuration required to take advantage of
the DRAWS hat gps & A/D converter all the other software provided in the
image are scripts that install or configure other software that could be
used by any sound card or serial/i2c TNC.

Most everything that I do to create an image I do with a script. See
n7nix/config/image_install.sh. That's only mostly true because there is
always some futzing around with a new Raspbian distribution to get some
things to work properly.

Perhaps you could explicitly state what you want to do and I can provide
some guidance on how to get there.
/Basil n7nix

David C Jenner - K7DCJ via Groups.Io <djenner8=mac.com@groups.io> writes:

Basil,

Please add how to install this on one's own RPi 4 Raspbian image (with
proper kernel). Your instructions at "Make your own Raspberry Pi image"
seem to end before adding the DRAWS-specific software.

Thanks,
Dave


Re: NWDR14 image release announcement #beta #support

David C Jenner - K7DCJ
 

Basil,

Please add how to install this on one's own RPi 4 Raspbian image (with proper kernel). Your instructions at "Make your own Raspberry Pi image" seem to end before adding the DRAWS-specific software.

Thanks,
Dave

On 10/7/19 9:30 AM, Basil Gunn wrote:
Before you update your image, please capture any configuration changes
you might have made like current alsamixer settings.
Run alsa-show.sh & make a copy of result. Note a minimum
microSD card size of at least 16GB is recommended.
Latest RPi image current_image.zip has been updated to nwdr14.zip at
this location: http://images.nwdigitalradio.com/downloads
Please follow the "Getting Started Guide" from the UDRC Wiki.
https://nw-digital-radio.groups.io/g/udrc/wiki/DRAWS%3A-Getting-Started
This image has a Linux kernel (4.19.66) that includes Anna's main line
TI tlv320aic device driver that supports the UDC / UDRC II & DRAWS hats.
This means you can more easily make your own images.
On first boot, if you have an attached monitor, you will see the piwiz
configuration screen currently used on new Raspbian images.
If you are using a Raspberry Pi 4 and your monitor is blank then add
this to /boot/config.txt to use HDMI safe mode.
hdmi_safe=1
If you have any problems please include the output of script showudrc.sh
with your problem description.
Changes since last release
* Image NWDR14 release
* Use Raspbian Buster (Debian 10) with main line tlv320aic driver as image base
* Compass is deprecated
* Updated all HF programs
* Updated 'Getting Started' guide
* Fix permission problem when installing iptables
* Made beacon scripts independent of gps.
* Add script to easily switch between 1200 & 9600 baud packet.
* Add script to change RPi led trigger method
8728704 - n7nix, 17 hours ago : Clean-up order of statements so comments make sense & facilitate comparing with other scripts.
93f8323 - n7nix, 18 hours ago : Move comment to where it makes more sense.
f4a64af - n7nix, 18 hours ago : Add note to verify ALSA settings. Take out count of reboots.
b2ad1db - n7nix, 22 hours ago : Add more description about AFOUT & DISCOUT, input signals to UDRC/DRAWS.
48fc21f - n7nix, 22 hours ago : Wordsmith a comment.
d00c948 - n7nix, 22 hours ago : Rearrange some lines to facilitate comparison with other setalsa scripts.
8314cb2 - n7nix, 24 hours ago : Add a note regarding UDRC II mDin6 channel.
c370052 - n7nix, 25 hours ago : Change initial config notes to include piwiz startup.
8736e68 - n7nix, 25 hours ago : Change comment to reflect direction of input.
6f1412c - n7nix, 3 days ago : Set execute permissions.
0108ce7 - n7nix, 3 days ago : Add help option to display usage.
ac00a5c - n7nix, 3 days ago : Only use gps if DRAWS hat is detected.
722968f - n7nix, 3 days ago : Update RPi model numbers & only display gps info if DRAWS hat detected.
6541719 - n7nix, 3 days ago : Parameterize led number.
c34eaf4 - n7nix, 7 days ago : Fix comments to describe reality.
276babe - n7nix, 7 days ago : Always run chk_bootcfg.sh from core_config.sh script to set overlay name.
7246656 - n7nix, 7 days ago : Wordsmith message on running claws_install for the first time.
6c0a847 - n7nix, 7 days ago : Fix problem of installing claws-mail & dovecot
e124819 - n7nix, 8 days ago : Fix bug, dbgecho was not defined.
9f0ea62 - n7nix, 8 days ago : Fix documentation regarding pluimap which is deprecated.
be96477 - n7nix, 8 days ago : Take out installing pluimap as an option.
f01a7af - n7nix, 8 days ago : Update getting started configuration.
1d82cae - n7nix, 9 days ago : Make beacon scripts independent of gpsd.
404d155 - n7nix, 9 days ago : Add display of current cpu temperature.
9cebc0f - n7nix, 9 days ago : Fix variable name change.
355f65c - n7nix, 9 days ago : Update to be compatible with latest Linux kernel in buster.
04ebd94 - n7nix, 13 days ago : libncurses.so.5 was not getting installed. Added libncurses5 to essential packages to install.
e9bebbc - n7nix, 2 weeks ago : Use canned lat/lon if can't read gps data.
ddafa49 - n7nix, 2 weeks ago : Fix failure due to no tmp directory.
888cb15 - n7nix, 3 weeks ago : Fix script syntax error when checking user:group of a directory
e2faf05 - n7nix, 3 weeks ago : Build fldigi before other FL apps.
a303dd4 - n7nix, 3 weeks ago : Fix xastir install script file name, install draws-manager when building image.
6ebaafa - n7nix, 3 weeks ago : Add dtoverlay= to flush any overlays loaded from eeprom.
c5991da - n7nix, 3 weeks ago : Add script to enlarge swap size before doing an image install.
df88d9c - n7nix, 3 weeks ago : Put HF program install at end of install.
c24b75a - n7nix, 3 weeks ago : Add reminder to use script to save all console output.
d95763e - n7nix, 3 weeks ago : Fix permissions bug when creating 70-ipv4.ax25 file.
14b6de7 - n7nix, 3 weeks ago : Fix RMS Gateway directory link on install
52a9aae - n7nix, 3 weeks ago : Fix downloading nodejs source, no need to do this.
dfcd672 - n7nix, 3 weeks ago : Increase swap size to 1024M
d931443 - n7nix, 3 weeks ago : Check swap size before doing an image build.
699637b - n7nix, 3 weeks ago : Fix building in wrong directory problem.
78961af - n7nix, 3 weeks ago : Fix FL apps check were app was downloaded but source not built.
1ec20ae - n7nix, 3 weeks ago : Update names of required packages.
669b64e - n7nix, 3 weeks ago : Get rid of references to compass.
de0a58a - n7nix, 4 weeks ago : Fix wrong source directory when only building fldigi.
ddddd7d - n7nix, 4 weeks ago : Rebuild fldigi as a default.
e7773d8 - n7nix, 4 weeks ago : Update FL app version numbers to current.
5a886c1 - n7nix, 4 weeks ago : Display gpsd version number that will be downloaded.
39ba260 - n7nix, 5 weeks ago : Fix mis-spelled variable name.
1f019d6 - n7nix, 5 weeks ago : Add easy way to get RPi temperature & throttling history.
4d8eaae - n7nix, 5 weeks ago : Display msg when disabling service, include RPi 4 in console output.
be92b5a - n7nix, 5 weeks ago : Include RPi 4 in echo statement.
9e7fa62 - n7nix, 5 weeks ago : Change directory owner to current user to build Xastir without being root.
fcf5042 - n7nix, 5 weeks ago : Detect & fix direwolf process running, gpio 7 mode ALT0.
0574b22 - n7nix, 5 weeks ago : Take out tlv320 driver conflict check.
a2234a6 - n7nix, 5 weeks ago : Add ax25-reset script to bin directory.
5212b4f - n7nix, 5 weeks ago : Make it more obvious how to initially start up rainloop.
b84cf95 - n7nix, 6 weeks ago : Make kissparms more aggressive for 9600 baud.
6ed7390 - n7nix, 6 weeks ago : Knock received signal down for 9600 baud.
0057400 - n7nix, 6 weeks ago : Fix path error.
5629dcb - n7nix, 6 weeks ago : Fix spelling.
81aaffd - n7nix, 7 weeks ago : Add script to easily switch between 1200 & 9600 baud packet.
b5bef04 - n7nix, 7 weeks ago : Conditional ALSA settings based on 9600 baud switch.
2518b53 - n7nix, 7 weeks ago : Fix broken relative url links.
6157e4a - n7nix, 7 weeks ago : Add over temperature CPU throttle indicator.
f982f79 - n7nix, 7 weeks ago : Support for 9600 baud.
17991a0 - n7nix, 7 weeks ago : Added for 9600 baud configuration checking.
d156136 - n7nix, 8 weeks ago : Add bc to required build tools for direwolf, add sensor support.
853fe9d - n7nix, 8 weeks ago : Display message when installing sensor support.
86367f1 - n7nix, 8 weeks ago : Add libudev-dev package as a new build requirement package for direwolf.
8dc1cb4 - n7nix, 8 weeks ago : Fix DireWolf version, just dev.
267a51c - n7nix, 8 weeks ago : Fix lingering PHP 7.0 reference.
8fd52e5 - n7nix, 8 weeks ago : Fix php version number for Debian buster.
b08b07e - n7nix, 8 weeks ago : Merge branch 'master' of https://github.com/nwdigitalradio/n7nix
ffa9612 - Basil Gunn, 8 weeks ago : Merge pull request #5 from sgtsmall/master
0f34f49 - n7nix, 8 weeks ago : Install required build packages.
fce35f4 - n7nix, 8 weeks ago : Update version numbers for HF programs.
254daea - n7nix, 8 weeks ago : Create symbolic link to /usr/local/etc/rmsgw & fix config part of build.
ebb6c22 - n7nix, 10 weeks ago : Setup permissions on target source directory so sudo is not required for wget.
755fbaf - n7nix, 10 weeks ago : Get rid of excess debug statement displaying gps version numbers.
b09062d - n7nix, 10 weeks ago : Set proper permissions on channels & version aging files in 'stat' directory.
94a13e8 - Alex Stewart, 10 weeks ago : update install script plus initial checking for new version on yaac site
c49b38b - Alex Stewart, 10 weeks ago : download to usr/local/src and adjust case for YAAC dir acording to ka2ddo site
1405d09 - Alex Stewart, 2 months ago : Add xterm to yaac for desktop icon
5d9aa9b - Alex, 2 months ago : fix latdir and londir in beacon_msg
a8ea76b - n7nix, 3 months ago : Fix version # is only major.minor number & permission problems.
1165bfc - n7nix, 3 months ago : Check for 3rd version digit is numeric.
d797551 - n7nix, 3 months ago : Install wide version (w) of libncureses as well.
10dcfe8 - n7nix, 3 months ago : If draws sensor file does not exist, create it.
16f079a - n7nix, 3 months ago : Pull latest version of Xastir when checking version.
c44ffb6 - n7nix, 3 months ago : Run apt-get in quiet mode
5beb627 - n7nix, 3 months ago : Install uppdates for new image using 4.19 kernel.
32c4be7 - n7nix, 3 months ago : Fix white space.
182f45d - n7nix, 3 months ago : Update ardop install script.
49efdc9 - n7nix, 3 months ago : Update RPi revision numbers for Pi 4B
74d25bd - n7nix, 3 months ago : Advance uronode install functionality.
e62182c - n7nix, 3 months ago : Fix display of correct program name.
db36e46 - n7nix, 3 months ago : Fix numeric conditional check.
07e697a - n7nix, 3 months ago : Make white space consistent for easier comparison.
7c24671 - n7nix, 3 months ago : Update xastir current version number.
f85cc01 - n7nix, 3 months ago : Add entry for Kenwood TM-281a
22d17f4 - n7nix, 3 months ago : display status of dovecot service.
47ec99e - n7nix, 3 months ago : Add display of GPS string for number of satellites in view.
f513419 - n7nix, 4 months ago : Update usage function with gpio on/off
e905122 - n7nix, 4 months ago : Change comments to be consistent to usage with js8call.
d32cc98 - n7nix, 4 months ago : Move ptt_ctrl.sh script to local bin directory.
be17f6b - n7nix, 4 months ago : Add parsing of arguments on/off with no dash
3dfe043 - n7nix, 4 months ago : Add toggle option, to toggle PTT state
5bdc095 - n7nix, 4 months ago : Add simple script to turn PTT on & off on both connectors.
9907d27 - n7nix, 4 months ago : Turn off upgrading packages & the kernel until all current patches to i2cbcm2835 & tlv320 drivers are accepted.
514f746 - n7nix, 4 months ago : Fix no split-channels directory found error.
128c29b - n7nix, 5 months ago : Add silent option to just update the gateway list file.
aa435f4 - n7nix, 5 months ago : Fix boolean flag to interrogate Winlink Web services.
a3bc3d6 - n7nix, 5 months ago : Update ChangeLog to reflect changes.
7b2f620 - n7nix, 5 months ago : Make prompt for keyboard input consistent.
22a48a3 - n7nix, 5 months ago : Make log file entry accurate.
e2d1861 - n7nix, 5 months ago : Use copy update to fix clobbering previously config'ed files.
139a075 - n7nix, 5 months ago : Set same AX25 port name in axports, ax25d.conf, channels.xml
2a72987 - n7nix, 5 months ago : Get port number from previous configured AX25 file, use parameterized SSID.
b6e95d8 - n7nix, 5 months ago : Fix comment to align with reality.
1604023 - n7nix, 5 months ago : Add no-pager option to systemctl call.
64e76f6 - n7nix, 5 months ago : Add entry for IC-7000
7a407fe - n7nix, 5 months ago : Add new dtoverlay entry for draws.
d773d7a - n7nix, 5 months ago : Add new dtoverlay entry for draws.