Date   

ThumbDV Issue

Eduardo Gallegos <xe2jeg@...>
 

Hi...

I am running a ThumbDV device on a Mac with Buster software but now I can’t connect to few Reflectors like 1C, 12A or 30C. I CAN connect to few others but not he ones that I mention.

I am a register user on D-Star.

Any help will be greatly appreciated.

Regards,

Eduardo Gallegos
XE2JEG


Re: Getting started with paclink-unix

Basil Gunn
 

Keith Williamson <hkwilliamson@...> writes:

Err..meant "Hi Basil". Not to be confused with "Nigel Gunn" over in the
Chirp forums...
Not a problem. I thought you were referring to Nigel Bruce who played
Dr. Watson to Basil Rathbone's Sherlock Holmes :)


On Mon, Jun 3, 2019 at 1:08 PM Keith Williamson via Groups.Io <hkwilliamson=
gmail.com@groups.io> wrote:

Hi Nigel,

More headway but some hiccups. First the headway:


Re: Getting started with paclink-unix

Basil Gunn
 

Keith Williamson <hkwilliamson@...> writes:

Hi Nigel,
Actaully Basil but I will answer to that as well.
(Nigel Bruce, Basil Rathbone, Sherlock Holmes)

More headway but some hiccups. First the headway:

I edited the grid locator in gatewaylist.sh and ran "gatewaylist.sh -l".
The list then showed that w7ecg-10 was closest to me. I successfully sent a
message using "wl2kax25 -c w7ecg-10"! Woo hoo!
Woo hoo indeed!
I also use rmslist.sh to get the list of gateways to check.

Usage: ./rmslist.sh <integer_distance_in_miles> <maidenhead_grid_square>

Now the hiccups:

1) I have a message that's stuck in the outbox
(/usr/local/var/wl2k/outbox). Each time I run either wl2kax25 or
wl2ktelnet, it's resent successfully to my gmail account. When I run
"chk_perm.sh", I get "permissions OK: pi:mail" and "1 files in outbox". I
originally created the message using Claws mail. Is it OK to just delete
the file from /usr/local/var/wl2k/outbox? Don't want to do that if there is
some meta data in another file tracking it.
Yes you can safely delete any file in /usr/local/var/wl2k/outbox
You should then delete the message ID data base
/usr/local/var/wl2k/mid.db

Be sure you do that as user (ie. pi) & not root.

Is this a possible symptom of a configuration problem?

2) When I run "wlgw-check.sh -g CN88tu", I am seeing an error from rigctl
for the set memory index command (E 35).
Yep. That is something I need to fix. Memory index 35 is my 2m aprs
memory location. I just need any 2M memory location that has been
programmed. This is due to the hack required to change bands (2M/440)
for the TM-V71a rig control.

In wlgw-check.sh look for the line: set_memchan_index 35 and change 35
to what ever 2M digital frequency memory index is programmed in your
radio.

Also you should program the two 440 frequencies into your memory so they
can be accessed via memory location instead of VFO.
K7KCA-10 440125000 32 1200 (in Lopez Village)
AE7LW-10 440950000 33 9600

Although, they are far enough away you will probably not be able to hit
them unless you live on a mountain.

If I run rigctl, I can do set
memory index commands for any of the memory channels I have written to
using Chirp but not memory channels that haven't been set to anything. So
far, I programmed the first 20 memory channels with Chirp. So, "rigctl -m
234 -r /dev/ttyUSB0 -E 20" will work but "rigctl -m 234 -r /dev/ttyUSB0 -E
35" fails. I imagine a workaround would be for me to program something into
channel 35 using Chirp (or directly from the radio), and that may fix that.
I'll try that next but wanted you to be aware of the issue. I just got this
radio but I imagine your V71a's have had many more channels previously
programmed so you might not have seen this issue. It would seem that once
the set memory index issue is fixed, the wlgw-check script should work.
When I did run it I could see it was changing the V71a frequency and
transmitting so I think we're really close.
When I run rmslist.sh using your gridsquare, 3 RMS gateways come up that
I control.
So there is an assumption that you are connecting to 1200 baud
Gateways. Just an FYI it is possible to change to 9600 baud on the fly
as well. I need to spend some time to test that out.

