Date   

Re: direwolf configuration file

Basil Gunn
 

Also enable both channels in Direwolf with config, ADEVICE like
this:

ADEVICE plughw:CARD=udrc,DEV=0 plughw:CARD=udrc,DEV=0

looks like you only enabled one channel.

/Basil

Hey John,

Which UDRC do you have, original or II?
- look at the silk screen on the board or
- run udrcver.sh from here:
https://github.com/nwdigitalradio/n7nix/blob/master/systemd/bin/udrcver.sh

Which UDRC port are you using mDin6 or HD15?

Assuming you have a UDRC II
If you are using mDin6 then you will need to set up Direwolf channel 1
(Direwolf uses chan 0 & 1) and PTT will be active on GPIO 23.

If you are using the HD15 interface you will need to set up Direwolf
channel 0 and PTT will be active on GPIO 12.

From your config it looks like you have the Direwolf channels switched
around for mDin6 & HD15 interfaces.

/Basil n7nix


On Thu, 15 Feb 2018 09:14:56 -0800
"John Spoonhower" <jpspoonhower@...> wrote:

I need some help with configuring direwolf. Let me start by saying
that I have direwolf running well in receive mode on a raspberry pi
3 with udrc-II. The problem lies with the lack of audio on
transmit. I am asking the setup to broadcast my setup with PBEACON
on the radio. With some setup configurations I get the transmitter
to key (PTT works!) but there is no audio (tones are not evident on
a separate second radio). I have setup FLDIGI using the online
installation notes and if I click "tune" in FLDIGI , the
transmitter keys and I hear I nice tone. I can run
measure_deviate.sh and also get the transmitter to key and generate
a tone. Measure_deviate.sh is setup in the "stock" manner with
gpio  set to gpio 12. FLDIGI setup is also "stock" with GPIO
hardware control : BCM 23, GPIO 04, pin 16 selection. 

The direwolf.conf file looks like:
ADEVICE plughw:CARD=udrc,DEV=0
ARATE 48000
ACHANNELS 2
#DIN-6
CHANNEL 0
MYCALL NX2I-10
MODEM 1200i
PTT GPIO 23
#HD-15
# note channels set the same
CHANNEL 1
MYCALL NX2I-10
MODEM 1200
PTT GPIO 23
AGWPORT 8000
KISSPORT 8001
PBEACON delay=1 sendto=0 every=10 overlay=R symbol="igate"
lat=28^52.69N long=82^$ #PBEACON delay=1 sendto=1 every=10 overlay=S
symbol="digi" lat=17^51.00N long=102$ #DIGIPEAT 0 0
^WIDE[3-7]-[1-7]$|^TEST$ ^WIDE[12]-[12]$ TRACE #DIGIPEAT 1 1
^WIDE[3-7]-[1-7]$|^TEST$ ^WIDE[12]-[12]$ TRACE #DIGIPEAT 0 1
^WIDE[3-7]-[1-7]$|^TEST$ ^WIDE[12]-[12]$ TRACE #DIGIPEAT 1 0
^WIDE[3-7]-[1-7]$|^TEST$ ^WIDE[12]-[12]$ TRACE IGSERVER
noam.aprs2.net IGLOGIN NX2I 4083  #YOUR INTERNET LOGIN AND PASSCODE
FOR APRS REPORTING # Degrees Decimal minutes format for lat, long
PBEACON sendto=IG delay=0:30 every=30:00 symbol="igate" overlay=R
lat=28^52.69386$ LOGDIR /home/pi/aprslogs
IGTXLIMIT 6 10
GPSD localhost
#IBEACON DELAY=30 EVERY=30 VIA=WIDE1-1

If I have PTT GPIO 23 set (like above) I see the transmitter key but
there is no audio. If I set the GPIO in this file to 12, the
transmitter does not key. Obviously I am doing something wrong, but
none of this makes any sense to me. 73, john, NX2I


Re: direwolf configuration file

Bernard f6bvp / ai7bg
 

