Re: [wsjt-devel] Hamlib error

A minor addition for Windows users. The COM port should be ‘Enhanced’ one for CAT control, see Device Manager – Ports (COM & LPT). 73, Reino OH3mA From: Jeff Stillinger via wsjt-devel [mailto:wsjt-devel@lists.sourceforge.net] Sent: Monday, April 29, 2024 8:17 PM To:

Re: [wsjt-devel] Another fun hash collision P97USI

Jon, It would be interesting to know whether you have decoded a message containing P97USI/P within 231900 and 232530 and what that message was? 73, Reino OH3mA From: Jon Anhold via wsjt-devel [mailto:wsjt-devel@lists.sourceforge.net] Sent: Tuesday, February 27, 2024 2:50 AM To: WSJT

Re: [wsjt-devel] Misleading QTH info on JTAlert

Hi, Just a clarification question. Do you update QRZ.com Grid Square information each time you move between those two operation locations? The question as such may be more appropriate on the HamsApps forum https://hamapps.groups.io/ 73, Reino OH3mA > -Original Message- > From: Luis

Re: [wsjt-devel] Not sure if an issue

[Edited message as I forgot to remove unnecessary part of the mail chain, sorry for that] Hi all, I have run WSJT-X latest versions now 2 year more or less 24/7 using Windows 10 and one or two times a Windows update has re-arranged my audio interfaces resulting that kind of situation. The

Re: [wsjt-devel] Not sure if an issue

Hi all, I have run WSJT-X latest versions now 2 year more or less 24/7 using Windows 10 and one or two times a Windows update has re-arranged my audio interfaces resulting that kind of situation. The program alone has not done it as far as I can tell. I have of course disabled all power saving

Re: [wsjt-devel] Response to CQ ignored

Hi Lance, See https://groups.io/g/ProgramsByW2JDB It's the first one QLog. Look Files for download. 73, Reino OH3mA > -Original Message- > From: Lance Collister via wsjt-devel [mailto:wsjt- > de...@lists.sourceforge.net] > Sent: Friday, February 2, 2024 10:47 PM > To: Sam W2JDB via

Re: [wsjt-devel] Response to CQ ignored

Sam, the mail service had hick-up for some reason. My mails were delayed hours. 73, Reino OH3mA From: Sam W2JDB via wsjt-devel [mailto:wsjt-devel@lists.sourceforge.net] Sent: Tuesday, January 30, 2024 2:46 PM To: WSJT software development Cc: Sam W2JDB Subject: Re: [wsjt-devel] Response

Re: [wsjt-devel] Decoding Anomaly

Hi Dennis, There may be something to improve in the hash table(s) management as in your example the first message CQ PJ5/SP9FIH was sent in full (it is a non-standard call, but that should not matter). Why the 10 bits hash was not updated into the hash table, but there is DP1POL instead for

Re: [wsjt-devel] wsjt-devel Digest, Vol 119, Issue 45

o, > Do you mean that a priori information is used to help > decode? That's a bias. Shouldn't decodes stand on their > own? > -73, Glenn, AF8C > > On 1/26/2024 12:32 PM, Reino Talarmo via wsjt-devel > wrote: > > Hi Glenn, congrats about a nice false decode. The 'a3' > > te

Re: [wsjt-devel] wsjt-devel Digest, Vol 119, Issue 45

Hi Glenn, congrats about a nice false decode. The 'a3' tells that the decoder tried as the known information your call, DX call, and rest is decoded. The '?' indicates that the probability of correct message is not too high. Also the contents of the decoded part is suspicious as the report is

Re: [wsjt-devel] Making F/H idiot proof

Hi, I think that the Fox simply ignores the “R+rpt” part of the message and takes it to be a Tx1 message. So Fox sends a report. The Hound station autoseq may not work correctly as it has not sent the Tx1 at all. A resending of the “R+rpt” should be a correct message. The Hound station sends

Re: [wsjt-devel] Show States for Grids in the Band Activity window

AM, Reino Talarmo via wsjt-devel mailto:wsjt-devel@lists.sourceforge.net> > wrote: Hi Ed, That message was appended to the display by some companion program as it is impossible to convey the additional information using the FT8 CQ message and the grid alone tells the state only by

Re: [wsjt-devel] Show States for Grids in the Band Activity window