/Basil


Re: Getting started with paclink-unix

Keith Williamson
 

Err..meant "Hi Basil". Not to be confused with "Nigel Gunn" over in the Chirp forums...



On Mon, Jun 3, 2019 at 1:08 PM Keith Williamson via Groups.Io <hkwilliamson=gmail.com@groups.io> wrote:
Hi Nigel,

More headway but some hiccups. First the headway:

I edited the grid locator in gatewaylist.sh and ran "gatewaylist.sh -l". The list then showed that w7ecg-10 was closest to me. I successfully sent a message using "wl2kax25 -c w7ecg-10"! Woo hoo!

Now the hiccups:

1) I have a message that's stuck in the outbox (/usr/local/var/wl2k/outbox). Each time I run either wl2kax25 or wl2ktelnet, it's resent successfully to my gmail account. When I run "chk_perm.sh", I get "permissions OK: pi:mail" and "1 files in outbox". I originally created the message using Claws mail. Is it OK to just delete the file from /usr/local/var/wl2k/outbox? Don't want to do that if there is some meta data in another file tracking it. 

2) When I run "wlgw-check.sh -g CN88tu", I am seeing an error from rigctl for the set memory index command (E 35). If I run rigctl, I can do set memory index commands for any of the memory channels I have written to using Chirp but not memory channels that haven't been set to anything. So far, I programmed the first 20 memory channels with Chirp. So, "rigctl -m 234 -r /dev/ttyUSB0 -E 20" will work but "rigctl -m 234 -r /dev/ttyUSB0 -E 35" fails. I imagine a workaround would be for me to program something into channel 35 using Chirp (or directly from the radio), and that may fix that. I'll try that next but wanted you to be aware of the issue. I just got this radio but I imagine your V71a's have had many more channels previously programmed so you might not have seen this issue. It would seem that once the set memory index issue is fixed, the wlgw-check script should work. When I did run it I could see it was changing the V71a frequency and transmitting so I think we're really close.

Thanks,

Keith
KF7DRV

On Mon, Jun 3, 2019 at 11:50 AM Basil Gunn <basil@...> wrote:

> Building latest paclink-unix did the trick. Apparently, latest version
> fixes passwords with multicase and letter/number combinations.

Great! Congrats on getting paclink-unix working!

> Next step for me is to get the radio involved using auto-rmsgw-find.

I currently run the the wlgw-check.sh (Winlink Gateway Check) script
from a cron job 4 times a day.

I know the documentation is a little thin so if you have any problems at
all please don't hesitate to ask questions.

/Basil n7nix

> Thanks!
>
> Keith
> KF7DRV
>
>
> On Mon, Jun 3, 2019 at 10:17 AM Basil Gunn <basil@...> wrote:
>
>>
>> If your password has upper & lower case letters then you need to get the
>> latest version of paclink-unix.
>>
>> cd /usr/local/src/paclink-unix
>> git pull
>> ./build-all.sh




Re: Getting started with paclink-unix

Keith Williamson
 

Hi Nigel,

More headway but some hiccups. First the headway:

I edited the grid locator in gatewaylist.sh and ran "gatewaylist.sh -l". The list then showed that w7ecg-10 was closest to me. I successfully sent a message using "wl2kax25 -c w7ecg-10"! Woo hoo!

Now the hiccups:

1) I have a message that's stuck in the outbox (/usr/local/var/wl2k/outbox). Each time I run either wl2kax25 or wl2ktelnet, it's resent successfully to my gmail account. When I run "chk_perm.sh", I get "permissions OK: pi:mail" and "1 files in outbox". I originally created the message using Claws mail. Is it OK to just delete the file from /usr/local/var/wl2k/outbox? Don't want to do that if there is some meta data in another file tracking it. 

