Date   
Re: DRAWS

Paul Noa
 

Hi Basil,

Me again!  I have had seemingly gotten most everything straighten out. Bryan helped.

Attached is a text of my current situation.  What I know is:
1.) My GPS receiver is not picking up because it is too far from the window not an issue now.
2.) I have not yet set up transmit levels and suspect that is my next challenge
3.) Having no prior experience I am not sure about some of the results could you look at my file of outputs and give me your insights please?

I will be checking the transmit side in the meantime.
Thanks for your support in advance!
Paul KO4BCZ

Re: GPS Extender

 

It is just coax with a voltage bias to power the antenna. Just follow common coax extension procedures. 

There are also antenna assemblies with longer coax. 

On Tue, Apr 7, 2020, 03:43 Ed Bloom, KD9FRQ via groups.io <ewbloom=verizon.net@groups.io> wrote:
My shack in the basement.  I only have two, 16x28 windows. Both have
very, very limited view of sky.

What GPS extender do you recommend and why?

Or could I put an SMA bulkhead connector through the wall and get more
SMA coax to connect the GPS unit?

Thanks, Ed, KD9FRQ




Program Setup & Use Instructions

Ed Bloom, KD9FRQ
 

Where can I find the PLU and Xastir setup and use instructions for our DRAWS?

Xastir will start and I have entered the basic information. Now, how do I get it to see the DRAWS and start receiving?

Same for PLU (linked to Claws Mail).  How do I start a Peer to Peer session and keep it open? How do I start a normal session to the local RMS Gateway?

Thanks, Ed, KD9FRQ

GPS Extender

Ed Bloom, KD9FRQ
 

My shack in the basement.  I only have two, 16x28 windows. Both have very, very limited view of sky.

What GPS extender do you recommend and why?

Or could I put an SMA bulkhead connector through the wall and get more SMA coax to connect the GPS unit?

Thanks, Ed, KD9FRQ

Re: NWDR15 Check

Ed Bloom, KD9FRQ
 

Basil,

PLU setup seemed to run successfully.  I am getting an error in Claws-Mail when sending.

*Account 'pi@localhost': Connecting to SMTP server smtp.draws:25...

*** smtp.draws:25: unknown host.

*** Error occurred while sending the message.

What did I do wrong?

Ed

On 4/6/2020 1:17 PM, Ed Bloom, KD9FRQ via groups.io wrote:
Thank you, Basil.

Yes, I just tapped enter, accepting all the values as default.

I will move forward the setup of PLU.

Ed Bloom, KD9FRQ
ewbloom@...
Sent from Webmail access


-----Original Message-----
From: Basil Gunn <basil@...>
To: udrc <udrc@nw-digital-radio.groups.io>
Sent: Mon, Apr 6, 2020 12:08 pm
Subject: Re: [draws and udrc] NWDR15 Check


Hi Ed,

> hostname : 1, passwd: 0, logfile: 0

This console output just means that your RPi host name is possibly one
of:

"raspberrypi", "compass", "draws"

which I wouldn't use but doesn't really matter.
Your installation should be fine.

/Basil


Ed Bloom, KD9FRQ via groups.io <ewbloom=verizon.net@groups.io> writes:

> Basil,
>
> I get :
>
> -- app_config.sh core script has NOT been run: hostname : 1, passwd: 0,
> logfile: 0
>
>
> 73s, Ed, KD9FRQ
>
> On 4/5/2020 6:55 PM, Basil Gunn wrote:
>>> I started over because after running the commands below or app_config.sh
>>> core & cd cd n7nix git pull sudo su apt-getupdate apt-getdist-upgrade
>>>
>>> the first time, the cfgcheck stated I did not running app_config yet.
>> Could you please copy & paste the console output of the cfgcheck.sh
>> script.
>> I ran it on all my running RPi's & it looked OK.
>>
>> /Basil n7nix



Re: when will the new hats ship?

 

Still waiting for FABs to ship. Was scheduled for last week but didn’t happen.

Bryan K7UDR

Re: when will the new hats ship?

Charles Blackburn
 

last email was basically a "shrug" ..... first was end of feb, then end of march, now looks to be end of april.

as posted on "the blog" at http://nwdigitalradio.com/stay-at-home-sale-on-the-thumbdv/

TL;DR


The “Stay at Home” order by Governor Inslee of Washington State, has impacted some of our vendors, delaying the DRAWS™ run. We will keep you apprised.

So it’s time for a sale on the ThumbDV™ !

Might as well contact Hams on the reflectors using DSTAR, DMR or Fusion from your PC at home.

Normally $119.95, on Sale NOW for $99.95 at least until the order is lifted, or we run out of inventory.

Price Protection Policy: If you ordered a ThumbDV™ in the last 30 days, email sales@... for a $20 refund.

On 4/6/2020 2:38 PM, Robert J. MIller 8.7 & 24 challenger via groups.io wrote:
Any projected date for the shipment of the new Draws hats?

Thanks




when will the new hats ship?

Robert J. MIller 8.7 & 24 challenger
 

Any projected date for the shipment of the new Draws hats?


Thanks

Re: NWDR15 Check

Ed Bloom, KD9FRQ
 

Thank you, Basil.

Yes, I just tapped enter, accepting all the values as default.

I will move forward the setup of PLU.

Ed Bloom, KD9FRQ
ewbloom@...
Sent from Webmail access


-----Original Message-----
From: Basil Gunn <basil@...>
To: udrc <udrc@nw-digital-radio.groups.io>
Sent: Mon, Apr 6, 2020 12:08 pm
Subject: Re: [draws and udrc] NWDR15 Check


Hi Ed,

> hostname : 1, passwd: 0, logfile: 0

This console output just means that your RPi host name is possibly one
of:

"raspberrypi", "compass", "draws"

which I wouldn't use but doesn't really matter.
Your installation should be fine.

/Basil


Ed Bloom, KD9FRQ via groups.io <ewbloom=verizon.net@groups.io> writes:

> Basil,
>
> I get :
>
> -- app_config.sh core script has NOT been run: hostname : 1, passwd: 0,
> logfile: 0
>
>
> 73s, Ed, KD9FRQ
>
> On 4/5/2020 6:55 PM, Basil Gunn wrote:
>>> I started over because after running the commands below or app_config.sh
>>> core & cd cd n7nix git pull sudo su apt-getupdate apt-getdist-upgrade
>>>
>>> the first time, the cfgcheck stated I did not running app_config yet.
>> Could you please copy & paste the console output of the cfgcheck.sh
>> script.
>> I ran it on all my running RPi's & it looked OK.
>>
>> /Basil n7nix



Re: NWDR15 Check

Basil Gunn
 

Hi Ed,

hostname : 1, passwd: 0, logfile: 0
This console output just means that your RPi host name is possibly one
of:

"raspberrypi", "compass", "draws"

which I wouldn't use but doesn't really matter.
Your installation should be fine.

/Basil


Ed Bloom, KD9FRQ via groups.io <ewbloom=verizon.net@groups.io> writes:

Basil,

I get :

-- app_config.sh core script has NOT been run: hostname : 1, passwd: 0,
logfile: 0


73s, Ed, KD9FRQ

On 4/5/2020 6:55 PM, Basil Gunn wrote:
I started over because after running the commands below or app_config.sh
core & cd cd n7nix git pull sudo su apt-getupdate apt-getdist-upgrade

the first time, the cfgcheck stated I did not running app_config yet.
Could you please copy & paste the console output of the cfgcheck.sh
script.
I ran it on all my running RPi's & it looked OK.

/Basil n7nix

Re: NWDR15 Check

Ed Bloom, KD9FRQ
 

Basil,

I get :

-- app_config.sh core script has NOT been run: hostname : 1, passwd: 0, logfile: 0


73s, Ed, KD9FRQ

On 4/5/2020 6:55 PM, Basil Gunn wrote:
I started over because after running the commands below or app_config.sh
core & cd cd n7nix git pull sudo su apt-getupdate apt-getdist-upgrade

the first time, the cfgcheck stated I did not running app_config yet.
Could you please copy & paste the console output of the cfgcheck.sh
script.
I ran it on all my running RPi's & it looked OK.

/Basil n7nix

Re: NWDR15 Check

Basil Gunn
 

I started over because after running the commands below or app_config.sh
core & cd cd n7nix git pull sudo su apt-getupdate apt-getdist-upgrade

the first time, the cfgcheck stated I did not running app_config yet.
Could you please copy & paste the console output of the cfgcheck.sh
script.
I ran it on all my running RPi's & it looked OK.

/Basil n7nix

Re: NWDR15 Check

Basil Gunn
 

