Date   

locked Understanding USB and PC noise

robertcharris@...
 

USB cables radiate considerable noise greatly raising the background noise floor  gawd awful to say the least.  EBAY is one source having listings of triple shielded USB to Micro cables, some as short at 6 inches.  What a difference a cable makes!  Background noise radiated from the USB cable is practically non existent.  Now the downside:  A simple long wire antenna readily picks up considerable noise, even from the short triple shielded USB cable in close proximity to the USB cable.  I've enjoyed great success drastically (understatement)  reducing USP cable noise feeding the Airspy HF+ with a Mini Whip placed at some distance away from the receiver and laptop computer feeding the Airspy HF+.  To put this is perspective---the original unshielded cable radiates noise so severely, that the considerable noise is transmitted to the mini whip placed fifty feet away.  By the way, ferrite "clampons" have proven useless in reducing USB cable noise radiation. Last, but not least, ditch the switching power adapters for powering the laptop.  These things are a disaster in terms of noise.  Go battery power and a laptop computer if possible. Another suggestion, turn off the AGC and add reduce gain on the slider control.  There is a point at which "spurs" across the visible spectrum suddenly disappear if IMD (false signals) is taking place. (Eliminate the noise, and what a pleasure it is listening around to high quality signal content!


Re: Playing with the Airspy R820T IF bandwidth

TLeconte <thierry.leconte@...>
 

Just for information :
My two  programs  for airspy : acarsdec and vdlm2dec  now set the R820T tuner bandwidth according to the listened frequencies , thanks to the measurements described above.


Re: Unable to install Airspy HF+ on windows 7 or windows 8.1 #airspyhfplus

jdow
 

BTW - you still haven't found your honest man. I'm not a man.
{O,o}


Re: Unable to install Airspy HF+ on windows 7 or windows 8.1 #airspyhfplus

jdow
 

Hm, sometimes machines act funny. Anyway....

(Pumps fist in the air metaphorically) Yay! You got it working!

{^_-}

On 20180415 03:37, diogenes@tinfoilcat.com wrote:
I did as suggested below and managed  to get the unit working. Thank you to all who tried to help with the problem. As to your question about the instructions I used when first installing the unit. They were those at https://airspy.com/quickstart/
As far as I am concerned now the problem has been solved.

> That said he might get lucky in Device Manager. Select the "WinUSB
> Generic
> Device" you found. Right click. Select "Uninstall Device". Unplug the
> ASHF+ and
> plug it back in a few seconds later. Then see what happens. If this
> does not
> work use "Uninstall Device" and then Install the compatibility driver.
> This
> might work. Otherwise a system restore point is your best friend here.
> (Those
> familiar with the "inf" folder can search the files for the .inf file
> that
> configures the dongle and delete it. But that is normally a high risk
> endeavor.)
>
> All that said I'll ask a stupid question. What instructions did you
> use when
> installing the dongle?
>
> {^_^}
>
> On 20180414 12:23, Joe M. wrote:
>> I believe it's the report you posted that is suggesting Zadig was
>> used since
>> that is the driver that is installed.
>>
>> Others are simply telling you what the report is saying.
>>
>> Regardless, that seems to be the problem.
>>
>> Joe M.
>>
>> On 4/14/2018 8:07 AM, diogenes@tinfoilcat.com wrote:
>>> Hello Alan,
>>>
>>> Are you suggesting I used Zadig (I have no idea what it is) I
>>> simply
>>> plugged the AHF+ into a USB port and I have already explained what
>>> happened then. When it would not work I downloaded the WinUSB
>>> Compatibilty
>>> Driver and followed the online instructions and it still would not
>>> work.
>>> Apart from trying it on three different pcs and also trying the USB
>>> cable
>>> from my AS that is all I have done. Peter
>>>
>>>>> libwdi means someone had the bright idea to use Zadig for the
>>>>> HF+.
>>>>> Unsupported scenario: There's no uninstaller for that driver.
>>>>> Only
>>>>> remaining advice: Fix your drivers and NEVER improvise.
>>>>
>>>> If that is true, you used Zadig then maybe prog could be a little
>>>> more
>>>> helpful.
>>>>
>>>> DO NOT USE ZADIG. If Zadig has been used to install the drivers
>>>> the best
>>>> thing might be to use "System Restore" to a point before it was
>>>> used. Or
>>>> go to Device Manager. Delete drivers. Then hopefully it should
>>>> then
>>>> automatically install the correct drivers. If not use the proper
>>>> one you
>>>> downloaded.
>>>>
>>>> 73 Alan G4ZFQ
>>
>>
>>
>>
>
>
>
>
>