2) When I run "wlgw-check.sh -g CN88tu", I am seeing an error from rigctl for the set memory index command (E 35). If I run rigctl, I can do set memory index commands for any of the memory channels I have written to using Chirp but not memory channels that haven't been set to anything. So far, I programmed the first 20 memory channels with Chirp. So, "rigctl -m 234 -r /dev/ttyUSB0 -E 20" will work but "rigctl -m 234 -r /dev/ttyUSB0 -E 35" fails. I imagine a workaround would be for me to program something into channel 35 using Chirp (or directly from the radio), and that may fix that. I'll try that next but wanted you to be aware of the issue. I just got this radio but I imagine your V71a's have had many more channels previously programmed so you might not have seen this issue. It would seem that once the set memory index issue is fixed, the wlgw-check script should work. When I did run it I could see it was changing the V71a frequency and transmitting so I think we're really close.

Thanks,

Keith
KF7DRV


On Mon, Jun 3, 2019 at 11:50 AM Basil Gunn <basil@...> wrote:

> Building latest paclink-unix did the trick. Apparently, latest version
> fixes passwords with multicase and letter/number combinations.

Great! Congrats on getting paclink-unix working!

> Next step for me is to get the radio involved using auto-rmsgw-find.

I currently run the the wlgw-check.sh (Winlink Gateway Check) script
from a cron job 4 times a day.

I know the documentation is a little thin so if you have any problems at
all please don't hesitate to ask questions.

/Basil n7nix

> Thanks!
>
> Keith
> KF7DRV
>
>
> On Mon, Jun 3, 2019 at 10:17 AM Basil Gunn <basil@...> wrote:
>
>>
>> If your password has upper & lower case letters then you need to get the
>> latest version of paclink-unix.
>>
>> cd /usr/local/src/paclink-unix
>> git pull
>> ./build-all.sh




Re: Getting started with paclink-unix

Basil Gunn
 

Building latest paclink-unix did the trick. Apparently, latest version
fixes passwords with multicase and letter/number combinations.
Great! Congrats on getting paclink-unix working!

Next step for me is to get the radio involved using auto-rmsgw-find.
I currently run the the wlgw-check.sh (Winlink Gateway Check) script
from a cron job 4 times a day.

I know the documentation is a little thin so if you have any problems at
all please don't hesitate to ask questions.

/Basil n7nix

Thanks!

Keith
KF7DRV


On Mon, Jun 3, 2019 at 10:17 AM Basil Gunn <@basil860> wrote:


If your password has upper & lower case letters then you need to get the
latest version of paclink-unix.

cd /usr/local/src/paclink-unix
git pull
./build-all.sh


Re: Getting started with paclink-unix

Keith Williamson
 

Hi,

Building latest paclink-unix did the trick. Apparently, latest version fixes passwords with multicase and letter/number combinations.

Next step for me is to get the radio involved using auto-rmsgw-find.

Thanks!

Keith
KF7DRV


On Mon, Jun 3, 2019 at 10:17 AM Basil Gunn <basil@...> wrote:

If your password has upper & lower case letters then you need to get the
latest version of paclink-unix.

cd /usr/local/src/paclink-unix
git pull
./build-all.sh

Also verify that the password in file:
/usr/local/etc/wl2k.conf

wl2k-password=

is exactly the same as the one you are using in Winlink Express.

Please send me a Winlink message when you have things working:
n7nix@....

/Basil


Keith Williamson <hkwilliamson@...> writes:

> Hi,
>
> I have the Beta 13 image installed and did the core configuration. Tested
> direwolf, fldigi, and rigctl successfully. This morning, I configured
> paclink-unix via "app_config.sh plu". This completed successfully. On a Win
> laptop, I had installed Winlink Express just for the purposes of creating
> and validating my Winlink credentials. That all worked fine and I have sent
> and received a few messages via the telnet interface.
>
> During the PLU config, I supplied the user (KF7DRV) and password from
> Winlink Express. However, when I run "wl2ktelnet", I get "secure login
> failure" along with "B2 protocol error 1":
>
> [image: image.png]
>
> I have verified that my "wl2k-password" in /usr/local/etc/wl2k.conf matches
> Winlink Express.
>
> Any ideas why this is failing?
>
> Keith
> KF7DRV




Re: Getting started with paclink-unix

Basil Gunn
 

If your password has upper & lower case letters then you need to get the
latest version of paclink-unix.

cd /usr/local/src/paclink-unix
git pull
./build-all.sh

Also verify that the password in file:
/usr/local/etc/wl2k.conf

wl2k-password=

is exactly the same as the one you are using in Winlink Express.

Please send me a Winlink message when you have things working:
n7nix@....

/Basil


Keith Williamson <hkwilliamson@...> writes:

Hi,

I have the Beta 13 image installed and did the core configuration. Tested
direwolf, fldigi, and rigctl successfully. This morning, I configured
paclink-unix via "app_config.sh plu". This completed successfully. On a Win
laptop, I had installed Winlink Express just for the purposes of creating
and validating my Winlink credentials. That all worked fine and I have sent
and received a few messages via the telnet interface.

During the PLU config, I supplied the user (KF7DRV) and password from
Winlink Express. However, when I run "wl2ktelnet", I get "secure login
failure" along with "B2 protocol error 1":

[image: image.png]

I have verified that my "wl2k-password" in /usr/local/etc/wl2k.conf matches
Winlink Express.

Any ideas why this is failing?

Keith
KF7DRV


Getting started with paclink-unix

Keith Williamson
 

Hi,

I have the Beta 13 image installed and did the core configuration. Tested direwolf, fldigi, and rigctl successfully. This morning, I configured paclink-unix via "app_config.sh plu". This completed successfully. On a Win laptop, I had installed Winlink Express just for the purposes of creating and validating my Winlink credentials. That all worked fine and I have sent and received a few messages via the telnet interface.

During the PLU config, I supplied the user (KF7DRV) and password from Winlink Express. However, when I run "wl2ktelnet", I get "secure login failure" along with "B2 protocol error 1":

image.png

I have verified that my "wl2k-password" in /usr/local/etc/wl2k.conf matches Winlink Express.

Any ideas why this is failing?

Keith
KF7DRV




Re: DRAWS and Allstar?

Anthony Leeser
 

Thanks Steve for any potential updates you'll stumble upon. Meanwhile, I'll continue to read all these emails in hopes I can learn enough to make my DRAWS work.

Tony
AG7GF 



Sent from my Verizon, Samsung Galaxy smartphone

-------- Original message --------
From: Steve KC1AWV <smiller@...>
Date: 6/2/19 8:38 PM (GMT-08:00)
To: udrc@nw-digital-radio.groups.io
Subject: Re: [udrc] DRAWS and Allstar?

I understand what you are saying. That's why I like to try and figure out what people are doing with their devices, and lend a hand when I can.

I just see that DRAWS is more of a Swiss army knife for digital on amateur radio than just a radio interface. That's why I would suggest a URIx instead of a DRAWS board with Allstar. But, I don't know everyone's use case so I could still do what I can to make it work.

Could it be done? I'm sure it could! But like you said, it's better to perfect the device for it's intended purpose than to stretch the capabilities out to cover everything.

I'll be over here on the side, and will update with findings if I get any! If I find time to tinker, I'll see what I can do to make it work. 

On Sun, Jun 2, 2019, 11:30 PM Anthony Leeser <tagtynee@...> wrote:
Steve,

Hmmm...the thought of the DRAWS board providing Allstar capabilities wasn't thought of. I would just be satisfied if they can both run on one operating system/RPi.

There's so many unanswered questions that haven't yet been answered and to add  Allstar or any other experiments to DRAWS is too early, in my oppinion, until it's perfected. Kinda like putting the horse in front of the cart?

