Apache Labs Community Forum

DCC2
s0=0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 9 9 5 2 0 0 0 0 0 0 0 11/27 10:46:11:467
s1=0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 9 9 5 0 0 0 0 0 0 0 0 11/27 10:46:11:467
s2=0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 9 9 0 0 0 0 0 0 0 0 0 11/27 10:46:11:467
s3=0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 9 0 0 0 0 0 0 0 0 0 0 11/27 10:46:11:467
s4=0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 0 0 0 0 0 0 0 0 0 0 0 11/27 10:46:11:467
s5=0 0 0 0 0 0 0 0 0 0 0 0 0 2 8 5 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 11/27 10:38:51:644
s6=0 0 0 0 0 0 0 0 0 0 0 0 0 2 8 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 11/27 10:38:51:644
s7=0 0 0 0 0 0 0 0 0 0 0 0 0 2 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 11/27 10:38:51:644
s8=0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 2 5 2 9 6 3 0 0 0 0 0 0 11/27 10:38:03:477
s9=0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 2 5 2 9 6 0 0 0 0 0 0 0 11/27 10:38:03:477
s10=0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 2 5 2 9 0 0 0 0 0 0 0 0 11/27 10:38:03:477
s11=0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 2 5 2 0 0 0 0 0 0 0 0 0 11/27 10:38:03:477
s12=0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 2 5 0 0 0 0 0 0 0 0 0 0 11/27 10:38:03:477
s13=0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 2 0 0 0 0 0 0 0 0 0 0 0 11/27 10:38:03:477
s14=0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 4 9 12 0 0 0 0 0 0 0 0 0 0 0 0 0 0 11/27 10:36:52:479
s15=0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 4 9 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 11/27 10:36:52:479
s16=0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 4 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 11/27 10:36:52:479
s17=0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 21 9 2 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 11/27 10:29:50:492
s18=0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 21 9 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 11/27 10:29:50:492
s19=0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 21 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 11/27 10:29:50:491

Just a note to mention that the random startup issue (roughly once every 4 startups) with my 200D (P2 FW v1.8) that plagued my use of Thetis since the release of version 2.6.7 seems to have gone away around the time that the 2.6.9 a6 release came out on 11/15/2019. The issue was:

When Thetis was started, RX1 and RX2 behaved as if they were not connected to their assigned ADC and the panadapter remained completely blank with no baseline displayed at all. I could transmit, and selecting different bands would result in relays clicking, but RX1 and RX2 remained totally dead no matter what settings were tried in Thetis. Oddly, SDR Console would start up and run fine when the 200D was in this state, but if I shut that down and went right back to Thetis the ANAN would still be RX dead. After re-setting the database, I made a short YouTube video showing (at the the 3 second mark) a bad startup with no RX. At the 56 second mark you can see it transmit in Tune mode while in this "dead RX" state:

https://www.youtube.com/watch?v=rabKwwfUyPQ

Things that would not resolve this issue:

-Shutting Thetis down and then restarting it
-Power cycling the ANAN
-Resetting the database
-Re-flashing the P2 firmware or flashing to another P2 version
-Removing all traces of Thetis and reinstalling it with a fresh database

Oddly, the only sure-fire way to bring my 200D out of this strange RX non-functional state was to switch to Thetis v2.6.6 or any earlier version. Once I jump-started it with Thetis v2.6.6 the ANAN would initialize properly and come alive. I could then shut down v2.6.6 and switch back to my Thetis v2.6.9 version and it would then start right up just fine and run for a couple of days before the random bad startup would return. (Another solution was to go back to protocol 1 and start up once with PowerSDR mRX and then re-flash to protocol 2 firmware and this would bring Thetis 2.6.7 through 2.6.9 back to life, but that was a more cumbersome task than just renaming two folders and going back to Thetis 2.6.6.)

So, for some reason versions 2.6.7 through early 2.6.9 were randomly leaving my my 200D in a bad state at shutdown or possibly improperly initialized at startup. Fortunately, since around the 2.6.9 a6 release on 11/15/2019, something changed either in the way Thetis shuts down, or starts up, and everything has been perfect!

73, Rob W1AEX

Very interesting Rob , also a great read !

gary /oxt

