12. mai 2025 kl.?00:18 skrev thomas.fruehwald via groups.io <thomas.fruehwald@...>:

?

Hi Barry,

?

?

Here is the location.

?

/g/nodered-hamradio/files/%211%21%20Flows%20by%20Type/ROTORS/4O3A_Azimuth_Magnetic_Sensor.json

?

vy 73?

Tom DL5NEN

On 4 May 2025, at 15:03, Scott Dupuie via groups.io <groupsio@...> wrote:

?

I am pleased to release a major upgrade to my Solar weather flow -- Solar 2.0.

?

On the surface, it doesn't look all that different than the 1.x flow, but under the hood it has been completely rewritten from the ground up. There are numerous enhancements, but the star of the show is that you no longer have to average the data from nearby ionosondes to get an estimate of MUF and foF2 for your QTH. Instead, I am now doing a direct lookup of MUF and foF2 for your QTH based on the sophisticated interpolation that Andrew Rodland, KC2G, is doing on his excellent web site . I reached out to Roland a couple of months back and he graciously agreed to make an API available that will take your latitude and longitude (or Maidenhead grid) and return an estimate of MUF and foF2 for that location. This is much more robust because it does not rely on nearby ionosondes being active to do the estimate and Roland's interpolation routine is more sophisticated that what I was doing. This API works anywhere on the planet and does not require you to maintain a list of ionosondes. Thanks to Roland for this excellent resource. Keep in mind that the MUF you will see is directly overhead at your location, not necessarily the MUF along a path between you and a distance station.

Since we no longer need to display the status of nearby ionosonde's, I repurposed that space for displaying recent X-ray flux data in the form of peak solar flare intensity over the past 24 hours (left number) and 2 hours (right number). In the screenshot shown, the maximum flare in the past 2 hours was a C5.4 classification. This was also the largest flare in the past 24 hours, so the two numbers are the same in this example. The solar flare classifications and the color scheme I am using throughout the flow can be found here:

I have updated all of the readings (other than MUF and foF2) so that they now pull data from NOAA instead of 3rd-party sources. All of the displays have been modified such that the color scheme and thresholds match NOAA standards (as best as I could determine). The space weather conditions R, S, and G (as defined in the link above) have also been rewritten, particularly what is displayed ?for the "Predicted" values. This one has always been tough, since the NOAA does not predict precise values for R and S, instead giving a range of probabilities. This is difficult to display in the space allotted. In the new flow, I do a better job of representing this information. The display for predicted R can be R0, R1/2, R2/3, or R3/5. For example, if R1/2 is displayed that means the most likely peak R value in the next 24 hours will be R1 or R2. NOAA provides less granularity for the S prediction so the two possible values are S0 or S1/+, the latter meaning that the most probably S value in the next 24 hours will be S1 or above. For both R and S predicted values, the display is further color coded to represent the expected intensity.

?

The headings for all of the fields (except for the gauges) are clickable and will take you to a web site with more information about that measurement.

?

As always, check out the README node for information about how to use the flow. In particular, you have to set up some environment variables with your latitude and longitude, otherwise you will be getting the MUF and foF2 for my location instead of yours. If you don't want the header "Solar Conditions", just delete the Solar Title node. This flow was developed and tested with Node-RED 4.0.2, but it should work fine with 3.x.

?

73,

Scott

AK5SD

?

<Solar 2.0.png>

<Solar 2.0.json>

On May 4, 2025, at 10:03, Scott Dupuie <groupsio@...> wrote:

I am pleased to release a major upgrade to my Solar weather flow -- Solar 2.0.

?

On the surface, it doesn't look all that different than the 1.x flow, but under the hood it has been completely rewritten from the ground up. There are numerous enhancements, but the star of the show is that you no longer have to average the data from nearby ionosondes to get an estimate of MUF and foF2 for your QTH. Instead, I am now doing a direct lookup of MUF and foF2 for your QTH based on the sophisticated interpolation that Andrew Rodland, KC2G, is doing on his excellent web site . I reached out to Roland a couple of months back and he graciously agreed to make an API available that will take your latitude and longitude (or Maidenhead grid) and return an estimate of MUF and foF2 for that location. This is much more robust because it does not rely on nearby ionosondes being active to do the estimate and Roland's interpolation routine is more sophisticated that what I was doing. This API works anywhere on the planet and does not require you to maintain a list of ionosondes. Thanks to Roland for this excellent resource. Keep in mind that the MUF you will see is directly overhead at your location, not necessarily the MUF along a path between you and a distance station.

Since we no longer need to display the status of nearby ionosonde's, I repurposed that space for displaying recent X-ray flux data in the form of peak solar flare intensity over the past 24 hours (left number) and 2 hours (right number). In the screenshot shown, the maximum flare in the past 2 hours was a C5.4 classification. This was also the largest flare in the past 24 hours, so the two numbers are the same in this example. The solar flare classifications and the color scheme I am using throughout the flow can be found here:

I have updated all of the readings (other than MUF and foF2) so that they now pull data from NOAA instead of 3rd-party sources. All of the displays have been modified such that the color scheme and thresholds match NOAA standards (as best as I could determine). The space weather conditions R, S, and G (as defined in the link above) have also been rewritten, particularly what is displayed ?for the "Predicted" values. This one has always been tough, since the NOAA does not predict precise values for R and S, instead giving a range of probabilities. This is difficult to display in the space allotted. In the new flow, I do a better job of representing this information. The display for predicted R can be R0, R1/2, R2/3, or R3/5. For example, if R1/2 is displayed that means the most likely peak R value in the next 24 hours will be R1 or R2. NOAA provides less granularity for the S prediction so the two possible values are S0 or S1/+, the latter meaning that the most probably S value in the next 24 hours will be S1 or above. For both R and S predicted values, the display is further color coded to represent the expected intensity.

?

The headings for all of the fields (except for the gauges) are clickable and will take you to a web site with more information about that measurement.

?

As always, check out the README node for information about how to use the flow. In particular, you have to set up some environment variables with your latitude and longitude, otherwise you will be getting the MUF and foF2 for my location instead of yours. If you don't want the header "Solar Conditions", just delete the Solar Title node. This flow was developed and tested with Node-RED 4.0.2, but it should work fine with 3.x.

?

73,

Scott

AK5SD

?

<Solar 2.0.png>

<Solar 2.0.json>

On May 6, 2025, at 12:20?PM, Tim Vandagriff via groups.io <wa5yom@...> wrote:

?

Dave, Alan,

?

Where are your flows that incorporate the SteppIR functions?

?

I havn't been able to locate them.

?

Thanks,

Tim

wa5yom

On May 3, 2025, at 10:32?AM, Alan Blind, WA9WUD via groups.io <a.alan.blind@...> wrote:

?

Tim

?

For the lower DB9, FRStack connection, be sure you are using a null modem cable. ?

?

Are you running FRStack on a windows PC?

?

Alan. WA9WUD