Today I've fixed the steering of the speed error indicator in landing mode (the little vertical line on the velocity vector). The function has been there since before, but now I've also got the logic for it. The code is written for both 12 degrees and 15.5 degrees alpha, but since we haven't connected the button to change between these, only 12 degrees work at this moment. I've also fixed the warning for critically low speed.
the low nav mode that I made earlier is now connected with the new logic and seems after the first test to work as it should. In this mode I've also added the functionality to toggle the course indicator by pressing the ref. omk. button. Now I only have a few things left before I start working on the input and out put from the CK program to the data panel.
Today's work was primarily to put all possible adjustments to the HUD into an INI-file. This way the adjusments and calibrations don't have to be med everytime the program is started. Additionally I have once again made it possible to use the ref. omk. button, but with slightly modified functionality. And I've also added the possability to tilt the HUD display at takeoff and landing. Since a HUD of this type has a very limited field of view, and much of the interresting presentation at takeoff and landing is positioned lower than you would like in normal flight, it is possible to physcally tilt the reflector glass of the HUD. But to get a proper presentation this has to be accompanyed by a similar tilt in the computer generated image. When the glass is tilted, a microswitch is pressed and the HUD-program gets a signal to tilt the image to a preset position... As simple as that.
Restructuring of the HUD (SI) program completed. I've implemented some variant of the bridge design pattern to control the different modes of the HUD. I hope that the HUD program this way will be easier to maintain. The hard thing about this project is tat we don't really know from the start how things are going to work. We do have a lot of documentation, but it's far from complete. And when I try to implement one thing we usually find that the way we assumed it worked is simply not true, or at least not the whole truth.
I've now started the flight computer program (CK). But since I haven't worked out the details for the communication between my programs, I included the whole CK program in the SI program with an interface between. This way it should be simple to just lift the CK code to a separate program when I want to. The restructuring means that we've lost some of the functionality. But this is simply a matter of not reaching it at the moment. The code for it is still there.
Since we now have a CK program, I've got the mode selector to work. Start mode is activated and deactivated according to the right conditions.
