whartsell

Just engines.

Not entirely true. When i was active duty our planes needed clearance to start or the SPs got really twitchy. During an ORI we had a crew kissing the pavement cause they cranked engines without clearance.

Ill take 1-2 sets

I am back from vacation as of yesterday and will be updating the code an wiki this week. Currently analog inputs are experimental ( need to tighten up error handling)

No worries. I have been out of town for RL for a while but will give you an update when I get back next week.

You can remove the stops on the auto gauge stepper motors. They are weak but can be directly driven by a microcontroller tgat can handle 20ma. there are a few arduino/avr libs for driving them.

I live in the area as well...just started recently...imwould love to get a central tx pit builders get together to share ideas and talents.

I have a predator flying an orbit in my MP mission. Will everything update when he hits his turning point in the orbit or will I have to manually define a box and use advanced scripting to get him to repeat waypoints?

Reloading after everybody is in appears to work Not perfect but ill take it. Thanks for the help

I was going to try that this evening. But that workaround really sucks for running a "dedicated" server.

I just loaded the attached mission in a MP session. My clients do not get a jtac menu at all

One more thing. I will be adding arduino support in my HogKeys utility in the near future. If your interested in that I can speed up the timeline. You can build an arduino compatible board for about 10us in parts :).

If you start putting delays in with caps and stuff ghosting and other timing related issues will be a major problem. If you plan on using an arduino as a joystick,handle the DX buttons programatically may be a solution. For example if matrix C2 is "on" send DX(modifier) then DX action button. Remember you will need to handle cases where multiple buttons in the matrix are down

Sorry I haven't posted anything new here in a bit. I have been too busy flying on my vacation :). I'll get the latest build up tonight or tomorrow morning

I have the same problem...is there a bug logged against this?

What a coincidence. In the simmeters altimeter they have the same Stepper motor I plan on building my instruments from. I plan on using amtel Instead of pic controller. If I get it working ill post pics of how to do it.

one more thing. I have also tested configs with and without helios exporting enabled. Ill get that cleaned up and posted with the next release as well. I havent made too much progess lately due to the holidays. Now that my cockpit is up and working (minimally) i have also been knocking the dust off the manuals and flying every chance i get to try to get back into the groove.

I have analog inputs working but have not posted the release yet. Ill get it posted this weekend. after that im gearing up to start with stepper motors and servo motors

I love your VHF solution..I may have to "borrow" your idea

Which sim were you using? In FSX and alot of other sims they don't do DME right. They put a VOR/DME station. That's probably why you got an active VOR needle. In real world you would have received a NAV flag on the OBS or no to-from indicating no bearing indication. Some of the DME units also allow you to put a separate freq outside of VOR 1/2 for DME only readings. Will

On this approach you dont use the VOR's OBI at all. The ADF's Radio compas or RMI if equipped is your primary nav instrument with DME providing distance only. You would track 073 QDM till about 8.5-9DME (depending on your airspeed) then turn right 90 degrees to 163. When the ADF slides down to 063 QDM you turn left 10 degrees to 153. When the ADF moves down to 053 QDM you turn left another 10 degrees 10 143. Keep repeating this until you are approaching QDM 026. Depending on winds and such you may need to adjust your heading increments to stay within the Arc. Normally +- 1 NM is fine. Once you are ready to intecept the IF track QDM 26 and start your decent below 2000. depending on the winds you may not actually be heading 026 so adjust your heading to maintain the QDM026 bearing all they way to MAP or when you have visual. Hope that helps

ADF is not used to fly a DME arc. You use VOR/DME for that. Flying DME arcs is a bit confusing at first. Im curious which approach you were flying.

Were you flying a VOR approach or a NDB DME approach? For a NDB approach you would not use the VOR indicator at all. On an NDP approach the main instrument would be your ADF indicator or RMI if equiped. If the NDB approach references DME fixes you would use the VOR only for verifying those fixes. On charts the radial reference would be (as shown in your VOR indicator) FROM the station. When you are tracking a VOR with a FROM reading you fly away (from) from the needle to center it. When the VOR has a TO reading you fly TOwards the needle. If you let me know what approach you were flying I can look over the chart and give you some pointers on it. Hope that helps

HogKeys V1.1.0 is available This new version supports discrete outputs e.g Annunciator Lamps. get it at... http://code.google.com/p/hogkeys/

Thanks. I'll be putting out a new version shortly that will support indicator light outputs