Re: [wsjt-devel] VFO-B behavior
One more thought – if this group really is intended for software development issues, can a separate user support group be created to keep the programming and operator issues separate? It could be mentioned on the WSJT-X webpage or in the documentation. I think there are many who would volunteer to be in the group to take some of the burden off the developers. 73, N4EFS From: Rebecca Milligan [mailto:rebeccamilli...@comcast.net] Sent: Monday, March 4, 2019 6:47 PM To: 'WSJT software development' Subject: RE: [wsjt-devel] VFO-B behavior I think it would be difficult for the developers to address every rig out there and every circumstance. I consider the software a gift as I did not have to pay for it and I am glad to put some effort into experimenting and reading available documentation to see what works best for my situation. There are a lot of forums, posts and videos posted on the web by Hams discussing such topics specific to WSJT-X. The manual does address “Fake It” by basically saying each user should choose what works best for them: “Split Operation: Significant advantages result from using Split mode (separate VFOs for Rx and Tx) if your radio supports it. If it does not, WSJT-X can emulate such behavior. Either method will result in a cleaner transmitted signal, by keeping the Tx audio always in the range 1500 to 2000 Hz so that audio harmonics cannot pass through the Tx sideband filter. Select Rig to use the radio’s Split mode, or Fake It to have WSJT-X adjust the VFO frequency as needed, when T/R switching occurs. Choose None if you do not wish to use split operation.” “On the Radio tab select Split Operation (use either Rig or Fake It; you may need to experiment with both options to find one that works best with your radio).” “Be sure that your rig control has been set up for Split Operation, using either Rig or Fake It on the Settings | Radio tab.” It is not my intent to offend anyone. It just seems that this group, which I thought was intended for software development issues, such as bugs in the actual software, has been steered towards answering questions that are addressed in the manual or problems resulting from operator error (clocks, notch filters, QRM, etc.) I may have misunderstood the purpose of this group so I could be way off base. 73, Rebecca, N4EFS From: Paul Kube [mailto:paul.k...@gmail.com] Sent: Monday, March 4, 2019 6:07 PM To: marting0...@gmail.com; WSJT software development Subject: Re: [wsjt-devel] VFO-B behavior " perhaps there should be a note in the User Manual that, at least for Icom rigs, the 'Fake It' split mode is preferred/recommended?" "Rig" mode works fine with my IC-7200 and IC-7300. 73, Paul K6PO On Mon, Mar 4, 2019 at 1:45 PM Martin Davies G0HDB wrote: On 4 Mar 2019 at 4:51, Black Michael via wsjt-devel wrote: > Both conditions need to fixed. VFO-A needs to be set as selected VFO > and VFO-B set to the split freq at all times. Otherwise a tune > instigated from an external source will be on the wrong frequency.And > yes...I know you can click Tune in WSJT-X and then VFO-B gets > set...but that leaves the amplifier in-line with too much power to > tune and for some could fry the amplifier. > Mike Hi Mike (and all), for what it's worth I've found that using the 'Fake It' split mode, rather than the 'Rig' mode, works best with my Icom IC-7600. Some years ago, when I first tried using the 'Rig' mode with WSJT I found that the time taken to switch VFOs (from A to B in my case) and then to re-tune the newly-selected VFO with the desired offset (eg. +1kHz) was significantly longer than just re-tuning the active VFO, presumably because there was a longer command sequence to be received, processed and then actioned by the rig. The delay in the rig switching VFOs and then re-tuning was resulting in the transmission not starting until (IIRC) some 2-3secs into a Tx period. I would assume that using the 'Fake It' mode would work equally well irrespective of which VFO was the active one, so perhaps there should be a note in the User Manual that, at least for Icom rigs, the 'Fake It' split mode is preferred/recommended? -- 73, Martin G0HDB --- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] VFO-B behavior
I think it would be difficult for the developers to address every rig out there and every circumstance. I consider the software a gift as I did not have to pay for it and I am glad to put some effort into experimenting and reading available documentation to see what works best for my situation. There are a lot of forums, posts and videos posted on the web by Hams discussing such topics specific to WSJT-X. The manual does address “Fake It” by basically saying each user should choose what works best for them: “Split Operation: Significant advantages result from using Split mode (separate VFOs for Rx and Tx) if your radio supports it. If it does not, WSJT-X can emulate such behavior. Either method will result in a cleaner transmitted signal, by keeping the Tx audio always in the range 1500 to 2000 Hz so that audio harmonics cannot pass through the Tx sideband filter. Select Rig to use the radio’s Split mode, or Fake It to have WSJT-X adjust the VFO frequency as needed, when T/R switching occurs. Choose None if you do not wish to use split operation.” “On the Radio tab select Split Operation (use either Rig or Fake It; you may need to experiment with both options to find one that works best with your radio).” “Be sure that your rig control has been set up for Split Operation, using either Rig or Fake It on the Settings | Radio tab.” It is not my intent to offend anyone. It just seems that this group, which I thought was intended for software development issues, such as bugs in the actual software, has been steered towards answering questions that are addressed in the manual or problems resulting from operator error (clocks, notch filters, QRM, etc.) I may have misunderstood the purpose of this group so I could be way off base. 73, Rebecca, N4EFS From: Paul Kube [mailto:paul.k...@gmail.com] Sent: Monday, March 4, 2019 6:07 PM To: marting0...@gmail.com; WSJT software development Subject: Re: [wsjt-devel] VFO-B behavior " perhaps there should be a note in the User Manual that, at least for Icom rigs, the 'Fake It' split mode is preferred/recommended?" "Rig" mode works fine with my IC-7200 and IC-7300. 73, Paul K6PO On Mon, Mar 4, 2019 at 1:45 PM Martin Davies G0HDB wrote: On 4 Mar 2019 at 4:51, Black Michael via wsjt-devel wrote: > Both conditions need to fixed. VFO-A needs to be set as selected VFO > and VFO-B set to the split freq at all times. Otherwise a tune > instigated from an external source will be on the wrong frequency.And > yes...I know you can click Tune in WSJT-X and then VFO-B gets > set...but that leaves the amplifier in-line with too much power to > tune and for some could fry the amplifier. > Mike Hi Mike (and all), for what it's worth I've found that using the 'Fake It' split mode, rather than the 'Rig' mode, works best with my Icom IC-7600. Some years ago, when I first tried using the 'Rig' mode with WSJT I found that the time taken to switch VFOs (from A to B in my case) and then to re-tune the newly-selected VFO with the desired offset (eg. +1kHz) was significantly longer than just re-tuning the active VFO, presumably because there was a longer command sequence to be received, processed and then actioned by the rig. The delay in the rig switching VFOs and then re-tuning was resulting in the transmission not starting until (IIRC) some 2-3secs into a Tx period. I would assume that using the 'Fake It' mode would work equally well irrespective of which VFO was the active one, so perhaps there should be a note in the User Manual that, at least for Icom rigs, the 'Fake It' split mode is preferred/recommended? -- 73, Martin G0HDB --- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] Candidate release WSJT-X 2.0.0-rc5
From: Edfel Rivera [mailto:edfelj...@gmail.com]
Sent: Monday, November 26, 2018 6:53 PM
To: WSJT software development
Subject: Re: [wsjt-devel] Candidate release WSJT-X 2.0.0-rc5
Hi All:
Just to remind to operate beyond 2 hz.
73'
Edfel
KP4Aj
On Mon, Nov 26, 2018 at 6:30 PM Krzysztof Krzemiński wrote:
Hello,
already done first contacts using RC5.
SUPER
Kris, SP5NOH
pon., 26 lis 2018 o 22:58 Joe Taylor napisał(a):
A fifth candidate release ("RC5") of WSJT-X 2.0 is now available for
download and use by beta testers. RC5 is stable, works well, and fixes
the known problems in RC4. It is likely that the General Availability
(GA) release of WSJT-X 2.0, scheduled for two weeks from today, will be
nearly identical to RC5.
Changes in RC5 relative to RC4 include the following:
- Make the "Auto Seq" checkbox sticky, again
- Remove the 5-minute mouse timer
- Correct the "worked before" logic for color highlighting
- Add "No own call decodes" checkbox in WSPR mode
- Display and log UTC (not local time) in contest operations
- Validate contest QSO details before allowing logging
- Force Aqua theme on macOS to avoid issues with Mojave dark theme
- Move Fox log Reset action to Fox log window context menu
- Improve layout of Working Frequencies and Station Information tables
- Allow deletes and editing in Fox and Contest log windows
- Add Tool Tips for Fox and Contest log windows
- Fix a bug causing false AP decodes in JT65 VHF+ operation
- Fix a bug that could switch unexpectedly from JT65 to JT9 mode
You may need to invoke "Settings | General | Colors | Reset
Highlighting" on your first program start with this version.
The "Quick-Start Guide to WSJT-X 2.0" has been updated. Be sure to read
this entire guide before using RC5:
http://physics.princeton.edu/pulsar/k1jt/Quick_Start_WSJT-X_2.0.pdf
We recommend using RC5 (and therefore the v2.0 FT8 protocol) in the
conventional FT8 sub-bands at audio Tx frequencies 2000 Hz and higher.
Inevitably the necessary transition from v1.x to v2.0 protocols for FT8
and MSK144 will cause some confusion and cross-protocol interference.
Users of v1.9.1 and earlier are unable to decode transmissions from
users of RC4 and later, and vice-versa.
As more users upgrade their software to WSJT-X 2.0 -- and particularly
after the General Availability (GA) release on December 10 -- the new
protocol should start to dominate the conventional FT8 sub-bands. As
soon as possible after December 10, everyone should upgrade to WSJT-X 2.0.
Download links for RC5 on Windows, Linux, and macOS can be found on the
WSJT-X web page http://physics.princeton.edu/pulsar/k1jt/wsjtx.html
A final FT8 "practice contest" will be held on Saturday, December 1,
0200-0300 UTC (that's Friday evening, Nov 30, NA time). Watch for a
separate announcement with more details.
If you find any unexpected behavior with WSJT-X 2.0-rc5, please send a
detailed report to the wsjt-devel email list,
wsjt-devel@lists.sourceforge.net. You must subscribe to the list in
order to post there.
The first serious FT8 contest is scheduled for the weekend of December
1-2. See https://www.rttycontesting.com/ft8-roundup/ for full details
and contest rules. The ARRL RTTY Roundup (January 5-6, 2019) permits
and encourages FT8 as well as traditional RTTY operation.
ONCE MORE: As soon as possible after December 10, and certainly by
January 1, 2019, everyone should be using WSJT-X 2.0 or a compatible
v2.0 version of derivative programs such as JTDX or MSHV. As of today,
PSKreporter statistics show roughly 3000 users of WSJT-X versions older
than v1.9.1, 9500 users of v1.9.1, and 3000 users of v2.0-rc#. Please,
everyone, help us to spread the word that upgrading to v2.0 after
December 10 is very important. There will be no looking back!
-- 73, Joe, K1JT (for the WSJT Development Group)
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
--
Kris, SP5NOH
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