Hi Ed, That message was appended to the display by some companion program as it is impossible to convey the additional information using the FT8 CQ message and the grid alone tells the state only by change. 73, Reino OH3mA From: Ed Stokes via wsjt-devel

Re: [wsjt-devel] WSJT noise estimates

Hi Andy, Interesting approach. But how you know that it really enhanced the signal detection? The wanted signal is now close the wanted signal and that may disturb the S/N calculation and you will see a better S/N values with your method without a real better sensitivity. Possibly the only

Re: [wsjt-devel] WSJT noise estimates

Hi Joe, Some quick comments in-line. 73, Reino OH3mA > Sent: Sunday, December 10, 2023 4:56 AM > Subject: [wsjt-devel] WSJT noise estimates > Been wondering how WSJT-X generates the noise power estimate it uses to calculate SNR for each FT8 signal.  Does it simply collect all the signals and

Re: [wsjt-devel] 160m S/N needs advanced mode

Hello Glenn, I think that you wish is already heard and fulfilled. The suitable mode is FST4. There are seven modes with transmission periods from 15 to 1800 seconds. The performance of the FST4-120 is about the same as for WSPR. For longer transmission periods transmitter frequency stability

Re: [wsjt-devel] WSJT-X parsing of the country file, specifically 4U1A (and others)

> From: Jim Reisert AD1C via wsjt-devel > [mailto:wsjt-devel@lists.sourceforge.net] > Sent: Thursday, December 7, 2023 3:51 AM > 3. 4U is listed as a prefix for Italy. Regarding #3, this was done so that "new" (previously unknown) 4U callsigns that are spotted on the DX cluster will propagate

Re: [wsjt-devel] WSPR and Diversity Receive

Hi Ben, You mentioned that you have two antennas. What kind antennas you have? Do they have any radiation patterns different from each other? What’s distance between the antennas? In any case you can affect to the noise level by combining two antennas that are at different locations. That beam

Re: [wsjt-devel] IC-705 little to no decodes

Could there be some audio enhancements that should be switched off, either windows or in rig such as noise blanker or some automatic interference reduction? Does your computer have two time services activated, perhaps not in the both computers? On those few decodes, what are the dT values?

Re: [wsjt-devel] Source code location for hashcodes.f90?

Hi David, Was it at www.arrl.org/qexfiles year 2020 July/August, The FT4 and FT8 Communication Protocols http://www.arrl.org/files/file/QEX%20Binaries/2020/ft4_f t8_protocols.tgz 73, Reino OH3mA PS. I like to see that Python utility. Reino

Re: [wsjt-devel] Astronomical window not working

In that situation it normally hides behind the main window. Try to move the main one. 73, Reino OH3mA From: G Richard Kreuter via wsjt-devel [mailto:wsjt-devel@lists.sourceforge.net] Sent: Monday, November 27, 2023 12:01 AM To: wsjt-devel@lists.sourceforge.net Cc: G Richard Kreuter

Re: [wsjt-devel] CQ Hound mode

double clicks on that message? 73, Reino OH3mA From: Sam W2JDB via wsjt-devel [mailto:wsjt-devel@lists.sourceforge.net] Sent: Sunday, November 5, 2023 11:53 PM To: Reino Talarmo via wsjt-devel Cc: Sam W2JDB Subject: Re: [wsjt-devel] CQ Hound mode and what's to stop mshv from adapting

Re: [wsjt-devel] CQ Hound mode

Just a minor point, I assume. If that is programmed into wsjt-x, then the change will not be backwards compatible. The CQ part of the message is actually a specific pretty long bit string (28 bits, ‘c28’). There could be another bit string for the CQF, but none of the current versions would

Re: [wsjt-devel] WSJT-X 2.7.0 rc2 flagged as malware

It is only a false positive malware indication. 73, Reino OH3mA > -Original Message- > From: F4FPR Benjamin via wsjt-devel [mailto:wsjt- > de...@lists.sourceforge.net] > Sent: Friday, October 27, 2023 11:36 PM > To: wsjt-devel@lists.sourceforge.net > Cc: F4FPR Benjamin > Subject:

Re: [wsjt-devel] No 73 allowed after RR73?

RR73? Last two months I have had about 5000 FT8/FT4 QSOs. I have received just one RRR, all the others were RR73. So RRR is not in use very much… 73 Keijo OG5O Lähetetty Windowsin Sähköposti <https://go.microsoft.com/fwlink/?LinkId=550986> ista Lähettäjä: Reino Talarmo via wsjt

