Date   

sox?

ab9ca@...
 

OK, while trying to troubleshoot my non-functioning UDRC I decided to run the tone generator to generate a test tone. But when I do that I get the message that I need 'sox', whatever that may be. So . . . do I really need to go get 'sox' or is it on the RPi somewhere but the script can't find it? And what is 'sox' and how do I install it, if need be? 

73 de dave

ab9ca/4



Re: Error running curl goo.gl command

 

Don't know why you have the DNS problem here is the long URL https://raw.githubusercontent.com/nwdigitalradio/udrc-tools/master/scripts/udrc-alsa-din6.sh


On Nov 24, 2016 19:17, <abe@...> wrote:

I'm trying to setup the UDRC on Pi 3 as a hotspot.

When running the command to curl from goo.gl/7rXUFJ a vacant .sh file is created. When looking at verbose output it says "could not resolve host:goo.gl"

What is wrong?

Abraham

N3BAH


Re: Error running curl goo.gl command

August Treubig <atreubig@...>
 

Look at your dns server definition.   

Aug in Alabama

On Nov 24, 2016, at 8:44 PM, abe@... wrote:

I'm trying to setup the UDRC on Pi 3 as a hotspot.

When running the command to curl from goo.gl/7rXUFJ a vacant .sh file is created. When looking at verbose output it says "could not resolve host:goo.gl"

What is wrong?

Abraham

N3BAH


Error running curl goo.gl command

abe@...
 

I'm trying to setup the UDRC on Pi 3 as a hotspot.

When running the command to curl from goo.gl/7rXUFJ a vacant .sh file is created. When looking at verbose output it says "could not resolve host:goo.gl"

What is wrong?

Abraham

N3BAH


Where did the modulation go . . .

ab9ca@...
 


On 11/24/16 5:56 PM, John D Hays - K7VE wrote:
> There is a sub-group for UDRC.
>

Maybe you can move the discussion to that sub-group? Or maybe I can. Will give it a stab.


> Going over wired or wireless does not make any difference to
> ircddbgateway.

AFAIK ircddbgateway is working OK. As I said in my note, it is dstarrepeater that is not working. I get no RX nor TX showing in the dstarrepeater.log file or when viewing the tail during operation.

>
> Do you have ircddbgateway and dstarrepeater talking to each other over
> the 127.0.0.1 address? If you were using LAN addresses, that could be
> the disconnect.

As far as I can tell, yes. Both config files show that address for the other device. Not using LAN addresses at all.

>
> If your alsa settings are correct, try shutting down and removing
> power to be sure nothing is in a unknown state.

This occurred yesterday afternoon late. The entire setup was without power overnight. The levels in alsamixer are as I left them set when it was sorta working.

>
> Can you perform other network activity from the RPI over Wifi?

Yes, I call up the NW Digital site to look over the instructions.

>
> I will be doing Thanksgiving with the family so may not be available
> for hours at a time.

Thank you much for your help . . . on Thanksgiving Day no less! I was not expecting to hear anything until tomorrow at the earliest.

Keep in mind that the setup was working for everything but audio from the reflectors. I could link to a reflector, hear the canned message that I was linked, etc. The crawl was being decoded and displayed on the screen of the 91AD. The addresses had to be right for all that to happen.

But while trying to set up the port forwarding I lost wired connectivity. The instant I connected via wireless, dstarrepeater stopped working. Nothing else changed. I told the RPi to connect to the wireless and dstarrepeater stopped working. No RX has been decoded since, nor have a I heard any modulation when the ID's key the TX, only dead carrier.

I have the ID interval set to 2 min. But earlier, while troubleshooting, it had been set to 30 sec. I see the ID being sent in the dstarrepeater.log window but nothing is heard over the air.

I have the tail of dstarrepeaterd.log in one window, the tail of ircddbgatewayd.log in another, and have a 3rd open to type commands into.

73 de dave
ab9ca/4


