Date   
Re: DRAWS GPIO/Accessory connector #accessory #draws #adc

Ryan Reid
 

Maybe I'm missing something, but Sensors is not seeing it...
The hat is installed, and connected through the +12v Input.

root@compass:~# sensors
No sensors found!
Make sure you loaded all the kernel drivers you need.
Try sensors-detect to find out which these are.
root@compass:~#  sensors-detect
# sensors-detect revision 6284 (2015-05-31 14:00:33 +0200)
# Kernel: 4.14.79-v7+ armv7l
# Processor: ARMv7 Processor rev 4 (v7l) (//)
 
This program will help you determine which kernel modules you need
to load to use lm_sensors most effectively. It is generally safe
and recommended to accept the default answers to all questions,
unless you know what you're doing.
 
Some south bridges, CPUs or memory controllers contain embedded sensors.
Do you want to scan for them? This is totally safe. (YES/no): yes
modprobe: FATAL: Module cpuid not found in directory /lib/modules/4.14.79-v7+
Failed to load module cpuid.
Silicon Integrated Systems SIS5595...                       No
VIA VT82C686 Integrated Sensors...                          No
VIA VT8231 Integrated Sensors...                            No
AMD K8 thermal sensors...                                   No
AMD Family 10h thermal sensors...                           No
AMD Family 11h thermal sensors...                           No
AMD Family 12h and 14h thermal sensors...                   No
AMD Family 15h thermal sensors...                           No
AMD Family 16h thermal sensors...                           No
AMD Family 15h power sensors...                             No
AMD Family 16h power sensors...                             No
Intel digital thermal sensor...                             No
Intel AMB FB-DIMM thermal sensor...                         No
Intel 5500/5520/X58 thermal sensor...                       No
VIA C7 thermal sensor...                                    No
VIA Nano thermal sensor...                                  No
 
Lastly, we can probe the I2C/SMBus adapters for connected hardware
monitoring devices. This is the most risky part, and while it works
reasonably well on most systems, it has been reported to cause trouble
on some systems.
Do you want to probe the I2C/SMBus adapters now? (YES/no): yes
Sorry, no supported PCI bus adapters found.
 
Next adapter: bcm2835 I2C adapter (i2c-1)
Do you want to scan it? (YES/no/selectively): yes
Client found at address 0x18
Handled by driver `tlv320aic32x4_i2c' (already loaded), chip type `tlv320aic32x4'
    (note: this is probably NOT a sensor chip!)
Client found at address 0x48
Probing for `National Semiconductor LM75'...                No
Probing for `National Semiconductor LM75A'...               No
Probing for `Dallas Semiconductor DS75'...                  No
Probing for `National Semiconductor LM77'...                No
Probing for `Analog Devices ADT7410/ADT7420'...             No
Probing for `Analog Devices ADT7411'...                     No
Probing for `Maxim MAX6642'...                              No
Probing for `Texas Instruments TMP435'...                   No
Probing for `National Semiconductor LM73'...                No
Probing for `National Semiconductor LM92'...                No
Probing for `National Semiconductor LM76'...                No
Probing for `Maxim MAX6633/MAX6634/MAX6635'...              No
Probing for `NXP/Philips SA56004'...                        No
Probing for `SMSC EMC1023'...                               No
Probing for `SMSC EMC1043'...                               No
Probing for `SMSC EMC1053'...                               No
Probing for `SMSC EMC1063'...                               No
Client found at address 0x50
Probing for `Analog Devices ADM1033'...                     No
Probing for `Analog Devices ADM1034'...                     No
Probing for `SPD EEPROM'...                                 No
Probing for `EDID EEPROM'...                                No
 
Sorry, no sensors were detected.
Either your system has no sensors, or they are not supported, or
they are connected to an I2C or SMBus adapter that is not
supported. If you find out what chips are on your board, check
http://www.lm-sensors.org/wiki/Devices for driver status.
root@compass:~# uname -a
Linux compass 4.14.79-v7+ #1159 SMP Sun Nov 4 17:50:20 GMT 2018 armv7l GNU/Linux

Re: DRAWS GPIO/Accessory connector #accessory #draws #adc

Ryan Reid
 

Answered my own question... forgot to change dtoverlay from udrc to draws.

Re: DRAWS GPIO/Accessory connector #accessory #draws #adc

 

Try the command

sensors

Instead of sensors-detect


On Mon, Dec 17, 2018 at 2:50 PM Ryan Reid <blupanthr2@...> wrote:
Maybe I'm missing something, but Sensors is not seeing it...
The hat is installed, and connected through the +12v Input.

root@compass:~# sensors
No sensors found!
Make sure you loaded all the kernel drivers you need.
Try sensors-detect to find out which these are.
root@compass:~#  sensors-detect
# sensors-detect revision 6284 (2015-05-31 14:00:33 +0200)
# Kernel: 4.14.79-v7+ armv7l
# Processor: ARMv7 Processor rev 4 (v7l) (//)
 
This program will help you determine which kernel modules you need
to load to use lm_sensors most effectively. It is generally safe
and recommended to accept the default answers to all questions,
unless you know what you're doing.
 
Some south bridges, CPUs or memory controllers contain embedded sensors.
Do you want to scan for them? This is totally safe. (YES/no): yes
modprobe: FATAL: Module cpuid not found in directory /lib/modules/4.14.79-v7+
Failed to load module cpuid.
Silicon Integrated Systems SIS5595...                       No
VIA VT82C686 Integrated Sensors...                          No
VIA VT8231 Integrated Sensors...                            No
AMD K8 thermal sensors...                                   No
AMD Family 10h thermal sensors...                           No
AMD Family 11h thermal sensors...                           No
AMD Family 12h and 14h thermal sensors...                   No
AMD Family 15h thermal sensors...                           No
AMD Family 16h thermal sensors...                           No
AMD Family 15h power sensors...                             No
AMD Family 16h power sensors...                             No
Intel digital thermal sensor...                             No
Intel AMB FB-DIMM thermal sensor...                         No
Intel 5500/5520/X58 thermal sensor...                       No
VIA C7 thermal sensor...                                    No
VIA Nano thermal sensor...                                  No
 
Lastly, we can probe the I2C/SMBus adapters for connected hardware
monitoring devices. This is the most risky part, and while it works
reasonably well on most systems, it has been reported to cause trouble
on some systems.
Do you want to probe the I2C/SMBus adapters now? (YES/no): yes
Sorry, no supported PCI bus adapters found.
 
Next adapter: bcm2835 I2C adapter (i2c-1)
Do you want to scan it? (YES/no/selectively): yes
Client found at address 0x18
Handled by driver `tlv320aic32x4_i2c' (already loaded), chip type `tlv320aic32x4'
    (note: this is probably NOT a sensor chip!)
