I just bought an SDRplay RSP2 receiver. It seemed to have good specs for the price. I already had a FunCUBE Pro Plus which covers roughly the same spectrum but it can only support a 96 kHz wide panadapter, which is a bother on VHF. The SDRplay RSP2 can be set for 500kHz, 1, 2, 3 ,4, 6, 7, 8, or 10 MHz (10MHz is at a lower bit rate at least on SDRconsole). This is neat because you can watch the whole of the 2m ham band or the 70cm band. (Not both at once).
The native software for the RSP2 is SDRuno which apparently was built from Studio1. It is OK, but a bit odd. For example each receiver has buttons for the HF bands and 2m, but not 6m. The buttons on the subsequent receivers don't work at all if RX0 is set to a VHF or UHF frequency. Each receiver can have its own panadapter and audio panadapter so you end up with lots of windows and it can be rather confusing working out which receiver relates to which panadapter. Having a separate panadapter for each receiver is pretty pointless since each receiver must be inside the maximum 10Mhz of bandwidth. Although you can have panadapters zoomed in to show smaller sections of the 10MHz spectrum available. Personally I would rather have all of the receivers displayed on a single panadapter. The HF band buttons only really work on RX0 and even then they are extremely annoying. I would have expected that pressing the button would switch the receiver so that the panadapter showed the band of interest... but it doesn't. If for example you have the sample rate set for a 6 MHz bandwidth and you press the 20m button, the receiver sets the current cursor position to 14.0 MHz. If the cursor happens to be at the center of the panadapter you get 11.5 MHz to 16.5 MHz on the panadapter. The memories work exactly the same way. If for example you have 5 repeaters setup as memories, each time you click on one the panadapter shifts and you lose visibility of the other repeaters. This really bugs me. The SDRconsole memory management is 1000 times better. Yeah I know you can lock the Local Oscillator, but it is still clunky.
Everything you look at on UHF or VHF is in a band. Aircraft band, Marine band, 70cm ham band etc. When you click on a band memory (s1b file). It should set the panadapter to show the band of interest or at least as much of it as possible. If the band is wider than 10 MHz, you could always save separate high and low band s1b files. Then when you click on a saved memory the panadapter should stay fixed and the cursor (receiver) should jump to the channel that you want to listen to. the developer needs to exploit the advantage of having a wideband panadapter, instead of thinking of the radio as a single channel receiver. The software is actually pretty good and it works OK. The panadapter works better than the one on SDRconsole which is strange and unpredictable especially if you change bandwidth to a different sample rate. Just a teething problem I guess. SDRconsole is pre-beta so it is unfair to be critical.
SDRuno is really very good, but some things do bug me. My main gripes about SDRuno are.
1 the band buttons should make the panadapter display a band, not just jump to the bottom of the band.
2 the band store should remember the current panadapter settings and actually be a 'band store' not just a directory
3 Saving a workplace is great except the receiver frequencies are lost not recalled. On a program restart or change of workplace, all of the receivers pop up on the same frequency. So you have to go and set them all to the right channels again.
4 you cant set the bandwidth of a receiver without opening its audio spectrum display window.Post is under moderationStream item published successfully. Item will now be visible on your stream.
I finally got SDR Console V3 to run on my PC. In the end I researched the 000007b error I was getting and the general consensus was to download a heap of dll files and bung them in the Windows System32 directory. I was not keen on this idea since everything else was working fine. I didn't want to end up crashing other programs. In the end I found a similar (not gaming focused website) and downloaded this file '0xc000007b_win10(x64).zip' Google it if you have the same problem that I did.
I was not brave enough to copy the files into my System32 and SysWOW64 directories, so I copied all of the dll files into the SDRConsole main directory. Working on the principle that the program will look there before looking at the system directories. That fixed the problem and everything is now working. I am a happy camper.
I have had SDRconsole freeze up a couple of times when changing to a different favourite. I do like the way the program remembers the panadapter settings and the four or five receivers as well. Super idea. Seems to be reasonably stable otherwise and it is pre-beta software so you cant expect it to be perfect yet. The favourites menu is SOOOOO much better than SDRUno which seems to have been written by somebody who does not understand that the radio is an SDR.Post is under moderationStream item published successfully. Item will now be visible on your stream.
I bought the Behringer CMD Micro. It is smaller than the 2A and it fits nicely on my desk immediately in front of the keyboard. WOW what a neat addition to he shack! It works great. BIG thanks to Chris W2PA for writing the code and the documentation. I had trouble making the VFO wheels work and would have been stuck without Chris' website. The big wheels have a dual function for DJs. The trick is when you map them to the Midi scheme do not touch the top of the knob at all. very gently rock the edge of the knob so that PowerSDR reads the control as a low of 63 and a high of 65. (If it is reading 0-127 you touched the top of the knob and the control wont work). Once that is saved it all works brilliantly.
I recently changed VFO-A to the right side and VFO-B to the left side. It seems counter-intuitive but being right handed it means that I can control the main receiver frequency without reaching over to the left side. I switched the volume controls as well but left the other controls the same.
I see that my forum post got deleted so I have added the picture of how I mapped the Midi controls.
The console has 20 switches, 3 "wheels" (the Browse knob is a wheel), 5 slider controls and 2 knob controls. Some PowerSDR controls can only be mapped to a wheel and others to a knob.Post is under moderationStream item published successfully. Item will now be visible on your stream.
This is a compilation of the release notes for PowerSDR mRX PS.
Sometimes it is nice to know when features were added, or when bugs were fixed. More importantly the notes often contain instructions on how to configure the new settings and the reason that changes were introduced. You may even find features that you didn't know about.
The notes are also a really good history of the results achieved from the thousands of hours that the volunteer coders put into making PowerSDR the excellent software package that it is. Remember you get the fruits of their labor absolutely free of charge.Post is under moderationStream item published successfully. Item will now be visible on your stream.
I just bought a Behringer CMD Micro midi controller (1 Sept 2017). A very neat unit, smaller than the 2A so it takes up less desk space. It is cheaper too. 5 Sliders, 3 wheels, 2 knobs, and 20 buttons is plenty of controls. I found it a struggle to find uses for them all. (Yes 3 wheels - the small knob in the very centre is a jog wheel. It spins 360 degrees with no end stops and maps 63/65. The other two knobs are standard potentiometers which map from 0-127).
WOW why didn't I buy one sooner what a fab addition to the ANAN radio. The unit has two knobs for operating VFO-A and VFO-B when in Split / Dual Rx mode and it is really nice. I mapped everything else with running Split mode on one panadapter in mind. Some functions can only be mapped to a wheel control and others can only be mapped only to a knob / slider, or to a button. Not everything maps perfectly, for example using buttons to control the RX2 band switching does not work reliably. But mostly the setup is a breeze.
BIG, BIG thanks to Chris W2PA for writing the code and the instructions. I would have been stuck without those notes because the two 'jog' wheels are hard to get working. They have a dual function intended for DJs that makes them tricky to map. They act like a switch as well as like a wheel. The answer is to not touch the top of the knob at all when you are doing the mapping. Just carefully move the rim left and right until the display says min = 63 and max = 65. Then hit 'Done' and the control will be mapped perfectly. If the max min says 0/127 you have touched the top and the control wont work.
I have added a picture of the mapping I have used, in case someone else wants to try a layout that works for me.
Post is under moderationStream item published successfully. Item will now be visible on your stream.
I have had an unbelievable amount of trouble getting audio to come out of the headphone jack on the Tinker board. The audio was one of the reasons that I chose the Tinker over the Rpi3. After some teething problems, I got piHPSDR to output to the headphone jack by setting RX to local audio and hw:0,2. I notice that if I plug in an external USB soundcard the audio moves to hw:1,2 but piHPSDR tracks that change with no problems. Note that piHPSDR works completely independent of the PulseAudio and ALSA settings in Linux.
BUT getting web browser or media player audio out to the headphone jack was a real issue, involving many hours of wasted time, and posts on several websites.
First step, find out which output device works. Either use piHPSDR (RX tab), or the aplay -l command to list them. On my system the headphone jack is on hw:0,2. Pulse Audio volume control also known as pavucontrol does not seem to know that and you can't set it from the GUI. Aplay is one of the alsa-utils You might have to install it. ftp://ftp.alsa-project.org/pub/utils/alsa-utils-1.1.4.tar.bz2 . The aplay -D hw:0,2 /a directory/a subdirectory/a wave file.wav command will play a wave file on the specified device. Substitute the path and filename to address a valid wav file on your Tinker. If you have the hardware card and device correct you will hear the audio from the amplified speakers or headphones that you plugged into the headphone jack. OK at this stage you know which port you want PulseAudio to work on. The next step is to make it do that.
In the etc/pulse directory use sudo leafpad default.pa to edit the default.pa file. You have to do it from the terminal or it wont save. Gee Linux is KLUNKY!
1. at the end of the section that says "## load drivers statically" I added a line
load-module module-alsa-sink device-hw:0,2 Note if your card outputs audio on a different hw combination put that in instead. Don't put # at the start of the line it stops the command working turning it into a REMark. But you knew that right?
2 at the end of the file where it says "## make some drivers default" I added a line
3. save the file. Start an application that has sound. YouTube or media player.
4. Open the PulseAudio volume control. It may error, but wait a minute and it should sort itself out and begin working.
5. Now the odd bit. Go to the 'Configuration' tab set both rockchip.miniarm-codec and USB Audio to off. You should get audio out from the speakers at this stage. I think that rockchip.miniarm-codec is for HDMI audio. The Output devices and Playback tabs should show the audio and the volume controls should work. YIPEEE It works and it only took three nights, aint Linux fun.
BTW the mic works but I cant get enough level to drive the transceiver. Needs more investigation because I would like to use a headset. I drilled a couple of holes in the back panel and wired a 4pin TRRS plug, plugged into the headphone jack out to separate stereo jacks. One for mic and one for amplified speakers. The pinout on the 4pin TRRS plug is; Left speaker = tip, Right speaker = ring 1, Earth = ring 2, Mic = ring 3.Post is under moderationStream item published successfully. Item will now be visible on your stream.
I asked Abhi at Apache Labs if there was any way of upgrading my ANAN-100 up to ANAN-7000DLE level or even just swapping the Hermes board for an Orion MKII board. Unfortunately the answer to both is no. The new radio has a completely different set of boards, so my only upgrade path is to sell the ANAN-100 and buy either a 7000-DLE or a FlexRadio. (Sad face).Post is under moderationStream item published successfully. Item will now be visible on your stream.
Post is under moderationStream item published successfully. Item will now be visible on your stream.
So SmartSDR V2 looks nice. You can now undock some of the control windows or a whole panadapter (receiver). The clever thing is that when you re-dock it to the main screen and later undock it, the window returns to the last place you had it. I like that a lot!
It has integration with the N1MM logger spectrum screen which can display a spectrum similar to the one on SmartSDR (why do we want that?). But the fully integrated N1MM screen can also display the callsigns of stations on the cluster, at the correct places on the spectrum. Hmmm that could be very useful in a contest. BUT it gets better. Any cluster user will know that you will not be able to hear most of the spots listed on the cluster. With this new software you can set a signal strength threshold and the N1MM spectrum will only display spots that you can hear (i.e. the ones that peak above the threshold). I think that is VERY COOL. The N1MM screen integrates well, and it tracks the settings and width of the SmartSDR receiver panadapter, but I think the second screen and display is unnecessary. Why not just put the spot callsigns and threshold line directly on the main panadapter?
There are dozens of tweaks and fixes in the new version, but the other main feature is the (long promised) ability to fully remote control a FlexRadio over the Internet. It uses a cloud server which you have to sign up for (I assume it is free). You can use a Maestro, PC, or Apple device to run SmartSDR remotely to control the radio. But here's the thing! If you paid $1000 extra for the M version of the Flex-6400 or Flex-6600 you would still need a Maestro, PC, or Apple device to run SmartSDR remotely. But if you bought the non-M version plus a Maestro for $1200 you could use it remotely. Something to consider if you are planning on remote operation.Post is under moderationStream item published successfully. Item will now be visible on your stream.
There are no activities here yet