Re: [wsjt-devel] No 73 allowed after RR73?

Hi Andy and all, The protocol is flexible on that issue. The original weak signal QSO do contain a “RRR” that is “confirmed” by a “73” to keep both sizes of the QSO happy. The “RR73” is really intended for “strong signal” QSO’s and then the “73” is not needed to keep the QSO time short.

Re: [wsjt-devel] Solar Eclipse participation #general

Yes, e.g. Radio observations of the 2015 solar eclipse (pa3fwm.nl) 73, Reino OH3mA From: Marco Calistri via wsjt-devel

Re: [wsjt-devel] Split

Hi Jim and all, I support this proposal. I know that on the rig's point of view the functionality is the same as in the classical "split". What is seen on the band may or may not be the same depending how the user selects the transmission frequency. In addition some words could be added to note

Re: [wsjt-devel] Problem with Hamlib

Hi Uwe, I have used the same serial port for CAT (no PTT) and DTR or RTS for PTT with my FT1000MP, but of course you can’t have at the same time a hardware flow control. 73 Reino OH3mA I use CAT. If you have DTR or RTS selected, make sure the COM port for that is different from the CAT

Re: [wsjt-devel] #Echo Echo shifts TX frequency when clicking "Set RX & TX offset" - should be disabled

Hi Andreas, It would be nice for you, if the echo mode had a ‘fail safe’ setting that forces the transmission to 1500 Hz. The source code is available and you may add that into the program. Otherwise the instructions are clear how to use the echo mode. 73, Reino OH3mA From: Andreas Junge

Re: [wsjt-devel] High CPU load with 2.7.0-rc2

Hi, Should we have in the rc version a button for a new hamlib file download like we have one for the cty.dat? May not be that simple to implement. 73, Reino OH3mA > -Original Message- > From: Black Michael via wsjt-devel [mailto:wsjt- > de...@lists.sourceforge.net] > Sent: tiistai 11.

Re: [wsjt-devel] list

Hi Ray, Best is to do it yourself. Go to https://lists.sourceforge.net/lists/listinfo/wsjt-devel (link should also be at the bottom of this mail) and in 'Unsubscribe & Settings' select 'Click here to unsubscribe or change settings' and follow the instructions, please. 73, Reino OH3mA >

Re: [wsjt-devel] I was dropped off list

599 in Finland. Did you got my private mails on the sakari.nylund(at)nic.fi? 73, Reino OH3mA > -Original Message- > From: Sakari Nylund via wsjt-devel [mailto:wsjt-devel@lists.sourceforge.net] > Sent: perjantai 7. heinäkuuta 2023 6.45 > To: wsjt-devel@lists.sourceforge.net > Cc: Sakari

Re: [wsjt-devel] New subscriber :)

Hej Palle, I identified two main issues in your mail, (1) naming of contest modes and how contests are supported and (2) a new way how protocol should support user needs. Contests naming and supporting protocols (1) Perhaps it is better to start what is supported in the current autosequence

Re: [wsjt-devel] Log file for changes in settings?

Glenn, All settings are stored into wsjt-x.ini file. You may take a copy of it for comparison before making 'radical' changes into your settings. As it is intended to be read by the program, it is not easy to interpret by humans, but in most cased useful. 73, Reino OH3mA > -Original

Re: [wsjt-devel] ARRL Digi contest log converting to Cabrillo

http://www.b4h.net/cabforms/arrldigi_cab3.php may work for you. I have not checked whether the wsjtx.log or wsjtx_log.adi or both could be used, manual at least. 73, Reino OH3mA From: Hannu Eloranta via wsjt-devel

Re: [wsjt-devel] Hamlib Beta Testing Group needed

> From: Tom M0LTE via wsjt-devel [mailto:wsjt-devel@lists.sourceforge.net] > Sent: lauantai 13. toukokuuta 2023 10.58 >While manual testing could probably never be eliminated in the case of hamlib, >has there been any consideration of creating test harnesses to remove/reduce >the need for

Re: [wsjt-devel] WSJTX Cabrillo log time

Hi Saku Some comments in-line. A bit long email, sri. It's time for the new candidate release discussion. 73, Reino OH3mA > From: Saku via wsjt-devel [mailto:wsjt-devel@lists.sourceforge.net] > Sent: perjantai 12. toukokuuta 2023 21.22 > if you calling CQ (TX1) and someone(s) answer to it

