|
Re: Airspy HF+ question
Stephen QRP
Paul
If this is the first time you are trying to flash the HF+, then make sure you have gently removed the lacquer on the pins being shorted. You really might have to send it back to the dealer. Anyway probably best not to use this forum as a proxy for main@..., even though Youssef blocks all hardware failure questions on his forum. I would guess Simon would like to keep his forum for his excellent software issues or questions. Good luck Stephen
|
|
|
|
Re: Airspy HF+ question
Paul Mclaren MM0ZBH
Stephen, Firmware tool doesn't detect it but I know that can be a bit hit and miss as well. Just trying to work out a pattern and was interested in what they orange LED x 3 flash meant as that is with a known working USB so will keep plugging away for now. Regards Paul
On Tue, 19 Mar 2019 at 09:52, Stephen QRP via Groups.Io <stephen_qrp=yahoo.com@groups.io> wrote:
|
|
|
|
Re: Airspy HF+ question
Stephen QRP
Hi Paul
If you have tried everything, then I would flash the firmware using a WIN7 or Win 10 machine.
|
|
|
|
Re: Airspy HF+ question
Dick
On Mon, Mar 18, 2019 at 07:18 PM, George Smythe wrote:
Windows 10 should be no different.And it isn't. Mine runs fine on Windows 10 without any additional drivers. It's blue and orange led's are constantly ON. What you could try is to connect the Airspy HF+ Go to device manager and find the device. With me it shows under "Universal Serial Bus Devices" Select the Airspy HF+ and Uninstall it. Remove the Airspy HF+ Re-insert the Airspy HF+ Now windows should detect it automatically. DO NOT use Zadig!!! Cheers, Dick
|
|
|
|
Re: Airspy HF+ question
George Smythe
Mine works without any added drivers on SDR-Radio 3.03 and Windows 7 (two different laptops). Windows 10 should be no different. I'm using the supplied (noise-suppressing) USB cable.
GSM -> George W. Smythe
jethawk@...
+1 (631) 780-4476
------------------------------------------------------
From: Paul Mclaren MM0ZBH Sent: Mon Mar 18 10:59:48 MST 2019 To: "main@SDR-Radio.groups.io" Subject: Re: [SDR-Radio] Airspy HF+ question
Paul,
It should be plug and play but happy to try anything.
Thanks
Paul
On Mon, 18 Mar 2019, 17:42 Paul Gulliver, <
paulg1953@...> wrote:
|
|
|
|
Re: Airspy HF+ question
Paul Mclaren MM0ZBH
Paul, It should be plug and play but happy to try anything. Thanks Paul
On Mon, 18 Mar 2019, 17:42 Paul Gulliver, <paulg1953@...> wrote:
|
|
|
|
Re: Airspy HF+ question
Paul,
I'm not
sure how similar the HF+ is to "standard" dongles, does it use special drivers
(like Zadig) - W10 seem to like overwriting drivers and causing various
problems.
This
might help here https://www.rtl-sdr.com/forum/viewtopic.php?t=2031
Cheers,
Paul
On
18/03/2019 at 16:43, Paul Mclaren MM0ZBH <paul.mcl@...> wrote:
|
|
|
|
wish list - sattelite passes
M0ZEH <m0zeh@...>
Could you make the passes window columns sortable please. That way I can sort the elevation by highest elevation.
Thanks Steve M0ZEH
|
|
|
|
Airspy HF+ question
Paul Mclaren MM0ZBH
A bit off topic but looking for some Airspy HF+ advice as the Airspy group won't let me ask this question and refer my to ITEAD support who by all accounts don't seem that responsive which is a shame. Anyway the PC my HF+ was connected to has died and testing the HF+ on other Win 10 PC's gives two conflicting results: 1) using the supplied USB cable the Airspy HF+ orange LED flashes three times then stays off. Windows error pops up about "USB device has malfunctioned" and nothing is detected in SDR-Radio Console. 2) using a number of other spare micro USB leads (6+ tried) the Airspy HF+ orange LED comes on and stays on solid orange. Windows error pops up about "USB device has malfunctioned" and nothing is detected in SDR-Radio Console. Any thoughts please. Thanks Paul
|
|
|
|
Re: SDRPlay released new hardware API
#sdrplay
Mark Cayton <mcayton@...>
I don't know squat about API but according to the API 3.02 Release Notes, the Reason for Change is "New AGC scheme, fixes to RSP1 & RSPduo control", so maybe there's something in there that a dev might want to look into.
-- Mark K1LSB
|
|
|
|
Re: Screenshots
Ken Alexander
On Mon, Mar 18, 2019, 01:12 Simon Brown <simon@...> wrote:
|
|
|
|
Re: SDRC v3.06 IQ Recordings/SDR#
Mike Fallon
Oops correction: If you could add support for plain WAV
From: main@SDR-Radio.groups.io [mailto:main@SDR-Radio.groups.io] On Behalf Of Mike Fallon
Sent: 17 March 2019 20:35 To: main@SDR-Radio.groups.io Subject: Re: [SDR-Radio] SDRC v3.06 IQ Recordings/SDR#
OK thank you Simon. I will contact the author but if you could add RF64 support too that would be great. Also, while I’m here, is there still a possibility of adding RDS logging and MPX out (for RDS Spy) please?
Kind regards, Mike
From: main@SDR-Radio.groups.io [mailto:main@SDR-Radio.groups.io] On Behalf Of Simon Brown
Mike,
This is because I moved to WAV RF64 format. I will add support for plain WAV again – maybe next week as part of 3.0.7.
You could always contact the author of the SDR# File Player and ask him / her to add support for WAV RF64.
Simon Brown, G4ELI
From: main@SDR-Radio.groups.io <main@SDR-Radio.groups.io> On Behalf Of Mike Fallon
Hi Simon,
I have just recorded an IQ file in SDRC 3.06, run it through Data Analyser and then attempted to open one of the files in SDR# File Player, as I have always done in the past. This worked fine when recording in SDRC 3.05 and previous versions but now, with 3.06 I get this error message in SDR#. Here are my SDRC Data Analyser general settings and SDRC ‘Start recording’ windows for you to have a look at in case I have something wrong.
Many thanks,
Mike
|
|
|
|
Re: SDRC v3.06 IQ Recordings/SDR#
Mike Fallon
OK thank you Simon. I will contact the author but if you could add RF64 support too that would be great. Also, while I’m here, is there still a possibility of adding RDS logging and MPX out (for RDS Spy) please?
Kind regards, Mike
From: main@SDR-Radio.groups.io [mailto:main@SDR-Radio.groups.io] On Behalf Of Simon Brown
Sent: 17 March 2019 18:12 To: main@SDR-Radio.groups.io Subject: Re: [SDR-Radio] SDRC v3.06 IQ Recordings/SDR#
Mike,
This is because I moved to WAV RF64 format. I will add support for plain WAV again – maybe next week as part of 3.0.7.
You could always contact the author of the SDR# File Player and ask him / her to add support for WAV RF64.
Simon Brown, G4ELI
From: main@SDR-Radio.groups.io <main@SDR-Radio.groups.io> On Behalf Of Mike Fallon
Hi Simon,
I have just recorded an IQ file in SDRC 3.06, run it through Data Analyser and then attempted to open one of the files in SDR# File Player, as I have always done in the past. This worked fine when recording in SDRC 3.05 and previous versions but now, with 3.06 I get this error message in SDR#. Here are my SDRC Data Analyser general settings and SDRC ‘Start recording’ windows for you to have a look at in case I have something wrong.
Many thanks,
Mike
|
|
|
|
Re: Screenshots
toggle quoted messageShow quoted text
From: main@SDR-Radio.groups.io <main@SDR-Radio.groups.io> On Behalf Of Ken Alexander
Hi Simon,
I know you're busy but I'm just wondering if you had a chance to check those screenshots I sent you?
Thanks!
|
|
|
|
Re: SDRC v3.06 IQ Recordings/SDR#
Mike,
This is because I moved to WAV RF64 format. I will add support for plain WAV again – maybe next week as part of 3.0.7.
You could always contact the author of the SDR# File Player and ask him / her to add support for WAV RF64.
Simon Brown, G4ELI
From: main@SDR-Radio.groups.io <main@SDR-Radio.groups.io> On Behalf Of Mike Fallon
Sent: 17 March 2019 17:05 To: main@SDR-Radio.groups.io Subject: [SDR-Radio] SDRC v3.06 IQ Recordings/SDR#
Hi Simon,
I have just recorded an IQ file in SDRC 3.06, run it through Data Analyser and then attempted to open one of the files in SDR# File Player, as I have always done in the past. This worked fine when recording in SDRC 3.05 and previous versions but now, with 3.06 I get this error message in SDR#. Here are my SDRC Data Analyser general settings and SDRC ‘Start recording’ windows for you to have a look at in case I have something wrong.
Many thanks,
Mike
|
|
|
|
SDRC v3.06 IQ Recordings/SDR#
Mike Fallon
Hi Simon,
I have just recorded an IQ file in SDRC 3.06, run it through Data Analyser and then attempted to open one of the files in SDR# File Player, as I have always done in the past. This worked fine when recording in SDRC 3.05 and previous versions but now, with 3.06 I get this error message in SDR#. Here are my SDRC Data Analyser general settings and SDRC ‘Start recording’ windows for you to have a look at in case I have something wrong.
Many thanks,
Mike
|
|
|
|
Re: Using the Es'Hail 2 beacon to correct for LNB drift.
Hi,
More info: https://www.sdr-radio.com/Blog/PostId/56/eshail-2-beacon - available in 3.0.7 in a week or so. Simon Brown, G4ELI www.sdr-radio.com ========================================= Excellent work! David GM8ARV -- SatSignal Software - Quality software for you Web: http://www.satsignal.eu Email: david-taylor@... Twitter: @gm8arv
|
|
|
|
Using the Es'Hail 2 beacon to correct for LNB drift.
Hi,
More info: https://www.sdr-radio.com/Blog/PostId/56/eshail-2-beacon - available in 3.0.7 in a week or so.
Simon Brown, G4ELI
|
|
|
|
Re: OMNIRIG - limited to 2 GHz
ve3dss@...
Henry
Agree but for SDR Console the ability utilize all amateur frequencies with external radios would be the logical way to go. So
like many programs there perhaps could be the option to use omnirig or Hamlib. Note that WSJT-X switched from OMNIRIG to Hamlib and we’ve used FT8 up on 3456 Mhz with ease using the K3 and transverters.
The W3SZ 64bit forked omnirig seems to work fine with programs that can handle the Integer format, as I mentioned.
At any rate, I defer to Simon and his wisdom on all this. He’s truly done an amazing job!!
73 Dana VE3DS
On Mar 17, 2019, at 08:26, Henry via Groups.Io <th444de@...> wrote:
I think we cannot expect that a software calling the IRigX.get_Freq interface (and all the others affected) with 32bit integer parameters will fully work with a forked Omnirig which expects 64bit parameters.
In my opinion it is also impossible that a software re-written for the forked Omnirig can handle installations of the "standard" Omnirig backward compatible. The software will crash because of a memory violence when passing 64bit parameters. I think it would be necessary to provide two versions of the control software. One for the standard Omnirig and one for the forked. Or code a switch which automatically detects which Omnirig is installed. But this is not so easy, I believe. I am not sure if every software author is willing to support an Omnirig version which is not official. 73s, Henry
|
|
|
|
Re: OMNIRIG - limited to 2 GHz
Henry
I think we cannot expect that a software calling the IRigX.get_Freq interface (and all the others affected) with 32bit integer parameters will fully work with a forked Omnirig which expects 64bit parameters.
In my opinion it is also impossible that a software re-written for the forked Omnirig can handle installations of the "standard" Omnirig backward compatible. The software will crash because of a memory violence when passing 64bit parameters. I think it would be necessary to provide two versions of the control software. One for the standard Omnirig and one for the forked. Or code a switch which automatically detects which Omnirig is installed. But this is not so easy, I believe. I am not sure if every software author is willing to support an Omnirig version which is not official. 73s, Henry
|
|
|