Date   

State QSO Party Challenge - News Release -

Stan K4SBZ
 

 

 

StateQSOParty.com

 

 

 

State QSO Party Challenge

 

-    News Release    -

 

 

 

The StateQSOParty.com Team has announced the 2020 State QSO Party Challenge. This annual program will recognize all radio amateurs’ participation in the U.S. State and Canadian Province QSO parties. It will be open to any radio amateur who participates in any of our approved State QSO Party (SQPs) contests. Participants must simply submit their scores to 3830Scores.com to be included in the Challenge.

 

 

 

Participants will be recognized for reaching five levels of achievement – Bronze, Silver, Gold, Platinum and Diamond. Using the submissions to 3830Scores.com, each radio amateur’s cumulative score will be calculated by totaling up his/her number of reported contacts and multiplying by the number of SQPs entered year-to-date.  Using the number of SQPs entered as a multiplier is expected to encourage radio amateurs to enter more state/province QSO parties. The use of the number of contacts as a metric is to encourage participants to operate longer in each SQP, increase the effectiveness of their station and improve their contesting skills. To qualify for an award level, the participant must have participated in at least two State QSO Parties. Each State QSO Party entry must have at least two QSOs.  

 

 

 

It is also expected that this program will positively benefit all SCPs, especially those that currently have lower participation levels.

 

 

 

The first SQPs in 2020 are the Vermont, Minnesota and British Columbia QSO Parties on the first weekend of February. Therefore, the first monthly report of the State QSO Party Challenge is scheduled to be available in early March 2020. The cumulative year-to-date Challenge scores will be published on the QSOParty.io forum and on the State QSO Party website (www.StateQSOParty.com). The full rules and other details of the Challenge are available on www.StateQSOParty.com).

 

 

 

Special thanks to Bruce Horn, WA7BNM of 3830scores.com for creating the SQP Activity Tracker located at 3830scores.com

 

 

 

If you have any questions regarding the State QSO Party Challenge, please contact Dave Edmonds, WN4AFP at daveedmo@... 

 

 

 

 

 


Re: AMTOR?

Andrew OBrien
 

Ha!  As we start a new decade, here is our first post to this email group from the year 2000!

Andy K3UK (ex KB2EOQ) 


Re: Meteor Scatter

Tony
 

Anyone doing MSK144 these days? Andy K3UK
I've been using MFSK144 on meteor scatter since it was introduced in 2016. It's said to decode better than FSK441 and that does seem to be the case.

This video shows several meteor pings decoding down into the -5 to -7 db range: https://www.youtube.com/watch?v=_DZZj1HUJIY

I ran a quick test on 6 meters to illustrate the range we often see on meteor scatter -- see attached image.

Tony -K2MO


Re: Meteor Scatter

Andrew OBrien
 

Anyone doing MSK144 these days ?
Andy K3UK


Re: Ham Radio Deluxe Logging with FT4

Tony
 

David:

Thanks for the tip. I'll keep an eye out for HRD updates. 

Tony -K2MO


On 12/5/2019 5:09 PM, David [kg5eiu] via Groups.Io wrote:
Hi Tony,

I am also using HRD to log and until the next release HRD will logging will show MFSK - when the QSO gets sent over from WSJTX into the HRD log.
Here is how I am dealing  with it.

in HRD setup (I am running 6.6.0.236) setup under Tools--->Configure--->Modes  add a FT4 mode and ADIF definition as FT4

as you collect log entries in HRD select them and then More--->Bulk Editor-->Any Fields
click on the Field TAB in that window and then select Add Field and in that window select the Mode and in the List box select FT4
save it all out THEN proceed to upload to the cloud logs, eQSL, QRZ, LoTW etc etc.




Re: Ham Radio Deluxe Logging with FT4

David [kg5eiu]
 

Hi Tony,

I am also using HRD to log and until the next release HRD will logging will show MFSK - when the QSO gets sent over from WSJTX into the HRD log.
Here is how I am dealing  with it.

