Date   
Re: Unable to get sound to FLDIGI with UDRC-II

Nick Ellson
 

Corky,

Hi!!

I had given up. It wasn't any fun bashing my head against the wall only to have a $4 USB sound dongle from Adafruit work out of the box.

But I will be happy to unpack the UDRC-II and work with you on it. Was hoping to help out others at SeaPac and Steve Aberle's workshop.

Nick

Nick Ellson - from iPhone (forgive typos)
CCIE #20018; VCIX-NV, CNSE
Network Hobbyist
"Educating Layer 8, one user at a time."

On Feb 9, 2017, at 9:55 AM, Corky Searls <af4pm@...> wrote:

I

Re: UDRC/RPi/DR-1X

VE3MIC
 

Opps! I may have misread the results. I was looking at pin#8 rather than pin#7.

de Mike

Re: UDRC/RPi/DR-1X

VE3MIC
 

Thanks John.

The GPIO settings looks good to me. I'll keep looking, and if I can't locate the problem, I'll restore the image.

73 de Mike


Re: UDRC/RPi/DR-1X

 

Mike,

I am not aware of any specific issue with the update, but a new package can always come in.

I do updates pretty often, but in most cases people are safe only doing it when there is a specific package or security update is known to be needed.

I have had several people that somehow get themselves into an unknown state and I have them do a fresh install and update, then follow the Wiki.  When I get personally involved, it is almost always a bad configuration somewhere in the setup.

One thing to check is use the gpio command with the readall switch, if GPIO.7 is not set to ALT0 then something is crossing up the gpio subsystem, this is where I go to a fresh install.  GPIO.7 is used to manage the sound chip.

-- John

On Sat, Feb 11, 2017 at 7:36 AM, VE3MIC via Groups.Io <ve3mic@...> wrote:

[Edited Message Follows]

I recently performed a 'apt-get update', and a 'apt-get upgrade' and since that time, my DR-1x is behaving as Gordon has described.

I've been through all of the settings again, and from the steps in the wiki, but no joy. I can always revert to my backup image, but have been trying to find out what exactly has broken my image that has been operating flawlessly since last August,

I'm at a loss as to what the problem is.

John, does performing an apt-get upgrade still break Compass? I had thought that this was no longer an issue.

Thanks in advance to everyone concerned.

73 de Mike




--


John D. Hays
K7VE

PO Box 1223, Edmonds, WA 98020-1223
   

Re: UDRC/RPi/DR-1X

VE3MIC
 
Edited

I recently performed a 'apt-get update', and a 'apt-get upgrade' and since that time, my DR-1x is behaving as Gordon has described.

I've been through all of the settings again, and from the steps in the wiki, but no joy. I can always revert to my backup image, but have been trying to find out what exactly has broken my image that has been operating flawlessly since last August,

I'm at a loss as to what the problem is.

John, does performing an apt-get upgrade still break Compass? I had thought that this was no longer an issue.

Thanks in advance to everyone concerned.

73 de Mike

Re: Unable to get sound to FLDIGI with UDRC-II

Corky Searls
 

Nick, I am really sorry that it has taken so long, but I have finally worked this through and think I have a working solution for you. At least I can say this works with my FT-817 which when I started experienced the same symptoms that you are seeing.

Perhaps you have already figured this out, but the problem seems to be in the way that Yaesu is handling the pins on the 6-pin connector, in particular the squelch pin (pin 6). I found that if this pin was connected there was no audio out to the UDRC. Using an oscilloscope I verified that there was signal on pin 5 (the 1200 baud output) and pin 4 (the 9600 baud output). Note that crossing the signals so that pin 5 on the radio goes to pin 4 on the UDRC also works fine with fldigi and may be required if pin 4 is muted (as implied by the manual) when not using 2-m packet.

As an aside, I recommend not using the digital psk settings (PSK31-U), but instead use USER-U as some of the Yaesu radios have issues with the PSK31 setting.

Again, I am sorry for the delay in getting you a solution and hope that this addresses the issues you are having with your Yaesu and the UDRC.

Thanks,
-Corky

On Nov 25, 2016, at 7:27 PM, udrc@... wrote:


Hey Corky,


I rebooted, re-ran the UDRC soundcard initialization script, peaked with alsamizer to see the level were where they were when I first installed (check), then rebooted again just to make sure nothing was in path or attached to the UDRC.

Then I ran FLDIGI, and insured that the port audio had UDRC in both capture and playback, which it did. There was a single pixel height blip of the poor water fall patter I was seeing (no strips though) but it goes to black after than I I have no waterfall. I have a spy glass to inspect saoldering, I will take some time to go over the card, see if it's something like that.


