Date   

Re: Can't access Draws Manager

 

First set Commands output:

pi@radiopi:~/n7nix/config $ ./bin_refresh.sh
 Updating local bin directory for user: pi
Already up-to-date.
 
FINISHED copying desktop files
 
FINISHED copying bin files
 
FINISHED copying AX.25 files
script: /home/pi/bin/sensor_update.sh found
Incorrect sensor config file found ... replacing.
Making sensor config file based on this version of DRAWS hat
Product ver: 0x0405, Assembly rev: 4, fab rev: 5
5V not connected to DRAWS A/D
 
FINISHED updating sensor config file


Second set of commands:  manager-sysd.sh status

pi@radiopi:~/n7nix/config $ manager-sysd.sh status
Systemd draws-manager.service is enabled
● 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 Mon 2020-08-31 12:04:53 AKDT; 30min ago
     Docs: https://github.com/nwdigitalradio/draws-manager
 Main PID: 12818 (code=exited, status=1/FAILURE)
 
Aug 31 12:04:53 radiopi npm[12818]: npm WARN For further explanations, please read
Aug 31 12:04:53 radiopi npm[12818]: /usr/share/doc/nodejs/README.Debian
Aug 31 12:04:53 radiopi npm[12818]:  
Aug 31 12:04:53 radiopi npm[12818]: npm ERR!
Aug 31 12:04:53 radiopi npm[12818]: npm ERR! Additional logging details can be found in:
Aug 31 12:04:53 radiopi npm[12818]: npm ERR!     /usr/local/var/draws-manager/webapp…g.log
Aug 31 12:04:53 radiopi npm[12818]: npm ERR! not ok code 0
Aug 31 12:04:53 radiopi systemd[1]: draws-manager.service: Main process exited, code…ILURE
Aug 31 12:04:53 radiopi systemd[1]: draws-manager.service: Unit entered failed state.
Aug 31 12:04:53 radiopi systemd[1]: draws-manager.service: Failed with result 'exit-code'.
Hint: Some lines were ellipsized, use -l to show in full.
Aug 31 12:04:53 radiopi npm[12818]: npm ERR! You can get their info via:
Aug 31 12:04:53 radiopi npm[12818]: npm ERR!     npm owner ls webapp
Aug 31 12:04:53 radiopi npm[12818]: npm ERR! There is likely additional logging output above.
Aug 31 12:04:53 radiopi npm[12818]: npm ERR! System Linux 4.14.98-v7+
Aug 31 12:04:53 radiopi npm[12818]: npm ERR! command "/usr/bin/node" "/usr/bin/npm" "start"
Aug 31 12:04:53 radiopi npm[12818]: npm ERR! cwd /usr/local/var/draws-manager/webapp
Aug 31 12:04:53 radiopi npm[12818]: npm ERR! node -v v8.11.1
Aug 31 12:04:53 radiopi npm[12818]: npm ERR! npm -v 1.4.21
Aug 31 12:04:53 radiopi npm[12818]: npm ERR! code ELIFECYCLE
Aug 31 12:04:53 radiopi npm[12818]: npm WARN This failure might be due to the use of legacy binary "node"
Aug 31 12:04:53 radiopi npm[12818]: npm WARN For further explanations, please read
Aug 31 12:04:53 radiopi npm[12818]: /usr/share/doc/nodejs/README.Debian
Aug 31 12:04:53 radiopi npm[12818]:  
Aug 31 12:04:53 radiopi npm[12818]: npm ERR!
Aug 31 12:04:53 radiopi npm[12818]: npm ERR! Additional logging details can be found in:
Aug 31 12:04:53 radiopi npm[12818]: npm ERR!     /usr/local/var/draws-manager/webapp/npm-debug.log
Aug 31 12:04:53 radiopi npm[12818]: npm ERR! not ok code 0
Aug 31 12:04:53 radiopi systemd[1]: draws-manager.service: Main process exited, code=exited, status=1/FAILURE
Aug 31 12:04:53 radiopi systemd[1]: draws-manager.service: Unit entered failed state.
Aug 31 12:04:53 radiopi systemd[1]: draws-manager.service: Failed with result 'exit-code'.

Last 2 commands:

pi@radiopi:~/n7nix/config $ manager-sysd.sh start

pi@radiopi:~/n7nix/config $ manager-sysd.sh status

Systemd draws-manager.service is enabled

● 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 Mon 2020-08-31 12:04:53 AKDT; 37min ago

Condition: start condition failed at Mon 2020-08-31 12:41:50 AKDT; 38s ago

           └─ ConditionPathExists=/proc/asound/udrc was not met

     Docs: https://github.com/nwdigitalradio/draws-manager

 Main PID: 12818 (code=exited, status=1/FAILURE)

 

Aug 31 12:04:53 radiopi npm[12818]: npm WARN For further explanations, please read

Aug 31 12:04:53 radiopi npm[12818]: /usr/share/doc/nodejs/README.Debian

Aug 31 12:04:53 radiopi npm[12818]:  

Aug 31 12:04:53 radiopi npm[12818]: npm ERR!

Aug 31 12:04:53 radiopi npm[12818]: npm ERR! Additional logging details can be found in:

Aug 31 12:04:53 radiopi npm[12818]: npm ERR!     /usr/local/var/draws-manager/webapp…g.log

Aug 31 12:04:53 radiopi npm[12818]: npm ERR! not ok code 0

Aug 31 12:04:53 radiopi systemd[1]: draws-manager.service: Main process exited, code…ILURE

Aug 31 12:04:53 radiopi systemd[1]: draws-manager.service: Unit entered failed state.

Aug 31 12:04:53 radiopi systemd[1]: draws-manager.service: Failed with result 'exit-code'.

Hint: Some lines were ellipsized, use -l to show in full.

Aug 31 12:04:53 radiopi npm[12818]: npm ERR! You can get their info via:

Aug 31 12:04:53 radiopi npm[12818]: npm ERR!     npm owner ls webapp

Aug 31 12:04:53 radiopi npm[12818]: npm ERR! There is likely additional logging output above.

Aug 31 12:04:53 radiopi npm[12818]: npm ERR! System Linux 4.14.98-v7+

Aug 31 12:04:53 radiopi npm[12818]: npm ERR! command "/usr/bin/node" "/usr/bin/npm" "start"

Aug 31 12:04:53 radiopi npm[12818]: npm ERR! cwd /usr/local/var/draws-manager/webapp

Aug 31 12:04:53 radiopi npm[12818]: npm ERR! node -v v8.11.1

Aug 31 12:04:53 radiopi npm[12818]: npm ERR! npm -v 1.4.21

Aug 31 12:04:53 radiopi npm[12818]: npm ERR! code ELIFECYCLE

Aug 31 12:04:53 radiopi npm[12818]: npm WARN This failure might be due to the use of legacy binary "node"

Aug 31 12:04:53 radiopi npm[12818]: npm WARN For further explanations, please read

Aug 31 12:04:53 radiopi npm[12818]: /usr/share/doc/nodejs/README.Debian

Aug 31 12:04:53 radiopi npm[12818]:  

Aug 31 12:04:53 radiopi npm[12818]: npm ERR!

Aug 31 12:04:53 radiopi npm[12818]: npm ERR! Additional logging details can be found in:

Aug 31 12:04:53 radiopi npm[12818]: npm ERR!     /usr/local/var/draws-manager/webapp/npm-debug.log

Aug 31 12:04:53 radiopi npm[12818]: npm ERR! not ok code 0

Aug 31 12:04:53 radiopi systemd[1]: draws-manager.service: Main process exited, code=exited, status=1/FAILURE

Aug 31 12:04:53 radiopi systemd[1]: draws-manager.service: Unit entered failed state.

 

Aug 31 12:04:53 radiopi systemd[1]: draws-manager.service: Failed with result 'exit-code'.

 


Re: Can't access Draws Manager

Basil Gunn
 

Since you are running an older kernel the following might work to start
DRAWS manager otherwise my previous answer holds.

cd
cd n7nix/config
./bin_refresh.sh

manager-sysd.sh status
manager-sysd.sh start
manager-sysd.sh status

Send me the console output of above.