Hi,
The main question is which plug are you using : din6 or hd15 ? And what kind of cable. I guess you use din6 for you have selected GPIO 23 for channel 1. If using din6 with a standard din6 cable you may need to use -n 1 parameter on Direwolf command line to get audio output. Careful you may need to change GPIO in case ptt does not work.
I suppose you have set correct audio level of PCM in alsamixer ?
LOR level is also important. I prefere to set it to 0 (null) to get a more clean audio output.
Did you notice spurious letter i after 1200 on your first MODEM 1200 line ?

73 de Bernard f6bvp

Le 15 févr. 2018 à 18:14, John Spoonhower <jpspoonhower@...> a écrit :

CHANNEL 0
MYCALL NX2I-10
MODEM 1200i
PTT GPIO 23


Re: direwolf configuration file

Basil Gunn
 

Hey John,

Which UDRC do you have, original or II?
- look at the silk screen on the board or
- run udrcver.sh from here:
https://github.com/nwdigitalradio/n7nix/blob/master/systemd/bin/udrcver.sh

Which UDRC port are you using mDin6 or HD15?

Assuming you have a UDRC II
If you are using mDin6 then you will need to set up Direwolf channel 1
(Direwolf uses chan 0 & 1) and PTT will be active on GPIO 23.

If you are using the HD15 interface you will need to set up Direwolf
channel 0 and PTT will be active on GPIO 12.

From your config it looks like you have the Direwolf channels switched
around for mDin6 & HD15 interfaces.

/Basil n7nix


On Thu, 15 Feb 2018 09:14:56 -0800
"John Spoonhower" <jpspoonhower@...> wrote:

I need some help with configuring direwolf. Let me start by saying
that I have direwolf running well in receive mode on a raspberry pi 3
with udrc-II. The problem lies with the lack of audio on transmit. I
am asking the setup to broadcast my setup with PBEACON on the radio.
With some setup configurations I get the transmitter to key (PTT
works!) but there is no audio (tones are not evident on a separate
second radio). I have setup FLDIGI using the online installation
notes and if I click "tune" in FLDIGI , the transmitter keys and I
hear I nice tone. I can run measure_deviate.sh and also get the
transmitter to key and generate a tone. Measure_deviate.sh is setup
in the "stock" manner with gpio  set to gpio 12. FLDIGI setup is also
"stock" with GPIO hardware control : BCM 23, GPIO 04, pin 16
selection. 

The direwolf.conf file looks like:
ADEVICE plughw:CARD=udrc,DEV=0
ARATE 48000
ACHANNELS 2
#DIN-6
CHANNEL 0
MYCALL NX2I-10
MODEM 1200i
PTT GPIO 23
#HD-15
# note channels set the same
CHANNEL 1
MYCALL NX2I-10
MODEM 1200
PTT GPIO 23
AGWPORT 8000
KISSPORT 8001
PBEACON delay=1 sendto=0 every=10 overlay=R symbol="igate"
lat=28^52.69N long=82^$ #PBEACON delay=1 sendto=1 every=10 overlay=S
symbol="digi" lat=17^51.00N long=102$ #DIGIPEAT 0 0
^WIDE[3-7]-[1-7]$|^TEST$ ^WIDE[12]-[12]$ TRACE #DIGIPEAT 1 1
^WIDE[3-7]-[1-7]$|^TEST$ ^WIDE[12]-[12]$ TRACE #DIGIPEAT 0 1
^WIDE[3-7]-[1-7]$|^TEST$ ^WIDE[12]-[12]$ TRACE #DIGIPEAT 1 0
^WIDE[3-7]-[1-7]$|^TEST$ ^WIDE[12]-[12]$ TRACE IGSERVER noam.aprs2.net
IGLOGIN NX2I 4083  #YOUR INTERNET LOGIN AND PASSCODE FOR APRS
REPORTING # Degrees Decimal minutes format for lat, long
PBEACON sendto=IG delay=0:30 every=30:00 symbol="igate" overlay=R
lat=28^52.69386$ LOGDIR /home/pi/aprslogs
IGTXLIMIT 6 10
GPSD localhost
#IBEACON DELAY=30 EVERY=30 VIA=WIDE1-1

If I have PTT GPIO 23 set (like above) I see the transmitter key but
there is no audio. If I set the GPIO in this file to 12, the
transmitter does not key. Obviously I am doing something wrong, but
none of this makes any sense to me. 73, john, NX2I


