Date   

DRAWS Turnkey Units

 

The first units have been delivered locally. I personally went thru setup with each user and learned a lot about expectations.

We're making some changes to the image for a better user experience. We will start shipping the remainder of the back-log next week and will have all units shipped by the end of the month. If you have an order on the books please fill out the Google Sheet I sent to you last month.

Thanks for your incredible patience !

Bryan K7UDR


Re: LinBBS config issue #ax25 #bbs

mlbayx@...
 

Just wanted to give an update.  Basil you are the man!  The script you created for me worked great.  I have since left linBBS to use linBPQ.  It was for me considerably easier to configure.  I have a 2m BBS running with DRAWS driving everything on two radios.  I use an FTM-300 on my desk to do my own packet/FM/digital stuff and swapped out the TM-733 with an alinco DR-135T mkiii both of which are being managed/TNC'd by DRAWS using the script Basil created (mentioned above).  The DR-135T is the BBS radio.  I love DRAWS and the only complaint I have is when I finally get an HF radio I will have to buy another one.  Thank you to the NWDR team you guys make a great product and to Basil for all the time you have put into the DRAWS image.

73,
Michael KJ7OOB


Re: Early odopter power pigtail

Tim Huffaker
 

On Thu, May 27, 2021 at 03:42 PM, Bryan Hoyer wrote:
Bryan K7UDR
Hi Bryan,
14002 Earlwood DR
Huntsville, AL. 35803

let me know if you need anything else and thank you.

Tim 
KM4ESU


Re: Early odopter power pigtail

 

Send shipping address and we’ll send one tomorrow

73,
Bryan K7UDR
NW Digital Radio



On May 27, 2021, at 3:40 PM, Tim Huffaker <thuffaker@...> wrote:

I have lost my generation 2 power pigtail.  it looks to be the same as the original on the early adopter board.  How can I get one of these to get my board running again. 

Tim 
KM4ESU. 


Re: Early odopter power pigtail

Tim Huffaker
 

I have lost my generation 2 power pigtail.  it looks to be the same as the original on the early adopter board.  How can I get one of these to get my board running again. 

Tim 
KM4ESU. 


Re: DRAWS Board Connectors

 

Hi Randy,
Have you ever received a reply for ths question?
I'm looking for the female HDR4X2  to work on the Accessory Connector of the DRAWS board.
He Amazon link looks promising, but I'm on the verge of spending the $12 to get and try it out
if I can't find anyone that knows for sure.
I've checked Mouser, digi-key etc but nothing comes up.

Thanks  73
Don WB5EKU 
Los Angeles 


Re: Error on apt-get upgrade #upgrade

KI5EVJ - Richard
 

Basil,
No modem but the DRAWS. I didn’t see this on previous upgrades but if nothings hurt I’ll ignore unless I can edit something to make it go away.
Richard
KI5EVJ

On May 21, 2021, at 8:38 PM, Basil Gunn <basil@pacabunga.com> wrote:


This hasn't occurred before to my knowledge. Need suggestions as I am
a rookie.
Unless you have a Bluetooth Modem I would ignore it.

I did an apt-get update; apt-get upgrade on 3 different kernels and
found the same problem on each.

Linux test21903212021 5.4.79-v7l+ #1373 SMP Mon Nov 23 13:27:40 GMT 2020 armv7l GNU/Linux
Linux test119013021 5.10.25-v7l+ #3 SMP Sun Mar 28 08:41:24 PDT 2021 armv7l GNU/Linux
Linux aprx 5.10.31-v7l+ #1412 SMP Wed Apr 21 15:45:18 BST 2021 armv7l GNU/Linux

# journalctl -u hciuart.service

May 21 16:02:47 aprx systemd[1]: Starting Configure Bluetooth Modems connected by UART...
May 21 16:03:17 aprx btuart[2428]: Initialization timed out.
May 21 16:03:17 aprx btuart[2428]: bcm43xx_init
May 21 16:03:17 aprx systemd[1]: hciuart.service: Control process exited, code=exited, status=1/FAILURE
May 21 16:03:17 aprx systemd[1]: hciuart.service: Failed with result 'exit-code'.
May 21 16:03:17 aprx systemd[1]: Failed to start Configure Bluetooth Modems connected by UART.

Looking at the /lib/systemd/system/hciuart.service file:

ConditionFileNotEmpty=/proc/device-tree/soc/gpio@7e200000/bt_pins/brcm,pins

It appears that it fails because brcm,pins file is not setup properly,
ie. it contains a dash and a null.

/proc/device-tree/soc/gpio@7e200000/bt_pins/brcm,pins

Are you using any Bluetooth Modems?

Doing some final configure steps and I got the following:

Unpacking pi-bluetooth (0.1.17) over (0.1.16) ...

-- A start job for unit hciuart.service has finished with a failure.

--
-- The job identifier is 2188 and the job result is failed.
May 21 15:40:53 raspberrypi systemd[1]: Dependency failed for Raspberry Pi bluetooth helpe
-- Subject: A start job for unit bthelper@hci0.service has failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
This hasn't occurred before to my knowledge. Need suggestions as I am a rookie.
Richard Ki5EVJ




Re: Error on apt-get upgrade #upgrade

Basil Gunn
 

This hasn't occurred before to my knowledge. Need suggestions as I am
a rookie.
Unless you have a Bluetooth Modem I would ignore it.

I did an apt-get update; apt-get upgrade on 3 different kernels and
found the same problem on each.

Linux test21903212021 5.4.79-v7l+ #1373 SMP Mon Nov 23 13:27:40 GMT 2020 armv7l GNU/Linux
Linux test119013021 5.10.25-v7l+ #3 SMP Sun Mar 28 08:41:24 PDT 2021 armv7l GNU/Linux
Linux aprx 5.10.31-v7l+ #1412 SMP Wed Apr 21 15:45:18 BST 2021 armv7l GNU/Linux

# journalctl -u hciuart.service

May 21 16:02:47 aprx systemd[1]: Starting Configure Bluetooth Modems connected by UART...
May 21 16:03:17 aprx btuart[2428]: Initialization timed out.
May 21 16:03:17 aprx btuart[2428]: bcm43xx_init
May 21 16:03:17 aprx systemd[1]: hciuart.service: Control process exited, code=exited, status=1/FAILURE
May 21 16:03:17 aprx systemd[1]: hciuart.service: Failed with result 'exit-code'.
May 21 16:03:17 aprx systemd[1]: Failed to start Configure Bluetooth Modems connected by UART.

Looking at the /lib/systemd/system/hciuart.service file:

ConditionFileNotEmpty=/proc/device-tree/soc/gpio@7e200000/bt_pins/brcm,pins

It appears that it fails because brcm,pins file is not setup properly,
ie. it contains a dash and a null.

/proc/device-tree/soc/gpio@7e200000/bt_pins/brcm,pins

Are you using any Bluetooth Modems?

Doing some final configure steps and I got the following:

Unpacking pi-bluetooth (0.1.17) over (0.1.16) ...

-- A start job for unit hciuart.service has finished with a failure.

--
-- The job identifier is 2188 and the job result is failed.
May 21 15:40:53 raspberrypi systemd[1]: Dependency failed for Raspberry Pi bluetooth helpe
-- Subject: A start job for unit bthelper@hci0.service has failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
This hasn't occurred before to my knowledge. Need suggestions as I am a rookie.
Richard Ki5EVJ


Error on apt-get upgrade #upgrade

KI5EVJ - Richard
 

Doing some final configure steps and I got the following:

Unpacking pi-bluetooth (0.1.17) over (0.1.16) ...
Preparing to unpack .../rpi-eeprom_12.4-1_armhf.deb ...
Unpacking rpi-eeprom (12.4-1) over (12.3-1) ...
Setting up pi-bluetooth (0.1.17) ...
Job for hciuart.service failed because the control process exited with error code.
See "systemctl status hciuart.service" and "journalctl -xe" for details.
Job for hciuart.service failed because the control process exited with error code.
See "systemctl status hciuart.service" and "journalctl -xe" for details.
Setting up rpi-eeprom (12.4-1) ...
Processing triggers for man-db (2.8.5-2) ...
pi@raspberrypi:~ $ journalctl -xe
-- Support: https://www.debian.org/support
-- 
-- The unit hciuart.service has entered the 'failed' state with result 'exit-code'.
May 21 15:40:53 raspberrypi systemd[1]: Failed to start Configure Bluetooth Modems connect
-- Subject: A start job for unit hciuart.service has failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- A start job for unit hciuart.service has finished with a failure.
-- 
-- The job identifier is 2188 and the job result is failed.
May 21 15:40:53 raspberrypi systemd[1]: Dependency failed for Raspberry Pi bluetooth helpe
-- Subject: A start job for unit bthelper@... has failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support