in HRD setup (I am running 6.6.0.236) setup under Tools--->Configure--->Modes  add a FT4 mode and ADIF definition as FT4

as you collect log entries in HRD select them and then More--->Bulk Editor-->Any Fields
click on the Field TAB in that window and then select Add Field and in that window select the Mode and in the List box select FT4
save it all out THEN proceed to upload to the cloud logs, eQSL, QRZ, LoTW etc etc.



Re: Ham Radio Deluxe Logging with FT4

Dave AA6YQ
 

* AA6YQ comments below

+ The ADIF representation for FT4 is <MODE:4>MFSK <SUBMODE:3>FT4
Understand the designation, but notice how FT8 is logged in HRD (see attached). It shows FT8 as the mode while FT4 shows up as MFSK.

* The ADIF representation for FT8 is

<MODE:3>FT8

* Yes, the two representations are inconsistent, but that's irrelevant from every perspective except aesthetics.

* What is specified in ADIF is what logging applications must implement if they wish to provide their users with the ability to interchange QSO information.

73,

Dave, AA6YQ


Re: Ham Radio Deluxe Logging with FT4

Tony
 

Dave:

+ The ADIF representation for FT4 is <MODE:4>MFSK <SUBMODE:3>FT4
Understand the designation, but notice how FT8 is logged in HRD (see attached). It shows FT8 as the mode while FT4 shows up as MFSK.

Good to hear from you - hope all is well.

Tony -K2MO


On 12/4/2019 2:24 AM, Dave AA6YQ wrote:
+ AA6YQ comments below

I've been using HRD to log all WSJT-X contacts in the HRD logbook. It works fine for all modes, but I've noticed that my FT4 contacts are being logged as MFSK.

I used the the HRD mode editor to add FT4 to the list of modes yet the problem still exists. The WSJT-X logging window shows FT4 in the mode field, but it winds up as MFSK in the HRD log.

Any ideas?

+ The ADIF representation for FT4 is

<MODE:4>MFSK <SUBMODE:3>FT4

73,

Dave, AA6YQ




Re: Ham Radio Deluxe Logging with FT4

Dave AA6YQ
 

+ AA6YQ comments below

I've been using HRD to log all WSJT-X contacts in the HRD logbook. It works fine for all modes, but I've noticed that my FT4 contacts are being logged as MFSK.

I used the the HRD mode editor to add FT4 to the list of modes yet the problem still exists. The WSJT-X logging window shows FT4 in the mode field, but it winds up as MFSK in the HRD log.

Any ideas?

+ The ADIF representation for FT4 is

<MODE:4>MFSK <SUBMODE:3>FT4

73,

Dave, AA6YQ


Ham Radio Deluxe Logging with FT4

Tony
 

All:

I've been using HRD to log all WSJT-X contacts in the HRD logbook. It works fine for all modes, but I've noticed that my FT4 contacts are being logged as MFSK.

I used the the HRD mode editor to add FT4 to the list of modes yet the problem still exists. The WSJT-X logging window shows FT4 in the mode field, but it winds up as MFSK in the HRD log.

Any ideas?

Tony -K2MO


Re: K3RWR TX ON 136/OP32 1 WATT #opera

Graham
 

Beacon remains active still  
Summery of stations  ,  spotting  K3RWR  
via the  opera  reporting  system 
range in Km 

Interestingly ,  mode  op32 , was intended to provide ,  reliable  Transatlantic Spots on the  136 band
the  -40 db s/n  for the  decoder , is proving to be sufficient  , with the additional  -5 dB provided  by the  
second  chance, 'correlection detector' a [Tx time of 2 hours would be  required to reach -45/-46] 
a high % of transmissions are being  reported  

nb- those interested in lf propagation,  the  results , are the  average levels , during the  tx  time , only 
the  system is  single pass ,  

73-Graham
g0nbd