I started over because after running the commands below or app_config.sh
core & cd cd n7nix git pull sudo su apt-getupdate apt-getdist-upgrade

the first time, the cfgcheck stated I did not running app_config yet.
that may be a bug I will look into it.

/Basil

Re: Icom 706MKIIG Setup #icom #ptt

 

I just got to this.   You probably needed to upgrade nodejs ?

# Using Debian, as root
curl -sL https://deb.nodesource.com/setup_13.x | bash -
apt-get install -y nodejs

On Sun, Apr 5, 2020 at 10:46 AM KB5ZUR <kb5zur@...> wrote:
I got it fixed sorry for the prior post.
looks like I am up and going now.
-Kb5zur-David

On Sun, Apr 5, 2020 at 12:22 PM David Savells <kb5zur@...> wrote:
Well I have manages to break draws-manager. I get the following messages when I check the status:
● draws-manager.service - DRAWS™ Manager - A web application to manage the DRAW™ HAT configuration.
   Loaded: loaded (/etc/systemd/system/draws-manager.service; enabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Sun 2020-04-05 12:15:39 CDT; 2min 26s ago
     Docs: https://github.com/nwdigitalradio/draws-manager
  Process: 456 ExecStart=/usr/bin/npm start (code=exited, status=1/FAILURE)
 Main PID: 456 (code=exited, status=1/FAILURE)

Apr 05 12:15:39 DRAWS15 npm[456]: npm ERR! errno 1
Apr 05 12:15:39 DRAWS15 npm[456]: npm ERR! webapp@0.0.1 start: `node ./bin/www`
Apr 05 12:15:39 DRAWS15 npm[456]: npm ERR! Exit status 1
Apr 05 12:15:39 DRAWS15 npm[456]: npm ERR!
Apr 05 12:15:39 DRAWS15 npm[456]: npm ERR! Failed at the webapp@0.0.1 start script.
Apr 05 12:15:39 DRAWS15 npm[456]: npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
Apr 05 12:15:39 DRAWS15 npm[456]: npm ERR! A complete log of this run can be found in:
Apr 05 12:15:39 DRAWS15 npm[456]: npm ERR!     /root/.npm/_logs/2020-04-05T17_15_39_643Z-debug.log
Apr 05 12:15:39 DRAWS15 systemd[1]: draws-manager.service: Main process exited, code=exited, status=1/FAILURE
Apr 05 12:15:39 DRAWS15 systemd[1]: draws-manager.service: Failed with result 'exit-code'.

additional log info:
0 info it worked if it ends with ok
1 warn npm npm does not support Node.js v10.15.2
2 warn npm You should probably upgrade to a newer version of node as we
3 warn npm can't make any promises that npm will work with this version.
4 warn npm Supported releases of Node.js are the latest release of 4, 6, 7, 8, 9.
5 warn npm You can find the latest version at https://nodejs.org/
6 verbose cli [ '/usr/bin/node', '/usr/bin/npm', 'start' ]
7 info using npm@5.8.0
8 info using node@...
9 verbose run-script [ 'prestart', 'start', 'poststart' ]
10 info lifecycle webapp@0.0.1~prestart: webapp@0.0.1
11 info lifecycle webapp@0.0.1~start: webapp@0.0.1
12 verbose lifecycle webapp@0.0.1~start: unsafe-perm in lifecycle true
13 verbose lifecycle webapp@0.0.1~start: PATH: /usr/share/npm/node_modules/npm-lifecycle/node-gyp-bin:/usr/local/var/draws-manager/webapp/node_modules/.bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
14 verbose lifecycle webapp@0.0.1~start: CWD: /usr/local/var/draws-manager/webapp
15 silly lifecycle webapp@0.0.1~start: Args: [ '-c', 'node ./bin/www' ]
16 silly lifecycle webapp@0.0.1~start: Returned: code: 1  signal: null
17 info lifecycle webapp@0.0.1~start: Failed to exec start script
18 verbose stack Error: webapp@0.0.1 start: `node ./bin/www`
18 verbose stack Exit status 1
18 verbose stack     at EventEmitter.<anonymous> (/usr/share/npm/node_modules/npm-lifecycle/index.js:283:16)
18 verbose stack     at EventEmitter.emit (events.js:189:13)
18 verbose stack     at ChildProcess.<anonymous> (/usr/share/npm/node_modules/npm-lifecycle/lib/spawn.js:55:14)
18 verbose stack     at ChildProcess.emit (events.js:189:13)
18 verbose stack     at maybeClose (internal/child_process.js:970:16)
18 verbose stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:259:5)
19 verbose pkgid webapp@0.0.1
20 verbose cwd /usr/local/var/draws-manager/webapp
21 verbose Linux 4.19.97-v7+
22 verbose argv "/usr/bin/node" "/usr/bin/npm" "start"
23 verbose node v10.15.2
24 verbose npm  v5.8.0
25 error code ELIFECYCLE
26 error errno 1
27 error webapp@0.0.1 start: `node ./bin/www`
27 error Exit status 1
28 error Failed at the webapp@0.0.1 start script.
28 error This is probably not a problem with npm. There is likely additional logging output above.
29 verbose exit [ 1, true ]



