![]() ![]() I have been building equipment for my telescope making it compatible with protocols of commercial equipment, for example, to be able to use the same drivers (again, I don’t know how to do them) and those are far from claiming to be “open”… But in this case it looks like it´s not that transparent. I was thinking that it would have been relatively easy to find -at the end, who sells the software doesn’t sell the hardware in this case, so if the interface is open you increase the amount of people who can use it. The issue for me is that, while I’m fairly decent with microcontroller programming, I’m complete useless with computer programming, so I need to rely on external software, and for that, I need a minimum of documentation on the communication protocol. ![]() I can add stepper motors for gauges, read encoders as I like for the controls, I can use one single connection for all panels, etc. The difference is, if I do the hardware, I can do what I want, and in a lot easier and cleaner way than using a general purpose board. ![]() The application for an instrument panel itself is very easy: read inputs, send outputs. I understand that people don’t know how to design or build electronics and go for that, same for me for PC software, I wouldn’t know where to start. Everythings else is the specific design for the application, and that’s not reinvented, that is simply… designed. Arduino is just a demo board for people who don’t know how to do electronics, the microcontroller part of the circuit takes literally ten minutes to design and route. Here is my overhead top with pokeys and led driver. The audio uses the HDMI cable to reach the cockpit so it is switched automatically from the desktop - this allow me to have a comfortable table to program and test, and quickly transfer to the cockpit to fly. All the rest is connected via a Gigabit switch and powered USB switch. Our Pro-Line Systems are more commercial turn-key all in one. This is as DIY (do it yourself) blueprint plans set or ready to assemble kits which are offered as unfinished Bare Bones kits or complete Ready to Assemble RTA kits. The monitor is connected to my desktop PC through an HDMI switch (Aukey) - simply pressing a button I transfer the video from my desktop to the 32" monitor of the simulator. All SimSamurai flight simulator cockpit designs are available for purchase in several ways. The power is supplied by an ATX ps for 3,3 - 5 and 12 V plus separate power supply for stepper and servos. The overhead panel is from FlightSimPM (only the panels and annunciators) the hardware (switches, leds, rotary switches, wiring, interfacing, etc) is assembled from Amazon parts and some from Opencockpits (737 style).īacklighting is made with LED stripes. These parts are currently powered with 2 Pokeys boards and interfaced with FSSymphony and sioc code through FSUIPC offsets. As I wrote the plug-in modules are the MCP, EFIS and NAV radio (from Opencockpits), and these are interfaced using SIOC code available on the net, that requires FSUIPC running.Īll the rest is hand made using MDF and some panels from Hispapanels (I do not have a laser engraver so I need panels with translucend signs for backlighting). ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |