Re: [wsjt-devel] r2.2.2 Minor Issue with "short" calls that use DX

Hi Steve, 5CT is not a valid RA call sign as the third character is not a number, when the first character is a number or one of those country codes such as N, G etc. That’s why it is not source coded properly and recognized as a call sign and double clicking don’t work for you; message is a f

Re: [wsjt-devel] Hashed Call Sign

The < . . . > is somebody who don't know how special calls are supported and wanted to make a fast QSO with you and used Tx2! He did not seem to know that he need to respond with an un-hashed call sign that is available in Tx1. 73, Reino OH3mA -Original Message- From: Gary Rogers [mailto

Re: [wsjt-devel] FW: 2.2.2 Decoding Performance

> [ I'll resend this as its not flowed through (Which has resulted in some testing of late) ] Steve, The first one arrived sound and safe at 7.44 local time here in the northern hemisphere. 73, Reino OH3mA ___ wsjt-devel mailing list wsjt-devel@lists.s

Re: [wsjt-devel] FT8: Double Click, sometimes wrong CallSign

Hi Roland, You could try use General > Display Start new period decodes at top. At least I got help. 73, Reino OH3mA From: roland.hartm...@web.de [mailto:roland.hartm...@web.de] Sent: 29. kesäkuuta 2020 19:24 To: 'WSJT software development' Subject: [wsjt-devel] FT8: Double Click, sometimes

Re: [wsjt-devel] WSJT-X 2.2.0-rc2 False Decode

>From: Bill Somerville [mailto:g4...@classdesign.com] On 26/05/2020 10:33, Reino Talarmo wrote: > Just a single bit error in a proper place adds e.g. /R to the decoded message. >that is far from the actual position. A single bit error will never result in an incorrect decode, the amou

Re: [wsjt-devel] WSJT-X 2.2.0-rc2 False Decode

>I'm still on rc1 but have captured two .wav files of false decodes without any >"aX?" marking. >First on 6m and second on 4m. Both captured from very silent band, no many >other stations. Hi All, In Saku's example false decodes are due to noise. Decoder can detect even an empty band synchron

Re: [wsjt-devel] WSJT-X 2.2.0-rc2 False Decode

Hi Steve, Have you analyzed how many of the low level decodes, say below -18 dB, are false positives compared to all decodes? That figure will be a nice educational information. It requires some manual treatment of ALL.TXT file, but most of the work can be automated. 73, Reino OH3mA -Original

Re: [wsjt-devel] Clicking on RR73 produced wrong TX response msg

>> On May 20, 2020, at 10:28, Neil Zampella wrote: >> >> The 73 from you is a courtesy ... the RR73 is saying "Roger Roger - >> BYE'"basically ... we're good.This is why the program then >> switches to the Tx6 to send the next CQ call. >If you call letting him know that you got his ackn

Re: [wsjt-devel] Hold TX Frequency Default

>From: Jim Brown [mailto:k...@audiosystemsgroup.com] Sent: 19. toukokuuta 2020 20:25 >On 5/19/2020 6:35 AM, Joe Taylor wrote: >> I operate on 6m a lot, using FT8, MSK144, and recently also FT4. I > >never have the problem you describe. >Can you please tell me how your setup prevents the proble

Re: [wsjt-devel] Incorrect decodes

The third line is an EU VHF report message with target call, sender's call, both hashed and not know in your decoder, report with serial number and six digit locator. Well, it is a false positive in any case. 73, Reino OH3mA From: K2DBK-WSJT [mailto:k2dbk+w...@k2dbk.com] Sent: 18. toukokuuta

Re: [wsjt-devel] FT4 and FT8 Contesting

rds that just slow you down. Why is an increased level of assurance needed for this mode? Other than it is easy to do, at least in theory. John John On Fri, Feb 28, 2020 at 11:24 AM Claude Frantz mailto:claude.fra...@bayern-mail.de> > wrote: On 2/27/20 10:13 PM, Reino Talarmo wrot

Re: [wsjt-devel] FT4 and FT8 Contesting

Hi Paul I agree your comment on RRR or RR73 being confirmation of reception "R" ack. There is a minor difference though RR73 is "I am fully happy and don't expect any further response from you", while RRR is usually taken to mean "I received you confirmation, but I want to be sure that you receive

Re: [wsjt-devel] WSJT-X Improperly responding to a station not called in TX1

Hi Sam, You had Call 1st checked. I have understood that it is intended to give protocol permission/request to response to the first decoded message to you as long as you are not yet in a call. If HB9FAH has answered to you, then he will have been in your call and protocol would have continued

Re: [wsjt-devel] FT4 and FT8 Contesting

Andy, if you don't receive RR73 you should resent your report. It is a clear message that my RR73 was lost and I need to send a new one. I may even send RRR and you should response to that. By receiving my RR73 you should know that I am happy with this QSO and you should log it as well, hi. Best L

Re: [wsjt-devel] 7 Digit Callsigns

mode, there are no CQ calls and the structured messages are much simpler since they are beacon transmissions. The handling of non-standard calls is also different from QSO modes. 73 Bill G4WJS. On 21/02/2020 06:39, Reino Talarmo wrote: Hi Matt, You should be possible to send CQ me

[wsjt-devel] EU VHF contest logging misbehaviour

Hi, I noted that in the EU VHF contest logging a wrong information is logged into database, when AP decoding and automatic logging is activated. If the confirmation message that initiates logging happens to be decoded with AP, then the AP level (a2) will be logged instead of the report and 6 digit

Re: [wsjt-devel] 7 Digit Callsigns

Hi Matt, You should be possible to send CQ message without grid square locator and make contacts with the help on hashed call sign using automatic message generation. There strong limits what can be included into a single message, when the basic call sign is 7 characters long. As a workaround y

Re: [wsjt-devel] TImes being incorrectly recorded in ALL.TXT

Martin and Bill, Yes, decoding do continue after the start of next transmission period. I do see sometimes many decodes after my transmitter has put full power out. I also do prefer that this issue is corrected as timestamps in ALL.TXT provide a nice comparison possibility e.g. for reception by two

Re: [wsjt-devel] Band change @ wsjt-x: decodes of old cycle falsely detected/reported as from new band

Hi Uwe, That is feature and it is recommended to stop monitoring for the duration of band change and erase Band activity display. 73, Reino oh3mA From: DG2YCB, Uwe [mailto:dg2...@gmx.de] Sent: 20. helmikuuta 2020 12:20 To: wsjt-devel@lists.sourceforge.net Subject: [wsjt-devel] Band change @

Re: [wsjt-devel] FT8 encoding logic

It seems that many, if not all messages, where the call sign is in the 'sender' position are reported to pskreporter.info. So 'DE VE3GHM FN25' would be fine, if non-standard call sign were supported with a locator. No need to use CQ, if broadcasting and not needing a response at that time. 73, Rei

Re: [wsjt-devel] FT8 encoding logic

>Since my call is six characters the grid gets truncated hence the reason for >my journey of discovery down the path of digging into the WSJT-X source to >understand how the standard message with non-standard call logic works. Hi Graham, You have an interesting Pico Balloon project. May I as

Re: [wsjt-devel] WSJT-X bug report

Zoli! You got a nice work-around for working non-standard call signs. The Users Guide states in clause 7.5 Except for the special cases involving /P or /R used in VHF contesting, WSJT-X 2.1 offers no support for two nonstandard callsigns to work each other. Good luck and 73, Reino oh3mA

Re: [wsjt-devel] Double-click RR73

While in the middle of a QSO you should use either ’Now’ or ’Next’ to modify message sequence instead of a double-click, I assume. 73, Reino oh3mA >When trying to resume a QSO when they repeat an RR73 the double-click produces >TX 3 instead of TX 5. Seems like this has been a problem for a

Re: [wsjt-devel] Anomaly in QSO count in log file

It is just number of different call signs, I assume. Are then e.g. OH3MA and OH3MA/P different or are OH3MA and OH0/OH3MA different? It is me in all cases. 73, Reino oh3mA ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sour

Re: [wsjt-devel] Feature Suggestion: Fox Mode

Hi Jon, All that is already supported by Configurations. Of course one has to do settings himself. On the other hand you may then select your fox base frequency freely. 73, Reino oh3mA ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net http

Re: [wsjt-devel] Problem with radio's audio input

The original mail stated: "I'm seeing a kind of noise at the beginning of many of my transmission. Anyone knows how I could verify if it is a problem with my radio, the sound card (which is embedded in the radio I think) or the WSJT-X software?" The video shows some kind of instability, perhaps a l

Re: [wsjt-devel] WSJT-X Issues

Hi Mark, Just download version 2.1.2 and all should be OK. 73, Reino oh3mA ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] odd county name listing