>
>
> On Nov 24, 2016 15:47, <ab9ca@... <mailto:ab9ca@...>> wrote:
>
>
>     OK, after several frustrating hours I finally got the UDRC to the
>     point where I could log on to reflectors. Heard the canned message
>     about being linked. But heard no reflector audio. I assume that is
>     because I had not yet set up port forwarding.
>
>     While trying to set up port forwarding something happened to my
>     router. Not sure what. Lost wired internet connectivity. Dunno what
>     caused it but eventually got it resolved and think the port forwarding
>     is set up. Have wired connectivity back.
>
>     While I had lost wired internet, the wireless still worked. So I set
>     the RPi up to connect wirelessly.  Apparently this is a mistake. The
>     docs are totally silent on this. No reason not to connect wireless,
>     right? The instant it connected wirelessly, the modulation
>     disappeared, and, numerous reboots and restarts later, it has not
>     re-appeared.
>
>     So why does the radio connection care about whether the internet is
>     wired or wireless?
>
>     And how do I get modulation back?
>
>     PTT is still working. I get dead carrier when the UDRC ID's. Note that
>     I also have no detection of RX modulation. Neither TX nor RX shows any
>     response. The internet connection does work, I can see the activity in
>     ircddbgatewayd.log. But nothing shows up in dstarrepeaterd@1.log <mailto:dstarrepeaterd@1.log>. And
>     I hear nothing over the air. Monitoring with a RX set to analog FM.
>
>     I checked the levels in alsamixer and those appear to be OK.
>
>     73, dave
>     ab9ca/4


Re: Unable to get sound to FLDIGI with UDRC-II

Urdc@...
 

I grabbed bed pictures of my environment.


you can see the C-Media sound dongle in white with the black DIN cord, and the Pi with UDRC and beige cord. The white cord is my CAT Control, with FLRig. Then Ethernet, HDMI, and Power.


to contrast between the two cards I am just swapping the DIN to the back of the radio.


nick





Re: Unable to get sound to FLDIGI with UDRC-II

udrc@...
 


Hi Corky!

1. Using a Yaesu 857d, in PSK31-U mode. My PKT Baud Rate was 1200, as that is what I use for my local BBS's, My MOBILINKd came with a short DIN-F to DIN-M extender that swaps the 1200/9600 baud pins, and that also allowed the UDRC-II to get some signal with the stripy noise.


2. Yup, I toned out each pin of the cable that came with, don't have an scope to put it on.


3. My first test was to re-run the set-udrc-din6.sh before running any application. Each time run a test is after reboot, since it takes so little time. I can't seem to rid myself of the nast stripy noise without killing the audio stream mixed with it. It is very hard to tell in the audio I am getting now is any sort of representation of what the C-Media Sound Card is seeing, I am working on a Female adaptor so I can more the DIN Male/Male cable between the two cards so that each test won't even change cable position.


I am open to other test, just shot :-D (And thank you for your guidance so far)


Nick









Re: Unable to get sound to FLDIGI with UDRC-II

Corky Searls
 

The signal you are seeing - the striped display - is a display of oscillator noise from a display or more likely the CPU and as you suspected indicates that no sound is being detected. Unfortunately, I do not have a system with me at this time I can test with, but a couple of suggestions of things to try.

First, make sure that no other applications are running that use the udrc. That is, make sure direwolf or other virtual connections as these will occasionally "steal" the sound stream. I have also seen occasional interaction between alsa-mixer and fldigi. You can tell if that is happening by whether you see the same settings when you open alsa-mixer  with and without fldigi running. If they are not the same, but you find "the LO channel raised all the way up" shut down fldigi and re-open alsa-mixer. Do you see the same settings? If not and everything looks normal, with alsa-mixer open and looking at the udrc display start fldigi. Now do you see the same waterfall display?

If you have access to an oscilloscope you can also check the input pin on the udrc to verify that you are seing signal from the radio.

I am assuming that you have already checked the continuity of the 6-pin cable to make sure all pins are passed through.

You do not say specifically what radio you are using, but from you description It sounds as though it might be an FT-817?

Thanks,
-Corky

On Nov 23, 2016, at 11:21 AM, Urdc@... wrote:

Thats fair. I removed all the virtual settings and went back to the initial setup. The same striped waterfall is there. I do have to use the swap left/right channels as in the docs, but with the audio setting from the factory set up modded to the tune tweaks, I get no waterfall, with the LO channel raised up I can just get this.