I've given up on the DRAWS. I don't know what I'm doing. Instructions are vague unless we're Linux geeks. Linux geek I'm not.

Tony
AG7GF 


Sent from my Verizon, Samsung Galaxy smartphone

-------- Original message --------
From: Steve KC1AWV <smiller@...>
Date: 6/2/19 8:02 PM (GMT-08:00)
Subject: Re: [udrc] DRAWS and Allstar?

"Allstar without the attached OS" is just Asterisk with app_rpt. Asterisk runs on many OSes - Linux, BSD, Windows, etc... Just need to compile it with app_rpt.

Allstar takes it a step further, building a network on top of Asterisk and app_rpt. They provide a distribution of Debian with Asterisk and app_rpt pre compiled, with all the heavy lifting and configuration already done. You could do it all yourself, but why when you can save time with the distro?

The issue I see is not with the Allstar distribution, but rather getting DRAWS to show up as a compatible device for app_rpt. The URIx and other similar radio interface were specifically designed for Allstar, IRLP and the like.

A driver may be needed for use with Allstar. If this is something that a lot of people are interested in, I could take a stab at it. Just need to dedicate the time and a board. Though, I feel that the exercise may be a little in vain, using DRAWS for just going from a radio to Allstar is seriously limiting the power and capabilities of the board. A URIx would be easier, since it's the right tools for the job kind of thing. Plus, it's cheaper than a DRAWS board.

Steve KC1AWV


On Sun, Jun 2, 2019, 10:24 PM Anthony Leeser <tagtynee@...> wrote:

Hello Christopher 

That's a very good question. I've been working on that for sometime. I didn't want to tie up and dedicate a RPi solely for Allstar. I wanted to do HF digital as well. I've been working on this project for about a year. The introduction of DRAWS changed my entire build... ugh. Unless I overlooked a possible workaround, only thing I haven't tried was requesting to get the Allstar software without the attached operating system. If that's possible, I don't see why DRAWS and Allstar can't be friendly neighbors one one operating system.

Tony
AG7GF 


Sent from my Verizon, Samsung Galaxy smartphone

-------- Original message --------
From: Christopher AI6KG <ch@...>
Date: 6/2/19 5:02 PM (GMT-08:00)
Subject: [udrc] DRAWS and Allstar?

Has anyone gotten Allstar running with DRAWS (or UDRC)?    I saw the thread re: URI but my aim is to use DRAWS rather than URI.

-christopher.

73 de AI6KG


Re: DRAWS and Allstar?

Steve KC1AWV
 

I understand what you are saying. That's why I like to try and figure out what people are doing with their devices, and lend a hand when I can.

I just see that DRAWS is more of a Swiss army knife for digital on amateur radio than just a radio interface. That's why I would suggest a URIx instead of a DRAWS board with Allstar. But, I don't know everyone's use case so I could still do what I can to make it work.

Could it be done? I'm sure it could! But like you said, it's better to perfect the device for it's intended purpose than to stretch the capabilities out to cover everything.

I'll be over here on the side, and will update with findings if I get any! If I find time to tinker, I'll see what I can do to make it work. 

On Sun, Jun 2, 2019, 11:30 PM Anthony Leeser <tagtynee@...> wrote:
Steve,

Hmmm...the thought of the DRAWS board providing Allstar capabilities wasn't thought of. I would just be satisfied if they can both run on one operating system/RPi.

There's so many unanswered questions that haven't yet been answered and to add  Allstar or any other experiments to DRAWS is too early, in my oppinion, until it's perfected. Kinda like putting the horse in front of the cart?

I've given up on the DRAWS. I don't know what I'm doing. Instructions are vague unless we're Linux geeks. Linux geek I'm not.

Tony
AG7GF 


Sent from my Verizon, Samsung Galaxy smartphone