Re: Unable to install Airspy HF+ on windows 7 or windows 8.1 #airspyhfplus

diogenes@...
 

I did as suggested below and managed  to get the unit working. Thank you to all who tried to help with the problem. As to your question about the instructions I used when first installing the unit. They were those at https://airspy.com/quickstart/
As far as I am concerned now the problem has been solved.

> That said he might get lucky in Device Manager. Select the "WinUSB
> Generic
> Device" you found. Right click. Select "Uninstall Device". Unplug the
> ASHF+ and
> plug it back in a few seconds later. Then see what happens. If this
> does not
> work use "Uninstall Device" and then Install the compatibility driver.
> This
> might work. Otherwise a system restore point is your best friend here.
> (Those
> familiar with the "inf" folder can search the files for the .inf file
> that
> configures the dongle and delete it. But that is normally a high risk
> endeavor.)
>
> All that said I'll ask a stupid question. What instructions did you
> use when
> installing the dongle?
>
> {^_^}
>
> On 20180414 12:23, Joe M. wrote:
>> I believe it's the report you posted that is suggesting Zadig was
>> used since
>> that is the driver that is installed.
>>
>> Others are simply telling you what the report is saying.
>>
>> Regardless, that seems to be the problem.
>>
>> Joe M.
>>
>> On 4/14/2018 8:07 AM, diogenes@... wrote:
>>> Hello Alan,
>>>
>>> Are you suggesting I used Zadig (I have no idea what it is) I
>>> simply
>>> plugged the AHF+ into a USB port and I have already explained what
>>> happened then. When it would not work I downloaded the WinUSB
>>> Compatibilty
>>> Driver and followed the online instructions and it still would not
>>> work.
>>> Apart from trying it on three different pcs and also trying the USB
>>> cable
>>> from my AS that is all I have done. Peter
>>>
>>>>> libwdi means someone had the bright idea to use Zadig for the
>>>>> HF+.
>>>>> Unsupported scenario: There's no uninstaller for that driver.
>>>>> Only
>>>>> remaining advice: Fix your drivers and NEVER improvise.
>>>>
>>>> If that is true, you used Zadig then maybe prog could be a little
>>>> more
>>>> helpful.
>>>>
>>>> DO NOT USE ZADIG. If Zadig has been used to install the drivers
>>>> the best
>>>> thing might be to use "System Restore" to a point before it was
>>>> used. Or
>>>> go to Device Manager. Delete drivers. Then hopefully it should
>>>> then
>>>> automatically install the correct drivers. If not use the proper
>>>> one you
>>>> downloaded.
>>>>
>>>> 73 Alan G4ZFQ
>>
>>
>>
>>
>
>
>
>
>


Re: ADSB SpyHelp Please

Martin Smith
 

On Fri, Apr 13, 2018 at 04:29 pm, <robert_eddy@iinet.net.au> wrote:


What additional information/ data comes from sdrsharp.com?
As far as I know know none, you are uploading your local ADSB data to that site which would mean that you did not need a local copy of virtual radar server or planeplotter running, that you used to be able to just point a web browser there and see your local planes (and everyone elses local planes aggregated).

And FYI (For Your Information) a port number typically has software bound to it offering a service. An IP address can be pinged (accessable via ICMP packets), but yet have no open ports running any services. Port 80 would typically be http (TCP) webserver, port 443 would typically be https(TCP) slightly secure webserver, port 25 would be SMTP(TCP) email transfers, port 22 would be SSH(TCP) Secure SHell, port 123 would NTP(UDP) Network Time Protocol, .... and so on for all ports, from port number zero up to 65535. If there is no software listening/bound to a specific port number then that service is not acessable or is not available. You could think of an IP address like the physical location of a hotel with 65k rooms, if there is no one in the room who speaks the same protocol that your client expects then no data can be transferred in either direction. Anyhow networking is complex and nothing really to do with SDR. But to summarise: ping may work while no ports are open, but tcptraceroute will may work when ICMP/UDP packets are blocked by firewalls (used by ping and/or traceroute). Just because a machine is pingable does not mean that it has any specific service running, it just means that the remote machine is powered up on the network and ICMP packets are not blocked by any firewalls between your machine and that remote machine.


