So having put my station back online after month of being used for SSB and FT4 I’ve noticed it’s being abused again for the same reason as last time. I’ve set the Minimum Horizon to 10deg for a reason and it appears that people can just over ride it and do as they want. This is NOT acceptable and could lead to damage of my rotor system and Antennas. How do i stop these people from violating the Minimum Horizon Setting of 10deg.
Thanks
Karl.
Hi Karl,
For now place it in testing to make sure others won’t damage your system.
Jan | PE0SAT
It seems the request to set the hard limits to match the stations Minimum Horizon was ignored and removed. Is there a reason for this ?
The minimum horizon setting is not a hard limit but a suggestion for more successful observations, and was set also to help not to waste observation time. Everyone can bypass it when scheduling in advanced settings.
Personally I bypass it when we have new deployments or when hunting re-entries given that the TLE are not fully accurate and sometimes in special events (like the recent SSTV event) that we know that there is a strong transmission that could work lower than the limits.
However I see some increased interest for using this as a hard limit, so I think it’s a good time to add another setting, like a checkbox, that will set, or not, this value as a hard limit.
@ve6kdx I’m really sorry if I caused any trouble to your station setup, I’m going to have it in mind when scheduling and I’ll take care to add this “hard limit” option as soon as possible.
Thanks for pointing to this, to be honest, I forgot it was there. It isn’t removed, it is just stay open and unimplemented, I guess due to other priorities and low development resources.
As I said on my previous post, I’ll make sure that it will be prioritized!
Thank you again for the Info Fredy and i didn’t single you out just your observation was the first observation i came across.
I have a Large Yagi above and Wire Antenna that’s in very close proximity under the UHF and VHF Yagi so it has been know to clash in the past.
Karl.
Thanks for clarification. But I must admit, that this does not match the expectations of users at all, as shown by several issues in gitlab and threads here. Users obviously expect a hard limit here. The UI does not imply the character of a “suggestion”, like it does e.g. by the utilisation target.
That is a good point to maybe be less strict about restrictions. Otherwise, station-owners certainly know best, what will work on their stations and what will not. At least I can tell this really precise for the stations I maintain.
To make a suggestion: Maybe enforcing a minimum culmination for observations would be an good idea.
In my opinion, overriding the settings on stations one can not profoundly know is a difficult topic! What, if such an action actually will break things? #1 already mentioned this.
I’d rather prefer to adjust the networks behaviour actually to that, what its user-interface implies. This would hold it cleaner, than adding an additional option.
Additionally, but that might be my personal view, enforcing standards should be opt-out. Not opt-in.
I agree there should be an option to set a hard limit for the minimum horizon. At my location I have the minimum value set to 60, anything to the south and west of that will not be heard on account of nearby hills. It’s just a waste of storage and my time vetting.
I’ve updated the related issues in order to start working on them:
A quick summary, min horizon will show (with hard or soft limit) from which elevation the observation will start and min culmination will show (with hard or soft limit) the minimum max elevation needed for the observation to be scheduled.
An example with min horizon set to 10 and min culmination set to 25:
| Observation Max Elevation | Hard Min Horizon | Hard Min Culmination | Hard Min Horizon | Soft Min Culmination (overridden, not used) | Soft Min Horizon (overridden, set to 0) | Hard Min Culmination | Soft Min Horizon (overridden, set to 0) | Soft Min Culmination (overridden, not used) |
|---|---|---|---|---|
| 15 degrees | Not scheduled, min culmination hard limit is hit (15 < 25) | Scheduled, starts from 10 degrees (min horizon hard limit) up to 15 degrees and back to 10 degrees (min horizon hard limit) | Not scheduled, min culmination hard limit is hit (15 < 25) | Scheduled, starts from 0 degrees up to 15 degrees and back to 0 degrees |
| 30 degrees | Scheduled, starts from 10 degrees (min horizon hard limit) up to 30 degrees and back to 10 degrees (min horizon hard limit) | Scheduled, starts from 10 degrees (min horizon hard limit) up to 30 degrees and back to 10 degrees (min horizon hard limit) | Scheduled, starts from 0 degrees up to 30 degrees and back to 0 degrees | Scheduled, starts from 0 degrees up to 30 degrees and back to 0 degrees |
