Date   

Re: Unable to install FLDigi

Steve Sampson <coupaydeville@...>
 

Your error message says it depends on  libasound2-dev so maybe try installing that first.

According to the UDRC docs it's:

sudo apt-get install libfltk1.3-dev
sudo apt-get install libsamplerate0-dev
sudo apt-get install portaudio19-dev  

Maybe try that order first.


On Sat, Jul 22, 2017 at 6:29 AM, Eric Coulombe <eric.coulombe@...> wrote:
Hi, i'm trying to install fldigi on a RPi3, new image of compass linux, updated.

with the command "sudo apt-get install portaudio19-dev" i get the following message

Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 portaudio19-dev : Depends: libasound2-dev but it is not going to be installed
E: Unable to correct problems, you have held broken packages.


Somebody can point me to a solution...?
(my UDRC-II works with Direwolf, so I'm pretty sure it's not the board)

Thanks!
Eric - VA2EC



Unable to install FLDigi

Eric Coulombe
 

Hi, i'm trying to install fldigi on a RPi3, new image of compass linux, updated.

with the command "sudo apt-get install portaudio19-dev" i get the following message

Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 portaudio19-dev : Depends: libasound2-dev but it is not going to be installed
E: Unable to correct problems, you have held broken packages.


Somebody can point me to a solution...?
(my UDRC-II works with Direwolf, so I'm pretty sure it's not the board)

Thanks!
Eric - VA2EC


Re: 1200 baud good …. 00 baud no joy

bill K7WXW
 


I figured that out *after* I posted. I skimmed your email a little too fast: ready, shoot, aim. 

73 de bill K7WXW


From: McGrew Julie <juliemcgrew@...>
Reply: udrc@nw-digital-radio.groups.io <udrc@nw-digital-radio.groups.io>
Date: July 17, 2017 at 7:05:33 AM
To: udrc@nw-digital-radio.groups.io <udrc@nw-digital-radio.groups.io>
Subject:  Re: [udrc] 1200 baud good …. 600 baud no joy

Hi Bill,

Not the problem, but thank you very much for your response.  :)

73,
julie
AC0WN


Re: 1200 baud good …. 600 baud no joy

Julie McGrew
 

Hi Bill,

Not the problem, but thank you very much for your response.  :)

73,
julie
AC0WN


Re: 1200 baud good …. 600 baud no joy

bill K7WXW
 

Julie,

The problem is probably with Winlink. In the modem settings, the TNC must be set to NORMAL rather than ACKMODE and will throw an error if it is. How do I know this? Because I just ran into it when I switched from soundmodem to direwolf.

73 de bill K7WXW


From: McGrew Julie <juliemcgrew@...>
Reply: udrc@nw-digital-radio.groups.io <udrc@nw-digital-radio.groups.io>
Date: July 15, 2017 at 7:19:39 PM
To: udrc@nw-digital-radio.groups.io <udrc@nw-digital-radio.groups.io>
Subject:  [udrc] 1200 baud good …. 9600 baud no joy

A few days ago I setup my 2nd UDRC-II with an Rpi3. I added 2.2 k pull-down resistors to GPIO 12 and 23. Also added 4.7 k pull-up resistors to the sql lines on the din6 and the HD Sub-15 to 3.3 vdc. I did the now famous Basil N7NIX script install of the core and AX25 services. At first I tried doing Basil’s script after the compass install and following the NWDigital instructions of “sudo apt-get remove bluez pi-bluetooth and sudo apt-mark hold libasound2 libasound2-data” …. BUT doing that prevented Basil’s script from running properly. So I skipped the remove bluetooth and hold libasound steps in favor of Basil’s script. Did the install to the letter. And I ran ./set-udrc-din6.sh

Now …. using Winlink Express over my wireless network 1200 baud packet works fine from both the din6 and the HD Sub15 BUT 9600 no joy. Tested this with a couple different radios ….. and I’m baffled. I put serious training wheel settings on the 9600 baud setup and tried a couple known good nodes.