Re: Unable to install Airspy HF+ on windows 7 or windows 8.1 #airspyhfplus

jdow
 

That said he might get lucky in Device Manager. Select the "WinUSB Generic Device" you found. Right click. Select "Uninstall Device". Unplug the ASHF+ and plug it back in a few seconds later. Then see what happens. If this does not work use "Uninstall Device" and then Install the compatibility driver. This might work. Otherwise a system restore point is your best friend here. (Those familiar with the "inf" folder can search the files for the .inf file that configures the dongle and delete it. But that is normally a high risk endeavor.)

All that said I'll ask a stupid question. What instructions did you use when installing the dongle?

{^_^}

On 20180414 12:23, Joe M. wrote:
I believe it's the report you posted that is suggesting Zadig was used since
that is the driver that is installed.
Others are simply telling you what the report is saying.
Regardless, that seems to be the problem.
Joe M.
On 4/14/2018 8:07 AM, diogenes@tinfoilcat.com wrote:
Hello Alan,
Are you suggesting I used Zadig (I have no idea what it is) I simply plugged the AHF+ into a USB port and I have already explained what happened then. When it would not work I downloaded the WinUSB Compatibilty
Driver and followed the online instructions and it still would not work.
Apart from trying it on three different pcs and also trying the USB cable
from my AS that is all I have done. Peter

libwdi means someone had the bright idea to use Zadig for the HF+. Unsupported scenario: There's no uninstaller for that driver. Only
remaining advice: Fix your drivers and NEVER improvise.
If that is true, you used Zadig then maybe prog could be a little more helpful.
DO NOT USE ZADIG. If Zadig has been used to install the drivers the best
thing might be to use "System Restore" to a point before it was used. Or
go to Device Manager. Delete drivers. Then hopefully it should then
automatically install the correct drivers. If not use the proper one you
downloaded.
73 Alan G4ZFQ


Re: Is the RSSI % value valid in the new ADS-B Spy Rev 38 ??? Rev 37 made more sense...

jdow
 

I don't know ADSB Spy at all these days. However, I do find setting the gain on an AirSpy to 100% to be rather cringeworthy. I'd reduce the gain to 1/2 and see what happens. Then move it to 3/4 and see if it improves. If it doesn't move to 1/4 and see how it works. Divide the steps by two and repeat over the smaller range until you get the gain setting that works best.

{^_^}

On 20180414 07:18, Bernard Nicoll wrote:
I just installed Rev 38 of ADS-B. Although the performance and coverage is the same as Rev 37, the value indicated by RSSI gauge makes no sense anymore. In Rev 37 I got at least > %70 of RSSI.
Anybody else experiencing the same behavior?
Thanks.


Re: Unable to install Airspy HF+ on windows 7 or windows 8.1 #airspyhfplus

Gary
 

I can only comment from my own experience with the AirspyHF+, when I first got mine, l also thought it had a problem. The ‘fix’ was that the micro-usb connection on the cable to the AirspyHF+ was not seated good and once I made sure it was plugged in all the way, it worked perfectly. A small thing I know, but sometimes it the small thing that causes a problem.

Gary, W5GGH

On Saturday, April 14, 2018, 2:23 PM, Joe M. <mch@...> wrote:

I believe it's the report you posted that is suggesting
Zadig was used since that is the driver that is installed.

Others are simply telling you what the report is saying.

Regardless, that seems to be the problem.

Joe M.

