Re: [wsjt-devel] 160m S/N needs advanced mode
Keep in mind that 160 is dead right now due to the sun cycle. 160 is always dead during the day. Larry / W1DYJ On 12/7/2023 10:46, Glenn Williams via wsjt-devel wrote: Hello, FT8 on 160m pales. WSJT-X operators customarily running FT8 and FT4 on 80m through 10m HF bands are likely disappointed with trials on 160m. As one of those operators I recently ran WSPR on 160m in comparison to working FT8 QSOs on 160m. In NA EST daytime operation at 2220Z WSPR faultlessly listed a -28 dBm decode. Here I suggest we need an improved decode sensitivity for 160m QSOs, likely needing to be done with a new mode. Granted, the TX and RX times would have to be increased (Shannon-Hartley Theorem). That would require additional operator patience and associated protocols for the extended timing. --73, Glenn, AF8C ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] Enhancement suggestion - 30 second cycles
Hi Glen, I have my TX watchdog set to 3 minutes. I just let it time out to check my frequency. Larry / W1DYJ On 4/27/2023 12:00, Glenn Williams via wsjt-devel wrote: Good Day, FT8/4 enhancement suggestion follows. (I know that stable code can be broken by side effects and "better is the enemy of good enough".) For example, with FT8, instead of having two 15 second transmission cycles per minute, it would be nice to have the option of ONE 15 second cycle per minute. Leave the other usual 15 second transmission period in receive as a way to monitor whether I am transmitting in a clear slot. This mode would be selectable with a radio button for "30" or "15". Or call it "Monitor on". Once a QSO is locked in, revert automatically to two 15 second transmissions per minute in order to finish the QSO at the normal rate before the propagation changes. I find that when the band is highly active, after a couple of my transmissions someone has moved into my slot. For DX that means my attempts to establish interest in my call sign can be smothered by another station and I have to stop, wait 30 seconds to see if my slot is clear, and restart or move first, all done manually. --73, Glenn, AF8C ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] fail to download
It's a false positive. Turn off you spam-blocker temporarily or better, add it to your allowed list. 73 -- Larry -- W1DYJ On 11/14/2022 14:29, hansenc--- via wsjt-devel wrote: I tried to download wsjtx-2.1.0-win64.exe and I got a message that it can't be downloaded securely. How do I download the program so I can run FT8 and other digital programs? Chris ___ 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] Feature request: Contest name
Hi Saku, It is much easier to use a proper contest logging program. There are many out there. I use the programs from N3FJP -- they are easy to set up and use. They do everything you need. Larry / W1DYJ On 10/14/2022 4:29, Saku via wsjt-devel wrote: Hi! Sorry if this feature exist. I did not find a mention about it from user guide. There are now several contests that use WSJT-X contest modes. It would be nice to have user defined contest name to logging window. That way name logged (also via UDP message) could be set by contest. And maybe also add a date to name if several contests are kept in same external log making them easier to find by the name of contest. Just worked contest "NAC-6m_10/2022" that uses EU VHF mode. So my external log has now contest name "NAC-6m_10/2022" with all CW and SSB qsos, but "EU VHF" with FT8 qsos that have to be changed manually afterwards. Good place for contest name would be either: Make "operator" column smaller and set "contest name" after that on right side. or Below "propagation mode". In both cases "retain" checbox is needed too. Thanks! ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] WSJT-X close the QSO unilaterally (?)
If they don't get your RR73, then they will send back their R-#. IF you get nothing back they got your R73 and are playing by the rules. Larry / W1DYJ On 7/15/2022 1:29, Adrian via wsjt-devel wrote: When you send a RR73 and get nothing back, then wsjtx has logged the call, but you don't know if your RR73 was received, or if the other party logged you. Making the log work only on 73 sent or received instead of RR73, confirms the sig report both ways and the qso both ways. if the program worked this way the everyone would send the 73 to get in and be logged. Why is using 73 to trigger a log entry sent/received a problem ? Send RR73 and program logs on received 73. Receive RR73 and program logs on sent 73. vk4tux On 15/7/22 15:12, Reino Talarmo via wsjt-devel wrote: >Hopefully, in an ideal world, it should be that WSJT-X waits for a second RR73 (hypothetical answer confirmation sequence I mean) from the remote station, before to definitely close and log the QSO. Hi Marco, I am not sure what you mean by the “second RR73”. There seems to be a generic misunderstanding how the protocol is assumed to work. User Guide sections 7.1. and 7.4. provide a nice advice. For a minimum QSO, where locator information is exchanged: CQ K1ABC FN42 #K1ABC calls CQ K1ABC G0XYZ IO91 #G0XYZ answers G0XYZ K1ABC –19 #K1ABC sends report K1ABC G0XYZ R-22 #G0XYZ sends R+report G0XYZ K1ABC RR73 #K1ABC sends RR73 K1ABC G0XYZ 73 #G0XYZ sends 73 The last message (73) is optional. Relevant issue is that in none of the examples a station that receives RR73 is sending back RR73, but 73 or nothing more for that call. 73, Reino OH3mA ___ 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 ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] (no subject)
They came back to me with a signal report three times, but then someone else in FN42 jumped on top of my frequency with more power and the Q never could complete. This may be what is happening to you. Lots of hams calling, and not necessarily looking for an open frequency. 73 -- Larry -- W1DYJ From: Bill Sent: Saturday, March 02, 2019 9:07 To: WSJT software development Subject: [wsjt-devel] (no subject) Is anyone else have issues working T31EU on FT8? He responses back to me when I call with very good signal reports but the QSO never finishes (All I get is my signal report and not an acknowledgment). This happens on multiple tries. I've tried both normal FT8 mode and also Fox Hound but no luck Sometimes it appears that he is sending Fox Hound responses (multiple calls on one line) and at other times it seems like standard FT8 contacts. He is transmitting on at least two frequencies so it seems like it should be Fox Hound. Any ideas what he is doing? I have been able to make valid QSOs with him using normal FT8 mode on a few bands but more often than not it gets stuck with my signal report and that's all. Is he using a WSJT-X variant of some sort or maybe equipment issues? Thanks! Bill - AK6A ___ 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] PJ4P Operation
I just worked then with one call -- they have multiple signals a bit apart from each other, but working them is not difficult. Just use normal FT8 protocols. 73 -- Larry -- W1DYJ [in Maine] -Original Message- From: Gary McDuffie Sent: Wednesday, January 23, 2019 18:25 To: WSJT software development Subject: Re: [wsjt-devel] PJ4P Operation On Jan 23, 2019, at 13:34, John Zantek wrote: Has anyone observed the FT8 operation of the PJ4P expedition team? Maybe I’m missing something obvious, but…. It LOOKS they’re operating as a Fox, but on the conventional FT8 frequencies. Saw the same thing this afternoon. I think it was on 17m. Their transmissions are varying between < 500Hz and > 1000Hz. In my case, they were ~200-300 I know this isn’t a Developer issue, but I trust the folks on his list. I’m after PJ4 on 160M, but wasted an entire evening last night trying to figure out how to work them. I wouldn’t waste my time trying to work them, since they aren’t “playing by the rules”, i.e. using the software the way it was intended, on the frequencies it was intended for. Working them just reinforces the fact that they can do it and people will still QSO them, so why change. Gary - AG0N ___ 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] Possible bug in V2 GA ?
Hi Chris, Even if you double-clicked, he/she would have to chose which ham to go back to of the many calling on frequency. I see this many times, especially with DX. I do find it *usually* more successful to call the DX split. 73 -- Larry -- W1DYJ From: Hasan al-Basri Sent: Monday, December 31, 2018 17:22 To: WSJT software development Subject: Re: [wsjt-devel] Possible bug in V2 GA ? If you didn't double click to get on his frq, you really weren't on his freq. Single click moves rx, double click moves both. What I think happened was you single clicked (and stayed on your prior tx freq), so, when he answered someone else, you continued to call him (but off his rx freq), which is "good". He might see you for the next qso, hence my queue comment. Hasan On Mon, Dec 31, 2018 at 4:11 PM Chris Getman wrote: Thanks for the information. I thought I was exactly on his frequency, I had just clicked on him calling CQ, And sent his call then mine. But he responded to someone else. So if this is to allow others to queue up, then what am I transmitting? And why would I want stations to queue up on his frequency? Sorry for rambling on, but I am just confused on this one Is this somewhere I can read up on, to better understand? Thanks Chris. - N3PLM On Mon, Dec 31, 2018 at 4:41 PM Hasan al-Basri wrote: Chris, If you are not calling right on or close to the station's frequency, the tx will not go out, it will continue. This is a feature, not a bug. It allows the "rare" station to queue up some callers while continuing to work an existing station that may or may not be on his tx freq. 73, N0AN Hasan On Mon, Dec 31, 2018 at 11:09 AM Chris Getman wrote: When responding to someone calling CQ But the calling station reply’s to someone else, The enable TX button goes out, and the transmit is supposed to stop But once in a while, the transmitter keep transmitting each cycle, Nothing shows up on the right hand screen . The only way to stop the repeating transmit, you have to manually re-enable the Enable TX button and the hit the Halt TX button. Hitting the Halt TX button alone does nothing. Windows 10 – Dell 6400 – Signalink SL1+ - FT-847 Doesn’t happen often and it isn’t a big problem Once you know what it is. Just Wondering if anyone else encountered this issue. Chris – N3PLM ___ 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 -- Chris Getman 413 Militia Drive Lansdale, PA 19446 215-368-1005 – Home 215-353-6429 – Cell chris.getman...@gmail.com ___ 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 ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] File not found SSL/TLS WSJT-X 2.0 release.
Hi Bill, Be sure to download the EXACT version number. I first downloaded a later version and it did not work. 73 -- Larry -- W1DYJ From: Bill Somerville Sent: Sunday, December 16, 2018 19:12 To: wsjt-devel@lists.sourceforge.net Subject: Re: [wsjt-devel] File not found SSL/TLS WSJT-X 2.0 release. On 16/12/2018 23:56, RICK SCOTT wrote: Seen several messages on the list on this and how to fix it. Well I run windows 10 and have downloaded the recommended file a couple times and installed it and I still get the message ever time I run 2.0. Rick, the answer is here: https://physics.princeton.edu/pulsar/k1jt/wsjtx-doc/wsjtx-main-2.0.0.html#INSTALL_WIN 73 Bill G4WJS. ___ 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] WSJT-X 2.0 RC5 -- difference from 1.9.1
Hi Bill, I was going to say the /ME was not illegal, especially with the space: W1DYJ /ME. In fact, as mentioned I have been using this for a year now from my Maine QTH and it has been helpful, as FN43 is not specific to Maine. 1.9.1 did not filter any free form messages as far as I could tell, and I have logged many new states and countries when using it. "CQ ME W1DYJ" obviously is worse. (Some hams did think this is what I meant.) Your suggestion for Tx5 is a good one. Larry / W1DYJ -Original Message- From: Bill Somerville Sent: Monday, December 03, 2018 17:42 To: wsjt-devel@lists.sourceforge.net Subject: Re: [wsjt-devel] WSJT-X 2.0 RC5 -- difference from 1.9.1 On 03/12/2018 22:24, Jim Shorney wrote: Not to mention that /ME would suggest that the op is in England, and would be a rules violation if he is not. 73 -Jim NU0C Hi Jim and Larry, point taken, but ME is not a valid UK prefix. We have 2E, MM etc. but the England M prefix is just plain 'M' followed by a digit. As far as WSJT-X is concerned, and I think Joe's point, is that if we allow 'CQ W1DYJ /ME' as a free text message (note the space before the '/') then it almost certainly will not be helpful as receivers of the message cannot double-click it to reply. OTOH 'CQ W1DYJ/ME' is a standard message but anyone double clicking it will end up logging the wrong callsign and you are probably misrepresenting your location as Jim states above. I wasn't aware that WSJT-X filtered any valid free text messages but in this case it seems to be the best thing to do. Larry I suggest you save a macro like '73 FROM MAINE' and use it as a Tx5 message now and again, I expect that would be much more productive as it will not trip up stations receiving it. 73 Bill G4WJS. ___ 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
[wsjt-devel] WSJT-X 2.0 RC5 -- difference from 1.9.1
Hi, I have just switched to 2.0 RC5. I use it mainly for HF/FT8. With FT8 and when at my 2nd home in Maine, I usually change my TX6 -- the autoloaded CQ W1DYJ FN43 -- to CQ W1DYJ /ME as Maine is far more important info than just FN43 (v1.9.1). NOW, it won’t take the /ME (v2.0 RC5). When I try, it just sends CQ W1DYJ. I did not find anything in the Quick Guide, etc., that helped me make this work as it used to. (I also tried CQ W1DYJ ME.) Have you deleted the “free form” 13-character CQ? Is this no longer allowed? 73 -- Larry -- W1DYJ ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