LOL, thanks Gary. However, after all that, the startup issue came back to taunt me this morning. Very strange that jump starting it with Thetis version 2.6.6 always brings it right back to life and then v2.6.9 a8_1 will start up fine. There must be something different about the startup sequence that happened when we moved from Thetis v2.6.6 to v2.6.7 that my 200D doesn't like.

73, Rob W1AEX

W1AEX wrote:LOL, thanks Gary. However, after all that, the startup issue came back to taunt me this morning. Very strange that jump starting it with Thetis version 2.6.6 always brings it right back to life and then v2.6.9 a8_1 will start up fine. There must be something different about the startup sequence that happened when we moved from Thetis v2.6.6 to v2.6.7 that my 200D doesn't like.

73, Rob W1AEX

not sure you tried this but do a database full reset and enter all the settings manually using 2.6.9

Yeah Nick, I did that and more. What I discovered is that the usual list of fixes when things get wonky don't get it going again. The only thing that brings it back to life is running Thetis 2.6.6 (or any earlier version) for a few seconds and then I can run any later version that followed (2.6.7, 2.6.8, and 2.6.9). I actually ran into a guy on the air who had exactly the same problem with his 200D, but I can't remember his call. I don't think it's a widespread problem and it takes me less than a minute to rename the folders so that I can swap versions.

See you on the air!

73, Rob

Things that do not resolve this issue:

-Shutting Thetis down and then restarting it
-Power cycling the ANAN
-Resetting the database
-Re-flashing the P2 firmware or flashing to another P2 version
-Removing all traces of Thetis and reinstalling it with a fresh database

that sure sounds like a database problem. if you have another computer, i would try it there.

Hmmm... if resetting the database doesn't resolve it, and a clean install doesn't resolve it, what makes you think it's a database issue? The other part is that it only happens with versions 2.6.7 and later. Version 2.6.6 and earlier versions are never a problem. It's a weird one Nick! But... I do have another computer sitting around so I'll give that a shot just to see...

not know other than what’s in the post, it sounds like your database is getting corrupt. i know the database was updated at some point but don’t recall when. no one else is having a problem like this that i know of so, with all you have tried it comes down to maybe a system problem. i have done a lit of trouble shooting vein in IT for 20 years and you never rule out anything without testing.

Yeah, but Nick, here's the weird thing. After I jump start the 200D with Thetis v2.6.6 and then switch back to the folders holding Thetis v2.6.9, it starts right up with the very same database that was there when it wouldn't start up before. So... that kind of infers that there is nothing wrong with the database. Personally, I think that the way Thetis starts up and initializes and also how it shuts down changed when we moved from v2.6.6 to 2.6.7 and later versions. Something about those later versions will sometimes leave my 200D in a wonky state where the antenna path to the receivers is no longer complete. It can transmit fine, it just can't receive.

I'm not losing sleep over it as it takes me less than a minute to get it working, but it is a curious behavior that has me stumped. Ah well, it's kind of like a high performance car that's a little cranky starting up now and then. I can live with it!

DCC0
s0=0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 -1 0 0 0 0 0 0 r:809273 l:809273 11/30 08:17:16:376

Anyone with a 200D having startup issues with latest Thetis 2.6.9 beta,
I have my own version which I built that I and others use without any issues
on the 200D and my 7000DLE. I can send you a .zip file with my (unofficial)
version 2.6.9.1 which I am developing and using for my SDR DSP research.

Gary,

Have you shared your findings regarding the startup issue with Richie?

Thanks,

Scott

Gary_Sitton wrote: I can send you a .zip file with my (unofficial)
version 2.6.9.1 which I am developing and using for my SDR DSP research.

What does your version incorporate or fix?

Scott:
No, I have not shared any of my work with the "Open Group" because
my my work is private and the source is not yet to be shared. I would
glad to let anyone have a copy of my executable package, but I am not
aware of anything I did to the current GitHub source repository image
which would have any effect as indicated by your 200D owners. I had
a very difficult time simply building this beta release with MS VC 2019.
Anyway, after some helpful input from Doug W5WC, I got a build done
and then added my changes to WDSP regarding some PSDR and Thetis
RX DSP features. If anything I did which might effect the behavior in
the 200D models, I don't know what it would be. The Only thing would
be in the MS VC 2019 build itself which I don't believe to be unusual.

