![]() |
If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
|
Thread Tools | Display Modes |
|
#1
|
|||
|
|||
![]()
Kurt, So unsurprisingly you want me to go away. Got it. But not going to happen. Do you have a LX product? Sorry it is nothing personal...
I want to see everyone's feet held to the same fire. The standard has been set clearly by USRC. If other software/hardware possesses AH capability (of any level of usefulness) the they must be forced to build a special version of firmware or software. LXNAV (and any other "offenders") should be "required" to provide its customers a special version as the others have been forced to do. Reason: nobody is going to check under the panel and the technology is very capable. Double standards are afoot. We have a big double standard in the case of LXNAV vs. Butterfly, XCSoar or LK8000. The USRC has opened this can of worms. But they are only forcing a couple parties to eat them. We all must eat the same worms. Now lets dig in! Ummmmm! Sean F2 On Wednesday, April 4, 2012 1:24:07 PM UTC-4, kirk.stant wrote: Sean, why are you the only person out there making a huge mountain out of this molehill? The rule is simple - don't show up with a gyro AH or T&B (or the ability to display USEFUL attitude data) if you want to race. Yes that means no LX with AHRS. You also can't show up with 18M wings at a 15M race - its the RULE! All your whining about smart phones and PDAs is exactly that - whining. Without gyros, none of them display USEFUL attitude data. That includes the latest smartphones. Just because it has a pretty "HUD" app doesn't mean you can use it to cloud fly! And no reasonable CD is going to waste the time worrying about iPhone apps or what version of XCLKSoar8000 you are using! If you cloud fly and get caught you will get booted, regardless of what you have in your cockpit - so stay out of the clouds! If you feel so stongly about changing the rule to allow gyros in the cockpit during a race, try building support from the racing community then approaching the RC with a reasoned argument and proposed solution. And to be honest, I wouldn't mind having a backup AH in my cockpit - but it's just not a big deal for me. But your approach of throwing a temper tantrum on RAS is REALLY counterproductive, IMO! - well, except for starting the hissy fit between Max and Paolo - as a SeeYouMobile user that was entertaining! OK, I'll shut up now. Good luck with your contest at Ionia - I really enjoyed the times I raced there - great location and great people. Cheers, Kirk 66 |
#2
|
|||
|
|||
![]()
Sean, did you actually read what I posted? I don't want you to go away, I want you to GROW UP!
You talk big about wanting to attract more people to racing, yet you repeat the same bull**** over and over about how the RC is preventing the march of progress by not allowing your (apparently) favorite toy - an AH in your glider. Instead, I can see potential racing pilots being scared away by your rants. Man, get over it. Just show up at your race, don't have any gyro's in your glider, turn off your smartphone to save the battery for your landout, and have fun. Oh, and it's Kirk - without the U. If I had wanted to use a U, It would have been in "FU!" Seriously, this would be a fun (and loud!) bar conversation. But as it is, you are not helping your cause on RAS. If you knew the guys on the RC, or had flown with and against them, you would realize how dedicated they are to our wonderful sport. And they are cool dudes, too. Cheers. Kirk 66 |
#3
|
|||
|
|||
![]()
[quote=kirk.stant;812642]Sean, did you actually read what I posted? I don't want you to go away, I want you to GROW UP!
You talk big about wanting to attract more people to racing, yet you repeat the same bull**** over and over about how the RC is preventing the march of progress by not allowing your (apparently) favorite toy - an AH in your glider. Instead, I can see potential racing pilots being scared away by your rants. Man, get over it. Just show up at your race, don't have any gyro's in your glider, turn off your smartphone to save the battery for your landout, and have fun. Oh, and it's Kirk - without the U. If I had wanted to use a U, It would have been in "FU!" Seriously, this would be a fun (and loud!) bar conversation. But as it is, you are not helping your cause on RAS. If you knew the guys on the RC, or had flown with and against them, you would realize how dedicated they are to our wonderful sport. And they are cool dudes, too. Cheers. Kirk 66[/QUOTE Well said Kirk |
#4
|
|||
|
|||
![]()
At 00:33 05 April 2012, kirk.stant wrote:
Sean, did you actually read what I posted? I don't want you to go away, I = want you to GROW UP! You talk big about wanting to attract more people to racing, yet you repeat= the same bull**** over and over about how the RC is preventing the march o= f progress by not allowing your (apparently) favorite toy - an AH in your g= lider. Instead, I can see potential racing pilots being scared away by your rants. Man, get over it. Just show up at your race, don't have any gyro's in your= glider, turn off your smartphone to save the battery for your landout, and= have fun. =20 Oh, and it's Kirk - without the U. If I had wanted to use a U, It would ha= ve been in "FU!" Seriously, this would be a fun (and loud!) bar conversation. But as it is,= you are not helping your cause on RAS. If you knew the guys on the RC, or= had flown with and against them, you would realize how dedicated they are = to our wonderful sport. And they are cool dudes, too. Cheers. Kirk 66 If all else fails you can still shoot them with your Sig Sauer, which you are allowed to carry with you in the cockpit. :-) |
#5
|
|||
|
|||
![]()
Kirk,
You make many assumptions about what you think I want. Most are wrong. Really wrong. Nothing personal but **** off. I have no interest in an AH in my glider. Rules are rules but the rulemaker has to defend them occasionally. That goes with the territory. I wish to see all pilots and manufacturers inconvienenced equally by the USRC rules.. Right now that is not EVEN CLOSE to happening. There is a distinct double standard. It is unethical for the USRC to make bold public requirements for some and not for the manufacturer who has the most lethal "in terms of cloud flying" capability. We need to see a ruling on the requirement of firmware for LXNAV vs the LXNAV dealers and customers saying "its ok...wink....ill just...wink...remove the box." Wink wink...;-) Get over it. I have no personal issue with the people of the RC. I have a really big issue with the manner they have handled this rule policy. It needs to be tightened up and enforcement needs to be far better defined. Any logical person can see the massive steaming pile of double standard here. I need it bagged up...not left on the sidewalk for people to step in this summer. |
#6
|
|||
|
|||
![]()
On Thursday, April 5, 2012 8:58:00 AM UTC-4, Sean F2 wrote:
It is unethical for the USRC to make bold public requirements for some and not for the manufacturer who has the most lethal "in terms of cloud flying" capability. We need to see a ruling on the requirement of firmware for LXNAV vs the LXNAV dealers and customers saying "its ok...wink...ill just...wink...remove the box." Wink wink...;-) I think there's a misunderstanding. A competition-ready version of XCSoar can ascertain a lack of cloud-flying instruments to extent that a lack of the AHRS box can. You can circumvent the XCSoar/Comp restriction by installing another XCSoar version in a hidden place, by taking a second PDA, by installing it via a data-link and removing it, and so on. Similarly, you can hide your sensor box somewhere. Either variant of cheating is relatively easy to accomplish. Such rules make it (a little) harder to cheat, but not impossible. The may or may not be in the interest of safety, and they are certainly silly in the light of the dysfunctional XCSoar horizon, but it seems that they apply to everybody and all devices. No AHRS box - no IMC instrument. No XCSoar with "horizon" - no instrument. Butterfly horizon disabled for 14 days - no instrument. And so on. Simple as that. |
#7
|
|||
|
|||
![]()
XC Soar and LK8000 are useless mobile based, unfixed 1g gyro's on mobile phones and faced direct demands from the USRC.
LXNAV has a huge high priced capability and not a peep? Follow the money... On Thursday, April 5, 2012 9:23:37 AM UTC-4, David Reitter wrote: On Thursday, April 5, 2012 8:58:00 AM UTC-4, Sean F2 wrote: It is unethical for the USRC to make bold public requirements for some and not for the manufacturer who has the most lethal "in terms of cloud flying" capability. We need to see a ruling on the requirement of firmware for LXNAV vs the LXNAV dealers and customers saying "its ok...wink...ill just...wink...remove the box." Wink wink....;-) I think there's a misunderstanding. A competition-ready version of XCSoar can ascertain a lack of cloud-flying instruments to extent that a lack of the AHRS box can. You can circumvent the XCSoar/Comp restriction by installing another XCSoar version in a hidden place, by taking a second PDA, by installing it via a data-link and removing it, and so on. Similarly, you can hide your sensor box somewhere. Either variant of cheating is relatively easy to accomplish. Such rules make it (a little) harder to cheat, but not impossible. The may or may not be in the interest of safety, and they are certainly silly in the light of the dysfunctional XCSoar horizon, but it seems that they apply to everybody and all devices. No AHRS box - no IMC instrument. No XCSoar with "horizon" - no instrument. Butterfly horizon disabled for 14 days - no instrument. And so on. Simple as that. |
#8
|
|||
|
|||
![]()
Sean,
You really are a prick. P3 |
#9
|
|||
|
|||
![]()
On Friday, April 6, 2012 7:23:43 AM UTC-4, Papa3 wrote:
Sean, You really are a prick. P3 Anytime. |
#10
|
|||
|
|||
![]()
Hi Sean,
I'm not sure I understand your argument. The XCSoar and LK8000 software products (which I hear are very nice) are (if I understand correctly) opensource products. The code is freely available. The LXNAV LX8000, LX8080 and LX9000 are not opensource. They are products that have firmware that is not freely available. Updates to those LXNAV products is done by requesting a new version of the firmware from LXNAV which is tied to a particular unit serial number. It would not be possible for anyone other than LXNAV to make changes to those products. They have recently implemented features in the firmware which make it easy to disable the artificial horizon for 14 days - longer than any contest. Also, it is easy for any contest official to look inside the glider and determine whether or not the AHRS unit is installed and connected to the flight computer. It connects to the flight computer using a standard USB cable. If there is no USB cable connected to the flight computer, then the AHRS is not connected. This is much different than the opensource software issues. However, I strongly agree with you that it is silly and frustrating that the rule committee has decided to restrict our technology. It discourages innovation and discourages pilots from flying in U.S. soaring competitions. Best Regards, Paul Remde "Sean F2" wrote in message news:32549288.367.1333683984277.JavaMail.geo-discussion-forums@ynbv36... XC Soar and LK8000 are useless mobile based, unfixed 1g gyro's on mobile phones and faced direct demands from the USRC. LXNAV has a huge high priced capability and not a peep? Follow the money... On Thursday, April 5, 2012 9:23:37 AM UTC-4, David Reitter wrote: On Thursday, April 5, 2012 8:58:00 AM UTC-4, Sean F2 wrote: It is unethical for the USRC to make bold public requirements for some and not for the manufacturer who has the most lethal "in terms of cloud flying" capability. We need to see a ruling on the requirement of firmware for LXNAV vs the LXNAV dealers and customers saying "its ok...wink...ill just...wink...remove the box." Wink wink...;-) I think there's a misunderstanding. A competition-ready version of XCSoar can ascertain a lack of cloud-flying instruments to extent that a lack of the AHRS box can. You can circumvent the XCSoar/Comp restriction by installing another XCSoar version in a hidden place, by taking a second PDA, by installing it via a data-link and removing it, and so on. Similarly, you can hide your sensor box somewhere. Either variant of cheating is relatively easy to accomplish. Such rules make it (a little) harder to cheat, but not impossible. The may or may not be in the interest of safety, and they are certainly silly in the light of the dysfunctional XCSoar horizon, but it seems that they apply to everybody and all devices. No AHRS box - no IMC instrument. No XCSoar with "horizon" - no instrument. Butterfly horizon disabled for 14 days - no instrument. And so on. Simple as that. |
|
Thread Tools | |
Display Modes | |
|
|
![]() |
||||
Thread | Thread Starter | Forum | Replies | Last Post |
U.S.A Rules Committee: We Didn't Mean It? | SoarPoint | Soaring | 3 | November 15th 10 02:06 PM |
US Rules Poll and Rules Committee Election | Ken Sorenson | Soaring | 0 | December 1st 06 01:36 AM |
SSA Rules Poll and Rules Committee Election | Ken Sorenson | Soaring | 2 | October 6th 06 03:27 PM |
US Rules Committee Election and Rules Poll | Ken Sorenson | Soaring | 1 | September 27th 05 10:52 PM |
FLASH! U.S.A. Rules Committee to Address Rules Complexity? | SoarPoint | Soaring | 1 | February 3rd 04 02:36 AM |