Any ideas on how to fix this ?

-Kb5zur David


On Sat, Apr 4, 2020 at 1:22 PM John D Hays - K7VE <john@...> wrote:
As I recall WSJT-X uses Hamlin/CAT for PTT. 

On Sat, Apr 4, 2020, 10:55 KB5ZUR <kb5zur@...> wrote:
I'm struggling with the TX audio settings in JS8Call. When i use the recommended settings based on the 0.4V Peak to Peak value for my ICOM 706, I don't seem to output any power. When I adjust the values up, I get power output but no replies to my CQ's or replies to other stations I can hear.

I would like to do some testing in WSJT-X Ver 2.1.2 but don't see a way PTT with the script file.  

2 Questions: 
Can you recommend TX Audio setting for my ICOM706MkIIG 
Do you know if WSJT-X supports Advanced PTT settings for the script file for keying?

On Sat, Apr 4, 2020 at 11:10 AM David Savells <kb5zur@...> wrote:
Couldnt find advanced PTT setting in WSJT-X 

which ptt_ctrl.sh showed  /home/pi/bin/ptt_ctrl.sh
So I set that path in JS8Call and it is now keying the radio.
Just now getting into the TX audio adjustments but looks like I can TX using the Test PTT button in JS8Call setup.
Ill follow up once I can confirm proper operation
Thanks again for your help.
-Kb5zur David


On Sat, Apr 4, 2020 at 10:55 AM Basil Gunn <basil@...> wrote:

Hi David,

> Try using the path that comes back from the above command for js8call
> /home/pi/bin/ptt_ctrl.sh %1
>
> I'll test this later on today.

Using full path seems to work fine for script /home/pi/bin/ptt_ctrl.sh
%1 and js8call

Have you used wstx?
What did you use for PTT control when using wstx and ICOM 706MKIIg?

/Basil n7niix





--
John D. Hays
Kingston, WA
K7VE

 

Re: NWDR15 Check

Ed Bloom, KD9FRQ
 

Basil,

Thank you.  That is how my aplay -l looks.

I started over because after running the commands below or app_config.sh core & cd cd n7nix git pull sudo su apt-getupdate apt-getdist-upgrade

the first time, the cfgcheck stated I did not running app_config yet.

I will see what I get this time.

Thanks again.

Ed

On 4/5/2020 5:10 PM, Basil Gunn wrote:
Hi Ed,

What do I need to edit to move the DRAWS to card 0 so the install may
continue?
You should be fine to continue the install as is.

What my aplay output looks like:

$ aplay -l
**** List of PLAYBACK Hardware Devices ****
card 0: ALSA [bcm2835 ALSA], device 0: bcm2835 ALSA [bcm2835 ALSA]
Subdevices: 7/7
Subdevice #0: subdevice #0
Subdevice #1: subdevice #1
Subdevice #2: subdevice #2
Subdevice #3: subdevice #3
Subdevice #4: subdevice #4
Subdevice #5: subdevice #5
Subdevice #6: subdevice #6
card 0: ALSA [bcm2835 ALSA], device 1: bcm2835 IEC958/HDMI [bcm2835 IEC958/HDMI]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 0: ALSA [bcm2835 ALSA], device 2: bcm2835 IEC958/HDMI1 [bcm2835 IEC958/HDMI1]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 1: udrc [udrc], device 0: bcm2835-i2s-tlv320aic32x4-hifi tlv320aic32x4-hifi-0 [bcm2835-i2s-tlv320aic32x4-hifi tlv320aic32x4-hifi-0]
Subdevices: 0/1
Subdevice #0: subdevice #0