Re: [wsjt-devel] WSJTX Cabrillo log time

57 427 > > -Original Message- > From: Reino Talarmo via wsjt-devel > Sent: Thursday, May 11, 2023 5:08 PM > To: 'WSJT software development' > Cc: Reino Talarmo > Subject: Re: [wsjt-devel] WSJTX Cabrillo log time > > Hi Saku and Alan, > > I think that Ala

Re: [wsjt-devel] WSJTX Cabrillo log time

Hi Saku and Alan, I think that Alan already pointed a least indirectly that the definition of the actual start time is a bit more difficult than a defining end time. Also end time may be difficult, if participants have different opinion e.g. whether a final 73 is needed or not. I have not

Re: [wsjt-devel] FT8 TX6 mod entry and security hole

> However attempting to use "CQ 3C AF8C EN81" created a couple of problems. Hi Glenn, You are simply trying something that is not supported in WSJT-X. The only supported additions to the CQ message are: CQ 000 - CQ 999 3 to 1002 CQ A - CQ Z 1004 to 1029 CQ AA - CQ ZZ 1031 to 1731 CQ AAA - CQ ZZZ

Re: [wsjt-devel] Fwd: Enhancement suggestion - 30 second cycles

as they >were >shifted up on TX? Hi Alan, You question is answered in the User Guide 4.1. General, see the last bullet point 'Split Operation'. If you have any further questions on that issue you may send me a private mail (clicking CC: Reino Talarmo should reveal my email addre

Re: [wsjt-devel] Fwd: Enhancement suggestion - 30 second cycles

> From: Black Michael via wsjt-devel [mailto:wsjt-devel@lists.sourceforge.net] > Much the same as a rig from 50 years ago looks nothing like today -- > including the fact that old rigs had no "split" capability at all and you had > to use a 2nd transceiver to accomplish the same thing. > Then

Re: [wsjt-devel] Fwd: Enhancement suggestion - 30 second cycles

> From: Black Michael via wsjt-devel [mailto:wsjt-devel@lists.sourceforge.net] > Sent: sunnuntai 7. toukokuuta 2023 19.35 > That's why I put 3 definitions of split in there. It means different things > in > different contexts Hi Mike and Sam, I have had a lot of private discussion with

Re: [wsjt-devel] Fwd: Enhancement suggestion - 30 second cycles

Hi Adrian, This start to be really funny! Let me take a real scenario that I participated. If I remember correctly it was a FT8 contest and there were a rare station, at least to me, K1JT. So everybody called him, including me, quite a pile-up on his transmit frequency. Joe tried to manage

Re: [wsjt-devel] Fwd: Enhancement suggestion - 30 second cycles

Hi Sam, Adrian and the Experts, Before I can answer some of the questions, I need to repeat my understanding how SPLIT should be defined. I use two different ‘splits’ that can be used at the same time or independently. #Class: the classical split simply means you are using a different radiated

Re: [wsjt-devel] Fwd: Enhancement suggestion - 30 second cycles

Jim, Mike and all experts, May I repeat a bit history of 'split' in the WSJT-X as I have learned it. 1# The split operation or split mode is mentioned on the radio settings. It defines how WSJT-X controls radio and that's the only usage of the split word in the User Manual. 2# Limiting the usage

Re: [wsjt-devel] Fwd: Enhancement suggestion - 30 second cycles

Hi Adrian, Sam and all interested parties, I also disagree, but that's not fair as we have not defined terminology for this discussion! Warning: this takes a bit bandwidth, sri. Behind there may be two issues. The first is what is meant by the transmission frequency in FT8? The second is of

Re: [wsjt-devel] Fwd: Enhancement suggestion - 30 second cycles

Sam, as you very well know the User Guide talks about CAT ‘Split Operation’ or ‘Split Mode’. It is the manner how WSJT-X controls your rig. Unfortunately a short version ‘Split’ is used in discussions both in that manner and in the classical manner what is described in the User Guide in 6.8.

Re: [wsjt-devel] Fwd: Enhancement suggestion - 30 second cycles

Hi Sam, Saku was talking about ‘RF split’. The WSJKT-X Split Operation is only a method to keep your signal at optimum range at audio level. On the other hand I don’t support of the idea that WSJT-X would randomly select my transmission frequency. I don’t like that the tx frequency jumps on a

Re: [wsjt-devel] Unsubscribe

Hi Dave, Go to https://sourceforge.net/projects/wsjt/lists/wsjt-devel/unsubscribe and follow instructions, please. 73, Reino OH3mA From: dave--- via wsjt-devel [mailto:wsjt-devel@lists.sourceforge.net] Sent: tiistai 25. huhtikuuta 2023 16.58 To: wsjt-devel@lists.sourceforge.net Cc:

Re: [wsjt-devel] Truncated Waterfall Display "Feature"

Michael via wsjt-devel [mailto:wsjt-devel@lists.sourceforge.net] Sent: maanantai 10. huhtikuuta 2023 17.00 To: Reino Talarmo via wsjt-devel Cc: Black Michael Subject: Re: [wsjt-devel] Truncated Waterfall Display "Feature" -24 is not the minimum SNR reported. -30 is. Below -24 is p

Re: [wsjt-devel] Truncated Waterfall Display "Feature"

@lists.sourceforge.net] Sent: maanantai 10. huhtikuuta 2023 17.00 To: Reino Talarmo via wsjt-devel Cc: Black Michael Subject: Re: [wsjt-devel] Truncated Waterfall Display "Feature" -24 is not the minimum SNR reported. -30 is. Below -24 is pretty rare though and is a big "knee"