direwolf configuration file

John Spoonhower
 

I need some help with configuring direwolf. Let me start by saying that I have direwolf running well in receive mode on a raspberry pi 3 with udrc-II. The problem lies with the lack of audio on transmit. I am asking the setup to broadcast my setup with PBEACON on the radio. With some setup configurations I get the transmitter to key (PTT works!) but there is no audio (tones are not evident on a separate second radio). I have setup FLDIGI using the online installation notes and if I click "tune" in FLDIGI , the transmitter keys and I hear I nice tone. I can run measure_deviate.sh and also get the transmitter to key and generate a tone. Measure_deviate.sh is setup in the "stock" manner with gpio  set to gpio 12. FLDIGI setup is also "stock" with GPIO hardware control : BCM 23, GPIO 04, pin 16 selection. 

The direwolf.conf file looks like:
ADEVICE plughw:CARD=udrc,DEV=0
ARATE 48000
ACHANNELS 2
#DIN-6
CHANNEL 0
MYCALL NX2I-10
MODEM 1200i
PTT GPIO 23
#HD-15
# note channels set the same
CHANNEL 1
MYCALL NX2I-10
MODEM 1200
PTT GPIO 23
AGWPORT 8000
KISSPORT 8001
PBEACON delay=1 sendto=0 every=10 overlay=R symbol="igate" lat=28^52.69N long=82^$
#PBEACON delay=1 sendto=1 every=10 overlay=S symbol="digi" lat=17^51.00N long=102$
#DIGIPEAT 0 0 ^WIDE[3-7]-[1-7]$|^TEST$ ^WIDE[12]-[12]$ TRACE
#DIGIPEAT 1 1 ^WIDE[3-7]-[1-7]$|^TEST$ ^WIDE[12]-[12]$ TRACE
#DIGIPEAT 0 1 ^WIDE[3-7]-[1-7]$|^TEST$ ^WIDE[12]-[12]$ TRACE
#DIGIPEAT 1 0 ^WIDE[3-7]-[1-7]$|^TEST$ ^WIDE[12]-[12]$ TRACE
IGSERVER noam.aprs2.net
IGLOGIN NX2I 4083  #YOUR INTERNET LOGIN AND PASSCODE FOR APRS REPORTING
# Degrees Decimal minutes format for lat, long
PBEACON sendto=IG delay=0:30 every=30:00 symbol="igate" overlay=R lat=28^52.69386$
LOGDIR /home/pi/aprslogs
IGTXLIMIT 6 10
GPSD localhost
#IBEACON DELAY=30 EVERY=30 VIA=WIDE1-1

If I have PTT GPIO 23 set (like above) I see the transmitter key but there is no audio. If I set the GPIO in this file to 12, the transmitter does not key. Obviously I am doing something wrong, but none of this makes any sense to me.
73,
john, NX2I


Re: UDRC not repeating

G3GJA
 

Hi John

Double checked band setting; see below. Version enquiry returns 0x0003

Clive



On 12/02/2018 00:41, John D Hays - K7VE wrote:
Hi Clive,

A few more pieces of information would be helpful.

Is the DR-1X on VHF or UHF?  Did you select the matching choice on the Web Interface? (It affects the way it sees the incoming signal)

Is CTCSS/DCS set an analogue for FM?

What is output by cat /sys/firmware/devicetree/base/hat/product_ver

If you don't get it running, send me your /etc/opendv/dstarrepeaterd_1 file via email to look at.






On Sun, Feb 11, 2018 at 3:05 PM, CliveR <clive@...> wrote:

I've having another attempt to use the UDRC (original version) to get D-Star on a Yaesu DR-1X as it now has v1.10q firmware installed. I have installed the image from starbuck.hays.org., using the web interface to configure it.

Tthe ircDDB gateway links to the DCS reflectors and any activity there is relayed by the DR-1X and is received on my IC-E2820 or an ID-51. However, when I transmit D-Star on the repeater's uplink channel the repeater's display shows both Tx and Rx switching to FM (changes from both Red to both Yellow) and the Rx symbol goes green indicating signal received but the transmitter does not key up until the input signal de-keys and then the DR-1X sends the usual pip. In other words it relays network traffic but not RF. 