Here’s the tail -f /var/log/direwolf/direwolf.log results:
Jul 15 17:27:05 xi direwolf[541]: Ready to accept KISS client application on port 8001 ...
Jul 15 18:02:46 xi direwolf[541]: Connected to KISS client application ...
Jul 15 18:02:46 xi direwolf[541]: KISS protocol set Persistence = 128, port 1
Jul 15 18:02:46 xi direwolf[541]: KISS protocol set SlotTime = 20 (*10mS units = 200 mS), port 1
Jul 15 18:02:46 xi direwolf[541]: KISS protocol set TXDELAY = 50 (*10mS units = 500 mS), port 1
Jul 15 18:02:46 xi direwolf[541]: KISS protocol set FullDuplex = 0, port 1
Jul 15 18:02:46 xi direwolf[541]: [1L] AC0WN>N7RCF-10:(SABM cmd, p=1)
Jul 15 18:02:51 xi direwolf[541]: [1L] AC0WN>N7RCF-10:(SABM cmd, p=1)
Jul 15 18:02:53 xi direwolf[541]: [1L] AC0WN>N7RCF-10:(SABM cmd, p=1)
Jul 15 18:02:56 xi direwolf[541]: [1L] AC0WN>N7RCF-10:(SABM cmd, p=1)
Jul 15 18:03:01 xi direwolf[541]: Error reading KISS byte from client application. Closing connection.
Jul 15 18:03:02 xi direwolf[541]: Ready to accept KISS client application on port 8001 ...

The UDRC-II / Rpi3 rig queries the gateway node, gets a response …. but acts like it doesn’t hear the response … after the 4 attempts set in Winlink it gives up. The responses from the queried node are solid on the S meter.

Pretty sure I probably over looked something simple, or did something stupid …. both genuine possibilities … but I’d really appreciate a bit of help.

If anyone has an idea as to what direction my troubleshooting should follow I’d be most appreciative.

Many thanks to NW Digital Radio for their great products and support!

73,
julie
AC0WN





1200 baud good …. 9600 baud no joy

Julie McGrew
 

A few days ago I setup my 2nd UDRC-II with an Rpi3. I added 2.2 k pull-down resistors to GPIO 12 and 23. Also added 4.7 k pull-up resistors to the sql lines on the din6 and the HD Sub-15 to 3.3 vdc. I did the now famous Basil N7NIX script install of the core and AX25 services. At first I tried doing Basil’s script after the compass install and following the NWDigital instructions of “sudo apt-get remove bluez pi-bluetooth and sudo apt-mark hold libasound2 libasound2-data” …. BUT doing that prevented Basil’s script from running properly. So I skipped the remove bluetooth and hold libasound steps in favor of Basil’s script. Did the install to the letter. And I ran ./set-udrc-din6.sh

Now …. using Winlink Express over my wireless network 1200 baud packet works fine from both the din6 and the HD Sub15 BUT 9600 no joy. Tested this with a couple different radios ….. and I’m baffled. I put serious training wheel settings on the 9600 baud setup and tried a couple known good nodes.

Here’s the tail -f /var/log/direwolf/direwolf.log results:
Jul 15 17:27:05 xi direwolf[541]: Ready to accept KISS client application on port 8001 ...
Jul 15 18:02:46 xi direwolf[541]: Connected to KISS client application ...
Jul 15 18:02:46 xi direwolf[541]: KISS protocol set Persistence = 128, port 1
Jul 15 18:02:46 xi direwolf[541]: KISS protocol set SlotTime = 20 (*10mS units = 200 mS), port 1
Jul 15 18:02:46 xi direwolf[541]: KISS protocol set TXDELAY = 50 (*10mS units = 500 mS), port 1
Jul 15 18:02:46 xi direwolf[541]: KISS protocol set FullDuplex = 0, port 1
Jul 15 18:02:46 xi direwolf[541]: [1L] AC0WN>N7RCF-10:(SABM cmd, p=1)
Jul 15 18:02:51 xi direwolf[541]: [1L] AC0WN>N7RCF-10:(SABM cmd, p=1)
Jul 15 18:02:53 xi direwolf[541]: [1L] AC0WN>N7RCF-10:(SABM cmd, p=1)
Jul 15 18:02:56 xi direwolf[541]: [1L] AC0WN>N7RCF-10:(SABM cmd, p=1)
Jul 15 18:03:01 xi direwolf[541]: Error reading KISS byte from client application. Closing connection.
Jul 15 18:03:02 xi direwolf[541]: Ready to accept KISS client application on port 8001 ...

