Date   
Hamvention 2016 - UDRC Rollout

 

Members of the NW Digital Radio team just returned from Hamvention® 2016 in Dayton, OH.

We had a Yaesu DR-1X repeater setup on 440+ running System Fusion Digital, Analog FM, and D-STAR using the UDRC in conjunction with the DR-1X's internal controller.

The booth is located very close to the exit of the main Yaesu booth and a lot of folks passing by noticed the repeater and when the functionality was shown, most who owned a DR-1X immediately purchased one or more UDRCs.

Xastir + Direwolf were also demonstrated using a FT-817 transceiver and UDRC board.  This combination can be configured and operated at either 1200 or 9600 baud packet.

Software and instructions for the UDRC will roll out in the next few days.  It was necessary to repackage the Compass extension to Raspbian due to changes made by the Raspbian development team.  All users of the UDRC need to use Compass distribution as their operating system to support the necessary drivers.  The code will be available as open source via Github for those interested in the enhancements.  Also, please use the Compass distribution for dstarrepeater package if using the UDRC for D-STAR either as a hotspot or as part of a repeater.

More to come in the coming days and weeks.

Tell Us About Your UDRC

 

What application are you implementing using the UDRC?

Where are you located?

What is the Callsign/Operating Frequency of the station of using the UDRC?

Audio Configuration Update

 

I changed a value in the udrc-alsa-setup.sh to adjust the transmit value.

If you have installed Compass Linux and have Sound Card TX set to 1.0 (or 100 in GUI), please run this command again:

curl -L -s https://goo.gl/h04nla | sudo sh

The modem voltage to the DR-1X with wide FM should be approximately 1.0 volt peak to peak.  The value set by the script was below that at 760 mv.

If you see carrier but don't hear decoded AMBE audio on a later model Icom radio like the ID-5100A, this can be the problem (it has tighter tolerances than older radios).  If you want to test the voltage, measure (I use a DSO) the signal on Pin 6.  If you look at the UDRC mounted on a Raspberry Pi, orient it so that the Ethernet jack is 'up', right below it and to the left of the 15 PIN jack is an array of pads, in the right row, the 3rd one down is Pin 6.  I clip the ground to the shell of the USB jack.

Compass image Permissions

 

Good afternoon and thank you for adding me to the group.

I previously posted in the Yahoo group the following:

In an effort to be prepared to plugin the URDC hat when it arrives I thought I would download the image and setup my micro SD card. Went to archive.compasslinux.org and downloaded zip file. No problems. Extracted the image and installed it on the SD card. No problem. Ethernet cable works but I cannot get the Edimax wifi dongle to work. the Pi sees it and loads the module for it. by doing lsusb it shows the wlan adapter on Bus 001 Device 004 exactly where it does in my other Pi distributions. Iwlist wlan0 scan shows the available networks. So I know the adapter is working and seeing the wireless world. The Pi and Edimax wifi adapter work great with several other distros.  

I cannot do much configuration with the Pi plugged into the ethernet cable as I do not have an HDMI monitor there. Where I have an HDMI monitor I do not have an available wired network connection. So where I can see what I am doing I have no network and where I have network I cannot see. (Could be a country song there, hi) 

I recognize this is not a NW Digital issue but I can find very little information concerning the compass distribution and what is built in, what works and what does not. I have followed several different step by step guides to get it to work all with failure. A little bit of direction would be very helpful and I would be grateful. 

John replied quickly and sent me on a path to solve my wifi connection issue. Turned out that even with using sudo commands I still was not able to change the configuration for the network settings to permit the wife adapter to work. I took ownership as user "pi" of the /etc/network/ directory and that permitted me to configure wife to work. I then had similar issues installing VNC. Finally got that working so I can remotely connect.

Today I thought I would preinstall dstarrepeater and ircddbgateway which again presented some permission issues, even with utilizing sudo commands. dstarrepeater was configured and I went on to ircddbgateway. When I run sudo ircddbgateway I am presented with a popup box which states "Cannot open /var/log/opendv/irrcddbgateway.log for appending. When I click OK i am presented with "Fatal Error: Assertion failed on line 67 in file Common/Logger.cpp and function DoLog: m_file->IsOpened() 
Aborted