All this means is that the RPi on board audio device is activated and
the udrc/draws sound device is showing up as the second device. If you
don't like that then comment out (with a #) the line: dtparam=audio=on
probably the last line in the /boot/config.txt file.

/Basil n7nix


Ed Bloom, KD9FRQ via groups.io <ewbloom=verizon.net@groups.io> writes:

|After sitting idle for a bit, I opted to move up from NWDR07 to NWDR15
using a Start From Scratch approach. I am using a Pi 3. After I boot and
follow the first steps offered by the OS and then reboot, I run the
aplay -l command and get : card 1: udrc [udrc], device 0:
bcm2835-i2s-tlv320aic32x4-hifi tlv320aic32x4-hifi-0 [] NOT card 0: My
card 0 shows up three times, each with different device count (7/7, 1/1,
1/1) and ALSA [bcm2535 ALSA] So, I have stopped and have not run the
commands below or app_config.sh core |
|

|cd cd n7nix git pull sudo su apt-getupdate apt-getdist-upgrade What do
I need to edit to move the DRAWS to card 0 so the install may continue?
Ed, KD9FRQ |

Re: NWDR15 Check

Basil Gunn
 

Hi Ed,

What do I need to edit to move the DRAWS to card 0 so the install may
continue?
You should be fine to continue the install as is.

What my aplay output looks like:

$ aplay -l
**** List of PLAYBACK Hardware Devices ****
card 0: ALSA [bcm2835 ALSA], device 0: bcm2835 ALSA [bcm2835 ALSA]
Subdevices: 7/7
Subdevice #0: subdevice #0
Subdevice #1: subdevice #1
Subdevice #2: subdevice #2
Subdevice #3: subdevice #3
Subdevice #4: subdevice #4
Subdevice #5: subdevice #5
Subdevice #6: subdevice #6
card 0: ALSA [bcm2835 ALSA], device 1: bcm2835 IEC958/HDMI [bcm2835 IEC958/HDMI]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 0: ALSA [bcm2835 ALSA], device 2: bcm2835 IEC958/HDMI1 [bcm2835 IEC958/HDMI1]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 1: udrc [udrc], device 0: bcm2835-i2s-tlv320aic32x4-hifi tlv320aic32x4-hifi-0 [bcm2835-i2s-tlv320aic32x4-hifi tlv320aic32x4-hifi-0]
Subdevices: 0/1
Subdevice #0: subdevice #0

All this means is that the RPi on board audio device is activated and
the udrc/draws sound device is showing up as the second device. If you
don't like that then comment out (with a #) the line: dtparam=audio=on
probably the last line in the /boot/config.txt file.

/Basil n7nix


Ed Bloom, KD9FRQ via groups.io <ewbloom=verizon.net@groups.io> writes:

|After sitting idle for a bit, I opted to move up from NWDR07 to NWDR15
using a Start From Scratch approach. I am using a Pi 3. After I boot and
follow the first steps offered by the OS and then reboot, I run the
aplay -l command and get : card 1: udrc [udrc], device 0:
bcm2835-i2s-tlv320aic32x4-hifi tlv320aic32x4-hifi-0 [] NOT card 0: My
card 0 shows up three times, each with different device count (7/7, 1/1,
1/1) and ALSA [bcm2535 ALSA] So, I have stopped and have not run the
commands below or app_config.sh core |
|

|cd cd n7nix git pull sudo su apt-getupdate apt-getdist-upgrade What do
I need to edit to move the DRAWS to card 0 so the install may continue?
Ed, KD9FRQ |

NWDR15 Check

Ed Bloom, KD9FRQ
 

After sitting idle for a bit, I opted to move up from NWDR07 to NWDR15 using a Start From Scratch approach.
I am using a Pi 3.

After I boot and follow the first steps offered by the OS and then reboot, I run the aplay -l command and get :

card 1: udrc [udrc], device 0: bcm2835-i2s-tlv320aic32x4-hifi tlv320aic32x4-hifi-0 []

NOT card 0:

My card 0 shows up three times, each with different device count (7/7, 1/1, 1/1) and ALSA [bcm2535 ALSA]

So, I have stopped and have not run the commands below or app_config.sh core

cd
cd n7nix
git pull

sudo su
apt-get update
apt-get dist-upgrade

What do I need to edit to move the DRAWS to card 0 so the install may continue?

Ed, KD9FRQ