I wouldn't think it would be this hard, maybe for fine tuning there would be some tweaking, but this is a non starter thus far.

Nick






Re: UDRC-II/Direwolf Help

W0NV
 

John, Basil and Tim; Thank you for the replies and information.  That gives me some things to try.  My goal is to use the UDRC II as a D-STAR hot Spot.  I got the UDRC original running as a hot spot with  no problems;  I'm sure I've just got something not quite right.

Thanks again!

Niles
K4RNV


On Wednesday, February 1, 2017 11:18 PM, John D Hays - K7VE <john@...> wrote:


Hi Niles,

Let try to clear up part of this for you.  There is only one sound chip on the UDRC-II, at the lowest levels there is a driver that talks to the physical device.  ALSA provides the sound framework used by both of these programs and ALSA manages what is talking to the physical sound device through the driver.  ALSA only allows one process to map a device.

When you have a program, like dstarrepeater (ircddbgateway only talks to networks, not to the UDRC, dstarrepeater talks to ircddbgateway through a network socket) or direwolf, the program communicates to ALSA what device it wants to use.  ALSA notes that and does not allow any other program to use it.

This is why dstarrepeater will not list the soundcard for configuration while it is being used by direwolf and conversely direwolf can't access the soundcard when its being used by dstarrepeater.

That's why when you are using UDRC-II in direwolf, you have two channels to map (left and right, with one going to each physical port HD-15 and DIN-6).  dstarrepeater only uses one channel but both are consumed when CARD=udrc,DEV=0

Experimentally you can create virtual sound devices in ALSA, which can allow two or more processes/programs to access a physical device, but you can't mix programs accessing both the physical device directly and through virtual devices -- while you can have multiple programs attaching to multiple virtual devices. (We explain how to create virtual devices, but there is no support -- it is purely for experimenters to experiment and learn.)  This doesn't help you with dstarrepeater though, since it only maps physical devices, e.g. the whole UDRC.