Again this seems to be a permissions issue. 

Clearly I am a novice with the Raspberry PI and Linux and I am using this as a learning experience and do not wish to cause any problem. I completely expect this to be an issue I created. Since I do not yet have my URDC hat it may be that simple. But It appears that the image my have some permission issues for user "pi". I will continue to plug away at it and want to say John has been great and responding to my direct emails. If this is an issue in the image then I will not be the only one experiencing the issue. 

Thanks for all the help!

Rich, KR4PI




 

Re: Compass image Permissions

Steve N4IRS
 

Rich
Make sure the directory exists  /var/log/opendv/
if not you can do a "mkdir -p  /var/log/opendv/

73, Steve N4IRS

On 5/26/2016 2:23 PM, Rich KR4PI wrote:

Good afternoon and thank you for adding me to the group.

I previously posted in the Yahoo group the following:

In an effort to be prepared to plugin the URDC hat when it arrives I thought I would download the image and setup my micro SD card. Went to archive.compasslinux.org and downloaded zip file. No problems. Extracted the image and installed it on the SD card. No problem. Ethernet cable works but I cannot get the Edimax wifi dongle to work. the Pi sees it and loads the module for it. by doing lsusb it shows the wlan adapter on Bus 001 Device 004 exactly where it does in my other Pi distributions. Iwlist wlan0 scan shows the available networks. So I know the adapter is working and seeing the wireless world. The Pi and Edimax wifi adapter work great with several other distros.  

I cannot do much configuration with the Pi plugged into the ethernet cable as I do not have an HDMI monitor there. Where I have an HDMI monitor I do not have an available wired network connection. So where I can see what I am doing I have no network and where I have network I cannot see. (Could be a country song there, hi) 

I recognize this is not a NW Digital issue but I can find very little information concerning the compass distribution and what is built in, what works and what does not. I have followed several different step by step guides to get it to work all with failure. A little bit of direction would be very helpful and I would be grateful. 

John replied quickly and sent me on a path to solve my wifi connection issue. Turned out that even with using sudo commands I still was not able to change the configuration for the network settings to permit the wife adapter to work. I took ownership as user "pi" of the /etc/network/ directory and that permitted me to configure wife to work. I then had similar issues installing VNC. Finally got that working so I can remotely connect.

Today I thought I would preinstall dstarrepeater and ircddbgateway which again presented some permission issues, even with utilizing sudo commands. dstarrepeater was configured and I went on to ircddbgateway. When I run sudo ircddbgateway I am presented with a popup box which states "Cannot open /var/log/opendv/irrcddbgateway.log for appending. When I click OK i am presented with "Fatal Error: Assertion failed on line 67 in file Common/Logger.cpp and function DoLog: m_file->IsOpened() 
Aborted

Again this seems to be a permissions issue. 

Clearly I am a novice with the Raspberry PI and Linux and I am using this as a learning experience and do not wish to cause any problem. I completely expect this to be an issue I created. Since I do not yet have my URDC hat it may be that simple. But It appears that the image my have some permission issues for user "pi". I will continue to plug away at it and want to say John has been great and responding to my direct emails. If this is an issue in the image then I will not be the only one experiencing the issue. 

Thanks for all the help!

Rich, KR4PI




 

-- 
"Anything is possible if you don't know what you are talking about."
1st Law of Logic

Re: Compass image Permissions

Jeremy McDermond <mcdermj@...>
 

On May 26, 2016, at 11:32 AM, Steve Zingman <szingman@...> wrote:

Rich
Make sure the directory exists /var/log/opendv/
if not you can do a "mkdir -p /var/log/opendv/
The opendv-base package, which is automatically brought in by the dstarrepeater or dstarrepeaterd package, creates /var/log/opendv. It is owned by the opendv user and group by default, as this is what the systemd unit file sets the dstarrepeaterd daemon to run as. If you are going to use a different user to run dstarrepeater/dstarrepeaterd that doesn’t have permissions to write there, you’ll have to chown/chmod the thing so that it works.

73, Steve N4IRS

On 5/26/2016 2:23 PM, Rich KR4PI wrote:
Good afternoon and thank you for adding me to the group.

