|
Re: Just got an Airspy+Discovery..
jdow6:57pm #43231
If a hub is used, a powered hub must be used.
Hi Jdow The hub mentioned was indeed a good quality, powered one that worked successfully with other devices to it's full rated capacity. Best wishes Paul
|
|
|
|
Re: Just got an Airspy+Discovery..
jdow
When that happens to me I usually remark with
chagrin, "The other left."
toggle quoted messageShow quoted text
{O,o} On 20220423 11:57:19, W0LEV wrote:
|
|
|
|
Re: Just got an Airspy+Discovery..
W0LEV
Ooooopppss....the triangle in the upper LEFT, NOT RIGHT DAVE
-- Dave - WØLEV Just Let Darwin Work
|
|
|
|
Re: Just got an Airspy+Discovery..
jdow
If a hub is used, a powered hub must be used.
toggle quoted messageShow quoted text
{^_-} On 20220423 11:46:33, Paul N via
groups.io wrote:
Hi Ed
|
|
|
|
Re: Just got an Airspy+Discovery..
W0LEV
You have to choose the specific radio that is connected.  After the radio is selected, you should see something like the following:  The radio you chose and the serial number should show. Then click the triangle at the upper right to begin. If no error displays, you likely will need to adjust the gains to see anything on the waterfall and spectrum display. Dave - WØLEV
Hello everyone. Well, my first post after getting the above and failing miserably to get it running! It's probably something stupidly obvious but nevertheless it's not visible to me... -- Dave - WØLEV Just Let Darwin Work
|
|
|
|
Re: Just got an Airspy+Discovery..
Hi Ed
welgud@ I clicked on the start arrow and was confronted with an error box in the middle of the screen saying, "No Device Available". Ed This might be a "red herring," but when I first got mine, I attached it via a usb hub and no device appeared. I got patient attention and guidance and prompts from Prog. In a nutshell, there was no (blue led showing) indicating no connection. Re-plugged into dedicated usb port and hey presto - problem solved that simply. Whatever your problem, I'm sure you'll sort it. Best Wishes Pauk
|
|
|
|
Re: Just got an Airspy+Discovery..
Hello Ed let us know if you see the device (usb) in Windows Device Manager Paul
On Apr 23, 2022, at 2:15 PM, welgud via groups.io <welgud@...> wrote:
|
|
|
|
Just got an Airspy+Discovery..
Ed.
Hello everyone. Well, my first post after getting the above and failing miserably to get it running! It's probably something stupidly obvious but nevertheless it's not visible to me...
I downloaded the zip file,. (SDR# from the home site), unzipped the download and was confronted by the list of unzipped files. So far so good. I couldn't see a, ".EXE" file so double clicked on the "SDRSharp" application file. Things were looking good with bits of relevant text flashing up and the the radio graphic was displayed in all its' splendour. I clicked on the start arrow and was confronted with an error box in the middle of the screen saying, "No Device Available". Much plugging and un-plugging ensued plus re-downloading and un-zipping also trying on another Windows 10 machine with the same result!! Could someone put me straight on this please - quite frustrating after the anticipation. I have a Winradio Receiver, now a few years old but wanted to try a more modern device. We live and learn (apparently). Any assistance much appreciated. Cheers. Ed G0AQI
|
|
|
|
Re: Airspy R2
#airspyr2
Isaiah B
Ignore the mode being NFM I had started SDR# up just to get a picture of the settings.
If I set the step to 25kHz for step size I miss a crap ton of traffic that it just scans over. The saved frequency is only there for # reference. I dont use it for anything. And yes I do know how frequency tolerances and all that work. I am a amateur radio operator. If I put a RTL SDR on scan it will have 0 issues with alignment or anything which is how I know its a airspy issue not a airband issue
|
|
|
|
Re: Spyserver network - has a free DNS provider had problems?
tony mann
"Looking at the Spyserver network map either as a web page or from within SDR#, the majority of global nodes are marked as unreachable, mine amongst them. This has been the case for a number of days."
That's what I found too - a sea of yellow and red. Something's amiss but I don't know what the cause is. Tony
|
|
|
|
Re: Airspy R2
#airspyr2
jdow
0.5 what? -0.1 what? You're making it bloody
difficult to help you, you should know.
toggle quoted messageShow quoted text
Do you understand anything about frequency tolerances and how to calculate them? If you EVER encounter a signal that tunes dead center in a receiver passband with zero error and without slight levels of tuning it's time for a serious visit to Las Vegas because you just spectacularly beat the odds. Give numbers and units on the numbers. Otherwise I, for one, will just leave you to flounder your way through life. (Can you tell I am quite frustrated with how obtuse you are being?) {+_+} On 20220421 21:41:54, Isaiah B wrote:
Every frequency has a different offset one could it +0.5 next could be -0.10
|
|
|
|
Re: Airspy R2
#airspyr2
Airspy US
2 should read:
--------- Airspy.USYour USA source for quality SDR products! www.Airspy.US NOTE: This email address is NOT MONITORED. If you want to email us use our normal email address. On Apr 22, 2022, at 1:33 AM, Airspy US via groups.io <airspy_us@...> wrote:
|
|
|
|
Re: Airspy R2
#airspyr2
Airspy US
We see at least 3 issues:
toggle quoted messageShow quoted text
1. Why are you using NFM in the airband? 2. Your saved frequencies are on on-frequency. 3. Your step is 8.33 kHz. That means your first step will be 33.333 Hz low, the second will be 66.666, etc. At 100 steps (about 800 kHz from the bottom) you will be 3.3333 kHz off. This error will continue to add up through the band. Set the step to 8.3333333 kHz get as accurate as you can, or better yet if you are in the USA just use a step size of 25 kHz and you will be right on each frequency. --------- Airspy.USYour USA source for quality SDR products! www.Airspy.US NOTE: This email address is NOT MONITORED. If you want to email us use our normal email address.
On Apr 22, 2022, at 12:42 AM, Isaiah B <ibertrang@...> wrote:
|
|
|
|
Re: Airspy R2
#airspyr2
Simon Byrnand <sbyrnand@...>
On Fri, Apr 22, 2022 at 05:41 AM, Isaiah B wrote:
Every frequency has a different offset one could it +0.5 next could be -0.10 Airband radios in planes and control towers are not frequency reference standards. Some can be significantly off frequency. Do not try to judge the calibration of your device using airband. When I try to run the AirspyCalibrate.exe it does nothing, not sure about firmware updatesIf you pressed the Clear or Calibrate buttons in the AirspyCalibrate.exe application you have now destroyed your factory calibration, and unless you have a suitable reference signal, this calibration cannot be recovered using the same utility. This utility is very dangerous. Please see this thread to see why it is so dangerous: https://groups.io/g/airspy/topic/88805373 If you launch AirspyCalibrate and do NOT press any buttons, what is the large PPM figure reported at the bottom ? Regards, Simon
|
|
|
|
Re: Airspy R2
#airspyr2
Isaiah B
Every frequency has a different offset one could it +0.5 next could be -0.10
After more messing around with SDR# & the R2 I am now noticing this is only happening on airband VHF channels and 1G channels. SDR# Settings - https://i.imgur.com/5LztXlO.png Frequency Manager & Scanner - https://i.imgur.com/KmUIFAu.png Frequency Scanner Ranges - https://i.imgur.com/v1wSHab.png When I try to run the AirspyCalibrate.exe it does nothing, not sure about firmware updates
|
|
|
|
Re: Airspy R2
#airspyr2
Here in the USA, we are operating on 25kHz spacing.
ATC may advise me "Contact Boston Center on 134 decimal 42, good day..." On the B-737NG, I would tune 134.42 in the standby window, and press the XFER button to make it active. In reality, I have tuned 134.425 MHz, not 134.420 MHz! My display doesn't read out to the 3rd digit. On my former aircraft, the B-777-200, I would tune 134.425 in the standby window and press XFER, since there is no 134.420... the tuning jumps from 134.400 to 134.425 and it does read out to the third digit. But since the image was SOOOOO small, nobody can tell what the graduations are. BTW... Listening to Boston Center frequency right now on 134.425, I can just barely make out their carrier (too far from TXR). It does appear to be slightly low. But... I'm watching aircraft check in and they are all within +/-1 kHz of 134.425MHz. Tuning panel differences: https://imgur.com/t2wqRSf SDRC Screenshot on my R2: https://imgur.com/LkRBwzn 73 Kriss KA1GJU
|
|
|
|
Re: Airspy R2
#airspyr2
jdow
Without numbers diagnosis is out of the question.
toggle quoted messageShow quoted text
Note that there are equipment tolerances on AirSpy AND the aircraft radios in question. {^_^} On 20220421 07:07:16, Airspy US via
groups.io wrote:
It should be calibrated then. Can you post a full screenshot including settings? The one you posted shows very little. Did you try to recalibrate it after receipt?
|
|
|
|
Re: Airspy R2
#airspyr2
I don’t know about scanning, but I use the excellent AirSpy R2 on SDR# to monitor 4 fixed frequencies in the 160MHz railroad band. When I start SDR# after a reboot I find that I must tweak the frequency off channel, then right back again to ensure that it is in fact receiving on the displayed frequency. If I don’t do this, stations show up approximately 1KC low.
It sounds very much like your problem, so I’m just adding a data point.
Bote Man http://www.botecomm.com/bote/radio/streaming.html
From: Isaiah B
Sent: Wednesday, 20 April, 2022 23:25 To: airspy@groups.io Subject: [airspy] Airspy R2 #airspyr2
Good evening,
|
|
|
|
Re: Airspy R2
#airspyr2
Martin Smith
If it is the Airband and 8.3333kHz channel spacing, there is a "step" pull down at the top of SDR# you could change this from 5kHz to 8.3333kHz as the step size while on airband. Or toggle off "snap".
Or you could make a backup copy of and edit the BandPlan.xml file to change "Air Band Voice" from a step of "5000" Hz to a step of "8333", that might be a solution ?
|
|
|
|
Re: Airspy R2
#airspyr2
Martin Smith
On Thu, Apr 21, 2022 at 02:45 PM, Isaiah B wrote:
My first assumption would be to check all my assumptions. The very first would be that the signal is actually being broadcast at the frequency that you think it should be. The only information I can possibly discern from your screen sliver is that the frequency might be on the airband. Some channels on the airband are spaced 8.33 kHz apart, are you allowing for that ? There is not enough information to tell me what frequency you are tuned to, nor the exact frequency that the signal is at, I only know that the signal is somewhere less than 126.30 MHz. But it is also entirely possible that you are using a spyverter and 126.30 Mhz is really 6.30 MHz ?
|
|
|
