Welcome to the new FlexRadio Community! Please review the new Community Rules and other important new Community information on the Message Board.
If you are having a problem, please check the Help Center for known solutions.
Need technical support from FlexRadio? It's as simple as Creating a HelpDesk ticket.
Need technical support from FlexRadio? It's as simple as Creating a HelpDesk ticket.
Need the latest SmartSDR and Power Genius Software?
SmartSDR v3.1.12 and the SmartSDR v3.1.12 Release Notes. | SmartSDR v2.6.2 and the SmartSDR v2.6.2 Release Notes.
SmartSDR v1.12.1 and the SmartSDR v1.12.1 Release Notes. | Power Genius XL Firmware v3.4.16. | Power Genius XL Utility v2.2.10.
SmartSDR v3.1.12 and the SmartSDR v3.1.12 Release Notes. | SmartSDR v2.6.2 and the SmartSDR v2.6.2 Release Notes.
SmartSDR v1.12.1 and the SmartSDR v1.12.1 Release Notes. | Power Genius XL Firmware v3.4.16. | Power Genius XL Utility v2.2.10.
Announce: experimental CAT/DAX clients for Linux
Leave a Comment
Categories
- 67 Community Topics
- 1.9K New Ideas
- 118 The Flea Market
- 5.4K Software
- 4.9K SmartSDR for Windows
- 35 SmartSDR for Maestro and M models
- 84 SmartSDR for Mac
- 143 SmartSDR for iOS
- 149 SmartSDR CAT
- 66 DAX
- 278 SmartSDR API
- 7K Radios and Accessories
- 5.8K FLEX-6000 Signature Series
- 553 Maestro
- 14 FlexControl
- 721 FLEX Series (Legacy) Radios
- 148 Power Genius Products
- 117 Power Genius XL Amplifier
- 10 Power Genius Utility
- 21 Tuner Genius
- 41 Shack Infrastructure
- 22 Networking
- 88 Remote Operation (SmartLink)
- 50 Contesting
- 127 Peripherals & Station Integration
- 61 Amateur Radio Interests
- 402 Third-Party Software
Comments
Alan - you need to rename the nDax-linux-arm to nDax. Then take a look at the readme file on github, he details the command line to execute on this page:
where station_name is the flex name for your ssdr instance running on some machine
Thanks Lou and others.
Making progress, but not there yet.
I renamed and ran the command with station name "Maestro. I got a response:
Next, tried to enter audio settings into WSJT-X running on the same Raspberry Pi and did not see the audio in/out devices on the pull down menu. Also, on startup received several alarm messages, including:
Alan. WA9WUD
More progress, but still not there yet.
I used "-station Maestro" with default for "discover". Got an error that port 4992 was in use. <first command/response>
So, I added the IP of my Flex Server, "-radio string 192.168.50.80" to the command (I think I am beginning to understand how to configure nDAX now). Received new error message, "no such host connecting to string" <second and third command/response>.
Note/Question - what is the "lookup string on 192.168.50.1:53 referring to? That is the ip of my router?? Is it asking the router where the Flex Server is? My router knows the flex IP because that is where I get the Flex IP from; the router client list.
Alan WA9WUD
Use "-radio 192.168.50.80". The "string" is to be replaced with your radio's IP address.
Also, the "Port 4992 in use" message is likely the result of already having nDax running in the background. Use the command "ps ax | grep -i dax" to find all instances of a running xDax process. The first part of the line will have a 4 or 5 digit number. Use the command "**** <number>", where <number> is replaced by that 4 digit number. Be careful that you type the number correctly - you will be terminating the process with that pid (Process Identification Number).
[Edit: the Community interface replaced the "k i l l" with asterisks! What's with that??? the command is "k i l l <pid>" . And the second time through, it passed on the command - weird.]
Thanks Ted:
Still not working.
Checked for multiple instances. None.
Tried again with "-radio 192.168.50.80" >>....."no such file......" (now I see how to correctly enter config parameters)
Tried again with default discovery >> ".....address in use....."
Tried rebooting the Raspberry Pi. Did not fix the problem
Tried rebooting the Flex Server (remote on/off). Did not fix the problem.
Tried xDAX. Worked just fine.
Tried DAX. Worked just fine.
Checked for the VITA49 UDP broadcast on port 4992. Flex Server is sending the packets
Was running multiplex. Removed a client. Now just the Maestro. Did not fix the problem.
Help!
Alan
sudo netstat -nap|grep 4992
this will tell us what program is using port 4992
Lou. Thanks. Here is the result:
192.168.50.171 is the Raspberry Pi running nDAX. I do not recognize the :41802 port??
Alan
From your last attempt, with the radio specified, it looks like you are missing a pulseaudio component. I have not seen that, but perhaps you should review your audio software install on the Pi. Google “Install pulseaudio on RaspberryPi” and you may get some help. Or some kind soul with more time here on the Community can give you some guidance.
i am unable to give specific advice because I refuse to run v3 software with multiflex - I want my profiles and tuner to work.
Ted
Thanks.
But, that would not explain the failure for nDAX to see see and connect to the Flex Server??
Back to your suggestion, I did a search "pulseaudio" on my Raspberry Pi "Synaptic Package Manager" and found a lot of hits. Can anyone tell me the specific pulse audio package I would need to install?
Alan
The second line is the one I am concerned with. so it looks like you have a dotnet application listening on port 4992. What software do you have running on the pi?
Try rebooting the pi and run the netstat command again. We really need to track down what program is listening on 4992. Did you setup .Net on the pi for any programs?
Lou
I am running ".NET Core 3.1" for FRStack
So.... I shut down FRStack, and re-ran the nDAX commands:
Looks like FRStack is a conflict. FRStack does listen to port 4992. Does that "tie up" the port?
This looks like progress. Perhaps Ted was correct, I need to load a "pulseaudio" dependency??
Which one?
Alan
yes it looks like there is a conflict with frstack, not sure how to get around that one....
to install pulse:
sudo apt-get install pulseaudio
Lou
So.....to further nDAX install. With FRstack shutdown.
I installed PulseAudio:
I re-ran nDAX.
Notice nDAX, it is looking for a file "user/1000/pulse/native". But....the "user" director does not exist on a Raspberry Pi???? Ummm.
Now, what do I do?
Alan
Lou
I installed the Pulse Audio package you directed me to:
sudo apt-get install pulseaudio
nDAX is still looking for the "user" directory on a Pi?? How do we tell nDAX the correct path??
Alan
if you did not restart the pi after installing try running:
Lou - Progress!
Re-started Pulse Audio.
New problem. nDAX is now looking for "module-pipe-source"??
Alan
1st not sure if this will help but you will need it so lets try it first:
restart pulse again:
then rerun nDax
Lou - Progress
After installing the utilities, nDAX said it was waiting for a station name. I entered "Maestro". nDAX appears to be waiting, or does this mean nDAX is running and bound to Flex Client "Maestro"? In the end, there is no audio into WSJT-X....see below.
So.... I took a look at WSJT-X. I now see the DAX audio devices in the pulldown.
However, it does not look there is any Audio into WSjT-X:
Alan, you have specified a station (Flex v3 artefact for the instance of the radio you are talking to), as "station_name" - you should probably replace that in the nDax invocation with the actual name. You have been using "Maestro" earlier.
Yaaaaaaa! Success!
Now on to nCAT. Do you have any suggestions? I guess I will follow the same path as I did for nDAX.
It was not exactly as "around" first said, "No installation required, and there are instructions in the README. For the most part, just download and run."
Was me installing on a Raspberry Pi the reason extra steps were necessary?
Alan
it assumes you are using pulse audio, equivalent to windows audio system - just ant work without it. Most linux's have it installed by default, not rPi
Good luck with nCAT - there should be no additional dependencies needed
Any plans (or progress) on enhancing nCAT - especially to operate in split mode? I've tried running two version of nCAT as a work around, but WSJTS/HAMLIB configuration only supports one port from in the radio configuration. Not sure how to work around that.
Thank you - Happy Holidays!
@cdub89_WX7V split isn't too hard from a technical point of view, it's figuring out how it should work in terms of user interface / configuration that's tricky. I'd be happy to hear about how people would like to use it, so I can come up with the right design.
For wsjt-x, setting split to "none" works just fine — the Flex has an absolutely flat TX passband in DIGU mode so there's no need for it to adjust the TX freq. Setting it to "fake it" works equally well, since the Flex can retune instantly without waiting for a VFO to settle :)