2019-11-28 00:42:20 K3RWR FM18QI W1VD/1 FN31LS 487 136 -7 Op32_||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||_~7dB
2019-11-27 06:01:00 K3RWR FM18QI LA3EQ/MW JO28XJ 6.053 136 -43 Op32__~44dB
2019-11-26 07:04:03 K3RWR FM18QI 2E0ILY IO82QV 5.703 136 -41 Op32__~41dB
2019-11-26 03:47:25 K3RWR FM18QI G8LCO IO91VU 5.893 136 -38 Op32__~38dB
2019-11-26 03:14:37 K3RWR FM18QI LA3EQ JO28XJ 6.053 136 -43 Op32__~44dB
2019-11-24 02:24:43 K3RWR FM18QI PA0LSB JO21LQ 6.235 136 -45 Op32__~45dB
2019-11-24 02:24:41 K3RWR FM18QI PA0RDT JO11TM 6.155 136 -44 Op32__~45dB
2019-11-23 23:08:01 K3RWR FM18QI EB8ARZ IL18UK 5.609 136 -41 Op32__~42dB
2019-11-21 02:00:46 K3RWR FM18QI KU4XR EM75XR 720 136 -9 Op32_||||||||||||||||||||||||||||||||||||||||||||||||||||||||||_~9dB
2019-11-21 00:22:54 K3RWR FM18QI W3BRB EM93TE 667 136 -44 Op32__~44dB
2019-11-21 00:22:50 K3RWR FM18QI K3SIW-1 EN52TA 1.077 136 -25 Op32_||||||||||||||||||||||||||_~25


APRX configuration

John Spoonhower
 

If anyone one here has experience configuring aprx, I could use some help. Please contact me directly at NX2I@... and I can provide some details. I have tried to post information over on the APRX google group but there doesn't seem to be any activity. I am having problems forwarding APRS-IS packets, specifically packets that originate with SMSGTE. The RF to SMS path (APRS -->SMS) works OK ; it's the reverse that I cannot get working.

73, John, NX2I


Re: #opera Icom 7610 CAT and Opera ? #opera

Graham
 

Thank's Andy 

The app , should  auto  detect the   settings , its usually  quite  robust,  at least its working , 
after  FT8  was launched ,   activity  on HF all  but  cane to a  end , 
But,  as  you  can see  from the  spot listing ,  the  net  using the  AO-100   sat  remains 
active  with  2.4 GHz up and  10 GHz  down  links ,.  all  showing on the  psk-map as  1296 MHz
the  highest  the  map  shows  

Fixed  2 and 70 cm beacons  in  south  EU F5ZAL  10  watts  to  loop on 2 meters 

And the  136 op32 LF activity , providing  some quite  outstanding  dx  with power levels in 
100 watt  region , [bold = full  decode , other are  correlation  spots , but time  match = ok]

73-Graham 
g0nbd 

2019-11-22 03:53:19 EA5DOM AA KU4XR EM75XR 0 136 -44 Op32__~44dB
2019-11-22 03:53:17 EA5DOM AA G8LCO IO91VU 0 136 -22 Op32_||||||||||||||||||||||||||||||||_~22dB
2019-11-22 03:53:17 EA5DOM AA RX3DHR KO94KS 0 136 -44 Op32__~45dB
2019-11-22 03:53:16 EA5DOM AA    I55387FI JN52HX 0 136 -29 Op32_||||||||||||||||_~30dB
2019-11-22 03:53:14 EA5DOM AA SM2DJK KP03AU 0 136 -27 Op32_||||||||||||||||||||_~28dB
2019-11-22 03:53:14 EA5DOM AA SV8RV KM07KS 0 136 -23 Op32_||||||||||||||||||||||||||||_~24dB
2019-11-22 03:53:13 EA5DOM AA PA0RDT JO11TM 0 136 -18 Op32_||||||||||||||||||||||||||||||||||||||||_~18


Re: K3RWR TX ON 136/OP32 1 WATT #opera

Graham
 

K3RWR  Continues , TX overnight  on 136 KHz
Providing  some  interesting  results  on the  path 
with virtual continuous spots  at EA8 , Canary islands 
no other EU  spots  , until  last night, producing 
spots from PA 

73-Graham
g0nbd

NB- Opera  is a  single pass  system , so  the  results  are  relevant  , at  and during the  time  of  each TX
in this  case  32 mins  per tx  cycle , tme is used , to  lower  the  s/n  limit,  the  longer the tx  time
the  more energy available  , allowing  detection  to  -45 db s/n in 2.4 KHz  b/w
yes the  duty cycle is  50% , but  when tx is  'off' no power is  wasted , hence the 
average is  50% of the  power supplied , in contrast ,  the system runs at 30 seconds 
for VHF use at  -23 dB s/n 

[ ignore the  -32 dB s/n  for these spost ] 
OPERA
0.136
22/11/2019 22:37
United States
K3RWR
FM18qi
EB8ARZ
IL18UK
RX -32.8dB on 137500.0Hz
OPERA
0.136
22/11/2019 23:09
United States
K3RWR
FM18qi
EB8ARZ
IL18UK
RX -32.8dB on 137500.0Hz
OPERA
0.136
22/11/2019 23:42
United States
K3RWR
FM18qi
EB8ARZ
IL18UK
RX -32.8dB on 137500.0Hz
OPERA
0.136
23/11/2019 00:15
United States
K3RWR
FM18qi
EB8ARZ
IL18UK
RX -32.8dB on 137500.0Hz
OPERA
0.136
23/11/2019 00:48
United States
K3RWR
FM18qi
EB8ARZ
IL18UK
RX -32.8dB on 137500.0Hz
OPERA
0.136
23/11/2019 01:20
United States
K3RWR
FM18qi
EB8ARZ
IL18UK
RX -32.8dB on 137500.0Hz
OPERA
0.136
23/11/2019 01:53
United States
K3RWR
FM18qi
EB8ARZ
IL18UK
RX -32.8dB on 137500.0Hz
OPERA
0.136
23/11/2019 02:26
United States
K3RWR
FM18qi
EB8ARZ
IL18UK
RX -32.8dB on 137500.0Hz
OPERA
0.136
23/11/2019 02:59
United States
K3RWR
FM18qi
EB8ARZ
IL18UK
RX -32.8dB on 137500.0Hz
OPERA
0.136
23/11/2019 03:32
United States
K3RWR
FM18qi
EB8ARZ
IL18UK
RX -32.8dB on 137500.0Hz
OPERA
0.136
23/11/2019 04:04
United States
K3RWR
FM18qi
EB8ARZ
IL18UK
RX -32.8dB on 137500.0Hz
OPERA
0.136
23/11/2019 04:37
United States
K3RWR
FM18qi
EB8ARZ
IL18UK
RX -32.8dB on 137500.0Hz
OPERA
0.136
23/11/2019 05:10
United States
K3RWR FM18qi EB8ARZ IL18UK RX -32.8dB on 137500.0Hz
OPERA
0.136
23/11/2019 05:43
United States
K3RWR FM18qi EB8ARZ IL18UK RX -32.8dB on 137500.0Hz
OPERA
0.136
23/11/2019 06:15
United States
K3RWR FM18qi EB8ARZ IL18UK RX -32.8dB on 137500.0Hz
OPERA
0.136
23/11/2019 07:21
United States
K3RWR FM18qi EB8ARZ IL18UK RX -32.8dB on 137500.0Hz

Compared  with  last night, 

  
Only 2  spots showing  at EA8
what looks like qsb  with W3 
First spots from PA  
Peak in signal , out west  at the  same time as the  opening  to  PA ,  , to K3 

2019-11-24 02:24:43 K3RWR FM18QI PA0LSB JO21LQ 6.235 136 -45 Op32__~45dB
2019-11-24 02:24:41 K3RWR FM18QI PA0RDT JO11TM 6.155 136 -44 Op32__~45dB