I previously posted in the Yahoo group the following:

In an effort to be prepared to plugin the URDC hat when it arrives I thought I would download the image and setup my micro SD card. Went to archive.compasslinux.org and downloaded zip file. No problems. Extracted the image and installed it on the SD card. No problem. Ethernet cable works but I cannot get the Edimax wifi dongle to work. the Pi sees it and loads the module for it. by doing lsusb it shows the wlan adapter on Bus 001 Device 004 exactly where it does in my other Pi distributions. Iwlist wlan0 scan shows the available networks. So I know the adapter is working and seeing the wireless world. The Pi and Edimax wifi adapter work great with several other distros.

I cannot do much configuration with the Pi plugged into the ethernet cable as I do not have an HDMI monitor there. Where I have an HDMI monitor I do not have an available wired network connection. So where I can see what I am doing I have no network and where I have network I cannot see. (Could be a country song there, hi)

I recognize this is not a NW Digital issue but I can find very little information concerning the compass distribution and what is built in, what works and what does not. I have followed several different step by step guides to get it to work all with failure. A little bit of direction would be very helpful and I would be grateful.

John replied quickly and sent me on a path to solve my wifi connection issue. Turned out that even with using sudo commands I still was not able to change the configuration for the network settings to permit the wife adapter to work. I took ownership as user "pi" of the /etc/network/ directory and that permitted me to configure wife to work. I then had similar issues installing VNC. Finally got that working so I can remotely connect.

Today I thought I would preinstall dstarrepeater and ircddbgateway which again presented some permission issues, even with utilizing sudo commands. dstarrepeater was configured and I went on to ircddbgateway. When I run sudo ircddbgateway I am presented with a popup box which states "Cannot open /var/log/opendv/irrcddbgateway.log for appending. When I click OK i am presented with "Fatal Error: Assertion failed on line 67 in file Common/Logger.cpp and function DoLog: m_file->IsOpened()
Aborted

Again this seems to be a permissions issue.

Clearly I am a novice with the Raspberry PI and Linux and I am using this as a learning experience and do not wish to cause any problem. I completely expect this to be an issue I created. Since I do not yet have my URDC hat it may be that simple. But It appears that the image my have some permission issues for user "pi". I will continue to plug away at it and want to say John has been great and responding to my direct emails. If this is an issue in the image then I will not be the only one experiencing the issue.

Thanks for all the help!

Rich, KR4PI




--
"Anything is possible if you don't know what you are talking about."
1st Law of Logic

Re: Compass image Permissions

Bob Nielsen <n7xy@...>
 

Rich,

I haven't installed Compass yet, but this should be relatively easy to resolve.

Check the ownership of the directories/files in question with the ls -al command.  In addition to the owner, the group will be shown.  You can add your user to the group and that will normally resolve these types of permission issues.  See 'man adduser' to get the syntax for doing this.

I probably should install Compass on one of my RPis to get ready for the UDRC (hopefully there are still a few left after Dayton for those of us who placed orders earlier this month).

73,
Bob, N7XY

On 5/26/16 11:23 AM, Rich KR4PI wrote:

Good afternoon and thank you for adding me to the group.

I previously posted in the Yahoo group the following:

In an effort to be prepared to plugin the URDC hat when it arrives I thought I would download the image and setup my micro SD card. Went to archive.compasslinux.org and downloaded zip file. No problems. Extracted the image and installed it on the SD card. No problem. Ethernet cable works but I cannot get the Edimax wifi dongle to work. the Pi sees it and loads the module for it. by doing lsusb it shows the wlan adapter on Bus 001 Device 004 exactly where it does in my other Pi distributions. Iwlist wlan0 scan shows the available networks. So I know the adapter is working and seeing the wireless world. The Pi and Edimax wifi adapter work great with several other distros.  

I cannot do much configuration with the Pi plugged into the ethernet cable as I do not have an HDMI monitor there. Where I have an HDMI monitor I do not have an available wired network connection. So where I can see what I am doing I have no network and where I have network I cannot see. (Could be a country song there, hi) 

I recognize this is not a NW Digital issue but I can find very little information concerning the compass distribution and what is built in, what works and what does not. I have followed several different step by step guides to get it to work all with failure. A little bit of direction would be very helpful and I would be grateful. 

