|
locked
Re: #BugReport
#IssueReport
On 04/02/2021 16:25, David Ackrill wrote:
Dave, that decoding takes many millions of CPU cycles, it cannot be instant. There will surely be some optimizations that speed things up but this is just the first release candidate and there are still some rough edges. Use a narrower FTol once you know where your QSO partners are and decoding will be much faster. If you are on a sked then check the "Settings->General->Single decode" option to save the decoder having to look for signals outside of the FTol frequency window. 73 Bill G4WJS.
|
|
|
|
locked
#BugReport
#IssueReport
I've used the hastag "BugReport" as there didn't seem to be anything else that would cover this. Using Q65 today someone, on one of the KST Chat rooms, mentioned that it was taking a long time from the end of a reception period before the decoded message appeared in the left-hand 'message' window on his set up. I put a stopwatch on it, on my set up, and found the following delay from when the blue "Decoding" button came on until when the display put the previous RX period results up. Q65-15A = 7 seconds, 15B = 6 seconds and C = 5 seconds. Q65-30A = 7 seconds, B = 7.5 seconds and C = 6 seconds. The 'decoding' button does come up before the end of the RX period, of course, but the decoded message still took between 3 and 5 seconds to appear after the end of the RX period. The other guy on the forum was reporting the decode not coming up until nearly the end of the transmit period on his set up at times, I have tried to be careful not to load up a lot of 'stuff' onto this 'new' (refurbished) machine so as not to slow it up too much. I also noticed that, at times, the blue 'decoding' button stayed on well into the next period, but I couldn't say why, or whether that was supposed to happen, so I've ignored it at the moment. Has anyone else noticed a significant delay in decoding on Q65? Cheers - Dave (G0DJA)
|
|
|
|
locked
Re: WSJT-X 2.4.0 RC1 ceash MacOS
#IssueReport
On 04/02/2021 14:42, alex wrote:
I just installed 2.4.0 RC1 next to 2.3.0 on MacOS Big SurHi Alex, see this post from the wsjt-devel Source Forge list: https://sourceforge.net/p/wsjt/mailman/message/37212133/ 73 Bill G4WJS.
|
|
|
|
locked
Re: Multiple Instances of WSJTX ..
#FT8
#WSJTX_config
On 04/02/2021 14:13, Dave H wrote:
Hi Dave, that is not necessary when using multicast IP, but some servers, notably JTAlert, do not handle multicast quite right and require each WSJT-X instance to send to a different service port :( 73 Bill G4WJS.
|
|
|
|
locked
Re: #bugreport
#IssueReport
Mike Lavelle K6ML
I get the exact same error running 2.4.0-rc1-win64 at the end of first JT4 decode period.
Does not happen in Q65/FT8/FT4 modes, will try some others
|
|
|
|
locked
Re: Is this supposed to happen?
#FoxAndHound
#IssueReport
Tony Collett
Thanks Bill (& Dave)
I realised this was expected behaviour, as you say 3 periods then moved into what I called "no mans land" . Good to know that if propagation or QRM allowed it would probably have completed even though I successfully chose to start fresh above 1000Hz. What I didn't expect was that there appeared to be no time out on my subsequent transmissions while I was sending the report. - For the record how long would I have continued to transmit his report - is this set by the usual Tx timer that is set for "normal" FT8 mode or would it have continued forever until I decided to give up? Thanks Tony G4NBS
|
|
|
|
w5ec
What was the idea behind the box?
|
|
|
|
locked
WSJT-X 2.4.0 RC1 ceash MacOS
#IssueReport
alex
I just installed 2.4.0 RC1 next to 2.3.0 on MacOS Big Sur
|
|
|
|
locked
Re: Multiple Instances of WSJTX ..
#FT8
#WSJTX_config
Dave H
Hi Karza,
Thanks.. 73 Dave G8LIY
|
|
|
|
locked
Re: Multiple Instances of WSJTX ..
#FT8
#WSJTX_config
Dave H
Hi Amos.. Thanks... I plan to use.? GRIDTRACKER if I can 73 Dave G8LIY
|
|
|
|
locked
Re: Multiple Instances of WSJTX ..
#FT8
#WSJTX_config
Dave H
Hi Bill, Another Q.? I assume I will therefore need a UDP Port Nos# per instance.
|
|
|
|
Bob K4RCG
HIHIHI I find the freq box handy! :-) I have a few FST4W skeds with DX stations and we use the freq to help ID traces of the participating stations if operating "random". I don't know how to turn it off, but it is easier when using FST4W than "hovering" over the traces to ID the Hz. 73 de Bob K4RCG
|
|
|
|
locked
Re: Is this supposed to happen?
#FoxAndHound
#IssueReport
John, K9MM
From: Tony CollettI had this same experience with 4U1UN on 30M. After sending my transmission several times at about +750, the QSO completed. I noted that while many of the stations calling were loud, they were frequently receiving reports lower than -15. Possibly he has high noise levels or a receiver problem? I had observed this same F/H behavior with 4U1UN a few days earlier on 40M, but didn't manage to work him that time. 73, John, K9MM
|
|
|
|
locked
Re: Is this supposed to happen?
#FoxAndHound
#IssueReport
On 04/02/2021 02:42, David Piersall wrote:
You've given a very good description of how Dxpedition mode works. Three strikes and you're out, as we say in the US.Dave, "kicked into the weeds" is not what is happening here. If you can't complete with the Fox in a couple of overs WSJT-X will shift you up a couple of hundred Hertz to allow stations with better propagation to be worked, but the Fox is still able to decode your signal and reply. Admittedly after a couple of minutes your best strategy is to move up above 1000 Hz and call again when you hear the Fox. If you are just waiting for an RR73 from the Fox then persevere a bit longer as the Fox will keep replying to R+report messages even if they have already logged the QSO. 73 Bill G4WJS.
|
|
|
|
locked
#BugReport Wsjt-x 2.3.0 and Ubuntu 20.4 + K3s
#IssueReport
Nando Pellegrini
I am reporting a problem trying to use WSJT-x and the above configuration
I started with release 1.1 and it was working perfectly, release 2.2 and 2.3 are giving the same results: no tone output to tranceiver via the USB connection. The input is instead working , i am not using the CAT (none as transceiver in the configuration). Let me add also an inconvenient in selection the audio devices to be chosen, the USB device list which is very long and where is impossible to understand what is the desired device without a correspondence with the Linux system naming. What i did (but not the best solution) i have been addressing the USB audio input and output as default device to the system and selecting default as audio device in the wsjt configuration. Doing it i am able to receive but not to send while i am able to send from the system a .wav file addressing the K3s which means a working physical connection. The mode i am using is JT65, it would be nice to have it working and avoid to be forced to remove the default on board audio from the Linux configuration while using WSJT. Thanks for the attention , i1ndp nando
|
|
|
|
On 04/02/2021 02:38, Pat via groups.io wrote:
Hi BillHi Pat, please upgrade to v2.3.0. 73 Bill G4WJS.
|
|
|
|
locked
#BugReport
#IssueReport
alex
Hi,
I just installed WSJT-X 2.4.0 RC1 on a RasPi over 2.2.0. Now I have an error on starting WSJT-X. It says : locale::facet::_S_create_c_locale name not valid 73's de PE1EVX, Alex
|
|
|
|
locked
#bugreport
#IssueReport
Dave Crook
Just loaded 2.4.0 rc1 and was monitoring jt4d and jt4F, both crashed with error EXIT CODE 2, and the following detail:: reinstall v2.3.0 and all ok. Running: C:\WSJT\wsjtx\bin\jt9 -s WSJT-X -w 1 -m 3 -e C:\WSJT\wsjtx\bin -a C:\Users\Dave\AppData\Local\WSJT-X -t C:\Users\Dave\AppData\Local\Temp\WSJT-X At line 13 of file C:\Users\bill\src\k1jt\wsjtx\lib\pctile.f90 Fortran runtime error: Index '-26' of dimension 1 of array 'tmp' below lower bound of 1
Error termination. Backtrace:
Could not print backtrace: libbacktrace could not find executable to open #0 0xffffffff #1 0xffffffff #2 0xffffffff #3 0xffffffff #4 0xffffffff #5 0xffffffff #6 0xffffffff #7 0xffffffff #8 0xffffffff #9 0xffffffff #10 0xffffffff #11 0xffffffff #12 0xffffffff #13 0xffffffff #14 0xffffffff #15 0xffffffff 73 Dave ZL2MQ
|
|
|
|
locked
Re: #Install #BugReport #WSJTX_config WSJT-X not working after 2.3.0 install
#install
#IssueReport
#WSJTX_config
Reino Talarmo
Hi Jim, With earlier versions v1.8.0 or so I had quite often restart also PC in that kind of situations. Also rig needed to be powered up before starting wsjt-x. 73, Reino OH3mA
From: main@WSJTX.groups.io [mailto:main@WSJTX.groups.io] On Behalf Of Jim Pruitt
Sent: 4. helmikuuta 2021 2:55 To: main@WSJTX.groups.io Subject: Re: [WSJTX] #Install #BugReport #WSJTX_config WSJT-X not working after 2.3.0 install
That (plug in USB dongle or the onboard sound card) does not even show up! The ONLY inputs and outputs listed is my Microsoft USB boom headphone/mic. No other options appear now. And I was not using the computer sound card I was using a plug in usb dongle! I am using a plug in usb dongle soundcard and it was working but no longer an option so exactly what do I do since no sound card now shows up to pick from? On 2/3/2021 3:07 PM, Bill Somerville wrote:
|
|
|
|
here is his adif file in my wsjt log
<call:4>K4YT <gridsquare:4>FM19 <mode:3>FT8 <rst_sent:3>-10 <rst_rcvd:3>-16 <qso_date:8>20200906 <time_on:6>085345 <qso_date_off:8>20200906 <time_off:6>085615 <band:3>80m <freq:8>3.573911 <station_callsign:5>N7UVH <my_gridsquare:6>DN17NR <comment:25>FT8 Sent: -10 Rcvd: -16 <eor>
<call:6>VK2AMA <gridsquare:4>QF54 <mode:3>FT8 <rst_sent:3>-11 <rst_rcvd:3>-10 <qso_date:8>20200906 <time_on:6>122615 <qso_date_off:8>20200906 <time_off:6>122715 <band:3>80m <freq:8>3.573911 <station_callsign:5>N7UVH <my_gridsquare:6>DN17NR <comment:25>FT8 Sent: -11 Rcvd: -10 <eor>
|
|
|