Re: [wsjt-devel] Truncated Waterfall Display "Feature"

ffected the variance and standard deviation values. 73, Sam W2JDB -Original Message- From: Reino Talarmo via wsjt-devel To: 'WSJT software development' Cc: Reino Talarmo Sent: Mon, Apr 10, 2023 3:33 am Subject: Re: [wsjt-devel] Truncated Waterfall Display "Feature" Hi, Just as p

Re: [wsjt-devel] Truncated Waterfall Display "Feature"

. That easily results to misinterpretation that a narrow RX bandwidth will enhance decoding probability, it is just the actual "wrong" noise bandwidth in the S/N calculation! 73, Reino OH3mA >From: Reino Talarmo [mailto:reino.tala...@kolumbus.fi] Sent: lauantai 8. huhtikuuta 2023 1

Re: [wsjt-devel] F/H mode in wrong period

And they are using the ”wrong” period on purpose an politely so that you see immediately that the normal FT8 should be used by “hounds”. 73, Reino OH3mA From: Alan McDonald via wsjt-devel [mailto:wsjt-devel@lists.sourceforge.net] Sent: sunnuntai 9. huhtikuuta 2023 15.05 To: WSJT software

Re: [wsjt-devel] Truncated Waterfall Display "Feature"

Hi All, You may discuss different issues! In FT8 mode Sam is correct as the signals are reached only on the frequencies displayed on the waterfall. In JT65 and Q65 the situation is different at there is a spinner called F Tol that defines the search range independent of the waterfall range.

Re: [wsjt-devel] Truncated Waterfall Display "Feature"

Hi Russ, You seems to hit the nail. I did not checked modes JT65 and Q65 and those use a frequency tolerance in User Guide 10.4. Center: *For modes lacking a multi-decode feature, or when Enable VHF/UHF/Microwave features has been checked on the File → Settings → General tab, the F

Re: [wsjt-devel] Truncated Waterfall Display "Feature"

Perhaps also reading User Guide 6.2. Wide Graph Settings should help: 'It is important to set appropriate lower and upper audio frequency limits for the Wide Graph because these limits define the FT8 decoder’s search window.' 73, Reino OH3mA > -Original Message- > From: Dwayne Sinclair

Re: [wsjt-devel] Enhancement Recommendation

Hi All, What Dave is proposing needs only WSJT-X no other logging program. BUT to make it work he needs to start WSJT-X from zero as the new grid information is based on the used wsjtx_log.adi file. It mean he needs to rename the wsjtx_log.adi file to something else e.g.

Re: [wsjt-devel] Minor nit in sourceforge main WSJT-X page

> From: Glenn Williams via wsjt-devel [mailto:wsjt-devel@lists.sourceforge.net] > > To quote: > > "Versions of WSJT-X labeled with a "-rcx" suffix, for example WSJT-X v2.2.0-rc6, > are Release..." > > While v2.2.0 is an example, you could update that to > > "Versions of WSJT-X labeled with a