Previous answer:
Regarding DRAWS manager: at the bottom of this post you will find your
answer. https://nw-digital-radio.groups.io/g/udrc/message/5111
Completed the version check for the programs. All match,
This isn't true, I am interested in why flmsg didn't get updated.
I put some error checking in a new fl apps install script and wonder if
you would please run it and post the console output.

cd
cd n7nix
git pull
cd hfprogs
./hf_install.sh pi flmsg 4.0.16
./hf_verchk.sh


Todd via groups.io <ic7461=yahoo.com@groups.io> writes:

Hello Basil:
Linux radiopi 4.14.98-v7+ #1200 SMP Tue Feb 12 20:27:48 GMT 2019 armv7l GNU/Linux

2020 08 31 10:23:02 AKDT: hf_install.sh: HF program (flmsg) install script FINISHED
2020 08 31 10:23:03 AKDT: hf_verchk.sh: hf program update script FINISHED

flmsg: current version: 4.0.16, installed: 4.0.8


Re: Can't access Draws Manager

 

Hello Basil:
Linux radiopi 4.14.98-v7+ #1200 SMP Tue Feb 12 20:27:48 GMT 2019 armv7l GNU/Linux

2020 08 31 10:23:02 AKDT: hf_install.sh: HF program (flmsg) install script FINISHED
 
flamp:  current version: 2.2.05, installed: 2.2.05
        version is current
fllog:  current version: 1.2.6, installed: 1.2.6
        version is current
 
2020 08 31 10:23:03 AKDT: hf_verchk.sh: hf program update script FINISHED
 
root@radiopi:/home/pi/n7nix/hfprogs# ./hf_verchk.sh
js8call: current version: 2.2.0, installed: 2.2.0
wsjtx:   current version: 2.2.2, installed: 2.2.2
Library: libflxmlrpc IS loaded.
flxmlrpc:  current version: 0.1.4, installed: 0.1.4
fldigi:  current version: 4.1.14, installed: 4.1.14
flrig:  current version: 1.3.51, installed: 1.3.51
flmsg:  current version: 4.0.16, installed: 4.0.8
flamp:  current version: 2.2.05, installed: 2.2.05
fllog:  current version: 1.2.6, installed: 1.2.6
root@radiopi:/home/pi/n7nix/hfprogs# 
Completed the version check for the programs. All match, but still can't get DRAWS Manager to come up in the browser localhost8080. 
Todd
AL7PX


Re: Can't access Draws Manager

Basil Gunn
 

In a console do the following:

cd
cd n7nix
git pull
cd hfprogs
./hf_verchk.sh -u

# then to verify
./hf_verchk.sh

If you have problems I will need to see all the console output.

Todd via groups.io <ic7461=yahoo.com@groups.io> writes:

Hello Basil: Current versions.

pi@radiopi:~/n7nix/hfprogs $ ./hf_verchk.sh
js8call: current version: 2.2.0-ga, installed: 1.0.0-rc3
wsjtx: current version: , installed: 2.0.1
Library: libflxmlrpc IS loaded.
flxmlrpc: current version: 0.1.4, installed: 0.1.4
fldigi: current version: 4.1.14, installed: 4.1.01
flrig: current version: 1.3.51, installed: 1.3.42
flmsg: current version: 4.0.16, installed: 4.0.8
flamp: current version: 2.2.05, installed: 2.2.04

Todd
AL7PX


Re: Can't access Draws Manager

 

Hello Basil: Current versions.

pi@radiopi:~/n7nix/hfprogs $ ./hf_verchk.sh
js8call: current version: 2.2.0-ga, installed: 1.0.0-rc3
wsjtx:   current version: , installed: 2.0.1
Library: libflxmlrpc IS loaded.
flxmlrpc:  current version: 0.1.4, installed: 0.1.4
fldigi:  current version: 4.1.14, installed: 4.1.01
flrig:  current version: 1.3.51, installed: 1.3.42
flmsg:  current version: 4.0.16, installed: 4.0.8
flamp:  current version: 2.2.05, installed: 2.2.04

Todd
AL7PX


Re: Can't access Draws Manager

Basil Gunn
 

Regarding DRAWS manager: at the bottom of this post you will find your
answer. https://nw-digital-radio.groups.io/g/udrc/message/5111

