Hi Steve,
K9An wrote:
> WSJT-X has been running for several hours now, and the day/sunset
> transition seemed to work just as it should.
>
> Regarding the user_hardware issue, would it make sense to send
> the band and the mode as command-line arguments to user_command
> and put the onus on the user-supplied script to “do the right
> thing” when called with a particular band/mode? In many cases,
> the right thing to do might be “nothing”. This would allow
> considering the user_hardware call to be an atomic part of a
> band change sequence.
Yes, of course this will make sense. I won't get to it until next week,
though ...
> I just noticed that if EnableTX is pressed during a “TX” interval,
> then transmission will start immediately. Would it be better to
> set a flag that would cause transmission to start at the beginning
> of the next TX interval rather than jumping in mid-transmission?
We've done it both ways in gthe past; one approach does not fit all
circumstances. During development I've found it convenient (in all
modes) to have transmissions start right away, even if late in the Tx
sequence. Our current "production" release allows starting a
transmission up to about 40% of the way through the Tx sequence -- the
idea being that this makes for enough signal to produce a decode, if the
S/N is adequate.
> With transmission percentage set to 40%, and hopping over 4 bands,
> I’ve seen the rig transmit three times in a row. Is there any
> limit to the number of contiguous transmissions?
We may want to play a bit more with the WSPR scheduling algorithm. At
present there is no limit on the number of consecutive transmissions.
> Finally (for tonight) - I have wide-band interference on 10m and
> 15m that raises the noise floor by several dB whenever the computer
> is polling the radio. Yes, I know that this is really my problem
> and not WSJT-X’s problem! — but I’ve been able to avoid fixing
> the noise issue until now by writing my control program to use
> single rigctl commands to change bands. Since there really isn’t
> a need to poll the rig in WSPR mode, would it be easy to turn
> polling off when in WSPR mode?
I guess we can consider this... (In the meantime, can you simply set
the polling interval to, say, 99 seconds?)
-- Joe, K1JT
------------------------------------------------------------------------------
One dashboard for servers and applications across Physical-Virtual-Cloud
Widest out-of-the-box monitoring support with 50+ applications
Performance metrics, stats and reports that give you Actionable Insights
Deep dive visibility with transaction tracing using APM Insight.
http://ad.doubleclick.net/ddm/clk/290420510;117567292;y
_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
