Tuesday, April 25, 2006
So far
The switches and analogue inputs on the lower panel will be connected to the sim through simkit's USB input boards. These will show up in Windows as standard game controller devices, FS can map the inputs to ignition key, light switch etc controls, so no additional interfacing is needed. I gave up on constructing the rather special flap switch in the real Cessna 172, it will be replaced by a simple up-down momentary switch. Trim wheel will be contructed using a helipot, so it will be an analogue input as well.
The outputs on the lower panel are: the flap indicator and the gear lights (trim indicator will be simply mechanically connected to the trim wheel). The flap indicator will be driven by a servo, the gear indicator lights are simple LEDs.
The inputs on the upper (main) panel are gyrocompass adjust, VOR and ADF OBS knobs. These will be rotary encoders.
The outputs on the upper panel are: several intrument needles, warning panel, annunciator panel. I hope to implement warning and annunciantor panel using LEDS. Instruments will be driven by servos for the "simple" instruments (small gauges, airspeed indicator, VSI, tachometer, attitude indicator, turn and bank coordinator, VOR1, VOR2, ADF) and probably stepper motors for the "complex" instruments (altitude and heading indicators). "Simple" here stands for "cannot make arbitrary number of turns".
The outputs will be driven with a custom board; it will communicate through serial port with PC (thanks, I've had enough of USB).
I have to remember that I'm doing this for myself; so instead of a fancy GUI, command line program will be more than OK to send data to output board(s).
First control program prototype will be something like processing some .ini file for the settings, reading values from FS through FSUIPC (version 2.96 which is freeware should be enough for the prototype), sending servo position info to serial port. The .ini will contain the address to be read from FS and calibration data, i.e. which value corresponds to which servo position. This should be good enough for the simple instruments.
The complex instruments require position feedback in some form. For mechanical solutions and driving the complex instruments I hope to get a lot of ideas from a book I've just ordered.
The outputs on the lower panel are: the flap indicator and the gear lights (trim indicator will be simply mechanically connected to the trim wheel). The flap indicator will be driven by a servo, the gear indicator lights are simple LEDs.
The inputs on the upper (main) panel are gyrocompass adjust, VOR and ADF OBS knobs. These will be rotary encoders.
The outputs on the upper panel are: several intrument needles, warning panel, annunciator panel. I hope to implement warning and annunciantor panel using LEDS. Instruments will be driven by servos for the "simple" instruments (small gauges, airspeed indicator, VSI, tachometer, attitude indicator, turn and bank coordinator, VOR1, VOR2, ADF) and probably stepper motors for the "complex" instruments (altitude and heading indicators). "Simple" here stands for "cannot make arbitrary number of turns".
The outputs will be driven with a custom board; it will communicate through serial port with PC (thanks, I've had enough of USB).
I have to remember that I'm doing this for myself; so instead of a fancy GUI, command line program will be more than OK to send data to output board(s).
First control program prototype will be something like processing some .ini file for the settings, reading values from FS through FSUIPC (version 2.96 which is freeware should be enough for the prototype), sending servo position info to serial port. The .ini will contain the address to be read from FS and calibration data, i.e. which value corresponds to which servo position. This should be good enough for the simple instruments.
The complex instruments require position feedback in some form. For mechanical solutions and driving the complex instruments I hope to get a lot of ideas from a book I've just ordered.
Wednesday, April 05, 2006
Custom electronics dumped
Long time no update.
I managed to buy a CH yoke plus CH pedals. My job required to visit Prague (Czech Republic) more than I wanted to, the good thing was that I managed to find a CH products reseller there
A local craftsman cut the lower panel and holes from 2mm aluminium (he asked for an outrageous amount though, about 40 EUR).
I have the switches for the lights and started constructing the starter key.
Although it was fun and I also learned many new things, I decided to go with a more robust solution for USB electronics, see simkits. I ordered the 32-digital inputs board and the 6-analogue inputs boards. They are almost identical in functionality to my design and implementation, but eventually I got tired of ironing out small bugs in my firmware and in my hardware. Total cost for the 2 boards is about the same as the price for the UV eraser itself :(
I managed to buy a CH yoke plus CH pedals. My job required to visit Prague (Czech Republic) more than I wanted to, the good thing was that I managed to find a CH products reseller there
A local craftsman cut the lower panel and holes from 2mm aluminium (he asked for an outrageous amount though, about 40 EUR).
I have the switches for the lights and started constructing the starter key.
Although it was fun and I also learned many new things, I decided to go with a more robust solution for USB electronics, see simkits. I ordered the 32-digital inputs board and the 6-analogue inputs boards. They are almost identical in functionality to my design and implementation, but eventually I got tired of ironing out small bugs in my firmware and in my hardware. Total cost for the 2 boards is about the same as the price for the UV eraser itself :(
