Apache Labs Community Forum

wa1oxt wrote:Fatal Error when installing 2.10.3. Win 11 Pro. WIn 11 update 23H2 _11/1/23.
12th Gen i7-12700K,3600Mhz. 12 Core(s).

Please see attached.

tnx ..OXT

FWIW, I had a similar but not exact fatal error message when I attempted installing v2.9.0 (iirc the exact version correctly) not long ago . It turned out to be the display setting in Windows was at 125% . When reduced to 100% (default) the version opened normally. I found this out by accident after many frustrating attempts to install.

Current version 2.10.3.3 operates as it should with screen resolution at 125%

73, Harry W2QAQ

2.10.3.3 solved problem.

Richie, tnx for your support

Gary / wa1oxt

2.10.3.3 solved my critical error as well. I'm back up and running!

Ritchie, thanks for all your support! Great Job!

Cal / N3CAL

Smooth update!
Thanks Ritchie!
James
WD5GWY

Thank you very Richie I am enjoying it as I type.

73, Dan KM6CQ.

Thanks again Richie for your hard work!

The new version is working very well with the new WASAPI options. And FM sounds much better!

Have to do some more testing in the next days, but very very happy with the new version!

73, Edwin PA3GVQ

V2.10.3.3

First off I want to thank you for ALL your time on doing Thetis firmware!!!! AWESOME! Thank You!!

One thing I found and it could be me...
In my previous ver 2.09 I added the Band Text in the database.xml file.
This update lost all pervious Band Text info.
No big deal as I have text doc of all my stuff.
I added again the Band Text into the database.xml file, saved it, and reopened it to make sure it was all there correctly.
When I opened Thetis I notice the time stamp on the darabase.xml file to change to the time of Thetis opening.
No new Band Text in the VFO area... Did this change twice. No new Band Text.
I found a file called ImportLog.txt and noticed that the first line said "Did not import table <BandText> into database."
It was time stamped at the inatial time of the V2.10 install.

So I guess that this new version rewrites the database.xml file every time Thetis starts...
Recommendation of how to add new Band Text to the database?

Thank You Sir!
Clint

@Clint

Make sure you edit the database with the band text changes when Thetis is NOT running, otherwise they will be lost. I've just tested here and it works fine.

Import doesn't import band text from old db, and hasn't for as long as I have been looking at the source code. The block that does it is commented out in ImportAndMergeDatabase()

Thank you for your reply!

Worked more on it now.

rebooted computer..
Open my BandText.txt file in Notepad
Copied all the stuff.
Opened database.xml in Notepad.
Scrolled way down into the Band Text area.
Inserted in between the frequency area of interest. Pasted copied txt.
Checked formatting errors in xml file.
save xml.
open database.xml in wordpad just to see it differently. All looks good.
Open Thetis, at frequency of new band text. VFO does not display new name. Did not even hit the Power button.
Close Thetis.
Open database.xml in notepad again and the newly inserted Band Text is no longer there.
In V2.9.0.6 Inserting the text was no problem. Worked well!

The problem is I just know enough how to do things to say oops and cant figure how to undo it!!

please make your changes, then send me the database.xml before you load up thetis. Email over on qrz. Thanks.

@WA6TMJ

You need to remove the 11m entry, as yours fall inside that, so all of yours get dumped. It has always been like that as I have not touched that code. Downside is that it will show out of band when just outside your spot channel frequencies. You could add a whole bunch to include the areas outside your spot frequencies.

Remove this from the database
Also to note, when changing region all of this bandtext stuff gets cleared.

Edit: yep, 11m was added into the SW Broadcast & Misc Band Plan some 6 months ago. That would be the cause of this.

I haven't really looked at the code before, but it is not ideal just to remove them. They apply if you are on those spot frequencies. I will add to the list to resolve it sometime. The code that does the removal is in CheckBandTextValid() in database.cs if anyone is interested.

YES! It Worked when I removed the code.
I did a little more snooping.
Turns out I had made a copy of the database.xml file when I started to do my Band Text experiments when I was on 2.9.0.6.
Sure enough that code above was NOT in the data base at that time. So my added band text work right off the bat when I did my copy and paste then!

Still learning about this Awesome software!

Very AWESOME Sir!
Thank You Rich!!

Clint

Rich,

Thanks so much for all your hard work.

I wish I had 1/100 of your talent!

Thank you very much again.

Mark

ramdor wrote:@WA6TMJ

You need to remove the 11m entry, as yours fall inside that, so all of yours get dumped. It has always been like that as I have not touched that code. Downside is that it will show out of band when just outside your spot channel frequencies. You could add a whole bunch to include the areas outside your spot frequencies.

Remove this from the database

Code: Select all

  <BandText>
    <Low>26.33</Low>
    <High>27.865</High>
    <Name>11M Band</Name>
    <TX>true</TX>
  </BandText>

Also to note, when changing region all of this bandtext stuff gets cleared.

Edit: yep, 11m was added into the SW Broadcast & Misc Band Plan some 6 months ago. That would be the cause of this.

I haven't really looked at the code before, but it is not ideal just to remove them. They apply if you are on those spot frequencies. I will add to the list to resolve it sometime. The code that does the removal is in CheckBandTextValid() in database.cs if anyone is interested.

I have a question Richie, since I think Clint and I are trying to do something similar here. How come on 80 meters, it has 3.885 mhz as the AM calling frequency, and when you go outside of that, it doesnt say out of band, it says 80m or what not. But on 11 meters, if I want to name, say, 27.025 mhz "The Superbowl", you cant without deleting the 11m BandText information and the rest of 11m will be "Out Of Band"?

I tried doing that exact thing, I went and read how the 80m BandText is setup and written, did it the same way, and the added info gets deleted after Thetis starts up?

Maybe im missing something thats already been covered.

Thanks for all this work man. Its gotta be quite time consuming. So again, thanks.

Perry

Hi Perry,

It is because either side of the spot 3.885 it has the 75m SSB entries. The same could be done with the 11m spot frequencies, but there would be a lot of fillers to rebuild the 11m areas, 41 one of them in Clint's case.

Cheers.

Thanks Rich for an Awesome explanation!!

The above couple of posts Should be made into a separate new thread to be search easy on!
Great info!! Would not have figured this out!
Now I really know how to add Band Text info!! AWESOME!

Also thank you VERY MUCH on the added Finder tab!

Even though I been running Thetis for almost 4+ years now this Finder tab has made understand this software so much better in like where's that!
Now I don't have to call my friend to ask where things are!!

I am just barely understanding all what this software can do!!

I know I am late to the punch.. But the Big Meter is Awesome!!

Thanks to you and all the team members for ALL these improvements to the software!
Makes me feel I am getting a new radio every time I upgrade the software!

So much to learn on this radio!
This Anand 8000DLE is my dream radio!!
Never thought I would get a radio like this when I started Ham Radio!!
AWESOME!!

ramdor wrote:Hi Perry,

It is because either side of the spot 3.885 it has the 75m SSB entries. The same could be done with the 11m spot frequencies, but there would be a lot of fillers to rebuild the 11m areas, 41 one of them in Clint's case.

Cheers.

spot3885.png

Dude, I didnt even notice that..
Thanks so much. I would have been pulling my hair out for hours.
Thanks again for the work.

Perry

yes, we need to implement a band text config ui, where you can add/remove, set up areas, etc easily without having to hack about in the database.xml. Only so many hours in the day though Same for band edges, which are dotted all over the code.

Richie,
I watched your video on the new FM setup and I see when you change the filter widths, on RCV or XMT they change on the main display.
When I increase the filter width, nothing changes. It stays the same frequency on the display. it is stuck on 300 low and 3000 high.

I maybe didn't explain it correctly, The panadaptor filter width on RCV never changes when you change the filter settings in the FM tab.

Hi
When using the flex control wheel running with ddutil for the vfo, and when I have the tune step at 100hz it moves 250hz. If I use a 50hz tune step it then tunes at 100hz. If I try 250hz it moves 500hz. With the mouse it works fine. I tried setting the ddutil to 1hz. to make sure it is not creating the problem. Not a big problem but is the first time I have seen this behavior. Running this through cat system. By the way if I use 1hz it moves 1hz.