The configuration you are attempting, with two programs trying to access the same physical sound device in parallel, will not work. (Due to dstarrepeaters' limitation of only attaching physical devices.)

On Wed, Feb 1, 2017 at 6:59 PM, K4RNV <nvaught@...> wrote:
I have been following this thread.  My experience is like Tim's. 

"Audio device for both receive and transmit: plughw:CARD=udrc,DEV=0
> (channels 0 & 1) Could not open audio device plughw:CARD=udrc,DEV=0
> for input Device or resource busy"

I started with fresh compass image and followed nwdigital instructions to the letter; running ircDDB GUI, mini din-6 connector (purchased from nwdigital) from URDCII to Yaseu radio.




pidof  direwolf  produces no result ( I just get back a prompt);  cd bin result: no such directory exists.

Direwolf appears to work fine as long as ircDDB Repeater  program is not running.  When Repeater  program is running, Direwolf says the UDRC is busy (as above) meanwhile the Repeater program has no response to or from  the radio (and in Repeater setup  the sound card choice is blank i.e. not choices available) although ircDDB gateway  is connected and working.  Reboot and reopen repeater setup and the sound card udrc is available and chosen for both rx and tx with no response from radio.  rx/tx inversion matters not.  The radio never responds to the computer and the computer never responds to RF into the Yaseu.  The very same R-Pi and compass image with UDRC original and appropriate direwolf.conf works fine

If you are tempted to start from scratch, clone
https://github.com/ nwdigitalradio/n7nix

and follow the instructions for installing core which is direwolf,
ax25 and systemd transactional files. It assumes you are using a mini
din-6 connector on UDRC side. It will put your system in a known
working configuration.


I guess I'm not able to understand this.  I cloned it to my github desk top; but I don't know what to do with it ( what are the instructions for installing core?) and I downloaded the zip file; extracted it to a folder but I don't know what to do with it either

Thanks for your help,

K4RNV
Niles
II



--


John D. Hays
K7VE

PO Box 1223, Edmonds, WA 98020-1223
   



Re: UDRC-II/Direwolf Help

Basil Gunn
 

On Wed, 01 Feb 2017 19:26:07 -0800
"Tim Fehr" <tim.w.fehr@...> wrote:

The core install instructions can be found at the link Basil provided
( https://github.com/nwdigitalradio/n7nix
( https://github.com/nwdigitalradio/n7nix ) ) under "CORE_INSTALL.md"
I tried it twice but not all of it installed for me. You may have
better luck.
Send me the console output of your core install & I'll figure out
where your ax.25 install is failing.

/Basil n7nix

Re: UDRC-II/Direwolf Help

Basil Gunn
 

On Thu, 2 Feb 2017 02:59:22 +0000 (UTC)
"K4RNV" <nvaught@...> wrote:

I have been following this thread.  My experience is like Tim's. 

"Audio device for both receive and transmit: plughw:CARD=udrc,DEV=0>
(channels 0 & 1) Could not open audio device plughw:CARD=udrc,DEV=0
for input Device or resource busy"
I started with fresh compass image and followed nwdigital
instructions to the letter; running ircDDB GUI, mini din-6 connector
(purchased from nwdigital) from URDCII to Yaseu radio.
You & Tim are installing 2 different things. You are installing some
D-Star app & Tim is installing a packet configuration

pidof  direwolf  produces no result ( I just get back a prompt);  cd
bin result: no such directory exists.
bin directory is only created during packet configuration.

Direwolf appears to work fine as long as ircDDB Repeater  program is
not running.  When Repeater  program is running, Direwolf says the
UDRC is busy (as above) meanwhile the Repeater program has no
response to or from  the radio (and in Repeater setup  the sound card
choice is blank i.e. not choices available) although ircDDB gateway
is connected and working.  Reboot and reopen repeater setup and the
sound card udrc is available and chosen for both rx and tx with no
response from radio.  rx/tx inversion matters not.  The radio never
responds to the computer and the computer never responds to RF into
the Yaseu.  The very same R-Pi and compass image with UDRC original
and appropriate direwolf.conf works fine

If you are tempted to start from scratch, clone
https://github.com/nwdigitalradio/n7nix

and follow the instructions for installing core which is direwolf,
ax25 and systemd transactional files. It assumes you are using a mini
din-6 connector on UDRC side. It will put your system in a known
working configuration.

I guess I'm not able to understand this.  I cloned it to my github
desk top; but I don't know what to do with it ( what are the
instructions for installing core?) and I downloaded the zip file;
extracted it to a folder but I don't know what to do with it either
Thanks for your help, K4RNVNiles II
For installing a packet setup ONLY.
Using a browser, go to the github repository link

https://github.com/nwdigitalradio/n7nix

scroll down to read the README.md file. Click on the other .md files
depending on what you want to install.

/Basil n7nix

Re: Illegal Instruction Executing Direwolf on Raspberry Pi B+

 

Recompiling fixed the problem.

 

Bob AF9W

 

From: udrc@nw-digital-radio.groups.io [mailto:udrc@nw-digital-radio.groups.io] On Behalf Of Bob AF9W
Sent: Wednesday, February 1, 2017 10:16 PM
To: udrc@nw-digital-radio.groups.io
Subject: [udrc] Illegal Instruction Executing Direwolf on Raspberry Pi B+

 

I installed Compass Lite on a Raspberry Pi B+.  I installed Direwolf using apt and when I execute the program I get an "Illegal Instruction" error.  The Makefile for Linux for Direwolf (https://github.com/wb2osz/direwolf/blob/master/Makefile.linux) has two lines after the section about compiling with Raspberry Pi 2 options:

# If you compile with the RPi 2 specific options above and try to run it on the RPi 

# model B (pre version 2), it will die with "illegal instruction."

Does anyone know if the version of Direwolf in the repository was compiled for a Pi 2?

I am going to try compiling Direwolf 1.3 in the morning to see if that helps but I thought I would ask in case anyone knew the answer.

 

Bob AF9W

Illegal Instruction Executing Direwolf on Raspberry Pi B+

 

I installed Compass Lite on a Raspberry Pi B+.  I installed Direwolf using apt and when I execute the program I get an "Illegal Instruction" error.  The Makefile for Linux for Direwolf (https://github.com/wb2osz/direwolf/blob/master/Makefile.linux) has two lines after the section about compiling with Raspberry Pi 2 options:

# If you compile with the RPi 2 specific options above and try to run it on the RPi 

# model B (pre version 2), it will die with "illegal instruction."

Does anyone know if the version of Direwolf in the repository was compiled for a Pi 2?

I am going to try compiling Direwolf 1.3 in the morning to see if that helps but I thought I would ask in case anyone knew the answer.


Bob AF9W

Re: UDRC-II/Direwolf Help

 

Hi Niles,

Let try to clear up part of this for you.  There is only one sound chip on the UDRC-II, at the lowest levels there is a driver that talks to the physical device.  ALSA provides the sound framework used by both of these programs and ALSA manages what is talking to the physical sound device through the driver.  ALSA only allows one process to map a device.

When you have a program, like dstarrepeater (ircddbgateway only talks to networks, not to the UDRC, dstarrepeater talks to ircddbgateway through a network socket) or direwolf, the program communicates to ALSA what device it wants to use.  ALSA notes that and does not allow any other program to use it.

This is why dstarrepeater will not list the soundcard for configuration while it is being used by direwolf and conversely direwolf can't access the soundcard when its being used by dstarrepeater.

That's why when you are using UDRC-II in direwolf, you have two channels to map (left and right, with one going to each physical port HD-15 and DIN-6).  dstarrepeater only uses one channel but both are consumed when CARD=udrc,DEV=0

Experimentally you can create virtual sound devices in ALSA, which can allow two or more processes/programs to access a physical device, but you can't mix programs accessing both the physical device directly and through virtual devices -- while you can have multiple programs attaching to multiple virtual devices. (We explain how to create virtual devices, but there is no support -- it is purely for experimenters to experiment and learn.)  This doesn't help you with dstarrepeater though, since it only maps physical devices, e.g. the whole UDRC.

The configuration you are attempting, with two programs trying to access the same physical sound device in parallel, will not work. (Due to dstarrepeaters' limitation of only attaching physical devices.)

On Wed, Feb 1, 2017 at 6:59 PM, K4RNV <nvaught@...> wrote:
I have been following this thread.  My experience is like Tim's. 

"Audio device for both receive and transmit: plughw:CARD=udrc,DEV=0
> (channels 0 & 1) Could not open audio device plughw:CARD=udrc,DEV=0
> for input Device or resource busy"

I started with fresh compass image and followed nwdigital instructions to the letter; running ircDDB GUI, mini din-6 connector (purchased from nwdigital) from URDCII to Yaseu radio.




pidof  direwolf  produces no result ( I just get back a prompt);  cd bin result: no such directory exists.

Direwolf appears to work fine as long as ircDDB Repeater  program is not running.  When Repeater  program is running, Direwolf says the UDRC is busy (as above) meanwhile the Repeater program has no response to or from  the radio (and in Repeater setup  the sound card choice is blank i.e. not choices available) although ircDDB gateway  is connected and working.  Reboot and reopen repeater setup and the sound card udrc is available and chosen for both rx and tx with no response from radio.  rx/tx inversion matters not.  The radio never responds to the computer and the computer never responds to RF into the Yaseu.  The very same R-Pi and compass image with UDRC original and appropriate direwolf.conf works fine

If you are tempted to start from scratch, clone
https://github.com/nwdigitalradio/n7nix

and follow the instructions for installing core which is direwolf,
ax25 and systemd transactional files. It assumes you are using a mini
din-6 connector on UDRC side. It will put your system in a known
working configuration.


I guess I'm not able to understand this.  I cloned it to my github desk top; but I don't know what to do with it ( what are the instructions for installing core?) and I downloaded the zip file; extracted it to a folder but I don't know what to do with it either

Thanks for your help,

K4RNV
Niles
II



--


John D. Hays
K7VE

PO Box 1223, Edmonds, WA 98020-1223
   

Re: UDRC-II/Direwolf Help

Tim Fehr <tim.w.fehr@...>
 

Niles,

The core install instructions can be found at the link Basil provided (https://github.com/nwdigitalradio/n7nix) under "CORE_INSTALL.md" I tried it twice but not all of it installed for me. You may have better luck.

Hope this helps.
--
Tim Fehr

KI7HFW

Re: UDRC-II/Direwolf Help

W0NV
 

I have been following this thread.  My experience is like Tim's. 

"Audio device for both receive and transmit: plughw:CARD=udrc,DEV=0
> (channels 0 & 1) Could not open audio device plughw:CARD=udrc,DEV=0
> for input Device or resource busy"

I started with fresh compass image and followed nwdigital instructions to the letter; running ircDDB GUI, mini din-6 connector (purchased from nwdigital) from URDCII to Yaseu radio.




pidof  direwolf  produces no result ( I just get back a prompt);  cd bin result: no such directory exists.

Direwolf appears to work fine as long as ircDDB Repeater  program is not running.  When Repeater  program is running, Direwolf says the UDRC is busy (as above) meanwhile the Repeater program has no response to or from  the radio (and in Repeater setup  the sound card choice is blank i.e. not choices available) although ircDDB gateway  is connected and working.  Reboot and reopen repeater setup and the sound card udrc is available and chosen for both rx and tx with no response from radio.  rx/tx inversion matters not.  The radio never responds to the computer and the computer never responds to RF into the Yaseu.  The very same R-Pi and compass image with UDRC original and appropriate direwolf.conf works fine

If you are tempted to start from scratch, clone
https://github.com/nwdigitalradio/n7nix

and follow the instructions for installing core which is direwolf,
ax25 and systemd transactional files. It assumes you are using a mini
din-6 connector on UDRC side. It will put your system in a known
working configuration.


I guess I'm not able to understand this.  I cloned it to my github desk top; but I don't know what to do with it ( what are the instructions for installing core?) and I downloaded the zip file; extracted it to a folder but I don't know what to do with it either

Thanks for your help,

K4RNV
Niles
II


On Sunday, January 29, 2017 6:24 PM, Basil Gunn <basil@...> wrote:


On Sun, 29 Jan 2017 13:53:28 -0800
"Tim Fehr" <tim.w.fehr@...> wrote:

> I tried starting from scratch
> using https://github.com/nwdigitalradio/n7nix
> ( https://github.com/nwdigitalradio/n7nix ) as you suggested. I went
> through the steps twice and followed them closely. Both times I was
> left without a usable direwolf.conf.

What was the symptom?
Please attach file /etc/direwolf.conf in an e-mail to me.

> I manually created a
> direwolf.conf using the template on the NWDR page but got the
> following when I ran direwolf.
>
> Reading config file direwolf.conf
> Audio device for both receive and transmit: plughw:CARD=udrc,DEV=0
> (channels 0 & 1) Could not open audio device plughw:CARD=udrc,DEV=0
> for input Device or resource busy

Sounds like you have 2 instances of direwolf running or at least 2
programs trying to use device 'udrc'.

Try:

pidof direwolf

should only see one number.

Also if you reboot, everything will start automatically with a single
instance of direwolf. Note direwolf is started by systemd and the ax.25
subsystem will be running & available to you to run xastir,
paclink-unix or whatever.

After a reboot

cd bin
./ax25-status

Copy & paste the output into an e-mail to me.

/Basil


> Pointless to continue without audio device.
>
> I'm back to using my fresh install of the compass and troubleshooting
> why I don't seem to be received any signals.
>
> As I noted in a previous post, I had no problems with
> measure_deviate.sh.
>
> --
> Tim Fehr
>
> KI7HFW





Re: UDRC-II/Direwolf Help

Basil Gunn
 

On Sun, 29 Jan 2017 13:53:28 -0800
"Tim Fehr" <tim.w.fehr@...> wrote:

I tried starting from scratch
using https://github.com/nwdigitalradio/n7nix
( https://github.com/nwdigitalradio/n7nix ) as you suggested. I went
through the steps twice and followed them closely. Both times I was
left without a usable direwolf.conf.
What was the symptom?
Please attach file /etc/direwolf.conf in an e-mail to me.

I manually created a
direwolf.conf using the template on the NWDR page but got the
following when I ran direwolf.

Reading config file direwolf.conf
Audio device for both receive and transmit: plughw:CARD=udrc,DEV=0
(channels 0 & 1) Could not open audio device plughw:CARD=udrc,DEV=0
for input Device or resource busy
Sounds like you have 2 instances of direwolf running or at least 2
programs trying to use device 'udrc'.

Try:

pidof direwolf

should only see one number.

Also if you reboot, everything will start automatically with a single
instance of direwolf. Note direwolf is started by systemd and the ax.25
subsystem will be running & available to you to run xastir,
paclink-unix or whatever.

After a reboot

cd bin
./ax25-status

Copy & paste the output into an e-mail to me.

/Basil


Pointless to continue without audio device.

I'm back to using my fresh install of the compass and troubleshooting
why I don't seem to be received any signals.

As I noted in a previous post, I had no problems with
measure_deviate.sh.

--
Tim Fehr

KI7HFW

Re: UDRC-II/Direwolf Help

Tim Fehr <tim.w.fehr@...>
 

Basil,

I tried starting from scratch using https://github.com/nwdigitalradio/n7nix as you suggested. I went through the steps twice and followed them closely. Both times I was left without a usable direwolf.conf. I manually created a direwolf.conf using the template on the NWDR page but got the following when I ran direwolf.

Reading config file direwolf.conf
Audio device for both receive and transmit: plughw:CARD=udrc,DEV=0  (channels 0 & 1)
Could not open audio device plughw:CARD=udrc,DEV=0 for input
Device or resource busy
Pointless to continue without audio device.

I'm back to using my fresh install of the compass and troubleshooting why I don't seem to be received any signals.


As I noted in a previous post, I had no problems with measure_deviate.sh.


--
Tim Fehr

KI7HFW

Re: Problem with ircNodeDashboard

 

Thanks, John.  That worked.  I’ll put that in my notes – “D-Star Hotspots for Dummies”

 

Bob AF9W

 

From: udrc@nw-digital-radio.groups.io [mailto:udrc@nw-digital-radio.groups.io] On Behalf Of John D Hays - K7VE
Sent: Wednesday, January 25, 2017 4:07 PM
To: udrc@nw-digital-radio.groups.io
Subject: Re: [udrc] Problem with ircNodeDashboard

 

Try

 

cd /var/log/opendv

 

sudo chown opendv:root *.log

sudo chmod 664 *.log

 

 

 

On Wed, Jan 25, 2017 at 2:58 PM, Bob AF9W <af9w@...> wrote:

I created a hotspot using the UDRC and Raspberry Pi including the ircNodeDashboard and it works great.  I just created another hotspot using the Compass linux and following the directions for the UDRC hotspot except that I used a DVRPTRV1 instead of the UDRC and I installed the full Compass with GUI instead of Compass Lite.  The hotspot works great except for one problem:

 

I think I followed the directions for the dashboard just like I did for my first hotspot except when I try to run the dashboard I get a permission error:

 

pi@n7crs-compass:/var/www-node/ircNodeDashboard $ sudo node webserver.js

 

fs.js:436

  return binding.open(pathModule._makeLong(path), stringToFlags(flags), mode);

                 ^

Error: EACCES, permission denied '/var/log/opendv/Links.log'

    at Object.fs.openSync (fs.js:436:18)

    at openThenF (/var/www-node/ircNodeDashboard/node_modules/touch/touch.js:80:40)

    at touch_ (/var/www-node/ircNodeDashboard/node_modules/touch/touch.js:73:10)

    at optionsRef (/var/www-node/ircNodeDashboard/node_modules/touch/touch.js:45:28)

    at touch (/var/www-node/ircNodeDashboard/node_modules/touch/touch.js:69:10)

    at Function.touch.touchSync.touch.sync (/var/www-node/ircNodeDashboard/node_modules/touch/touch.js:6:10)

    at Server.<anonymous> (/var/www-node/ircNodeDashboard/webserver.js:44:10)

    at Server.g (events.js:180:16)

    at Server.emit (events.js:92:17)

    at net.js:1055:10

 

What I discovered was the Links.log file and other files were created with root as owner when I ran the GUI version of ircDDBGateway and DStarrepeater.  The ircNodeDashboard is trying to access these files as opendv.  I closed the GUI versions of ircDDBGateway and DStarrepeater and tried running the daemon versions and dstarrepeaterd can’t access the log files because it is running as opendv and the files are still owned by root

 

pi@n7crs-compass:~ $ ls -al /var/log/opendv

total 956

drwxr-xr-x 2 opendv opendv   4096 Jan 25 21:39 .

drwxr-xr-x 8 root   root     4096 Jan 25 21:59 ..

-rw-r--r-- 1 root   root    64884 Jan 25 22:17 dstarrepeater_1.log

-rw-r--r-- 1 opendv opendv    209 Jan 25 21:39 dstarrepeaterd_1.log

-rw-r--r-- 1 root   root    11195 Jan 25 22:17 Headers.log

-rw-r--r-- 1 opendv opendv  11841 Jan 25 21:48 ircddbgatewayd.log

-rw-r--r-- 1 root   root   862191 Jan 25 22:20 ircddbgateway.log

-rw-r--r-- 1 root   root       94 Jan 25 22:17 Links.log

-rw-r--r-- 1 root   root        0 Jan 25 22:17 STARnet.log

 

Upon further research I see that the dstarrepeaterd@.service and ircddgatewayd.service specify user=opendv.  The .desktop files use “Exec=sudo /usr/bin/ircddbgateway” to start the apps which I believe in my limited knowledge of Linux starts the apps owned by root. 

 

Can someone tell me how to start the GUI apps as owned by opendv or is there something else I should do?

 

Bob AF9W

 

 

 

 



 

--

 


John D. Hays

K7VE

 

PO Box 1223, Edmonds, WA 98020-1223

   

 

Re: Problem with ircNodeDashboard

 

Try

cd /var/log/opendv

sudo chown opendv:root *.log
sudo chmod 664 *.log



On Wed, Jan 25, 2017 at 2:58 PM, Bob AF9W <af9w@...> wrote:

I created a hotspot using the UDRC and Raspberry Pi including the ircNodeDashboard and it works great.  I just created another hotspot using the Compass linux and following the directions for the UDRC hotspot except that I used a DVRPTRV1 instead of the UDRC and I installed the full Compass with GUI instead of Compass Lite.  The hotspot works great except for one problem:

 

I think I followed the directions for the dashboard just like I did for my first hotspot except when I try to run the dashboard I get a permission error:

 

pi@n7crs-compass:/var/www-node/ircNodeDashboard $ sudo node webserver.js

 

fs.js:436

  return binding.open(pathModule._makeLong(path), stringToFlags(flags), mode);

                 ^

Error: EACCES, permission denied '/var/log/opendv/Links.log'

    at Object.fs.openSync (fs.js:436:18)

    at openThenF (/var/www-node/ircNodeDashboard/node_modules/touch/touch.js:80:40)

    at touch_ (/var/www-node/ircNodeDashboard/node_modules/touch/touch.js:73:10)

    at optionsRef (/var/www-node/ircNodeDashboard/node_modules/touch/touch.js:45:28)

    at touch (/var/www-node/ircNodeDashboard/node_modules/touch/touch.js:69:10)

    at Function.touch.touchSync.touch.sync (/var/www-node/ircNodeDashboard/node_modules/touch/touch.js:6:10)

    at Server.<anonymous> (/var/www-node/ircNodeDashboard/webserver.js:44:10)

    at Server.g (events.js:180:16)

    at Server.emit (events.js:92:17)

    at net.js:1055:10

 

What I discovered was the Links.log file and other files were created with root as owner when I ran the GUI version of ircDDBGateway and DStarrepeater.  The ircNodeDashboard is trying to access these files as opendv.  I closed the GUI versions of ircDDBGateway and DStarrepeater and tried running the daemon versions and dstarrepeaterd can’t access the log files because it is running as opendv and the files are still owned by root

 

pi@n7crs-compass:~ $ ls -al /var/log/opendv

total 956

drwxr-xr-x 2 opendv opendv   4096 Jan 25 21:39 .

drwxr-xr-x 8 root   root     4096 Jan 25 21:59 ..

-rw-r--r-- 1 root   root    64884 Jan 25 22:17 dstarrepeater_1.log

-rw-r--r-- 1 opendv opendv    209 Jan 25 21:39 dstarrepeaterd_1.log

-rw-r--r-- 1 root   root    11195 Jan 25 22:17 Headers.log

-rw-r--r-- 1 opendv opendv  11841 Jan 25 21:48 ircddbgatewayd.log

-rw-r--r-- 1 root   root   862191 Jan 25 22:20 ircddbgateway.log

-rw-r--r-- 1 root   root       94 Jan 25 22:17 Links.log

-rw-r--r-- 1 root   root        0 Jan 25 22:17 STARnet.log

 

Upon further research I see that the dstarrepeaterd@.service and ircddgatewayd.service specify user=opendv.  The .desktop files use “Exec=sudo /usr/bin/ircddbgateway” to start the apps which I believe in my limited knowledge of Linux starts the apps owned by root. 

 

Can someone tell me how to start the GUI apps as owned by opendv or is there something else I should do?

 

Bob AF9W

 

 

 

 




--


John D. Hays
K7VE

PO Box 1223, Edmonds, WA 98020-1223
   

Problem with ircNodeDashboard

 

I created a hotspot using the UDRC and Raspberry Pi including the ircNodeDashboard and it works great.  I just created another hotspot using the Compass linux and following the directions for the UDRC hotspot except that I used a DVRPTRV1 instead of the UDRC and I installed the full Compass with GUI instead of Compass Lite.  The hotspot works great except for one problem:

 

I think I followed the directions for the dashboard just like I did for my first hotspot except when I try to run the dashboard I get a permission error:

 

pi@n7crs-compass:/var/www-node/ircNodeDashboard $ sudo node webserver.js

 

fs.js:436

  return binding.open(pathModule._makeLong(path), stringToFlags(flags), mode);

                 ^

Error: EACCES, permission denied '/var/log/opendv/Links.log'

    at Object.fs.openSync (fs.js:436:18)

    at openThenF (/var/www-node/ircNodeDashboard/node_modules/touch/touch.js:80:40)

    at touch_ (/var/www-node/ircNodeDashboard/node_modules/touch/touch.js:73:10)

    at optionsRef (/var/www-node/ircNodeDashboard/node_modules/touch/touch.js:45:28)

    at touch (/var/www-node/ircNodeDashboard/node_modules/touch/touch.js:69:10)

    at Function.touch.touchSync.touch.sync (/var/www-node/ircNodeDashboard/node_modules/touch/touch.js:6:10)

    at Server.<anonymous> (/var/www-node/ircNodeDashboard/webserver.js:44:10)

    at Server.g (events.js:180:16)

    at Server.emit (events.js:92:17)

    at net.js:1055:10

 

What I discovered was the Links.log file and other files were created with root as owner when I ran the GUI version of ircDDBGateway and DStarrepeater.  The ircNodeDashboard is trying to access these files as opendv.  I closed the GUI versions of ircDDBGateway and DStarrepeater and tried running the daemon versions and dstarrepeaterd can’t access the log files because it is running as opendv and the files are still owned by root

 

pi@n7crs-compass:~ $ ls -al /var/log/opendv

total 956

drwxr-xr-x 2 opendv opendv   4096 Jan 25 21:39 .

drwxr-xr-x 8 root   root     4096 Jan 25 21:59 ..

-rw-r--r-- 1 root   root    64884 Jan 25 22:17 dstarrepeater_1.log

-rw-r--r-- 1 opendv opendv    209 Jan 25 21:39 dstarrepeaterd_1.log

-rw-r--r-- 1 root   root    11195 Jan 25 22:17 Headers.log

-rw-r--r-- 1 opendv opendv  11841 Jan 25 21:48 ircddbgatewayd.log

-rw-r--r-- 1 root   root   862191 Jan 25 22:20 ircddbgateway.log

-rw-r--r-- 1 root   root       94 Jan 25 22:17 Links.log

-rw-r--r-- 1 root   root        0 Jan 25 22:17 STARnet.log

 

Upon further research I see that the dstarrepeaterd@.service and ircddgatewayd.service specify user=opendv.  The .desktop files use “Exec=sudo /usr/bin/ircddbgateway” to start the apps which I believe in my limited knowledge of Linux starts the apps owned by root. 

 

Can someone tell me how to start the GUI apps as owned by opendv or is there something else I should do?

 

Bob AF9W

 

 

 

 

Re: UDRC-II/Direwolf Help

Paul Johnson
 

For info running the following will also key the radio and send out
a tone which allows for testing the keyline and transmit audio. Use
alsamixer to adjust the tone volume.

direwolf -x


Paul VE7DHM

On Sat, 2017-01-21 at 18:15 -0800, Tim Fehr wrote:
Basil, thanks for the advice. I ran measure_deviate.sh. It ran no
problem. I tried both 1200 and 2200 Hz. I had no problem with the
board keying the transmitter. The output is below. I have to admit
though that much of the output is a bit over my head.

I looked closely at the board under a magnifying glass and saw now
obvious damage. I verified no shorts on the board's pins and all 15
pins connect to the DB15 connector pins. I also noticed that pins 5
GND is tied to pin 10 per the schematic.


pi@compass:~ $ ~/measure_deviate.sh -f 2200 -c din6 -l 30
Using tone: 2200 (wave file name: 2200hzsin.wav) for duration 30 &
connector: din6 using gpio: 23
Generating wavefile: 2200hzsin.wav with duration of 30 seconds.
wavgen exit code: 0
If using devcal from Svxlink make sure devcal line has -f2200
Using PTT GPIO 23 with tone of 2200 Hz
Playing WAVE '2200hzsin.wav' : Signed 32 bit Little Endian, Rate 48000
Hz, Stereo
Hardware PCM card 0 'udrc' device 0 subdevice 0
Its setup is:
stream : PLAYBACK
access : RW_INTERLEAVED
format : S32_LE
subformat : STD
channels : 2
rate : 48000
exact rate : 48000 (48000/1)
msbits : 32
buffer_size : 24000
period_size : 6000
period_time : 125000
tstamp_mode : NONE
period_step : 1
avail_min : 6000
period_event : 0
start_threshold : 24000
stop_threshold : 24000
silence_threshold: 0
silence_size : 0
boundary : 1572864000
appl_ptr : 0
hw_ptr : 0
##################################################+| MAX
Is carrier turned off?

pi@compass:~ $ ~/measure_deviate.sh -f 1200 -c din6 -l 5
Using tone: 1200 (wave file name: 1200hzsin.wav) for duration 5 &
connector: din6 using gpio: 23
Generating wavefile: 1200hzsin.wav with duration of 5 seconds.
wavgen exit code: 0
If using devcal from Svxlink make sure devcal line has -f1200
Using PTT GPIO 23 with tone of 1200 Hz
Playing WAVE '1200hzsin.wav' : Signed 32 bit Little Endian, Rate 48000
Hz, Stereo
Hardware PCM card 0 'udrc' device 0 subdevice 0
Its setup is:
stream : PLAYBACK
access : RW_INTERLEAVED
format : S32_LE
subformat : STD
channels : 2
rate : 48000
exact rate : 48000 (48000/1)
msbits : 32
buffer_size : 24000
period_size : 6000
period_time : 125000
tstamp_mode : NONE
period_step : 1
avail_min : 6000
period_event : 0
start_threshold : 24000
stop_threshold : 24000
silence_threshold: 0
silence_size : 0
boundary : 1572864000
appl_ptr : 0
hw_ptr : 0
##################################################+| MAX
Is carrier turned off?


--
Tim Fehr

KI7HFW