Re: DRAWS

Paul Noa
 

Basil,

I am still waiting to here from back from Bryan, but in the mean time I checked my three units and they all have the wrong value components stuffed.

That is 6 each 100K ohm resistors and 2 each capacitors.  Does explain some of my problems?

Paul

Re: Icom 706MKIIG Setup #icom #ptt

KB5ZUR
 

I got it fixed sorry for the prior post.
looks like I am up and going now.
-Kb5zur-David

On Sun, Apr 5, 2020 at 12:22 PM David Savells <kb5zur@...> wrote:
Well I have manages to break draws-manager. I get the following messages when I check the status:
● draws-manager.service - DRAWS™ Manager - A web application to manage the DRAW™ HAT configuration.
   Loaded: loaded (/etc/systemd/system/draws-manager.service; enabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Sun 2020-04-05 12:15:39 CDT; 2min 26s ago
     Docs: https://github.com/nwdigitalradio/draws-manager
  Process: 456 ExecStart=/usr/bin/npm start (code=exited, status=1/FAILURE)
 Main PID: 456 (code=exited, status=1/FAILURE)

Apr 05 12:15:39 DRAWS15 npm[456]: npm ERR! errno 1
Apr 05 12:15:39 DRAWS15 npm[456]: npm ERR! webapp@0.0.1 start: `node ./bin/www`
Apr 05 12:15:39 DRAWS15 npm[456]: npm ERR! Exit status 1
Apr 05 12:15:39 DRAWS15 npm[456]: npm ERR!
Apr 05 12:15:39 DRAWS15 npm[456]: npm ERR! Failed at the webapp@0.0.1 start script.
Apr 05 12:15:39 DRAWS15 npm[456]: npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
Apr 05 12:15:39 DRAWS15 npm[456]: npm ERR! A complete log of this run can be found in:
Apr 05 12:15:39 DRAWS15 npm[456]: npm ERR!     /root/.npm/_logs/2020-04-05T17_15_39_643Z-debug.log
Apr 05 12:15:39 DRAWS15 systemd[1]: draws-manager.service: Main process exited, code=exited, status=1/FAILURE
Apr 05 12:15:39 DRAWS15 systemd[1]: draws-manager.service: Failed with result 'exit-code'.

additional log info:
0 info it worked if it ends with ok
1 warn npm npm does not support Node.js v10.15.2
2 warn npm You should probably upgrade to a newer version of node as we
3 warn npm can't make any promises that npm will work with this version.
4 warn npm Supported releases of Node.js are the latest release of 4, 6, 7, 8, 9.
5 warn npm You can find the latest version at https://nodejs.org/
6 verbose cli [ '/usr/bin/node', '/usr/bin/npm', 'start' ]
7 info using npm@5.8.0
8 info using node@...
9 verbose run-script [ 'prestart', 'start', 'poststart' ]
10 info lifecycle webapp@0.0.1~prestart: webapp@0.0.1
11 info lifecycle webapp@0.0.1~start: webapp@0.0.1
12 verbose lifecycle webapp@0.0.1~start: unsafe-perm in lifecycle true
13 verbose lifecycle webapp@0.0.1~start: PATH: /usr/share/npm/node_modules/npm-lifecycle/node-gyp-bin:/usr/local/var/draws-manager/webapp/node_modules/.bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
14 verbose lifecycle webapp@0.0.1~start: CWD: /usr/local/var/draws-manager/webapp
15 silly lifecycle webapp@0.0.1~start: Args: [ '-c', 'node ./bin/www' ]
16 silly lifecycle webapp@0.0.1~start: Returned: code: 1  signal: null
17 info lifecycle webapp@0.0.1~start: Failed to exec start script
18 verbose stack Error: webapp@0.0.1 start: `node ./bin/www`
18 verbose stack Exit status 1
18 verbose stack     at EventEmitter.<anonymous> (/usr/share/npm/node_modules/npm-lifecycle/index.js:283:16)
18 verbose stack     at EventEmitter.emit (events.js:189:13)
18 verbose stack     at ChildProcess.<anonymous> (/usr/share/npm/node_modules/npm-lifecycle/lib/spawn.js:55:14)
18 verbose stack     at ChildProcess.emit (events.js:189:13)
18 verbose stack     at maybeClose (internal/child_process.js:970:16)
18 verbose stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:259:5)
19 verbose pkgid webapp@0.0.1
20 verbose cwd /usr/local/var/draws-manager/webapp
21 verbose Linux 4.19.97-v7+
22 verbose argv "/usr/bin/node" "/usr/bin/npm" "start"
23 verbose node v10.15.2
24 verbose npm  v5.8.0
25 error code ELIFECYCLE
26 error errno 1
27 error webapp@0.0.1 start: `node ./bin/www`
27 error Exit status 1
28 error Failed at the webapp@0.0.1 start script.
28 error This is probably not a problem with npm. There is likely additional logging output above.
29 verbose exit [ 1, true ]