John replied quickly and sent me on a path to solve my wifi connection issue. Turned out that even with using sudo commands I still was not able to change the configuration for the network settings to permit the wife adapter to work. I took ownership as user "pi" of the /etc/network/ directory and that permitted me to configure wife to work. I then had similar issues installing VNC. Finally got that working so I can remotely connect.

Today I thought I would preinstall dstarrepeater and ircddbgateway which again presented some permission issues, even with utilizing sudo commands. dstarrepeater was configured and I went on to ircddbgateway. When I run sudo ircddbgateway I am presented with a popup box which states "Cannot open /var/log/opendv/irrcddbgateway.log for appending. When I click OK i am presented with "Fatal Error: Assertion failed on line 67 in file Common/Logger.cpp and function DoLog: m_file->IsOpened() 
Aborted

Again this seems to be a permissions issue. 

Clearly I am a novice with the Raspberry PI and Linux and I am using this as a learning experience and do not wish to cause any problem. I completely expect this to be an issue I created. Since I do not yet have my URDC hat it may be that simple. But It appears that the image my have some permission issues for user "pi". I will continue to plug away at it and want to say John has been great and responding to my direct emails. If this is an issue in the image then I will not be the only one experiencing the issue. 

Thanks for all the help!

Rich, KR4PI




 


Compass Technical Information

Jeremy McDermond <mcdermj@...>
 

Just briefly so that everyone understands what “Compass” is.

Compass is just a minimally modified Raspbian distribution. By and large, whatever you use on Raspbian, will work on Compass. I use the same tools to build images as the Raspbian folks, and I use, as a base, the same kernel source as the Raspbian folks. We make minimal changes to those images when we create them. Those changes are:

* Change the hostname of the machine to “compass” rather than “raspberrypi”
* Install the Compass repository as an overlay on Raspbian
* Change the default keyboard layout and language to US English rather than The Queen’s English
* Do not install pulseaudio by default (it interferes with DStarRepeater[d]’s access to the audio device)

You can see these changes in the code in our GitHub repository for pi-gen at https://github.com/nwdigitalradio/pi-gen.

As far as the Compass packages go, we override a single major set of packages, those created by the “raspberrypi-firmware” source package. For the raspberrypi-bootloader package, we grab those from the “next” branch of the Raspberry Pi Foundation’s firmware repository at https://github.com/raspberrypi/firmware. The source for the raspberrypi-kernel package comes from our fork of the Raspberry Pi Foundation’s kernel and lives in our GitHub Repository at https://github.com/nwdigitalradio/linux. The rest of the packages are straight out of Raspbian.

The reason we have to override the raspberrypi-kernel package is that the hardware support for everything that is necessary to run the UDRC is not in the Foundation’s kernel yet. Notably, the master clock for the codec uses the “General Purpose 0” clock on the Raspberry Pi through one of the header pins. To be able to do this, we need to have the bcm2835-clk driver installed. This is in the Foundation’s kernel, but it breaks the I2S driver that the UDRC needs. We apply a patch to fix the I2S driver to properly use the clock driver. I expect this patch will make its way into Raspbian official soon. There are also some fixes to the bcm2835-clk driver that stops it from crashing the machine but shutting down clocks it’s not supposed to.

In addition, we have made some improvements ourselves to the tlv320aic32x4 driver, which drives the sound chip on the UDRC. Those are starting to be committed upstream through the ALSA folks and into the master Linux kernel, but this stuff takes time to get into the kernel in the first place, and also to filter down to the Raspbian kernel. So, we have to keep our own sources until we can get everything upstreamed. To be very clear about this, our intent is that one day in the future, we will not need a special Compass kernel package, it will all be in the upstream generic Linux kernel. We may or may not succeed, but this is certainly the goal.

I would also like to emphasize that we are in no way trying to “hide the ball” from anyone. We try to make everything possible available publicly on our GitHub account at https://github.com/nwdigitalradio. If you see something that’s not there that you’re curious about, please let us know. It may just be an oversight that we haven’t published it yet.