This version was NOT intended to fix and issue with 2.6.9 beta or any
other Theis version

Hi, I am privileged to be an alpha/beta tester with K5AMH Thetis 2.6.9.1.

It is performing great on all modes on my 200d using Protocol-2.

I have also tested the new DL1YCF version of the RaspberryPi pihpsdr and that also clicks along with a great new CW note in the headphones.

Jackie K5JLC has been using the DL1YCF MAC port of pihpsdr on his MAC desktop and his 200d performs beautifully in Protocol-1.

GL de Ken N9VV

Gary_Sitton wrote:Anyone with a 200D having startup issues with latest Thetis 2.6.9 beta,
I have my own version which I built that I and others use without any issues
on the 200D and my 7000DLE. I can send you a .zip file with my (unofficial)
version 2.6.9.1 which I am developing and using for my SDR DSP research.

Hi, Gary,

Would it be possible to get your 2.6.9.1 unofficial version to try it?

73 Isaac 4Z1AO

Scott,

I have taken a look at the 'not so smooth' waterfall and it is caused by the thread sleep in the main draw thread. To make it 100% consistent we can not use Thread.Sleep in there to handle the frame limiting.

I have been playing around with some experimental code but the side effect is increased cpu usage while it sits in a loop waiting for the required frame delay to pass. Putting the thread to sleep will not guarantee that frame delay. A catch-22 problem. I do notice the same 'micro stutter' thing with ExpertSDR2 as well (expert electronics).

I can leave that experimental stuff in there for next release as it can be turned off/on with option, but I can't really recommend using it for the minimal gains it gives.

I will aim to get something out over the coming weekend with a couple of additional features. I treated myself to some parts to build an updated pc based around an AMD 3800X and an NVidia RTX 2070super, so having some fun with that at the mo

73 RIchie.

ramdor wrote:Scott,

I have taken a look at the 'not so smooth' waterfall and it is caused by the thread sleep in the main draw thread. To make it 100% consistent we can not use Thread.Sleep in there to handle the frame limiting.

I have been playing around with some experimental code but the side effect is increased cpu usage while it sits in a loop waiting for the required frame delay to pass. Putting the thread to sleep will not guarantee that frame delay. A catch-22 problem. I do notice the same 'micro stutter' thing with ExpertSDR2 as well (expert electronics).

I can leave that experimental stuff in there for next release as it can be turned off/on with option, but I can't really recommend using it for the minimal gains it gives.

Hi Richie--it will be interesting to try this It really sounds like some sort of fundamental change is required to creating that display, but what that would be is outside my expertise.

I will aim to get something out over the coming weekend with a couple of additional features. I treated myself to some parts to build an updated pc based around an AMD 3800X and an NVidia RTX 2070super, so having some fun with that at the mo

Oooh, that sounds nice. I just went through a one week debug cycle on my crypto-smasher here. I was getting a lot of blue screens and since I'm overclocked to 5GHZ (i7-7700k) I immediately thought "thermal problem" and re-did my de-lid, but that wasn't it at all. It turned out to be bad memory. Of course I discovered this on the day before Thanksgiving, so no new memory until Monday, but now I'm back in action and the system is back to rock solid status

Cheers!

Scott

Gary_Sitton wrote:Scott:
No, I have not shared any of my work with the "Open Group" because
my my work is private and the source is not yet to be shared. I would
glad to let anyone have a copy of my executable package, but I am not
aware of anything I did to the current GitHub source repository image
which would have any effect as indicated by your 200D owners. I had
a very difficult time simply building this beta release with MS VC 2019.
Anyway, after some helpful input from Doug W5WC, I got a build done
and then added my changes to WDSP regarding some PSDR and Thetis
RX DSP features. If anything I did which might effect the behavior in
the 200D models, I don't know what it would be. The Only thing would
be in the MS VC 2019 build itself which I don't believe to be unusual.

This version was NOT intended to fix and issue with 2.6.9 beta or any
other Theis version

Gary whilst it is nice that you are experimenting with your own version I don't see the point to keep the source private. The software is open source and by developing your own version and hijacking this thread you are not helping anyone.