2019-11-24 04:03:00 K3RWR FM18QI K3SIW-1 EN52TA 1.077 136 -26 Op32_||||||||||||||||||||||||_~26dB
2019-11-24 03:30:13 K3RWR FM18QI K3SIW-1 EN52TA 1.077 136 -22 Op32_||||||||||||||||||||||||||||||||_~22dB
2019-11-24 02:57:27 K3RWR FM18QI K3SIW-1 EN52TA 1.077 136 -16 Op32_||||||||||||||||||||||||||||||||||||||||||||_~16dB
2019-11-24 02:24:40 K3RWR FM18QI K3SIW-1 EN52TA 1.077 136 -15 Op32_||||||||||||||||||||||||||||||||||||||||||||||_~15dB
2019-11-24 01:51:54 K3RWR FM18QI K3SIW-1 EN52TA 1.077 136 -13 Op32_||||||||||||||||||||||||||||||||||||||||||||||||||_~13dB
2019-11-24 01:19:07 K3RWR AA K3SIW-1 EN52TA 0 136 -15 Op32_||||||||||||||||||||||||||||||||||||||||||||||_~15dB
2019-11-24 00:46:21 K3RWR FM18QI K3SIW-1 EN52TA 1.077 136 -17 Op32_||||||||||||||||||||||||||||||||||||||||||_~17dB
2019-11-24 00:13:34 K3RWR FM18QI K3SIW-1 EN52TA 1.077 136 -22 Op32_||||||||||||||||||||||||||||||||_~22dB
2019-11-23 23:40:48 K3RWR FM18QI K3SIW-1 EN52TA 1.077 136 -22 Op32_||||||||||||||||||||||||||||||||_~2
 
 

2019-11-24 07:52:25 K3RWR FM18QI W3BRB EM93TE 667 136 -38 Op32__~38dB
*
2019-11-24 04:35:49 K3RWR FM18QI W3BRB EM93TE 667 136 -45 Op32__~45dB
*
2019-11-24 03:30:15 K3RWR FM18QI W3BRB EM93TE 667 136 -45 Op32__~45dB
**>
2019-11-24 01:51:56 K3RWR FM18QI W3BRB EM93TE 667 136 -44 Op32__~44dB
*
2019-11-23 11:10:48 K3RWR FM18QI W3BRB EM93TE 667 136 -43 Op32__~43dB




Re: #opera Icom 7610 CAT and Opera ? #opera

Andrew OBrien
 

By trial and error I discovered Opera expects a C-IV USB baud rate of 19200.  My 7610 and Opera are now communicating. 

Andy K3UK


Re: K3RWR TX ON 136/OP32 1 WATT #opera

Andrew OBrien
 

I'll give a listen  for all on that freq now that trans-Atlantic Long Wave season is upon us.

Andy K3UK


#opera Icom 7610 CAT and Opera ? #opera

Andrew OBrien
 

I see that the Opera software says "audio by the Rear Connector" .  I don't  use the rear connector .  With other software I just use the sound chip (audio codec) in the Icom.  Also if I choose the Icom 7610 from Jose's drop-down list, the scan does not find the radio.  I do not see anywhere in Opera to double check the CI-V address or change a baud rate.  
Andy K3UK


Re: FT8 in MixW 4

Andrew OBrien
 

But I don't see RSID in Mixw4.  
Andy


K3RWR TX ON 136/OP32 1 WATT #opera

Graham
 

New Opera  TX station  on 136 KHz 

K3RWR  TX ON 136/OP32 1 WATT

Bob reports, running  1  watt  erp ,  showing  good  signal to west 
in land  , during  daylight , should  cross  pond  to  uk/eu 

Follow  progress   at   http://spots.microwavers.es/index.php

73-Graham
g0nbd


Re: FT8 in MixW 4

Andrew OBrien
 

I am VERY late in evaluating MixW4 but looking at it for the first time today , the GUI is very nice and FT8 integration looks good.
Andy K3UK

541 - 560 of 51560