The only other things that Compass encompasses is extra and updated Ham Radio packages. For example, the OpenDV packages are not in upstream Raspbian or Debian. We provide those built off of my sources at https://github.com/mcdermj/OpenDV. They are currently built from the mcdermj/udrc-beta branch. Another example is fldigi, which we provide a package built off of the Debian unstable repository that is more up to date with the current source status. Our intention with these types of packages is that as Debian catches up, we’ll age out our packages.

As far as releases go, Compass currently has a “stable” and an “unstable” release. The stable release is called “alder”. The naming convention for stable releases is species of tree in alphabetical order (kinda like Ubuntu does). When we decide to increment the stable release, the next one will be called “birch.” For those who really would like to be on the bleeding edge, the unstable release is called “wilderness.” If you do decide to use wilderness packages, please know that you’ve gone of the beaten path, and there is no “Search and Rescue” service provided. If you get lost in the wilderness, NWDR provides no support unless someone has specifically told you to do so. If it breaks, you own both pieces. Please don’t ask me how to switch to wilderness, if you don’t know how to get there, you don’t belong there. Wilderness is entirely automatically built, so there is no guarantee whatsoever that the packages will even run on a machine, let alone run correctly.

I’m happy to attempt to answer any questions as long as my time allows, but hopefully this enlightens some folks as to what exactly is involved in Compass.

--
Jeremy McDermond (NH6Z)
Xenotropic Systems
mcdermj@...

Re: Compass Technical Information

Duane Angles
 

Jeremy, this is the error message I get:

Fatal Error: Assertion failed on line 277 in file Common/SerialDataController.cpp and function CserialDataController: !device.IsEmpty().

Duane Angles
AA5KD

-----Original Message-----
From: udrc@nw-digital-radio.groups.io [mailto:udrc@nw-digital-radio.groups.io] On Behalf Of Jeremy McDermond
Sent: Thursday, May 26, 2016 2:59 PM
To: udrc@nw-digital-radio.groups.io
Subject: [udrc] Compass Technical Information

Just briefly so that everyone understands what “Compass” is.

Compass is just a minimally modified Raspbian distribution. By and large, whatever you use on Raspbian, will work on Compass. I use the same tools to build images as the Raspbian folks, and I use, as a base, the same kernel source as the Raspbian folks. We make minimal changes to those images when we create them. Those changes are:

* Change the hostname of the machine to “compass” rather than “raspberrypi”
* Install the Compass repository as an overlay on Raspbian
* Change the default keyboard layout and language to US English rather than The Queen’s English
* Do not install pulseaudio by default (it interferes with DStarRepeater[d]’s access to the audio device)

You can see these changes in the code in our GitHub repository for pi-gen at https://github.com/nwdigitalradio/pi-gen.

As far as the Compass packages go, we override a single major set of packages, those created by the “raspberrypi-firmware” source package. For the raspberrypi-bootloader package, we grab those from the “next” branch of the Raspberry Pi Foundation’s firmware repository at https://github.com/raspberrypi/firmware. The source for the raspberrypi-kernel package comes from our fork of the Raspberry Pi Foundation’s kernel and lives in our GitHub Repository at https://github.com/nwdigitalradio/linux. The rest of the packages are straight out of Raspbian.

The reason we have to override the raspberrypi-kernel package is that the hardware support for everything that is necessary to run the UDRC is not in the Foundation’s kernel yet. Notably, the master clock for the codec uses the “General Purpose 0” clock on the Raspberry Pi through one of the header pins. To be able to do this, we need to have the bcm2835-clk driver installed. This is in the Foundation’s kernel, but it breaks the I2S driver that the UDRC needs. We apply a patch to fix the I2S driver to properly use the clock driver. I expect this patch will make its way into Raspbian official soon. There are also some fixes to the bcm2835-clk driver that stops it from crashing the machine but shutting down clocks it’s not supposed to.

In addition, we have made some improvements ourselves to the tlv320aic32x4 driver, which drives the sound chip on the UDRC. Those are starting to be committed upstream through the ALSA folks and into the master Linux kernel, but this stuff takes time to get into the kernel in the first place, and also to filter down to the Raspbian kernel. So, we have to keep our own sources until we can get everything upstreamed. To be very clear about this, our intent is that one day in the future, we will not need a special Compass kernel package, it will all be in the upstream generic Linux kernel. We may or may not succeed, but this is certainly the goal.