Richie is doing a fantastic job developing Thetis - you either contribute and help him and others with those efforts or please keep your "private" version private.

Thanks

Nicholas - 2E0GKG

Nico--cut Gary some slack, please. We are damn lucky that anyone want to code anything at all for the community. I know we are all eager and insatiable for more, More, MORE, but pressure like that may not be motivational. I'm sure Gary will release the code so that it can be integrated into the common baseline when he feels it is ready for more widespread consumption. Everyone can't be an alpha tester.

Thanks,

Scott

I agree Scott we are indeed lucky that someone wants to work on this.

nico wrote:

Gary_Sitton wrote:Scott:
No, I have not shared any of my work with the "Open Group" because
my my work is private and the source is not yet to be shared. I would
glad to let anyone have a copy of my executable package, but I am not
aware of anything I did to the current GitHub source repository image
which would have any effect as indicated by your 200D owners. I had
a very difficult time simply building this beta release with MS VC 2019.
Anyway, after some helpful input from Doug W5WC, I got a build done
and then added my changes to WDSP regarding some PSDR and Thetis
RX DSP features. If anything I did which might effect the behavior in
the 200D models, I don't know what it would be. The Only thing would
be in the MS VC 2019 build itself which I don't believe to be unusual.

This version was NOT intended to fix and issue with 2.6.9 beta or any
other Theis version

Gary whilst it is nice that you are experimenting with your own version I don't see the point to keep the source private. The software is open source and by developing your own version and hijacking this thread you are not helping anyone.

Richie is doing a fantastic job developing Thetis - you either contribute and help him and others with those efforts or please keep your "private" version private.

Thanks

Nicholas - 2E0GKG

Nico-- Where do you get that Gary is "Hijacking This Thread"? And you said, "you either help him or keep your version private..." Did I not see Gary say " I will send you a zip with my version" Sounds to me like hes offering to help... Just saying... Seems to me you're just mad hes not sharing it with you. Give the guy a break. Be lucky ANYONE is working on it beings it's done in their own free time.

Perry

I would like to thank everyone including Mw0lhe for all the hard work And Also everyone who has Beta tested these changes.

Anyone who is taking their time to contribute .

I believe there is in place some controls to allow everyone to do this .

It is not there to limit the exploration but to limit any miss use .

As long as any "ANY" software mod has been offered as a venturesome or improvement to the program and complied with the people in charge of protecting us This is not Hi Jacking .

So If there is something busted , please fix it . If there is a better way , please Fix it If there is a super function , please produce it . Add it .
Innovation comes from very talented people Keep up the good work.

Ed

Hi folks,

I wont be putting out anything this weekend as I have not had much free time to spend on it. Hopefully sometime in the week.

However, just a small teaser...
Richie.

What a nice Christmas present!

ramdor wrote:Hi folks,

I wont be putting out anything this weekend as I have not had much free time to spend on it. Hopefully sometime in the week.

However, just a small teaser...

test1.png

Richie.

Very nice Richie - may be a small thing for you.....but really BIG at least for me

Andy

First time Ive gotten a Seq error that been anything but a random 1 in a sequence of 0's...

DCC2
s0=0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 46 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 r:326789 l:326742 12/09 06:10:26:136


We'll keep an eye on things...


Perry

UPDATE

HI all,

Small update with the peak indicators, and a couple of other bits and bobs. Most of it is only implemented in DirectX at the moment. The peak detect is a simple algorithm, and does not use crossing point/smoothing/slope.

Quite handy for this sort of thing, with PS on :
Also, an experimental change to frame rate calculations that can be enabled with 'accurate frame timings' option. However, It sits in a very tight loop until the expected delay has passed and consequently is quite cpu hungry. It is perhaps only worth using if you have a work horse of a PC and want to test if it improves the micro-stutter in the waterfall.

Link : link removed, see post #1

Cheers, Richie.

(11/19/19) b2
-add(*): peak markers on the panadapter. Configure through Setup>Display>General. Note: this is a very simple algorithm and does not consider slope
-add(*): experimental accurate frame timing. This will probably have a substantial impact on cpu usage
-change(*): if a timed waterfall update is ‘late’ the next update will be made ‘early’
-change: now using hiperf timer in RunDisplay
(*) only implemented in DirectX atm