Welcome, Guest
Username: Password: Remember me

TOPIC: EESDR3 A 0.9.0 - Thoughts so far

EESDR3 A 0.9.0 - Thoughts so far 08 Sep 2021 20:19 #31

  • Tom_G0JSV
  • Tom_G0JSV's Avatar
  • OFFLINE
  • Posts: 74
  • Thank you received: 29
Just to advise that I did use the bug report to provide the detail around the lack of sensitivity problem affecting 2M with the v3 software. Roman (from EE) responded and confirmed that they have identified a calibration issue. He advised that this will be fixed in the next release. I am currently testing 0.9.0c alpha. The problem seems to be still present in this version.

At the moment, it isn't possible to tell which version of the software is installed based on the Info tab. It just shows v3 0.9.0 alpha. So I have asked if the minor version can be included on that info screen. The Windows setup file for 0.9.0c is 74,143 KB.
The administrator has disabled public write access.
The following user(s) said Thank You: N8SDR

EESDR3 A 0.9.0 - Thoughts so far 09 Sep 2021 03:13 #32

  • VK6NX
  • VK6NX's Avatar
  • OFFLINE
  • Posts: 331
  • Thank you received: 162
WB4RAG wrote:
When I try to raise it to 100% It only remains in 60 DB
I am not sure what you are trying to achieve by changing gain to 100% ... sounds unreasonable.

Here are my BM "real world" settings with Wellbrook Loop RX (those in combination with Preamp on +10)
ScreenShot2021-09-09at11.32.46.png


I barely understand how this may help :), because input gain settings are very dependent on antenna, QTH, surrounding noise level, even current solar cycle noise floor, etc
For example the above settings are completely useless if I switch my RX antenna to GP.
Last Edit: 09 Sep 2021 03:14 by VK6NX.
The administrator has disabled public write access.

EESDR3 A 0.9.0 - Thoughts so far 09 Sep 2021 05:19 #33

  • VK6NX
  • VK6NX's Avatar
  • OFFLINE
  • Posts: 331
  • Thank you received: 162
Almost there, almost there :yahoo:
ScreenShot2021-09-09at15.16.12.png


Just waiting for github's documentation update ...
The administrator has disabled public write access.
The following user(s) said Thank You: N8SDR

EESDR3 A 0.9.0 - Thoughts so far 09 Sep 2021 11:01 #34

VK6NX wrote:
WB4RAG wrote:
When I try to raise it to 100% It only remains in 60 DB
I am not sure what you are trying to achieve by changing gain to 100% ... sounds unreasonable.

Here are my BM "real world" settings with Wellbrook Loop RX (those in combination with Preamp on +10)
ScreenShot2021-09-09at11.32.46.png


I barely understand how this may help :), because input gain settings are very dependent on antenna, QTH, surrounding noise level, even current solar cycle noise floor, etc
For example the above settings are completely useless if I switch my RX antenna to GP.

Thanks for the picture of your BM, my interest is to be able to use the software, but I see that I will wait until the beta version, with its adjustments the RX remains the same in relation to the SDR2 software that is more sensitive, there are stations that I do not copy with the SDR3 that I can listen to with the SDR2, Thanks for your time 73 "
The administrator has disabled public write access.

EESDR3 A 0.9.0 - Thoughts so far 09 Sep 2021 11:31 #35

  • N8SDR
  • N8SDR's Avatar
  • OFFLINE
  • Posts: 609
  • Thank you received: 289
That's odd,
I just did the updated versions of 0.9.0 lets call it C and show 72.4 MB (75,920,696 bytes) as of this morning,
The prior release of 0.9.0 I have is 67.5 MB (70,876,414 bytes)

and agree it would make sense if these minor changes had some definition in the release info like C D etc. or just 0.9.1 0.9.2 etc
makes it much easier to figure and track bugs based on release versions
73 Rick
The administrator has disabled public write access.
The following user(s) said Thank You: EA5ML

EESDR3 A 0.9.0 - Thoughts so far 09 Sep 2021 11:57 #36

  • Rome
  • Rome's Avatar
  • OFFLINE
  • Quod Licet Jovi Non Licet Bovi
  • Posts: 1054
  • Thank you received: 528
We'll add build # in future
Роман, Roman
Expert Electronics
The administrator has disabled public write access.
The following user(s) said Thank You: VK6NX, Tom_G0JSV, N8SDR, yo3tco

EESDR3 A 0.9.0 - Thoughts so far 09 Sep 2021 15:42 #37

  • Tom_G0JSV
  • Tom_G0JSV's Avatar
  • OFFLINE
  • Posts: 74
  • Thank you received: 29
N8SDR, looks like they are doing continuous builds. That's great news. I will download a couple of times a day in future. I did a Checksum on the file that was downloaded yesterday verses one downloaded just now. The checksums are different and so is the file size. (In Windows 10, right click the file, choose CRC SHA, choose your preferred hash to generate the checksum)

Also, a correction on my part. The 2M sensitivity (lack of) is now fixed in 0.9.0c and later. Check that the VHF LNA is enabled. Left click the chain/link icon in the bottom left of the v3 application to enable/disable. Thanks to Roman for pointing that out to me.

P.S. I have also reported another issue, via the bug report tool, concerning the memory channels. There seems to be a problem when saving RPTR shift and CTCSS tone and then recalling these channels from memory. I wonder if anyone else has noticed this. Roman has confirmed receipt of the bug report and is investigating.
The administrator has disabled public write access.
The following user(s) said Thank You: N8SDR, EA5ML

EESDR3 A 0.9.0 - Thoughts so far 09 Sep 2021 17:01 #38

  • kc2rgw
  • kc2rgw's Avatar
  • OFFLINE
  • Posts: 99
  • Thank you received: 33
