Hansolo

Here is another Huey panel for you; http://www.ebay.com/itm/US-Army-OH-58-Kiowa-UH-1-Huey-Pilot-Crew-Intercom-Control-Panel-Console-Box-/222492812962?hash=item33cd9ae6a2:g:RyMAAOSwtGlZBMTv Cheers Hans

Yes watch Ebay. From time to time something good comes up. This panel looks like the Governor panel for a Huey and recently went for just $40 plus shipping. http://www.ebay.com/itm/Vintage-Aircraft-FUEL-DE-ICE-ENGINE-RPM-GOV-ELECTRICAL-PANEL-UNTESTED-/222456639094?_trksid=p2047675.l2557&ssPageName=STRK%3AMEBIDX%3AIT&nma=true&si=t%252Fvcu576jqsQQI34q99hTozeTxA%253D&orig_cvip=true&rt=nc Cheers Hans

Beautiful work there @molevitch. When I assisted a good flying budy of mine implementing this collective, we chopped of the MIL spec connector simply because it was too much hazzle to find the female part. Then we too the collective head apart and basically just pulled gently in one wire at a time to map out the connections. As Ian mentioned there may very well be redundant connections which you may just want to get rid of. I look forward for seeing more photos of your project. Cheers Hans

Nice. Thanks for posting Cheers Hans

We don't mind a few impression. Too bad you did have our skins installed. Good job everyone and looking forward to check in with you next time :thumbup: Cheers Hans

There should be some here; http://en.wiki.eagle.ru/wiki/DCS_A-10C_Guides,_Tutorials_and_Reference_Documents#Aircraft_Systems Cheers Hans

IIRCC then SEND function does not included correct elevation so for MP at least you are better off with broadcast SPI, as this included correct elevation data. Cheers Hans

For the A-10C you should be able to use just ON-OFF-ON for the landing light. That the setup I am using now. You may have to alter the joystick.lua to get it to work. It's a little tricky but not overly. I did a little assistance here https://forums.eagle.ru/showthread.php?t=96522&page=11 in post 102 and onwards. The Leo Bodnar cards are real easy to use and have the advantage that you can get software for them so they can handle rotary incremental encoders. I currently use the BBI-32 for my three radios in the A-10C. I never tried a ON-ON-ON with a joystick controller (loe Bodnar card or similar) so whether it is doable I don't know. I am pretty sure it doable with DCS-BIOS but that is another story. Looking forward to seeing more of your project Cheers Hans

FA (Fault Acknowledge) on the CDU or TMS Left short (http://en.wiki.eagle.ru/w/images/2/21/Dcsa10c-keybindings.pdf) Cheers Hans

Could it be an input error? If you type in something wrong the scratchpad will CDU INPUT ERROR or something similar. Unless cleared you cannot enter anything. Cheers Hans

That sound like very awesome news Sir. I think this feature will be important to ensure that the simulator toggle shows the same as the real ones in the home cockpit. Else IMHO I might as well have used momentary switches or pushbuttons for all the inputs but that is not the pit I am trying to achieve. DCS-BIOS has given us (none-coders) the opportunity to produce a more advanced home cockpit than would have been possible using ‘just’ a joystick controller. Please don’t get me wrong. The ‘just’ is by no means meant as a condescending remark. I have used them for all the inputs in my pit simply and have worked very well. But take a look at some of the stuff Warhog, Romeokilo, Patriot and many more have been able to achieve with DCS-BIOS. Thanks again for this great news and effort Ian. Highly appreciated Cheers Hans

Hi Ian, Sorry if this has been asked before but is there a way to command the individual slaves to send their status? If I run joystick controller boards most of the inputs are automatically updated when I get in game. If I was able to 'force' the slaves e.g. one by one to send what they have then I imagine that a similar effect could be achieved with DCS-BIOS. E.g. once RS485 master sees that game is sending data, then it will ask slave #1 for status, then send status to DCS, then ask slave #2 for status and send it to DCS. Once it has asked all slaves then function is being dismissed. I am sure this will take a little time, but normally I am waiting 5-10 seconds anyway waiting for zoom to reset. Is such a functionality possible ? Cheers Hans

Is this any better? Cheers Hans

I agree with TheBamse. Enter a new number and press OSB17 Cheers Hans

Takeoff trim is not neded for EAC. Cheers Hans

Not sure how small the encoders Warhog posted are but this was the smallest rotary switch I found a long time back; http://www.mouser.dk/Search/ProductDetail.aspx?R=SRBV131803virtualkey68800000virtualkey688-SRBV131803 May be able to fit in there. Cheers Hans

You may have to disassembly the entire radio altogether depending on what sort of electrical circuits are in there. I am not saying this to scare you away from the project however sometimes the panels are design to communicate on a BUS and therefore it probably won't communicate with the Arduino anyway. I would as a kind suggestion try and open up the panel and see what is in there. If it's only switches connected directly to the AMPHENOL connector then it should be fairly easy to map out the pins and reuse the connector. However if you find any circuits in there it may be a lot more difficult. Wiring and mapping out the rotary switches (DIS-CARR-TONE & OFF-T/R-RETRAN-HOME & VOL) should be too bad as long as you IMHO are connected directly to the rotary switches. You may even want to change them out to something less expensive and easier to work with. I did that the rotary for the TACAN as there were too many layer and I gave up trying to figure it out :-) Looking forward to seeing more of your project Sir Cheers Hans

