Re: [Flightgear-devel] Cessna 310 Model
Hi, Can you post what you changed? I'm not sure from the above exactly which tags went where. Certainly, if you put the right tags in the right places, it should work. :) Here it is. I posted it earlier, but you might have missed the msg. For both YASim and JSBSim the flaps seem inop. Gear, flight surfaces, engines are okay. Except it looks like the YASim 747 needs a nose gear Key board ] and [ activate audio flap sound and panel movement of flap switch, just nothing from properties Here is code snip from XML file for 747 control-input axis=/controls/flaps control=FLAP0/ control-input axis=/controls/aileron control=FLAP1 split=true/ control-input axis=/controls/aileron-trim control=FLAP1 split=true/ control-input axis=/controls/slats control=SLAT/ control-input axis=/controls/spoilers control=SPOILER/ control-output control=FLAP0 prop=/surface-positions/flap-pos-norm/ control-speed control=FLAP0 transition-time=10 and the code from my source file to retrieve the properties data-elevator = fgGetDouble(/surface-positions/elevator-pos-norm); //data-elevator_trim = globals-get_controls()-get_elevator_trim(); //data-rudder = globals-get_controls()-get_rudder(); //data-rudder_trim = p_Controls-get_rudder_trim(); data-flaps = fgGetDouble(/surface-positions/flaps-pos-norm); //data-flaps = globals-get_controls()-get_flaps(); data-gear_nose = fgGetDouble(/gear/gear[0]/position-norm); data-gear_left = fgGetDouble(/gear/gear[1]/position-norm); data-gear_right = fgGetDouble(/gear/gear[2]/position-norm); It's not there. The property interface is soft-coded. YASim is directed by its configuration file to put the specified control value in the specified place. So this: wing ... control-output control=FLAP0 prop=/surface-positions/flap-pos-norm/ /wing ... tells it to place the final FLAP0 setting for that wing (typically the inner/landing flap for most wing objects) into the specified property. Is there any documentation outlining how the properties work, setting them up, and various options available for their implementation. Trying to decipher it can be confusing. Kept wondering why the the JSBsim and YAsim xml files were different. Is this the reason? Does that also mean that the source to retrieve the data from JSBsim and YAsim will be different if the properties for the same value are created differently? Regards JW ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] Cessna 310 Model
Hi, Oh, never mind, it's just a typo. Note spelling of the property above, and here: [...] data-flaps = fgGetDouble(/surface-positions/flaps-pos-norm); [...] Snip the stray s, and you should see correct behavior. This, it must be admitted, is the biggest disadvantage of a dynamically bound interface like properties. Typos get detected only at runtime, and even then only with some difficulty. Some of David's work with property tracing can be really helpful here, as can the property picker (a very good thing -- make it your friend). That was it. last week, though, so the discussions about them should be fresh in the mailing list archives. Was able to pick up most of it, just the flaps that were throwing me for a loop Some of the internals of how properties work is still a mystery. Haven't had the time or patience to work thru the code to see exactly what is happening. Working mostly from other examples versus an in-depth understanding. Thanks for catching the stray How complete is the 747 wing model for slats, spoilers? Note they are in the XML file; is it just a question of specifying the control axis input. If using the native-ctrls network interface, would that need to pass the control axis parameters from the network to YASim. working in the FMC autoland sequence and need to deploy spoilers, thrust reversers, brakes and such upon touchdown signal with WOW from main bogeys. Regards JW Regards JW ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] Cessna 310 Model
John Wojnaroski wrote: How complete is the 747 wing model for slats, spoilers? Note they are in the XML file; is it just a question of specifying the control axis input. Indeed. I have the /controls/spoilers property bound to the same joystick axis I use for mixture (or maybe propeller advance, I forget). The slats property I just toggle as a boolean with a button mapping. Now that I think about it, really good stuff to add to the aircraft description would be a control-speed entry for slats, as they take a few seconds to deploy; and an input mapping from the outer part of /controls/aileron to spoiler deflection, since the spoilers assist in roll control at high control inputs. If using the native-ctrls network interface, would that need to pass the control axis parameters from the network to YASim. working in the FMC autoland sequence and need to deploy spoilers, thrust reversers, brakes and such upon touchdown signal with WOW from main bogeys. Yes. Presumably you'd query the appropriate outputs (/gear/gears[n]/wow, in this case) out of the property system, and set the inputs (/controls/*) appropriately. Andy -- Andrew J. RossNextBus Information Systems Senior Software Engineer Emeryville, CA [EMAIL PROTECTED] http://www.nextbus.com Men go crazy in conflagrations. They only get better one by one. - Sting (misquoted) ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] Cessna 310 Model
David Megginson wrote: For some reason, the animations are not working with the YASim Cessna 310 model (despite the fact that the same kinds of animations work fine with the YASim DC-3). I cannot find anything obvious in the config file, but perhaps Andy could take a glance. It's not exporting any properties. :) I was lazy when I did the new XML files, and only did property exports for the aircraft that I could test visually. All that's necessary is to clone the control-output tags from the DC-3, which should be identical in all ways. I'll get a new one put together soon, if you don't want to do it yourself. Andy -- Andrew J. RossNextBus Information Systems Senior Software Engineer Emeryville, CA [EMAIL PROTECTED] http://www.nextbus.com Men go crazy in conflagrations. They only get better one by one. - Sting (misquoted) ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] Cessna 310 Model
Andy Ross writes: It's not exporting any properties. :) I was lazy when I did the new XML files, and only did property exports for the aircraft that I could test visually. All that's necessary is to clone the control-output tags from the DC-3, which should be identical in all ways. I'll get a new one put together soon, if you don't want to do it yourself. I did it today. All the best, David -- David Megginson [EMAIL PROTECTED] ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] Cessna 310 Model
It's not exporting any properties. :) I was lazy when I did the new XML files, and only did property exports for the aircraft that I could test visually. All that's necessary is to clone the control-output tags from the DC-3, which should be identical in all ways. I'll get a new one put together soon, if you don't want to do it yourself. I added the tags to the 747 file, but it appears the code is not exporting a value for the nose gear or the flap settings. Did a grep on flap-pos-norm, find the property in JSBSim but nothing in YASsim. Source was downloaded from CVS Sat afternoon. Regards JW ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] Cessna 310 Model
John Wojnaroski wrote: I added the tags to the 747 file, but it appears the code is not exporting a value for the nose gear or the flap settings. Can you post what you changed? I'm not sure from the above exactly which tags went where. Certainly, if you put the right tags in the right places, it should work. :) As with all bug reports: the more you can tell me, the more help I can give. Did a grep on flap-pos-norm, find the property in JSBSim but nothing in YASsim. Source was downloaded from CVS Sat afternoon. It's not there. The property interface is soft-coded. YASim is directed by its configuration file to put the specified control value in the specified place. So this: wing ... control-output control=FLAP0 prop=/surface-positions/flap-pos-norm/ /wing ... tells it to place the final FLAP0 setting for that wing (typically the inner/landing flap for most wing objects) into the specified property. Andy -- Andrew J. RossNextBus Information Systems Senior Software Engineer Emeryville, CA [EMAIL PROTECTED] http://www.nextbus.com Men go crazy in conflagrations. They only get better one by one. - Sting (misquoted) ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] Cessna 310 Model
Curtis L. Olson writes: Looking a bit closer at the JSBSim behavior, I think it's giving us an over abundance of nose wheel slippage. Even an slow speeds, watch what happens if you turn the nose wheel hard one direction and then hard the other. It takes a long time for the yaw to respond. I agree. I have brought this up once or twice, but given the more serious gear problems, I've never pushed it. Do you find YASim's nose-gear handling more reasonable? All the best, David -- David Megginson [EMAIL PROTECTED] ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] Cessna 310 Model
OK, another one on my list. Could be as simple as a gearing constant in teh config file. Jon - Original Message - From: David Megginson [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Saturday, March 02, 2002 3:29 PM Subject: Re: [Flightgear-devel] Cessna 310 Model Curtis L. Olson writes: Looking a bit closer at the JSBSim behavior, I think it's giving us an over abundance of nose wheel slippage. Even an slow speeds, watch what happens if you turn the nose wheel hard one direction and then hard the other. It takes a long time for the yaw to respond. I agree. I have brought this up once or twice, but given the more serious gear problems, I've never pushed it. Do you find YASim's nose-gear handling more reasonable? All the best, David -- David Megginson [EMAIL PROTECTED] ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] Cessna 310 Model
On Sat, Mar 02, 2002 at 04:29:30PM -0500, David Megginson wrote: Curtis L. Olson writes: Looking a bit closer at the JSBSim behavior, I think it's giving us an over abundance of nose wheel slippage. Even an slow speeds, watch what happens if you turn the nose wheel hard one direction and then hard the other. It takes a long time for the yaw to respond. I agree. I have brought this up once or twice, but given the more serious gear problems, I've never pushed it. Do you find YASim's nose-gear handling more reasonable? Is the cg too far aft? All the best, David -- David Megginson [EMAIL PROTECTED] ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel -- Tony Peden [EMAIL PROTECTED] We all know Linux is great ... it does infinite loops in 5 seconds. -- attributed to Linus Torvalds ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