<IMG_7747.JPG>


Re: Unable to get sound to FLDIGI with UDRC-II

Urdc@...
 

If if I swap to the C-Media dongle, leaving the radio untouched.. I get good waterfall and QSO's.





Re: Unable to get sound to FLDIGI with UDRC-II

Urdc@...
 

Thats fair. I removed all the virtual settings and went back to the initial setup. The same striped waterfall is there. I do have to use the swap left/right channels as in the docs, but with the audio setting from the factory set up modded to the tune tweaks, I get no waterfall, with the LO channel raised up I can just get this.




Re: Unable to get sound to FLDIGI with UDRC-II

 

Test against the basic hardware (udrc) device first. Remember the virtual stuff is experimental.


On Nov 22, 2016 21:31, <Urdc@...> wrote:

I'm at a loss, following the docs on setup, I configured my virtual soundcard for the 6 pin din, made the mod add to config.txt and rebooted. I see my din_In and din_out devices, and so does FLDIGI. I set the turbo = 1 as I am on a RPi 3b+


with my radio on digital (psk31usb) I plug in the UDRC card. I get a flat line, no waterfall. 

this is with the recieve channels reversed as the wiki says.


if I don't reverse channels, I get a very weak stripped waterfall. If I up the "LO Drive" I get a slightly fuller striped waterfall that's just as unreadable.

With my C-Media USB soundcard plugged in at the same time, I use the 6-pin din to the radio, I get a clean waterfall. 


I sat  with the radio connected and alsamixer open and tried moving every capture setting, could not get a clean waterfall.


might I have a bad board?




Re: Unable to get sound to FLDIGI with UDRC-II

Urdc@...
 

Attached is the really applified stripey waterfall on 14070.00 


Unable to get sound to FLDIGI with UDRC-II

Urdc@...
 

I'm at a loss, following the docs on setup, I configured my virtual soundcard for the 6 pin din, made the mod add to config.txt and rebooted. I see my din_In and din_out devices, and so does FLDIGI. I set the turbo = 1 as I am on a RPi 3b+


with my radio on digital (psk31usb) I plug in the UDRC card. I get a flat line, no waterfall. 

this is with the recieve channels reversed as the wiki says.


if I don't reverse channels, I get a very weak stripped waterfall. If I up the "LO Drive" I get a slightly fuller striped waterfall that's just as unreadable.

With my C-Media USB soundcard plugged in at the same time, I use the 6-pin din to the radio, I get a clean waterfall. 


I sat  with the radio connected and alsamixer open and tried moving every capture setting, could not get a clean waterfall.


might I have a bad board?




Re: UDRC-II DIN to Yaesu 857D, sound is killed.

Urdc@...
 

Ok, switched Audacity to Stereo and the left channel seems to be getting the audio.

(See picture) 


there is nasty hiss on either side of my HT announcing my call sign. Is that expected? I have my 857d on 146.460 simplex with PKT mode enabled to allow the PC port to work.



Re: UDRC-II DIN to Yaesu 857D, sound is killed.

Urdc@...
 

Ok, going to basics.. using Audacity to record the din_in device, while my radio is connected, I get a quick hiss and dead air.


i try moving the dial, nothing. Thinking the DIN to my 857D is having an issue? 


Re: UDRC-II DIN to Yaesu 857D, sound is killed.

Stuart Longland VK4MSL
 

On 23/11/16 08:46, John D Hays - K7VE wrote:
I actually kind of like the Yaesu mute the speaker feature, but can
understand why some would like it :)
I don't like it when it mutes the output to said DIN connector too.

--
Stuart Longland (aka Redhatter, VK4MSL)

I haven't lost my mind...
...it's backed up on a tape somewhere.


Re: UDRC-II DIN to Yaesu 857D, sound is killed.

 

I actually kind of like the Yaesu mute the speaker feature, but can understand why some would like it :)

On Tue, Nov 22, 2016 at 1:54 PM, <udrc@...> wrote:

I am moving my last issue to a separate thread, as I am slowly unwinding my software interaction confusion. :-)