The UDRC-II / Rpi3 rig queries the gateway node, gets a response …. but acts like it doesn’t hear the response … after the 4 attempts set in Winlink it gives up. The responses from the queried node are solid on the S meter.

Pretty sure I probably over looked something simple, or did something stupid …. both genuine possibilities … but I’d really appreciate a bit of help.

If anyone has an idea as to what direction my troubleshooting should follow I’d be most appreciative.

Many thanks to NW Digital Radio for their great products and support!

73,
julie
AC0WN


Re: UDRC firmware upgrade

Art - KC7SDA
 

thanks! so far the eeprom flashing is working like a charm!


Re: UDRC firmware upgrade

 

ftp://cloud2.hays.org is back online.

On Sat, Jul 8, 2017 at 6:53 AM, Art - KC7SDA <nouse4anick@...> wrote:
So I tried downloading the firmware as described in https://nw-digital-radio.groups.io/g/udrc/wiki/UDRC-II-EEPROM-Flashing however apparently the ftp link isn't working!

is there another spot where I can download this?

Art
KC7SDA




--


John D. Hays
K7VE

PO Box 1223, Edmonds, WA 98020-1223
   


UDRC firmware upgrade

Art - KC7SDA
 

So I tried downloading the firmware as described in https://nw-digital-radio.groups.io/g/udrc/wiki/UDRC-II-EEPROM-Flashing however apparently the ftp link isn't working!

is there another spot where I can download this?

Art
KC7SDA


Re: Changes to "LO Drive" in AlsaMixer Have No Affect #udrc-ii

Kenny Richards
 

David,

That is exactly my situation as well, but I only had to drop the PCM down to 24 (and the LO at 0) to get the deviation correct.

Thanks
Kenny


Re: Changes to "LO Drive" in AlsaMixer Have No Affect #udrc-ii

DAVID BASHAM <davidcbasham@...>
 

I have done exactly that. I moved LO Drive to 0.  Then I kept reducing PCM until their was an affect on deviation and that did not happen until PCM was down to about 8 (-33db).  Thanks again.


Re: Changes to "LO Drive" in AlsaMixer Have No Affect #udrc-ii

Jeremy McDermond <mcdermj@...>
 

On Jul 5, 2017, at 9:44 PM, DAVID BASHAM <davidcbasham@msn.com> wrote:

Jeremy, Thanks for the additional detail. I understand what your are saying re the PCM control. I believe that I have greater than desired deviation and thus would need to do something else such as add a resister divider in the output (rather than using the PCM control) to bring the level down without sacrificing DAC resolution. My deviation is not that excessive and perhaps I just shouldn't worry about it. Thanks again for your explanations.
By all means, if you can’t get it to the proper deviation, use the PCM control. But, you’d rather cut the LO control to it’s full down position first, and then move the PCM down to accomplish your goal.

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


Re: Changes to "LO Drive" in AlsaMixer Have No Affect #udrc-ii

DAVID BASHAM <davidcbasham@...>
 

Jeremy, Thanks for the additional detail.  I understand what your are saying re the PCM control.  I believe that I have greater than desired deviation and thus would need to do something else such as add a resister divider in the output (rather than using the PCM control) to bring the level down without sacrificing DAC resolution.  My deviation is not that excessive and perhaps I just shouldn't worry about it.  Thanks again for your explanations.


Re: Changes to "LO Drive" in AlsaMixer Have No Affect #udrc-ii

Jeremy McDermond <mcdermj@...>
 

On Jul 5, 2017, at 8:35 PM, DAVID BASHAM <davidcbasham@msn.com> wrote:

Thanks Jeremy. Can you expand just a little on what the PCM control is doing. When you say the PCM control multiplies the sample by a scaling factor, I assume there is a scaling factor that multiples PCM by 1. Would that be the value of 38 (0 db)?
Yes, 0dB should be multiplying samples by 1.0 essentially.

I have been reading more about deviation and understand that if your looking at a spectrum plot, and you increase the modulation till the center frequency disappears and you just see the side tones, then you are at about a deviation of 3khz. I have Basil's script running and generating a tone of 1200hz using the UDRCII into a Yaesu FT-8800. I'm looking at the output via a RTL Dongle and SDR#. With the PCM at 38 changing the LO Drive has negligible affect. It is not until I bring PCM down to about 8 that the LO Slider makes any difference and it is not till the PCM is around 8 that my center frequency in the spectrum begins to disappear. So, would it be correct to think I have to reduce the gain of the DAC alot (33db in this case) in order to get down to about 3khz deviation? If so, then should I be using a PCM value of 8 and making fine adjustment with the LO Drive. Things seem to work with the default values of PCM 38 and LO Drive of 9 however I'm not sure if reducing PCM would make things better. I'm just trying to understand more about the system of things at work and the methods I should use to optimize it. Thanks again for your thoughts.
I can’t tell you about Basil’s script or looking at spectrum plots. I have an HP 8901A that I use for setting deviation of my devices.

What I can tell you is that reducing PCM to get more LO Drive isn’t an optimal setup. This is what I was trying to explain to Kenny. Let me see if I can explain a little.

When you use the PCM control, you are multiplying the samples that go into the AIC3204 by some fraction. My recollection is that the control is essentially in voltage gain, which means that every 6dB you knock off on the PCM control, you’re halving the samples, or multiplying by .5.

But, remember that we’re doing this in *binary* and in a computer. Multiplying by half is essentially shifting the value right by one bit. So, a full scale value of 1111111111111111 now becomes 0111111111111111. Since that’s full scale, that means that *no* value will now use the highest order bit. That bit will *ALWAYS* be zero.