-------- Original message --------
From: Steve KC1AWV <smiller@...>
Date: 6/2/19 8:02 PM (GMT-08:00)
Subject: Re: [udrc] DRAWS and Allstar?

"Allstar without the attached OS" is just Asterisk with app_rpt. Asterisk runs on many OSes - Linux, BSD, Windows, etc... Just need to compile it with app_rpt.

Allstar takes it a step further, building a network on top of Asterisk and app_rpt. They provide a distribution of Debian with Asterisk and app_rpt pre compiled, with all the heavy lifting and configuration already done. You could do it all yourself, but why when you can save time with the distro?

The issue I see is not with the Allstar distribution, but rather getting DRAWS to show up as a compatible device for app_rpt. The URIx and other similar radio interface were specifically designed for Allstar, IRLP and the like.

A driver may be needed for use with Allstar. If this is something that a lot of people are interested in, I could take a stab at it. Just need to dedicate the time and a board. Though, I feel that the exercise may be a little in vain, using DRAWS for just going from a radio to Allstar is seriously limiting the power and capabilities of the board. A URIx would be easier, since it's the right tools for the job kind of thing. Plus, it's cheaper than a DRAWS board.

Steve KC1AWV


On Sun, Jun 2, 2019, 10:24 PM Anthony Leeser <tagtynee@...> wrote:

Hello Christopher 

That's a very good question. I've been working on that for sometime. I didn't want to tie up and dedicate a RPi solely for Allstar. I wanted to do HF digital as well. I've been working on this project for about a year. The introduction of DRAWS changed my entire build... ugh. Unless I overlooked a possible workaround, only thing I haven't tried was requesting to get the Allstar software without the attached operating system. If that's possible, I don't see why DRAWS and Allstar can't be friendly neighbors one one operating system.

Tony
AG7GF 


Sent from my Verizon, Samsung Galaxy smartphone

-------- Original message --------
From: Christopher AI6KG <ch@...>
Date: 6/2/19 5:02 PM (GMT-08:00)
Subject: [udrc] DRAWS and Allstar?

Has anyone gotten Allstar running with DRAWS (or UDRC)?    I saw the thread re: URI but my aim is to use DRAWS rather than URI.

-christopher.

73 de AI6KG


Re: DRAWS and Allstar?

Anthony Leeser
 

Steve,

Hmmm...the thought of the DRAWS board providing Allstar capabilities wasn't thought of. I would just be satisfied if they can both run on one operating system/RPi.

There's so many unanswered questions that haven't yet been answered and to add  Allstar or any other experiments to DRAWS is too early, in my oppinion, until it's perfected. Kinda like putting the horse in front of the cart?

I've given up on the DRAWS. I don't know what I'm doing. Instructions are vague unless we're Linux geeks. Linux geek I'm not.

Tony
AG7GF 


Sent from my Verizon, Samsung Galaxy smartphone

-------- Original message --------
From: Steve KC1AWV <smiller@...>
Date: 6/2/19 8:02 PM (GMT-08:00)
To: udrc@nw-digital-radio.groups.io
Subject: Re: [udrc] DRAWS and Allstar?

"Allstar without the attached OS" is just Asterisk with app_rpt. Asterisk runs on many OSes - Linux, BSD, Windows, etc... Just need to compile it with app_rpt.

Allstar takes it a step further, building a network on top of Asterisk and app_rpt. They provide a distribution of Debian with Asterisk and app_rpt pre compiled, with all the heavy lifting and configuration already done. You could do it all yourself, but why when you can save time with the distro?

The issue I see is not with the Allstar distribution, but rather getting DRAWS to show up as a compatible device for app_rpt. The URIx and other similar radio interface were specifically designed for Allstar, IRLP and the like.

A driver may be needed for use with Allstar. If this is something that a lot of people are interested in, I could take a stab at it. Just need to dedicate the time and a board. Though, I feel that the exercise may be a little in vain, using DRAWS for just going from a radio to Allstar is seriously limiting the power and capabilities of the board. A URIx would be easier, since it's the right tools for the job kind of thing. Plus, it's cheaper than a DRAWS board.