Thanks guys. I wouldn't have been able to pull it off without advanced mode of DCS-BIOS :thumbup: It's not too bad Mac. This is the seup I have used; Q1 is a MOSFET. I have used an IFR510 but others may be better suited. D1 is a flyback diode. I have used 1N4004 K1 is the coil of the magnectic toogle switch. R1 is a pull down resistor. X1-3 is output 3 of the Arduino using this DcsBios::LED saspPitchSasL(0x1108, 0x1000, PIN); X1-4 & X1-5 are inputs 4 & 5 to the Arduino using this; const byte saspPitchSasLPins[2] = {PIN_0, PIN_1}; DcsBios::SwitchMultiPos saspPitchSasL("SASP_PITCH_SAS_L", saspPitchSasLPins, 2); PIN_0 is off, and PIN_1 is on so in above example it should look like this; DcsBios::LED sasp_PitchSasL(0x1108, 0x1000, 3); const byte saspPitchSasLPins[2] = {5, 4}; DcsBios::SwitchMultiPos saspPitchSasL("SASP_PITCH_SAS_L", saspPitchSasLPins, 2); Please notice that I the LED has been renamed from saspPitchSasL to sasp_PitchSasL. Otherwise it will not compiles; https://forums.eagle.ru/showpost.php?p=3111882&postcount=724 Full SAS code /* The following #define tells DCS-BIOS that this is a RS-485 slave device. It also sets the address of this slave device. The slave address should be between 1 and 126 and must be unique among all devices on the same bus. */ #define DCSBIOS_RS485_SLAVE 5 /* The Arduino pin that is connected to the /RE and DE pins on the RS-485 transceiver. */ #define TXENABLE_PIN 2 #include "DcsBios.h" /* paste code snippets from the reference documentation here */ //Right Pitch SAS DcsBios::LED sasp_PitchSasR(0x1108, 0x2000, 3); const byte saspPitchSasRPins[2] = {4, 5}; //off, on DcsBios::SwitchMultiPos saspPitchSasR("SASP_PITCH_SAS_R", saspPitchSasRPins, 2); //Left Pitch SAS DcsBios::LED sasp_PitchSasL(0x1108, 0x1000, 6); const byte saspPitchSasLPins[2] = {7, 8}; //off, on DcsBios::SwitchMultiPos saspPitchSasL("SASP_PITCH_SAS_L", saspPitchSasLPins, 2); //Right Yaw SAS DcsBios::LED sasp_YawSasR(0x1108, 0x0800, 9); const byte saspYawSasRPins[2] = {10, 11}; //off, on DcsBios::SwitchMultiPos saspYawSasR("SASP_YAW_SAS_R", saspYawSasRPins, 2); //Left Yaw SAS DcsBios::LED sasp_YawSasL(0x1108, 0x0400, 12); const byte saspYawSasLPins[2] = {14, 15}; //off, on DcsBios::SwitchMultiPos saspYawSasL("SASP_YAW_SAS_L", saspYawSasLPins, 2); DcsBios::Switch3Pos saspMonitorTest("SASP_MONITOR_TEST", 16, 17); DcsBios::Switch2Pos saspToTrim("SASP_TO_TRIM", 18); DcsBios::Potentiometer saspYawTrim("SASP_YAW_TRIM", 19); DcsBios::LED takeOffTrim(0x1026, 0x0400, 13); void setup() { DcsBios::setup(); } void loop() { DcsBios::loop(); } I think in next prototype board I will probably incorporate a small fuse to the 12VDC line for shortcircuit protection. Right now I have a small common 1A circuit breaker for all 12VDC. Later I dream of designing a common board and then have it manufactured so it will be more compact than the prototype board I am using right now. Cheers Hans

Comparrision test between 3D toggle and real mag switches Hi Duckling, Sorry for the delay, but now I had some time to make a small YT clip showing the differences between 3D toggle and the real mag switches; Quality is not super but I think you get the idea. I tried to test different scenarios; 1. Without power 2. With Battery ON 3. With battery and Inverter ON 4. With battery, inverter and APU ON 5. Monitor test 6. Loss of APU power 7. Running on main generators 8. Loss of main generators 9. Loss of engines I ran the sim last week during training for serveal hours and the mag. switches got really hot on 24VDC. I didn't measure the temperature but when at sea we had a rule of thumb that if you could touch an item then it was less than 60º C. If it was too hot then it was above. Not fool proof but my estimate is that they were near 60ºC. Even the bat itself got hot. I now run them off a 12VDC ATX PSU and now they are temperated. Hope you can use the YT otherwise let me know if there is anything else you want me to test. It'd be my pleasure. Cheers Hans

