Date   

Re: Hamwan / DRAWS / Fiber / HF / RMS Gateway

Basil Gunn
 

If you are addressing this post to Alan Bush, I live in the same county
as Alan & will be going over to his QTH in the coming weeks to assist in
his install. When we do the Linux RMS Gateway install we will note any
discrepancies between what we did and what is already in the UDRC/DRAWS
Raspberry Pi Getting Started Guide here:
https://nw-digital-radio.groups.io/g/udrc/wiki/DRAWS%3A-Getting-Started
I have installed and support 3 active Linux RMS Gateways in our region
and am a maintainer of Linux RMS Gateway repository.

If you intend to use both channels of the DRAWS hat please describe
exactly what your expectations are for the functionality you
require. ie. state your requirements including baud rates &
frequencies. Also please tell us if you made your own hat-to-radio
cable(s) and which radio(s) you intend to use.

I recommend you install paclink-unix as well so you can get automated
status reports of your RMS Gateway.

/Basil n7nix


Chris Robinson KF6NFW DMR ID 3153250 <kf6nfw@...> writes:

Have you made any progress on this project?

I just got my DRAWS board in hand on a pi 3B+, and am about to dig in
on this very near identical setup you are attempting. If you have made
progress, i would be very interested in what you have accomplished.


Re: Hamwan / DRAWS / Fiber / HF / RMS Gateway

 

Have you made any progress on this project?

 I just got my DRAWS board in hand on a pi 3B+, and am about to dig in on this very near identical setup you are attempting. If you have made progress, i would be very interested in what you have accomplished.

 


Re: 13.8V? #12vsupply

Rico Abagnale, DG5BQ
 

Thanks,
I had in mind that DRAWS can just handle up to 12 volts. But in this case it makes a lot of hardware installation things a lot easier.

Once again thanks for your help


Re: 13.8V? #12vsupply

 

The.Pi USB power input is a nominal 5.1 VDC. Typical 'wall wart' USB supplies may have voltage drop who h in turn manifests in inconsistent operation of the Pi. This, and a single station power supply, is why DRAWS™ HAT has the 9-15 VDC power input.

One can use either to power both the Pi and DRAWS ™. 

On Mon, Oct 21, 2019, 06:32 Gayland Gump <kg7gcf@...> wrote:
I believe you want make sure you use the power input on the DRAWS and not the Pi itself.

Gayland
KG7GCF


On Mon, Oct 21, 2019 at 6:29 AM John D Hays - K7VE <john@...> wrote:
That will be just fine. Input voltage range is 9-15 VDC

On Mon, Oct 21, 2019, 06:28 Rico Abagnale <rico@...> wrote:
Hi group.

This might be a stupid question. But since I wouldn’t like to grill my D.R.A.W.S. I will post it anyway:
I saw a video where somebody presented D.R.A.W.S. In this presentation he recommended to attach a cable with a Powerpole connector to use the Powerpole distributor he uses for all the rig components to power the Raspberry Pi with the D.R.A.W.S.
Will this work? My Powerpole terminal delivers constant regulated 13.8 volts for my radios!

73 de Rico, DG5BQ


Re: 13.8V? #12vsupply

Gayland Gump
 

I believe you want make sure you use the power input on the DRAWS and not the Pi itself.

Gayland
KG7GCF


On Mon, Oct 21, 2019 at 6:29 AM John D Hays - K7VE <john@...> wrote:
That will be just fine. Input voltage range is 9-15 VDC

On Mon, Oct 21, 2019, 06:28 Rico Abagnale <rico@...> wrote:
Hi group.

This might be a stupid question. But since I wouldn’t like to grill my D.R.A.W.S. I will post it anyway:
I saw a video where somebody presented D.R.A.W.S. In this presentation he recommended to attach a cable with a Powerpole connector to use the Powerpole distributor he uses for all the rig components to power the Raspberry Pi with the D.R.A.W.S.
Will this work? My Powerpole terminal delivers constant regulated 13.8 volts for my radios!

73 de Rico, DG5BQ


Re: 13.8V? #12vsupply

 

That will be just fine. Input voltage range is 9-15 VDC


On Mon, Oct 21, 2019, 06:28 Rico Abagnale <rico@...> wrote:
Hi group.

This might be a stupid question. But since I wouldn’t like to grill my D.R.A.W.S. I will post it anyway:
I saw a video where somebody presented D.R.A.W.S. In this presentation he recommended to attach a cable with a Powerpole connector to use the Powerpole distributor he uses for all the rig components to power the Raspberry Pi with the D.R.A.W.S.
Will this work? My Powerpole terminal delivers constant regulated 13.8 volts for my radios!