Just some feedback for the build team, Ubuntu 20.04LTS is working very nicely here. Installed the latest build and configured this morning and running nicely and with MicPC at that.
The administrator has disabled public write access.

EESDR3 A 0.9.0 - Thoughts so far 09 Sep 2021 18:15 #39

  • N8SDR
  • N8SDR's Avatar
  • OFFLINE
  • Posts: 609
  • Thank you received: 289
Hello Tom

I setup a few listing repeaters in prior version that worked, when I get home I will check in this latest release and see if they are still working.. thanks for heads up
73 Rick
The administrator has disabled public write access.

EESDR3 A 0.9.0 - Thoughts so far 10 Sep 2021 06:00 #40

  • Tom_G0JSV
  • Tom_G0JSV's Avatar
  • OFFLINE
  • Posts: 74
  • Thank you received: 29
Here is what I found. I set-up up the radio to use a local 2M repeater. So frequency, tone and shift all defined. I then keyed up and the repeater opened. Then using the 'plus' icon to the left of the main frequency display I saved to memory overwriting 'comment' with the repeater name and then pressing enter. Then I did the same for another repeater on a different frequency and CTCSS tone. But then when recalling the saved memory channels, the repeaters failed to open. My SunPro2 SDR is located remotely from the shack. About 150M. But I did head down with a frequency counter yesterday evening and found the radio was not TXing on the correct frequency. The first repeater was set-up as 145.650-600KHz and the RF was coming out on 145.675!! This wasn't the frequency of the second memory channel either.
The administrator has disabled public write access.

EESDR3 A 0.9.0 - Thoughts so far 10 Sep 2021 13:19 #41

  • Iu4jnr
  • Iu4jnr's Avatar
  • OFFLINE
  • Posts: 27
  • Thank you received: 8
Tom_G0JSV wrote:
Here is what I found. I set-up up the radio to use a local 2M repeater....
Do the TX audio in NFM work properly? my audio is like i'm transmitting in WFM.
With the 0.8.1 FM was ok
Max IU4JNR
The administrator has disabled public write access.

EESDR3 A 0.9.0 - Thoughts so far 10 Sep 2021 20:25 #42

  • DL5RK
  • DL5RK's Avatar
  • OFFLINE
  • Posts: 15
  • Thank you received: 1
CPU load shows in the MAC-Version around 1-3%, real CPU load is 55-60% and Fans are still blowing loud in my Macbook pro.
The administrator has disabled public write access.

EESDR3 A 0.9.0 - Thoughts so far 10 Sep 2021 21:20 #43

  • N8SDR
  • N8SDR's Avatar
  • OFFLINE
  • Posts: 609
  • Thank you received: 289
Exactly the same results here - If i switch to another band and mode then come back the first time it will work, but if i change repeaters then broken again
73 Rick
The administrator has disabled public write access.

EESDR3 A 0.9.0 - Thoughts so far 10 Sep 2021 21:21 #44

  • N8SDR
  • N8SDR's Avatar
  • OFFLINE
  • Posts: 609
  • Thank you received: 289
Have a friend using V3 0.9.0c ( this would be TCI 1.6) MAC v3 , has anyone using the Mac version be able to get JTDX 32A with TCI to connect and work? in V3 with JTDX error message can not open TCI or can not connect TCI..

It does connect in V2 but not in V3 ? anyone else
73 Rick
The administrator has disabled public write access.

EESDR3 A 0.9.0 - Thoughts so far 11 Sep 2021 01:43 #45

  • VK6NX
  • VK6NX's Avatar
  • OFFLINE
  • Posts: 331
  • Thank you received: 162
DL5RK wrote:
CPU load shows in the MAC-Version around 1-3%, real CPU load is 55-60% and Fans are still blowing loud in my Macbook pro.
The performance under Mac is a long story, which starts with ESDR2. It was reported numerous times with ESDR2 and it there is a believe (according to Roman) of developers, that CPU/GPU usage can be improved in ESDR3 under MAC via utulising Qt6 in-build mechanisms. However, I do not think it will happen just in one click. Currently it appears there is a lot of code, which is ported from ESDR2 source, but actually not yet refactored to utilise Qt6 video/audio native drivers and that what causes CPU to be loaded. Performance enhancements in code writing world is always big task and it always left right to the end, because functionality should go first.

In ESDR3 I have found that even Launcher is CPU hungry. In my Mac when Launcher only started (but main window), it eats around 20% of CPU already, doing nothing as yet, just polling Sun devices presence. When main window started, then Launcher reduces to 0.1-2% of CPU - and that precisely matching what we see in main window measurements - however main window itself starts to use 40-55% of CPU and 25-30% of GPU, The actual CPU/GPU usage dependent on mode, window size on a screen and composition (percentage) of bandscope and waterfall.

I see improvements if compare to ESDR2. In ESDR2 I have up to 65% CPU easily and fans are starting from time to time. In ESDR3 it currently 10% CPU less and have not seen fans starting as yet. Surely, this performance can be improved. But. Not in Alpha and Beta. May be in first release - however this will cause Win and Linux users to wait for release, while developers would work on Mac performance, and I am not sure if Win/Linux users will be thankful for this. Hence, may be in second release. Before that time, I am afraid, we have to live with as it is.

P.S. Actually, CPU performance precisely was the case forced me to start writing my own applications for Log and ATU control. While minimising feature set to absolute necessary minimum in both, I can easily control CPU usage. And CPU usage has direct correlation to battery power (which is imperative for field/dxpeditions operations).
The administrator has disabled public write access.
Time to create page: 0.142 seconds