Re: [wsjt-devel] Custom frequencies lost after upgrade from 2.5.4 to 2.6.1

>From: false via wsjt-devel [mailto:wsjt-devel@lists.sourceforge.net] >Before the upgrade, I renamed the old version (2.5.4) and when I open it, the >custom frequencies are present. Is there any way to add them to 2.6.1 other >than manually? Hi Bill, In version 2.5.4 go to Frequencies tab and

Re: [wsjt-devel] 3Y0J strange F/H operation

> “ We had issues with the FT8 due to we did not have any device to sync > against, and our clock was 14 seconds off - which meant we at some time were > TX odd, while we thought it was even.” >Well a simple GPS device connected to one of their notebooks would have >prevented the problem

Re: [wsjt-devel] Who was I working with???

> From: Saku via wsjt-devel [mailto:wsjt-devel@lists.sourceforge.net] > Sent: 13. helmikuutata 2023 14:57 > The callsign of AJ4YX varied as <...>, , and in > ALL.TXT and screen. Hi Saku, Actually in the ALL.txt file the progress was: - <...> any unknown hash, but most probably J8/AJ4YX, you

Re: [wsjt-devel] Hashed callsign collisions?

at 6:23 PM Jon Anhold mailto:j...@anhold.com> > wrote: I'm pretty sure, although I can't know for certain, that W1AW/0's WSJT-X auto seq answered me after his CQ when I was calling W1AW/7. On Fri, Jan 20, 2023 at 4:42 PM Reino Talarmo via wsjt-devel mailto:wsjt-devel@lists.sourcefor

Re: [wsjt-devel] Hashed callsign collisions?

Hi Jon, I don’t see any hash collision in those messages. You should ask what W1WW/0 did? Perhaps operator was waiting a “73” from your, but you sent one to W1WW/3 and W1WW/0 decided to send you a new report. I don’t know whether that station received your message at 205445 as you changed it

Re: [wsjt-devel] Request from WSPRNet Devs

Hi Gary, My information is limited to the Release notes and it seems that the “15” is used in the GA version 2.6.0. See https://wsjt.sourceforge.io/Release_Notes.txt 73, Reino OH3mA ___ wsjt-devel mailing list

Re: [wsjt-devel] Unable to find how to reset Q65A default Tx duration (defaults to 30 sec and my operating requires 60 seconds)

Hi Dave, Joe sent this mail on the [WSJTX] list 73, Reino OH3mA Joe’s mail: Sorry about the missing T/R period control in WSJT-X 2.6.0. This was completely unintentional; the problem had been recognized and corrected, but the corrected code was inadvertently not moved into the

Re: [wsjt-devel] Fwd: WSJT-X 2.6.0 GA Release

Hi Al, The new User Guide advices in 20.2. Bug Reports: One of your responsibilities as a WSJT-X user is to help the volunteer programmers to make the program better. Bugs may be reported to the WSJTX forum on Groups.io Post Message or the WSJT Developers list (wsjt-devel@lists.sourceforge.net).

Re: [wsjt-devel] {wsjt-devel] v2.6.0-rc5 User Guide website

>But this does not solve the problem in the cases of: >1) I'm not on that computer or even in the shack, or maybe I am in a meeting or someplace where suddenly I need to obtain the User Guide. I can get to the website but I can't get to the shack computer. >2) Similarly I am on my smartphone

Re: [wsjt-devel] v2.6.0-rc5 User Guide website

>Where are the user guides of any version like V2.5.x or above? Hi Glenn, If you have downloaded version 2.6.0-rc5, then C:\WSJT\wsjtx2.6.0_rc5\share\doc\wsjtx. Or ... \ wsjtx2.6.0_rc5\share\doc\wsjtx, if you have installed wsjt-x somewhere else. The User Guide is wsjtx-main-2.6.0-rc5.html. The

Re: [wsjt-devel] Power Slice Bar

Hi Marty, It a known "feature" of the Qt that provides code for MacOS and others. It will be corrected in the next general version. I assume that it is already corrected in 2.6.0-rc's. 73, Reino OH3mA -Original Message- From: Marty Wayne via wsjt-devel

Re: [wsjt-devel] v2.6.0-rc5 F/H Issue