Client found at address 0x48
Probing for `National Semiconductor LM75'...                No
Probing for `National Semiconductor LM75A'...               No
Probing for `Dallas Semiconductor DS75'...                  No
Probing for `National Semiconductor LM77'...                No
Probing for `Analog Devices ADT7410/ADT7420'...             No
Probing for `Analog Devices ADT7411'...                     No
Probing for `Maxim MAX6642'...                              No
Probing for `Texas Instruments TMP435'...                   No
Probing for `National Semiconductor LM73'...                No
Probing for `National Semiconductor LM92'...                No
Probing for `National Semiconductor LM76'...                No
Probing for `Maxim MAX6633/MAX6634/MAX6635'...              No
Probing for `NXP/Philips SA56004'...                        No
Probing for `SMSC EMC1023'...                               No
Probing for `SMSC EMC1043'...                               No
Probing for `SMSC EMC1053'...                               No
Probing for `SMSC EMC1063'...                               No
Client found at address 0x50
Probing for `Analog Devices ADM1033'...                     No
Probing for `Analog Devices ADM1034'...                     No
Probing for `SPD EEPROM'...                                 No
Probing for `EDID EEPROM'...                                No
 
Sorry, no sensors were detected.
Either your system has no sensors, or they are not supported, or
they are connected to an I2C or SMBus adapter that is not
supported. If you find out what chips are on your board, check
root@compass:~# uname -a
Linux compass 4.14.79-v7+ #1159 SMP Sun Nov 4 17:50:20 GMT 2018 armv7l GNU/Linux



--


John D. Hays
Edmonds, WA
K7VE

   

Re: DRAWS GPIO/Accessory connector #accessory #draws #adc

Basil Gunn
 

Answered my own question... forgot to change dtoverlayfrom udrc to draws.
If you use the current beta image for draws the dtoverlay is set up properly.
http://nwdig.net/downloads/

/Basil

Re: DRAWS GPIO/Accessory connector #accessory #draws #adc

Ryan Reid
 

Is there a changelog between the beta image, and modifying the last Compass release?  Wondering if it is worth overwriting any settings/other modifications I have done so far.

Ryan
K1BLU


On Mon, Dec 17, 2018 at 4:44 PM Basil Gunn <basil@...> wrote:

> Answered my own question... forgot to change dtoverlayfrom udrc to draws.

If you use the current beta image for draws the dtoverlay is set up properly.
http://nwdig.net/downloads/

/Basil



Re: DRAWS Technical Documents

ac8dg@...
 

On this schematic,  the pictorial of the 6 pin mini-din JL/JR Data Ports shows a pin layout
that very different then the 'conventional' pin number assignments.  The descriptions
seem to match the standard radio data ports of Icom/Yeasu/Alinco,  Can this be clarified.

Re: DRAWS Technical Documents

 

That is correct, they match the Icon/Yaesu/Kenwood pinout. Alinco uses a DB-9 so you have to modify the Cable.

Bryan K7UDR

Re: DRAWS Image

Basil Gunn
 

The DRAWS image starts with a compass image and adds other HAM programs.

See "Table of Installed Programs" at this link for a list of those programs:
https://github.com/nwdigitalradio/n7nix/blob/master/config/IMAGE_README.md
/Basil

Ryan Reid <@blupanthr2> writes:

Is there a changelog between the beta image, and modifying the last Compass
release? Wondering if it is worth overwriting any settings/other
modifications I have done so far.

Ryan
K1BLU


On Mon, Dec 17, 2018 at 4:44 PM Basil Gunn <@basil860> wrote:


Answered my own question... forgot to change dtoverlayfrom udrc to draws.
If you use the current beta image for draws the dtoverlay is set up
properly.
http://nwdig.net/downloads/
/Basil

Re: DRAWS GPIO/Accessory connector #accessory #draws #adc

KB5ZUR
 


I can't seem to get the sensor readings to work. says" command not found". tried that and lm-sensors command as well, same thing. Do I need to install something? What am I missing?
I'm using this version of  compass:
Linux compass 4.14.79-v7+ #1159 SMP Sun Nov 4 17:50:20 GMT 2018 armv7l GNU/Linux
debian_version 9.6
This is I think the first beta image released. 
Also, what is the range of the ADC's? I would like to read two 0-5VDC signals from my SWR bridge from Kits and Parts. Are the inputs isolated?
 

Re: DRAWS GPIO/Accessory connector #accessory #draws #adc

 

sudo apt-get install lm-sensors

sensors

On Wed, Dec 19, 2018, 08:42 KB5ZUR <kb5zur@... wrote:

I can't seem to get the sensor readings to work. says" command not found". tried that and lm-sensors command as well, same thing. Do I need to install something? What am I missing?
I'm using this version of  compass:
Linux compass 4.14.79-v7+ #1159 SMP Sun Nov 4 17:50:20 GMT 2018 armv7l GNU/Linux
debian_version 9.6
This is I think the first beta image released. 
Also, what is the range of the ADC's? I would like to read two 0-5VDC signals from my SWR bridge from Kits and Parts. Are the inputs isolated?
 

Re: DRAWS GPIO/Accessory connector #accessory #draws #adc

 

All about the Ain inputs on the accessory connector.

Each input connects to a Pi IO Pin and an ADC input. Clearly you can’t use both. There is also an ESD protection diode and 33ohm series resistor to reduce the chance of damaging the input.

To use the ADC set the corresponding GPIO to input with pulldown.

The max input is 3.3V so use a resistor divider above that voltage. The PS Input is scaled with 48.7k and 10.0k 1% this gives a range of:

0-19.7V

The actual installed ADC is a TI I2C 4CH 12Bit Device It is SW compatible with the ads1015 with a few less features.

Datasheet:


The resistor values are set into SW so the sensor command displays the voltage correctly.

pi@compass:~ $ sensors
ads1015-i2c-1-48
Adapter: bcm2835 I2C adapter
User ADC Differential:  +0.00 V  
+12V:                  +13.77 V  
User ADC 1:             +0.00 V  
User ADC 2:             +0.00 V  

If you put 10.0k and 10.0k in your signal path, you can read sensors and multiply User ADC by 2.

It is possible, but not trivial, to change the file so it reads directly with your values. This will be documented in a future APP Note.

Bryan K7UDR


fldigi with DRAWS #draws #fldigi

Steve
 

Symptom: After entering text and clicking the "TX" button, fldigi looks like it is transmitting (text turns red and is moved to the upper window), but the transmitter does not come on.

Details below. What am I missing?

Thanks,
Steve

- - - - -

Hardware:
• Radio: Kenwood TM-V71A {known to be working with a USB connected "brand X" external sound card, both with a RPi and a debian stretch system}
• Cable: As supplied with the DRAWS board
• Connected: First to the 6-pin port adjacent to the GPS antenna, then to the other 6-pin port

Images tried:
http://archive.compasslinux.org/images/image_2018-11-18-compass.zip {fldigi built from source}
http://nwdig.net/downloads/draws_beta5.zip {fldigi pre-installed}

Using minicom, data is seen on /dev/ttySC0 from the GPS, but nothing on /dev/ttySC1

Setup parameter debugging changes:
• Configuration Audio -> Devices {installation default}
• Configuration Audio -> Devices -> PortAudio {checked with Capture and Playback left to default}
• Configuration Audio -> Devices -> PortAudio {checked with Capture and Playback both set to "udrc: - (hw:0,0)"}

- - - - -

locked Using the discussion topics #support

 


Hi Everyone.

First of all thank you for your testing, observations, suggestions, and requests for help via the established groups on groups.io


This allows the folks at NW Digital Radio and others to answer once and everyone can benefit.

A few important requests:
  1. Use the right sub-group for you topic (e.g. draws and udrc to https://nw-digital-radio.groups.io/g/udrc and so forth)
  2. Use subject line hashtags, e.g. #fldigi for topics about fldigi. If you use the web interface you can click on hashtags in the subject and see all postings related to that topic, including previous conversations.  Also you can search them in your email.  This helps with organizing information and doing your research on a topic.
  3. Place one and only only one issue per topic, with  a matching hashtag, and create separate topics for each issue so that a thread can be established for a topic/issue.  E.g. don't place an AX.25 and D-STAR issue in the same topic, unless it is specific to an interaction of the two (rare), create a topic for each.
  4. Be thorough in your description, e.g. radio, which port, which application, configuration, etc. Others can't figure out what is going on without sufficient information.
Again, thank you for using NW Digital Radio products and services and your valuable insights.

--


John D. Hays
Director

  

locked Case #draws #case

Todd
 

Any idea when a case will be available? I don't see anything on the shopping site about it. Price? 
Todd
AL7PX

locked Re: Case #draws #case

 

The case will be available after the first of the year.  Pricing and availability will be announced once the manufacturing run is initiated.

Follow-ups in UDRC subgroup.

Re: DRAWS Image

Julian OH8STN <julian@...>
 

Would love to see this table on the local wiki, rather than driving users to github. Is that possible?
73
Julian oh8stn

Re: MMDVM & UDRC

Dan Porter (AI2M)
 

Hi Anna,

I noticed several recent GitHub updates. Am I missing something obvious or are there still some things to be worked out?

When I start MMDVM-UDRC it appears ok…

pi@udrc:~/MMDVM-UDRC $ sudo ./MMDVM 
Virtual pty: /dev/pts/2 <> /dev/ttyMMDVM0
Opened hw:CARD=udrc,DEV=0 hw:CARD=udrc,DEV=0 Rate 48000

But MMDVMHost fails like this:

pi@udrc:~/MMDVMHost $ sudo ./MMDVMHost MMDVM.ini
I: 2018-12-29 19:38:11.296 This software is for use on amateur radio networks only,
I: 2018-12-29 19:38:11.297 it is to be used for educational purposes only. Its use on
I: 2018-12-29 19:38:11.297 commercial networks is strictly prohibited.
I: 2018-12-29 19:38:11.297 Copyright(C) 2015-2018 by Jonathan Naylor, G4KLX and others
M: 2018-12-29 19:38:11.297 MMDVMHost-20180916 is starting
M: 2018-12-29 19:38:11.297 Built 11:47:45 Dec 29 2018 (GitID #5de3bee)
I: 2018-12-29 19:38:11.298 General Parameters
I: 2018-12-29 19:38:11.298     Callsign: AI2M
I: 2018-12-29 19:38:11.298     Id: xxxxxxx04
I: 2018-12-29 19:38:11.298     Duplex: no
I: 2018-12-29 19:38:11.298     Timeout: 180s
I: 2018-12-29 19:38:11.298     D-Star: enabled
I: 2018-12-29 19:38:11.299     DMR: disabled
I: 2018-12-29 19:38:11.299     YSF: disabled
I: 2018-12-29 19:38:11.299     P25: disabled
I: 2018-12-29 19:38:11.299     NXDN: disabled
I: 2018-12-29 19:38:11.299     POCSAG: disabled
I: 2018-12-29 19:38:11.299 Modem Parameters
I: 2018-12-29 19:38:11.300     Port: /dev/ttyMMDVM0
I: 2018-12-29 19:38:11.300     Protocol: uart
I: 2018-12-29 19:38:11.300     RX Invert: no
I: 2018-12-29 19:38:11.300     TX Invert: yes
I: 2018-12-29 19:38:11.300     PTT Invert: no
I: 2018-12-29 19:38:11.300     TX Delay: 100ms
I: 2018-12-29 19:38:11.300     RX Offset: 0Hz
I: 2018-12-29 19:38:11.301     TX Offset: 0Hz
I: 2018-12-29 19:38:11.301     RX DC Offset: 0
I: 2018-12-29 19:38:11.301     TX DC Offset: 0
I: 2018-12-29 19:38:11.301     RF Level: 100.0%
I: 2018-12-29 19:38:11.301     DMR Delay: 0 (0.0ms)
I: 2018-12-29 19:38:11.301     RX Level: 50.0%
I: 2018-12-29 19:38:11.301     CW Id TX Level: 50.0%
I: 2018-12-29 19:38:11.301     D-Star TX Level: 50.0%
I: 2018-12-29 19:38:11.301     DMR TX Level: 50.0%
I: 2018-12-29 19:38:11.302     YSF TX Level: 50.0%
I: 2018-12-29 19:38:11.302     P25 TX Level: 50.0%
I: 2018-12-29 19:38:11.302     NXDN TX Level: 50.0%
I: 2018-12-29 19:38:11.302     POCSAG TX Level: 50.0%
I: 2018-12-29 19:38:11.302     RX Frequency: 145650000Hz (145650000Hz)
I: 2018-12-29 19:38:11.302     TX Frequency: 146650000Hz (146650000Hz)
M: 2018-12-29 19:38:11.303 Opening the MMDVM
E: 2018-12-29 19:38:11.303 Cannot get the control attributes for /dev/ttyMMDVM0

Followed by this in MMDVM-UDRC:

Slave disconnected, reopening master
Virtual pty: /dev/pts/2 <> /dev/ttyMMDVM0

This is on a working DStarRepeater system with the dstarrepeaterd service disabled.

I’m just fooling around with it in my spare time out of curiosity. I don’t have a real need for it otherwise.

I’ll admit I don’t understand the Pseudo TTY part very well.

Thanks,
Dan - AI2M

On 7 Dec 2018, at 1:01, Annaliese McDermond wrote:

Dan --

Because I’m trying to get my repeater up and running again, and would like to use MMDVM-UDRC to do so, I’ve been doing some work on getting MMDVM-UDRC to work. My code is in the nwdigitalradio github account at:

https://github.com/nwdigitalradio/MMDVM-UDRC

You’re welcome to play with it with the understanding that it’s development code, may not work at all. I’m getting close to having things possibly working acceptably.

An issue you’ll have to deal with is that mmdvm-udrc expects a 24000 sample rate. The UDRC hardware doesn’t support this and if you try to use hw:CARD=udrc,DEV=0 it will fail complaining on not being able to send sample rate. You might try using plughw:CARD=udrc,DEV=0 instead. I’m using a custom asound.conf to support it.

More as I get things worked out.

--
Annaliese McDermond (NH6Z)
nh6z@...

On Dec 6, 2018, at 4:51 AM, Dan Porter (AI2M) groups@... wrote:

Hi Rich,

Did you eventually manage to get it working?
I was thinking of trying again with my UDRC.

73, Dan - AI2M

On Jul 6, 2018, at 3:05 PM, Rich KR4PI rich.schnieders@... wrote:

Thanks John, that helped but there were still a few errors along the way:

g++ -g -O3 -Wall -std=c++0x -pthread -c -o Biquad.o Biquad.cpp
g++ -g -O3 -Wall -std=c++0x -pthread -c -o CalDMR.o CalDMR.cpp
g++ -g -O3 -Wall -std=c++0x -pthread -c -o CalDStarRX.o CalDStarRX.cpp
g++ -g -O3 -Wall -std=c++0x -pthread -c -o CalDStarTX.o CalDStarTX.cpp
g++ -g -O3 -Wall -std=c++0x -pthread -c -o CalNXDN.o CalNXDN.cpp
g++ -g -O3 -Wall -std=c++0x -pthread -c -o CalP25.o CalP25.cpp
g++ -g -O3 -Wall -std=c++0x -pthread -c -o CWIdTX.o CWIdTX.cpp
g++ -g -O3 -Wall -std=c++0x -pthread -c -o DMRDMORX.o DMRDMORX.cpp
g++ -g -O3 -Wall -std=c++0x -pthread -c -o DMRDMOTX.o DMRDMOTX.cpp
g++ -g -O3 -Wall -std=c++0x -pthread -c -o DMRSlotType.o DMRSlotType.cpp
g++ -g -O3 -Wall -std=c++0x -pthread -c -o DStarRX.o DStarRX.cpp
g++ -g -O3 -Wall -std=c++0x -pthread -c -o DStarTX.o DStarTX.cpp
DStarTX.cpp: In member function ‘void CDStarTX::txHeader(const uint8_t*, uint8_t*) const’:
DStarTX.cpp:382:7: warning: this ‘if’ clause does not guard... [-Wmisleading-indentation]
if (d & 0x08U)
^~
DStarTX.cpp:384:9: note: ...this statement, but the latter is misleadingly indented as if it is guarded by the ‘if’
i++;
^
g++ -g -O3 -Wall -std=c++0x -pthread -c -o FIR.o FIR.cpp
g++ -g -O3 -Wall -std=c++0x -pthread -c -o FIRInterpolator.o FIRInterpolator.cpp
g++ -g -O3 -Wall -std=c++0x -pthread -c -o IO.o IO.cpp
g++ -g -O3 -Wall -std=c++0x -pthread -c -o IOUDRC.o IOUDRC.cpp
g++ -g -O3 -Wall -std=c++0x -pthread -c -o MMDVM.o MMDVM.cpp
g++ -g -O3 -Wall -std=c++0x -pthread -c -o NXDNRX.o NXDNRX.cpp
g++ -g -O3 -Wall -std=c++0x -pthread -c -o NXDNTX.o NXDNTX.cpp
g++ -g -O3 -Wall -std=c++0x -pthread -c -o P25RX.o P25RX.cpp
g++ -g -O3 -Wall -std=c++0x -pthread -c -o P25TX.o P25TX.cpp
g++ -g -O3 -Wall -std=c++0x -pthread -c -o POCSAGTX.o POCSAGTX.cpp
g++ -g -O3 -Wall -std=c++0x -pthread -c -o SampleRB.o SampleRB.cpp
g++ -g -O3 -Wall -std=c++0x -pthread -c -o SerialController.o SerialController.cpp
g++ -g -O3 -Wall -std=c++0x -pthread -c -o SerialPort.o SerialPort.cpp
g++ -g -O3 -Wall -std=c++0x -pthread -c -o SerialRB.o SerialRB.cpp
g++ -g -O3 -Wall -std=c++0x -pthread -c -o SoundCardReaderWriter.o SoundCardReaderWriter.cpp
SoundCardReaderWriter.cpp: In member function ‘virtual void CSoundCardWriter::entry()’:
SoundCardReaderWriter.cpp:479:85: warning: comparison between signed and unsigned integer expressions [-Wsign-compare]
le ((ret = ::snd_pcm_writei(m_handle, m_samples + offset, nSamples - offset)) != (nSamples - offset)) {
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~
g++ -g -O3 -Wall -std=c++0x -pthread -c -o Thread.o Thread.cpp
g++ -g -O3 -Wall -std=c++0x -pthread -c -o Utils.o Utils.cpp
g++ -g -O3 -Wall -std=c++0x -pthread -c -o YSFRX.o YSFRX.cpp
g++ -g -O3 -Wall -std=c++0x -pthread -c -o YSFTX.o YSFTX.cpp
g++ Biquad.o CalDMR.o CalDStarRX.o CalDStarTX.o CalNXDN.o CalP25.o CWIdTX.o DMRDMORX.o DMRDMOTX.o DMRSlotType.o DStarRX.o DStarTX.o FIR.o FIRInterpolator.o IO.o IOUDRC.o MMDVM.o NXDNRX.o NXDNTX.o P25RX.o P25TX.o POCSAGTX.o SampleRB.o SerialController.o SerialPort.o SerialRB.o SoundCardReaderWriter.o Thread.o Utils.o YSFRX.o YSFTX.o -g -lpthread -lasound -lwiringPi -o MMDVM

it did complete the compile. When I attempt ./MMDVM is receive the following:

Link does not exist: /dev/pts/1 <> ttyMMDVM0
Error creating symlink from /dev/pts/1 to ttyMMDVM0
Unable to open serial port on vpty: ttyMMDVM0

I am assuming this indicates that it is not properly configured for the UDRC. That is what I will be exploring next.

Thanks for the help
Rich, KR4PI

Re: MMDVM & UDRC

Annaliese McDermond
 

Dan --

I’m still working on the code to get things running, but I’m not quite there yet. I’ve gotten sidetracked by some DRAWS issues that I’m running down for the team. Thanks for trying things out, though, it’s nice to have some folks to test and see if things are running correctly.

--
Annaliese McDermond (NH6Z)
nh6z@...

On Dec 29, 2018, at 12:10 PM, Dan Porter (AI2M) <groups@...> wrote:

Hi Anna,

I noticed several recent GitHub updates. Am I missing something obvious or are there still some things to be worked out?

When I start MMDVM-UDRC it appears ok…

pi@udrc:~/MMDVM-UDRC $ sudo ./MMDVM
Virtual pty: /dev/pts/2 <> /dev/ttyMMDVM0
Opened hw:CARD=udrc,DEV=0 hw:CARD=udrc,DEV=0 Rate 48000

But MMDVMHost fails like this:

pi@udrc:~/MMDVMHost $ sudo ./MMDVMHost MMDVM.ini
I: 2018-12-29 19:38:11.296 This software is for use on amateur radio networks only,
I: 2018-12-29 19:38:11.297 it is to be used for educational purposes only. Its use on
I: 2018-12-29 19:38:11.297 commercial networks is strictly prohibited.
I: 2018-12-29 19:38:11.297 Copyright(C) 2015-2018 by Jonathan Naylor, G4KLX and others
M: 2018-12-29 19:38:11.297 MMDVMHost-20180916 is starting
M: 2018-12-29 19:38:11.297 Built 11:47:45 Dec 29 2018 (GitID #5de3bee)
I: 2018-12-29 19:38:11.298 General Parameters
I: 2018-12-29 19:38:11.298 Callsign: AI2M
I: 2018-12-29 19:38:11.298 Id: xxxxxxx04
I: 2018-12-29 19:38:11.298 Duplex: no
I: 2018-12-29 19:38:11.298 Timeout: 180s
I: 2018-12-29 19:38:11.298 D-Star: enabled
I: 2018-12-29 19:38:11.299 DMR: disabled
I: 2018-12-29 19:38:11.299 YSF: disabled
I: 2018-12-29 19:38:11.299 P25: disabled
I: 2018-12-29 19:38:11.299 NXDN: disabled
I: 2018-12-29 19:38:11.299 POCSAG: disabled
I: 2018-12-29 19:38:11.299 Modem Parameters
I: 2018-12-29 19:38:11.300 Port: /dev/ttyMMDVM0
I: 2018-12-29 19:38:11.300 Protocol: uart
I: 2018-12-29 19:38:11.300 RX Invert: no
I: 2018-12-29 19:38:11.300 TX Invert: yes
I: 2018-12-29 19:38:11.300 PTT Invert: no
I: 2018-12-29 19:38:11.300 TX Delay: 100ms
I: 2018-12-29 19:38:11.300 RX Offset: 0Hz
I: 2018-12-29 19:38:11.301 TX Offset: 0Hz
I: 2018-12-29 19:38:11.301 RX DC Offset: 0
I: 2018-12-29 19:38:11.301 TX DC Offset: 0
I: 2018-12-29 19:38:11.301 RF Level: 100.0%
I: 2018-12-29 19:38:11.301 DMR Delay: 0 (0.0ms)
I: 2018-12-29 19:38:11.301 RX Level: 50.0%
I: 2018-12-29 19:38:11.301 CW Id TX Level: 50.0%
I: 2018-12-29 19:38:11.301 D-Star TX Level: 50.0%
I: 2018-12-29 19:38:11.301 DMR TX Level: 50.0%
I: 2018-12-29 19:38:11.302 YSF TX Level: 50.0%
I: 2018-12-29 19:38:11.302 P25 TX Level: 50.0%
I: 2018-12-29 19:38:11.302 NXDN TX Level: 50.0%
I: 2018-12-29 19:38:11.302 POCSAG TX Level: 50.0%
I: 2018-12-29 19:38:11.302 RX Frequency: 145650000Hz (145650000Hz)
I: 2018-12-29 19:38:11.302 TX Frequency: 146650000Hz (146650000Hz)
M: 2018-12-29 19:38:11.303 Opening the MMDVM
E: 2018-12-29 19:38:11.303 Cannot get the control attributes for /dev/ttyMMDVM0

Followed by this in MMDVM-UDRC:

Slave disconnected, reopening master
Virtual pty: /dev/pts/2 <> /dev/ttyMMDVM0

This is on a working DStarRepeater system with the dstarrepeaterd service disabled.

I’m just fooling around with it in my spare time out of curiosity. I don’t have a real need for it otherwise.

I’ll admit I don’t understand the Pseudo TTY part very well.

Thanks,
Dan - AI2M

On 7 Dec 2018, at 1:01, Annaliese McDermond wrote:

Dan --

Because I’m trying to get my repeater up and running again, and would like to use MMDVM-UDRC to do so, I’ve been doing some work on getting MMDVM-UDRC to work. My code is in the nwdigitalradio github account at:

https://github.com/nwdigitalradio/MMDVM-UDRC

You’re welcome to play with it with the understanding that it’s development code, may not work at all. I’m getting close to having things possibly working acceptably.

An issue you’ll have to deal with is that mmdvm-udrc expects a 24000 sample rate. The UDRC hardware doesn’t support this and if you try to use hw:CARD=udrc,DEV=0 it will fail complaining on not being able to send sample rate. You might try using plughw:CARD=udrc,DEV=0 instead. I’m using a custom asound.conf to support it.

More as I get things worked out.

--
Annaliese McDermond (NH6Z)
nh6z@...

On Dec 6, 2018, at 4:51 AM, Dan Porter (AI2M) groups@... wrote:

Hi Rich,

Did you eventually manage to get it working?
I was thinking of trying again with my UDRC.

73, Dan - AI2M

On Jul 6, 2018, at 3:05 PM, Rich KR4PI @KR4PI wrote:

Thanks John, that helped but there were still a few errors along the way:

g++ -g -O3 -Wall -std=c++0x -pthread -c -o Biquad.o Biquad.cpp
g++ -g -O3 -Wall -std=c++0x -pthread -c -o CalDMR.o CalDMR.cpp
g++ -g -O3 -Wall -std=c++0x -pthread -c -o CalDStarRX.o CalDStarRX.cpp
g++ -g -O3 -Wall -std=c++0x -pthread -c -o CalDStarTX.o CalDStarTX.cpp
g++ -g -O3 -Wall -std=c++0x -pthread -c -o CalNXDN.o CalNXDN.cpp
g++ -g -O3 -Wall -std=c++0x -pthread -c -o CalP25.o CalP25.cpp
g++ -g -O3 -Wall -std=c++0x -pthread -c -o CWIdTX.o CWIdTX.cpp
g++ -g -O3 -Wall -std=c++0x -pthread -c -o DMRDMORX.o DMRDMORX.cpp
g++ -g -O3 -Wall -std=c++0x -pthread -c -o DMRDMOTX.o DMRDMOTX.cpp
g++ -g -O3 -Wall -std=c++0x -pthread -c -o DMRSlotType.o DMRSlotType.cpp
g++ -g -O3 -Wall -std=c++0x -pthread -c -o DStarRX.o DStarRX.cpp
g++ -g -O3 -Wall -std=c++0x -pthread -c -o DStarTX.o DStarTX.cpp
DStarTX.cpp: In member function ‘void CDStarTX::txHeader(const uint8_t*, uint8_t*) const’:
DStarTX.cpp:382:7: warning: this ‘if’ clause does not guard... [-Wmisleading-indentation]
if (d & 0x08U)
^~
DStarTX.cpp:384:9: note: ...this statement, but the latter is misleadingly indented as if it is guarded by the ‘if’
i++;
^
g++ -g -O3 -Wall -std=c++0x -pthread -c -o FIR.o FIR.cpp
g++ -g -O3 -Wall -std=c++0x -pthread -c -o FIRInterpolator.o FIRInterpolator.cpp
g++ -g -O3 -Wall -std=c++0x -pthread -c -o IO.o IO.cpp
g++ -g -O3 -Wall -std=c++0x -pthread -c -o IOUDRC.o IOUDRC.cpp
g++ -g -O3 -Wall -std=c++0x -pthread -c -o MMDVM.o MMDVM.cpp
g++ -g -O3 -Wall -std=c++0x -pthread -c -o NXDNRX.o NXDNRX.cpp
g++ -g -O3 -Wall -std=c++0x -pthread -c -o NXDNTX.o NXDNTX.cpp
g++ -g -O3 -Wall -std=c++0x -pthread -c -o P25RX.o P25RX.cpp
g++ -g -O3 -Wall -std=c++0x -pthread -c -o P25TX.o P25TX.cpp
g++ -g -O3 -Wall -std=c++0x -pthread -c -o POCSAGTX.o POCSAGTX.cpp
g++ -g -O3 -Wall -std=c++0x -pthread -c -o SampleRB.o SampleRB.cpp
g++ -g -O3 -Wall -std=c++0x -pthread -c -o SerialController.o SerialController.cpp
g++ -g -O3 -Wall -std=c++0x -pthread -c -o SerialPort.o SerialPort.cpp
g++ -g -O3 -Wall -std=c++0x -pthread -c -o SerialRB.o SerialRB.cpp
g++ -g -O3 -Wall -std=c++0x -pthread -c -o SoundCardReaderWriter.o SoundCardReaderWriter.cpp
SoundCardReaderWriter.cpp: In member function ‘virtual void CSoundCardWriter::entry()’:
SoundCardReaderWriter.cpp:479:85: warning: comparison between signed and unsigned integer expressions [-Wsign-compare]
le ((ret = ::snd_pcm_writei(m_handle, m_samples + offset, nSamples - offset)) != (nSamples - offset)) {
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~
g++ -g -O3 -Wall -std=c++0x -pthread -c -o Thread.o Thread.cpp
g++ -g -O3 -Wall -std=c++0x -pthread -c -o Utils.o Utils.cpp
g++ -g -O3 -Wall -std=c++0x -pthread -c -o YSFRX.o YSFRX.cpp
g++ -g -O3 -Wall -std=c++0x -pthread -c -o YSFTX.o YSFTX.cpp
g++ Biquad.o CalDMR.o CalDStarRX.o CalDStarTX.o CalNXDN.o CalP25.o CWIdTX.o DMRDMORX.o DMRDMOTX.o DMRSlotType.o DStarRX.o DStarTX.o FIR.o FIRInterpolator.o IO.o IOUDRC.o MMDVM.o NXDNRX.o NXDNTX.o P25RX.o P25TX.o POCSAGTX.o SampleRB.o SerialController.o SerialPort.o SerialRB.o SoundCardReaderWriter.o Thread.o Utils.o YSFRX.o YSFTX.o -g -lpthread -lasound -lwiringPi -o MMDVM

it did complete the compile. When I attempt ./MMDVM is receive the following:

Link does not exist: /dev/pts/1 <> ttyMMDVM0
Error creating symlink from /dev/pts/1 to ttyMMDVM0
Unable to open serial port on vpty: ttyMMDVM0

I am assuming this indicates that it is not properly configured for the UDRC. That is what I will be exploring next.

Thanks for the help
Rich, KR4PI


Current Beta & Beta7 Image's

Todd
 

What's the difference between the two? Also, can I load the image without having the HAT yet? Or should I wait?
Thanks,

Re: Current Beta & Beta7 Image's

 

It is the same file.  A script could always pull current beta and not need to know which beta number is current. 


On Mon, Jan 7, 2019, 15:33 Todd via Groups.Io <ic7461=yahoo.com@groups.io wrote:
What's the difference between the two? Also, can I load the image without having the HAT yet? Or should I wait?
Thanks,