Hansolo

Nice work Sir. Perhaps this done by A10C-Wolf may be of interest for you; http://forums.eagle.ru/showthread.php?p=2842166#post2842166 Cheers Hans

Very nice job there DM :thumbup: My guess would be getting a 1:1 ratio LCD that fits inside the bezels. Cheers Hans

Hi hansangb, I haven't done anything to the DIFF.lua I am still using the 3000+ numbers in the default.lua file that I exchange the original with using JSGME. Then afterwards I map the buttons DCSW. DCSW will then alter the DIFF.lua accordingly. I think I did look into the DIFF at one time but couldn't find heads and tails on it. Not much I am afraid :cry: Cheers Hans

This should work; http://www.amvi.it/download238-dcsmp.html Cheers Hans

Very nice thread with lots of good info. Just found it. IMHO the issues is caused by what appears to be incorrect projection of the HUD image. HUD image appears to be projected in front of the aircraft and not on HUD glass itself. This is why if you move you head sideways you loose some of the image behind the support pillars for the beam, why you have to move you head closer to the get support beam bigger and then being able to see the HUD image. It may also be the reason why heat blur for other aircrafts affect you HUD which I presume it shouldn't. Anyway its just my belief. Cheers Hans

You are welcome. Glad to be of assistance Cheers Hans

Maybe this is what you are looking for http://forums.eagle.ru/showthread.php?t=131931 Cheers Hans

IMHO It will only show up when HUD is in NAV mode. Use the Master Mode control button switch on the stick for that. Cheers Hans

Should be possible Tekkx. Looks somewhat similar to what Robinmli and Patriot has used; http://forums.eagle.ru/showthread.php?t=163008 Cheers Hans

Totally agree :thumbup: Rep inbound. Sir Cheers Hans

Reproduction Spitfire panels? http://www.ebay.com/itm/REPRODUCTION-RAF-WW2-SPITFIRE-MK9-Main-Instrument-Panel-/322208196884?hash=item4b051ae914:g:UxMAAOSwgY9XePyE http://www.ebay.com/itm/REPRODUCTION-RAF-WW2-Aircraft-Curved-Top-Blind-Flying-Panel-SPITFIRE-etc-/322203047565?hash=item4b04cc568d:g:SJcAAOSw6aVUpUGW http://www.ebay.com/itm/REPRODUCTION-RAF-WW2-Aircraft-Flat-Top-Blind-Flying-Panel-SPITFIRE-etc-/322203043160?hash=item4b04cc4558:g:hccAAOSw9uFW9WGj

Ha ha @escaner, copy that :thumbup: I usually don't run into fuel problems with the Hog either. Last time was probably during a very cool mission AMVI hosted where there was a flight into the AO of about an hour. Mostly our own missions we have a fixed landing time which would give us a tie on station of about 1½ hours for CAS. I should have written more clearly. The download link probably works but I will not try it. There was a warning/cautioning a while back about the distribution of that manual, http://forums.eagle.ru/showthread.php?t=60293&page=9 Cheers Hans

Thanks @Aginor. Was pointed towards it by Energy or IronHog from 476th. Not sure I understand the die part? You mean it cannot fly with that AOA or I will be very old when reaching the destination? I am afraid that I cannot download. As far as I have understood on previous thread that is a classified/restricted doc :cry: Cheers Hans

If you want to you can use your AOA indicator in the Main Instrument Panel for fuel optimization; AoA for cruising: 15-16, AoA for maximum endurance: 17-18 (may come in handy for loitering) AoA for landing approaches: 19-20-21 Please check out the full article here; http://kriegsimulation.blogspot.dk/2010/10/dcs-10c-warthog-angle-of-attack-watch_24.html Cheers Hans