Steve KC1AWV


On Sun, Jun 2, 2019, 10:24 PM Anthony Leeser <tagtynee@...> wrote:

Hello Christopher 

That's a very good question. I've been working on that for sometime. I didn't want to tie up and dedicate a RPi solely for Allstar. I wanted to do HF digital as well. I've been working on this project for about a year. The introduction of DRAWS changed my entire build... ugh. Unless I overlooked a possible workaround, only thing I haven't tried was requesting to get the Allstar software without the attached operating system. If that's possible, I don't see why DRAWS and Allstar can't be friendly neighbors one one operating system.

Tony
AG7GF 


Sent from my Verizon, Samsung Galaxy smartphone

-------- Original message --------
From: Christopher AI6KG <ch@...>
Date: 6/2/19 5:02 PM (GMT-08:00)
Subject: [udrc] DRAWS and Allstar?

Has anyone gotten Allstar running with DRAWS (or UDRC)?    I saw the thread re: URI but my aim is to use DRAWS rather than URI.

-christopher.

73 de AI6KG


Re: DRAWS and Allstar?

Steve KC1AWV
 

"Allstar without the attached OS" is just Asterisk with app_rpt. Asterisk runs on many OSes - Linux, BSD, Windows, etc... Just need to compile it with app_rpt.

Allstar takes it a step further, building a network on top of Asterisk and app_rpt. They provide a distribution of Debian with Asterisk and app_rpt pre compiled, with all the heavy lifting and configuration already done. You could do it all yourself, but why when you can save time with the distro?

The issue I see is not with the Allstar distribution, but rather getting DRAWS to show up as a compatible device for app_rpt. The URIx and other similar radio interface were specifically designed for Allstar, IRLP and the like.

A driver may be needed for use with Allstar. If this is something that a lot of people are interested in, I could take a stab at it. Just need to dedicate the time and a board. Though, I feel that the exercise may be a little in vain, using DRAWS for just going from a radio to Allstar is seriously limiting the power and capabilities of the board. A URIx would be easier, since it's the right tools for the job kind of thing. Plus, it's cheaper than a DRAWS board.

Steve KC1AWV


On Sun, Jun 2, 2019, 10:24 PM Anthony Leeser <tagtynee@...> wrote:

Hello Christopher 

That's a very good question. I've been working on that for sometime. I didn't want to tie up and dedicate a RPi solely for Allstar. I wanted to do HF digital as well. I've been working on this project for about a year. The introduction of DRAWS changed my entire build... ugh. Unless I overlooked a possible workaround, only thing I haven't tried was requesting to get the Allstar software without the attached operating system. If that's possible, I don't see why DRAWS and Allstar can't be friendly neighbors one one operating system.

Tony
AG7GF 


Sent from my Verizon, Samsung Galaxy smartphone

-------- Original message --------
From: Christopher AI6KG <ch@...>
Date: 6/2/19 5:02 PM (GMT-08:00)
Subject: [udrc] DRAWS and Allstar?

Has anyone gotten Allstar running with DRAWS (or UDRC)?    I saw the thread re: URI but my aim is to use DRAWS rather than URI.

-christopher.

73 de AI6KG


Re: DRAWS and Allstar?

Anthony Leeser
 


Hello Christopher 

That's a very good question. I've been working on that for sometime. I didn't want to tie up and dedicate a RPi solely for Allstar. I wanted to do HF digital as well. I've been working on this project for about a year. The introduction of DRAWS changed my entire build... ugh. Unless I overlooked a possible workaround, only thing I haven't tried was requesting to get the Allstar software without the attached operating system. If that's possible, I don't see why DRAWS and Allstar can't be friendly neighbors one one operating system.

Tony
AG7GF 


Sent from my Verizon, Samsung Galaxy smartphone

