Since I am into comparative testing,
The only real way to get an accurate comparison of WSJT-X vs
JTDX is to run an instance of Both programs at the same time on the same band. Basically two slices on the same frequency which is easy to do with the Flex.
As you are aware Flex 6700 is a multi-slice receiver capable of receiving 8 simultaneous digital signals.
I have successfully run multiple simultaneous instances of WSJT on the same and different bands with no issues or conflicts
I have successfully run multiple simultaneous instances of JTDX on the same and different bands with no issues or conflictsHowever when I try to run an instance of WSJT-X and JTDX at the same time the programs seem to hang at decode time.
Any suggestions or ideas?
I just ran two different computers at the same time,
1. One computer 1 Started SSDR with Slice A DAX Channel 1 and Slice B DAX Channel 2
2. Run WSJT on Computer 1 to slice A DAX 1 on 14.076
3. Run JTDX on Computer 2 to DAX 2 on 14.076
4. had to screw around with the controls for JTDX to convince it was connected to the radio
To date my best ever QSO was a DL @ -29 when I ran 1.5KW into my beam (10+KW ERP) so he could hear me and he gave me a -19...
Sort of wish the weak guys would have better receivers as invariably the weak ones are the interesting DX.
Recommended settings for v17.4: http://www.qrz.lt/ly3bg/JTDX/info/rel...
See 17.4 region of the document.
- JT65+JT9 combined mode
- AGCc button: use it only if AGC being triggered in receiver by JT signals at beginning of the RX interval. Noise level change in the waterfall might be used as criterion showing that AGC is triggered in the receiver.
- Hint button: use it to decode signals on the QSO frequency and for wideband hinted decoding of the CQ messages
I use FAST with the slider all the way to the right. AGC OFF has not worked for me as signals vary so much.
Recently my stats on PSKreporter 14.5K reports in 24 hours and 104 countries so something is working!
Saw a test where the AGC button did help with files that had over 300 stations in a minute; however, when there are that many calls to look through a few extra + or - are irrelevant!
It is most likely this issue is connected to the same executable file name wsjtx.exe being used by both software and it is memory sharing issue. Unfortunately now I can not change it to jtdx.exe now as this approach will restrict JTAlert usage for HRD software users.
In some scenario I did run both WSJT-X and JTDX on the same computer under Windows 10, I did use --rig-name key for one of them and software starting order makes sense there also.
73 Igor UA3DJY
NOW for a COMPLETELY DIFFERENT ISSUE
On one computer, WSJT-X receives to about 1200Hz
On the second computer, WSJT-X receives full bandwidth
Both running W7/64 -
WSJT Configurations are EXACTLY the same.
Results do not differ for the following variations
1. on any different DAX Channel
2. I can run an instance of WSJT simultaneously on both computers or NOT
3. I can share the same DAX Channel or Not
4. I can run SSDR on either computer
DAX Version is the most current Alpha version on both computers.
The first computer is an i7 and the second computer is an i5
Both have lots of memory.
Any guesses as to why I only receive 1200Hz on that one computer????
Start WSJT-X and JTDX from a command-prompt window, passing each instance a unique identifier (MACHINE NAME) as in the following two-instance example. This procedure will isolate the Settings file and the writable file location for each instance of WSJT-X AND JTDX
wsjtx --rig-name=WSJT wsjtx --rig-name=JTDX
NOTE: BOTH WSJT AND JTDX USE THE SAME PROGRAM NAME WSJTX
last night, pskReporter says I heard SV9CVY, IS0XRB, CT1EKY, DL5MGV, DK3DG, G3LDI, and SM6NOC, all on 160m. and top band has been LOUSY. while none were new, it is interesting
recent all night runs, while i'm sleeping, with wsjt 17 would only turn up one or 2 europeans.
thanks for the heads up, howard. maybe i'll finally get mainland china ?? which i DO need..
73, w5xz, dan
- 5375 Conversations
- 1675 Followers
- 3152 Conversations
- 652 Followers
- 3694 Conversations
- 963 Followers
- 1014 Conversations
- 407 Followers
- 496 Conversations
- 177 Followers
- 440 Conversations
- 154 Followers
- 398 Conversations
- 142 Followers
- 3053 Conversations
- 872 Followers
- 1016 Conversations
- 260 Followers
- 467 Conversations
- 142 Followers