This problem does not always show and then a valid D-Star signal on the input is relayed. About 1 in 10 startups successfully relay D-Star RF. FM relaying works normally at all times. I have tried different SD cards and a different Raspberry Pi (a model 2B and a 3) with no difference. The repeater is set to wide deviation although it will need to use narrow FM when it goes into service.

A D-Star RF input signal produces 220mV pk-pk of D-Star data on pin 8 of the interface (discout) but there is 620mV pk-pk of audio when using FM; is there enough D-Star signal for the modem chip? pin 6 (tone in) has around 1v pk-pk when relaying the reflector.

Can anyone suggest why it won't relay D-Star RF please?

Clive G3GJA





--


John D. Hays
Edmonds, WA
K7VE

   


HESH Computer Services Limited Tel: (01482) 324936
12 Louis Pearlman Centre Web: www.hesh.co.uk
Goulton Street Registered in England No.: 3003479
Hull VAT No.: GB 647 3679 95
HU3 4DL

Disclaimer:
The information contained in this email may be legally privileged and/or confidential. If you are not the intended recipient, use of this information (including disclosure, copying or distribution) or any action taken, or omitted to be taken, in reliance on it is prohibited and may be unlawful; therefore please inform the sender and delete the message immediately. The views expressed in this email are those of the originator and not necessarily those held by HESH Computer Services Ltd, who do not accept liability for any action taken in reliance on the contents of this message or for the consequences of any computer viruses which may have been transmitted by this email.


Re: UDRC not repeating

G3GJA
 

Thanks for responding John

 

The DR-1X is set to VHF and the appropriate choice made which I presume is the same as the section in the NWDR DR-1X WiKi for audio inversion or not depending on the band in use.

 

CTCSS is selected – it’s mandatory in the UK

 

I’ll look at the other items when I get home tonight.

 

Clive

 

From: udrc@nw-digital-radio.groups.io [mailto:udrc@nw-digital-radio.groups.io] On Behalf Of John D Hays - K7VE
Sent: 12 February 2018 00:42
To: udrc@nw-digital-radio.groups.io
Subject: Re: [udrc] UDRC not repeating

 

Hi Clive,

 

A few more pieces of information would be helpful.

 

Is the DR-1X on VHF or UHF?  Did you select the matching choice on the Web Interface? (It affects the way it sees the incoming signal)

 

Is CTCSS/DCS set an analogue for FM?

 

What is output by cat /sys/firmware/devicetree/base/hat/product_ver

 

If you don't get it running, send me your /etc/opendv/dstarrepeaterd_1 file via email to look at.

 

 



 

On Sun, Feb 11, 2018 at 3:05 PM, CliveR <clive@...> wrote:

I've having another attempt to use the UDRC (original version) to get D-Star on a Yaesu DR-1X as it now has v1.10q firmware installed. I have installed the image from starbuck.hays.org., using the web interface to configure it.

Tthe ircDDB gateway links to the DCS reflectors and any activity there is relayed by the DR-1X and is received on my IC-E2820 or an ID-51. However, when I transmit D-Star on the repeater's uplink channel the repeater's display shows both Tx and Rx switching to FM (changes from both Red to both Yellow) and the Rx symbol goes green indicating signal received but the transmitter does not key up until the input signal de-keys and then the DR-1X sends the usual pip. In other words it relays network traffic but not RF. 

This problem does not always show and then a valid D-Star signal on the input is relayed. About 1 in 10 startups successfully relay D-Star RF. FM relaying works normally at all times. I have tried different SD cards and a different Raspberry Pi (a model 2B and a 3) with no difference. The repeater is set to wide deviation although it will need to use narrow FM when it goes into service.

A D-Star RF input signal produces 220mV pk-pk of D-Star data on pin 8 of the interface (discout) but there is 620mV pk-pk of audio when using FM; is there enough D-Star signal for the modem chip? pin 6 (tone in) has around 1v pk-pk when relaying the reflector.

Can anyone suggest why it won't relay D-Star RF please?

Clive G3GJA



 

--

 


John D. Hays
Edmonds, WA

K7VE

 

   

 

