Welcome to the new FlexRadio Community! Please review the new Community Rules and other important new Community information on the Message Board.
Need the latest SmartSDR, Power Genius, Tuner Genius and Antenna Genius Software?
SmartSDR v3.8.19 and the SmartSDR v3.8.19 Release Notes | SmartSDR v2.12.1 and the SmartSDR v2.12.1 Release Notes
SmartSDR v1.12.1 and the SmartSDR v1.12.1 Release Notes
Power Genius XL Utility v3.8.8 and the Power Genius XL Release Notes v3.8.8
Tuner Genius XL Utility v1.2.11 and the Tuner Genius XL Release Notes v1.2.11
Antenna Genius Utility v4.1.8
SmartSDR v3.8.19 and the SmartSDR v3.8.19 Release Notes | SmartSDR v2.12.1 and the SmartSDR v2.12.1 Release Notes
SmartSDR v1.12.1 and the SmartSDR v1.12.1 Release Notes
Power Genius XL Utility v3.8.8 and the Power Genius XL Release Notes v3.8.8
Tuner Genius XL Utility v1.2.11 and the Tuner Genius XL Release Notes v1.2.11
Antenna Genius Utility v4.1.8
If you are having a problem, please refer to the product documentation or check the Help Center for known solutions.
Need technical support from FlexRadio? It's as simple as Creating a HelpDesk ticket.
Need technical support from FlexRadio? It's as simple as Creating a HelpDesk ticket.
wsjt-x field day 2019
Tom Worthington
Member ✭✭
WSJT-x has support for Field Day this year, but not everyone will be operating in FD mode.
We always work a lot of DX stations who are not in FD. At night we point a 20m beam to Asia and take advantage of the propagation. In SSB and CW we just log these stations as 1D DX.
That is going to be a problem with WSJT-x in FD mode. It does not send the expected signal report message and will not log the QSO.
During a recent test contest it was very difficult to deal with stations responding to a CQ in non contest mode. This is sure to be much worse during FD when the bands are completely swamped with stations. One solution that I have tested for this is to run two separate instances of WSJT-x, using the same radio (both physical and logical and slice), one set for FD contest mode and the other for standard mode. I added a 2nd TCP port and PTT port for the second instance. Both instances send log data to a single instance of N1MM+. There are some issues. The standard instance of WSJT-x logs a contact with the correct call sign and mode, but leaves the class and section empty. This is not really a problem because all that is required to remove the DUPS is the call sign and mode. Since FD does not include log checking, is does not matter what is in the class and section fields. The FD instance of WSJT-x will (presumably since I haven't gotten any live testing data) correctly fill in the Class and Section information in the log.
The only issue I've run into so far is that the system is perfectly happy carrying on two QSO's simultaneously, transmitting two signals on different audio offsets. I've seen DX stations do this but it is, I believe, a violation of FD rules. I suspect it will take some practice but if I give preference to working FD stations it may be a good solution with dealing with non-FD stations.
What could possible go wrong? :-)
Please look for us during Field -- KH6RS
73 and Aloha, Tom, NH6Y
We always work a lot of DX stations who are not in FD. At night we point a 20m beam to Asia and take advantage of the propagation. In SSB and CW we just log these stations as 1D DX.
That is going to be a problem with WSJT-x in FD mode. It does not send the expected signal report message and will not log the QSO.
During a recent test contest it was very difficult to deal with stations responding to a CQ in non contest mode. This is sure to be much worse during FD when the bands are completely swamped with stations. One solution that I have tested for this is to run two separate instances of WSJT-x, using the same radio (both physical and logical and slice), one set for FD contest mode and the other for standard mode. I added a 2nd TCP port and PTT port for the second instance. Both instances send log data to a single instance of N1MM+. There are some issues. The standard instance of WSJT-x logs a contact with the correct call sign and mode, but leaves the class and section empty. This is not really a problem because all that is required to remove the DUPS is the call sign and mode. Since FD does not include log checking, is does not matter what is in the class and section fields. The FD instance of WSJT-x will (presumably since I haven't gotten any live testing data) correctly fill in the Class and Section information in the log.
The only issue I've run into so far is that the system is perfectly happy carrying on two QSO's simultaneously, transmitting two signals on different audio offsets. I've seen DX stations do this but it is, I believe, a violation of FD rules. I suspect it will take some practice but if I give preference to working FD stations it may be a good solution with dealing with non-FD stations.
What could possible go wrong? :-)
Please look for us during Field -- KH6RS
73 and Aloha, Tom, NH6Y
0
Comments
-
I don't believe this is a violation as long as you count it as two transmitters.0
-
0
-
I see. I would expect a transmitter to be the hardware itself (physical radio), regardless of what software is interfaced to it.0
Leave a Comment
Categories
- All Categories
- 289 Community Topics
- 2.1K New Ideas
- 536 The Flea Market
- 7.5K Software
- 6K SmartSDR for Windows
- 146 SmartSDR for Maestro and M models
- 360 SmartSDR for Mac
- 250 SmartSDR for iOS
- 231 SmartSDR CAT
- 172 DAX
- 353 SmartSDR API
- 8.8K Radios and Accessories
- 7K FLEX-6000 Signature Series
- 32 FLEX-8000 Signature Series
- 851 Maestro
- 44 FlexControl
- 847 FLEX Series (Legacy) Radios
- 799 Genius Products
- 417 Power Genius XL Amplifier
- 279 Tuner Genius XL
- 103 Antenna Genius
- 243 Shack Infrastructure
- 166 Networking
- 404 Remote Operation (SmartLink)
- 130 Contesting
- 632 Peripherals & Station Integration
- 125 Amateur Radio Interests
- 873 Third-Party Software