[hpsdr] Resurrecting Old Setup - establish Ozy/Mercury USB control

craig heatingengineer at cfl.rr.com
Tue May 19 11:48:31 PDT 2020 

Sorry if communications are not right. Please keep providing direction as needed.

Driver problem is resolved. Thank you for the instruction.

Have not been able to find the versions currently loaded in the Ozy and Mercury.
PowerSDR displays error message:
HPSDR Error Invalid Firmware
You have Ozy: 0.0
Mercury: 0.0
Penny: 0.0
Both PowerSDR and KISS Konsole return the version numbers of 0.0.

Have not been able to use HPSDRProgrammer or HPSDRBootloader. Both utilities are looking for an ethernet interface. Only have the USB interface.

Did try selecting all the various versions in the initozy11.bat file for both PowerSDR and KISS Konsole. None of the drivers provided control of Ozy and Mercury.

Craig KA0KQC

> On May 17, 2020, at 11:22 AM, George Byrkit <ghbyrkit at chartermi.net> wrote:
> 
> Craig,
> Not only is the incompatibility possible, it is well documented!  That's why I referred you previously to looking at the firmware versions!
> 
> So what's changed for Ozy?  You can find back in February that I was working with Ram (in India) about getting Ozy working.  We discovered with KISS Konsole that there were some issues with KISS but not PowerSDR.  So PowerSDR, as installed, is loading a given version of the Ozy_Janus firmware, right?  YOU need to ensure that you have the matching versions of firmware loaded into Mercury and Penelope/PennyLane. OR that YOU edit the batch file that loads the Ozy_Janus firmware to load what is compatible with your current firmware in Mercury and Penelope.  If your installation has old firmware as you suggest, this is happening to you.
> 
> You will use the HPSDR firmware updating utility (also linked from OpenHPSDR, and in the TAPR/OpenHPSDR GitHub (TAPR hosts this for OpenHPSDR) to update old firmware.
> 
> For example, this is what the InitOzy11.bat file looks like for KISS Konsole.  It is similar for PowerSDR:
> _______________________________________
> loadFW 0xfffe 0x0007 ozyfw-sdr1k.hex
> msecsleep 3000
> 
> rem Mercury 2.9a Penelope v1.3
> rem loadFPGA 0xfffe 0x0007 Ozy_Janus.v18.rbf
> 
> rem Mercury v2.9a Penelope v1.4
> rem loadFPGA 0xfffe 0x0007 Ozy_Janus.v19.rbf
> 
> rem Mercury v3.0 Penelope v1.5
> rem loadFPGA 0xfffe 0x0007 Ozy_Janus.v20.rbf
> 
> rem Mercury v3.1 Penelope v1.6
> rem loadFPGA 0xfffe 0x0007 Ozy_Janus.v21.rbf
> 
> rem Mercury v3.2 Penelope v1.7
> rem loadFPGA 0xfffe 0x0007 Ozy_Janus.v22.rbf
> 
> rem Mercury v3.3 Penelope v1.7
> rem loadFPGA 0xfffe 0x0007 Ozy_Janus.v24.rbf
> 
> rem Mercury v3.4 Penelope v1.8
> rem loadFPGA 0xfffe 0x0007 Ozy_Janus.v25.rbf
> 
> rem Mercury v3.4 Penelope v1.8
> rem loadFPGA 0xfffe 0x0007 Ozy_Janus.v27.rbf
> 
> rem Mercury v3.4 Penelope v1.8
> loadFPGA 0xfffe 0x0007 Ozy_Janus.v28.rbf
> ______________________________________________
> 
> Note that only one 'loadFPGA' invocation is un-commented.  Note that the line before suggests that Mercury and Penelope versions are compatible.
> 
> This should let you solve the problem.  It's possibly also how you thought that the 'device showed' after what you called initial installation.  I have no idea if you actually did a driver installation, or whether you only unzipped and copied the files.  But that's water under the bridge or over the dam at this point, with your having gotten the driver truly installed.  I don't know what you think the 'automated install' was. (no images or text, so purely suggestive and anecdotal on your part.)
> 
> 73,
> George K9TRV
> 
> -----Original Message-----
> From: craig <heatingengineer at cfl.rr.com> 
> Sent: Sunday, May 17, 2020 11:08 AM
> To: George Byrkit <ghbyrkit at chartermi.net>
> Cc: Erik Skovgaard <ve7mdl at gmail.com>; hpsdr at openhpsdr.org
> Subject: Re: [hpsdr] Resurrecting Old Setup
> 
> Update. Some progress.
> 
> In Device Manager, right clicked on Other Devices —> Unknown Device.
> Chose load driver.
> Selected driver from downloads.
> 
> Driver installed and now have Ozy Host Assisted Firmware Load device.
> Don’t know why automated install didn’t work.
> 
> Now PowerSDR v3.4.9 can turn on Ozy and Mercury.
> 
> However get this error:
> HPSDR Error
> Invalid Firmware.
> You Have Ozy: 0.0
> Mercury: 0.0
> Penny: 0.0
> 
> Since these boards are likely some of the earliest sold. Would make sense that firmware is one of the earliest released.
> 
> Is it possible this early firmware isn’t compatible with the latest PowerSDR v3.4.9 version?
> 
> 73
> Craig KA0KQC
> 
>> On May 17, 2020, at 7:52 AM, George Byrkit <ghbyrkit at chartermi.net> wrote:
>> 
>> Dear Erik,
>> The driver that he downloaded IS signed!
>> 
>> 73,
>> George K9TRV
>> 
>> -----Original Message-----
>> From: Erik Skovgaard <ve7mdl at gmail.com> 
>> Sent: Sunday, May 17, 2020 1:46 AM
>> To: George Byrkit <ghbyrkit at chartermi.net>; craig <heatingengineer at cfl.rr.com>
>> Cc: hpsdr at openhpsdr.org
>> Subject: Re: [hpsdr] Resurrecting Old Setup
>> 
>> Hi Craig,
>> 
>> I just went though a driver problem with com0com.  Check the properties 
>> of the device.  If you see error code 52, it mean that the driver was 
>> not accepted by Windows since it needs to be signed.  Let me know and I 
>> can dig out the work-around process.
>> 
>> 73 de va7qi,            ....Erik.
>> www.MarineHandbooks.com
>> 
>> 
>> ------ Original Message ------
>> From: "George Byrkit" <ghbyrkit at chartermi.net>
>> To: "craig" <heatingengineer at cfl.rr.com>
>> Cc: hpsdr at openhpsdr.org
>> Sent: 2020-05-16 14:49:31
>> Subject: Re: [hpsdr] Resurrecting Old Setup
>> 
>>> ***** High Performance Software Defined Radio Discussion List *****
>>> 
>>> Well, with a valid installation of the driver, what I described is what you should see on Windows 10. YMMV.  If it doesn't, it's very complex to try to diagnose a Windows driver problem remotely, if it didn't install or doesn’t show up properly.
>>> 
>>> If you have a local support person who can help you thru this, it would be better.  Yes, social distancing does pose a problem.  But if you use Zoom or Skype or whatever, and share your desktop, the other person can see what is happening.
>>> 
>>> As far as running as Administrator: if you right-click the icon you use to launch PowerSDR, it likely should have a setting (maybe it's under compatibility) to 'run as administrator'.  And if that's true, then you get asked when you run PowerSDR if you want it to change your system (or if you trust it or whatever.)  You need to make the non-default choice.  If you don't see that message, it isn't running as administrator.  And you're screwed until it is.
>>> 
>>> It you are running PowerSDR from the start menu, right click on that Icon and you can often choose to 'run as Administrator'.  But you want to make that setting permanent, and just be asked each time you run PowerSDR if 'it is OK to do that'.
>>> 
>>> 73,
>>> George K9TRV
>>> 
>>> -----Original Message-----
>>> From: craig <heatingengineer at cfl.rr.com>
>>> Sent: Saturday, May 16, 2020 5:10 PM
>>> To: George Byrkit <ghbyrkit at chartermi.net>
>>> Cc: hpsdr at openhpsdr.org
>>> Subject: Re: [hpsdr] Resurrecting Old Setup
>>> 
>>> Yes, system was powered on.
>>> 
>>> The LibUSB-Win32 does not show up in Device Manager.
>>> 
>>> It has: Other Devices —> Unknown Device
>>> That’s a problem.
>>> 
>>> PowerSDR was down loaded and installed from the web site.
>>> 
>>> Don’t know about running as administrator. How do I verify that? Not super sharp on Windows.
>>> 
>>> So far I’ve not been able to see what firm ware is on the boards.
>>> 
>>> Yes, Hardware, not Harare. Thanks for the support.
>>> 
>>> Craig KA0KQC
>>> 
>>>> On May 16, 2020, at 4:56 PM, George Byrkit <ghbyrkit at chartermi.net> wrote:
>>>> 
>>>> And so was the radio powered on at that time?
>>>> 
>>>> Installation works if you end up with a device under 'LibUSB-Win32 devices' in Device Manager.
>>>> It is initially the Ozy Host Assisted Firmware Load devices.
>>>> 
>>>> Now assuming you have a valid installation of PowerSDR, and are RUNNING IT AS ADMINISTRATOR, the InitOzy11.bat file should run at PowerSDR startup (assuming configed in PowerSDR to use USB (Ozy/Magister), and actually have firmware files there, too, you should end up with the Ozy firmware being loaded successfully, and PowerSDR running.  You should of course consult the PowerSDR manual.  And GitHUB to ensure that you have a consistent set of firmware for all the boards you have defined to PowerSDR.  I'm sure you mean 'Hardware' and not 'Harare'...
>>>> 
>>>> 73,
>>>> George K9TRV
>>>> 
>>>> -----Original Message-----
>>>> From: Hpsdr <hpsdr-bounces at lists.openhpsdr.org> On Behalf Of craig
>>>> Sent: Saturday, May 16, 2020 4:10 PM
>>>> To: hpsdr at openhpsdr.org
>>>> Subject: Re: [hpsdr] Resurrecting Old Setup
>>>> 
>>>> ***** High Performance Software Defined Radio Discussion List *****
>>>> 
>>>> Here’s what’s happening. No joy yet:
>>>> 
>>>> Down loaded LibUSB-HPSDR_driver_win10_x86_x64.zip
>>>> 
>>>> Ran installation. It listed USB devices. Ozy showed up as vendor=0xFFFE, Product ID=0x0007 and no vendor or name info.
>>>> 
>>>> Installion seemed to work.
>>>> 
>>>> Ran PowerSDR v3.4.9.
>>>> 
>>>> When clicking Power button, received error “Error starting HPSDR Harare, is it connected and powered?”
>>>> 
>>>> Craig KA0KQC
>>>> 
>>>>> On May 16, 2020, at 3:54 PM, Laurence Barker <laurence at nicklebyhouse.co.uk> wrote:
>>>>> 
>>>>> Hi Craig
>>>>> 
>>>>> I **think"" you will just need to download the windows 10 signed drivers.
>>>>> 
>>>>> this link is from the openhpsdr web site:
>>>>> https://github.com/TAPR/OpenHPSDR-WindowsDrivers/releases/download/v1/LibUSB-HPSDR_driver_win10_x86_x64.zip
>>>>> 
>>>>> As far as I know power SDR can still connect to USB.
>>>>> 
>>>>> 
>>>>> Laurence Barker G8NJJ
>>>>> 
>>>>> laurence at nicklebyhouse.co.uk
>>>>> 
>>>>> 
>>>>> -----Original Message-----
>>>>> From: Hpsdr [mailto:hpsdr-bounces at lists.openhpsdr.org] On Behalf Of craig
>>>>> Sent: 16 May 2020 20:06
>>>>> To: hpsdr at openhpsdr.org
>>>>> Subject: [hpsdr] Resurrecting Old Setup
>>>>> 
>>>>> ***** High Performance Software Defined Radio Discussion List *****
>>>>> 
>>>>> Have original system made up of Mercury, Ozy and Alex.
>>>>> 
>>>>> Trying to dust it off and restart. It did run years ago. Don’t have original Windows configurations.
>>>>> 
>>>>> Have not been successful communicating with Ozy over USB.
>>>>> 
>>>>> What does it take to reactivate this system?
>>>>> 
>>>>> Have Windows 10 and 7.
>>>>> 
>>>>> 73, Craig, KA0KQC
>>>>> 
>>>>> 
>>>>> _______________________________________________
>>>>> HPSDR Discussion List
>>>>> To post msg: hpsdr at openhpsdr.org
>>>>> Subscription help: http://lists.openhpsdr.org/listinfo.cgi/hpsdr-openhpsdr.org
>>>>> HPSDR web page: http://openhpsdr.org
>>>>> Archives: http://lists.openhpsdr.org/pipermail/hpsdr-openhpsdr.org/
>>>>> 
>>>> 
>>>> _______________________________________________
>>>> HPSDR Discussion List
>>>> To post msg: hpsdr at openhpsdr.org
>>>> Subscription help: http://lists.openhpsdr.org/listinfo.cgi/hpsdr-openhpsdr.org
>>>> HPSDR web page: http://openhpsdr.org
>>>> Archives: http://lists.openhpsdr.org/pipermail/hpsdr-openhpsdr.org/
>>>> 
>>> 
>>> _______________________________________________
>>> HPSDR Discussion List
>>> To post msg: hpsdr at openhpsdr.org
>>> Subscription help: http://lists.openhpsdr.org/listinfo.cgi/hpsdr-openhpsdr.org
>>> HPSDR web page: http://openhpsdr.org
>>> Archives: http://lists.openhpsdr.org/pipermail/hpsdr-openhpsdr.org/
>> 
>

More information about the Hpsdr mailing list