Date   
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



Re: DRAWS Power

Mike B
 

I saw another thread with an issue that might involve power, so I figured I would just add to this one.

If you use an external power supply for your Pi, be very selective on your cables   I picked up a USB power meter and load.

I tested ALL of my USB cables.

On some standard micro usb cables I had as much as 1.3V drop with a 1A load (cable about 2' long) . Most crummy ones had 0.5-0.9V drop at 1A

The trend was (obviously) almost double the voltage drop over 2A.

There were no visual physical characteristics that could identify why one random cable performed poorer than another (like length, cable thickness, color, style)...I couldn't grab one out of the pile and predict it's outcome.

The cables I tested that had consistently virtually no voltage drop at even 2A (standard 2A wall wart still put tested 5V output at the microusb connector) were the Anker Powerlinee Usb cables.  I bought them because many of my other cables were performing so badly (lighting bolt on the pi, errors and crashes).  I didn't believe they would perform any better, but they got good reviews outside Amazon so I thought I would give them a shot.

I think part of the problem is the microusb standard wasn't set very high in the beginning (unlike the USB-C)

Now the Pi4 uses a USB C, but apparently there are some compatibility issues with some power supplies...I haven't noticed any but apparently it is a thing.

Re: Icom 706MKIIG Setup #icom #ptt

 

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
 

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: Keying FreeDV with GPIO #draws #freedv

Mike B
 

I am bringing this topic back up...does anyone have a working FreeDV on DRAWS yet...

I am just asking for completeness...

Mike

KF5DEY

Re: Icom 706MKIIG Setup #icom #ptt

KB5ZUR
 

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

Basil Gunn
 

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

 

Also make sure it is executable. 


On Sat, Apr 4, 2020, 07:44 Basil Gunn <basil@...> wrote:


> Tried ~/n7nix/bin/ptt_ctrl.sh %1 and cant get it to work (with
> JS8Cal)l.

Most likely needs an absolute path. Also ptt_ctrl.sh should be in your
path. Type this at console

which ptt_ctrl.sh

Try using the path that comes back from the above command for wsjtx
/home/pi/bin/ptt_ctrl.sh %1

I'll test this later on today.

/Basil n7nix


> Do I need a different command for your script?
> Please advise.
> -Kb5zur David
>
>
> On Fri, Apr 3, 2020 at 5:39 PM Basil Gunn <basil@...> wrote:
>
>>
>> The script that John had you link to will not work when using PIN=12
>> because it is expecting wiringpi gpio pin numbers instead of BCM_GPIO
>> pin numbers. DRAWS hat uses pin numbers 12 for the left port & 23 for
>> the right port which are BCM_GPIO numbers. You can fix the script by
>> using the -g argument with the gpio command ie.
>>
>> PIN=12
>>
>> gpio -g write $PIN 0
>> gpio -g write $PIN 1
>>
>> From man gpio
>>  -g     Use  the  BCM_GPIO pins numbers rather than wiringPi pin numbers.
>>
>> or just use the ptt_ctrl.sh script which I maintain.
>>
>> /Basil n7nix
>>
>>
>> KB5ZUR <kb5zur@...> writes:
>>
>> > Thanks John,
>> > I got script set up and can run it but it doesn't turn on the GPIO. I'm
>> > using left hand DIN connector and calling for pin 12.
>> > gpio -g toggle 12 keys and unkeys radio.
>> > ./ptt.sh on doesn't key radio. Script does run just but no change on GPIO
>> > Do I need to configure a permission of something else?
>> > -Kb5zur David
>> >
>> > On Fri, Apr 3, 2020 at 3:31 PM John D Hays - K7VE <john@...> wrote:
>> >
>> >> https://gist.github.com/jsherer/dd09895ab23bdf571e2117cdd814c198
>> >>
>> >>
>> >> On Fri, Apr 3, 2020 at 1:27 PM KB5ZUR <kb5zur@...> wrote:
>> >>
>> >>>
>> >>> I saw  post regarding setting up an Icom 706 with Draws. I'm trying to
>> >>> use JS8Call with my ICOM706MkIIg / DRAWS set up and have TX issues.
>> Receive
>> >>> works great and see stations from all over the place.
>> >>>
>> >>> I can toggle the TX of the radio using the toggle GPIO command but
>> can't
>> >>> figure out how to link that to the tx settings for JS8CALL.
>> >>>
>> >>> Can anyone help.
>> >>>
>> >>> Thanks,
>> >>> -KB5ZUR David
>> >>>
>> >>>
>> >>>
>> >>>
>> >>
>> >> --
>> >> John D. Hays
>> >> Kingston, WA
>> >> K7VE
>> >>
>> >>
>> >>
>> >>
>> >>
>> >>
>> >
>> >
>>
>>
>>
>>
>
>



Re: Icom 706MKIIG Setup #icom #ptt

Basil Gunn
 

Tried ~/n7nix/bin/ptt_ctrl.sh %1 and cant get it to work (with
JS8Cal)l.
Most likely needs an absolute path. Also ptt_ctrl.sh should be in your
path. Type this at console

which ptt_ctrl.sh

Try using the path that comes back from the above command for wsjtx
/home/pi/bin/ptt_ctrl.sh %1

I'll test this later on today.

/Basil n7nix


Do I need a different command for your script?
Please advise.
-Kb5zur David


On Fri, Apr 3, 2020 at 5:39 PM Basil Gunn <@basil860> wrote:


The script that John had you link to will not work when using PIN=12
because it is expecting wiringpi gpio pin numbers instead of BCM_GPIO
pin numbers. DRAWS hat uses pin numbers 12 for the left port & 23 for
the right port which are BCM_GPIO numbers. You can fix the script by
using the -g argument with the gpio command ie.

PIN=12

gpio -g write $PIN 0
gpio -g write $PIN 1

From man gpio
-g Use the BCM_GPIO pins numbers rather than wiringPi pin numbers.

or just use the ptt_ctrl.sh script which I maintain.

/Basil n7nix


KB5ZUR <@KB5ZUR> writes:

Thanks John,
I got script set up and can run it but it doesn't turn on the GPIO. I'm
using left hand DIN connector and calling for pin 12.
gpio -g toggle 12 keys and unkeys radio.
./ptt.sh on doesn't key radio. Script does run just but no change on GPIO
Do I need to configure a permission of something else?
-Kb5zur David

On Fri, Apr 3, 2020 at 3:31 PM John D Hays - K7VE <@john_hays> wrote:

https://gist.github.com/jsherer/dd09895ab23bdf571e2117cdd814c198


On Fri, Apr 3, 2020 at 1:27 PM KB5ZUR <@KB5ZUR> wrote:


I saw post regarding setting up an Icom 706 with Draws. I'm trying to
use JS8Call with my ICOM706MkIIg / DRAWS set up and have TX issues.
Receive
works great and see stations from all over the place.

I can toggle the TX of the radio using the toggle GPIO command but
can't
figure out how to link that to the tx settings for JS8CALL.

Can anyone help.

Thanks,
-KB5ZUR David



--
John D. Hays
Kingston, WA
K7VE







Re: Icom 706MKIIG Setup #icom #ptt

KB5ZUR
 

Thanks,
I have both scripts working now. Thanks for your help!
Added this in the "PTT Command" setting in the Radio / Rig Options tab:
~/ptt.sh %1 and this seems to work for ptt.sh script
Tried ~/n7nix/bin/ptt_ctrl.sh %1 and cant get it to work (with JS8Cal)l.
Do I need a different command for your script?
Please advise.
-Kb5zur David


On Fri, Apr 3, 2020 at 5:39 PM Basil Gunn <basil@...> wrote:

The script that John had you link to will not work when using PIN=12
because it is expecting wiringpi gpio pin numbers instead of BCM_GPIO
pin numbers. DRAWS hat uses pin numbers 12 for the left port & 23 for
the right port which are BCM_GPIO numbers. You can fix the script by
using the -g argument with the gpio command ie.

PIN=12

gpio -g write $PIN 0
gpio -g write $PIN 1

From man gpio
 -g     Use  the  BCM_GPIO pins numbers rather than wiringPi pin numbers.

or just use the ptt_ctrl.sh script which I maintain.

/Basil n7nix


KB5ZUR <kb5zur@...> writes:

> Thanks John,
> I got script set up and can run it but it doesn't turn on the GPIO. I'm
> using left hand DIN connector and calling for pin 12.
> gpio -g toggle 12 keys and unkeys radio.
> ./ptt.sh on doesn't key radio. Script does run just but no change on GPIO
> Do I need to configure a permission of something else?
> -Kb5zur David
>
> On Fri, Apr 3, 2020 at 3:31 PM John D Hays - K7VE <john@...> wrote:
>
>> https://gist.github.com/jsherer/dd09895ab23bdf571e2117cdd814c198
>>
>>
>> On Fri, Apr 3, 2020 at 1:27 PM KB5ZUR <kb5zur@...> wrote:
>>
>>>
>>> I saw  post regarding setting up an Icom 706 with Draws. I'm trying to
>>> use JS8Call with my ICOM706MkIIg / DRAWS set up and have TX issues. Receive
>>> works great and see stations from all over the place.
>>>
>>> I can toggle the TX of the radio using the toggle GPIO command but can't
>>> figure out how to link that to the tx settings for JS8CALL.
>>>
>>> Can anyone help.
>>>
>>> Thanks,
>>> -KB5ZUR David
>>>
>>>
>>>
>>>
>>
>> --
>> John D. Hays
>> Kingston, WA
>> K7VE
>>
>>
>>
>>
>>
>>
>
>



Re: #DRAWS oddity, GPS and ALSA headaches #draws

Mike B
 

I am using this Adafruit antenna...because it has a 5M long cable...

https://www.amazon.com/gp/product/B013EUOCZ6/ref=ppx_yo_dt_b_search_asin_title?ie=UTF8&psc=1

Re: #DRAWS oddity, GPS and ALSA headaches #draws

Basil Gunn
 

Hi Jack,

It also turns out that the original GPS/LNA antenna had gone bad along with
the Pi3B+. It was working before the RPi started into the overheating
problem. So what ever started the heating problem took out the ability to
connect to the DRAWS hat and apparently the GPS antenna...

I tried the GPS antenna from the other DRAWS unit I have in my GO box and it
came right up. Just ordered another from you.
I found these also work:
https://www.amazon.com/gp/product/B00LXRQY9A/ref=ppx_yo_dt_b_search_asin_title

Note: The Pi4 B+ really needs a fan... runs 55 to 60C without, 35-37C with.
Had a 12V microfan sitting in the junk box, wired it in, and the Pi stays
cool now.
Yes I agree. Pi4's run cool enough when laying naked on my bench but as
soon as you put them into any kind of enclosure they heat up.

I have a case on back order. Does it have a place for a fan mount?
Don't know. Bryan or John need to answer that.

Jack - kd4iz

Re: #DRAWS oddity, GPS and ALSA headaches #draws

Jack Spitznagel
 

Basil,

The saga continues.

It also turns out that the original GPS/LNA antenna had gone bad along with
the Pi3B+. It was working before the RPi started into the overheating
problem. So what ever started the heating problem took out the ability to
connect to the DRAWS hat and apparently the GPS antenna...

I tried the GPS antenna from the other DRAWS unit I have in my GO box and it
came right up. Just ordered another from you.

Note: The Pi4 B+ really needs a fan... runs 55 to 60C without, 35-37C with.
Had a 12V microfan sitting in the junk box, wired it in, and the Pi stays
cool now.

I have a case on back order. Does it have a place for a fan mount?

Jack - kd4iz

-----Original Message-----
From: udrc@nw-digital-radio.groups.io <udrc@nw-digital-radio.groups.io> On
Behalf Of Basil Gunn
Sent: Wednesday, April 1, 2020 19:28
To: udrc@nw-digital-radio.groups.io
Subject: Re: [draws and udrc] #DRAWS oddity, GPS and ALSA headaches


Hi Jack,
Taking your responses out of order.

it ain't worth fretting about. Solution found.
Yep, totally agree. Get another RPi and continue having some fun. A friend
of mine had exactly the same symptom on a Pi 3B. I have 6 RPi's on my bench
running 24/7 and haven't seen the problem with any yet. At least two of the
RPi's are RMS Gateways that have been running for a couple of years.

I am going to add a cron job to all my RPis that check's being throttle &
over temperature as in the case you had where vcgencmd get_throttled
returned 0xd0005.

vcgencmd get_throttled
https://www.raspberrypi.org/documentation/raspbian/applications/vcgencmd.md

// Is it OK to run a Pi4 off the DRAWS buck regulator? - I vaguely
remember discussion concluding it was.
Yep. I have 2 RPi 4's (2GB, 4GB) running powered by the DRAWS 12 V buck
regulator with no problem. Actually all my RPi's run from 12 V. I never have
problems with under voltage & it is a lot easier to manage a bunch of power
pole connectors than a bunch of wall warts plugged into a power strip.

// it is on all 40 pins correctly - that is one of my personal QC
checks - burnt up my first pi making that error
You are not an RPi expert unless you burn at least one up.
I killed two due to mDin6 control cable laying on antenna coax. Didn't learn
my lesson the first time.

Glad to hear you are back up & running.
/Basil n7nix

Jack Spitznagel <@flyingfrawg> writes:

Hi Basil,

Good news/bad news story:
DRAWS hat appears to be OK, the Pi3B+ is a sick puppy. Silver lining:
discovered just how fast everything DRAWS seems to respond with a Pi4.
That may be the replacement board I pick. The 1GB versions have gotten
fairly cheap.

See inline after your suggestions below:

* Keep a continuous eye on the temperature In a console window cd cd
n7nix/debug watch ./pitemp.sh
// never bothered with pitemp.sh - just used vcgencmd measure_temp to
start
with & GPU temp
// kept rising, so removed the DRAWS board, let the Pi cool, booted
vanilla
Rasbian Buster
// and the GPU temp headed toward 65C very quickly. Both GPU and CPU
sinks
were very hot to touch so
// shut it down so not to waste time to create pitemp.sh on the sick
Pi in
vanilla buster.
// AT this point I decided the Pi3B+ board was ailing and did not push it.
* Using pitemp.sh note the temperature at boot & after 1/2 hour
// Skipped this as noted above
* Removed the DRAWS hat, boot, note the temperature & after a 1/2 hour
// Skipped, see above
* When you re-install DRAWS hat check for being off by one on the
40pin connector.
// it is on all 40 pins correctly - that is one of my personal QC
checks -
burnt up my first pi making that error

* Power down RPi with DRAWS hat, let RPi cool down At cool power up is
the DRAWS hat working?
* just run alsa-show.sh and look for something reasonable.
// I did this and the symptoms were the same, nothing in alsa-show.sh
output and nothing
// from gpsmon other than it "could not find the device at localhost
port
2XXX" whatever.

* Do a close visual inspection of the DRAWS hat & RPi.
* Anything look charred?
// Nope! Just two very hot to touch processors - both have heat sinks
on
them too! That may have
// been what prevented a total meltdown.
* Feel the USB cable powering your RPi does it feel warm?
// Neither power cable configuration got warm
More things to try as you suggested.

The Pi did not seem to be acting sick by itself.
Could it be the power source or should I not trust the PI at all?
// wired the buck regulator feed to the display power line and saw the
same
symptoms with the Pi3B+
// THEN I subbed in a Pi4 (4GB) that I have been playing with and it
fired
right up. DRAWS came up and
// behaved normally for alsa-show and gpsmon including no lightning
bolt
while running off the buck
// regulator on the DRAWS board.
QUESTION:
// Is it OK to run a Pi4 off the DRAWS buck regulator? - I vaguely
remember
discussion concluding it was.

It is suspicious to me that the RPi gives the low voltage symptom
(lightning bolt). Is it the power supply or is the DRAWS card loading
the RPi voltage source?

The following is not a bad idea but I would confirm that there is not
something seriously fried on the DRAWS hat first.

If you think I can trust the Pi, I could always take a different
power supply tactic and use the buck supply line in the DRAWs card
for the Pi and feed the display from a separate line.
SO: The Pi4 is good with the DRAWS but the Pi3 is the second I have
consigned to the junk bin. Something probably munged up the GPIO lines
needed by the sound and GPS subsystems - have no idea what and @ <$30
for a replacement, it ain't worth fretting about. Solution found.

Re: Icom 706MKIIG Setup #icom #ptt

Basil Gunn
 

The script that John had you link to will not work when using PIN=12
because it is expecting wiringpi gpio pin numbers instead of BCM_GPIO
pin numbers. DRAWS hat uses pin numbers 12 for the left port & 23 for
the right port which are BCM_GPIO numbers. You can fix the script by
using the -g argument with the gpio command ie.

PIN=12

gpio -g write $PIN 0
gpio -g write $PIN 1

From man gpio
-g Use the BCM_GPIO pins numbers rather than wiringPi pin numbers.

or just use the ptt_ctrl.sh script which I maintain.

/Basil n7nix


KB5ZUR <@KB5ZUR> writes:

Thanks John,
I got script set up and can run it but it doesn't turn on the GPIO. I'm
using left hand DIN connector and calling for pin 12.
gpio -g toggle 12 keys and unkeys radio.
./ptt.sh on doesn't key radio. Script does run just but no change on GPIO
Do I need to configure a permission of something else?
-Kb5zur David

On Fri, Apr 3, 2020 at 3:31 PM John D Hays - K7VE <@john_hays> wrote:

https://gist.github.com/jsherer/dd09895ab23bdf571e2117cdd814c198


On Fri, Apr 3, 2020 at 1:27 PM KB5ZUR <@KB5ZUR> wrote:


I saw post regarding setting up an Icom 706 with Draws. I'm trying to
use JS8Call with my ICOM706MkIIg / DRAWS set up and have TX issues. Receive
works great and see stations from all over the place.

I can toggle the TX of the radio using the toggle GPIO command but can't
figure out how to link that to the tx settings for JS8CALL.

Can anyone help.

Thanks,
-KB5ZUR David



--
John D. Hays
Kingston, WA
K7VE





Re: Icom 706MKIIG Setup #icom #ptt

Basil Gunn
 

ptt_ctrl.sh in n7nix/bin works
https://github.com/nwdigitalradio/n7nix/blob/master/bin/ptt_ctrl.sh

ie.
cd n7nix/bin
./ptt_ctrl.sh on
Turn gpio 12 on

./ptt_ctrl.sh off
Turn gpio 12 off

with the added benefit of being able to debug any problems and
explicitly sets the gpio to output.

/ptt_ctrl.sh -h
Usage: ptt_ctrl.sh [-l][-r][-on][-off][-c][-h]
-l | --left Select left connector gpio
-r | --right Select right connector gpio
-on | on Turn selected gpio ON
-off | off Turn selected gpio OFF
-t | --toggle Toggle PTT state
-c | --check Check gpio state ie. read gpio
-d | --debug Turn debug on
-h display this message

/Basil n7nix


KB5ZUR <@KB5ZUR> writes:

Thanks John,
I got script set up and can run it but it doesn't turn on the GPIO. I'm
using left hand DIN connector and calling for pin 12.
gpio -g toggle 12 keys and unkeys radio.
./ptt.sh on doesn't key radio. Script does run just but no change on GPIO
Do I need to configure a permission of something else?
-Kb5zur David

On Fri, Apr 3, 2020 at 3:31 PM John D Hays - K7VE <@john_hays> wrote:

https://gist.github.com/jsherer/dd09895ab23bdf571e2117cdd814c198


On Fri, Apr 3, 2020 at 1:27 PM KB5ZUR <@KB5ZUR> wrote:


I saw post regarding setting up an Icom 706 with Draws. I'm trying to
use JS8Call with my ICOM706MkIIg / DRAWS set up and have TX issues. Receive
works great and see stations from all over the place.

I can toggle the TX of the radio using the toggle GPIO command but can't
figure out how to link that to the tx settings for JS8CALL.

Can anyone help.

Thanks,
-KB5ZUR David



--
John D. Hays
Kingston, WA
K7VE





Re: Icom 706MKIIG Setup #icom #ptt

KB5ZUR
 

Thanks John,
I got script set up and can run it but it doesn't turn on the GPIO. I'm using left hand DIN connector and calling for pin 12. 
gpio -g toggle 12 keys and unkeys radio.
./ptt.sh on doesn't key radio. Script does run just but no change on GPIO
Do I need to configure a permission of something else?
-Kb5zur David

On Fri, Apr 3, 2020 at 3:31 PM John D Hays - K7VE <john@...> wrote:

On Fri, Apr 3, 2020 at 1:27 PM KB5ZUR <kb5zur@...> wrote:

I saw  post regarding setting up an Icom 706 with Draws. I'm trying to use JS8Call with my ICOM706MkIIg / DRAWS set up and have TX issues. Receive works great and see stations from all over the place.

I can toggle the TX of the radio using the toggle GPIO command but can't figure out how to link that to the tx settings for JS8CALL.

Can anyone help.

Thanks,
-KB5ZUR David 

 



--
John D. Hays
Kingston, WA
K7VE

 

Re: Icom 706MKIIG Setup #icom #ptt

 


On Fri, Apr 3, 2020 at 1:27 PM KB5ZUR <kb5zur@...> wrote:

I saw  post regarding setting up an Icom 706 with Draws. I'm trying to use JS8Call with my ICOM706MkIIg / DRAWS set up and have TX issues. Receive works great and see stations from all over the place.

I can toggle the TX of the radio using the toggle GPIO command but can't figure out how to link that to the tx settings for JS8CALL.

Can anyone help.

Thanks,
-KB5ZUR David 

 



--
John D. Hays
Kingston, WA
K7VE

 

Re: Icom 706MKIIG Setup #icom #ptt

KB5ZUR
 


I saw  post regarding setting up an Icom 706 with Draws. I'm trying to use JS8Call with my ICOM706MkIIg / DRAWS set up and have TX issues. Receive works great and see stations from all over the place.

I can toggle the TX of the radio using the toggle GPIO command but can't figure out how to link that to the tx settings for JS8CALL.

Can anyone help.

Thanks,
-KB5ZUR David 

 

Re: Draws manager - 'successful' configurations #drawsmanager #draws-manager

 

Added to git repository

On Thu, Apr 2, 2020 at 12:46 PM Mike B <kf5dey@...> wrote:
./usr/local/var/draws-manager/webapp/radios.json

{
        "radio":"FT-857D FM AX25",
        "audiorx":"af",
        "negresistor":"10 kOhm",
        "powertune":"PTM_P3",
        "pcmvol":"15.00db",
        "lodigvol":"0.00db",
        "adcvol":"0.0db",
        "dacswitch":"on",
        "dacplaysw":"on",
        "comments":""
    }



--
John D. Hays
Kingston, WA
K7VE

 

Re: Draws manager - 'successful' configurations #drawsmanager #draws-manager

Mike B
 

./usr/local/var/draws-manager/webapp/radios.json

{
        "radio":"FT-857D FM AX25",
        "audiorx":"af",
        "negresistor":"10 kOhm",
        "powertune":"PTM_P3",
        "pcmvol":"15.00db",
        "lodigvol":"0.00db",
        "adcvol":"0.0db",
        "dacswitch":"on",
        "dacplaysw":"on",
        "comments":""
    }