Oh yes that is so nice to hear that 'smack' when they all disengage :smilewink: Thanks a lot Duckling, yes I haven't found anything which works differently. Apart from the fact that the toggle in the 3D pit won't move if I try and put the mag switches in ON while there is no power. Bu as you can see from Gadroc's reply in posr #139 that is normal. I can try and make a small YT showing the different situation both using 3D toggle and the mag switches for comparrision. Please allow for a day or two for me to make it. Thanks a lot Warhog, I hope to be getting a little more done this year than I have the past few. To be honest I haven't really done anything but utilizing DCS-BIOS. Yeah they are not cheap compared to regular toogle switches. I'd gotten mine in fairly decent prices but even at the extremely low prices currently then it's still $120 for 7 pieces. All the best Hans

Hi Managed to get the SAS up and running with real mag switches, much easier than anticipated, Initially I though of making a one-shot timer for the ON position but seems like this is not necessary at all with DCS-BIOS. Nice work Ian :thumbup: I have just been using DCS-BIOS with advanced setup, i.e. two inputs per mag switch, as well as a single output via a MOSFET semiconductor. I can see only very small differences between mouse clicking in 3D cockpit compared to using the real switches. Cheers Hans

SAS Panel Alright I finally decided to try and install my mag switches into my old poorly build SAS panel using DCS-BIOS. Instead of using just one input for the ON position I decided to go for the advanced solution and use two inputs. One for Off and one for ON. E.g. const byte saspPitchSasLPins[2] = {PIN_0, PIN_1}; DcsBios::SwitchMultiPos saspPitchSasL("SASP_PITCH_SAS_L", saspPitchSasLPins, 2); The mag switches I have has this feature build in as they have a change-over set of contacts. The coil for the mag switch is energized by the LED output via a MOSFET semiconductor, with 24VDC as drive voltage E.g. DcsBios::LED saspPitchSasL(0x1108, 0x1000, PIN); The Monitor Test switch is a MIL spec one but not the correct type. It’s set up for simple solution, i.e. only two inputs instead of three. T/O Trim push button is an Otto with really nice feedback. T/O TRIM led and YAW TRIM are not connected at this point Anyway this the a poor recording of it; At the end you can see that I power down the APU which causes all the switches to de-energize. It does same if I remove power supplied from the main generators. So far the only difference I have found comparing with mouse clicking in the 3D cockpit are this: 1. When there is no generator online mouse clicking will cause SAS mag switches to flip ON then instantly OFF. With the real mag switches they do not move at all in 3D cockpit. I do not see this as an issue 2. Should you by mistake set SAS switches on in 3D cockpit using mouse clicks then turning them on via hardwire will have the 3D’s go to off position. Not really an issue since I’ll use the hardwired ones. Apart from this it appears to be working like what they do from 3D cockpit, however I need to do more extensive tests to see if I run into other issues. Cheers Hans

Works, Thanks Ian. Cheers Hans

Alright. A small question. I have just installed DCS-BIOS folder v 0.5.2 into my \Saved Games\DCS.openalpha\Scripts and added the .zip Arduino Libary v0.2.9. I have trying to get the Anti-Collision light switch up and runningusing two digital inputs via const byte lcpAnticollisionPins[2] = {3, 4}; //off, on DcsBios::SwitchMultiPos lcpAnticollision("LCP_ANTICOLLISION", lcpAnticollisionPins, 2); However when I then insert the status LED DcsBios::LED lcpAnticollision(0x1144, 0x0080, 12); I get a compiller error; Full sketch; /* The following #define tells DCS-BIOS that this is a RS-485 slave device. It also sets the address of this slave device. The slave address should be between 1 and 126 and must be unique among all devices on the same bus. */ #define DCSBIOS_RS485_SLAVE 4 /* The Arduino pin that is connected to the /RE and DE pins on the RS-485 transceiver. */ #define TXENABLE_PIN 2 #include "DcsBios.h" /* paste code snippets from the reference documentation here */ DcsBios::LED masterCaution(0x1012, 0x0800, 13); DcsBios::Potentiometer lcpFormation("LCP_FORMATION", A0); DcsBios::Potentiometer lcpAuxInst("LCP_AUX_INST", A1); DcsBios::Potentiometer lcpEngInst("LCP_ENG_INST", A2); DcsBios::Potentiometer lcpFlightInst("LCP_FLIGHT_INST", A3); DcsBios::Potentiometer lcpConsole("LCP_CONSOLE", A4); DcsBios::Potentiometer lcpFlood("LCP_FLOOD", A5); DcsBios::LED lcpAnticollision(0x1144, 0x0080, 12); //const byte lcpAnticollisionPins[2] = {3, 4}; //off, on //DcsBios::SwitchMultiPos lcpAnticollision("LCP_ANTICOLLISION", lcpAnticollisionPins, 2); void setup() { DcsBios::setup(); } void loop() { DcsBios::loop(); } Anyone got an idea why this is happening?? I admit that last time I tried it I used DcsBios::Switch2Pos lcpAnticollision("LCP_ANTICOLLISION", PIN); to activate the anti-collission switch but using that instead of the SwitchMultiPos also gives compiler error. Cheers Hans

This is a test we did on 1.2.9.7; Cheers Hans