Aronis Posted February 16 Posted February 16 I build a right panel for the F16 and have been using it with some success. However, I have noted that when I switch from "Stored HTG" to "Nav" although the in game image changes properly, the INS gets messed up about 1/2 the time and I have restart the INS sync because I get error in the EHSI, redline through range. Also even if the INS align works and I see range info in the EHSI, sometimes the flight path marker in the heads up is not present. How does the external switch box cause this? Any thoughts? Mike
No1sonuk Posted February 16 Posted February 16 Can you recreate the INS switch separately? It might be you have too much on one Arduino. Try commenting out everything except the INS switch and see if it works OK. You might need to split the panels across a couple/few Arduinos.
Aronis Posted February 16 Author Posted February 16 yes, I going to go with my original design with the Potentiometer/rotary switch idea now that I have the BORT files and can see a selection for Potentiometer in that command set. I just have to open the box and re do that switch using a single A# input instead of the 8 digital ones. Will take a week to get to it, too busy at work this week. I'm going to set up a test pot on the Arduino Uno that I have, I have some new rotary switches on order. Mike
Aronis Posted February 23 Author Posted February 23 (edited) Got it all sorted out. I was able to get a better rotary switch and convert it to a pot by adding some resistors, and then programmed a second Arduino Uno as a test base, I got it kinda working, but if I rotated the switch to far clockwise direction it got wonky. So I then figured out how to test the pot/switch with a Sketch that shows the values at each setting, and figured out I had it wired off by one pin. Once I got the switch working and figured out the error, I was able to plug the new stitch back into the main Arduino Mega and everything works properly. In the code: DcsBios::AnalogMultiPos insKnb("INS_KNB", PIN, STEPS); I found that I needed the number of Steps in the code to be set to 8 even though the in-game simulated switch setup was only for 7 positions. I think if I move my positive lead back one pin and remove a resistor I can set that Steps to 7, but I don't think it makes a difference as the extra switch position does not get used anyway. I still do not understand why using the 8 digital inputs for switches would let the In Game image of the switch move correctly, yet the iNS was not setting up correctly in the simulator. It's just odd. Perhaps I'll try just for kicks and giggles using one of the better rotary switches I bought. Some times good enough is not good enough, and you just have to know why. I tested start up 4 times and the INS was proper each time including showing the flight path marker correctly. Mike Edited February 23 by Aronis
Aronis Posted March 13 Author Posted March 13 (edited) Out with the old....3d printer arrives Friday. Mike Edited March 13 by Aronis
Aronis Posted March 15 Author Posted March 15 I had to figure out how to fill the holes left by the Text. And did. Printing the first test now, and it's almost done. The printer came with Green and Black. I bought several rolls of black and clear, but the clear requires 8 hours of Drying in the printer before I can use it, so I printed just the CMS panel in black and green. It's almost done, but looks pretty good so far. This is the final package to print tomorrow. Mike
Recommended Posts