73 de Rico, DG5BQ


13.8V? #12vsupply

Rico Abagnale, DG5BQ
 

Hi group.

This might be a stupid question. But since I wouldn’t like to grill my D.R.A.W.S. I will post it anyway:
I saw a video where somebody presented D.R.A.W.S. In this presentation he recommended to attach a cable with a Powerpole connector to use the Powerpole distributor he uses for all the rig components to power the Raspberry Pi with the D.R.A.W.S.
Will this work? My Powerpole terminal delivers constant regulated 13.8 volts for my radios!

73 de Rico, DG5BQ


Re: GPS Monitoring for DRAWS

 



On Thu, Oct 17, 2019 at 1:04 PM Kevin K. - N7KJK <kkutzera@...> wrote:

One thought if you're looking for useful information.. If the programming environment has access to any useful info about the PI itself like the CPU temperature this would be very useful for remote monitoring...


There is code in DRAWS™ Manager to monitor temperature, voltages, etc.  See https://github.com/nwdigitalradio/draws-manager/blob/master/webapp/io.js#L58


--
John D. Hays
Kingston, WA
K7VE

 


Re: GPS Monitoring for DRAWS

Kevin K. - N7KJK
 

This is really nice.  I hope to make use of it when I get my second system setup for APRS...
One thought if you're looking for useful information.. If the programming environment has access to any useful info about the PI itself like the CPU temperature this would be very useful for remote monitoring...
Really great work.  Thank you for contributing to the collection of resources for the DRAWS system.

73
Kevin
N7KJK


On Wed, Oct 16, 2019 at 1:29 PM Edouard Lafargue <edouard@...> wrote:
Hi everyone,

  Since the DRAWS is equipped with a GPS receiver, I figured I would write a quick web interface for it. I mostly use my Raspberry Pi station remotely from my Mac, and having a web interface to monitor the radio and GPS is fairly useful.

   I used the open source Wizkers.io framework to implement this, so that it works nicely with the remote rig control and monitoring that already exist for it (full disclosure, I am the developer). The code is not pushed to Github yet, but if there is interest, I'll be happy to oblige.

What other GPS information would you want to see on a status dashboard? The screenshots below are all web pages:

GPS Monitor screen:
Screen Shot 2019-10-16 at 09.36.07.png

Kenwood V71A remote control screen:

Screen Shot 2019-10-16 at 13.24.14.png



--
Kevin J. Kutzera CISSP, CISM, CEH
Cell: 206-850-7762


Re: GPS Monitoring for DRAWS

lee hyde
 

Awesome efforr!


On Wed, Oct 16, 2019, 10:09 PM Edouard Lafargue <edouard@...> wrote:
  and... here is the manual: https://elafargue.github.io/wizkers-doc/

   In particular, look up the "Developer/Building" section if you want to build it! That project is a bit unloved these days for lack of free time, but it still works great - it is used in multiple remote locations running 24/7/365 for various projects, but let's not stray off-topic, this is the UDRS/DRAWS list. Reach out directly if you have any questions,

Ed

On Wed, Oct 16, 2019 at 8:59 PM Edouard Lafargue via Groups.Io <edouard=lafargue.name@groups.io> wrote:
It doesn't use hamlib so far - it does far more than hamlib can do for Elecraft or Kenwoodradios, but at the expense of wider rig support.

Source is at https://GitHub.com/wizkers/wizkers.git . I need to replublish the manual too...

On Wed, Oct 16, 2019, 17:08 Ruben . <rubenkaf@...> wrote:
Hello Edouard,

Just wondering if your program uses or can use hamlib, this would greatly expand the number of radios your program can use.

Thank you and 73,
Ruben
WA2NBL

On 10/16/2019 1:28 PM, Edouard Lafargue wrote:,
Hi everyone,

  Since the DRAWS is equipped with a GPS receiver, I figured I would write a quick web interface for it. I mostly use my Raspberry Pi station remotely from my Mac, and having a web interface to monitor the radio and GPS is fairly useful.

   I used the open source Wizkers.io framework to implement this, so that it works nicely with the remote rig control and monitoring that already exist for it (full disclosure, I am the developer). The code is not pushed to Github yet, but if there is interest, I'll be happy to oblige.

What other GPS information would you want to see on a status dashboard? The screenshots below are all web pages:

GPS Monitor screen:
Screen Shot 2019-10-16 at 09.36.07.png

Kenwood V71A remote control screen:

Screen Shot 2019-10-16 at 13.24.14.png


Re: GPS Monitoring for DRAWS

