Eric Tweet
Active Member
Either I'm missing something significant, or I've discovered an ugly bug relating to antenna profiles.
Here's the story:
- I have some profiles set up for my metric rod, along with appropriate vertical offsets. For example, a profile for the 2-meter setting on my Seco. I created it by entering the height using the Meters units (entered as 2.0 meters), and measured the actual rod height, yielding a difference of 0.056m. That gets entered into my vertical offset, still using the Meters units.
- My project is in USft, so when I save the profile, I see the readings as: 6.5617' with vertical offset of 0.1837'. Great! I've used and checked all my profiles in multiple projects and they work fine.
Now for the confusing bit...
- I have the need to use a different rod for a while, so I make a new profile for it like normal. Again measured and entered in metric, and auto-converted to feet. Let's call it 1.4 meters height with no offset.
- Somewhere during that process of making a new profile, the bug occurs.
The Bug:
Upon saving the profile for the new rod, my profile for the 2-meter Seco rod has been mysteriously changed and now reads: 2.0 FEET, with 0.1837-foot vertical offset. While the newly created profile shows up correctly as 4.5932 feet.
Somehow, J-field has "forgotten" the units in a previously-created profile during the course of making an entirely unrelated one, but only for the height. The offset remains correct.
This has happened twice over the last couple of weeks, in different projects. When the bug happens, it affects multiple saved profiles at once, in the same way. I've tried to manually re-create the problem, but I'm not sure what combination of actions during creation of Profile #2 causes problems to occur in the previously-created Profile #1. To be clear, this problem does NOT happen every time I make a new profile - it appears to be rare, making it tricky to replicate.
Thoughts? Are there some procedures that I might be doing which are obviously "dangerous" and could yield this issue?
Here's the story:
- I have some profiles set up for my metric rod, along with appropriate vertical offsets. For example, a profile for the 2-meter setting on my Seco. I created it by entering the height using the Meters units (entered as 2.0 meters), and measured the actual rod height, yielding a difference of 0.056m. That gets entered into my vertical offset, still using the Meters units.
- My project is in USft, so when I save the profile, I see the readings as: 6.5617' with vertical offset of 0.1837'. Great! I've used and checked all my profiles in multiple projects and they work fine.
Now for the confusing bit...
- I have the need to use a different rod for a while, so I make a new profile for it like normal. Again measured and entered in metric, and auto-converted to feet. Let's call it 1.4 meters height with no offset.
- Somewhere during that process of making a new profile, the bug occurs.
The Bug:
Upon saving the profile for the new rod, my profile for the 2-meter Seco rod has been mysteriously changed and now reads: 2.0 FEET, with 0.1837-foot vertical offset. While the newly created profile shows up correctly as 4.5932 feet.
Somehow, J-field has "forgotten" the units in a previously-created profile during the course of making an entirely unrelated one, but only for the height. The offset remains correct.
This has happened twice over the last couple of weeks, in different projects. When the bug happens, it affects multiple saved profiles at once, in the same way. I've tried to manually re-create the problem, but I'm not sure what combination of actions during creation of Profile #2 causes problems to occur in the previously-created Profile #1. To be clear, this problem does NOT happen every time I make a new profile - it appears to be rare, making it tricky to replicate.
Thoughts? Are there some procedures that I might be doing which are obviously "dangerous" and could yield this issue?