Any ideas on how to fix this ?

-Kb5zur David


On Sat, Apr 4, 2020 at 1:22 PM John D Hays - K7VE <john@...> wrote:
As I recall WSJT-X uses Hamlin/CAT for PTT. 

On Sat, Apr 4, 2020, 10:55 KB5ZUR <kb5zur@...> wrote:
I'm struggling with the TX audio settings in JS8Call. When i use the recommended settings based on the 0.4V Peak to Peak value for my ICOM 706, I don't seem to output any power. When I adjust the values up, I get power output but no replies to my CQ's or replies to other stations I can hear.

I would like to do some testing in WSJT-X Ver 2.1.2 but don't see a way PTT with the script file.  

2 Questions: 
Can you recommend TX Audio setting for my ICOM706MkIIG 
Do you know if WSJT-X supports Advanced PTT settings for the script file for keying?

On Sat, Apr 4, 2020 at 11:10 AM David Savells <kb5zur@...> wrote:
Couldnt find advanced PTT setting in WSJT-X 

which ptt_ctrl.sh showed  /home/pi/bin/ptt_ctrl.sh
So I set that path in JS8Call and it is now keying the radio.
Just now getting into the TX audio adjustments but looks like I can TX using the Test PTT button in JS8Call setup.
Ill follow up once I can confirm proper operation
Thanks again for your help.
-Kb5zur David


On Sat, Apr 4, 2020 at 10:55 AM Basil Gunn <basil@...> wrote:

Hi David,

> Try using the path that comes back from the above command for js8call
> /home/pi/bin/ptt_ctrl.sh %1
>
> I'll test this later on today.

Using full path seems to work fine for script /home/pi/bin/ptt_ctrl.sh
%1 and js8call

Have you used wstx?
What did you use for PTT control when using wstx and ICOM 706MKIIg?

/Basil n7niix



Re: Icom 706MKIIG Setup #icom #ptt

KB5ZUR
 