Edouard Lafargue
 

  and... here is the manual: https://elafargue.github.io/wizkers-doc/

   In particular, look up the "Developer/Building" section if you want to build it! That project is a bit unloved these days for lack of free time, but it still works great - it is used in multiple remote locations running 24/7/365 for various projects, but let's not stray off-topic, this is the UDRS/DRAWS list. Reach out directly if you have any questions,

Ed


On Wed, Oct 16, 2019 at 8:59 PM Edouard Lafargue via Groups.Io <edouard=lafargue.name@groups.io> wrote:
It doesn't use hamlib so far - it does far more than hamlib can do for Elecraft or Kenwoodradios, but at the expense of wider rig support.

Source is at https://GitHub.com/wizkers/wizkers.git . I need to replublish the manual too...

On Wed, Oct 16, 2019, 17:08 Ruben . <rubenkaf@...> wrote:
Hello Edouard,

Just wondering if your program uses or can use hamlib, this would greatly expand the number of radios your program can use.

Thank you and 73,
Ruben
WA2NBL

On 10/16/2019 1:28 PM, Edouard Lafargue wrote:,
Hi everyone,

  Since the DRAWS is equipped with a GPS receiver, I figured I would write a quick web interface for it. I mostly use my Raspberry Pi station remotely from my Mac, and having a web interface to monitor the radio and GPS is fairly useful.

   I used the open source Wizkers.io framework to implement this, so that it works nicely with the remote rig control and monitoring that already exist for it (full disclosure, I am the developer). The code is not pushed to Github yet, but if there is interest, I'll be happy to oblige.

What other GPS information would you want to see on a status dashboard? The screenshots below are all web pages:

GPS Monitor screen:
Screen Shot 2019-10-16 at 09.36.07.png

Kenwood V71A remote control screen:

Screen Shot 2019-10-16 at 13.24.14.png


Re: GPS Monitoring for DRAWS

Edouard Lafargue
 

It doesn't use hamlib so far - it does far more than hamlib can do for Elecraft or Kenwoodradios, but at the expense of wider rig support.

Source is at https://GitHub.com/wizkers/wizkers.git . I need to replublish the manual too...

On Wed, Oct 16, 2019, 17:08 Ruben . <rubenkaf@...> wrote:
Hello Edouard,

Just wondering if your program uses or can use hamlib, this would greatly expand the number of radios your program can use.

Thank you and 73,
Ruben
WA2NBL

On 10/16/2019 1:28 PM, Edouard Lafargue wrote:,
Hi everyone,

  Since the DRAWS is equipped with a GPS receiver, I figured I would write a quick web interface for it. I mostly use my Raspberry Pi station remotely from my Mac, and having a web interface to monitor the radio and GPS is fairly useful.

   I used the open source Wizkers.io framework to implement this, so that it works nicely with the remote rig control and monitoring that already exist for it (full disclosure, I am the developer). The code is not pushed to Github yet, but if there is interest, I'll be happy to oblige.

What other GPS information would you want to see on a status dashboard? The screenshots below are all web pages:

GPS Monitor screen:

Kenwood V71A remote control screen:




Re: GPS Monitoring for DRAWS

Ruben .
 

Hello Edouard,

Just wondering if your program uses or can use hamlib, this would greatly expand the number of radios your program can use.

Thank you and 73,
Ruben
WA2NBL

On 10/16/2019 1:28 PM, Edouard Lafargue wrote:,

Hi everyone,

  Since the DRAWS is equipped with a GPS receiver, I figured I would write a quick web interface for it. I mostly use my Raspberry Pi station remotely from my Mac, and having a web interface to monitor the radio and GPS is fairly useful.

   I used the open source Wizkers.io framework to implement this, so that it works nicely with the remote rig control and monitoring that already exist for it (full disclosure, I am the developer). The code is not pushed to Github yet, but if there is interest, I'll be happy to oblige.

What other GPS information would you want to see on a status dashboard? The screenshots below are all web pages:

GPS Monitor screen:
Screen Shot 2019-10-16 at 09.36.07.png

Kenwood V71A remote control screen:

Screen Shot 2019-10-16 at 13.24.14.png


Re: Temporary mobile RMS Gateway for EMCOM #winlink #rms

 

Basil has limited email access for a few days, maybe ping this when he is back.


Temporary mobile RMS Gateway for EMCOM #winlink #rms

Matthew Kozma <matthew@...>
 

I am thinking of creating a mobile RMS gateway for temporary use on ARES & Search and Rescue missions. I have a rPi with a UDRC II in my vehicle. It is configured to run APRS using a radio on the DB15 port.  I also have a second radio connected the din port.  This radio is used by my laptop running Winlink and connecting via KISS port 2.  I have a hot spot in the vehicle too and was considering installing the RMS gateway on the rPi so that I can operate as a temporary RMS using that second radio.  My question is how can I start and stop the RMS gateway service.  I want to be able to control when that function is running.     