This has been seen with other Yaesu radios, but when I connect my DIN cable (came with the UDRC-II) to the 6-pin PC port of my Radio, my speaker instantly goes dead. My previous FLDIGI cms USB sound-card connection never did that. I had the option of listening to the noise, or turning down the volume once it was working and playing PSK-31 is silence.

I thought there was a pull up resistor issue that might be attributed to this? 


Nick




--


John D. Hays
K7VE

PO Box 1223, Edmonds, WA 98020-1223
   


UDRC-II DIN to Yaesu 857D, sound is killed.

udrc@...
 

I am moving my last issue to a separate thread, as I am slowly unwinding my software interaction confusion. :-)


This has been seen with other Yaesu radios, but when I connect my DIN cable (came with the UDRC-II) to the 6-pin PC port of my Radio, my speaker instantly goes dead. My previous FLDIGI cms USB sound-card connection never did that. I had the option of listening to the noise, or turning down the volume once it was working and playing PSK-31 is silence.

I thought there was a pull up resistor issue that might be attributed to this? 


Nick





Re: Latest kernel on compass distribution

 

A few developers are working together in the background to bring updates into the distribution.

Perhaps this discussion should continue in the compass list.  https://nw-digital-radio.groups.io/g/compass/messages



Re: Latest kernel on compass distribution

Edouard Lafargue
 

  Hi Basil,

   The way to reproduce is as follows: With an AX25 interface at ax0, I can reliably crash the kernel by starting a virtual KISS using 'net2kiss -i ax0 /dev/ptmx', and then by using another program (Linpac or ldsped, for instance) to open a connected session on that same ax0 interface with any remote station.

   As you can see, you don't need to do anything with the new KISS interface, the only requirement is that net2kiss is running, and you open an ax.25 connection using another program.

    Let me know if you can reproduce!

My kernel is: Linux compass 4.4.15-v7+ #1 SMP Fri Jul 29 04:35:51 UTC 2016 armv7l GNU/Linux
pi@compass:/etc/ax25 $ netstat --ax25
Active AX.25 sockets
Dest       Source     Device  State        Vr/Vs    Send-Q  Recv-Q
*          W6ELA-0    ax0     LISTENING    000/000  0       0     
*          W6ELA-0    ax1     LISTENING    000/000  0       0    


On Sun, Nov 20, 2016 at 10:16 PM, Basil Gunn <basil@...> wrote:
Edouard,

Could you please describe the bug you are seeing & the procedure you
would use to replicate it. Also could you please post the output of
the following 2 commands.

uname -a
netstat --ax25

I would like to try & reproduce what you are seeing.

Thanks,

/Basil n7nix


On Sun, 20 Nov 2016 15:05:15 -0800
"Edouard Lafargue" <ed@...> wrote:

>   Thanks Bernard! Yes, this is the bug I have been hitting as well - a
> straighforward kernel panic when using net2kiss, which is frustrating
> - it's the only missing link for my RPi setup, I have native AX25,
> AWGPE emulation and the rest working great, but I still need TCPKISS
> for a couple of applications such as Winlink Express...
>
> 73 de ed w6ela
>
> On Sun, Nov 20, 2016 at 9:25 AM, f6bvp <f6bvp@...> wrote:
>
> > Hi all,
> >
> > I have been working on the AX.25 module bug that is responsible of a
> > kernel panic and crash. It appeared recently on Raspbian distro when
> > performing an rpi-update. I checked all previous kernels and finally
> > localized the bug in LINUX kernel 4.1.15. Then I worked on a simple
> > patch that I discussed with AX.25 maintainers and others. However
> > the patch has not yet been committed to netdev mailing list and it
> > could take a long time to be done. It is sad that this bug prevents
> > us from upgrading kernel to keep a safe AX.25 system working.
> > If Raspbian or Compass distro (I am now using with UDRC-II for 9600
> > bauds in ground station for Cubesat French satellites project)
> > could be patched, it would be a nice feature.
> >
> > 73 de Bernard f6bvp
> >
> > http://f6bvp.free.fr/raspberrypi.html
> >