flyinjake
02-06-2011, 01:48 PM
Hello Everyone,
I have been viewing the website over the last month or so putting together my ideas on how I want to proceed with a cockpit. I am not trying to build an aircraft specific cockpit but one that will work with the different types I like to fly. One of my biggest frustrations is the point and clicks required while flying some aircraft. Also, it will add to the enjoyment and feel of realism.
Generally I feel I should start with the simpler controls and then move on to the more complicated designs. I already know I am going to order a few of Leo's BU036X USB cards. I say a few because my Dad flys and he wants to build his own cockpit also. This will introduce me to using the card and working in the registered version of FSUIPC. I will start with a Lights panel, gear selector lever, flaps, mags, starters and so on. I do not see me having any issues in that department. One area I need to read up on is what is the best board to give me feedback back to instrument panel indicator lights such as gear condition lights. Those do not indicate "down and locked" right away as there is a delay until they are in position. I could put a timer in the circuit but I would like to use this as a time to learn more about the communication back and forth between the software and hardware.
I will admit when it comes to radios or TQs I need to do more research. I like the layout of the Airbus\RJ TQ I saw at Kennair's website. I will look further into that type of setup but I can definetly see something similiar to that in my simulator.
Radios; I will take two paths. First I will use encoders to control them while still looking at the screen to determine the settings. Then either buy or build radios that have the channel displays built into them. Basically depends on cost to build from scratch versus buying. Even though I am not a fan of the look of Saitek products it may be the best fit for what I am doing.
I might buy an already made airliner MCP from someone. My only concern is, will it work across other aircraft types such as a Cessna 185, Seneca, Lear Jet or King air? Basically it is the autopilot but what limitations would i encounter? Also, is there a generic MCP available that I have not found yet? Yes, I realize Saitek has one but unless I am mistaking it does not use mach numbers that jets would use during flight.
Yoke and rudders are CH products and will work for now.
Visuals: I have several monitors right now and plan on using them. My plan is to use one or two of the monitors for instrument display and the other for outside view. Down the road I would like to go with a projector setup but for now my 22's will work just fine.
I will build the switch panels modular so I can repalce or expand as necessary. The switches do not need to be specific aircraft switches but I will try to at least mimick the type of switch.
To me that appears to be a good start. Its hard to nail down specifics about some of this when one does not know enough about the input and output requirements. First desgin the panels and implement the basics and see how far I can go. Once I have that implemented I will look at the more complicated parts.
One last concern of mine, that I have ignored, is the software programming that some of you mentioned when designing your own panels. That will be a major factor in which way I head when it comes a time to work with that. I have no clue about programing software so there will be a learning curve for me.
Please give me your thoughts and suggestions. In my head I know what I want and it does not need to be perfect. However, it does need to be functional and adaptable.
Thanks,
Jake
I have been viewing the website over the last month or so putting together my ideas on how I want to proceed with a cockpit. I am not trying to build an aircraft specific cockpit but one that will work with the different types I like to fly. One of my biggest frustrations is the point and clicks required while flying some aircraft. Also, it will add to the enjoyment and feel of realism.
Generally I feel I should start with the simpler controls and then move on to the more complicated designs. I already know I am going to order a few of Leo's BU036X USB cards. I say a few because my Dad flys and he wants to build his own cockpit also. This will introduce me to using the card and working in the registered version of FSUIPC. I will start with a Lights panel, gear selector lever, flaps, mags, starters and so on. I do not see me having any issues in that department. One area I need to read up on is what is the best board to give me feedback back to instrument panel indicator lights such as gear condition lights. Those do not indicate "down and locked" right away as there is a delay until they are in position. I could put a timer in the circuit but I would like to use this as a time to learn more about the communication back and forth between the software and hardware.
I will admit when it comes to radios or TQs I need to do more research. I like the layout of the Airbus\RJ TQ I saw at Kennair's website. I will look further into that type of setup but I can definetly see something similiar to that in my simulator.
Radios; I will take two paths. First I will use encoders to control them while still looking at the screen to determine the settings. Then either buy or build radios that have the channel displays built into them. Basically depends on cost to build from scratch versus buying. Even though I am not a fan of the look of Saitek products it may be the best fit for what I am doing.
I might buy an already made airliner MCP from someone. My only concern is, will it work across other aircraft types such as a Cessna 185, Seneca, Lear Jet or King air? Basically it is the autopilot but what limitations would i encounter? Also, is there a generic MCP available that I have not found yet? Yes, I realize Saitek has one but unless I am mistaking it does not use mach numbers that jets would use during flight.
Yoke and rudders are CH products and will work for now.
Visuals: I have several monitors right now and plan on using them. My plan is to use one or two of the monitors for instrument display and the other for outside view. Down the road I would like to go with a projector setup but for now my 22's will work just fine.
I will build the switch panels modular so I can repalce or expand as necessary. The switches do not need to be specific aircraft switches but I will try to at least mimick the type of switch.
To me that appears to be a good start. Its hard to nail down specifics about some of this when one does not know enough about the input and output requirements. First desgin the panels and implement the basics and see how far I can go. Once I have that implemented I will look at the more complicated parts.
One last concern of mine, that I have ignored, is the software programming that some of you mentioned when designing your own panels. That will be a major factor in which way I head when it comes a time to work with that. I have no clue about programing software so there will be a learning curve for me.
Please give me your thoughts and suggestions. In my head I know what I want and it does not need to be perfect. However, it does need to be functional and adaptable.
Thanks,
Jake