Re: GPS Monitoring for DRAWS

 

Very nice. A git repository would be very welcome.

On Wed, Oct 16, 2019 at 1:29 PM Edouard Lafargue <edouard@...> wrote:
Hi everyone,

  Since the DRAWS is equipped with a GPS receiver, I figured I would write a quick web interface for it. I mostly use my Raspberry Pi station remotely from my Mac, and having a web interface to monitor the radio and GPS is fairly useful.

   I used the open source Wizkers.io framework to implement this, so that it works nicely with the remote rig control and monitoring that already exist for it (full disclosure, I am the developer). The code is not pushed to Github yet, but if there is interest, I'll be happy to oblige.

What other GPS information would you want to see on a status dashboard? The screenshots below are all web pages:

GPS Monitor screen:
Screen Shot 2019-10-16 at 09.36.07.png

Kenwood V71A remote control screen:

Screen Shot 2019-10-16 at 13.24.14.png



--
John D. Hays
Kingston, WA
K7VE

 


GPS Monitoring for DRAWS

Edouard Lafargue
 

Hi everyone,

  Since the DRAWS is equipped with a GPS receiver, I figured I would write a quick web interface for it. I mostly use my Raspberry Pi station remotely from my Mac, and having a web interface to monitor the radio and GPS is fairly useful.

   I used the open source Wizkers.io framework to implement this, so that it works nicely with the remote rig control and monitoring that already exist for it (full disclosure, I am the developer). The code is not pushed to Github yet, but if there is interest, I'll be happy to oblige.

What other GPS information would you want to see on a status dashboard? The screenshots below are all web pages:

GPS Monitor screen:
Screen Shot 2019-10-16 at 09.36.07.png

Kenwood V71A remote control screen:

Screen Shot 2019-10-16 at 13.24.14.png


Re: KC9KKORE: Second interface

 

Multiple instances of the audio on a physical device is accomplished using PulseAudio. See the wiki. 


On Mon, Oct 14, 2019, 20:11 Stuart Longland VK4MSL <stuartl@...> wrote:
On 15/10/19 8:56 am, Bill Vodall wrote:
> On Mon, Oct 14, 2019 at 11:21 AM John D Hays - K7VE <john@...> wrote:
>>
>> JP,
>>
>> If you are asking about running 1200/9600 in parallel on the same radio port.  This only partially works at the current time.  It receives just fine and can transmit on one rate or the other.  The gating factor is activating PTT from direwolf.  The current version of direwolf allow only one channel to access a given GPIO PTT in configuration.  The configuration runs two virtual sound device on a single audio channel.
>
> How about running two instances of Direwolf?

You might run afoul of one instance of Direwolf opening the ALSA device
for the sound card and locking out the second instance unless you do
some trickery in the ALSA configuration files to present the UDRC/DRAWS
as two separate audio interfaces.

This is doable of course, just may require a bit of research.
--
Stuart Longland (aka Redhatter, VK4MSL)

I haven't lost my mind...
   ...it's backed up on a tape somewhere.




Re: KC9KKORE: Second interface

Stuart Longland VK4MSL
 

On 15/10/19 8:56 am, Bill Vodall wrote:
On Mon, Oct 14, 2019 at 11:21 AM John D Hays - K7VE <@john_hays> wrote:

JP,

If you are asking about running 1200/9600 in parallel on the same radio port. This only partially works at the current time. It receives just fine and can transmit on one rate or the other. The gating factor is activating PTT from direwolf. The current version of direwolf allow only one channel to access a given GPIO PTT in configuration. The configuration runs two virtual sound device on a single audio channel.
How about running two instances of Direwolf?
You might run afoul of one instance of Direwolf opening the ALSA device for the sound card and locking out the second instance unless you do some trickery in the ALSA configuration files to present the UDRC/DRAWS as two separate audio interfaces.

This is doable of course, just may require a bit of research.
--
Stuart Longland (aka Redhatter, VK4MSL)

I haven't lost my mind...
...it's backed up on a tape somewhere.


Re: KC9KKORE: Second interface

 

On Mon, Oct 14, 2019 at 11:21 AM John D Hays - K7VE <@john_hays> wrote:

JP,

If you are asking about running 1200/9600 in parallel on the same radio port. This only partially works at the current time. It receives just fine and can transmit on one rate or the other. The gating factor is activating PTT from direwolf. The current version of direwolf allow only one channel to access a given GPIO PTT in configuration. The configuration runs two virtual sound device on a single audio channel.
How about running two instances of Direwolf?