Why does this matter? It matters because you’ve now just essentially turned your 16-bit DAC into a 15-bit DAC. This will affect things like the dynamic range you get out of the device (as a simplification, you get a range of 16383 to -16384 instead of 32767 to -32768). More importantly, you have halved the number of steps between the biggest number you can represent, and the smallest number you can represent. This makes what’s called the “quantization noise” (https://en.wikipedia.org/wiki/Quantization_(signal_processing)) worse. So, you’re actually making your signal noisier when you do this.

Think of the degenerate case where you cut off 15 of the 16 bits by multiplying the samples down. Your signal can now only assume two different levels, 0 or 1. You can amplify those (using the LO gain control), but you’ll end up with a square wave. That’s probably not very close to what you intend.

So, you’d rather use the PCM control sparingly, and turn to the LO control first. I understand that there are cases where you’ll have to adjust PCM, but you should do that as a second-order adjustment.

Hopefully this makes some amount of sense.

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


Re: Changes to "LO Drive" in AlsaMixer Have No Affect #udrc-ii

DAVID BASHAM <davidcbasham@...>
 

Thanks Jeremy.  Can you expand just a little on what the PCM control is doing.  When you say the PCM control multiplies the sample by a scaling factor, I assume there is a scaling factor that multiples PCM by 1.  Would that be the value of 38 (0 db)?  I have been reading more about deviation and understand that if your looking at a spectrum plot, and you increase the modulation till the center frequency disappears and you just see the side tones, then you are at about a deviation of 3khz.  I have Basil's script running and generating a tone of 1200hz using the UDRCII into a Yaesu FT-8800.  I'm looking at the output via a RTL Dongle and SDR#.  With the PCM at 38 changing the LO Drive has negligible affect.  It is not until I bring PCM down to about 8 that the LO Slider makes any difference and it is not till the PCM is around 8 that my center frequency in the spectrum begins to disappear.  So, would it be correct to think I have to reduce the gain of the DAC alot (33db in this case) in order to get down to about 3khz deviation?  If so, then should I be using a PCM value of 8 and making fine adjustment with the LO Drive.  Things seem to work with the default values of PCM 38 and LO Drive of 9 however I'm not sure if reducing PCM would make things better.  I'm just trying to understand more about the system of things at work and the methods I should use to optimize it.  Thanks again for your thoughts.


Re: Changes to "LO Drive" in AlsaMixer Have No Affect #udrc-ii

Jeremy McDermond <mcdermj@...>
 

On Jul 3, 2017, at 5:00 PM, Kenny Richards <kenny@holenwall.com> wrote:

Bummer.

I have two radios which require much lower levels. I finally got the IC-207 working by dropping the PCM to 24 with the LO at zero. (Which gave me a near prefect deviation of 3 khz on the service monitor)

I'll bug Bryan about a more hardware focused solution.
There’s not much analog there to deal with. If you need more range on PCM, you might be able to combine the default UDRC with the alsa “softvol” control (http://alsa.opensrc.org/How_to_use_softvol_to_control_the_master_volume). You can use softvol to cut the levels of the input samples before they get to the hardware device. That being said, the volume control on the DAC goes down to 63.5dB. That being said, remember that the dynamic range of a 16 bits of ADC is only around 96dB. If you turn things down all the way, you’re only getting around 33dB of dynamic range on there. Anything you add to that in software volume control is going to reduce that further.

Thanks
Kenny

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


Re: Changes to "LO Drive" in AlsaMixer Have No Affect #udrc-ii

Kenny Richards
 

Bummer.

I have two radios which require much lower levels. I finally got the IC-207 working by dropping the PCM to 24 with the LO at zero. (Which gave me a near prefect deviation of 3 khz on the service monitor)  

I'll bug Bryan about a more hardware focused solution.

Thanks
Kenny


Re: Changes to "LO Drive" in AlsaMixer Have No Affect #udrc-ii

Jeremy McDermond <mcdermj@...>
 

No, there’s no option for lowering the LO bias rail.  I don’t have the datasheet in front of my, but I don’t recall a third setting on it.

Jeremy McDermond

On Jul 3, 2017, at 2:50 PM, Kenny Richards <kenny@...> wrote:

Jeremy,

Is there a dtoverlay option for lowering the LO output without having to change the PCM control?

Thanks
Kenny


Re: Changes to "LO Drive" in AlsaMixer Have No Affect #udrc-ii

Kenny Richards
 

Jeremy,

Is there a dtoverlay option for lowering the LO output without having to change the PCM control?

Thanks
Kenny


Re: Changes to "LO Drive" in AlsaMixer Have No Affect #udrc-ii

Jeremy McDermond <mcdermj@...>
 

LO drive controls the gain of the analog "line out" amplifier after the DAC. The PCM control affects the output of the DAC by itself. The PCM count control merely multiples the incoming samples by a scaling factor, so you actually lose DAC resolution by using it. This is why we tell you to adjust LO drive first. 

The LO amp has a few options on where it gets bias from. The dtoverlay setting makes it take off the 3.3v bus, which gives you a bit more drive than stock. 

You also want to check out the waveform itself. My experience is such that 0db on both controls is not very far off from clipping. 

Jeremy
Nh6z@...
Sent from my iPhone

On Jul 3, 2017, at 12:47 PM, DAVID BASHAM <davidcbasham@...> wrote:

Thanks Basil.  I understand what you are saying in regards to different radios reacting differently to the audio drive level being inserted.  That all makes sense.
I did some further testing and found that when PCM is set to 38 (the value set by the set-udrc-din6.sh script)
then any change in LO Drive has no affect.  If I lower PCM to where I first hear a change in received audio level on a second radio (PCM set to around 10), then changing LO Drive does make a difference.  It acts the opposite of what I expected with it acting like the LO Drive is fine control and PCM is course.  I would have expected no output when LO Drive is set to 0 regardless of the PCM setting.  Again, when PCM is set to 38 and LO Drive is set to 0, I hear a good solid tone on my second rig.  I will read up on what those settings do in the TI literature and I will see what affect the dtovlay has on the environment as well.

4381 - 4400 of 5888