DRAWS manager will not work properly on kernel versions newer than
4.19.118 ie. if you have done any upgrades the current Raspberry Pi OS
kernel is 5.4.51-v7l+ #1333

Do NOT run draws-manager web app as it needs some work to be
compatible with the new sensors driver. The NWDR17 image has the
draws-manager daemon disabled.
Tried updating FLdigi and was unsuccessful
How did you try to update FLdigi?
Show the console output of:

cd
cd n7nix/hfprogs
./hf_verchk.sh -u

# Then verify

./hf_verchk.sh
js8call: current version: 2.2.0, installed: 2.2.0
wsjtx: current version: 2.2.2, installed: 2.2.2
Library: libflxmlrpc IS loaded.
flxmlrpc: current version: 0.1.4, installed: 0.1.4
fldigi: current version: 4.1.14, installed: 4.1.14
flrig: current version: 1.3.51, installed: 1.3.51
flmsg: current version: 4.0.16, installed: 4.0.16
flamp: current version: 2.2.05, installed: 2.2.05
fllog: current version: 1.2.6, installed: 1.2.6

Todd via groups.io <ic7461=yahoo.com@groups.io> writes:

Tried updating FLdigi and was unsuccessful and realized the Draws
Manager program was not accessible anymore. Does anyone know if there
is a way to access it? Draws manager that is, old fldigi version seems
still intact. Thanks, Todd AL7PX


Can't access Draws Manager

 

Tried updating FLdigi and was unsuccessful and realized the Draws Manager program was not accessible anymore. Does anyone know if there is a way to access it? Draws manager that is, old fldigi version seems still intact.
Thanks,
Todd
AL7PX 


Re: core_install.sh failures

Basil Gunn
 

Hi Bernard,

The n7nix repository scripts work with the NWDR image and not an HAMPi
image. The NWDR image is regularly tested against UDRC & DRAWS hats &
has different versions & configuration files of some programs then HAMPi.

The n7nix repository scripts require an NWDR image.
/Basil


Bernard f6bvp <f6bvp@free.fr> writes:

Hi,
Harware is a RaspBerry Pi 3B with an DRAWS HAT and I am runing HAMPI 1.0 with stretch
Linux raspberrypi 5.4.51-v7+ #1333 SMP Mon Aug 10 16:45:19 BST 2020 armv7l GNU/Linux

My today challenge is to use n7nix scripts in order to set-up a new system starting from HAMPI 1.0 image !


core_install.sh failures

Bernard f6bvp / ai7bg
 

Hi,
Harware is a RaspBerry Pi 3B with an DRAWS HAT and I am runing HAMPI 1.0 with stretch
Linux raspberrypi 5.4.51-v7+ #1333 SMP Mon Aug 10 16:45:19 BST 2020 armv7l GNU/Linux

My today challenge is to use n7nix scripts in order to set-up a new system starting from HAMPI 1.0 image !

Here I describe how I did the first steps with the distro.

I cloned n7nix scripts ;
git clone https://github.com/nwdigitalradio/n7nix.git

I entered into config

and ran ./core_install.sh

then ./core_config

After reboot aplay -l showed that DRAWS hat driver was started.

carte 2: udrc [udrc], périphérique 0: bcm2835-i2s-tlv320aic32x4-hifi tlv320aic32x4-hifi-0 [bcm2835-i2s-tlv320aic32x4-hifi tlv320aic32x4-hifi-0]
  Sous-périphériques: 1/1
  Sous-périphérique #0: subdevice #0

An FTM-100D Transceiver was connected to left DRAWS din6 plug with a dedicated din6 cable for the trx din plug.  
After copy of direwolf.conf into /home/pi/ Direwolf  -t 0 -x could transmit calibration tone

This seems all fine, however in order to achieve this I had to perform some tricks.

First, ./core_install.sh script stopped at direwolf step with the following message :
....
Test if direwolf has been installed
direwolf already installed
Direwolf: config file NOT installed!
copying direwolf config file from package to /etc/direwolf.conf
cp: impossible d'évaluer '/usr/share/doc/direwolf/examples/direwolf.conf*': Aucun fichier ou dossier de ce type
gzip: /etc/direwolf.conf.gz: No such file or directory
core_install.sh: direwolf install failed!