Well I have manages to break draws-manager. I get the following messages when I check the status:
● draws-manager.service - DRAWS™ Manager - A web application to manage the DRAW™ HAT configuration.
   Loaded: loaded (/etc/systemd/system/draws-manager.service; enabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Sun 2020-04-05 12:15:39 CDT; 2min 26s ago
     Docs: https://github.com/nwdigitalradio/draws-manager
  Process: 456 ExecStart=/usr/bin/npm start (code=exited, status=1/FAILURE)
 Main PID: 456 (code=exited, status=1/FAILURE)

Apr 05 12:15:39 DRAWS15 npm[456]: npm ERR! errno 1
Apr 05 12:15:39 DRAWS15 npm[456]: npm ERR! webapp@0.0.1 start: `node ./bin/www`
Apr 05 12:15:39 DRAWS15 npm[456]: npm ERR! Exit status 1
Apr 05 12:15:39 DRAWS15 npm[456]: npm ERR!
Apr 05 12:15:39 DRAWS15 npm[456]: npm ERR! Failed at the webapp@0.0.1 start script.
Apr 05 12:15:39 DRAWS15 npm[456]: npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
Apr 05 12:15:39 DRAWS15 npm[456]: npm ERR! A complete log of this run can be found in:
Apr 05 12:15:39 DRAWS15 npm[456]: npm ERR!     /root/.npm/_logs/2020-04-05T17_15_39_643Z-debug.log
Apr 05 12:15:39 DRAWS15 systemd[1]: draws-manager.service: Main process exited, code=exited, status=1/FAILURE
Apr 05 12:15:39 DRAWS15 systemd[1]: draws-manager.service: Failed with result 'exit-code'.

additional log info:
0 info it worked if it ends with ok
1 warn npm npm does not support Node.js v10.15.2
2 warn npm You should probably upgrade to a newer version of node as we
3 warn npm can't make any promises that npm will work with this version.
4 warn npm Supported releases of Node.js are the latest release of 4, 6, 7, 8, 9.
5 warn npm You can find the latest version at https://nodejs.org/
6 verbose cli [ '/usr/bin/node', '/usr/bin/npm', 'start' ]
7 info using npm@5.8.0
8 info using node@...
9 verbose run-script [ 'prestart', 'start', 'poststart' ]
10 info lifecycle webapp@0.0.1~prestart: webapp@0.0.1
11 info lifecycle webapp@0.0.1~start: webapp@0.0.1
12 verbose lifecycle webapp@0.0.1~start: unsafe-perm in lifecycle true
13 verbose lifecycle webapp@0.0.1~start: PATH: /usr/share/npm/node_modules/npm-lifecycle/node-gyp-bin:/usr/local/var/draws-manager/webapp/node_modules/.bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
14 verbose lifecycle webapp@0.0.1~start: CWD: /usr/local/var/draws-manager/webapp
15 silly lifecycle webapp@0.0.1~start: Args: [ '-c', 'node ./bin/www' ]
16 silly lifecycle webapp@0.0.1~start: Returned: code: 1  signal: null
17 info lifecycle webapp@0.0.1~start: Failed to exec start script
18 verbose stack Error: webapp@0.0.1 start: `node ./bin/www`
18 verbose stack Exit status 1
18 verbose stack     at EventEmitter.<anonymous> (/usr/share/npm/node_modules/npm-lifecycle/index.js:283:16)
18 verbose stack     at EventEmitter.emit (events.js:189:13)
18 verbose stack     at ChildProcess.<anonymous> (/usr/share/npm/node_modules/npm-lifecycle/lib/spawn.js:55:14)
18 verbose stack     at ChildProcess.emit (events.js:189:13)
18 verbose stack     at maybeClose (internal/child_process.js:970:16)
18 verbose stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:259:5)
19 verbose pkgid webapp@0.0.1
20 verbose cwd /usr/local/var/draws-manager/webapp
21 verbose Linux 4.19.97-v7+
22 verbose argv "/usr/bin/node" "/usr/bin/npm" "start"
23 verbose node v10.15.2
24 verbose npm  v5.8.0
25 error code ELIFECYCLE
26 error errno 1
27 error webapp@0.0.1 start: `node ./bin/www`
27 error Exit status 1
28 error Failed at the webapp@0.0.1 start script.
28 error This is probably not a problem with npm. There is likely additional logging output above.
29 verbose exit [ 1, true ]



Any ideas on how to fix this ?

-Kb5zur David


On Sat, Apr 4, 2020 at 1:22 PM John D Hays - K7VE <john@...> wrote:
As I recall WSJT-X uses Hamlin/CAT for PTT. 

On Sat, Apr 4, 2020, 10:55 KB5ZUR <kb5zur@...> wrote:
I'm struggling with the TX audio settings in JS8Call. When i use the recommended settings based on the 0.4V Peak to Peak value for my ICOM 706, I don't seem to output any power. When I adjust the values up, I get power output but no replies to my CQ's or replies to other stations I can hear.

I would like to do some testing in WSJT-X Ver 2.1.2 but don't see a way PTT with the script file.  

2 Questions: 
Can you recommend TX Audio setting for my ICOM706MkIIG 
Do you know if WSJT-X supports Advanced PTT settings for the script file for keying?

On Sat, Apr 4, 2020 at 11:10 AM David Savells <kb5zur@...> wrote:
Couldnt find advanced PTT setting in WSJT-X 

which ptt_ctrl.sh showed  /home/pi/bin/ptt_ctrl.sh
So I set that path in JS8Call and it is now keying the radio.
Just now getting into the TX audio adjustments but looks like I can TX using the Test PTT button in JS8Call setup.
Ill follow up once I can confirm proper operation
Thanks again for your help.
-Kb5zur David


On Sat, Apr 4, 2020 at 10:55 AM Basil Gunn <basil@...> wrote:

Hi David,

> Try using the path that comes back from the above command for js8call
> /home/pi/bin/ptt_ctrl.sh %1
>
> I'll test this later on today.

Using full path seems to work fine for script /home/pi/bin/ptt_ctrl.sh
%1 and js8call

Have you used wstx?
What did you use for PTT control when using wstx and ICOM 706MKIIg?

/Basil n7niix