I would also like to emphasize that we are in no way trying to “hide the ball” from anyone. We try to make everything possible available publicly on our GitHub account at https://github.com/nwdigitalradio. If you see something that’s not there that you’re curious about, please let us know. It may just be an oversight that we haven’t published it yet.

The only other things that Compass encompasses is extra and updated Ham Radio packages. For example, the OpenDV packages are not in upstream Raspbian or Debian. We provide those built off of my sources at https://github.com/mcdermj/OpenDV. They are currently built from the mcdermj/udrc-beta branch. Another example is fldigi, which we provide a package built off of the Debian unstable repository that is more up to date with the current source status. Our intention with these types of packages is that as Debian catches up, we’ll age out our packages.

As far as releases go, Compass currently has a “stable” and an “unstable” release. The stable release is called “alder”. The naming convention for stable releases is species of tree in alphabetical order (kinda like Ubuntu does). When we decide to increment the stable release, the next one will be called “birch.” For those who really would like to be on the bleeding edge, the unstable release is called “wilderness.” If you do decide to use wilderness packages, please know that you’ve gone of the beaten path, and there is no “Search and Rescue” service provided. If you get lost in the wilderness, NWDR provides no support unless someone has specifically told you to do so. If it breaks, you own both pieces. Please don’t ask me how to switch to wilderness, if you don’t know how to get there, you don’t belong there. Wilderness is entirely automatically built, so there is no guarantee whatsoever that the packages will even run on a machine, let alone run correctly.

I’m happy to attempt to answer any questions as long as my time allows, but hopefully this enlightens some folks as to what exactly is involved in Compass.

--
Jeremy McDermond (NH6Z)
Xenotropic Systems
mcdermj@...

Re: Compass Technical Information

 


Duane

Did you copy in the dstarrepeater_1 file to /etc/opendv  before starting dstarrepeater? 

Re: Compass Technical Information

Duane Angles
 

John, yes there is a dstarrepeater_l.log but it is zero length.

 

Duane Angles

AA5KD

 

From: udrc@nw-digital-radio.groups.io [mailto:udrc@nw-digital-radio.groups.io] On Behalf Of John Hays
Sent: Thursday, May 26, 2016 5:40 PM
To: udrc@nw-digital-radio.groups.io
Subject: Re: [udrc] Compass Technical Information

 

 

Duane

Did you copy in the dstarrepeater_1 file to /etc/opendv  before starting dstarrepeater? 

Re: Compass Technical Information

Duane Angles
 

My bad, yes the dstarrepeater_l file is in etc/opendv.

 

Duane Angles

AA5KD

 

From: udrc@nw-digital-radio.groups.io [mailto:udrc@nw-digital-radio.groups.io] On Behalf Of John Hays
Sent: Thursday, May 26, 2016 5:40 PM
To: udrc@nw-digital-radio.groups.io
Subject: Re: [udrc] Compass Technical Information

 

 

Duane

Did you copy in the dstarrepeater_1 file to /etc/opendv  before starting dstarrepeater? 

Re: Compass Technical Information

 

Look inside the file /etc/opendv/dstarrepeater_1 and make sure it has these two values

controllerType=UDRC
serialConfig=2


Also, how are you starting up dstarrepeater/dstarrepeaterd?

Send us

ls -al /etc/opendv
ls -al /var/log/opendv
ls -al /tmp


On Thu, May 26, 2016 at 4:04 PM, Duane Angles <dangles1@...> wrote:

My bad, yes the dstarrepeater_l file is in etc/opendv.

 

Duane Angles

AA5KD

 




John D. Hays
K7VE

PO Box 1223, Edmonds, WA 98020-1223 
  

Re: Compass Technical Information

Jeremy McDermond <mcdermj@...>
 

On May 26, 2016, at 4:04 PM, Duane Angles <dangles1@...> wrote:

My bad, yes the dstarrepeater_l file is in etc/opendv.
Make sure you confirm that the last character of the file is the number one (1) not the letter ell (l or L).

Duane Angles
AA5KD
--
Jeremy McDermond (NH6Z)
Xenotropic Systems
mcdermj@...

