Date
1 - 20 of 54
WB6YRW/6 TX beacon service for FST4W listeners
Stuart Ogawa
past 12 hours
fst4w 15m
mode = 5
from San Jose, CA
4 watts
vertical
------------
past 12 hours
------------
past 12 hours
wspr 15m
mode = 2
from San Jose, CA
200 milliwatts
sky loop
--------
past 12 hours
--------
past 12 hours
wspr 80 to 6m
mode = 2
from San Jose, CA
200 milliwatts
sky loop
--------------
--------------
02:48 UTC / 7:48 AM PST
Begin FST4W 40m tx beacon
mode = 5
from San Jose, CA
4 watts
antenna = big sky loop
admin
Hello,
the wspr.live mode watch dashboard has been updated to give detailed insight into station activity on the new modes.
https://wspr.live/gui/d/vhwRxD67z/wspr-mode-watch
Regards
toggle quoted message
Show quoted text
the wspr.live mode watch dashboard has been updated to give detailed insight into station activity on the new modes.
https://wspr.live/gui/d/vhwRxD67z/wspr-mode-watch
Regards
On 07.07.22 17:11, Stuart Ogawa wrote:
Hi John,
http://wspr.rocks/
-------------
past 14 hours
fst4w 80m
mode = 5
from San Jose, CA
4 watts
vertical
Screen Shot 2022-07-07 at 7.52.21 AM.png
------------
past 14 hours
wspr 80m
mode = 2
from San Jose, CA
200 milliwatts
sky loop
Screen Shot 2022-07-07 at 7.53.11 AM.png
--------
past 14 hours
wspr 80m to 6m
mode = 2
from San Jose, CA
200 milliwatts
sky loop
Screen Shot 2022-07-07 at 7.53.41 AM.png
---------
On a go forward basis, I will swap in one of two sky loops for fst4w 80m and 40m and notate this in the abstract (e.g. vertical, big sky loop, small sky loop)
* big sky loop = 160 to 10m 522 foot length; this antenna tx skews generously throughout the Pacific Rim and Antarctica and intermittently to EU; almost no LatAm
* small sky loop = 80 to 10m 220 foot length; this antenna tx skews Aus, NZ, Northern Europe, and Africa
Last night propagation, as displayed in last screen capture above, was very good tx prop 80 to 10m from my location. Only 2 other times since I have began experimenting with WSPR did my location cover all continents in this short time frame using 200 milliwatts
--------
14:55 UTC / 7:55AM PST
Begin FST4W 15m tx beacon
mode = 5
from San Jose, CA
4 watts
vertical
On Thu, Jul 7, 2022 at 7:22 AM John via groups.io <http://groups.io> <n0ure@...> wrote:
Stuart, what do you use to produce these reports. Would you share any code you use?
Thanks much.
John
TI4JWC
El miércoles, 6 de julio de 2022, 06:05:07 p. m. CST, Stuart Ogawa <stuartogawa@...> escribió:
past 9 hours
fst4w 20m
mode = 5
from San Jose, CA
4 watts
vertical
Screen Shot 2022-07-06 at 4.56.34 PM.png
----------------
past 9 hours
wspr 20m
mode = 2
from San Jose, CA
200 milliwatts
sky loop
Screen Shot 2022-07-06 at 4.57.12 PM.png
-------------
past 9 hours
wspr 80 to 10m
mode = 2
from San Jose, CA
200 milliwatts
sky loop
Screen Shot 2022-07-06 at 5.00.42 PM.png
-----------
00:03 UTC / 5:03 PST
begin fst4w 80m tx
mode = 5
from San Jose, CA
4 watts
vertical
On Wed, Jul 6, 2022 at 8:07 AM Stuart Ogawa via groups.io <http://groups.io> <stuartogawa@...> wrote:
encountered issue with call sign W6YR
needed to switch to another temp call sign ---> K6TR
summary WB6YRW/6 ----> K6TR for the San Jose, Ca FST4W tx beacon service
----------
past 8 hours
fst4w 40m
mode = 5
from San Jose, CA
4 watts
vertical
Screen Shot 2022-07-06 at 8.02.14 AM.png
--------
past 8 hours
wspr 40m
mode = 2
from San Jose, CA
200 milliwatts
sky loop
Screen Shot 2022-07-06 at 8.03.10 AM.png
Stuart Ogawa
Hi John,
-------------
past 14 hours
fst4w 80m
mode = 5
from San Jose, CA
4 watts
vertical
------------
past 14 hours
wspr 80m
mode = 2
from San Jose, CA
200 milliwatts
sky loop
--------
past 14 hours
wspr 80m to 6m
mode = 2
from San Jose, CA
200 milliwatts
sky loop
---------
On a go forward basis, I will swap in one of two sky loops for fst4w 80m and 40m and notate this in the abstract (e.g. vertical, big sky loop, small sky loop)
* big sky loop = 160 to 10m 522 foot length; this antenna tx skews generously throughout the Pacific Rim and Antarctica and intermittently to EU; almost no LatAm
* small sky loop = 80 to 10m 220 foot length; this antenna tx skews Aus, NZ, Northern Europe, and Africa
Last night propagation, as displayed in last screen capture above, was very good tx prop 80 to 10m from my location. Only 2 other times since I have began experimenting with WSPR did my location cover all continents in this short time frame using 200 milliwatts
--------
14:55 UTC / 7:55AM PST
Begin FST4W 15m tx beacon
mode = 5
from San Jose, CA
4 watts
vertical
Stuart, what do you use to produce these reports. Would you share any code you use?Thanks much.JohnTI4JWCEl miércoles, 6 de julio de 2022, 06:05:07 p. m. CST, Stuart Ogawa <stuartogawa@...> escribió:past 9 hoursfst4w 20mmode = 5from San Jose, CA4 wattsvertical----------------past 9 hourswspr 20mmode = 2from San Jose, CA200 milliwattssky loop-------------past 9 hourswspr 80 to 10mmode = 2from San Jose, CA200 milliwattssky loop-----------00:03 UTC / 5:03 PSTbegin fst4w 80m txmode = 5from San Jose, CA4 wattsverticalencountered issue with call sign W6YRneeded to switch to another temp call sign ---> K6TRsummary WB6YRW/6 ----> K6TR for the San Jose, Ca FST4W tx beacon service----------past 8 hoursfst4w 40mmode = 5from San Jose, CA4 wattsvertical--------past 8 hourswspr 40mmode = 2from San Jose, CA200 milliwattssky loop
John
Stuart, what do you use to produce these reports. Would you share any code you use?
Thanks much.
John
TI4JWC
El miércoles, 6 de julio de 2022, 06:05:07 p. m. CST, Stuart Ogawa <stuartogawa@...> escribió:
past 9 hours
fst4w 20m
mode = 5
from San Jose, CA
4 watts
vertical
----------------
past 9 hours
wspr 20m
mode = 2
from San Jose, CA
200 milliwatts
sky loop
-------------
past 9 hours
wspr 80 to 10m
mode = 2
from San Jose, CA
200 milliwatts
sky loop
-----------
00:03 UTC / 5:03 PST
begin fst4w 80m tx
mode = 5
from San Jose, CA
4 watts
vertical
encountered issue with call sign W6YRneeded to switch to another temp call sign ---> K6TRsummary WB6YRW/6 ----> K6TR for the San Jose, Ca FST4W tx beacon service----------past 8 hoursfst4w 40mmode = 5from San Jose, CA4 wattsvertical--------past 8 hourswspr 40mmode = 2from San Jose, CA200 milliwattssky loop
Stuart Ogawa
past 9 hours
fst4w 20m
mode = 5
from San Jose, CA
4 watts
vertical
----------------
past 9 hours
wspr 20m
mode = 2
from San Jose, CA
200 milliwatts
sky loop
-------------
past 9 hours
wspr 80 to 10m
mode = 2
from San Jose, CA
200 milliwatts
sky loop
-----------
00:03 UTC / 5:03 PST
begin fst4w 80m tx
mode = 5
from San Jose, CA
4 watts
vertical
encountered issue with call sign W6YRneeded to switch to another temp call sign ---> K6TRsummary WB6YRW/6 ----> K6TR for the San Jose, Ca FST4W tx beacon service----------past 8 hoursfst4w 40mmode = 5from San Jose, CA4 wattsvertical--------past 8 hourswspr 40mmode = 2from San Jose, CA200 milliwattssky loop
Rob Robinett
Does mode = 5 mean you are sending FST4W-300 packets?
On Wed, Jul 6, 2022 at 8:11 AM Stuart Ogawa <stuartogawa@...> wrote:
15;00 UTC / 8AM PSTbegin fst4w 20m tx beaconmode = 5On Wed, Jul 6, 2022 at 8:07 AM Stuart Ogawa <stuartogawa@...> wrote:encountered issue with call sign W6YRneeded to switch to another temp call sign ---> K6TRsummary WB6YRW/6 ----> K6TR for the San Jose, Ca FST4W tx beacon service----------past 8 hoursfst4w 40mmode = 5from San Jose, CA4 wattsvertical--------past 8 hourswspr 40mmode = 2from San Jose, CA200 milliwattssky loop
--
Stuart Ogawa
15;00 UTC / 8AM PST
begin fst4w 20m tx beacon
mode = 5
On Wed, Jul 6, 2022 at 8:07 AM Stuart Ogawa <stuartogawa@...> wrote:
encountered issue with call sign W6YRneeded to switch to another temp call sign ---> K6TRsummary WB6YRW/6 ----> K6TR for the San Jose, Ca FST4W tx beacon service----------past 8 hoursfst4w 40mmode = 5from San Jose, CA4 wattsvertical--------past 8 hourswspr 40mmode = 2from San Jose, CA200 milliwattssky loop
Stuart Ogawa
encountered issue with call sign W6YR
needed to switch to another temp call sign ---> K6TR
summary WB6YRW/6 ----> K6TR for the San Jose, Ca FST4W tx beacon service
----------
past 8 hours
fst4w 40m
mode = 5
from San Jose, CA
4 watts
vertical
--------
past 8 hours
wspr 40m
mode = 2
from San Jose, CA
200 milliwatts
sky loop
Stuart Ogawa
@ tom....my bad....screen grabbed the wrong area of pref freq table:
correct version below
past 10.5 hoursfst4w 15mmode = 5from San Jose, CA4 wattsvertical----------past 10.5 hourswspr 15mmode = 2from San Jose, CA200 milliwattssky loop-----------begin 01:20 utc / 6:20pm pstfst4w 40mmode = 5from San Jose, CA4 wattsverticalOn Tue, Jul 5, 2022 at 6:30 PM WA2TP - Tom <myis300@...> wrote:Ever since I enabled all 4w modes 40 and up, decode performance has suffered.I have removed 4w modes from 40 and up.
On Jul 5, 2022, at 9:27 PM, Stuart Ogawa <stuartogawa@...> wrote:
@ tom, glenn, and rob,
the following screen capture is the error message i receive when attempting to tx fst4w on 30m
-------
the following screen capture is the preferences table
----------
the following screen capture is the wsjt x version i am running on mac mini m1 with 16 gigs of ram. (i was using the most recent mac distribution version (2.5.4), but there were comments on wsjtx groups that lead me to believe 2.5.4 may not be stable and 2.5.2 was the last known stable mac version)
maybe i am doing something wrong on this fst4w 30m band?
at least for now, i cannot transmit using fst4w 30m for you listeners.
running some more workaround experiments tonight
On Tue, Jul 5, 2022 at 4:00 PM WA2TP - Tom <myis300@...> wrote:
This is what core utilization and temps look like as of now, with all enabled on 64rx. I am not utilizing a whole lot of CPU time. Each of these three cycles included a minimum of 225 spots to decode/ 2-minute cycle.
Stuart Ogawa
past 10.5 hours
fst4w 15m
mode = 5
from San Jose, CA
4 watts
vertical
----------
past 10.5 hours
wspr 15m
mode = 2
from San Jose, CA
200 milliwatts
sky loop
-----------
begin 01:20 utc / 6:20pm pst
fst4w 40m
mode = 5
from San Jose, CA
4 watts
vertical
On Tue, Jul 5, 2022 at 6:30 PM WA2TP - Tom <myis300@...> wrote:
Ever since I enabled all 4w modes 40 and up, decode performance has suffered.I have removed 4w modes from 40 and up.
On Jul 5, 2022, at 9:27 PM, Stuart Ogawa <stuartogawa@...> wrote:
@ tom, glenn, and rob,
the following screen capture is the error message i receive when attempting to tx fst4w on 30m
-------
the following screen capture is the preferences table
----------
the following screen capture is the wsjt x version i am running on mac mini m1 with 16 gigs of ram. (i was using the most recent mac distribution version (2.5.4), but there were comments on wsjtx groups that lead me to believe 2.5.4 may not be stable and 2.5.2 was the last known stable mac version)
maybe i am doing something wrong on this fst4w 30m band?
at least for now, i cannot transmit using fst4w 30m for you listeners.
running some more workaround experiments tonight
On Tue, Jul 5, 2022 at 4:00 PM WA2TP - Tom <myis300@...> wrote:
This is what core utilization and temps look like as of now, with all enabled on 64rx. I am not utilizing a whole lot of CPU time. Each of these three cycles included a minimum of 225 spots to decode/ 2-minute cycle.
Glenn Elmore
What mode does the table state for 30m?
Make sure its 'all' and not 'wspr'
On Jul 5, 2022 7:27 PM, Stuart Ogawa <stuartogawa@...> wrote:
@ tom, glenn, and rob,the following screen capture is the error message i receive when attempting to tx fst4w on 30m-------the following screen capture is the preferences table----------the following screen capture is the wsjt x version i am running on mac mini m1 with 16 gigs of ram. (i was using the most recent mac distribution version (2.5.4), but there were comments on wsjtx groups that lead me to believe 2.5.4 may not be stable and 2.5.2 was the last known stable mac version)maybe i am doing something wrong on this fst4w 30m band?at least for now, i cannot transmit using fst4w 30m for you listeners.running some more workaround experiments tonightOn Tue, Jul 5, 2022 at 4:00 PM WA2TP - Tom <myis300@...> wrote:This is what core utilization and temps look like as of now, with all enabled on 64rx. I am not utilizing a whole lot of CPU time. Each of these three cycles included a minimum of 225 spots to decode/ 2-minute cycle.
WA2TP - Tom
Ever since I enabled all 4w modes 40 and up, decode performance has suffered.
I have removed 4w modes from 40 and up.
On Jul 5, 2022, at 9:27 PM, Stuart Ogawa <stuartogawa@...> wrote:
@ tom, glenn, and rob,
the following screen capture is the error message i receive when attempting to tx fst4w on 30m
-------
the following screen capture is the preferences table
----------
the following screen capture is the wsjt x version i am running on mac mini m1 with 16 gigs of ram. (i was using the most recent mac distribution version (2.5.4), but there were comments on wsjtx groups that lead me to believe 2.5.4 may not be stable and 2.5.2 was the last known stable mac version)
maybe i am doing something wrong on this fst4w 30m band?
at least for now, i cannot transmit using fst4w 30m for you listeners.
running some more workaround experiments tonight
On Tue, Jul 5, 2022 at 4:00 PM WA2TP - Tom <myis300@...> wrote:
This is what core utilization and temps look like as of now, with all enabled on 64rx. I am not utilizing a whole lot of CPU time. Each of these three cycles included a minimum of 225 spots to decode/ 2-minute cycle.
Stuart Ogawa
@ tom, glenn, and rob,
the following screen capture is the error message i receive when attempting to tx fst4w on 30m
-------
the following screen capture is the preferences table
----------
the following screen capture is the wsjt x version i am running on mac mini m1 with 16 gigs of ram. (i was using the most recent mac distribution version (2.5.4), but there were comments on wsjtx groups that lead me to believe 2.5.4 may not be stable and 2.5.2 was the last known stable mac version)
maybe i am doing something wrong on this fst4w 30m band?
at least for now, i cannot transmit using fst4w 30m for you listeners.
running some more workaround experiments tonight
On Tue, Jul 5, 2022 at 4:00 PM WA2TP - Tom <myis300@...> wrote:
This is what core utilization and temps look like as of now, with all enabled on 64rx. I am not utilizing a whole lot of CPU time. Each of these three cycles included a minimum of 225 spots to decode/ 2-minute cycle.
Glenn Elmore
Stu,
I can't remember but I think I have. But I've upgraded to
WSJT-Xv2.5.4 since then so things may have changed. I did set
14.095600 dial to be correct for all modes in the
settings:frequency tab though so I can't see why changing mode in
FST4W would matter, though it needs to be tested. I am getting the
impression that FST4W has not been extensively tested by the
developers, both in terms of stability and function in corner
cases.
I'm presently transmitting mode15 and will be dropping power to get down to a level that is harder for spotters and that would not produce spots with WSPR2. I just dropped it to 1W but will continue as far as necessary in order to see some -30's if possible.
If that is successful and I see some ~-34 or lower reports I'll
try Mode30. I may continue to drop power way down to see what
my remote receiver does. That 12 mile path is very stable and I'll
probably have to drop 60 dB, to below 1 microwatt, to test it but
I have attenuators and power measurement equipment so this
shouldn't be a problem. At that level I wouldn't expect any other
spots though 10 dB above that level I might get a few. In the
past 1 mW has generated several with WSPR2.
On 7/5/22 11:27, Stuart Ogawa wrote:
glenn,
have you successfully tx'ed wsjt x fst4w on 30m?
i receive an error message.
i am at work and cannot remote access / screen grab that wsjt x fst4w user error message.
content was something like 'wsjt x will not knowingly transmit on a wspr frequency
i checked the preferences/frequency table for 30m fstw4...standard default setup
On Tue, Jul 5, 2022 at 10:20 AM WA2TP - Tom <myis300@...> wrote:
Will you be moving to mode 30 on 40 and up?
I am currently only set for mode 30 on all below 40.
I can add -30 to upper bands, just let me know.
> On Jul 5, 2022, at 1:03 PM, Glenn Elmore <n6gn@...> wrote:
>
>
> Since 1500 UTC today, July 5, I am transmitting mode15 on 14.097005 with transmitter ID N6GN/F.
>
> Both Stu, WB6YRW, and I have had some problems keeping WSJT-X running properly for longer periods so it's possible there will be quiet times in my transmission (again). I'll do my best to keep it running this way for a while and then perhaps move to Mode30. I'm interested to see if the longer modes show clear benefit for very weak conditions as we hope. I may include a parallel WSPR2 transmission on 14.097195 again as reference.
>
> Until Rob gets a fix into wsprdaemon.sh code and distributed only WSJT-X decoders will properly report the mode. but my FST4W transmissions continue to be identifiable by the TX ID and frequency.
>
> For those that can and are interested, maintaining a receiver for 20m mode15 will help provide us all with more results.
>
> Glenn n6gn
>
>
>
>
>
>
Glenn Elmore
No, since same actual frequency can be obtained with many different dials by adjusting tx audio to be something different from [1500] Hz. I always mean actual transmitted band center for the mode which is what is reported by the by the databases.
Glenn n6gn
toggle quoted message
Show quoted text
Glenn n6gn
On 7/5/22 12:45, KD2OM wrote:
Glen,
When you say 14.097005, is that dial?
Steve KD2OM
Sent from my iPhone.
On Jul 5, 2022, at 13:03, Glenn Elmore <n6gn@...> wrote:
Since 1500 UTC today, July 5, I am transmitting mode15 on 14.097005 with transmitter ID N6GN/F.
Both Stu, WB6YRW, and I have had some problems keeping WSJT-X running properly for longer periods so it's possible there will be quiet times in my transmission (again). I'll do my best to keep it running this way for a while and then perhaps move to Mode30. I'm interested to see if the longer modes show clear benefit for very weak conditions as we hope. I may include a parallel WSPR2 transmission on 14.097195 again as reference.
Until Rob gets a fix into wsprdaemon.sh code and distributed only WSJT-X decoders will properly report the mode. but my FST4W transmissions continue to be identifiable by the TX ID and frequency.
For those that can and are interested, maintaining a receiver for 20m mode15 will help provide us all with more results.
Glenn n6gn
Stuart Ogawa
@ tom, short answer is yes.
the plan is to fst4w beacon tx the 80 to 10m bands from my location
without the wsjt x band hopper feature, i will manually change bands = high hf bands during the day and low hf bands during the night...for now
30m wsjt x transmit fst4w i think has an issue/bug...i am performing some workaround tests...but all other fst4w bands will broadcasted.
once i have the qrp qdx exciters and two dell workstations operational, then i will be able to beacon tx 3 bands simultaneously.
On Tue, Jul 5, 2022 at 11:46 AM KD2OM <steve@...> wrote:
Glen,
When you say 14.097005, is that dial?
Steve KD2OM
.
> On Jul 5, 2022, at 13:03, Glenn Elmore <n6gn@...> wrote:
>
>
> Since 1500 UTC today, July 5, I am transmitting mode15 on 14.097005 with transmitter ID N6GN/F.
>
> Both Stu, WB6YRW, and I have had some problems keeping WSJT-X running properly for longer periods so it's possible there will be quiet times in my transmission (again). I'll do my best to keep it running this way for a while and then perhaps move to Mode30. I'm interested to see if the longer modes show clear benefit for very weak conditions as we hope. I may include a parallel WSPR2 transmission on 14.097195 again as reference.
>
> Until Rob gets a fix into wsprdaemon.sh code and distributed only WSJT-X decoders will properly report the mode. but my FST4W transmissions continue to be identifiable by the TX ID and frequency.
>
> For those that can and are interested, maintaining a receiver for 20m mode15 will help provide us all with more results.
>
> Glenn n6gn
>
>
>
>
>
>
Glen,
When you say 14.097005, is that dial?
Steve KD2OM
Sent from my iPhone.
toggle quoted message
Show quoted text
When you say 14.097005, is that dial?
Steve KD2OM
Sent from my iPhone.
On Jul 5, 2022, at 13:03, Glenn Elmore <n6gn@...> wrote:
Since 1500 UTC today, July 5, I am transmitting mode15 on 14.097005 with transmitter ID N6GN/F.
Both Stu, WB6YRW, and I have had some problems keeping WSJT-X running properly for longer periods so it's possible there will be quiet times in my transmission (again). I'll do my best to keep it running this way for a while and then perhaps move to Mode30. I'm interested to see if the longer modes show clear benefit for very weak conditions as we hope. I may include a parallel WSPR2 transmission on 14.097195 again as reference.
Until Rob gets a fix into wsprdaemon.sh code and distributed only WSJT-X decoders will properly report the mode. but my FST4W transmissions continue to be identifiable by the TX ID and frequency.
For those that can and are interested, maintaining a receiver for 20m mode15 will help provide us all with more results.
Glenn n6gn
Stuart Ogawa
glenn,
have you successfully tx'ed wsjt x fst4w on 30m?
i receive an error message.
i am at work and cannot remote access / screen grab that wsjt x fst4w user error message.
content was something like 'wsjt x will not knowingly transmit on a wspr frequency
i checked the preferences/frequency table for 30m fstw4...standard default setup
On Tue, Jul 5, 2022 at 10:20 AM WA2TP - Tom <myis300@...> wrote:
Will you be moving to mode 30 on 40 and up?
I am currently only set for mode 30 on all below 40.
I can add -30 to upper bands, just let me know.
> On Jul 5, 2022, at 1:03 PM, Glenn Elmore <n6gn@...> wrote:
>
>
> Since 1500 UTC today, July 5, I am transmitting mode15 on 14.097005 with transmitter ID N6GN/F.
>
> Both Stu, WB6YRW, and I have had some problems keeping WSJT-X running properly for longer periods so it's possible there will be quiet times in my transmission (again). I'll do my best to keep it running this way for a while and then perhaps move to Mode30. I'm interested to see if the longer modes show clear benefit for very weak conditions as we hope. I may include a parallel WSPR2 transmission on 14.097195 again as reference.
>
> Until Rob gets a fix into wsprdaemon.sh code and distributed only WSJT-X decoders will properly report the mode. but my FST4W transmissions continue to be identifiable by the TX ID and frequency.
>
> For those that can and are interested, maintaining a receiver for 20m mode15 will help provide us all with more results.
>
> Glenn n6gn
>
>
>
>
>
>