HESH Computer Services Limited Tel: (01482) 324936
12 Louis Pearlman Centre Web: www.hesh.co.uk
Goulton Street Registered in England No.: 3003479
Hull VAT No.: GB 647 3679 95
HU3 4DL

Disclaimer:
The information contained in this email may be legally privileged and/or confidential. If you are not the intended recipient, use of this information (including disclosure, copying or distribution) or any action taken, or omitted to be taken, in reliance on it is prohibited and may be unlawful; therefore please inform the sender and delete the message immediately. The views expressed in this email are those of the originator and not necessarily those held by HESH Computer Services Ltd, who do not accept liability for any action taken in reliance on the contents of this message or for the consequences of any computer viruses which may have been transmitted by this email.


Re: UDRC not repeating

 

Hi Clive,

A few more pieces of information would be helpful.

Is the DR-1X on VHF or UHF?  Did you select the matching choice on the Web Interface? (It affects the way it sees the incoming signal)

Is CTCSS/DCS set an analogue for FM?

What is output by cat /sys/firmware/devicetree/base/hat/product_ver

If you don't get it running, send me your /etc/opendv/dstarrepeaterd_1 file via email to look at.






On Sun, Feb 11, 2018 at 3:05 PM, CliveR <clive@...> wrote:

I've having another attempt to use the UDRC (original version) to get D-Star on a Yaesu DR-1X as it now has v1.10q firmware installed. I have installed the image from starbuck.hays.org., using the web interface to configure it.

Tthe ircDDB gateway links to the DCS reflectors and any activity there is relayed by the DR-1X and is received on my IC-E2820 or an ID-51. However, when I transmit D-Star on the repeater's uplink channel the repeater's display shows both Tx and Rx switching to FM (changes from both Red to both Yellow) and the Rx symbol goes green indicating signal received but the transmitter does not key up until the input signal de-keys and then the DR-1X sends the usual pip. In other words it relays network traffic but not RF. 

This problem does not always show and then a valid D-Star signal on the input is relayed. About 1 in 10 startups successfully relay D-Star RF. FM relaying works normally at all times. I have tried different SD cards and a different Raspberry Pi (a model 2B and a 3) with no difference. The repeater is set to wide deviation although it will need to use narrow FM when it goes into service.

A D-Star RF input signal produces 220mV pk-pk of D-Star data on pin 8 of the interface (discout) but there is 620mV pk-pk of audio when using FM; is there enough D-Star signal for the modem chip? pin 6 (tone in) has around 1v pk-pk when relaying the reflector.

Can anyone suggest why it won't relay D-Star RF please?

Clive G3GJA





--


John D. Hays
Edmonds, WA
K7VE

   


UDRC not repeating

G3GJA
 

I've having another attempt to use the UDRC (original version) to get D-Star on a Yaesu DR-1X as it now has v1.10q firmware installed. I have installed the image from starbuck.hays.org., using the web interface to configure it.

Tthe ircDDB gateway links to the DCS reflectors and any activity there is relayed by the DR-1X and is received on my IC-E2820 or an ID-51. However, when I transmit D-Star on the repeater's uplink channel the repeater's display shows both Tx and Rx switching to FM (changes from both Red to both Yellow) and the Rx symbol goes green indicating signal received but the transmitter does not key up until the input signal de-keys and then the DR-1X sends the usual pip. In other words it relays network traffic but not RF. 

This problem does not always show and then a valid D-Star signal on the input is relayed. About 1 in 10 startups successfully relay D-Star RF. FM relaying works normally at all times. I have tried different SD cards and a different Raspberry Pi (a model 2B and a 3) with no difference. The repeater is set to wide deviation although it will need to use narrow FM when it goes into service.

A D-Star RF input signal produces 220mV pk-pk of D-Star data on pin 8 of the interface (discout) but there is 620mV pk-pk of audio when using FM; is there enough D-Star signal for the modem chip? pin 6 (tone in) has around 1v pk-pk when relaying the reflector.

Can anyone suggest why it won't relay D-Star RF please?

Clive G3GJA



Re: UDRC with both fldigi and direwolf

John Spoonhower
 

Please disregard my prior note. I found the problem in direwolf.conf.
NX2I

