1. udrc@nw-digital-radio.groups.io
   Date   
KC9KKORE: Second interface

J P Watters <kc9kko@...>
 

John,

I saw that you referenced that you were able to run 9600 and or 1200 on a single radio interface. 

Can you refer us to the code, configuration that allows for on the fly switchng between Direwolf 9600/1200 baud packet speeds.

..jpw J P Watters
KC9KKO
Re: Eureka!!!! She works perfectly!!

Anthony Sutera
 

Hello John,

I am running WSJT-X.  I have one of the boards that had the issue.  I removed both caps.  The RX audio works pretty well (but not quite as sensitive as my signal link).  I have tried multiple sets of cables with and without Pin6.  I ran the alsa command for the 817, played with multiple setting in the draws manager including changing to the right hand port.  The best I can get out the of the TX audio are occasional TX reports WSPR.

Thank you,
Tony 

On Oct 13, 2019, at 4:34 PM, John D Hays - K7VE <john@...> wrote:

The FT-817 is a heavily tested radio with the UDRC and DRAWS boards.  There are built-in configurations on the image.

What application(s) are you trying to setup?

The proper way to set audio levels is using Draws™ Manager  -- the FT-817 settings assume the FT-817 internal menu settings are at default, so you may want to do a factory reset on the radio.  Also note that removing the squelch pin (PIN 6) in the cable is generally required on Yaesu radios.

Have you followed the recall notes?  If you have a newer board with the SMA coming out the same end as the power jack, you should review the thread and specifically https://nw-digital-radio.groups.io/g/udrc/message/3977



On Sun, Oct 13, 2019 at 3:10 PM <tsutera@...> wrote:
I have the 817 and have tried for weeks to get solid audio out to the radio.  Does anyone have a configuration that is really working ? If so please post it.  Thank you! Tony


--
John D. Hays
Kingston, WA
K7VE

 


?
smime.p7s

Re: Eureka!!!! She works perfectly!!

K4KDR
 

Appreciate all the info shared about this product!

I don't know about the FT-817, but my FT-857d works great with the latest DRAWS board using an un-modified 6-pin data cable (NO pins removed).  Just wanted to mention in case anyone with an FT-857d sees this post and wonders if they have to make any cable modifications.

-Scott,  K4KDR

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


On Sun, Oct 13, 2019 at 6:35 PM John D Hays - K7VE <john@...> wrote:
The FT-817 is a heavily tested radio with the UDRC and DRAWS boards.  There are built-in configurations on the image.

What application(s) are you trying to setup?

The proper way to set audio levels is using Draws™ Manager  -- the FT-817 settings assume the FT-817 internal menu settings are at default, so you may want to do a factory reset on the radio.  Also note that removing the squelch pin (PIN 6) in the cable is generally required on Yaesu radios.

Have you followed the recall notes?  If you have a newer board with the SMA coming out the same end as the power jack, you should review the thread and specifically https://nw-digital-radio.groups.io/g/udrc/message/3977



On Sun, Oct 13, 2019 at 3:10 PM <tsutera@...> wrote:
I have the 817 and have tried for weeks to get solid audio out to the radio.  Does anyone have a configuration that is really working ? If so please post it.  Thank you! Tony


--
John D. Hays
Kingston, WA
K7VE

 
Re: Eureka!!!! She works perfectly!!

John D Hays - K7VE
 

The FT-817 is a heavily tested radio with the UDRC and DRAWS boards.  There are built-in configurations on the image.

What application(s) are you trying to setup?

The proper way to set audio levels is using Draws™ Manager  -- the FT-817 settings assume the FT-817 internal menu settings are at default, so you may want to do a factory reset on the radio.  Also note that removing the squelch pin (PIN 6) in the cable is generally required on Yaesu radios.

Have you followed the recall notes?  If you have a newer board with the SMA coming out the same end as the power jack, you should review the thread and specifically https://nw-digital-radio.groups.io/g/udrc/message/3977



On Sun, Oct 13, 2019 at 3:10 PM <tsutera@...> wrote:
I have the 817 and have tried for weeks to get solid audio out to the radio.  Does anyone have a configuration that is really working ? If so please post it.  Thank you! Tony


--
John D. Hays
Kingston, WA
K7VE

 
Re: Eureka!!!! She works perfectly!!

Anthony Sutera
 

I have the 817 and have tried for weeks to get solid audio out to the radio.  Does anyone have a configuration that is really working ? If so please post it.  Thank you! Tony
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

Bill Vodall
 

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

John D Hays - K7VE
 

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 <basil@pacabunga.com> 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 <basil@pacabunga.com> 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

John D Hays - K7VE
 

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

John D Hays - K7VE
 

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@gmail.com> 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 <basil@pacabunga.com> 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@gmail.com> 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@pacabunga.com> 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
1301 - 1320 of 5368  
More
Home Messages Hashtags Wiki About Features Pricing Updates Terms Help Twitter