Date   
Re: UDRC II

 

Matt,

We have an asound.conf that does break the ports out and yes mmap support needs to be enabled.  

However, the mmap module is still experimental and needs a lot of testing before recommendation in production systems.

Also, some applications need work to support the 'virtual' soundcards, for example dstarrepeater cannot currently support these configurations.

Its great that you have sorted it for yourself, but as you say it is complex to setup and thus we generally don't recommend it until it can be better documented and tested.

On Fri, Sep 30, 2016 at 4:11 PM, Matthew Wolf <mjwn4mtt@...> wrote:

The UDRC is using the I2S interface on the RPI. The I2S driver for the RPI interface does not allow multiple applications to access the CODEC.

There is a way to get multiple applications to use the I2S interface. The Linux Alsa drivers support software based "multiplexing" of the I2S interface.

The Alsa subsystem accesses the I2S (CODEC) interface and then the applications access a "virtual" sound card. Configuring Alsa multiplexing is non-trivial. It is very complex.

Here is a link that provides a overview of how to create a Alsa configuration file (asoundrc) for multiplexing,  http://alsa.opensrc.org/AlsaSharing . 

In order for the Alsa multiplexing to function the hardware is required to support Alsa mmap. The default configuration of a RPI does not support mmap.  A device tree overlay has to be loaded to enable the mmap on the RPI's I2S interface.

The line "dtoverlay=i2s-mmap" has to be added to the /boot/config.txt to load the i2c-mmap device tree overlay

I have Direwolf and the Festival Speech Synthesis accessing the CODEC at the same time.  My current Alsa configuration file is a mess. Once I get the configuration file cleaned up, I am going to post a message about how I am able to use the UDRC to allow a single RPI to be a APRS digi / igate and a APRSTT gateway.

I still need find a filter that will allow me to use the same antenna for ARPS and ARPSTT .


-Matt, N4MTT




--


John D. Hays
K7VE

PO Box 1223, Edmonds, WA 98020-1223
   

Re: Pi Case

 

Hi Dave,

Budd makes a good product and it is a good way to enclose/protect your UDRC and Pi.

Be advised that the 12 VDC connection is not needed when attached to the DR-1X as the 15-Pin cable provides power to the UDRC and Pi, but having it available is good for when you might want to operate without the repeater.

-- John

Re: Pi Case

davet1953@...
 

Hello Budd,


Want to get a case with the 12VDC Connector Kit. Your complete email address isn't shown so need that for PayPal. Beautiful country there in Washington State. Spent 5 days in Oak Harbor on Whidbey Island a few years back visiting my Daughter-in-law and Grandaughters. My son was deployed at the time (Navy). They are now in Scotland.


In the process of setting up 2 UDRC's with Raspberry Pi's to use with Yaesu Fusions (in shipping)

Dave, AB2WL


Re: UDRC II

Matthew Wolf
 

The UDRC is using the I2S interface on the RPI. The I2S driver for the RPI interface does not allow multiple applications to access the CODEC.

There is a way to get multiple applications to use the I2S interface. The Linux Alsa drivers support software based "multiplexing" of the I2S interface.

The Alsa subsystem accesses the I2S (CODEC) interface and then the applications access a "virtual" sound card. Configuring Alsa multiplexing is non-trivial. It is very complex.

Here is a link that provides a overview of how to create a Alsa configuration file (asoundrc) for multiplexing,  http://alsa.opensrc.org/AlsaSharing . 

In order for the Alsa multiplexing to function the hardware is required to support Alsa mmap. The default configuration of a RPI does not support mmap.  A device tree overlay has to be loaded to enable the mmap on the RPI's I2S interface.

The line "dtoverlay=i2s-mmap" has to be added to the /boot/config.txt to load the i2c-mmap device tree overlay

I have Direwolf and the Festival Speech Synthesis accessing the CODEC at the same time.  My current Alsa configuration file is a mess. Once I get the configuration file cleaned up, I am going to post a message about how I am able to use the UDRC to allow a single RPI to be a APRS digi / igate and a APRSTT gateway.

I still need find a filter that will allow me to use the same antenna for ARPS and ARPSTT .


-Matt, N4MTT

Re: Will UDRC II work with RPi A+ ?

Jeremy McDermond <mcdermj@...>
 

The UDRC is not supported on armv6 platforms.

Jeremy McDermond

On Sep 30, 2016, at 4:40 AM, VK3IL <david@...> wrote:

Yes, I downloaded a fresh image of compass, loaded it onto the A+ and used a WiFi dongle to connect to the network. I followed the Direwolf instructions and did the update and upgrades as well as installing Direwolf. I also disabled the on-board audio as per the instructions and made sure i2c and i2s were enabled in the config.txt file. Everything seemed to work fine except that udrc is not recognised by ALSA. Happy to try and fault find if you can give me some pointers.


Re: Will UDRC II work with RPi A+ ?

VK3IL
 

Yes, I downloaded a fresh image of compass, loaded it onto the A+ and used a WiFi dongle to connect to the network. I followed the Direwolf instructions and did the update and upgrades as well as installing Direwolf. I also disabled the on-board audio as per the instructions and made sure i2c and i2s were enabled in the config.txt file. Everything seemed to work fine except that udrc is not recognised by ALSA. Happy to try and fault find if you can give me some pointers.

Re: Will UDRC II work with RPi A+ ?

 

We have not tested on the A+ and I don't have one to verify.

In general I find it good to have a network interface for updates and software loading. 

The UDRC II works with the network disconnected after installation.

Did you burn a fresh image and perform an apt-get update and apt-get upgrade before transferring it to the A+?

On Thu, Sep 29, 2016 at 5:54 PM, VK3IL <david@...> wrote:

Hi John,

My UDRC II has now arrived - thanks for the quick shipping.

In my application (tracking/digipeating), I don't need network interfacing, so was hoping to use the RPi A+ rather than a Pi 2/3. I've installed the card and compass image on the A+, but can't get the card recognised by ALSA (not listed through aplay -l). I've tried re-plugging, rebooting and making sure both i2c and i2s hardware is enabled in /boot/config.txt. 

First wanted to check whether there was any known incompatibility with the A+ model and if not, suggestions on diagnosing the problem.

Thanks.

David

VK3IL




--


John D. Hays
K7VE

PO Box 1223, Edmonds, WA 98020-1223
   

Will UDRC II work with RPi A+ ?

VK3IL
 

Hi John,

My UDRC II has now arrived - thanks for the quick shipping.

In my application (tracking/digipeating), I don't need network interfacing, so was hoping to use the RPi A+ rather than a Pi 2/3. I've installed the card and compass image on the A+, but can't get the card recognised by ALSA (not listed through aplay -l). I've tried re-plugging, rebooting and making sure both i2c and i2s hardware is enabled in /boot/config.txt. 

First wanted to check whether there was any known incompatibility with the A+ model and if not, suggestions on diagnosing the problem.

Thanks.

David

VK3IL

Re: UDRC II

 

If you are using it as a local repeater, it works out fine, especially if users turn on BCLO (Busy Channel Lock Out) -- but if you are connecting to a network (D-STAR or WIRES-X) best practice suggests you pick one or the other.

On Thu, Sep 29, 2016 at 4:52 PM, Michael Champion Sr <mikec@...> wrote:
There are delays in the software but I don't think that will help. I can see where this would happen bough since both digital users have no idea the other is there. 

Tri mode sounds cool but in actual practice with wires-x it seems problematic. 

-Michael

On Sep 28, 2016, at 18:52, VE1JSR @outlook.com <ve1jsr@...> wrote:

Good Evening,

Thank you for the info on updating my software and getting the UDRC-II up and running. So far all is working good, I did notice that if you have fusion connected to a wires-x node and D-star connected to a busy reflector the repeater switches back and forth between both instantaneously. With the UDRC I believe there was a slight delay.

Currently if I am connected to a busy D-star reflector and a busy Wires-x node and having a QSO on D-star, once I un-key my radio the repeater switches immediately to the traffic on Wires-x and visa versa. Is there not a delay in the software to prevent that from happening? and if so is there an adjustment to extend the delay?

 (NOT THAT I WOULD EVER HAVE BOTH RUNNING AT THE SAME TIME) but it is a scenario that may occur on the repeater


If I am not mistaken when I had the UDRC running I could un-key and would continue to hear the other ham I was talking to get back to me. And if there was a long space in-between the QSO on the next go around it would switch modes?



James ve1jcs




--


John D. Hays
K7VE

PO Box 1223, Edmonds, WA 98020-1223
   

Re: UDRC II

Michael Champion Sr
 

There are delays in the software but I don't think that will help. I can see where this would happen bough since both digital users have no idea the other is there. 

Tri mode sounds cool but in actual practice with wires-x it seems problematic. 

-Michael

On Sep 28, 2016, at 18:52, VE1JSR @outlook.com <ve1jsr@...> wrote:

Good Evening,

Thank you for the info on updating my software and getting the UDRC-II up and running. So far all is working good, I did notice that if you have fusion connected to a wires-x node and D-star connected to a busy reflector the repeater switches back and forth between both instantaneously. With the UDRC I believe there was a slight delay.