This hasn't occurred before to my knowledge. Need suggestions as I am a rookie.

Richard
Ki%EVJ
 


Re: #pat #pat

erwin.grabler@...
 
Edited

Hello Basil,

thanks for the update. According to the PAT. I did the script and settings
# change grid square and distance in ardoplist.sh
cd
cd n7nix/ardop
nano ardoplist.sh
 
max_distance=150        # default max distance of ARDOP RMS Gateways
include_history=48     # default number of history hours
grid_square="jn88de"   # default grid square location or origin

called:
./ardoplist.sh -d -D 150 -g JN88de -f

looks like the settings are not recognized and result is still (see the difference in the distance number between settings and call of the script):
pi@draws:~/n7nix/ardop $ ./ardoplist.sh -d -D 150 -g JN88de -f
Check packages: jq curl
Determine how old current file is, stale criteria: 50 hours
/home/pi/tmp/ardop/ardopprox.json file is: 1 hours 5 minute(s), 13 seconds old
Using distance of 150 miles & grid square JN88DE
 
Using URL: https://api.winlink.org/gateway/proximity?&Key=43137F63FDBA4F3FBEEBA007EB1ED348&OperatingMode=ardop&Gridsquare=CN88nl&MaxDistance=150&format=json
Generated new /home/pi/tmp/ardop/ardopprox.json file
 
Have good request json
 
Function parse_proximity with input file /home/pi/tmp/ardop/ardopprox.json
                    Center          Dial
 Callsign         Frequency       Frequency  Distance    Baud
 VA7DEP       7088500   7087000 46 600
 VA7PF       3598000   3596500 56 600
 
When I want to connect to a RMS gateway I got the message:
Missing mycall

PAT config file: .wl2k/config.json
changed:
  "mycall": "oe1ekg",
  "secure_login_password": "PASSWORD",
  "auxiliary_addresses": [],
  "locator": "JN88de",
 
unclear where I have to put the entry to hamlib_rigs:
 "KX3": {"address": "localhost:4532", "network": "tcp"}
