v.3.4.x xml d/b creation bug?

g0rvm
Posts: 7
Joined: Mon Apr 10, 2017 8:56 pm

v.3.4.x xml d/b creation bug?

Postby g0rvm » Sat Aug 19, 2017 8:09 pm

I have what looks like an xml database creation bug. Apologies if this has been reported already but a search hasn't found anything.

I've been using the v3.4.x releases since their release, but only on the 6m band. Today I've returned to 2m and noticed that the band segments are incorrectly displayed in the area under the frequency in HPSDR.

The whole of the 2m definition looks odd. I haven't checked other bands.

Below is just a snippet of the xml d/b to illustrate the problem:

A newly v3.4.2 created d/b contains:
<BandText>
<Low>144.3</Low>
<High>144.499999</High>
<Name>2M Satellite</Name>
<TX>true</TX>
</BandText>
<BandText>
<Low>144.5</Low>
<High>144.599999</High>
<Name>2M Linear Translator Inputs</Name>
<TX>true</TX>
</BandText>

But the same definition created by 3.3.17 contained:
<BandText>
<Low>144.300001</Low>
<High>144.399999</High>
<Name>2M SSB</Name>
<TX>true</TX>
</BandText>
<BandText>
<Low>144.4</Low>
<High>144.489999</High>
<Name>2M Beacons</Name>
<TX>true</TX>
</BandText>
<BandText>
<Low>144.49</Low>
<High>144.499999</High>
<Name>2M Guard Band</Name>
<TX>true</TX>
</BandText>
<BandText>
<Low>144.5</Low>
<High>144.799999</High>
<Name>2M All Mode</Name>
<TX>true</TX>
</BandText>

The 3.3.17 definition is correct for Region 1. I don't know about other regions but it looks wrong....
I've checked a d/b export from 3.4.1 and that has the same problem as 3.4.2.

For now I've simply copied the xml 2m band definition from the 3.3.17 d/b and overwritten the corresponding xml in the current 3.4.2 d/b and all is ok again :-)

Is this a known defect, or am I missing something? Its easily reproducible....

Thanks,
Andrew
G0RVM
User avatar
W2PA
Posts: 50
Joined: Sun Apr 09, 2017 6:34 pm

Re: v.3.4.x xml d/b creation bug?

Postby W2PA » Sun Aug 20, 2017 11:43 am

Andrew,

Thanks for noting this. It's not really a bug but certainly may be incorrect. The way the code is structured (I don't know how far back this goes), these segments and names are literally hard-coded into the software. I'll have a look at it and see if we can correct it according to what you posted.

If anyone else notices incorrect segment labeling, please note it here too.

Addtional info after editing:

I just checked the code and the correct Region 1 entries are there for the segments you named. I don't know how to explain why you're getting something different, Andrew.

If you want to try an experiment to see if it can be corrected, try this:
1) Make a backup copy of your database.
2) Edit your database to delete the offending entries for the 2m band.
3) Reset the database
4) Import your edited database
73,
Chris, W2PA
g0rvm
Posts: 7
Joined: Mon Apr 10, 2017 8:56 pm

Re: v.3.4.x xml d/b creation bug?

Postby g0rvm » Sun Aug 20, 2017 6:13 pm

Chris,

Thanks for looking at this... But I am mighty confused.

As an even more basic test I:
a) closed HPSDR v3.4.2 (7/5/17)
b) deleted file: C:\Users\agawthrope\AppData\Roaming\FlexRadio Systems\PowerSDR mRX PS\database.xml
c) Restarted HPSDR
d) Selected a ANAN-10E radio...after which the default HPSDR grey/black window is shown with default settings
e) Closed HPSDR
f) Opened in Notepad the newly created C:\Users\agawthrope\AppData\Roaming\FlexRadio Systems\PowerSDR mRX PS\database.xml
g) searched for 144 and found the following incorrect xml... (Shown in its entirety this time)

<BandText>
<Low>144</Low>
<High>144.099999</High>
<Name>2M CW</Name>
<TX>true</TX>
</BandText>
<BandText>
<Low>144.1</Low>
<High>144.199999</High>
<Name>2M CW/SSB</Name>
<TX>true</TX>
</BandText>
<BandText>
<Low>144.2</Low>
<High>144.2</High>
<Name>2M Calling</Name>
<TX>true</TX>
</BandText>
<BandText>
<Low>144.200001</Low>
<High>144.274999</High>
<Name>2M CW/SSB</Name>
<TX>true</TX>
</BandText>
<BandText>
<Low>144.275</Low>
<High>144.299999</High>
<Name>2M Beacon Sub-Band</Name>
<TX>true</TX>
</BandText>
<BandText>
<Low>144.3</Low>
<High>144.499999</High>
<Name>2M Satellite</Name>
<TX>true</TX>
</BandText>
<BandText>
<Low>144.5</Low>
<High>144.599999</High>
<Name>2M Linear Translator Inputs</Name>
<TX>true</TX>
</BandText>
<BandText>
<Low>144.6</Low>
<High>144.899999</High>
<Name>2M FM Repeater</Name>
<TX>true</TX>
</BandText>
<BandText>
<Low>144.9</Low>
<High>145.199999</High>
<Name>2M FM Simplex</Name>
<TX>true</TX>
</BandText>
<BandText>
<Low>145.2</Low>
<High>145.499999</High>
<Name>2M FM Repeater</Name>
<TX>true</TX>
</BandText>
<BandText>
<Low>145.5</Low>
<High>145.799999</High>
<Name>2M FM Simplex</Name>
<TX>true</TX>
</BandText>
<BandText>
<Low>145.8</Low>
<High>145.999999</High>
<Name>2M Satellite</Name>
<TX>true</TX>
</BandText>
<BandText>
<Low>146</Low>
<High>146.399999</High>
<Name>2M FM Repeater</Name>
<TX>true</TX>
</BandText>
<BandText>
<Low>146.4</Low>
<High>146.609999</High>
<Name>2M FM Simplex</Name>
<TX>true</TX>
</BandText>
<BandText>
<Low>146.61</Low>
<High>147.389999</High>
<Name>2M FM Repeater</Name>
<TX>true</TX>
</BandText>
<BandText>
<Low>147.39</Low>
<High>147.599999</High>
<Name>2M FM Simplex</Name>
<TX>true</TX>
</BandText>
<BandText>
<Low>147.6</Low>
<High>147.999999</High>
<Name>2M FM Repeater</Name>
<TX>true</TX>
</BandText>


I did also try your suggestion but still get the incorrect values as in the xml above. Did you try the same build of HPSDR?

Andrew
G0RVM
g0rvm
Posts: 7
Joined: Mon Apr 10, 2017 8:56 pm

Re: v.3.4.x xml d/b creation bug?

Postby g0rvm » Sun Aug 20, 2017 6:32 pm

*** Post submission edit ***

I realised after posting that these are most probably the default values and thus what gets used if the Region is either not configured or there was an upgrade problem....

*** End of post submission edit ***


Chris,

Just out of curiosity I downloaded the v3.4.2 source just now from Github and had a look at file: OpenHPSDR-PowerSDR-3.4.2/Project Files/Source/Console/database.cs

It contains the following lines:

144.000000, 144.099999, "2M CW", true,
144.100000, 144.199999, "2M CW/SSB", true,
144.200000, 144.200000, "2M Calling", true,
144.200001, 144.274999, "2M CW/SSB", true,
144.275000, 144.299999, "2M Beacon Sub-Band", true,
144.300000, 144.499999, "2M Satellite", true,
144.500000, 144.599999, "2M Linear Translator Inputs", true,
144.600000, 144.899999, "2M FM Repeater", true,
144.900000, 145.199999, "2M FM Simplex", true,
145.200000, 145.499999, "2M FM Repeater", true,
145.500000, 145.799999, "2M FM Simplex", true,
145.800000, 145.999999, "2M Satellite", true,
146.000000, 146.399999, "2M FM Repeater", true,
146.400000, 146.609999, "2M FM Simplex", true,
146.610000, 147.389999, "2M FM Repeater", true,
147.390000, 147.599999, "2M FM Simplex", true,
147.600000, 147.999999, "2M FM Repeater", true,

Now, I don't believe in Region 1 or Region 2 (I don't know about other Regions), 144.300000-144.499999 is the "2M Satellite" segment, 144.500000-144.599999 is the "2M Linear Translator Inputs" etc....

This was correct in v3.3.n...

Andrew
G0RVM
Last edited by g0rvm on Sun Aug 20, 2017 7:22 pm, edited 2 times in total.
g0rvm
Posts: 7
Joined: Mon Apr 10, 2017 8:56 pm

Re: v.3.4.x xml d/b creation bug?

Postby g0rvm » Sun Aug 20, 2017 7:08 pm

OK Chris,

Getting closer now...

Using my v3.4.2 d/b, the one before any manual changes and with which HPSDR is showing the the incorrect 2m band plan info I see the Region - shown in the Setup dialog - as United Kingdom. However, if in the Setup dialog I select 'India' followed by re-selecting 'United Kingdom' the band plan is then correctly shown in the HPSDR main window and the correct values are written to the xml d/b.

A possible explanation may be that, for some reason and possibly during the 3.4.1/3.4.2 upgrades HPSDR created the xml d/b content for the 2m band at its default settings but then didn't then overwrite these with those needed for the configured Region. Perhaps that could be the problem? If not, then something else occurred in the upgrade process that resulted in the default 2m band plan in the xml d/b and the Region 1 specialisations not being applied, despite the Region being set to 'United Kingdom'.

Anyhow, I can confirm that if the Region is changed to another then back to the desired Region the correct information is written to the xml d/b.
So, if anyone else does suffer from this, that's the simple fix...

Thanks,
Andrew
G0RVM
User avatar
W2PA
Posts: 50
Joined: Sun Apr 09, 2017 6:34 pm

Re: v.3.4.x xml d/b creation bug?

Postby W2PA » Thu Aug 24, 2017 7:42 pm

Thanks for tracking it down, Andrew. Glad there's a fix, but it's clearly not something that should happen. I'll have a look when I get a chance.
73,
Chris, W2PA

Return to “PowerSDR mRX”