Currently if I am connected to a busy D-star reflector and a busy Wires-x node and having a QSO on D-star, once I un-key my radio the repeater switches immediately to the traffic on Wires-x and visa versa. Is there not a delay in the software to prevent that from happening? and if so is there an adjustment to extend the delay?

 (NOT THAT I WOULD EVER HAVE BOTH RUNNING AT THE SAME TIME) but it is a scenario that may occur on the repeater


If I am not mistaken when I had the UDRC running I could un-key and would continue to hear the other ham I was talking to get back to me. And if there was a long space in-between the QSO on the next go around it would switch modes?



James ve1jcs

Re: UDRC II

 

If there is an analog signal with PL or Fusion Digital on the input of the repeater it will assert a pin that basically tells D-STAR that there is local traffic and block traffic coming in on the network from D-STAR.  

Without knowing your exact configuration (are you depending on signal capture) it's hard to say what is happening for you.

Re: Kenwood TKR-750/850

Mason AF5WN
 

I have the version 2 with the 91D software so I'm good in that department. I mostly have experience with programming the repeater and various controllers so the UDRC is new territory for me. My main goal is to convert this repeater over to a full out d-star repeater without any modifications to the physical repeater.

UDRC II

VE1JSR
 

Good Evening,

Thank you for the info on updating my software and getting the UDRC-II up and running. So far all is working good, I did notice that if you have fusion connected to a wires-x node and D-star connected to a busy reflector the repeater switches back and forth between both instantaneously. With the UDRC I believe there was a slight delay.

Currently if I am connected to a busy D-star reflector and a busy Wires-x node and having a QSO on D-star, once I un-key my radio the repeater switches immediately to the traffic on Wires-x and visa versa. Is there not a delay in the software to prevent that from happening? and if so is there an adjustment to extend the delay?

 (NOT THAT I WOULD EVER HAVE BOTH RUNNING AT THE SAME TIME) but it is a scenario that may occur on the repeater


If I am not mistaken when I had the UDRC running I could un-key and would continue to hear the other ham I was talking to get back to me. And if there was a long space in-between the QSO on the next go around it would switch modes?



James ve1jcs

ircddbgateway logs

John McDonough
 

Is there a way to reduce the amount of detail in the gateway logs?  Seems like a lot of writing for an SD card, and a lot more detail than I need.


Re: UDRC II

 

Yes.

On Wed, Sep 28, 2016 at 10:29 AM, Michael Champion Sr <mikec@...> wrote:

As I am labbing this, I don’t have a Fusion HT so testing this for Fusion is tough.  Does PKSQL go low for Fusion as well as decoded PL/DCS?

 

-Michael

 

--


John D. Hays
K7VE

PO Box 1223, Edmonds, WA 98020-1223
   

Re: UDRC II

Michael Champion Sr
 

As I am labbing this, I don’t have a Fusion HT so testing this for Fusion is tough.  Does PKSQL go low for Fusion as well as decoded PL/DCS?

 

-Michael

 

From: udrc@nw-digital-radio.groups.io [mailto:udrc@nw-digital-radio.groups.io] On Behalf Of John Hays
Sent: Saturday, September 24, 2016 3:53 PM
To: udrc@nw-digital-radio.groups.io
Subject: Re: [udrc] UDRC II

 

The PKSQL on the HD15 connector (PIN 3, accessible from the matching pad behind the connector on the UDRC/UDRC II -- mislabeled an output on the datasheet) -- to ground tells the dstarrepeater function that there is analog(PL/DCS)/Fusion Digital traffic on the local repeater and should prevent network D-STAR traffic from keying the repeater.  Be mindful that this is not buffered so mind logic levels.

This is not a supported configuration, but you are free to experiment.

 

On Sat, Sep 24, 2016 at 3:33 PM, Michael Champion Sr <mikec@...> wrote:

Since this topic is open… J

 

To run my analog controller with the UDRC I’m using an Arduino to facilitate the connections between the controller, UDRC, and DR-1X. PTT from the controller and the UDRC go to 2 input pins and then Base, PTT, and EXT1 are driven by the Arduino.  There is an issue with parallel audio if dstar chimes in during a conversation it will just go through and be heard since the transmit tone would be on.  I was thinking about using an Audio matrix so that the Arduino could also mute audio from the UDRC.

 