W9BHI wrote:Richie,
I watched your video on the new FM setup and I see when you change the filter widths, on RCV or XMT they change on the main display.
When I increase the filter width, nothing changes. It stays the same frequency on the display. it is stuck on 300 low and 3000 high.

RX only works in 2.10.3.3, however widths on the display are not changed as we were not Carlson's rule to calculate them. Also, TX was not tested sufficiently.

2.10.3.4 will see this fixed when eventually released. Please see this testing video : https://youtu.be/vn2rW_g_RVQ?si=YIBC2JJ3Xy2E0L6u

n2gq wrote:Hi
When using the flex control wheel running with ddutil for the vfo, and when I have the tune step at 100hz it moves 250hz. If I use a 50hz tune step it then tunes at 100hz. If I try 250hz it moves 500hz. With the mouse it works fine. I tried setting the ddutil to 1hz. to make sure it is not creating the problem. Not a big problem but is the first time I have seen this behavior. Running this through cat system. By the way if I use 1hz it moves 1hz.

check under Setup->Navigation that the HID stuff is turned off. It might be cause for multiple vfo changes.

I know this is all probably stuff related to the update to 2.10.3.3, but it would help the forum and future searches if separate threads ands posts were made instead of turning this into a mega thread. Perhaps tag the new thread title such as

My new thread asking about blah - [2.10.3.3]

Cheers.

ramdor wrote:

n2gq wrote:Hi
When using the flex control wheel running with ddutil for the vfo, and when I have the tune step at 100hz it moves 250hz. If I use a 50hz tune step it then tunes at 100hz. If I try 250hz it moves 500hz. With the mouse it works fine. I tried setting the ddutil to 1hz. to make sure it is not creating the problem. Not a big problem but is the first time I have seen this behavior. Running this through cat system. By the way if I use 1hz it moves 1hz.

check under Setup->Navigation that the HID stuff is turned off. It might be cause for multiple vfo changes.

I just checked navigation, all was unchecked.

Richie,
I am running the 2.10.3.3 but I guess the version you were running in the video is possibly the 2.10.3.4 that you are still working on?
Thanks,
Don W9BHI

Hi Richie,

Changes made in the Mode Form do not seem to be save when I close and restart Thetis.
Also, note that the Finder menu item does not show up on my Andromeda. Perhaps it could be implemented as one of the buttons on the bottom of the display?

73 de va7qi, ....Erik.

va7qi wrote:Hi Richie,

Changes made in the Mode Form do not seem to be save when I close and restart Thetis.
Also, note that the Finder menu item does not show up on my Andromeda. Perhaps it could be implemented as one of the buttons on the bottom of the display?

73 de va7qi, ....Erik.

probably related to your band stack config. A band stack entry will be recovered on startup and if that was not updatable on close down, then it will recover with the mode associate with that pre-existed on that stack entry. May also be related to the bandstack return to last used/specific/or frequency mode. Changing mode using the mode form, shutting down and restarting works fine here.

Hi Richie,
Since I upgraded to v2.10.3.3 occasionally I get a shut down error. The flash screen saying Thetis is closing never goes off the screen. If I try to force it to close I get the MS error message that windows is reporting the problem.
73, George
W2GS

Sorry, I guess I was not clear. It is the ModeDependentSettingsForm that is not saved.

73 de va7qi, ....Erik.

ramdor wrote:

va7qi wrote:Hi Richie,

Changes made in the Mode Form do not seem to be save when I close and restart Thetis.
Also, note that the Finder menu item does not show up on my Andromeda. Perhaps it could be implemented as one of the buttons on the bottom of the display?

73 de va7qi, ....Erik.

probably related to your band stack config. A band stack entry will be recovered on startup and if that was not updatable on close down, then it will recover with the mode associate with that pre-existed on that stack entry. May also be related to the bandstack return to last used/specific/or frequency mode. Changing mode using the mode form, shutting down and restarting works fine here.