he proper exchange, namely fox sending R-report, me sending R-report and then the fox sending RR73. --Dennis NE6I -----Original Message- From: Reino Talarmo via wsjt-devel Sent: Wednesday, December 7, 2022 9:26 PM To: 'WSJT software development' Cc: Reino Talarmo Subject: Re: [ws

Re: [wsjt-devel] v2.6.0-rc5 F/H Issue

>The third time this happened, the fox did respond to me with RR73 but I wonder >what happened there? It still didn’t move me below 1,000 so I moved myself >down. At that point, the fox moved me to where they wanted me (681). Hi Dennis, I don't know what actually happened, but the frequency

Re: [wsjt-devel] WSJT-X v2.6.0-rcr5 Hound frequency - k3wyc

>If Hound is then deselected the Fox/Hound frequencies remain in the frequency selector. Hi Andy, Have you read the related Release notes: When in Hound mode and click the "H" button again, the frequency is now kept. This gives the user the following two options to return to

Re: [wsjt-devel] 2.6.0-rc5 "Start new period at top" anomaly

Hi Rich, This is a long known problem and no solution in the program found. You may erase the band activity window at regular intervals and it continues fine or restore operation. You may erase both displays with the Erase button or click in the Band activity window and select Erase from

Re: [wsjt-devel] v2.6.0-rc4 observations

Dave That was not a real Fox at all. You should have used normal FT8 mode. Hound will never send RRR or RR73 to fox in the real F/H protocol. Somebody sending multiple carriers on a standard frequency really indicates that operator is not using Fox, but a derivate that can send multiple

Re: [wsjt-devel] RC4 crashes

>Maybe just co-incidence but I have had two crashes now where the last entry in >the ...ALL.TXT file was a station with compound call that was answering my CQ. 221123_18124521.074 Rx FT8-12 0.2 1386 KB1EFS/2 Hi AL, Could this be the same issue Mike stated: ‘Referring to "Max Dist"

Re: [wsjt-devel] fail to download

Hi Cris, By the way do you have a reason not to download version 2.5.4? The 2.1.0 is quite old version and you will miss some features. Or you may have an error in the file name. 73, Reino OH3mA From: Larry Banks via wsjt-devel [mailto:wsjt-devel@lists.sourceforge.net] Sent: 14.

Re: [wsjt-devel] Fox sends "DUPE" instead of "+rpt" in DX pedition mode

Hi Take san, It's not you English, but a protocol challenge. The reason for not receiving the RR73 from a fox depends on the S/N at the hound station and the detection probability of various messages. The S/N depends on the propagation, but also strongly on the number of carriers fox is using.

Re: [wsjt-devel] Request for additional new logging option

>LOTW now has the option of automatically recording your grid squares from your log as you travel across the country. This is great, but it doesn't provide information about what state or county the contact was made from. If WSJT-X had the option to also log your latitude and longitude in addition

Re: [wsjt-devel] WSJT-X 2.6.0-rc4: Sudden shut-down, "CQ: Max Dist" doesn't work, "CQ: None" stops working

>Frode, I don't know what it means. I read that text hastly, so, apologize. I stop allways there, where is something mentioned "contest". Not my thing... :) We wait now time, when manual is written.. Hi Jarmo, Frode, The draft User Guide for 2.6.0 states simply: "When calling CQ you may choose

Re: [wsjt-devel] Possible RC4 issue

>Sorry, I forgot to respond to this. I was only doing the mode change with the new mode buttons, not the mode drop down. Hi Gary and All, So this could be related somehow to the mode change using the new buttons as you may have not had the same issue using the menu selection. In any case it may

Re: [wsjt-devel] Possible RC4 issue

Hi Gary, >I was on 17M FT8, made a few contacts with no problem. After the last one >logged, I hit the FT4 button and jumped up the band as I frequently do when >things are busy. I worked one station on FT8 and logged it. After it logged, >the program simply closed itself - gone. This may

Re: [wsjt-devel] TX..RX with different radios

>The problem with all this is that completing a QSO does not count for >anything. You cannot log to LOTW, QRZ, eQSL since split TX/RX is not >permitted. It makes sense for SSB/Net Control/adhoc QSO’s with friends but not >for WSJT-X since many of us using WSJT-X are using it for awards. Hi

Re: [wsjt-devel] disable PSKreporter functions unless CAT control is active.

Hi, Just a reminder, why there are so many false band spots. From the current candidate release notes rc1: Correct a flaw that could send incorrect frequencies to ALL.TXT and PSK Reporter after a band change That happens each time you change the band during monitoring. The previous band

Re: [wsjt-devel] RC2 syslog file

Hi Mike, Bill (sk) was not concern about short drops at all. He considered those normal. I have had those all the time in my all WSJT-X installations since 1.9.1. Now I should have enough data to study whether the drops really affect to decoding performance e.g. the number of decodes in each

Re: [wsjt-devel] Hamlib Error

Hi Marty, Lets start from beginning. How is your CAT communication signaling built in your system? Do you have a USB to RS-232 converted cable or direct RS-232 to RS-232 cable between PC and your FT-1000MP? To me it seems a simple loss of that connection for some reason. Even just the bit

Re: [wsjt-devel] Hamlib Error

Marty, I have used a simple USB to RS-232 converter cable with my FT-1000MP for CAT control. You have already Signalink for audio audio/PTT. 73, Reino OH3mA -Original Message- Marty, In your list of equipment, I don't see a CAT interface. The Signalink is only a sound card interface.

Re: [wsjt-devel] WSJT-X 2.6.0 rc1 feed back

Luis, That functionality surfaces the general problem of an “instant” mode change. Does the operator want to continue/start a new QSO on the current frequency or jump to the default/pre-defined frequency for the mode. Additional problem for the F/H operation is how the Fox frequency is

Re: [wsjt-devel] 222 MHz and Up Distance Contest Rules. First full weekend in August.

That is supported in EU VHF contest. There is one difficulty with that as both operator need to use it before a call is really possible. 73, Reino OH3mA From: robert evans LAST_NAME via wsjt-devel [mailto:wsjt-devel@lists.sourceforge.net] Sent: 20. heinäkuutata 2022 18:56 To:

Re: [wsjt-devel] “Disable Tx after sending 73” not working

>For clarity: I am trying to set it to the UNCHECKED function. >Checked or unchecked, it is still the same: “Enable Tx” is OFF when a QSO is >complete. Hi Gene To my understanding this the normal behavior for FT8. If Tx Enable would stay active, then you would have a robot functionality

Re: [wsjt-devel] no call

It is not a mystery, but misuse of non-standard callsign! Somebody using a non-standard callsign such as OH31MA does not know that he needs to send for a QSO a message that contains the whole callsign. In this case it needs to be Tx1 i.e. ZP4KFX OH31MA There cannot be a locator as the

Re: [wsjt-devel] WSJT-X close the QSO unilaterally (?)

>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

Re: [wsjt-devel] RC1 UI bug

Hi Marco. It is just a title defined for a Configuration by AL. 73, Reino >What is that "FT8-D" mode? ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] SUGGESTION

