[hpsdr] Problem with Powersdr 2.2.3 and Hermes

Thu Oct 18 07:12:53 PDT 2012

Hi Isaac,

Please reset the database and try it again. If the problem still exists,
please let me know which Region you are using.

73,
Doug
W5WC

From: Weksler Izik [mailto:weksler at elta.co.il] 
Sent: Thursday, October 18, 2012 3:09 AM
To: Doug W5WC
Cc: hpsdr at lists.openhpsdr.org
Subject: RE: [hpsdr] Problem with Powersdr 2.2.3 and Hermes

Doug,
I have installed the latest version of PSDR (2.2.3.12). Starting from some
of the new versions (don't remember exactly which) it does not remember the
frequency when switching the bands. For example if it was set to 14.185 SSBU
then switched to 18.130 SBU. After that, if I switch to 20m (press the "20"
band button) it goes to 14.001 CWU etc. I would expect it to go to 14.185
SSBU - last setting. At least that was the case in the "pre-installer"
versions. Or maybe I'm doing something wrong? Please advise.
73 Isaac 4Z1AO

-----Original Message-----
From: hpsdr-bounces at lists.openhpsdr.org
[mailto:hpsdr-bounces at lists.openhpsdr.org] On Behalf Of Doug W5WC
Sent: Wednesday, October 17, 2012 10:08 PM
To: 'Andrew'
Cc: hpsdr at lists.openhpsdr.org
Subject: Re: [hpsdr] Problem with Powersdr 2.2.3 and Hermes

***** High Performance Software Defined Radio Discussion List *****

Hi Andrew,

The second -20 is the attenuator on Alex and is shown in the pull down list
as -20db to distinguish it from the one on Mercury which is shown as -20dB.

The selection goes in this manner:

  0 = no attenuation
-20dB = Mercury

-10db = Alex
-20db = Alex

-30db = both -10 & -20 on Alex
-40db = Mercury and -20 on Alex
-50db = Mercury and both attenuators on Alex

The console control named 'ALEX' will have a subdued name when Alex is
turned off. The button background still appears illuminated because Mercury
is in the automatic mode for switching the filters. Mercury will still
control the filters properly even with the Alex deselected.

73,
Doug
W5WC

From: Andrew [mailto:irbsurfing at yahoo.co.uk]
Sent: Wednesday, October 17, 2012 2:39 PM
To: Doug W5WC
Cc: hpsdr at lists.openhpsdr.org
Subject: Re: [hpsdr] Problem with Powersdr 2.2.3 and Hermes

Doug,
Apologies - re-run the level cal routine and the levels now read correctly
in and out of band - phew!
However in the Rx1 version the attenuator values go 0, -20, -10, -20, -30,
-40, -50dB, double selection of -20dB!
Not checked the Rx2 version.
Andrew
G4XZL

________________________________________
From: Doug W5WC <w5wc at windstream.net>
To: 'Andrew' <irbsurfing at yahoo.co.uk>
Cc: hpsdr at lists.openhpsdr.org
Sent: Wednesday, 17 October 2012, 14:51
Subject: RE: [hpsdr] Problem with Powersdr 2.2.3 and Hermes

Hi Andrew,

The svn revision for the single receiver version is 2515 with a release
version of 2.2.3.12 dated 10/16/2012.

The svn revision for the dual receiver version is 2518 with a release
version of 2.2.3.13 dated 10/17/2012.

Normally you will find the most recent versions in an installer package on
the Downloads page on OpenHPSDR.org. For whatever reason it did not pick up
the most current version from yesterday.

The notes about each release is contained in the svn log. For example I am
using TortoiseSVN and to read the log I Right-Click on the Folder or File in
my local directory click on the 'TortoiseSVN->Show Log' feature and the
history for those updates will come up.
That information appears nowhere else that I'm aware of.

73,
Doug

From: Andrew [mailto:irbsurfing at yahoo.co.uk]
Sent: Wednesday, October 17, 2012 7:55 AM
To: Doug W5WC
Cc: hpsdr at lists.openhpsdr.org
Subject: Re: [hpsdr] Problem with Powersdr 2.2.3 and Hermes

Hi Doug,
Thanks (and others) for pointing out that there is a new version with the
problems fixed. I shall try them out this evening.
Perhaps you could confirm the revision that I should be using please so no
confusion?

Is there a page somewhere that gives revision history so I know whats fixed
or added?
Its a bit confusing when the releases are being updated regularily as I only
downloaded the version I am using last week.
Maybe something could be added to the website to indicate when a newer is
available version???
Thanks,
Andrew
G4XZL

________________________________________
From: Doug W5WC <w5wc at windstream.net>
To: 'Andrew' <irbsurfing at yahoo.co.uk>
Cc: hpsdr at lists.openhpsdr.org
Sent: Wednesday, 17 October 2012, 6:30
Subject: RE: [hpsdr] Problem with Powersdr 2.2.3 and Hermes

Hi Andrew,

Thank you for bringing these problems to our attention. The 'ALEX' control
on the console is for toggling between automatic and manual filter switching
modes for Alex.  If it appears illuminated that means Alex is in the
automatic mode. If you have not enabled Alex in Setup, the console control
is disabled.

The loss you see on 6m is due to a programming oversight. This has been
corrected in both versions of PowerSDR.

The ADC Overload comes from the ADC on Mercury. On Hermes the code was not
looking for the flag in the correct place. This has also been corrected in
the RX2 version of PowerSDR.

Both updated versions are currently on the svn.

Sorry, I am unable to answer your question concerning the dBFS readings.
Maybe someone can enlighten us all on that area.

73,
Doug
W5WC

From: hpsdr-bounces at lists.openhpsdr.org
[mailto:hpsdr-bounces at lists.openhpsdr.org] On Behalf Of Andrew
Sent: Tuesday, October 16, 2012 2:53 PM
To: hpsdr at lists.openhpsdr.org
Subject: [hpsdr] Problem with Powersdr 2.2.3 and Hermes

Hi,
A couple of small problems running v2.2.3 (single or dual Rx version)
downloaded from the openhpsdr website with Hermes and that is that 'Alex' is
always selected. This means that within the 50MHz band the dBm levels are
out by the gain of the LNA in Alex (26dB?). Tuning just outside the band and
all the levels return to normal.
Is there a way to deselect Alex properly please? Its unticked in the
setup>hardware window, but the button is illuminated on the main screen
(button next to MOX and below TUN).
(I also get Metis selected, can't deselect that either??)

Second problem - the ADC overload warning comes on fine with the single
receiver version but does seem to function with the dual receiver version???

What triggers the overload warning, is it the actual ADC overflow output or
triggered by the input level exceeding a certain dBFS level determined in
software (if so, what is it -1dBFS or 0dBFS etc??) Incidentally, I notice
that there is about as far as I can estimate a -7dB (maybe its 6dB, can't
tell) difference between ADC input level (dBFS) and the level indicated on
the Powersdr s meter set to read ADC level.
I can guess why this might be i.e. each I/Q being 6dB lower than the ADC
real level etc, but can anyone confirm the relationship please?
Is there any way to observe the actual ADC wideband level in dBFS??
Many thanks,
Andrew
G4XZL

_______________________________________________
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/
The information contained in this communication is proprietary to Israel
Aerospace Industries Ltd. and/or third parties, may contain confidential or
privileged information, and is intended only for the use of the intended
addresse thereof. If you are not the intended addressee, please be aware
that any use, disclosure, distribution and/or copying of this communication
is strictly prohibited. If you receive this communication in error, please
notify the sender immediately and delete it from your computer.

Thank you.

 1350569573.0