Re: Compass Technical Information

Duane Angles
 

It is the number one. I have it working in C4FM and Analog but cannot get it
to TX in DStar.

Duane Angles
AA5KD

-----Original Message-----
From: udrc@nw-digital-radio.groups.io
[mailto:udrc@nw-digital-radio.groups.io] On Behalf Of Jeremy McDermond
Sent: Thursday, May 26, 2016 8:22 PM
To: udrc@nw-digital-radio.groups.io
Subject: Re: [udrc] Compass Technical Information


On May 26, 2016, at 4:04 PM, Duane Angles <dangles1@...> wrote:

My bad, yes the dstarrepeater_l file is in etc/opendv.
Make sure you confirm that the last character of the file is the number one
(1) not the letter ell (l or L).

Duane Angles
AA5KD
--
Jeremy McDermond (NH6Z)
Xenotropic Systems
mcdermj@...

Re: Compass Technical Information

 

Duane,

Have you been able to get dstarrepeater or dstarrepeaterd to run?

Is your repeater on 2m or 70cm 

Is your repeater in 'Remote' mode?

Does the DR-1X go to Auto Normal / Auto Normal (Red) when dstarrepeater starts?

tail -f /var/log/opendv/dstarrepeater_1

Key up on D-STAR on the repeater.

Does the DR-1X display change to Fixed / FM Fixed/FM (Yellow)?

Does anything show in the log as you key up?

What is the repeater callsign and do you have ircddbgateway running and registered with ircddb?


Schematics/hotspot usage

Stephen Brown
 

Hi guys... thanks again for the great product you built being the UDRC :) I enjoyed being able to stop by your booth at Dayton and walked away with one along with a ThumbDV for another project. 

Are there any schematics available yet for the board? My intended use for this board is that of a hotspot off the mini-din jack. The best I could tell with an multimeter is that it appears to be wired in parallel, but wasn't sure if there was any software switches etc in any of the config files that have to be set? 

Also.. being completely new to D-Star, are there any audio adjustment utilities or methods to get the digital voice encode/decode set properly with my intended target radio? I'll be using a Yaesu FT-817ND to start with, may move over to a dedicated mobile (or pair if I go full duplex) which will most likely be Motorola Maxtrac's or similar. 

73
Stephen
K1LNX

GMSK modem

Ed Ingber WA6AXX
 

Is the GMSK modem implemented in software in the Raspberry Pi? How does its performance compare to the CMX589 GMSK modem chip that's used in the DV MEGA, for example?

73,

Ed

Re: Schematics/hotspot usage

 

Hi Stephen,

At the top of the UDRC page there is a link to the DataSheet, which has the schematic and pinout table.

I’ll let others weigh in on the alsa mixer settings.

Bryan K7UDR

On May 27, 2016, at 6:12 AM, Stephen Brown <k1lnx@...> wrote:

Hi guys... thanks again for the great product you built being the UDRC :) I enjoyed being able to stop by your booth at Dayton and walked away with one along with a ThumbDV for another project. 

Are there any schematics available yet for the board? My intended use for this board is that of a hotspot off the mini-din jack. The best I could tell with an multimeter is that it appears to be wired in parallel, but wasn't sure if there was any software switches etc in any of the config files that have to be set? 

Also.. being completely new to D-Star, are there any audio adjustment utilities or methods to get the digital voice encode/decode set properly with my intended target radio? I'll be using a Yaesu FT-817ND to start with, may move over to a dedicated mobile (or pair if I go full duplex) which will most likely be Motorola Maxtrac's or similar. 

73
Stephen
K1LNX


Re: Tell Us About Your UDRC

 

My plan for implementing the UDRC is primarily as a hotspot on my IC7100. I will have to build a cable or purchase the 13 to 6 pin Yaesu cable to utilize my FTM-100 for the hotspot and ax.25 WL2K. Without a Dstar repeater in Fort Myers, FL, I also want to experiment with converting one of the local ARES DR-1X repeaters into a Dstar repeater with access to the reflector system. With successful testing I believe ARES will purchase a couple UDRCs for DR-1X application and for AX.25 packet applications in ARES go boxes.

Thanks 

Rich KR4PI