[wsjt-devel] RTTY RU Log Questions
Hi All: My first contest sorry for some simple questions. First, I figured how to edit Contest Name, at Log Export just use ARRL-RTTY. I do have a specific problem, have to set RTTY RU EXC to DX (Advance Settings). After uploading my log, I am receiving warnings "copied exchange (qthserial) is missing". What I have to do to fix those errors. Some QSO's have the serial (if DX) and others have US State letters example ND, FL, NC. So my logs have mixed letters for US States and numbers for DX. is there is a way to fix this? Sorry newbie with contests. 73' Edfel KP4AJ ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
[wsjt-devel] RTTY RU Contest Name FT8-RU
Hi: Seems I missed resetting title. Any idea how to change Contest name and what is the correct contest name. Previous to the contest I reset log but name of previous contest is still there. BTW, great contest for FT8 and WSJTX. For those who were skeptical about contesting compliance capabilities in v2, answer is now clear. Regards! 73' Edfel KP4AJ ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
[wsjt-devel] K1JT and other observations
BTW, it was a pleasure to see Dr. Joe Taylor participating in the RTTY RU. I managed to QSO with him on 3 different bands. Next, I saw a situation where there were 2 FT8 stations operating within the 170 Hz separation area of a single RTTY signal. Hopefully they did not interfere with the RTTY station. And I was able to decode them. Next, the FT8 mode is a bit better about decoding overlapping signals as compared to the first release of FT8. As a humble AR operator, I can hope that decoding of overlapping FT8 signals will improve in future releases of wsjtx. 73 to all ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] Rtty Ru lock out
I have configured wsjtx to not allow a change in frequency during transmit. During the RTTY RU contest, the receive frequency was locked as well as the transmit frequency. It was a bit annoying that I could not move the receive bracket during transmission. Sometimes the receive bracket would not update to the current QSO station and not being able to manually update it was a hassle. Not updating receive bracket: when I was finishing a QSO, occasionally a station would tailgate. I clicked on that station (right panel) and the sequence would update the TX list, but not the receive bracket (in the waterfall display). On Sun, Jan 6, 2019, 2:27 PM Thomas Kocourek I ran into the same issue during the RTTY RU contest. The work-around > which I used was to click on TX6 (CQ) and reenable the transmit in advance > of getting an answer back from the other station. If they were successful > in receiving my RR73, I aborted the CQ and chose my next QSO partner. > > On Sun, Jan 6, 2019, 11:06 AM Saku >> >> Working as "search, not CQ" station there is one thing in RTTY RU >> actions that I would like to change. >> When I pick a CQ calling station, send "RST NR" and get "R RST NR" as >> return my next TX will be "RR73". >> >> But when that happens the radio button "Next" jumps to TX_6. Always, not >> depending have I logged qso or not. >> >> This makes extra work as while I'm sending RR73 I have to manually >> change "Next" radio button back to TX_4 (RR73) >> in case that opponent station did not receive my RR73 and keeps >> transmitting "R RST NR" . >> Then just press TX enable on again will repeat RR73. >> >> Suggestion: >> >> Drop "Next" radio button to TX_6 only after qso is logged, not from >> RR73 sending action. >> Dropping TX enable off is ok during RR73 sending period. Just keep >> the "Next" at TX_4. >> >> >> v2.0/Linux/Fedora28 >> >> >> -- >> Saku >> OH1KH >> >> >> >> ___ >> 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] Rtty Ru property of TX_4->TX_6
I ran into the same issue during the RTTY RU contest. The work-around which I used was to click on TX6 (CQ) and reenable the transmit in advance of getting an answer back from the other station. If they were successful in receiving my RR73, I aborted the CQ and chose my next QSO partner. On Sun, Jan 6, 2019, 11:06 AM Saku > Working as "search, not CQ" station there is one thing in RTTY RU > actions that I would like to change. > When I pick a CQ calling station, send "RST NR" and get "R RST NR" as > return my next TX will be "RR73". > > But when that happens the radio button "Next" jumps to TX_6. Always, not > depending have I logged qso or not. > > This makes extra work as while I'm sending RR73 I have to manually > change "Next" radio button back to TX_4 (RR73) > in case that opponent station did not receive my RR73 and keeps > transmitting "R RST NR" . > Then just press TX enable on again will repeat RR73. > > Suggestion: > > Drop "Next" radio button to TX_6 only after qso is logged, not from > RR73 sending action. > Dropping TX enable off is ok during RR73 sending period. Just keep > the "Next" at TX_4. > > > v2.0/Linux/Fedora28 > > > -- > Saku > OH1KH > > > > ___ > 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] Able to send RRR in ARRL RTTY RU
Hi, I have received a number of RRR messages at the end of a QSO in this weekends RU. I believe this is caused by users operating with tab 2 (iso tab 1) and initiating the QSO. If there is no reason for a RRR in ARRL RU contest mode , maybe disabling tab 2 and 3 ? Best regards and enjoying the contest ! 73's Erik ON4PB ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
[wsjt-devel] Rtty Ru property of TX_4->TX_6
Working as "search, not CQ" station there is one thing in RTTY RU actions that I would like to change. When I pick a CQ calling station, send "RST NR" and get "R RST NR" as return my next TX will be "RR73". But when that happens the radio button "Next" jumps to TX_6. Always, not depending have I logged qso or not. This makes extra work as while I'm sending RR73 I have to manually change "Next" radio button back to TX_4 (RR73) in case that opponent station did not receive my RR73 and keeps transmitting "R RST NR" . Then just press TX enable on again will repeat RR73. Suggestion: Drop "Next" radio button to TX_6 only after qso is logged, not from RR73 sending action. Dropping TX enable off is ok during RR73 sending period. Just keep the "Next" at TX_4. v2.0/Linux/Fedora28 -- Saku OH1KH ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] MSK144 period length change (by itself)
Aaaahh! Yes Bill! You are right. I was looking at 00-30-00 times, but 15-45-15 makes also 30sek ;-( I now carefully looked again ALL.TXT during those 2 days that I did use MSK. All transmits seem to be 30sek periods. How ever I can not understand that because I have predefined setup for MSK and I load that when I start to work MSK. I just loaded it again like I did then and it gives 15sec. been at If I would have changed it during last working session I assume it would have saved 30sec period time that would now show up again. Or am I wrong (again also with this) ? I suppose not, as I did now change period to 30sec and close program. When started again it was still 30sec. Then changed it to 5sec and loaded normal HF profile (without shutting down). And then loaded again MSK profile and 5sec was there as expected. So If loading now MSKprofile from RTTY RU profile as first time after last worked MSK sessions it should have shown 30sec period, not 15sec as you can see from capture. I'm still wondering what really happened. (Like I'm wondering that I can not get rid of "been at" text after I pasted the screen capture. Deleting it makes it just pop up to another place. So ignore it) Bill Somerville kirjoitti 6.1.2019 klo 13.26: On 06/01/2019 10:22, Saku wrote: For some reason (any possibility of bug?) v2.0/Linux/Fedora28 has changed period length by itself from 15sec to 30sec and then back again to 15sec. No explanation for this. Has anybody else ever seen something similar? A cut of ALL.TXT is attached Hi Saku & HNY, your extract from ALL.TXT does not support your reported issue. All the transmissions are at 30s intervals which is consistent with 15s T/R periods. 73 Bill G4WJS. ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel -- Saku OH1KH ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] MSK144 period length change (by itself)
On 06/01/2019 10:22, Saku wrote: For some reason (any possibility of bug?) v2.0/Linux/Fedora28 has changed period length by itself from 15sec to 30sec and then back again to 15sec. No explanation for this. Has anybody else ever seen something similar? A cut of ALL.TXT is attached Hi Saku & HNY, your extract from ALL.TXT does not support your reported issue. All the transmissions are at 30s intervals which is consistent with 15s T/R periods. 73 Bill G4WJS. ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
[wsjt-devel] MSK144 period length change (by itself)
Hi! Few days ago I worked some qsos on 6m / MSK144. Afterwards I was advised that I should not use 30sec periods. How ever I did not touch period length at any time. It was 15sec when I started and 15sec when I ended working. I am absolutely sure I did not touch it meanwhile. And if I had set it to 30sec by accident, not knowing what happened, I should have been "double lucky" to put it back to 15sec again by accident without knowing it ! For some reason (any possibility of bug?) v2.0/Linux/Fedora28 has changed period length by itself from 15sec to 30sec and then back again to 15sec. No explanation for this. Has anybody else ever seen something similar? A cut of ALL.TXT is attached as pasting to this message did not work ok. It mixed line feeds. Even when the cut was filtered twice and should not have any control characters. (a thing that I also have never seen before when pasting plane text file). Mysterious start for year 2019! -- Saku OH1KH 190104_133615 Transmitting 50.28 MHz MSK144: OH1KH R+02 190104_133645 Transmitting 50.28 MHz MSK144: OH1KH R+02 190104_133715 Transmitting 50.28 MHz MSK144: OH1KH R+02 190104_133745 Transmitting 50.28 MHz MSK144: OH1KH R+02 190104_145900 Transmitting 50.28 MHz MSK144: CQ OH1KH KP01 190104_145930 Transmitting 50.28 MHz MSK144: CQ OH1KH KP01 190104_15 Transmitting 50.28 MHz MSK144: CQ OH1KH KP01 190104_150030 Transmitting 50.28 MHz MSK144: CQ OH1KH KP01 190104_150100 Transmitting 50.28 MHz MSK144: CQ OH1KH KP01 190104_150130 Transmitting 50.28 MHz MSK144: SP6CPH OH1KH +04 190104_150200 Transmitting 50.28 MHz MSK144: SP6CPH OH1KH +04 190104_150230 Transmitting 50.28 MHz MSK144: SP6CPH OH1KH +04 190104_150300 Transmitting 50.28 MHz MSK144: SP6CPH OH1KH +04 190104_150330 Transmitting 50.28 MHz MSK144: SP6CPH OH1KH +04 190104_150400 Transmitting 50.28 MHz MSK144: SP6CPH OH1KH +04 190104_150430 Transmitting 50.28 MHz MSK144: SP6CPH OH1KH +04 190104_150500 Transmitting 50.28 MHz MSK144: SP6CPH OH1KH +04 190104_150530 Transmitting 50.28 MHz MSK144: SP6CPH OH1KH +03 190104_150600 Transmitting 50.28 MHz MSK144: SP6CPH OH1KH +03 190104_150630 Transmitting 50.28 MHz MSK144: SP6CPH OH1KH -03 190104_150700 Transmitting 50.28 MHz MSK144: SP6CPH OH1KH -03 190104_150730 Transmitting 50.28 MHz MSK144: SP6CPH OH1KH -03 190104_150800 Transmitting 50.28 MHz MSK144: SP6CPH OH1KH -03 190104_150830 Transmitting 50.28 MHz MSK144: SP6CPH OH1KH -03 190104_150900 Transmitting 50.28 MHz MSK144: SP6CPH OH1KH -03 190104_150930 Transmitting 50.28 MHz MSK144: SP6CPH OH1KH -03 190104_151000 Transmitting 50.28 MHz MSK144: SP6CPH OH1KH -03 190104_151030 Transmitting 50.28 MHz MSK144: SP6CPH OH1KH -03 190104_151100 Transmitting 50.28 MHz MSK144: SP6CPH OH1KH -03 190104_151130 Transmitting 50.28 MHz MSK144: SP6CPH OH1KH -03 190104_151200 Transmitting 50.28 MHz MSK144: SP6CPH OH1KH -03 190104_151230 Transmitting 50.28 MHz MSK144: SP6CPH OH1KH -03 190104_151300 Transmitting 50.28 MHz MSK144: SP6CPH OH1KH -03 190104_151330 Transmitting 50.28 MHz MSK144: SP6CPH OH1KH -03 190104_151400 Transmitting 50.28 MHz MSK144: SP6CPH OH1KH -03 190104_151515 Transmitting 50.28 MHz MSK144: DL5XJ OH1KH KP01 190104_151545 Transmitting 50.28 MHz MSK144: DL5XJ OH1KH KP01 190104_151615 Transmitting 50.28 MHz MSK144: DL5XJ OH1KH KP01 190104_151645 Transmitting 50.28 MHz MSK144: DL5XJ OH1KH KP01 ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] RTTX RU 80 m contest avtivity frequency in Europe
Tnx for your info Tom -although that frequency is more exactly 14130 kHz !!! Do you know - or does anyone know the 21 MHz FT8 frequency for ARRL RTTY RU ? We all badly need a list of real FT8 RU calling frequencies for now and for ever! gl de ha6nn Andras On Sun, Jan 6, 2019 at 9:16 AM Tom Ramberg via wsjt-devel < wsjt-devel@lists.sourceforge.net> wrote: > 14030 is lively, mostly EU-EU stuff. > > Tom OH6VDA@OH2K > > 6. jan. 2019 kl. 00:39 skrev : > > Sri those are this side of the pond. > > > Sent from Xfinity Connect Application > > > -Original Message- > > From: n...@comcast.net > To: ha6nn.a...@gmail.com, wsjt-devel@lists.sourceforge.net > Sent: 2019-01-05 5:33:20 PM > Subject: Re: [wsjt-devel] RTTX RU 80 m contest avtivity frequency in Europe > > > 3.59 > 7.08 > 14.13 > > Sent from Xfinity Connect Application > > > -Original Message- > > From: ha6nn.a...@gmail.com > To: wsjt-devel@lists.sourceforge.net > Sent: 2019-01-05 5:16:38 PM > Subject: Re: [wsjt-devel] RTTX RU 80 m contest avtivity frequency in Europe > > Thanks a lot Keith, > I know, but I have problem with 7 MHz ant because of snowing. :( > GL, 73 > > On Sat, Jan 5, 2019 at 10:09 PM Keith Wallace > wrote: > >> Plenty on 40m 7.080 >> >> >> On Sat 5 Jan 2019 at 22:04, Andras Bato wrote: >> >>> For the God's sake, where are RTTY RU FT( contest avtivity is going on? >>> gl de ha6nn >>> Andras >>> ___ >>> 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 > > ___ > 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] RTTX RU 80 m contest avtivity frequency in Europe
14030 is lively, mostly EU-EU stuff. Tom OH6VDA@OH2K > 6. jan. 2019 kl. 00:39 skrev : > > Sri those are this side of the pond. > > > Sent from Xfinity Connect Application > > > -Original Message- > > From: n...@comcast.net > To: ha6nn.a...@gmail.com, wsjt-devel@lists.sourceforge.net > Sent: 2019-01-05 5:33:20 PM > Subject: Re: [wsjt-devel] RTTX RU 80 m contest avtivity frequency in Europe > > > 3.59 > 7.08 > 14.13 > > Sent from Xfinity Connect Application > > > -Original Message- > > From: ha6nn.a...@gmail.com > To: wsjt-devel@lists.sourceforge.net > Sent: 2019-01-05 5:16:38 PM > Subject: Re: [wsjt-devel] RTTX RU 80 m contest avtivity frequency in Europe > > Thanks a lot Keith, > I know, but I have problem with 7 MHz ant because of snowing. :( > GL, 73 > >> On Sat, Jan 5, 2019 at 10:09 PM Keith Wallace wrote: >> Plenty on 40m 7.080 >> >> >>> On Sat 5 Jan 2019 at 22:04, Andras Bato wrote: >>> For the God's sake, where are RTTY RU FT( contest avtivity is going on? >>> gl de ha6nn >>> Andras >>> ___ >>> 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 ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
[wsjt-devel] New station layout RX TX
HNY I want to control with CAT different rigs,one receiver and one transmitter with different COM ports under WSJT-X. Any idea how I can do it? Thank you Alex SV8QG ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