>Then let's make it switchable.The majority of users will certainly find a Tune >watchdog useful and want to have it activated, but those who don't like it can >then simply switch it off. Good solution. Hi Uwe, How that new Tune watchdog will interact with the current Tx watchdog? 1.

Re: [wsjt-devel] SUGGESTION

I also belong to the continuous carrier lot. Already now there is the TX watch dog that can be set from 1 min to 99 min or disabled. I assume that the 1 min value could be good enough in most cases for those who don't want boil their rig.. The 1 min value seems to be maximum 1 min time depending

Re: [wsjt-devel] QSO 15 meters FT8 F/H not logged!

Hi Michael, Marco and all I know that this is not a wsjt-x development issue at all and should not be discussed on this list, but may I present my observations. I got the opportunity to work 3X2021 with my contest call ov9a. And as you can see at the picture I worked him in WSJTX Normal mode

Re: [wsjt-devel] 2.5.4 Closes

Message- From: Reino Talarmo via wsjt-devel mailto:wsjt-devel@lists.sourceforge.net> > To: 'WSJT software development' mailto:wsjt-devel@lists.sourceforge.net> > Cc: Reino Talarmo mailto:reino.tala...@kolumbus.fi> > Sent: Sun, Feb 6, 2022 12:54 am Subject: Re: [wsjt-devel] 2.

Re: [wsjt-devel] 2.5.4 Closes

Hi Ray, Did you got any error message? How the 2.5.3 stopped, most probably the actual reason is already there? Has wssjt-x written something more than warnings about dropped audio samples into a wsjtx_syslog.log file. It is in the log directory? You did not revealed at all which operating

  1   2   3   >