What would be nice is if the controller code of dstarrepeater can be manipulated so that if a GPIO pin goes high(PTT from the analog Controller) then the base, ext1, and PTT lines go high on the DR-1X and some kind of interrupt for DSTAR so it doesn’t jump in(maybe even mute while the pin is high would work).   Right now I parallel the audio but what would be even cooler is to take the audio from the analog controller and run it in the DIN port and just pipe that audio back out the 15 pin.  I could then eliminate the Arduino.

 

 

-Michael

 

--

 


John D. Hays
Director

PO Box 1223, Edmonds, WA 98020-1223 

  

Re: UDRC II

 

Yes.


On Tue, Sep 27, 2016 at 3:00 PM, VE1JSR @outlook.com <ve1jsr@...> wrote:

Just a further quick comment I am using the 15pin cable that came with the UDRC, It is the same as the new one shipped with the UDRC-II is it not?

James VE1JCS




--


John D. Hays
K7VE

PO Box 1223, Edmonds, WA 98020-1223
   

Re: UDRC II

Michael Champion Sr
 

Do the below first.  I banged my head on my desk repeatedly and the upgrade fixed my odd audio issue with the UDRC-II.

 

-Michael

 

From: udrc@nw-digital-radio.groups.io [mailto:udrc@nw-digital-radio.groups.io] On Behalf Of John Hays
Sent: Tuesday, September 27, 2016 2:54 PM
To: udrc@nw-digital-radio.groups.io
Subject: Re: [udrc] UDRC II

 

Run 

 

sudo apt-get update

sudo apt-get upgrade

 

Depending on how long its been, there is a slightly newer dstarrepeater that detects whether a UDRC or UDRC II is plugged in.

 

 

On Tue, Sep 27, 2016 at 2:42 PM, VE1JSR @outlook.com <ve1jsr@...> wrote:

Just received my UDRC-II and installed it onto my raspberry pi2 running the same SD card with software that was running my UDRC. powered the unit up and my second simplex port using a moencom modem powered up and linked onto reflector and worked no problem. The DR1-x repeater would not recognise or decode D-star or the C4FM. I shutdown the system by VNC and after shutdown I rebooted the repeater and afterwards I found the C4FM started to work and decode, I had a QSO by logging into America link, No issues there.

I then tried the D-star once again and it seems to be seeing the signal and responding back but no audio is being heard, all I get on my ID-5100 is a full scale S meter signal and the DV-FM indicator flashes back and forth between DV-FM, indicating to me that it is not locking in on the D-star signal.

 

Any suggestions?

 

Thank You

 

James VE1JCS



 

--

 


John D. Hays

K7VE

 

PO Box 1223, Edmonds, WA 98020-1223

   

 

Re: UDRC II

VE1JSR
 

Just a further quick comment I am using the 15pin cable that came with the UDRC, It is the same as the new one shipped with the UDRC-II is it not?

For now I reinstalled the UDRC again until I hear back about this issue. Powered up the unit with the UDRC and all is working great again.

Now with the UDRC installed again I wanted to verifie something, While the UDRC-II was installed when I keyed up my  d-star radio the DR-1x would switch to analog (Yellow-Yellow FM) RX would light up and TX DID NOT,  hmm I could of sworn it did light up with the UDRC installed. Well I did confirm with the UDRC installed when I keyed up with my ID-5100 the DR-1x would switch to analog (Yellow-Yellow FM) and RX and TX would light up.

Now I believe this to be normal operation as this is what I have been seeing all along with the UDRC, first key up with D-star would give a DV-FM flashing on ID-5100 (indicating not locking  to signal) and second key up would lock into DV mode and return back a beep?


James VE1JCS


Re: UDRC II

 

Run 

sudo apt-get update
sudo apt-get upgrade

Depending on how long its been, there is a slightly newer dstarrepeater that detects whether a UDRC or UDRC II is plugged in.


On Tue, Sep 27, 2016 at 2:42 PM, VE1JSR @outlook.com <ve1jsr@...> wrote:

Just received my UDRC-II and installed it onto my raspberry pi2 running the same SD card with software that was running my UDRC. powered the unit up and my second simplex port using a moencom modem powered up and linked onto reflector and worked no problem. The DR1-x repeater would not recognise or decode D-star or the C4FM. I shutdown the system by VNC and after shutdown I rebooted the repeater and afterwards I found the C4FM started to work and decode, I had a QSO by logging into America link, No issues there.

I then tried the D-star once again and it seems to be seeing the signal and responding back but no audio is being heard, all I get on my ID-5100 is a full scale S meter signal and the DV-FM indicator flashes back and forth between DV-FM, indicating to me that it is not locking in on the D-star signal.


Any suggestions?


Thank You


James VE1JCS




--


John D. Hays
K7VE

PO Box 1223, Edmonds, WA 98020-1223