On 4/14/2018 8:07 AM, diogenes@... wrote:
> Hello Alan,
>
> Are you suggesting I used Zadig (I have no idea what it is) I simply
> plugged the AHF+ into a USB port and  I have already explained what
> happened then. When it would not work I downloaded the WinUSB
> Compatibilty Driver and followed the online instructions and it still
> would not work. Apart from trying it on three different pcs and also
> trying the USB cable from my AS that is all I have done.
> Peter
>
>  >> libwdi means someone had the bright idea to use Zadig for the HF+.
>  >> Unsupported scenario: There's no uninstaller for that driver.
>  >> Only remaining advice: Fix your drivers and NEVER improvise.
>  >
>  > If that is true, you used Zadig then maybe prog could be a little more
>  > helpful.
>  >
>  > DO NOT USE ZADIG.
>  > If Zadig has been used to install the drivers the best thing might be
>  > to
>  > use "System Restore" to a point before it was used. Or go to Device
>  > Manager. Delete drivers. Then hopefully it should then automatically
>  > install the correct drivers. If not use the proper one you downloaded.
>  >
>  > 73 Alan G4ZFQ





Re: Unable to install Airspy HF+ on windows 7 or windows 8.1 #airspyhfplus

Joe M.
 

I believe it's the report you posted that is suggesting
Zadig was used since that is the driver that is installed.

Others are simply telling you what the report is saying.

Regardless, that seems to be the problem.

Joe M.

On 4/14/2018 8:07 AM, diogenes@tinfoilcat.com wrote:
Hello Alan,

Are you suggesting I used Zadig (I have no idea what it is) I simply
plugged the AHF+ into a USB port and I have already explained what
happened then. When it would not work I downloaded the WinUSB
Compatibilty Driver and followed the online instructions and it still
would not work. Apart from trying it on three different pcs and also
trying the USB cable from my AS that is all I have done.
Peter

>> libwdi means someone had the bright idea to use Zadig for the HF+.
>> Unsupported scenario: There's no uninstaller for that driver.
>> Only remaining advice: Fix your drivers and NEVER improvise.
>
> If that is true, you used Zadig then maybe prog could be a little more
> helpful.
>
> DO NOT USE ZADIG.
> If Zadig has been used to install the drivers the best thing might be
> to
> use "System Restore" to a point before it was used. Or go to Device
> Manager. Delete drivers. Then hopefully it should then automatically
> install the correct drivers. If not use the proper one you downloaded.
>
> 73 Alan G4ZFQ


Re: Unable to install Airspy HF+ on windows 7 or windows 8.1 #airspyhfplus

Pete Smith <n4zr@...>
 

I think a part of the problem is that for those of us who were raised on yahoogroups or contesting.com reflectors, the idea of a wiki even existing within the group structure is less than obvious.

73, Pete N4ZR
Check out the Reverse Beacon Network 
at <http://reversebeacon.net>, now 
spotting RTTY activity worldwide. 
For spots, please use your favorite 
"retail" DX cluster.
On 4/14/2018 1:26 PM, David Ranch wrote:

Hey Joanne,

This is a solid start to what I'd say should be in the wiki at:

   https://airspy.groups.io/g/main/wiki/home

At some point, we should point users to the Wiki to get their answers FIRST before posting a message as we generally cover the same topics over and over.  Anyway, I think if we all try to focus a little more on the Wiki and a little more less on emails, I think getting something substantial would be good.  Would you be willing to copy / paste this very email into a new Wiki entry for something like "My Airspy isn't being recognized" and others can then chime in with more details, tips, etc.  If you're too busy and you're ok with a copy /paste of your email, I can put it into the wiki for you.

Thoughts?

--David
KI6ZHD


On 04/13/2018 02:55 PM, jdow wrote:
If the other suggestions didn't help let's dig in a little deeper. Unplug ASHF+.
* Bring up Device Manager.
     Right click on "Computer". Select Properties at the bottom of the list of selections in the popup menu. On the big dialog that pops up select on the left "Device Manager" hotlink top of the left hand column.

* On the Device manager tree view note if anything appears under a "Ports (COM & LPT)" selection if it exists and under a "Universal Serial Bus devices" selection if it exists. (Expand them.)

* Now plug in the ASHF+.

* The Device Manager view should automatically refresh after a few moments. If it doesn't then it may be defective.

* Check if anything appears under "Universal Serial Bus devices". If so check what name it shows and note to the list about. You should expect "AIRSPY HF+" if everything is happy. But I suspect that won't be what you see.

