It appears they are not picked up from the DX4WIN ADIF fields (most. The shallow learning curve, modern features and great support here.
![]() DX4WIN Station Logging Software
I have been using DX4WIN Station Logging Software for about 12 years or more now. I started using it with Version 4 and I have stayed with it because it is very stable. I have been in the software business for almost 40 years and this has been one of the most stable software packages I have used. There are not a lot of updates to this software and that is one reason that it is so stable. A lot of people are coming out with intermediate releases for their software almost daily, and this can lead to failures in their software. There have been very few bugs in their software, as they have been vetted very well before their release.
This is not a contest logging software package, as it is intended to be your station logging software. It does a very good job of reporting and keeping up with all of awards that you want to track. The Packet window connects easily to DXClusters via the internet or via packet radio. The spot show up in both the Packet Window and the DX Spots Window. The software automatically highlights the contacts that you need for the various band/mode awards. The default highlighting is:
It is very easy to import and export contacts with DX4WIN. I mainly use the ADIF imports from my contesting software and ADIF exports to Logbook of the World (LOTW). But it has many options for importing and exporting data, such as, DXBase, DX Desktop, DXLOG, Easy Log, Fast Log, GEMRadio, GENE xls conversion, Hamlog, Hyperlog, Kachina, KD3ZM, a logbook format, Log EQF, Logic for Windows, LogMaster, Logplus, LogView, LogVRR, LogWindows, N6TR, NA, OH1AA, ProLog, SD ARRL, SD CQWW, SD IOTA, N6RJ Second Op, SwissLog, Text, TopLog, Total Ham Plus, TurboLog, UPF IOTA, VA QSO Party, WB2DND, WF1B, WJ2O, WriteLog, WRTC, and XMLog. The other nice thing is that you can create your own custom import/export options with their built-in tool. Of course it has direct export for LOTW functions. I have created several of my own custom import/export functions to interact with my web page and other items. I have also imported Cabrillo formated files into DX4WIN. I am a contester and I either use WriteLog or N1MM and it easily imports the logs into DX4WIN. As long as you can get the data in some form of logical format, you can build an import/export rule to handle the data, especially if you can get it into an ADIF format.
DX4WIN does an excellent job with producing QSL labels/cards. It comes with several pre-configured label formats and again, they have a built-in tool for creating your own custom QSL labels or even printing directly on your QSL cards. Since I keep up with the DXCC Challenge Award, I do a lot of QSLing and it handles it very well. It automatically keeps up with which contacts you need to QSL for the various awards. I receive a lot of card requests from contesting and it is easy to use.
There are a lot of 3rd party add-ons for DX4WIN, also. Jim Reisert, AD1C, has one of the best pages out there with a lot of tools and automated update functions. Jim does an outstanding job with this. He not only has country files for DX4WIN, but other logging programs, also. You can get to his website by going to:
Jim has Country Files, DX Cluster information, DX4WIN Support Site, and Software Tools for Hams. Some of the Software Tools he has are ADIF County Conversion, ADIF to CQ DX Marathon, Analyze Contest Passing, Cabrillo to CT, Contest Club Score, CT to ADIF, and LOTW to CSV. I really commend Jim for all the work he does in support of these software packages and databases. Jim also has utilities to Compare DX4WIN to LOTW DXCC Credits, Create VUCC Map from Award Listing, Convert ADIF to DX4WIN DXQ, Convert .DXN to .CSV, DX4WIN Data Updater, and DXBase to ADIF. There are also others that have good DX4WIN add-ons like 9K2HN, ON4AOI, SP7DQR, and W8TTS.
Of course DX4WIN does CW, RTTY, Packet, PSK31, etc. It has windows for Country, Sunrise/Sunset, IOTA, Log Book, Same Call, State, County, Zone, Grid, WPX, CQ DX Field, Master Calls, and World Map. It has a Report Generator that creates reports for all of the awards and again, has a built-in tool to create your own custom reports. DX4WIN does a very good job of rig control, rotator control, etc. Like I said before, it handles LOTW. It also handles eQSL, but be warned, eQSL is not valid for submitting to the ARRL for any awards because despite eQSL's best efforts to accomodate ARRL's needs for security and accuracy, the ARRL not going to accept your eQSLs for DXCC. It is the ARRL's belief that electronic QSLs cannot be made secure enough to meet their requirements unless each one is encapsulated in a digitally signed package. So if you chase any of the ARRL awards, an eQSL is useless. CQ has announced that they will accept eQSL, but I do not know about it when the ARRL is handling CQ Awards in LOTW.
Needless to say, DX4WIN is a full-featured, robust, station logging package that is very stable. It only runs on Windows Operating Systems unless you can get it to run in Wine on one of the Linux variants. Linux is my preferred operating system, but I still maintain a Windows environment so that I can run all of my ham radio software packages cleanly. You can go to their web site at:
ALLCALL7.TXT update for rc148 versions: ALLCALL7_20200225.zip
rc148
- reordered launching of threads in FT8 decoder
- minor changes to Spt/Menu controls view, reversed broken Pwr slider appearance - 'fusion' is set as default JTDX style, '-style=windows' key in JTDX launching shortcut will switch 'fusion' style off - crossband 160m band operation with Japan is moved to option for all scenarios but EU-JA QSO, by default crossband is enabled, can be switched off in Misc tab of main window UI - patch to possible marker misalignment in QSO RX frequency messages window triggered at double click on message - messages like '73' shall not be treated as 'reply to other' while correspondent using multislot transmission - prevent calling on Fox frequency when user resuming TX after three unsuccessful TX attempts - added optional broadcast of logged QSO ADIF message to secondary UDP server, the same message format as in WSJT-X being used, controls are in 'Reporting' tab of configuration settings, same message format as in WSJT-X is used - 'Logged ADIF' UDP message addressed to primary UDP server now is optional, can be activated in 'Reporting' tab of configuration settings - main frequencies introduced, marked in frequency list by asterisk. At mode change JTDX will be selecting main frequency rather than Fox frequency. Some frequently used DXpedition frequencies added as default values in the frequency list. Main mode&band frequencies can be deleted by user, 'reset frequency list' will recover default frequencies - six-pass SWL option is withdrawn from FT8 decoder - implemented up to 3 cycles of FT8 decoding (each cycle has three decoding passes, six-pass SWL mode was two cycle decoding), one cycle is set by default, two or three cycles can be activated independently for operation and SWL modes. Withdrawn multicycle FT8 decoding dependency on number of running JTDX instances. Still there shall be more than 3 threads used in FT8 decoder to get multicyle decoding active in SWL mode. - Hint button shall be switched on in FT8 mode by default(first launch of JTDX or if .ini file is deleted) - automatic FT8 decoder thread selection shall spare one thread to other tasks if CPU has more than 2 logical cores. If user sure in flawless CPU & software functionality he|she can bring back decoding time selecting manually number of FT8 decoder threads equal to number of CPU logical cores. - FT8 decoder AP masks related code cleanup - main window UI: CAT recovery button is moved up close to frequency label, minor changes to top/right side buttons allocation - thinning FT8 candidate list based on the sync pattern quality: 3..15% decrease of decoding time of FT8 interval - upon accepting configuration settings JTDX shall retain current VFO frequency if it matches to a frequency in the list, else shall set main mode&band frequency - patch for counters when doubleclicked on call which is not in history (no CQ or 73 like messages received from this callsign), first counter did not work in such scenario - ALLCALL7.TXT is now being used for filtering false FT8 decodes with support of 7-char Australian callsigns, ALLCALL.TXT is not used anymore - filtering false decodes: faster callsign search in the ALLCALL7 based list via block data access - added checking for false FT4 decodes starting from 'TU; ' - added SNR and DT criteria for checking FT8 false decodes containing ' R ' - one more attempt to eliminate 'CQ DE AA00' false FT8 decode, it was likely coming from OSD decoder with AP mask in presence of strong signal on the band - LoTW users list is updated, cty.dat file is updated to version CTY-3004 - ALLCALL7.TXT is updated to 111851 callsigns - rc148 is built with modified Hamlib code v20200123
rc147_32a
- 32-bit audio stream support: wideband dynamic range is expanded from 90 up to 186dB.
- JTDX v2.1.0-rc147_32A is built with modified Hamlib v20200123
This experimental version of JTDX is dedicated for trial in setups with very low noise environment on overcrowded bands and receiver's path IMD3 dynamic range greater than 90dB.
In SDR software WDM KS or better driver shall be used, virtual audio cable shall be configured to support 32-bit audio stream.
rc147
- major defect in FT8 decoder fixed for 64bit builds, affected all previous Linux/Mac 64bit JTDX builds: improved FT8 decoder efficiency and decreased decoding time
- JTDX-win64 build is made under Qt 5.14.0, approximately 1.6 times faster in decoding FT8 signals (tested with 4 threads) on overcrowded band versus JTDX-win32 built under Qt 5.5 - reworked meter stuff, now should be also bulletproof around enabling meter for rigs where it is not supported. RF output power indication should work with Icoms: ic7000, ic7100, ic7200, ic7300, ic7410, ic756pro3, ic7600, ic7610, ic7700, ic7800, ic785x with new introduced RFPOWER_METER level function. - attempt to get S-meter indication for Yaesu ft100,ft450,ft600,ft736,ft757gx,ft950,ft1000mp,ft1200,ft2000,ft5000,ft9000 - attempt to enable RF output power indication for new Yaesu radios using newcat protocol - reworked S-meter indication for any new Yaesu radio where newcat protocol being used - FT8 FT4 decoders shall clear in current interval audio frames received prior to the band change - attempt to prevent 'CQ DE AA00' false message created by FT8 decoder - allow to set AF RX frequency below 200 Hz - status bar: date format is changed to DD.MM.YYYY - LoTW users file is updated, cty.dat is updated to CTY-3001 version - JTDX 2.1.0-rc147 is built with modified Hamlib v20200123
rc146
- allow transmission of DXpedition special message from Tx2
- cursor position shall be stored/restored while operator's callsign&grid being edited in configuration settings - empty message shall be treated as false decode in FT4 decoder - some Decode control related code cleanup - workaround to modulator start failure(no TX audio issue) - patch to 'Decode button hung up' issue in FT4 and FT8 modes - JTDX shall not attempt to start decoder if it is working - patch to broken decoding of FT8 signals in scenario where both user's and correspondent's callsigns are nonstandard ones - compound-to-compound callsign QSO Tx message generation is supported now. Compound-to-compound callsign QSO is possible between JTDX 2.1.0-rc146 and MSHV v2.32 users, Tx message generation could be changed in WSJT-X to provide support for such QSO. - two more chars added in displaytext and decoders to fit messages like 'CC2/CC1CCC BB2/BB1BBB R-15' in Band Activity and RX frequency text windows - FT8 decoder shall process signals with 'CQ ??? ???' AP mask if there is nonstandard callsign in DxCall window - improved DxCall searching if there is nonstandard callsign in DxCall window - number of FT8 decoder threads shall not exceed number of logical cores - FT8: added option to SWL mode to utilize 3 more decoding passes ('6 pass SWL mode') if JTDX being run as single instance and CPU has more than three logical cores. Can be activated in 'Decode->FT8 decoding' tab of mainwindow UI. Multiple instances being detected from the rig-name key, it is unreliable approach and shall be reworked in a future version of JTDX. User would need to make sure CPU is not coming into thermal throttling in this mode, and avoid usage of the SWL mode if FT8 decoding time is greater than 15 seconds. - user can add second callsign from a decoded message into wanted callsign list via (CTRL+ALT+double-click) on the message if the list has less than 20 callsigns and this callsign being not located in DxCall window. Wanted callsign list can be cleared via CTRL+ALT+A keyboard shortcut. - reset QSO history counters for new call when DxCall is changed with double click - at double click on decoded message cursor position shall be set prior to emitting of the selectCallsign(alt,ctrl) signal - added option to copy callsign to clipboard at double-click on the decoded message or at autoselection. By default this option is enabled, can be switched off in Misc tab of mainwindow UI. - cty.dat file is updated to version CTY-2918, LoTW users file is updated - JTDX 2.1.0-rc146 is built with updated modified Hamlib as of 20200104
rc145
- added Filter functionality to FT4 mode
- option to hide contest messages is expanded to FT4 mode - added 4th decoding pass to WSPR decoder, improved sensitivity - some cleanup changes to FT8 AP mask functionality - base callsigns shall be used in FT8 AP masks for standard messages in Hound mode - new exceptions added: ???/ND /KT /AG /AE shall not be treated as callsign's prefixes - attempt to make Fox/Hound compound/compound callsign QSO possible in AutoSeq: Tx3 message is changed to '<FoxCompoundCall> MyBaseCall RREPORT' in Hound mode if both callsigns are compound - DX Call signal searching with FT8 AP masks is implemented for CQ/73/RR73 messages raising FT8 decoder sensitivity up to 4dB: QSO RX frequency by default, optionally wideband DX Call search. DX Call signal searching being activated if there is DX callsing in DX Call window, Enable Tx button is switched off and DX Call is not the same as last logged callsign variable value. New mainwindow UI controls: Decode->FT8 decoding->Wideband DX Call search - DX Call signal searching being supported for nonstandard base callsign and compound callsign - DX Call signal searching being supported in Hound mode - 'CQ <...>' message shall be treated as false decode - some code changes based on the Valgrind checking results - wanted grid functionality is implemented, where 4-char grid being supported only, user can fill in comma separated list of grids in the 'wanted' area of main window UI, tooltip added there. 'Wanted grid' in autoselection has the same priority as 'wanted prefix'. - special DXpedition messages shall be underlined with dashed line. To resolve conflict with B4 underlined with straight line B4 special message shall be underlined with the waved line. To avoid any possible confusion starting from rc145 we recommend to use 'strike B4' option instead of the 'underline B4' one. - changed line length for B4 notification (striked|underlined) - QSO history shall forget interrupted/unfinished QSO in 5 minutes since first message transmission - 'wanted' CQ/RR73/73 messages shall have lower priority in autoselection versus any incoming call to user - 'Highlight worked ones' option shall be disabled by default (first run of JTDX with new ini file) - LoTW users file is updated - JTDX 2.1.0-rc145 is built with updated modified Hamlib as of 20191212
rc144
- improved FT4 decoder efficiency and sensitivity
- FT4 decoder shall process signals below 200Hz - WSPR code is updated to WSJT-X 2.1.0 version, WSPR decoding depth can be set in the Decode tab of mainwindow UI, the same controls being used to set JT9 and WSPR decoding depth - added third decoding pass to WSPR decoder, improved sensitivity of WSPR decoder - FT8S decoder shall not be activated since special message is decoded on the QSO RX frequency - FT8S decoder shall not be activated if part of RX audio stream is received in the current interval - minor change to appearance of the Windows text commands in the DX Call text window - several changes to SkipTx1 and Hound mode interaction. State of SkipTx1 shall be stored/restored upon toggling Hound mode button. - transmission of message is not allowed if user callsign is empty in configuration - average DT shall not be calculated for interval where partial RX audio data received - average DT shall be calculated if there is more than one signal decoded in interval, last interval DT weight shall vary with respect to number of messages decoded - reset average DT if mode is changed - FT4/FT8 modes: Band Activity label shall change color to yellow/red and text to 'check time' if there is major/critical average DT delta to computer clock. Average DT thresholds to major/critical 'check time' alarms: 0.4/0.8sec in FT4, 0.75/1.5sec in FT8 mode. - '??? RR73; MyCall ???' and 'MyCall RR73; ??? ???' AP masks for special message shall be used in FT8 decoder in Hound mode - application of AP masks to FT8 decoder in Hound mode is reworked - improved sensitivity for special messages decoding in Hound mode - added AP masks to FT8 decoder for nonstandard DX Call - cty.dat file is updated to version CTY-2916, LoTW users file is updated - rc144 is built with updated Hamlib code&software as of 20191127
rc143
- added exceptions: /LH shall not be considered as country prefix, CQ LP (long path) shall not be processed as direction by autoselection functionality
- changed tooltip to 'strict directional CQ operation' option to: 'By default autoselection ignoring received/transmitted direction of CQ if there is a valid 'new DXCC' message decoded, either incoming call or selection from decoded CQ/73 messages. This option eliminates 'new DXCC' exception in autoselection for directional CQ processing.' - patch to FT8 frequency Filter fuctionality to prevent loss of some candidates if Filter is switched on - improved FT8 decoder efficiency - 4V1000 callsign shall be processed by doubleclick & AutoSeq - some changes to provide gcc8 gcc9 compatibility - second part of compound callsign shall also be considered for DXCC country recognition while reading ADIF data - Tune functionality shall work in Hound mode
rc142
- TX messages addressed to callsigns which prefixes starting from 'CQ' letters shall be correctly handled by AutoSeq
- added FT4 signal simulator - improved sensitivity of FT4 decoder(with no respect to AGCc button setting) - added tooltips in Notifications tab of the settings to RR73/73 and Markers & Other standard messages checkboxes - FT8 AGC compensation functionality is reworked: taking less CPU cycles and shall be automatically skipped if AGC operation is not detected in the current interval - improved FT8 decoder sensitivity while AGC compensation is in operation - patch to avoid empty distance: distance to correspondent with 8-char grid shall be calculated for 6-char grid - bug is fixed in TCP QSO logging debug - DX Grid window data shall be checked for 'new grid' notification if grid for DX Call callsign is absent in QSO history and message with grid is not received. Grid will be stored in QSO history from DX Grid window upon CQ (no grid) or 73/RR73 message received from DX Call callsign, then 'new grid' notification will be using grid from QSO history This functionality is dedicated to users who prefer to enter manually or from CALL3.TXT file grid data in the DX Grid window to check if grid is new one. - DX Grid window shall not be populated from log for /MM /M /AM /P /A callsigns - sliding DT synchronization window is implemented to take in account a latency of RX audio stream (SDR and remote receiver setups, setups with bad computer clock sync) at making candidate list for decoding: FT8: +/- 2.5sec by default, +/- 3.5sec for late start of decoder and SWL functionality FT4: +/- 1.1sec by default, +/- 1.4sec for SWL functionality. Initial DT window (at start of program) is -1.0..+1.4sec by default and -1.2..+1.7sec in SWL mode is applied to 0.0sec DT value. - average DT being used for FT4/FT8 RX sync sliding window shall be displayed in UI above the 'Band Activity' window. Based on this value user can make step-by-step computer clock correction with external software.
This feature is not a physical button or physical slider but software code and have no user adjustment required, this displays the average DT in a cycle.
rc141
- free messages shall be properly recognized by FT4 decoder
- FT4 decoder DT range is extended from -1.0..+1.0 to -1.0..+1.4 sec, in SWL mode to -1.2..+1.7 sec - widegraph dynamic range is restored for 'scale by median' option - improved sensitivity of FT8 decoder at AGC compensation being switched off - widegraph timestamp ini setting shall be correctly handled at program startup - attempt to provide stable UDP Reply operation: Enable Tx and TX interval buttons shall be clicked via UI in MainWindow::processMessage() - gain/zero slider values being now displayed in the widegraph UI - improved sensitivity of FT8 decoder at AGC compensation being switched off - Hint decoder shall stop process non CQ messages if band is changed either from transceiver or from JTDX UI - added debug of TCP connection&exchange for QSO logging, being recorded into tcptrace.txt file located in the JTDX log directory. Debug messages recording shall be enabled in JTDX settings to get TCP trace recorded. - added debug messages recording into ALL.TXT file for RX->TX transition and modulator start failure event, expanded 'double click on call processed' debug
rc140
- prevent displaying vertical lines in waterfall at low level of incoming audio signal for 'Scale spectrum by median value' option
- waterfall timestamp is moved to option for any mode but 'JT9+JT65', can be optionally shown on right side of the waterfall - improved FT8 decoder efficiency and sensitivity - fixed AutoSeq processing of the CQ messages transmitted by user without grid. Affects 1-st counter, own frequency recognition and some other parts of the code, important patch escpecially when using nonstandard or compound callsign. - changed a little New DXCC priority exceptions - fixed long lasting bug on Grid retrieving from log when incoming call with report is received - added FT8 GFSK signal simulator - added support for unpacking WWROF contest exchange messages - Grid button in tab2 shall generate message with grid if first callsign in the message is nonstandard one - implemented basic functionality of FT4 mode - FT4 QSO shall be logged as mode MFSK / submode FT4 into wsjtx_log.adi and via TCP command. UDP log QSO command goes with mode FT4 and shall be parsed properly by an interacting software. - optional AGC compensation functionality is implemented for FT4 mode - improved FT4 decoding - patch: occasional repeat decoding of the partially received interval is eliminated - FT4 partial interval decoding implemented - improved time synchronization at decoding of the partially received interval for all modes - default value for TX delay is changed from 0.2 to 0.1 sec - first part of compound callsign shall be used for prefix recognition if both parts have equal length - LoTW users list is updated, cty.dat file is updated to version CTY-2914 - ALLCALL.TXT file is updated to 97476 callsigns using latest LoTW activity data - installation package is built with the latest Hamlib changes as of October 4th, 2019 and previously made modifications
Rc 134
changed source files:
commons.h, decoder.f90, ft8_decode.f90, ft8_mod1.f90, ft8b.f90, ft8s.f90, ft8sd.f90, ft8sd1.f90, jt9com.f90, msgparser.f90, packjt77.f90, sync8d.f90, tonesd.f90, CMakeLists.txt, Configuration.cpp, decodedtext.cpp, displaytext.cpp, mainwindow.cpp/h/ui, Radio.cpp, ALLCALL.TXT, lotw-user-activity.csv, cty.dat
added new source files(+ added to svn): extract_call.f90, ft8mf1.f90, tonesd.f90 added new parameter into JTDX.ini file: 'NFT8QSORXfreqSensitivity' parameters deleted from JTDX.ini: 'geometryNoControls', 'geometryWanted'
Rc 135
changed source files:
cwfilter.f90, ft8_decode.f90, ft8_mod1.f90, ft8b.f90, ft8s.f90, tone8.f90, tonesd.f90, sync8d.f90, ALLCALL.TXT, CMakeLists.txt, displaytext.cpp/h, lotw-user-activity.csv, mainwindow.cpp, qsohistory.cpp
added new files(also added to svn): ft8mfcq.f90
Rc136
changed source files:
adif.cpp, agccft8.f90, ALLCALL.TXT, commons.h, cty.dat, decoder.f90, displaytext.cpp/h, ft8_decode.f90, ft8_downsample.f90, ft8_mod1.f90, ft8b.f90, ft8s.f90, jt9com.f90, lotw-user-activity.csv, mainwindow.cpp/h/ui, plotter.cpp/h, qsohistory.cpp, symspec.f90, widegraph.cpp/h/ui
Rc137_6
changed source files:
mainwindow.cpp, qsohistory.cpp/h, mainwindow.cpp/h, ft8b.f90
Rc 137
changed source files:
cty.dat, decodedtext.cpp, displaytext.cpp, ft8_downsample.f90, ft8b.f90, lotw-user-activity.csv, mainwindow.cpp/h, qsohistory.cpp/h, Radio.cpp
Rc138
changed source files:
about.cpp, cty.dat, decoder.f90, ft8_decode.f90, ft8b.f90, ft8s.f90, lotw-user-activity.csv, mainwindow.cpp/h/ui
added new parameter into JTDX.ini file: 'SpotText'
Rc139
changed source files:
ALLCALL.TXT, CMakeList.txt, commons.h, cwfilter.f90, decodedtext.cpp, decoder.f90, Detector.cpp/hpp, displaytext.cpp, foxgen.f90, ft8_mod1.f90, ft8b.f90, INSTALL.Debian, jt9com.f90, lotw-user-activity.csv, mainwindow.cpp/h/ui, Modulator.cpp/hpp, plotter.cpp/h, qsohistory.cpp, subtract1...subtract12.f90, soundout.cpp, widegraph.cpp/h
added new source files(also added to svn): lib/gen_ft8wave.f90, lib/gfsk_pulse.f90, lib/gen_ft8wavesub.f90, lib/tone8myc.f90
Rc 2.1.0 140
changed source files:
about.cpp, adif.cpp, ALLCALL.TXT, CMakeLists.txt, commons.h, cty.dat, decoder.f90, displaytext.cpp, Detector.cpp/hpp,
foxgen.f90, FrequencyList.cpp, ft4_decode.f90, ft4_downsample.f90, ft4_params.f90, ft8_downsample.f90, ft8_mod1.f90, ft8b.f90, get_ft4_bitmetrics.f90, getcandidates4.f90, jt9a.f90, jt9com.f90, logbook.cpp, lotw-user-activity.csv, mainwindow.cpp/h/ui, Modes.cpp/hpp, Modulator.cpp, osd4_174_91.f90, packjt77.f90, partint.f90, partintft8.f90, plotter.cpp/h, soundout.cpp, widegraph.cpp/h/ui, subtractft4.f90, sync8.f90 added new source files(also added to svn): ft8sim_gfsk.f90, lib/ft4_decode.f90, lib/ft4_mod1.f90, lib/ft4/ft4_baseline.f90, lib/ft4/ft4_downsample.f90, lib/ft4/get_ft4_bitmetrics.f90, lib/ft4/ft4_params.f90, lib/ft4/getcandidates4.f90, lib/ft4/ldpc_174_91_c_generator.f90, lib/ft4/ldpc_174_91_c_reordered_parity.f90, lib/ft4/osd4_174_91.f90, lib/ft4/agccft4.f90, lib/ft4/partintft4.f90
Rc 141_3
Changed source files:
get_ft4_bitmetrics, plotter.cpp
Rc 141
changed source files:
decoder.f90, ft4_decode.f90, ft8_downsample.f90, ft8b.f90, get_ft4_bitmetrics,
mainwindow.cpp, logqso.cpp/h, plotter.cpp, sync8.f90, widegraph.cpp/ui
Rc 142
changed source files:
adif.cpp, agccft8.f90, CMakeLists.txt, Configuration.ui, cty.day, decoder.f90, displaytext.cpp/h, ft4_decode.f90, ft4_downsample.f90, ft4_mod1.f90, ft8_decode.f90, ft8_downsample.f90, ft8_mod1.f90, ft8b.f90, get_ft4_bitmetrics.f90, logqso.cpp, lotw-user-activity.csv, mainwindow.cpp, sync8.f90
added new source files(also added to svn): ft4sim.f90 ![]()
Rc143
Changed source files
adif.cpp, chkcrc12a.f90, chkfalse8.f90, chkspecial8.f90, commons.h, Configuration.ui, decodedtext.cpp/h, decoder.f90, extractmessage174.f90, ft8_decode.f90, ft8_mod1.f90, ft8apset.f90, ft8b.f90, ft8s.f90, jt9com.f90, mainwindow.cpp, qsohistory.cpp, Radio.cpp, sync8.f90, tone8.f90, tone8myc.f90
Rc144
Changed source files
chkfalse8.f90, CMakeLists.txt, commons.h, cty.dat, decoder.f90, ft4_baseline.f90, ft4_params.f90, ft8_decode.f90, ft8_mod1.f90, ft8apset.f90, ft8b.f90, getcandidates4.f90, jt9com.f90, lotw-user-activity.csv, mainwindow.cpp/h/ui, sync8.f90
/wsprd/ : fano.c, Makefile, metric_tables.c, README, wsprd_utils.c, wsprd.c, wsprsim.c, wsprsim_utils.c, wsprsim_utils.h added new files(also added to svn): osdwspr.f90
Rc145
Changed source files
Bands.cpp, chkfalse8.f90, commons.h, Configuration.cpp, decodedtext.cpp/h, decoder.f90, displaytext.cpp/h, ft4_decode.f90, ft4_mod1.f90, ft8_mod1.f90, ft8apset.f90, ft8b.f90, HamlibTransceiver.hpp, jt9com.f90, lotw-user-activity.csv, mainwindow.cpp/h/ui, plotter.cpp, PollingTransceiver.cpp, qsohistory.cpp, Radio.cpp
deleted JTDX.ini parameter 'HideFT8ContestMessages' added new JTDX.ini parameter 'HideFTContestMessages','FT8WideDXCallSearch','WantedGridCommaList'
Rc146
Changed source files
about.cpp, commons.h, Configuration.cpp, cty.dat, cwfilter.f90, decoder.f90, displaytext.cpp, ft4_decode.f90, ft8_decode.f90, ft8_mod1.f90, ft8b.f90, jt9_decode.f90, jt9a.f90, jt9com.f90, jt9s_decode.f90, jt10_decode.f90, jt65_decode.f90, lotw-user-activity.csv, mainwindow.cpp/h/ui, mousecommands.txt, partint.f90, partint4.f90, partint8.f90, shortcuts.txt, sync8.f90, sync8d.f90
added new parameters into JTDX.ini file: 'sixPassFT8SWLmode','CallsignToClipboard'
Rc147
Changed source files
CMakeLists.txt, commons.h, decoder.f90, ft8mf1.f90, ft8mfcq.f90, HamlibTransceiver.cpp/hpp, jt9com.f90, mainwindow.cpp/h/ui.
Rc14x
Changed source files
VAC 4.60 tuning for usage with JTDX/WSJT-X. Created by Igor UA3DJY on March 15th, 2019.
1. Install both WSJT-X and JTDX, set VAC Line 1 as output audio device in WSJT-X and input audio device in JTDX, push Tune button in WSJT-X and monitor signal in JTDX waterfall.
There is an example of the dirty signal with multiple breaks:
Check VAC ‘ms per int’ settings:
and reduce value there until signal breaks will disappear (you will have to switch off JTDX/WSJT-X to get permission to change this value):
Now try to change audio TX frequency by the CTRL+click in WSJT-X waterfall, monitor signal in JTDX, there is the normal behaviour:
In some setups broken spectrum can be observed at frequency change, for instance like this one:
If you getting such behaviour then run VAC control panel as admimistrator and try to change there capture and render ports from Auto to WavePci (you will have to switch off JTDX/WSJT-X to get permission to change this values):
WavePci is hardcoded as capture/render port in VAC 4.15. Now try change TX frequency in WSJT-X and make sure that proper port selection have eliminated broken signal in your setup:
Set this settings to every VAC cable being used in JTDX/WSJT-X. Now you are ready to go on air.
Subcategories![]() FT8v2 changelog
![]() Comments are closed.
|
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
December 2022
Categories |