there is only this part:
 "listen": [],
  "hamlib_rigs": {KX3},
  "ax25": {
    "port": "wl2k",
    "beacon": {
      "every": 3600,
      "message": "Winlink P2P",
      "destination": "IDENT"
 
73 de Erwin
OE1EKG


Re: #pat #pat

Basil Gunn
 

Ardop is running but can not find the PAT
$ pat rmslist -s -m ardop J

results in:
bash: pat: command not found
I updated the current version number in the install script for pat to
0.10. Please do the following:

# Update the n7nix repository

cd
cd n7nix
git pull

cd email/pat
./pat_install.sh

which pat

/Basil n7nix


Re: #pat #pat

erwin.grabler@...
 
Edited

Hello,

found the fault - I chose the wrong port. correct is the UDRC: 

cd ~/bin

./piardopc 8515 plughw:2,0 plughw:2,0 -p GPIO=12

Ardop is running but can not find the PAT
$ pat rmslist -s -m ardop J

results in:

bash: pat: command not found


73 de Erwin
OE1EKG


#pat #pat

erwin.grabler@...
 

Hello,

I went further in my installation - next step PAT for Winlink. I went through the installation README and all went smooth till I started ARDOP. I got the error at the end:


Opening Playback Device plughw:1,0 Rate 12000

Opening Capture Device plughw:1,0 Rate 12000

cannot open capture audio device plughw:1,0 (No such file or directory)

ARDOPC listening on port 8515


Waterfall GUI was possible to start but with of course with no capture. I can not find any failure - does somebody have ideas to this or experienced similar problems?

See my complete walkthrough below. There exists also a new PAT version but I was not able to update this.

73 de Erwin
OE1EKG

# DRAWS PAT config file lives here: .wl2k/config.json

# NOTE preceeding dot in directory name

# Edit the following configuration variables in the json config file

# mycall

# secure_login_password

# locator

# hamlib_rigs

# ardop, "rig":

 

cd

cd n7nix

cd email

cd pat

nano pat_install.sh

#change in pat_install.sh - but no effects

# from patver=„0.9.0“

# to patver="0.10.0"

 

nano config.json

#change in config.json

  "mycall": "oe1ekg",

  "secure_login_password": „PASSWORD",

  "locator": "JN88de",

  "hamlib_rigs": {

  "KX3": {"address": "localhost:4532", "network": "tcp"}

    "rig": "KX3"

 

# starting rIgctrl - not necessary cause of new rigctrl script from Basil

# rigctld -m2045 -r /dev/ttyUSB0 -s 38400

 

#console ARDOP

cd ~/bin

./piardopc 8515 plughw:1,0 plughw:1,0 -p GPIO=12

 

—————————————————————————————-

pi@draws:~/bin $ ./piardopc 8515 plughw:1,0 plughw:1,0 -p GPIO=12

ARDOPC Version 1.0.4.1j-BPQ

GPIO interface for PTT available

Using GPIO pin 12 for PTT

ARDOPC listening on port 8515

Capture Devices

 

Card 0, ID `b1', name `bcm2835 HDMI 1'

 

Card 1, ID `Headphones', name `bcm2835 Headphones'

 

Card 2, ID `udrc', name `udrc'

  Device hw:2,0 ID `bcm2835-i2s-tlv320aic32x4-hifi tlv320aic32x4-hifi-0', name `bcm2835-i2s-tlv320aic32x4-hifi tlv320aic32x4-hifi-0', 1 subdevices (1 available)

    2 channels,  sampling rate 8000..192000 Hz

 

Playback Devices

 

Card 0, ID `b1', name `bcm2835 HDMI 1'

  Device hw:0,0 ID `bcm2835 HDMI 1', name `bcm2835 HDMI 1', 4 subdevices (4 available)

    1..8 channels, sampling rate 8000..192000 Hz

 

Card 1, ID `Headphones', name `bcm2835 Headphones'

  Device hw:1,0 ID `bcm2835 Headphones', name `bcm2835 Headphones', 4 subdevices (4 available)

    1..8 channels, sampling rate 8000..192000 Hz

 

Card 2, ID `udrc', name `udrc'

  Device hw:2,0 ID `bcm2835-i2s-tlv320aic32x4-hifi tlv320aic32x4-hifi-0', name `bcm2835-i2s-tlv320aic32x4-hifi tlv320aic32x4-hifi-0', 1 subdevices (1 available)

    2 channels,  sampling rate 8000..192000 Hz

 

Opening Playback Device plughw:1,0 Rate 12000

Opening Capture Device plughw:1,0 Rate 12000

cannot open capture audio device plughw:1,0 (No such file or directory)

ARDOPC listening on port 8515


Re: #audio #install #config #wsjtx #config #wsjtx #audio #install

erwin.grabler@...
 

Hello Basil,

that's great ... I did this (below my steps and results). It is essential to stop AX25 before. Now the switch between Fldigi and WSJTX is smooth. Great script and very helpful.

My next steps are getting PAT running ... there I have to try out something cause it makes problems. DIREWOLF the same. But I come back when I can't find a solution.

73 de Erwin
OE1EKG

## Integrating script first time before start WSJTX and JS8Call

cd

cd n7nix/config

./bin_refresh.sh

 

# change baudrate for KX3 to 38400

nano wsj_ctrl.sh 

 

========= Stop any rigctld-wstx processes and force a systemd file update

./wsj_ctrl.sh -a kx3 -f stop

 

pi@draws:~/n7nix/hfprogs $ ./wsj_ctrl.sh -a kx3 -f stop

Setting radio name to: radio_kx3, rig name: KX3

Force update mode on

Kill rigctld-wsjtx process

 

 == Status for configured rig: KX3

  == audio device udrc check: closed

 == rigctld-wsjtx systemctl unit file check

Service: rigctld-wsjtx, status: 3

Creating systemd service files.

 == unit file update

DEBUG: creating rigctld-wsjtx unit file for radio: KX3

 systemctl daemon-reload

 == rigctld-wsjtx process check

proc rigctld-wsjtx: 1, NOT running

 

========= Start rigctld-wstx processes

./wsj_ctrl.sh -a kx3 start

 

pi@draws:~/n7nix/hfprogs $ ./wsj_ctrl.sh -a kx3 start

Setting radio name to: radio_kx3, rig name: KX3

 == rigctld-wsjtx systemctl unit file check

Service: rigctld-wsjtx, status: 3

Systemd service files found

ENABLING rigctld-wsjtx

Created symlink /etc/systemd/system/multi-user.target.wants/rigctld-wsjtx.service -> /etc/systemd/system/rigctld-wsjtx.service.

Starting service: rigctld-wsjtx

Service: rigctld-wsjtx, status: 0

 

========= check rigctld-wstx status

./wsj_ctrl.sh -a kx3 status

 

pi@draws:~/n7nix/hfprogs $ ./wsj_ctrl.sh -a kx3 status

Setting radio name to: radio_kx3, rig name: KX3

 

 == Status for configured rig: KX3

 == rigctld-wsjtx systemctl unit file check

Service: rigctld-wsjtx, status: 0

Systemd service files found

 == rigctld-wsjtx process check

proc rigctld-wsjtx: 0, pid: 9026, args:  -m 2045 -r /dev/ttyUSB0 -s 38400 -P GPIO=12

  == audio device udrc check: closed

 

========= check rigctld-wstx status AFTER reboot

cd

cd n7nix

cd hfprogs

./wsj_ctrl.sh -a kx3 status

 

pi@draws:~/n7nix/hfprogs $ ./wsj_ctrl.sh -a kx3 status

Stopping service: direwolf

Service: direwolf already disabled.

Service: direwolf now stopped.

Setting radio name to: radio_kx3, rig name: KX3

 

 == Status for configured rig: KX3

 == rigctld-wsjtx systemctl unit file check

Service: rigctld-wsjtx, status: 0

Systemd service files found

 == rigctld-wsjtx process check

proc rigctld-wsjtx: 0, pid: 449, args:  -m 2045 -r /dev/ttyUSB0 -s 38400 -P GPIO=12

  == audio device udrc check: closed

 

# Starting WSJTX results in an error - couldn’t find the sound device so I did a stop of AX25 which was already running:

 

cd

cd bin

# Become root

sudo su

./ax25-stop

 


Re: #audio #install #config #wsjtx #config #wsjtx #audio #install

Basil Gunn
 

Erwin:

I have a kx2 and following is what I ran with an unmodified script.
First run stop then start & status. Reboot & check status.

Verify that your baud rate matches what is in your radio.
Check the order of command executed below and look at what is returned.
The console output is verbose for debugging.

If you still have a problem see DEBUG section in:
https://github.com/nwdigitalradio/n7nix/tree/master/hfprogs#debug

Below is console output you sent and is normal until a service file is
created.

Check rigctld-wsjtx unit file, not configured properly
*** rigctld-wsjtx NOT CONFIGURED.

== Status for configured rig:
== rigctld-wsjtx systemctl unit file check
Service: rigctld-wsjtx, status: 3
Creating systemd service files.
========= Stop any rigctld-wstx processes and force a systemd file update

./wsj_ctrl.sh -a kx2 -f stop
Setting radio name to: radio_kx2, rig name: KX2
Force update mode on
Kill rigctld-wsjtx process
proc rigctld-wsjtx: 0, pid: 3399, args: -m 2044 -r /dev/ttyUSB0 -s 19200 -P GPIO=12
DISABLING rigctld-wsjtx
Removed /etc/systemd/system/multi-user.target.wants/rigctld-wsjtx.service.
Service: rigctld-wsjtx now stopped.

== Status for configured rig: KX2
== audio device udrc check: closed
== rigctld-wsjtx systemctl unit file check
Service: rigctld-wsjtx, status: 3
Creating systemd service files.
== unit file update
DEBUG: creating rigctld-wsjtx unit file for radio: KX2
systemctl daemon-reload
== rigctld-wsjtx process check
proc rigctld-wsjtx: 1, NOT running


========= Start rigctld-wstx processes

./wsj_ctrl.sh -a kx2 start
Setting radio name to: radio_kx2, rig name: KX2
== rigctld-wsjtx systemctl unit file check
Service: rigctld-wsjtx, status: 3
Systemd service files found
ENABLING rigctld-wsjtx
Created symlink /etc/systemd/system/multi-user.target.wants/rigctld-wsjtx.service → /etc/systemd/system/rigctld-wsjtx.service.
Starting service: rigctld-wsjtx
Service: rigctld-wsjtx, status: 0

========= check rigctld-wstx status

./wsj_ctrl.sh -a kx2 status
Setting radio name to: radio_kx2, rig name: KX2

== Status for configured rig: KX2
== rigctld-wsjtx systemctl unit file check
Service: rigctld-wsjtx, status: 0
Systemd service files found
== rigctld-wsjtx process check
proc rigctld-wsjtx: 0, pid: 3580, args: -m 2044 -r /dev/ttyUSB0 -s 19200 -P GPIO=12
== audio device udrc check: closed

========= check rigctld-wstx status AFTER reboot

./wsj_ctrl.sh -a kx2 status
Setting radio name to: radio_kx2, rig name: KX2

== Status for configured rig: KX2
== rigctld-wsjtx systemctl unit file check
Service: rigctld-wsjtx, status: 0
Systemd service files found
== rigctld-wsjtx process check
proc rigctld-wsjtx: 0, pid: 526, args: -m 2044 -r /dev/ttyUSB0 -s 19200 -P GPIO=12
== audio device udrc check: closed

erwin.grabler@artcom.cc writes:

Hello Basil,

thank you very much for your support ... made the update - but problem is after changing the script to only use the KX3 I commented the other radios so only the KX3 line is active.

declare -A radio_kx3=( [rigname]="KX3" [rignum]=2045 [audioname]=udrc [samplerate]=48000 [baudrate]=38400 [pttctrl]="GPIO=12" [catctrl]="" [rigctrl]="" [alsa_lodriver]="0.0" [alsa_pcm]="0.0" )

Also changed:
# default radio name
radioname="radio_kx3"

But result was not a success seems that the rigctld setting is not correct - in the wsj_ctrl.sh it is empty as you can see. Is that the problem? If yes - what are the basis of the settings therefore? Sorry for the stupid questions.

pi@draws:~/n7nix/hfprogs $ ./wsj_ctrl.sh -a kx3 -f status
Setting radio name to: radio_kx3, rig name: KX3
Force update mode on
Check rigctld-wsjtx unit file, not configured properly
*** rigctld-wsjtx NOT CONFIGURED.

== Status for configured rig:
== rigctld-wsjtx systemctl unit file check
Service: rigctld-wsjtx, status: 3
Creating systemd service files.
== unit file update
DEBUG: creating rigctld-wsjtx unit file for radio: KX3
systemctl daemon-reload
== rigctld-wsjtx process check
proc rigctld-wsjtx: 1, NOT running
== audio device udrc check: closed

In Flrig the transceiver control is: /dev/serial/by-id/usb-FTDI_FT232R_USB_UART_AH034AU9-if00-port0 but I have no success to put this in the declare part for the radio.

73 de Erwin
OE1EKG



Re: #audio #install #config #wsjtx #config #wsjtx #audio #install

erwin.grabler@...
 

Hello Basil,

thank you very much for your support ... made the update - but problem is after changing the script to only use the KX3 I commented the other radios so only the KX3 line is active.

declare -A radio_kx3=( [rigname]="KX3" [rignum]=2045 [audioname]=udrc [samplerate]=48000 [baudrate]=38400 [pttctrl]="GPIO=12" [catctrl]="" [rigctrl]="" [alsa_lodriver]="0.0" [alsa_pcm]="0.0" )

Also changed:
# default radio name
radioname="radio_kx3"

But result was not a success seems that the rigctld setting is not correct - in the wsj_ctrl.sh it is empty as you can see. Is that the problem? If yes - what are the basis of the settings therefore? Sorry for the stupid questions.

 
pi@draws:~/n7nix/hfprogs $ ./wsj_ctrl.sh -a kx3 -f status
Setting radio name to: radio_kx3, rig name: KX3
Force update mode on
Check rigctld-wsjtx unit file, not configured properly
 *** rigctld-wsjtx NOT CONFIGURED.
 
 == Status for configured rig: 
 == rigctld-wsjtx systemctl unit file check
Service: rigctld-wsjtx, status: 3
Creating systemd service files.
 == unit file update
DEBUG: creating rigctld-wsjtx unit file for radio: KX3
 systemctl daemon-reload
 == rigctld-wsjtx process check
proc rigctld-wsjtx: 1, NOT running
  == audio device udrc check: closed

In Flrig the transceiver control is: /dev/serial/by-id/usb-FTDI_FT232R_USB_UART_AH034AU9-if00-port0 but I have no success to put this in the declare part for the radio.

73 de Erwin
OE1EKG


Re: Hardware question about power

Basil Gunn
 

The suggestion is to back feed power to the PI via the 12v pigtail to
the hat due to some of the "less than optimal" wall warts that
sometimes are used.
Yes, the assumption is since you are a HAM all your gear probably runs
on 12V.

That said, I'm using a Canakit Raspberry PI 4 with the supplied wall
wart with my DRAWS hat/PI and I've seen no power issues so far. Your
mileage may vary.
I concur. I have had NO problems with any of the wall warts purchased
from Canakit (https://www.canakit.com/). Having said that most of my
wall warts are in a box and I use the same power supply as my radio to
power my Pi.

When you use a less than ideal power supply (volts < 5.1) for your RPi
you will see a variety of symptoms that may be difficult to debug.

I'm also using a "less than optimal" radio and home brew cable with my
hat too, so...

Best regards,
Bruce KM6KEF


Re: Hardware question about power

Robert Ferrell
 

Hi Basil,

I'm sort of old and sort of new at this too.

The suggestion is to back feed power to the PI via the 12v pigtail to the hat due to some of the "less than optimal" wall warts that sometimes are used.

That said, I'm using a Cannakit Raspberry PI 4 with the supplied wall wart with my DRAWS hat/PI and I've seen no power issues so far.  Your mileage may vary.

I'm also using a "less than optimal" radio and home brew cable with my hat too, so...

Best regards,
Bruce
KM6KEF

On 5/11/21 9:09 PM, Richard Gilbert via groups.io wrote:
Basil,

I'm newbie #2. So I can power the DRAWS/Pi with the power cable that came with the Pi? The cord that came with the DRAWS, what do people use for connectors and power sources so the power goes to the HAT?

Thanks,
Richard
KI5EVJ


Re: Hardware question about power

KI5EVJ - Richard
 

Basil,

Thanks for the info. I have a Pi 4 from Canakit. The wall wart is 3.5A output.

I will check out your other links. 

Many thanks,
Richard
ALI5EVJ


Re: Hardware question about power

Basil Gunn
 

Richard,

The thing to remember is you can either use the 5.1V wall wart that came
with the Pi OR 12V connector on the DRAWS board. Use either OR but not
both at the same time. I find it convenient to use the same power supply
that powers my radio.

So I can power the DRAWS/Pi with the power cable that came with the
Pi?
Depends. What does the power cable look like and what kind of RPi do you
have? If you bought some sort of Pi package that comes with a wall wart
look at the wall wart to see what current it is rated for ie. RPi 2,3
usually come with a 2.5A wart and RPi 4 have a 3.5A wart.

You can NOT power the Pi 400 with a DRAWS board.

The cord that came with the DRAWS, what do people use for connectors
and power sources so the power goes to the HAT?
You will need a 12V power supply to power your radio. I use an Alinco
DM-330MV that I am happy with.

I use Anderson Power Poles from the power supply plugged into some sort
of Power Pole distribution block that can feed my radio and RPi's.

Using the link below scroll down you can see a picture of a rig runner in my truck
* [[https://github.com/n7nix/nixtracker | Truck set up]]

Some links that may be helpful.

* [[https://www.dxengineering.com/parts/alo-dm-330mvt | Alinco DM-330MV 32A power supply]]

* [[http://www.westmountainradio.com/rigrunner.php | West Mountain Radio Rig Runner]]
* [[http://www.westmountainradio.com/product_info.php?products_id=rr_4006u | Rig Runner 4006U]]
* [[http://www.westmountainradio.com/product_info.php?products_id=rr_4005_c | Rig Runner 4005]]
* [[https://mfjenterprises.com/products/mfj-1126 | MFJ 1126]] - 8 Anderson Power Pole outlets
* [[https://www.amazon.com/dp/B07V5CQ71S?psc=1&ref=ppx_yo2_dt_b_product_details | Deimcdy Car Fuse Kit 140pcs Car Fuses Assortment Kit]]

* [[https://www.amazon.com/gp/product/B07GHB6X64/ref=ppx_yo_dt_b_search_asin_title?ie=UTF8&psc=1 | pre made 5.5mm to Power Pole connector cable]]

Hope that helps.
/Basil N7NIX

61 - 80 of 5764