|
Post by ScottB on Jan 11, 2015 16:30:52 GMT
My setup when I began experimenting with triple-monitors and networking software for FSX. One laptop is balanced on some brackets up top and running Google Earth Tracker. The laptop below is running SimPlugins software and the iPad is running FSWidgets software. The keyboard labels are from Rodger Dodger Aviation. The aircraft is Sibwings Bird Dog and the scenery is Orbx. The landing? Well the landing speaks for itself! Haha!
I've since upgraded my PC and gaming cockpit. I've also upgraded to an Almost Aviation panel. One panel is still in the works and I plan to upload a video of that as well.
Scott
|
|
|
Post by MarkH on Jan 11, 2015 16:45:46 GMT
That is a tidy setup already and having good sound makes all the difference. And you have a GoPro (or maybe not - the sound seems too good!) Will be interesting to see the new setup, especially after the pics of your radios-in-progress. (P.S. That was almost a good landing, right up to the last minute )
|
|
|
Post by ScottB on Jan 11, 2015 17:33:28 GMT
That is a tidy setup already and having good sound makes all the difference. And you have a GoPro (or maybe not - the sound seems too good!) Will be interesting to see the new setup, especially after the pics of your radios-in-progress. (P.S. That was almost a good landing, right up to the last minute ) Thanks! :-) You are right, I used a GoPro! Speakers and subwoofer are Bose, aided by vibration from a B.K. Gamer.
I rounded up the few photos I have and put them in this video, a progression of sorts. I'm still working on the radio stack.
Thanks for allowing us to post projects on this forum.
Scott
|
|
|
Post by MarkH on Jan 11, 2015 20:04:25 GMT
I rounded up the few photos I have and put them in this video, a progression of sorts. I'm still working on the radio stack. Wow, that EXPERIMENTAL panel is very cool and the radios look pretty darned good so far. I like the extended joystick too...
|
|
|
Post by ScottB on Jan 12, 2015 15:07:33 GMT
Thanks Mark. I'm dragging my feet in regards to completing the radio stack. I'm pretty sure I would have bought your panels if I hadn't already started my project before you decided to sell kits. Anything to shave off a little time and make it easier! Scott
|
|
|
Post by ScottB on Feb 13, 2015 1:23:06 GMT
May I please get a wiring diagram? (ha,ha)
|
|
|
Post by MarkH on Feb 13, 2015 8:45:58 GMT
Did you attach all those little plugs yourself?!
|
|
|
Post by ScottB on Feb 13, 2015 14:11:42 GMT
Hi Mark. No, they are part of the cable. I've used cables like them before connecting servos in RC aircraft. The female end is cut off. They fit across the pins, as to close the circuit of one button, or they can be used along the row of pins, as to connect one side of three buttons. That probably doesn't make sense. Using cables with the same color looks confusing but, my boards will be close to the panel so it's pretty easy to sort out. The whole thing is a lot more disorganized and chaotic than your panels. But I'm pretty confident it will all work.
|
|
|
Post by MarkH on Feb 17, 2015 18:36:26 GMT
Well I have to say I am impressed with your growing panel. Pretty damned professional-looking if you ask me!
|
|
|
Post by ScottB on Feb 17, 2015 19:00:36 GMT
Thanks man! That means a lot coming from you!
|
|
|
Post by MarkH on Feb 17, 2015 19:10:41 GMT
Now you need to build a box to enclose it all in. I just had some contact with this guy - awesome results. I never thought plywood could be beautiful!
|
|
|
Post by ScottB on Feb 18, 2015 1:23:09 GMT
Oh my God! That's friggin' awesome! That's what I want you to do! And after you've built it, I want you to make one for me! It's not often you see GA in full-blown flight sim cockpits. That's why your setup is so cool. Is he using FSX in his videos?
I'm thinking of ways to trim out my panels. This afternoon I setup the radio stack to work with the A2A 180 and guess what? It all works!! Damndest thing I've ever seen! Very cool to see it work. Thanks for posting your videos. Without them, I may not have tried any of it. Scott
|
|
|
Post by MarkH on Feb 18, 2015 8:18:48 GMT
Oh my God! That's friggin' awesome!...Is he using FSX in his videos? I like how his two-place Cessna cockpit has actual landing gear! I don't know if he's using FSX - I asked that too, since he was asking about using Air Manager for his next project. Good to hear the radios are working! It's always a bonus
|
|
|
Post by ScottB on Feb 23, 2015 16:40:08 GMT
Ok. I hit some stumbling blocks yesterday. My switch panel and radio stack work as planned with the A2A 180 (which is what I fashioned the panels around to some degree). All of the buttons work (well, some of the buttons connected to the rotary encoders don't because I ran out of circuit boards to connect them to). Even button animations work!. Now, because the panel was meant to be generic, I've found certain buttons for the Realair Scout Autopilot and ADF particularly frustrating. The Scout somehow uses multiple FSX functions in succession to operate the ADF and Autopilot, and I can't identify the variables/fuctions in the FSX commands, Linda Tracer, or FSUIPC console nor do they appear to be located in the variables list of the FSUIPC.log. So, this results in many "buttons" like the autopilots' Yaw Dampener, Vertical Speed, Arm, and the rotary not functioning in the same manner as they do when using the mouse... and this includes other more simple commands like Altitude, etc. I only mention this because now I realize that I should have given more thought to the layout of the panels, exactly which buttons would be most advantageous overall, and maybe built smaller independent units that would be easier to disassemble and modify. I'm still happy with it all and love flying with it. However, I probably should have made an independent GPS, Autopilot, Com radio and Instrument adjust knobs (sound familiar?). I probably would have omitted the audio panel and streamlined the Autopilot and GPS. It appears the Scout AP almost needs three-position toggle switches to accommodate some of the Scout AP functions. I have a feeling the Carenado and Alabeo stuff will be just as tricky. I'm not too concerned with the Scout but, the Realair Lancair... I'd like the AP and GPS to function properly. Part of the problem is research and knowledge. I didn't familiarize myself with the various functions of the AP prior to making the panels, and I seldom used an AP in real life. No real question here... just adding to my project experience.
|
|
|
Post by MarkH on Feb 23, 2015 18:19:04 GMT
many "buttons" like the autopilots' Yaw Dampener, Vertical Speed, Arm, and the rotary not functioning in the same manner as they do when using the mouse... Hi Scott. You know what I am going to say - LINDA is calling your name. That way you can call a couple of functions in sequence. I think you can do that in FSUIPC by listing a button twice and the definitions are executed in sequence. What you can't really do is make any complex (or even simple) conditions, which is why Pete added...well, you know If you look at the Almost Aviation library you will find the AP functions work with the Scout - almost. Here are some miscellaneous notes that might help. (Some of this is rescued from a notepad so might be approximate!) You will not see the target altitude change on the display when you change the altitude with the rotary knob. The Scout uses two Lvars: 'AP_ALT_Hold_Var' and 'apAlt100Knob'. I forget what the second one does but if you write to the first one it changes the display and sets the target altitude. I did not use this method for the AA library because I wanted it to be generic and hence work with other aircraft too. The Scout maintains its target altitude internally, which is why nothing happens until you press the ARM button. If you change the FSX target altitude and ALT mode is in effect, the aircraft begins to climb or descend immediately. I faked the Scout way in my functions by using the FSX target altitude but switching off ALT mode whenever you change it. Then my ARM function just switches ALT mode back on! If I remember, all the 'VS' button does is change the display briefly so you can see the vertical speed instead of the altitude, but you can just change the vertical speed anyway with the regular FSX functions ('AP_VS_VAR_INC' and '...DEC'), which is what the Scout's UP and DN buttons do (they may also change the display briefly to show vertical speed as well). I can't remember if there is an Lvar to make the display change to show the vertical speed, but you can still see the effect on the VSI (with some lag, obviously). I do remember that the Scout's Lvars were not conveniently labelled 'Realair_...' or 'Scout_...' or anything helpful like that! The Yaw Damper function doesn't appear to be implemented - I can't press it and the tool-tip says 'unavailable'! I agree it is difficult to make the autopilot generic and I think the most straightforward solution is not to try. If you're doing this with FSUIPC you could make a Scout-specific profile and a Carenado-specific profile and so on. With L***A you can do the same, just more flexibly.
|
|