* Check if anything appears under "Ports (COM & LPT)". If it does then an unprogrammed unit escaped manufacturing. This can probably be repaired "at home" fairly easily. Note the port which appears and let the list know. One of us can tell you in detail what to do in this case. (I'd try downloading the latest driver. Then pulling apart the "Flash.bat" file that comes wit it so I could manually perform the actual programming step manually. But if this is your problem listen to any advice from "prog" or "AirSpyUS" first rather than experimenting.)

* If nothing appeared then if you are patient you can look for changes elsewhere in the Device Manager that might be the ASHF+ appearing as something it shouldn't. Report what you find to the list.

So first you are looking to see if the USB system recognizes the device. If it doesn't a hardware repair is needed. If Device Manager refreshes then look for the appearance of AIRSPY HF+ in Device Manager under AIRSPY HF+ as a "Universal Serial Bus device". If it appears then the programs you are using have a problem. If AIRSPY HF+ does not appear then look for it to appear as a serial communications device. If that appears it means the ASHF+ hardware is showing its programming interface. If that is the case report it here and follow advice from Youssef (prog) or AirSpyHF+ (the US distributor.) I'd not right off recommend being fearless and manually programming the device right off. There might be some special event that must take place for an initial programming.

{^_^}  Joanne



Re: Unable to install Airspy HF+ on windows 7 or windows 8.1 #airspyhfplus

David Ranch
 

Hey Joanne,

This is a solid start to what I'd say should be in the wiki at:

   https://airspy.groups.io/g/main/wiki/home

At some point, we should point users to the Wiki to get their answers FIRST before posting a message as we generally cover the same topics over and over.  Anyway, I think if we all try to focus a little more on the Wiki and a little more less on emails, I think getting something substantial would be good.  Would you be willing to copy / paste this very email into a new Wiki entry for something like "My Airspy isn't being recognized" and others can then chime in with more details, tips, etc.  If you're too busy and you're ok with a copy /paste of your email, I can put it into the wiki for you.

Thoughts?

--David
KI6ZHD


On 04/13/2018 02:55 PM, jdow wrote:
If the other suggestions didn't help let's dig in a little deeper. Unplug ASHF+.
* Bring up Device Manager.
     Right click on "Computer". Select Properties at the bottom of the list of selections in the popup menu. On the big dialog that pops up select on the left "Device Manager" hotlink top of the left hand column.

* On the Device manager tree view note if anything appears under a "Ports (COM & LPT)" selection if it exists and under a "Universal Serial Bus devices" selection if it exists. (Expand them.)

* Now plug in the ASHF+.

* The Device Manager view should automatically refresh after a few moments. If it doesn't then it may be defective.

* Check if anything appears under "Universal Serial Bus devices". If so check what name it shows and note to the list about. You should expect "AIRSPY HF+" if everything is happy. But I suspect that won't be what you see.

* Check if anything appears under "Ports (COM & LPT)". If it does then an unprogrammed unit escaped manufacturing. This can probably be repaired "at home" fairly easily. Note the port which appears and let the list know. One of us can tell you in detail what to do in this case. (I'd try downloading the latest driver. Then pulling apart the "Flash.bat" file that comes wit it so I could manually perform the actual programming step manually. But if this is your problem listen to any advice from "prog" or "AirSpyUS" first rather than experimenting.)

* If nothing appeared then if you are patient you can look for changes elsewhere in the Device Manager that might be the ASHF+ appearing as something it shouldn't. Report what you find to the list.

So first you are looking to see if the USB system recognizes the device. If it doesn't a hardware repair is needed. If Device Manager refreshes then look for the appearance of AIRSPY HF+ in Device Manager under AIRSPY HF+ as a "Universal Serial Bus device". If it appears then the programs you are using have a problem. If AIRSPY HF+ does not appear then look for it to appear as a serial communications device. If that appears it means the ASHF+ hardware is showing its programming interface. If that is the case report it here and follow advice from Youssef (prog) or AirSpyHF+ (the US distributor.) I'd not right off recommend being fearless and manually programming the device right off. There might be some special event that must take place for an initial programming.

{^_^}  Joanne


Is the RSSI % value valid in the new ADS-B Spy Rev 38 ??? Rev 37 made more sense...

Bernard Nicoll <bernard.nicoll@...>
 

I just installed Rev 38 of ADS-B. Although the performance and coverage is the same as Rev 37, the value indicated by RSSI gauge makes no sense anymore. In Rev 37 I got at least > %70 of RSSI.
Anybody else experiencing the same behavior?
Thanks.


Re: Improved File Player for SDR#

Paul <aceblaggard@...>
 

It's working OK for me Andy on V1664, I would say that it's very sensitive to vertical mouse movement during the click which causes it to zoom to an impossibly small portion of the file and right mouse clicking just reloads the preview panel each time, regardless of whether it's already in full file display.

It's a really useful addition although I would liked to have seen the preview window have a zoom and scroll function to save playing the file in small chunks to spot brief signals such as MS but hats off to Vasily for another great plug in.

Paul


Re: Unable to install Airspy HF+ on windows 7 or windows 8.1 #airspyhfplus

Alan G4ZFQ
 

Are you suggesting I used Zadig (I have no idea what it is)
Peter,

No, not me "prog" the actual software writer and developer of the HF+ said "libwdi means someone had the bright idea to use Zadig for the HF+."
Which was accusing you of doing this.
As you do not even know what Zadig is then he was wrong. [Zadig is a driver installer for other devices, notably the RTL SDR.]
Sorry, you seem to have done all the correct things. I hope prog comes up with an answer. "libwdi" must have come from somewhere else.

73 Alan G4ZFQ

I simply plugged the AHF+ into a USB port and  I have already explained what happened then. When it would not work I downloaded the WinUSB Compatibilty Driver and followed the online instructions and it still would not work. Apart from trying it on three different pcs and also trying the USB cable from my AS that is all I have done.
>> libwdi means someone had the bright idea to use Zadig for the HF+.
>> Unsupported scenario: There's no uninstaller for that driver.
>> Only remaining advice: Fix your drivers and NEVER improvise.


Re: Unable to install Airspy HF+ on windows 7 or windows 8.1 #airspyhfplus

diogenes@...
 

Hello Alan,

Are you suggesting I used Zadig (I have no idea what it is) I simply plugged the AHF+ into a USB port and  I have already explained what happened then. When it would not work I downloaded the WinUSB Compatibilty Driver and followed the online instructions and it still would not work. Apart from trying it on three different pcs and also trying the USB cable from my AS that is all I have done.
Peter

>> libwdi means someone had the bright idea to use Zadig for the HF+.
>> Unsupported scenario: There's no uninstaller for that driver.
>> Only remaining advice: Fix your drivers and NEVER improvise.
>
> If that is true, you used Zadig then maybe prog could be a little more
> helpful.
>
> DO NOT USE ZADIG.
> If Zadig has been used to install the drivers the best thing might be
> to
> use "System Restore" to a point before it was used. Or go to Device
> Manager. Delete drivers. Then hopefully it should then automatically
> install the correct drivers. If not use the proper one you downloaded.
>
> 73 Alan G4ZFQ
>
>
>
>
>


Re: Unable to install Airspy HF+ on windows 7 or windows 8.1 #airspyhfplus

Alan G4ZFQ
 

libwdi means someone had the bright idea to use Zadig for the HF+. Unsupported scenario: There's no uninstaller for that driver.
Only remaining advice: Fix your drivers and NEVER improvise.
If that is true, you used Zadig then maybe prog could be a little more helpful.

DO NOT USE ZADIG.
If Zadig has been used to install the drivers the best thing might be to use "System Restore" to a point before it was used. Or go to Device Manager. Delete drivers. Then hopefully it should then automatically install the correct drivers. If not use the proper one you downloaded.

73 Alan G4ZFQ


Re: Unable to install Airspy HF+ on windows 7 or windows 8.1 #airspyhfplus

prog
 

On Sat, Apr 14, 2018 at 02:37 am, jdow wrote:
I hope that is enough diagnostic information for Youssef and his crew. I've not seen that report ever.

{^_^}
libwdi means someone had the bright idea to use Zadig for the HF+. Unsupported scenario: There's no uninstaller for that driver.
Only remaining advice: Fix your drivers and NEVER improvise.


Re: Unable to install Airspy HF+ on windows 7 or windows 8.1 #airspyhfplus

jdow
 

I hope that is enough diagnostic information for Youssef and his crew. I've not seen that report ever.

{^_^}

On 20180414 01:43, diogenes@tinfoilcat.com wrote:
Thank you Joanne,
I followed your instructions and find that the device pops up as;
Universal Serial Bus Device
     WinUSB Generic Device
It says it is working properly.
Driver Provider libusb.info
Driver Date       18/06/2013
Driver Version   6.1.7600.16385
Digital Signer    USB\MS_COMP_WINUSB (lbwdi autogenerated)
I hope that with this information someone can tell me what needs to be done.
Peter

> If the other suggestions didn't help let's dig in a little deeper.
> Unplug ASHF+.
> * Bring up Device Manager.
> Right click on "Computer". Select Properties at the bottom of
> the list of
> selections in the popup menu. On the big dialog that pops up select on
> the left
> "Device Manager" hotlink top of the left hand column.
>
> * On the Device manager tree view note if anything appears under a
> "Ports (COM &
> LPT)" selection if it exists and under a "Universal Serial Bus
> devices"
> selection if it exists. (Expand them.)
>
> * Now plug in the ASHF+.
>
> * The Device Manager view should automatically refresh after a few
> moments. If
> it doesn't then it may be defective.
>
> * Check if anything appears under "Universal Serial Bus devices". If
> so check
> what name it shows and note to the list about. You should expect
> "AIRSPY HF+" if
> everything is happy. But I suspect that won't be what you see.
>
> * Check if anything appears under "Ports (COM & LPT)". If it does then
> an
> unprogrammed unit escaped manufacturing. This can probably be repaired
> "at home"
> fairly easily. Note the port which appears and let the list know. One
> of us can
> tell you in detail what to do in this case. (I'd try downloading the
> latest
> driver. Then pulling apart the "Flash.bat" file that comes wit it so I
> could
> manually perform the actual programming step manually. But if this is
> your
> problem listen to any advice from "prog" or "AirSpyUS" first rather
> than
> experimenting.)
>
> * If nothing appeared then if you are patient you can look for changes
> elsewhere
> in the Device Manager that might be the ASHF+ appearing as something
> it
> shouldn't. Report what you find to the list.
>
> So first you are looking to see if the USB system recognizes the
> device. If it
> doesn't a hardware repair is needed. If Device Manager refreshes then
> look for
> the appearance of AIRSPY HF+ in Device Manager under AIRSPY HF+ as a
> "Universal
> Serial Bus device". If it appears then the programs you are using have
> a
> problem. If AIRSPY HF+ does not appear then look for it to appear as a
> serial
> communications device. If that appears it means the ASHF+ hardware is
> showing
> its programming interface. If that is the case report it here and
> follow advice
> from Youssef (prog) or AirSpyHF+ (the US distributor.) I'd not right
> off
> recommend being fearless and manually programming the device right
> off. There
> might be some special event that must take place for an initial
> programming.
>
> {^_^} Joanne
>
> On 20180413 05:29, diogenes@tinfoilcat.com wrote:
>> Hello,
>> I have spent two days trying to install this device. The driver is
>> the problem
>> it did not install via windows as the installation instructions
>> suggested so I
>> downloaded the _WinUSB Compatibility Driver _ which was no help at
>> all. I have
>> so far tried 3 different machines with the same result. I have
>> searched the
>> group but none of the comments I have seen help me. Can anyone give
>> me
>> straightforward instructions as to how to get this radio working?
>> Peter
>
>
>
>
>
>


Re: ADSBSpy Output format

prog
 

So, Rob Malcolm helped checking, improving and fixing a few things in ADSBSpy and its cli counterpart, airspy_adsb. We just compared this morning vs. FlightRadar24's receiver (our reference benchmark) using Jetvision's ADSB Active Diapason antenna, and could conclude a significant improvement of successful frame decodes could be made. This translated in smoother updates and more aircraft of the map. The ratio of false positives is not degraded. Thanks Rob!

The new updates are available on download: http://airspy.com/download

11301 - 11320 of 39948