Hampi distro did not install direwolf/examples !
I had to comment with an # the following lines  and run again the script.

#if [ ! -e /etc/direwolf.conf ] ; then
#   echo "$scriptname: direwolf install failed!"
#   exit 1
#
#   echo "direwolf: config file found OK"
#fi

Script succeeded but /boot/config.txt was not configured correctly as I had to remove # on two lines :
dtoverlay=

dtoverlay=draws,alsaname=udrc
 
resulting in :
-----
[all]
#dtoverlay=vc4-fkms-v3d
# BEGIN ANSIBLE MANAGED BLOCK
# Uncomment these if you have a D.R.A.W.S. / UDRC from NW Digital Radio
# Flush all overlays, ie. deprecated overlays loaded from eeprom
dtoverlay=
# Enable UDRC/DRAWS if no EEPROM
dtoverlay=draws,alsaname=udrc
# https://www.raspberrypi.org/documentation/configuration/config-txt/overclocking.md
force_turbo=1
# Enable audio (loads snd_bcm2835)
# dtparam=audio=0
# End of D.R.A.W.S. / UDRC section
# END ANSIBLE MANAGED BLOCK
gpu_mem=64
 
# Enable audio (loads snd_bcm2835)
dtparam=audio=on

----

73 de Bernard f6bvp / ai7bg


Re: Where is the CPU temperature sensor ?

Andrew P.
 

On my Pi with the DRAWS hat, sensors is reporting
+12V: +13.67 V
+5V: +5.07 V

so it would appear that the regulator is doing its job.

Andrew, KA2DDO
________________________________________
From: udrc@nw-digital-radio.groups.io <udrc@nw-digital-radio.groups.io> on behalf of Bryan Hoyer <bhhoyer@gmail.com>
Sent: Wednesday, August 26, 2020 2:04 PM
To: udrc@nw-digital-radio.groups.io
Subject: Re: [draws and udrc] Where is the CPU temperature sensor ?

