Hi,
I've been running wsjt-x for a long time with my Flex 6300.
Nearly continuous WSPR operation hopping all HF bands + 6M, and
monitoring 630m and 2190m.
Currently (past several years) running win7pro in vmware workstation on
my linux (ubuntu) laptop. All solid there except for the first bug.
I'm trying to move this off of my laptop and into my shiny new proxmox
cluster on a Win 10 Pro vm.
WSJT-X version: 6.2.1
____
First bug: When starting up WSPR I [Enable TX] so that the system can
tune my antenna when band hopping and so that it can transmit 20% of the
time (defaults). HOWEVER, after the first tune cycle, and sometimes the
second or third, [Enable TX] will switch itself off. This means that I
have to baby-sit wsjt-x for several minutes before it will operate reliably.
This is repeatable any time I'm starting up WSJT-X... at least 1 cycle I
must re-enable TX, and often 2 or 3 before it will stay enabled.
____
Second bug: On Windows 10 Pro proxmox VM: I have successfully loaded the
DAX drivers, and CAT. I can successfully control the radio through
WSJT-X. It appears to read audio from the radio and it successfully
sends audio for tuning etc... So connectivity to the radio seems fine.
I'm using the baked in VNC Console because RDP is problematic for the
audio drivers.
HOWEVER (Here's the bug) When I start up WSPR mode (same config from my
working system) it will complete the current cycle, it will change bands
and tune the radio, but then it will never do that again... something
deep inside is stuck. As per the previous bug, the first time it tunes
it disables tx.
While this is happening,... the audio is still recognized, the waterfall
still falls, the controls for WSJT-X still work as expected. For
example, I can toggle [Enable TX], I can [Stop] and [Monitor] with all
of the expected results; the clock continues to run and the progress bar
continues to move as expected.
Except: Tx Next is ignored; and nothing is ever reported in the window
(no Receiving/Transmitting WSPR lines, no decodes, etc). It's kind-of a
zombie.
Occasionally, at random, it will work normally but only if I'm not
watching it in the VNC Console, but only in receive... likely because it
disables [Enable TX] ... I can hear it switch bands in the radio
(relays) and when I go back and look I can see events recorded in the
window... but then it will stop working again. Working cases are rare.
If we can figure out what inside of it is getting "stuck" and make it
robust against that then I can continue to work out the remaining
problems and get this up and running solidly.
Any idea what could be stuck like that while leaving the GUI and
waterfall "normal" ? ... just the automation and decode seem stuck under
the covers.
VM is set up with
4 Cores
Host CPU (running on i5 Nuc)
8G Ram
64G Hdd
Fixed IP on private network
Windows 10 Pro, up to date
Power settings are Never Sleep
Flex SDR software seems completely normal and happy on this vm.
Thanks!
_M
--
kf4hcw
Pete McNeil
lifeatwarp9.com/kf4hcw
_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