On Fri, Feb 9, 2018 at 11:22 AM, John Spoonhower <jpspoonhower@...> wrote:
OK, this did not go well. 
I removed the restriction on libasound2 and libasound2-data with "sudo apt-mark unhold  libasound2 and libasound2-data". Then did sudo apt-get update and sudo apt-get upgrade to install the latest libraries.
Now direwolf is broken and reports:

pi@compass:~ $ direwolf
Dire Wolf version 1.3
Includes optional support for:  gpsd
Reading config file direwolf.conf
Audio input device for receive: plughw:CARD=udrc,DEV=0  (channel 0)
Audio out device for transmit: ARATE  (channel 0)
Could not set hw params
Invalid argument
for plughw:CARD=udrc,DEV=0 input.
ALSA lib pcm.c:2239:(snd_pcm_open_noupdate) Unknown PCM ARATE
Could not open audio device ARATE for output
No such file or directory
Pointless to continue without audio device.

so now what do I do??
73, NX2I, John


On Fri, Feb 9, 2018 at 10:23 AM, John D Hays - K7VE <john@...> wrote:
I have compiled and run WSJT-X with CAT control for PTT 

On Feb 9, 2018 07:01, "Corky Searls" <af4pm@...> wrote:
John, sorry for the confusion. The hold for the libasound libraries is no longer required (at least I have not used it and all is working fine. 

You can load fldigi, and WSJT-X on the pi, but you will only be able to use one application at a time as each of them (Direwolf, Fldigi, and WSJT-X) seem to need full control of the UDRC. While I have fully tested fldigi with the versions that were current as of this past Monday (updated instructions are on the NW Digital Radio web side wiki), I have not yet tested WSJT-X with the Pi/UDRC combination, though I see no reason why this should not work.

Hope this helps to clear the confusion,
-Corky, AF4PM

On Feb 9, 2018, at 6:36 AM, John Spoonhower <jpspoonhower@...> wrote:

I have a nicely working Packet Igate currently running on a Raspberry Pi 3 with a UDRC-II, Direwolf 1.3 and the latest Compass build. The Wiki for the installation is pretty explicit about not using the libasound libraries ; "sudo apt-mark hold libasound2 libasound2-data" (from the Wiki). I want to also install fldigi and perhaps, WSJT-X on this same Pi, but the installation calls for Portaudio that depends on the libasound libraries. Are these 2 installations incompatible? Can I get these all the work on the same Raspberry Pi 3?

73, John, NX2I




Re: UDRC with both fldigi and direwolf

John Spoonhower
 

OK, this did not go well. 
I removed the restriction on libasound2 and libasound2-data with "sudo apt-mark unhold  libasound2 and libasound2-data". Then did sudo apt-get update and sudo apt-get upgrade to install the latest libraries.
Now direwolf is broken and reports:

pi@compass:~ $ direwolf
Dire Wolf version 1.3
Includes optional support for:  gpsd
Reading config file direwolf.conf
Audio input device for receive: plughw:CARD=udrc,DEV=0  (channel 0)
Audio out device for transmit: ARATE  (channel 0)
Could not set hw params
Invalid argument
for plughw:CARD=udrc,DEV=0 input.
ALSA lib pcm.c:2239:(snd_pcm_open_noupdate) Unknown PCM ARATE
Could not open audio device ARATE for output
No such file or directory
Pointless to continue without audio device.

so now what do I do??
73, NX2I, John


On Fri, Feb 9, 2018 at 10:23 AM, John D Hays - K7VE <john@...> wrote:
I have compiled and run WSJT-X with CAT control for PTT 

On Feb 9, 2018 07:01, "Corky Searls" <af4pm@...> wrote:
John, sorry for the confusion. The hold for the libasound libraries is no longer required (at least I have not used it and all is working fine. 

You can load fldigi, and WSJT-X on the pi, but you will only be able to use one application at a time as each of them (Direwolf, Fldigi, and WSJT-X) seem to need full control of the UDRC. While I have fully tested fldigi with the versions that were current as of this past Monday (updated instructions are on the NW Digital Radio web side wiki), I have not yet tested WSJT-X with the Pi/UDRC combination, though I see no reason why this should not work.

Hope this helps to clear the confusion,
-Corky, AF4PM

On Feb 9, 2018, at 6:36 AM, John Spoonhower <jpspoonhower@...> wrote:

I have a nicely working Packet Igate currently running on a Raspberry Pi 3 with a UDRC-II, Direwolf 1.3 and the latest Compass build. The Wiki for the installation is pretty explicit about not using the libasound libraries ; "sudo apt-mark hold libasound2 libasound2-data" (from the Wiki). I want to also install fldigi and perhaps, WSJT-X on this same Pi, but the installation calls for Portaudio that depends on the libasound libraries. Are these 2 installations incompatible? Can I get these all the work on the same Raspberry Pi 3?

73, John, NX2I



Re: UDRC with both fldigi and direwolf

 

I have compiled and run WSJT-X with CAT control for PTT 

On Feb 9, 2018 07:01, "Corky Searls" <af4pm@...> wrote:
John, sorry for the confusion. The hold for the libasound libraries is no longer required (at least I have not used it and all is working fine. 

You can load fldigi, and WSJT-X on the pi, but you will only be able to use one application at a time as each of them (Direwolf, Fldigi, and WSJT-X) seem to need full control of the UDRC. While I have fully tested fldigi with the versions that were current as of this past Monday (updated instructions are on the NW Digital Radio web side wiki), I have not yet tested WSJT-X with the Pi/UDRC combination, though I see no reason why this should not work.

Hope this helps to clear the confusion,
-Corky, AF4PM

On Feb 9, 2018, at 6:36 AM, John Spoonhower <jpspoonhower@...> wrote:

I have a nicely working Packet Igate currently running on a Raspberry Pi 3 with a UDRC-II, Direwolf 1.3 and the latest Compass build. The Wiki for the installation is pretty explicit about not using the libasound libraries ; "sudo apt-mark hold libasound2 libasound2-data" (from the Wiki). I want to also install fldigi and perhaps, WSJT-X on this same Pi, but the installation calls for Portaudio that depends on the libasound libraries. Are these 2 installations incompatible? Can I get these all the work on the same Raspberry Pi 3?

73, John, NX2I


Re: UDRC with both fldigi and direwolf

John Spoonhower
 

Corky,
thanks for the information. I understand the restriction on one application at a time.
I'll remove the restriction on libasound and see how the rest goes.
Again, thanks for the prompt reply!!
73, John

On Fri, Feb 9, 2018 at 10:00 AM, Corky Searls <af4pm@...> wrote:
John, sorry for the confusion. The hold for the libasound libraries is no longer required (at least I have not used it and all is working fine. 

You can load fldigi, and WSJT-X on the pi, but you will only be able to use one application at a time as each of them (Direwolf, Fldigi, and WSJT-X) seem to need full control of the UDRC. While I have fully tested fldigi with the versions that were current as of this past Monday (updated instructions are on the NW Digital Radio web side wiki), I have not yet tested WSJT-X with the Pi/UDRC combination, though I see no reason why this should not work.

Hope this helps to clear the confusion,
-Corky, AF4PM

On Feb 9, 2018, at 6:36 AM, John Spoonhower <jpspoonhower@...> wrote:

I have a nicely working Packet Igate currently running on a Raspberry Pi 3 with a UDRC-II, Direwolf 1.3 and the latest Compass build. The Wiki for the installation is pretty explicit about not using the libasound libraries ; "sudo apt-mark hold libasound2 libasound2-data" (from the Wiki). I want to also install fldigi and perhaps, WSJT-X on this same Pi, but the installation calls for Portaudio that depends on the libasound libraries. Are these 2 installations incompatible? Can I get these all the work on the same Raspberry Pi 3?

73, John, NX2I



Re: UDRC with both fldigi and direwolf

Corky Searls
 

John, sorry for the confusion. The hold for the libasound libraries is no longer required (at least I have not used it and all is working fine. 

You can load fldigi, and WSJT-X on the pi, but you will only be able to use one application at a time as each of them (Direwolf, Fldigi, and WSJT-X) seem to need full control of the UDRC. While I have fully tested fldigi with the versions that were current as of this past Monday (updated instructions are on the NW Digital Radio web side wiki), I have not yet tested WSJT-X with the Pi/UDRC combination, though I see no reason why this should not work.

Hope this helps to clear the confusion,
-Corky, AF4PM

On Feb 9, 2018, at 6:36 AM, John Spoonhower <jpspoonhower@...> wrote:

I have a nicely working Packet Igate currently running on a Raspberry Pi 3 with a UDRC-II, Direwolf 1.3 and the latest Compass build. The Wiki for the installation is pretty explicit about not using the libasound libraries ; "sudo apt-mark hold libasound2 libasound2-data" (from the Wiki). I want to also install fldigi and perhaps, WSJT-X on this same Pi, but the installation calls for Portaudio that depends on the libasound libraries. Are these 2 installations incompatible? Can I get these all the work on the same Raspberry Pi 3?

73, John, NX2I


UDRC with both fldigi and direwolf

John Spoonhower
 

I have a nicely working Packet Igate currently running on a Raspberry Pi 3 with a UDRC-II, Direwolf 1.3 and the latest Compass build. The Wiki for the installation is pretty explicit about not using the libasound libraries ; "sudo apt-mark hold libasound2 libasound2-data" (from the Wiki). I want to also install fldigi and perhaps, WSJT-X on this same Pi, but the installation calls for Portaudio that depends on the libasound libraries. Are these 2 installations incompatible? Can I get these all the work on the same Raspberry Pi 3?

73, John, NX2I


Wi-Fi connection #udrc-ii

Alexander <alexgish3rd@...>
 

Just installed Compass on a fresh SD card. Compass and my Pi seem to get along ok. I would like to know how to configure a warless connection with my home router??? 


Re: Dashboard won't start

Dave N2OA
 

Thank you but I wanted to use realvnc because of the cloud access. I cannot get an inbound connection because of the way the provider has secured their service.

Dave
N2OA

On Mon, Feb 5, 2018 at 6:16 AM, TG9AOR <qrz@...> wrote:
I have used x11vnc. After apt-get install x11vnc you would need to store the vnc password under the home directory(/home/pi)
X11vnc -storepasswd (no sudo command so that pi is the owner)

Then you make a startup file, also under the home directory.
nano .xsessionrc (no sudo so that user pi is the owner) the contents would be

x11vnc -bg -forever -nevershared -tightfilexfer -usepw -display :0

After you save it you make it executable via the command: chmod 0775 .xsessionrc

After doing the above you reboot and you should be able to VNC into it with your preferred VNC client.

I credit the procedure above to Code Chief's Space.

73 de TG9AOR



Re: Dashboard won't start

TG9AOR
 

I have used x11vnc. After apt-get install x11vnc you would need to store the vnc password under the home directory(/home/pi)
X11vnc -storepasswd (no sudo command so that pi is the owner)

Then you make a startup file, also under the home directory.
nano .xsessionrc (no sudo so that user pi is the owner) the contents would be

x11vnc -bg -forever -nevershared -tightfilexfer -usepw -display :0

After you save it you make it executable via the command: chmod 0775 .xsessionrc

After doing the above you reboot and you should be able to VNC into it with your preferred VNC client.

I credit the procedure above to Code Chief's Space.

73 de TG9AOR


Re: Dashboard won't start

Dave N2OA
 

Of course I was too far gone already and started a rebuild :-( Now I have a new issue. VNC seems to be missing in the latest version of Compass. The only way I have found to access my devices is through the cloud service because of firewall/NAT restrictions. I did an install of VNC but can't figure out how to enable it since all the options are gone from raspi-config and the gui. Of course everything on the internet is based on the availability of those tools.

Thanks,

Dave
N2OA


Re: installation issue curl doesn't work

 

Thanks for the followup -- I suspected network issues.  I was on my phone so didn't type out a longish response.


On Fri, Feb 2, 2018 at 11:03 AM, John Spoonhower <jpspoonhower@...> wrote:
thanks.
I got the curl command working. Turns out I had a temporary network problem.




--


John D. Hays
Edmonds, WA
K7VE

   


Re: installation issue curl doesn't work

John Spoonhower
 

thanks.
I got the curl command working. Turns out I had a temporary network problem.