-------- Original message --------
From: Christopher AI6KG <ch@...>
Date: 6/2/19 5:02 PM (GMT-08:00)
To: udrc@nw-digital-radio.groups.io
Subject: [udrc] DRAWS and Allstar?

Has anyone gotten Allstar running with DRAWS (or UDRC)?    I saw the thread re: URI but my aim is to use DRAWS rather than URI.

-christopher.

73 de AI6KG


Re: JS8 and draws

Douglas
 

My current audio settings are
 ===== ALSA Controls for Radio Transmit =====
LO Driver Gain  L:[-6.00dB] R:[-6.00dB]
PCM         L:[-25.00dB] R:[-25.00dB]
DAC Playback PT L:[PTM_P3] R:[PTM_P1]
LO Playback CM [Full Chip CM]
 
 ===== ALSA Controls for Radio Receive =====
ADC Level L:[0.00dB] R:[0.00dB]
IN1 L:[Off] R:[Off]
IN2 L:[10 kOhm] R:[10 kOhm]
CM L:[10 kOhm] R:[10 kOhm]
 


DRAWS and Allstar?

Christopher AI6KG
 

Has anyone gotten Allstar running with DRAWS (or UDRC)?    I saw the thread re: URI but my aim is to use DRAWS rather than URI.

-christopher.

73 de AI6KG


NVIDIA Jetson Nano and DRAWS

Edward Seeliger
 

Has anyone tried to use the DRAWS board with an NVIDIA Jetson Nano board - it has an ARM processor and a 40 pin GPIO output that is equivalent to that on the RPi. It runs a version of Ubuntu 18.04 Linux.
Edd - KD5M


Re: Kx3 IQ and draws #kx3

 

The DRAWS™ HAT has two mono radio interfaces, they are the left and right channels of a single sound chip. 


On Thu, May 30, 2019, 18:41 Jeff Scaparra <jeff@...> wrote:
New here but considering making my own PX3 that can also do wsjt-x fldigi etc... My understanding is that the draws hat has two stereo ADCs and I am hoping that I can use one for I/Q panadapter stuff and one for sound in for digital modes. Is there also a sound out? What is the bitrate as this would affect the bandwidth of the panadapter. 

Jeff


Kx3 IQ and draws #kx3

Jeff Scaparra
 

New here but considering making my own PX3 that can also do wsjt-x fldigi etc... My understanding is that the draws hat has two stereo ADCs and I am hoping that I can use one for I/Q panadapter stuff and one for sound in for digital modes. Is there also a sound out? What is the bitrate as this would affect the bandwidth of the panadapter. 

Jeff


Re: JS8 and draws

Basil Gunn
 

There is a new script in n7nix/bin/ptt_ctrl.sh that can be used in the
JS8Call radio configuration PTT command. It is used like this:

# For left connector
ptt_ctrl.sh -l on
ptt_ctrl.sh -l off
# Display state of ptt gpio
ptt_ctrl.sh -l -c

# For right connector
ptt_ctrl.sh -r on
ptt_ctrl.sh -r off
# Display state of ptt gpio
ptt_ctrl.sh -r -c

# To display all command line options
ptt_ctrl.sh -h

# To install
cd
cd n7nix
git pull
cd config
./bin_refresh.sh

# Assuming left connector is used, this is what the JS8Call PTT command
would look like:

ptt_ctrl.sh -l %1

/Basil


John D Hays - K7VE <@john_hays> writes:

Jordan says " There is GPIO support via an external PTT script. You
can learn more in the "Radio (CAT and PTT control)" section of the
documentation: https://docs. google.com/document/d/
159S4wqMUVdMA7qBgaSWmU- iDI4C9wd4CuWnetN68O9U/edit#
heading=h.5xqo9txkzgxf " (
https://docs.google.com/document/d/159S4wqMUVdMA7qBgaSWmU-iDI4C9wd4CuWnetN68O9U/edit#heading=h.5xqo9txkzgxf
)

Best,
Jordan / KN4CRD"