RX2 enabled at Start results in RX2 signal strength display lock up at-399dbm about thetis HOT 16 CLOSED

version? as it defaults to -200dBm on both RX1 and RX2 at startup here

from thetis.

Richie,
After starting Thetis I see -200dbm in the RX1 signal meter before I hit the power button.

If I start Thetis with RX2 already enabled, and then hit power button the RX2 signal meter reads -399dbm.

I have to disable RX2, shut down thetis, then restart Thetis. Once I hit the power buton Then I can enable RX2 and the RX2 signal meter works as expected.

Bill

from thetis.

What version of thetis are you running? and radio?

If you start Thetis with RX2 enabled, do you see -200dBm in RX2 meter before your power on the radio? So does it change from -200dBm to -399dBm? Have you tried doing a backup of your database, and setting up a new one to check?

R.

from thetis.

Yes, if I start Thetis with Rx2 enabled I see -200dbm in the RX1 and RX2 Meters.
When I then hit the power button the RX2 meter displays changes from -200dbm to -399 dbm and will not change while Thetis is running..

I just reset the database. Without making any settings changes in Thetis, upon startup the Rx2 meter reads -200dbm until I hit the power button and then it displays -399dbm.

I just discovered that I can get RX2 meter to recover if I change RX2 bands. Restarted and repowered several times and the Rx2 band change fixes the meter. Reloaded my original database and the same issue is present.

from thetis.

I can not replicate this, and there have been no other reports. I ask again, what radio are you using? What version of Thetis are you using?

from thetis.

Richie,
100D, P1, Thetis 2.9.x. I have experienced this with various Thetis releases. Currently running 2.9.0.7 with meters.

Start Thetis with Rx2 enabled, then hit the power button :

Now, simply select another Rx2 band and here is what you get.

Apparently a Rx2 initialization issue at startup. Instead of selecting another band after the issue appears I can just select the same rx2 band in place at startup and the problem goes away.

PowerSDR 3.4.9 does not exhibit the same problem with Rx2 initialization.

Thanks for looking into this.

Bill

from thetis.

Hi Bill,

Please can you email me your database.xml file that is in use when this problem occurs. I have spent an hour looking at the code and nothing stands out. I have also checked PowerSDR and all looks ok.

Thanks.

from thetis.

Richie,

I can reproduce this by selecting VFO B for Tx and cycling the power button. I know I fixed this on the HL2 release but I can't find the actual fix in my git repository.

Cheers

Reid
Gi8TME/Mi0BOT

from thetis.

Reid,

I have just run a diff on your source vs my latest, and it all looks the same in relation to rx2 meter readings and offsets etc, very odd. rx2_meter_new_data is the variable that holds the readings in console.cs together with a bunch of offsets. meter.c + dsp.cs are identical. Also, I can't replicate the error at all, I have never seen it in years of using the radio. I have a gut feeling it is a firmware problem to be honest, or the database is up the duff with some odd entries for the offsets. Hopefully Bill will email me his database.xml.

Cheers

Richie.

from thetis.

I don't think it's in the metering but the startup code. If I remember right, the problem could be corrected for by switching Tx back to VFO A. I'll try and do a comparison of the code.

Cheers

Reid.

from thetis.

No difference really in InitConsole, the Console constructor, or getOptions or Setup constructor.

from thetis.

from thetis.

Richie,
Once the problem is observed after power up, it can be cured by selecting a rx2 band, or hitting tune, mox or as Reid said by switching VFO's from B to A. I wonder if it is a sequencing issue at power up, rather than a code issue.

from thetis.

database.txt
database.txt

from thetis.

Richie,

Found the change I made in setup.cs - I removed the test for Protocol 2.

Cheers

Reid.

from thetis.

@reid I had noticed this when working through the source differences, but had not twigged it was the cause. Thanks !

from thetis.