DRAWS Regulator Spec is 5.0 - 5.1 VDC 3.5A max on the Pi Header (After the Ideal Diode required by the HAT Spec

On Aug 26, 2020, at 10:30 AM, Andrew P. <andrewemt@hotmail.com<mailto:andrewemt@hotmail.com>> wrote:

So will the sensors command if the kernel is up-to-date, which I just did. I am concerned about that particular Pi reporting ALARM (LCRIT) for the voltage sensor (but no useful value). The Pi with the DRAWS hat (and using the hat's 12V power input instead of a micro-USB supply) doesn't have that ALARM on its sensors report.

________________________________________
From: udrc@nw-digital-radio.groups.io<mailto:udrc@nw-digital-radio.groups.io> <udrc@nw-digital-radio.groups.io<mailto:udrc@nw-digital-radio.groups.io>> on behalf of Steve, N9VW <steve@vanwambeck.net<mailto:steve@vanwambeck.net>>
Sent: Wednesday, August 26, 2020 1:26 PM
To: udrc@nw-digital-radio.groups.io<mailto:udrc@nw-digital-radio.groups.io>
Subject: Re: [draws and udrc] Where is the CPU temperature sensor ?

Andrew,
The vcgencmd measure_temp command will provide you with the cpu temperature on a stock rasbian image.

Happy Trails,
Steve, N9VW

On 8/26/2020 9:11 AM, Andrew P. wrote:

Greetings.

I was noticing that the sensors command on the DRAWS image can report not only the A/DC values from the DRAWS hat, but also the CPU temperature. Where is that temperature coming from? A Pi-3B+ using raspbian-buster doesn't have that sensor show up in the sensors report and sensors-detect doesn't find it. How did you manage to get the CPU temperature reported?

I ask this because I have a Pi system (not using the DRAWS hat) that is repeatedly crashing at irregular time intervals, and I can't tell if it's from overheating or something else, and it would be nice to be able to get the CPU temperature to see if it is overheating.

Andrew, KA2DDO


Re: Where is the CPU temperature sensor ?

 

DRAWS Regulator Spec is 5.0 - 5.1 VDC 3.5A max on the Pi Header (After the Ideal Diode required by the HAT Spec

On Aug 26, 2020, at 10:30 AM, Andrew P. <andrewemt@...> wrote:

So will the sensors command if the kernel is up-to-date, which I just did. I am concerned about that particular Pi reporting ALARM (LCRIT) for the voltage sensor (but no useful value). The Pi with the DRAWS hat (and using the hat's 12V power input instead of a micro-USB supply) doesn't have that ALARM on its sensors report.

________________________________________
From: udrc@nw-digital-radio.groups.io <udrc@nw-digital-radio.groups.io> on behalf of Steve, N9VW <steve@...>
Sent: Wednesday, August 26, 2020 1:26 PM
To: udrc@nw-digital-radio.groups.io
Subject: Re: [draws and udrc] Where is the CPU temperature sensor ?

Andrew,
The vcgencmd measure_temp command will provide you with the cpu temperature on a stock rasbian image.

Happy Trails,
Steve, N9VW

On 8/26/2020 9:11 AM, Andrew P. wrote:

Greetings.

I was noticing that the sensors command on the DRAWS image can report not only the A/DC values from the DRAWS hat, but also the CPU temperature. Where is that temperature coming from? A Pi-3B+ using raspbian-buster doesn't have that sensor show up in the sensors report and sensors-detect doesn't find it. How did you manage to get the CPU temperature reported?

I ask this because I have a Pi system (not using the DRAWS hat) that is repeatedly crashing at irregular time intervals, and I can't tell if it's from overheating or something else, and it would be nice to be able to get the CPU temperature to see if it is overheating.

Andrew, KA2DDO








Re: Where is the CPU temperature sensor ?

Andrew P.
 

So will the sensors command if the kernel is up-to-date, which I just did. I am concerned about that particular Pi reporting ALARM (LCRIT) for the voltage sensor (but no useful value). The Pi with the DRAWS hat (and using the hat's 12V power input instead of a micro-USB supply) doesn't have that ALARM on its sensors report.

________________________________________
From: udrc@nw-digital-radio.groups.io <udrc@nw-digital-radio.groups.io> on behalf of Steve, N9VW <steve@vanwambeck.net>
Sent: Wednesday, August 26, 2020 1:26 PM
To: udrc@nw-digital-radio.groups.io
Subject: Re: [draws and udrc] Where is the CPU temperature sensor ?

Andrew,
The vcgencmd measure_temp command will provide you with the cpu temperature on a stock rasbian image.

Happy Trails,
Steve, N9VW

On 8/26/2020 9:11 AM, Andrew P. wrote:

Greetings.

I was noticing that the sensors command on the DRAWS image can report not only the A/DC values from the DRAWS hat, but also the CPU temperature. Where is that temperature coming from? A Pi-3B+ using raspbian-buster doesn't have that sensor show up in the sensors report and sensors-detect doesn't find it. How did you manage to get the CPU temperature reported?

I ask this because I have a Pi system (not using the DRAWS hat) that is repeatedly crashing at irregular time intervals, and I can't tell if it's from overheating or something else, and it would be nice to be able to get the CPU temperature to see if it is overheating.

Andrew, KA2DDO


Re: Where is the CPU temperature sensor ?

Steve, N9VW
 

Andrew,
The vcgencmd measure_temp command will provide you with the cpu temperature on a stock rasbian image.

Happy Trails,
Steve, N9VW

On 8/26/2020 9:11 AM, Andrew P. wrote:
Greetings.

I was noticing that the sensors command on the DRAWS image can report not only the A/DC values from the DRAWS hat, but also the CPU temperature. Where is that temperature coming from? A Pi-3B+ using raspbian-buster doesn't have that sensor show up in the sensors report and sensors-detect doesn't find it. How did you manage to get the CPU temperature reported?

I ask this because I have a Pi system (not using the DRAWS hat) that is repeatedly crashing at irregular time intervals, and I can't tell if it's from overheating or something else, and it would be nice to be able to get the CPU temperature to see if it is overheating.

Andrew, KA2DDO




Re: has anyone wired up the AQlinco DR-135T MkIII yet?

Charlie Hein
 

For Ed and Basil:

@ED (and all): I'm really mostly interested in understanding:

- if the squelch indication pin input on the DRWAS board can be connected safely *as is* (as the Alinco has a squelch indication pin output on its interface)

- or if there needs to be some additional circuitry added to do this safely

- or if it's even really beneficial at all to hook it up in the first place.

I've heard nothing but good things about the radio and I'm really looking forward to getting it on the air.  If I don't hear anything conclusive regarding this before it's time to concoct the interface cable, I'll simply leave the squelch unconnected, as I know for sure that the radio will work without it. 

That being said, the geek in me really wants to hook it up if it can work, but the guy in me who's funding this project wants to avoid any damage to the DRAWS board or the radio if the pins are somehow incompatible.

@BASIL:  are you using the cable for 9600 or 1200 baud?  Let me know because at the moment I'm thinking that's for the 9600 baud input to DRAWS. 

I see the 9600 bps output pin from the radio (that would go to the DISCOUT pin #4 on the DRAWS radio port if I'm reading this right) is a 10Kohm circuit - according to the Alinco user guide.  That might be why there's a resistor on that pin (it makes sense anyway), and all the other inputs and outputs from the radio are 600 ohm. 

Charlie


Re: Where is the CPU temperature sensor ?

Andrew P.
 

Ah, must be the old kernel on the other Pi. Your NWDR17 image is using kernel 5.4.51 and the other Pi is still at 4.19.97.


________________________________________
From: udrc@nw-digital-radio.groups.io <udrc@nw-digital-radio.groups.io> on behalf of Bryan Hoyer <bhhoyer@gmail.com>
Sent: Wednesday, August 26, 2020 12:35 PM
To: udrc@nw-digital-radio.groups.io
Subject: Re: [draws and udrc] Where is the CPU temperature sensor ?

Hi Andrew,

Temp comes from the cpu. The sensors command uses this with the supply monitor on DRAWS but a straight pi can display temp also.

Bryan K7UDR

pi@K7UDR:~ $ sensors
iio_hwmon-isa-0000
Adapter: ISA adapter
+12V: +13.41 V
+5V: +5.06 V
User ADC 1: +0.02 V
User ADC 2: +0.02 V

cpu_thermal-virtual-0
Adapter: Virtual device
temp1: +51.5°C

rpi_volt-isa-0000
Adapter: ISA adapter
in0: N/A

pi@K7UDR:~ $ vcgencmd measure_temp
temp=51.0'C
pi@K7UDR:~ $


On Aug 26, 2020, at 9:11 AM, Andrew P. <andrewemt@hotmail.com<mailto:andrewemt@hotmail.com>> wrote:

Greetings.

I was noticing that the sensors command on the DRAWS image can report not only the A/DC values from the DRAWS hat, but also the CPU temperature. Where is that temperature coming from? A Pi-3B+ using raspbian-buster doesn't have that sensor show up in the sensors report and sensors-detect doesn't find it. How did you manage to get the CPU temperature reported?

I ask this because I have a Pi system (not using the DRAWS hat) that is repeatedly crashing at irregular time intervals, and I can't tell if it's from overheating or something else, and it would be nice to be able to get the CPU temperature to see if it is overheating.

Andrew, KA2DDO


Re: Where is the CPU temperature sensor ?

 

Hi Andrew,

Temp comes from the cpu. The sensors command uses this with the supply monitor on DRAWS but a straight pi can display temp also.

Bryan K7UDR

pi@K7UDR:~ $ sensors
iio_hwmon-isa-0000
Adapter: ISA adapter
+12V:        +13.41 V  
 +5V:         +5.06 V  
User ADC 1:   +0.02 V  
User ADC 2:   +0.02 V  

cpu_thermal-virtual-0
Adapter: Virtual device
temp1:        +51.5°C  

rpi_volt-isa-0000
Adapter: ISA adapter
in0:              N/A  

pi@K7UDR:~ $ vcgencmd measure_temp
temp=51.0'C
pi@K7UDR:~ $ 


On Aug 26, 2020, at 9:11 AM, Andrew P. <andrewemt@...> wrote:

Greetings.

I was noticing that the sensors command on the DRAWS image can report not only the A/DC values from the DRAWS hat, but also the CPU temperature. Where is that temperature coming from? A Pi-3B+ using raspbian-buster doesn't have that sensor show up in the sensors report and sensors-detect doesn't find it. How did you manage to get the CPU temperature reported?

I ask this because I have a Pi system (not using the DRAWS hat) that is repeatedly crashing at irregular time intervals, and I can't tell if it's from overheating or something else, and it would be nice to be able to get the CPU temperature to see if it is overheating.

Andrew, KA2DDO




Re: has anyone wired up the AQlinco DR-135T MkIII yet?

Ed Bloom, KD9FRQ
 

I have two hooked up!!!

But I purchased my cable from HamMadeparts..

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


-----Original Message-----
From: Charlie Hein <chein@...>
To: udrc@nw-digital-radio.groups.io
Sent: Wed, Aug 26, 2020 9:48 am
Subject: [draws and udrc] has anyone wired up the AQlinco DR-135T MkIII yet?

I'm looking at the manual for the radio's DB-9 data port and the DRAWS port pin outs and connection  looks pretty straightforward, but I have at least one question...

The radio and the DRAWS board both have squelch indication on the ports, but:
The radio manual says "SQC squelch signal output.  Carrier in: closed.  Open collector output."
The DRAWS documentation says "Pullup to 5V"

Just want to confirm that it's safe to connect the radio's squelch indicator pin (pin 1) to the DRAWS port's SQL pin (pin 6) directly or if it's just safer to leave it off or if a circuit of some sort is needed to isolate them from each other.  I'd like to have squelch indication if it's safe to do so.

Charlie


Where is the CPU temperature sensor ?

Andrew P.
 

Greetings.

I was noticing that the sensors command on the DRAWS image can report not only the A/DC values from the DRAWS hat, but also the CPU temperature. Where is that temperature coming from? A Pi-3B+ using raspbian-buster doesn't have that sensor show up in the sensors report and sensors-detect doesn't find it. How did you manage to get the CPU temperature reported?

I ask this because I have a Pi system (not using the DRAWS hat) that is repeatedly crashing at irregular time intervals, and I can't tell if it's from overheating or something else, and it would be nice to be able to get the CPU temperature to see if it is overheating.

Andrew, KA2DDO


Re: has anyone wired up the AQlinco DR-135T MkIII yet?

Basil Gunn
 

When I search the forum I get 21 entries relating to Alinco
DR-135/235/435MkIII radios. You might find some of those posts useful.

I use the HAM Made Parts cable which works well.
ALINCO DR-135 / 235 - DB9 MALE TO 6 PIN MINI DIN PLUG - N.W. DIGITAL 1200 & 9600 BAUD WIRING
https://hammadeparts.com/shop-for-cables/ols/products/alinco-dr-135-235-db9-packet-port-db9-male-to-6-pin-mini-din

This cables uses a 10k ohm resistor so as to not load the mic audio line when
connected to a DRAWS hat.


Charlie Hein <chein@bellsouth.net> writes:

I'm looking at the manual for the radio's DB-9 data port and the DRAWS
port pin outs and connection looks pretty straightforward, but I have
at least one question...

The radio and the DRAWS board both have squelch indication on the
ports, but: The radio manual says "SQC squelch signal output. Carrier
in: closed. Open collector output." The DRAWS documentation says
"Pullup to 5V"

Just want to confirm that it's safe to connect the radio's squelch
indicator pin (pin 1) to the DRAWS port's SQL pin (pin 6) directly or
if it's just safer to leave it off or if a circuit of some sort is
needed to isolate them from each other. I'd like to have squelch
indication if it's safe to do so.

Charlie


has anyone wired up the AQlinco DR-135T MkIII yet?

Charlie Hein
 

I'm looking at the manual for the radio's DB-9 data port and the DRAWS port pin outs and connection  looks pretty straightforward, but I have at least one question...

The radio and the DRAWS board both have squelch indication on the ports, but:
The radio manual says "SQC squelch signal output.  Carrier in: closed.  Open collector output."
The DRAWS documentation says "Pullup to 5V"

Just want to confirm that it's safe to connect the radio's squelch indicator pin (pin 1) to the DRAWS port's SQL pin (pin 6) directly or if it's just safer to leave it off or if a circuit of some sort is needed to isolate them from each other.  I'd like to have squelch indication if it's safe to do so.

Charlie

601 - 620 of 5709