Hi Tim, You are using a priori decoding. See Manual section 12.1. for more details. 73, Reino oh3mA ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Veird

Hi, Seems to be a hash collision! 73, Reino oh3mA 072715 Tx 1047 ~ VK4JNA/5 RR73 072730 -6 0.4 553 ~ VK4JNA/5 73 < I see OH2YG, but my friend saw 072730 -2 0.3 550 ~ VK4JNA/5 73 < No wav avaiable. Any idea what

Re: [wsjt-devel] FT8 Fox and Hound Mode - FOX Mode Operator

Hi Grant, I assume that the timestamps in the ALL.TXT are taken from the slot time counter at the moment, when software has performed its reception decoding. If the decoding happens to take place after the start of the next transmission, then the time indicated is wrong. That may or may not bee

Re: [wsjt-devel] WSJTX Bug - RSTR / RSTS will be logged incorrectly..

Joe informed that it is addressed in the next release. The same issue is in EU VHF contest mode. 73, Reino oh3mA ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] adif log

File > Open log directory wsjtx_log.adi 73, Reino oh3mA ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Grid proposal

Hi Andy, That would work fine with standard call signs, but already now special call signs don't add (support) grid in CQ and that may be misleading. 73, Reino oh3ma >The solution seems simple to me - If you want callers to reply to your CQ with a grid then include your grid in your CQ. If

Re: [wsjt-devel] Occasional zero power indication when transmitting

Fred, If so, reason could be disturbed Cat communication due RF going into USB interface. 73, Reino once in a while, when CQing or anwsering using WSJTX, my IC-7300 go in TX mode (TX indicator + fan running) but the Power meter (Po) show zero output power. Just before the occurence, everyt

Re: [wsjt-devel] FT8 Screen Layout

Just a minor performance issue the latest version of the wsjt-z is 32 bits Windows. The 64 bits performance is much better than 32 bits. I have solved you display problem using two displays and small font. 73, Reino oh3ma >You can download it here: https://sourceforge.net/projects/wsjt-z/fil

Re: [wsjt-devel] FT8/4 Color Codes

Hello Dave, That was a different issue at the start a WSJT-X program: It was answered today. Re: [wsjt-devel] Lookup bug in WSJT-X 2.1.0 WSJT-X is designed to show colors only at CQ messages to keep it simple and clear. I have hear

Re: [wsjt-devel] WWDIGI Tesdting

Hello Claude and All, Claude wrote: A similar situation occurs outside of the contest mode, if the one station sends RR73 and the partner stations sends 73, which the first station was not able to decode. The QSO cannot be considered as ended. This point has been mentioned many times previously.

Re: [wsjt-devel] Random mode switch ?

Hello Al, My knowledge about the latest FT8 coding is limited, I recognize ‘~’ meaning FT8. The first line is interesting as it ends with ‘K’. The real reason is KC3IME, who answered to your call with EU VHF report and that switched your WSJT-X to response it properly as designed. He’s been in

Re: [wsjt-devel] Contest confusion

>Thus, ham radio has a free opportunity to return to its roots when RST was meaningful and exchange meaningful SNR reports. Readability and Tone don't have much value in the WSJT-X modes, but signal strength adds interest and some substance to each QSO. I'm a strong advocate of supporting SNR in

[wsjt-devel] signal report RST

Hi All, There has been many situation, where FT8 signal quality is less than perfect due to hum, actually hum related harmonics. In one example hum related sidebands were down relative to the intended signal: Delta frequency, signal strength -600 = 10 x 60 Hz, -41 dB -240 = 4 x 60 Hz, -29 dB

Re: [wsjt-devel] FT8 ghost signals

Hi Roland, Yes there are now and then 100 or -100 Hz differences and some with 50 or -50 Hz. The latter is an indication that 50 Hz mains is overloading some section of audio path. It may also happen at the receiver side. I did not analyzed, if this is the case on those 50 Hz instances. But a l

Re: [wsjt-devel] FT8 ghost signals

17 0.3 950 WC4H W4I R-13 120 190708_22404550.313 Rx FT8-24 0.3 350 WC4H W4I 73 190708_22404550.313 Rx FT8-14 0.3 709 WC4H W4I 73 Thanks for the tip. Here is the episode. Bill W2PKY On Sat, Jul 13, 2019 at 1:46 PM Reino Talarmo mailto:reino.tala

Re: [wsjt-devel] FT8 ghost signals

Bill, Do you happen to have an ALL.TXT on that situation? If so what was the frequency difference between those sub-harmonics? 73, Reino oh3ma ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ws

Re: [wsjt-devel] FT8 ghost signals

Hi All, >Evidently what's puzzling you is Doppler shifts that remain nearly constant for a minute or so. Aircraft at 10,000 meters can be line-of-sight visible at distances up to several hundred km. With typical aircraft speeds, in such cases the geometry for bi-static reflections will not chang

Re: [wsjt-devel] FT8 ghost signals

Hi All, Perhaps this a wrong forum, but still I like to ask how you explain ghost signals with varying frequency offset? Do you have both a direct signal and an ES reflection from a moving cloud? 73, Reino oh3ma ___ wsjt-devel mailing list wsjt-devel

Re: [wsjt-devel] 60 Hz + harmonics sidebands on FT8 signals?

When those sidebands are 60 Hz steps from the main signal, then there is a 60 Hz mains and the audio going into an nonlinear part in the transmitter and those signals are mixed together. More often the sidebands are in 120 Hz steps due to full wave rectification in power supply. If in an power a

Re: [wsjt-devel] Does the FT8 signal spike at the beginning of each transmission?

>1. The power spike problem can be “avoided” through keeping the xmtr power >low at the beginning of each cycle and then gradually increasing it. I have >bit of auxiliary code in Xojo which can do this, ramping power up during the >first 5 seconds of the cycle. Is it known what actually ca

Re: [wsjt-devel] Field Day time problem

>Why actually set the computer clock? Just compute an offset for the local >clock based on the mean (or median) of the DT of the decoded messages. Then >use this offset within WSJT-X to adjust the time used in the software from the >actual computer clock. Hi Jim Consider what would happen, if

Re: [wsjt-devel] Field Day time problem

Thanks for comments. I totally agree the GPS solution, just everybody needs to do so! I have one. Actually I did not proposed, at least not before testing, any addition or change into WSJTX. I just proposed a method more useful here, the other side of pond, were WWV etc. are not so strong and

Re: [wsjt-devel] Field Day time problem

Hi, We are amateurs and could provide another time distribution experiment especially during Field Day events. I mean setting up time beacon or beacons that send e.g. every 15 s a short pulse, say 100 ms, on the base carrier frequency e.g. 14.080 MHz. Timing of that pulse could be 'minute mark

Re: [wsjt-devel] Unwanted automatic switching to contest mode

Returning to the STATE value that now contains Maidenhead locator as an EU VHF contest exchange information. I also think that it is a mistake to use the STATE field for that purpose. We have and that now contains the same information. Perhaps the use of the STATE field in the EU VHF contest is j

Re: [wsjt-devel] Unwanted automatic switching to contest mode

>190622_095330 7.074 Tx FT8 0 0.0 1480 HB9CGH DJ0OT -04 190622_095400 7.074 Tx FT8 0 0.0 1480 HB9CGH R 550001 JN58TC >Some observations: 55 and 55 were not exchanged in the QSO and they are typical FONE reports. According to the ADIF specs, I consider JN36RW as not valid. Th

Re: [wsjt-devel] Clock Sync Tolerance

FT8 should deal with 2.5 s time´difference so +/- 1 s is suitable tolerance. FT4 at the moment tolerates 1 s difference so less than half a second say 400 ms is a suitable target. 73, Reino oh3ma ___ wsjt-devel mailing list wsjt-devel@lists.sourcef

Re: [wsjt-devel] Fox power level

>The optimum solution would probably be an asymmetric mode where multiple QSOs >can be held using a single MFSK message. Perhaps 3 times as much information >for the Fox with messages like: >K1ABC -10; W9MDB -05; G4WJS RR73; K1JT -06; K9AN RR73; DE P5RAREDX >Just sending the Fox call once per p

Re: [wsjt-devel] RU mock contest, some observations

Hi Tom, It seems that YO6.. did not received your report confirmation in first place. Even the RR73 seems not be a real one. In that situation you should not send RR73, perhaps 73 instead. I think that was a nice example how some operators don’t give up even, when they don’t decode you any mor

Re: [wsjt-devel] Time

Claude wrote: " as well as the propagation delay and the time needed to decode." We may forget propagation time that is less than 0.1 s on globe, moonbounce is another issue. To my understanding dT is calculated based on message time sync location on the received timeslot and is fully independent

Re: [wsjt-devel] Expiration Date on Software

Hi Onno, >A better idea is to include a protocol version number in the QSO information, >that way both sides have a chance to alert the operator. A nice idea, but that information needs to be sent using the lower layer of the previous protocol version…. 73, Reino, oh3ma ___

[wsjt-devel] FT4 mock contest RR73

Hi All, >I think it would be helpful for the called station to return a 73 message in >response my RR73. As things are now, if I received nothing after sending >RR73, I do not know if the other station received my RR73 or if I could no >longer copy the other station due to band conditions or QR

[wsjt-devel] FT4 mock contest

Hi, I joined the contest half an hour late. I got 8 QSOs to European stations during the test and two US QSOs just after the test! I got typically three to five decodes per timeslot, but my 100 W in a three legged dipole was not enough for more exotic contacts. In earlier successful FT4 QSOs decod

[wsjt-devel] FT4 timing accuracy

Hi, Thanks for an excellent piece of communication protocol both FT8 and FT4. It would be interesting to see how big guns start to use FT4 instead of RTTY. For strong signals RTTY is a bit faster than FT8, but most of the users are not big guns! The bandwidth saving in FT4 is a really big issue, s

<    1   2   3