Josh Babcock wrote:
Jim Wilson wrote:
Yeah, I have been reviewing this, and I think I understand how the definition works. I'm getting pretty much the same numbers based on the 2900 and .35 which I got out of the POH and several internet sources on the cyclone engines. I have a more appropriate yasim file now, but I still can't get it to solve, so I wonder if there is another problem somewhere else? Maybe I have screwed up the aero data and it is producing way too much drag.
Here's the latest: http://home.comcast.net/~jrbabcock/superfort/b29-yasim.2.xml
Everyone, thanks for all the help so far, it is very appreciated, Josh
Not sure if I started with the latest or not, but this one solves: http://www.spiderbark.com/fgfs/b29-yasim.xml
This is what I changed:
1) Added fuselage length.
2) Increased wing length to something closer to correct length. 3) Probably adjusted a couple other less significant numbers that seemed wrong (wing sweep angle maybe?).
4) Fixed rpm/power numbers under the prop tags. They need to be scaled back according to the gear ratio. Someone with a better understanding of mech engineering might be able to explain why the BHP on the prop shaft is reduced by a factor of 0.35 when that's the gear ratio, or maybe that is wrong and there is something going on in the YASim calcs. It seems that is what you have to do to get a solution that works. In any case YASim should at least do some sanity checking here to avoid the endless loop thing.
Solution results: Iterations: 1220 Drag Coefficient: 3.398360 Lift Ratio: 417.065216 Cruise AoA: 1.252508 Tail Incidence: 3.132050 Approach Elevator: 0.268476 CG: -10.439, 0.000, -0.137
This solution isn't quite right. I had to knock down your cruise speed and altitude, but at least you've got something to go back to while tweaking. BTW I don't know much about the B-29, but did you do that airspeed in KIAS? 365 @ 25000 sounds a bit high.
Best regards,
Jim Wilson
_______________________________________________ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Is the sweep supposed to be the LE or the .25% chord?
Josh
_______________________________________________ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
OK, it solves with this line:
<control-input axis="/controls/engines/engine[3]/propeller-pitch" control="ADVANCE"/>
but not this one:
<control-input axis="/controls/engines/engine[3]/propeller-pitch" control="PROPPITCH"/>
Does ADVANCE mean prop pitch here?
Josh
_______________________________________________ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
OK, looks good in yasim, but in fgfs I get this:
[snip]
open("/usr/local/share/FlightGear/data/Aircraft/b29/jim.xml", O_RDONLY) = 15
fstat64(15, {st_mode=S_IFREG|0644, st_size=10371, ...}) = 0
mmap2(NULL, 131072, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0xa53da000
read(15, "<?xml version=\"1.0\"?>\n<!-- Tacti"..., 131072) = 10371
read(15, "", 131072) = 0
read(15, "", 131072) = 0
close(15) = 0
munmap(0xa53da000, 131072) = 0
--- SIGSEGV (Segmentation fault) @ 0 (0) ---
+++ killed by SIGSEGV +++
Oh woe is me, what's up with the segfaults? Let me know if anyone wants the whole strace. This looks suspiciously like what the jsbsim one was doing, but my b29-magic works fine, and the only difference is the fdm file.
Josh
_______________________________________________ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d