Gentlemen please calm down and please refrain from using facepalm smileys. IMHO they don't really contribute anything :-) Lets keep the thread civilized. ClayM thanks for your opinion. You have a very nice pit and I always enjoy reading your progress on it. The size of the pit has previously been raised as a problem for some and the truth is that this setup just isn't for everyone. Luckily there are other options for a pit. Y2KIAS plans are for a swing out type full pit but sizewise the same as DM's. Dimebug's plans on the other hand offer a more essential pit layout with just the MIP and side console which offers the builder the option to take it part relatively easy. It sound like you have done it like this which is also how Tacno has done his setup. There is a nice YT where he puts his together in 10 minutes, ] And as you mentioned there will always be some kind of compromise when building a pit. Deadman, I understand your frustration. There was a lot of interest in the plans way back. Perhaps looking in hindsight the interest were more related to the side console than the pit itself. Or perhaps the layout wasn't fully explained in details. I for one still appriciate that you have made the plans available DM and allowed me to distribute to the community. Now every builder has a broader variety of option to choose from. Let us not forget that in the end it is the builders personal preference, capability, space, availability and needs that defines his/her pit. Some goes full monty others make a single panel with a few buttons and so on. They are pits in my book and I enjoy reading about all of them :-) Enjoy your summer All the best Hans

Have you tried to lean forward? It may just be that the you do not see the full HUD when doing Concent Release. You may be able to see that I lead forward on this small test; [ame] [/ame] Don't pay attention to the poor SEM. Cheers Hans

Thanks for sharing. Rep inbound Cheers Hans

Nice clean job Eamoe :thumbup: Cheers Hans

Perhaps also download 476TTP3-3.A-10C found here; http://forums.eagle.ru/showthread.php?t=165469. Direct download is here; http://www.476vfightergroup.com/downloads.php?do=file&id=376 IMHO it is some of the info in the two threads posted by Eddie but collected into one unified chapter '5 Air to Surface Employment'. Cheers Hans

That backlighting looks really awesome Sir. Well nailed romeokilo. And I see you changed STEER PT and PAGE into 45º turn switches. Keep em comming :thumbup: Cheers Hans

Hi Warhog, Thank you very much. I think it makes very good sense to use 3 Mega for a pit :thumbup: Based upon your good info I think I may actually go for a MiniPro per panel with a Mega for each mayor component. Then I should even get anywere near 32 units per RS485 string. Thanks a lot for sharing your experience. I have only begun to scratch the surface so its really appriated :-) All the very best Hans

:thumbup: that is exactly how I have done it in the past :-D You are most welcome Clay. @John a small question regarding RS485 if I may. As far as I have understood we can connect up to 32 units to the RS485 bus. Do you have an idea whether that be enought for all the panels or do you anticipate that some of them are combined? Cheers Hans

Looks very nice Warhog. Cheers Hans

Hi ClayM, It may not be of much assistance but in the experiemental version of DCS-BIOS I actually managed to get the MCP23017 to work use the sketch found here; http://docs.macetech.com/doku.php/centipede_shield Now granted that Ian did say that I could make it work the 'old' in later versions my programming skill level or lack of same did manage to get it working. I think this was my original code fr NMSP which include connections via Ethernet shield to the Uno; #include <DcsBios.h> #include <Servo.h> #include <SPI.h> // needed for Arduino versions later than 0018 #include <Ethernet.h> #include <EthernetUdp.h> #include <Wire.h> #include <Centipede.h> /**** Change these values to the IP address to assign to your Arduino and the IP address of your DCS computer. Make sure that the IP address you assign to your Arduino is on the same network as your DCS host. If you make sure that the first three numbers are the same, you should be fine. You will also edit BIOSConfig.lua to send a copy of the export data to the IP address of your Arduino. ****/ IPAddress arduinoIpAddress(192, 168, 87, 120); IPAddress dcsHost(192, 168, 87, 104); // Enter a MAC address for your controller below. byte mac[] = { 0xDE, 0xAD, 0xBE, 0xEF, 0xDC, 0xB0 }; /**** Make your changes after this line ****/ Centipede CS; // create Centipede object /**** In most cases, you do not have to change anything below this line ****/ /* Instantiate a ProtocolParser object to parse the DCS-BIOS export stream */ DcsBios::ProtocolParser parser; /* Create an instance of the Udp class */ EthernetUDP Udp; void setup() { Ethernet.begin(mac, arduinoIpAddress); Udp.begin(7777); Wire.begin(); // start I2C CS.initialize(); // set all registers to default CS.portMode(0, 0b0000000000000000); // set all pins on chip 0 to output //TWBR = 12; // uncomment for 400KHz I2C (on 16MHz Arduinos) // Test of all lamps for (int i = 0; i < 15; i++) { CS.digitalWrite(i, HIGH); delay(500); } for (int i = 0; i < 15; i++) { CS.digitalWrite(i, LOW); delay(500); } CS.digitalWrite(1, HIGH); delay(2000); CS.digitalWrite(1, LOW); } /* Your main loop needs to pass data from the DCS-BIOS export stream to the parser object you instantiated above. It also needs to call DcsBios::PollingInput::pollInputs() to detect changes in the state of connected controls and pass them on to DCS. */ void loop() { // if there's data available, read a packet int packetSize = Udp.parsePacket(); if(packetSize) { for (int i=0; i<packetSize; i++) { parser.processChar(Udp.read()); } } // poll inputs DcsBios::PollingInput::pollInputs(); } void onDcsBiosMessage(char* msg, char* arg) { } /* You need to define void sendDcsBiosMessage(const char* msg, const char* arg) so that the string msg, followed by a space, the string arg and a newline gets sent to the DCS-BIOS import stream. In this example we send it to the DCS computer in a UDP packet. */ void sendDcsBiosMessage(const char* msg, const char* arg) { Udp.beginPacket(dcsHost, 7778); Udp.write(msg); Udp.write(' '); Udp.write(arg); Udp.write('\n'); Udp.endPacket(); } /* This subroutine gets called every time new data is received from the export stream (you need to define it even if it does nothing). Use this to handle integer outputs which are not covered by the DcsBios Arduino library. */ //void onDcsBiosWrite(unsigned int address, unsigned int value) { void onDcsBiosWrite(unsigned int address, unsigned int value) { if (address, "NMSP_ILS_LED" == 0) { // NMSP ILS if (value == '1') { CS.digitalWrite(6, HIGH); } else { CS.digitalWrite(6, LOW); } } if (address, "NMSP_TCN_LED" == 0) { // NMSP TACAN if (value == '1') { CS.digitalWrite(5, HIGH); } else { CS.digitalWrite(5, LOW); } } if (address, "NMSP_ANCHR_LED" == 0) { // NMSP ANCHOR POINT if (value == '1') { CS.digitalWrite(4, HIGH); } else { CS.digitalWrite(4, LOW); } } if (address, "NMSP_STEERPT_LED" == 0) { // NMSP STeer PT if (value == '1') { CS.digitalWrite(3, HIGH); } else { CS.digitalWrite(3, LOW); } } if (address, "NMSP_TISL_LED" == 0) { // NMSP TISL if (value == '1') { CS.digitalWrite(2, HIGH); } else { CS.digitalWrite(2, LOW); } } if (address, "NMSP_EGI_LED" == 0) { // NMSP EGI if (value == '1') { CS.digitalWrite(1, HIGH); } else { CS.digitalWrite(1, LOW); } } if (address, "NMSP_HARS_LED" == 0) { // NMSP HARS if (value == '1') { CS.digitalWrite(0, HIGH); } else { CS.digitalWrite(0, LOW); } } } Anyway you may very well be able to find the missing link which I never did :-) Cheers Hans

You can't delete mark point in moddeled suite of the A-10C. I think it is introduced in the real aircraft but in a later suite. Can't remember which suite. If you use up the alphabet the the CDU will just write data into your first made one i.e Mark A and so on. And if you have slaved TGP to STPT and go from MARK to FLT PLAN on STEER PT knob on your Aux. Avionics Panel your TGP will go into TGP XR ERROR (http://forums.eagle.ru/showthread.php?p=2825383#post2825383) Cheers Hans