Warhog

Not directly and not without reprogramming the mega, which, if you have to ask, you should probably stay with the BBI board until you have more programming skills.

Hans is 100% correct. The mega, when used as a master, cannot be used for anything else. One other note, make sure you use the most current version of DCS BIOS.

In response to your first question... I run a 65” 4K Sony TV with a 1080ti (see signature below) and I would typically see +100 FPS. As soon as I added two 7” 1024 displays for my MFCDs and a small display for my CDU, frame rates dropped below 45fps. It’s still a smooth animation so it’s not really an issue. Can't help with your 2nd question.

Besides running DCS BIOS with several handfuls of Pro Minis, RS-487 chips and at least 4 Arduino Mega’s in my cockpit, I also run 2 BBI-64 boards for my MFCDs, F1 thru F12 keys and a bunch of rotary encoders. They are nice boards, easy to use but not as versatile as Arduino boards with DCS BIOS in the mix. They are also a tad expensive in my opinion. However, they do allow the novice builder to get some switches and rotary encoders working without having to deal with a lengthy learning curve.

Not sure if this has been mentioned in this thread yet... although we call this an RS485 bus, you should use the RS487 Chip and not the 485 chip. Please don't ask why. I just know that when Ian wrote the code for the bus, he had determined that the 487 chip would be the optimal choice

Sorry, I miss read your issue. Don,t have any idea why that’s happening. I run two 7” displays for my MFCDs as well but never had an issue as you have described. If I might suggest... Try adjusting the contrast and brightness of your small screens until the Mav page reads well. Then check your tgp and tad pages. It may be your tgp and tad pages are not that affect by the change. Otherwise...:dunno:

The Slaw Pedals are built to a whole different level than any other commercial product. That’s one reason they are so expensive. I've gone through at least four sets of rudder Pedals over the past number of years. My RX Viper Pedals by Slaw are built so well they will definitely outlive me. Don't second guess your decision to buy them. You’ll see what I mean when they arrive.

It’s 100% normal for the AGM-65D. The seeker head for the D model is returning exactly what it is seeing...an infrared image. This is why the AGM-65D works in bad weather and at night or when your above the cloud layer.

I wish I could be more help Linden, but lua is way beyond my pay grade. I don't know why it wouldn’t work since all it’s doing is exporting info much like Tacview and Helios would do.

Don't see why you couldn’t. Each one has its own lua code which the export.lua file would reference. But Helios, from my own experience, created lag issues when I used it with DCS. It was so frustrating, I removed it entirely from my PC. It’s also what motivated me to use DCS BIOS for my cockpit as it was so easy to program Arduino boards and there was excellent documentation for DCS BIOS.

@Goblin... I never bothered with a build thread. However, everything I've built has been photographed in various stages of completion and can be found in my signature. @Trubshaw... AutoCAD to design. CamBam to develop G-code. A decent CNC machine to cut virtually every part of the cockpit. Besides learning AutoCAD and CamBam, learning electronics and programming is an absolute must. It may sound daunting but this has been a 4 year build up to this date mostly because of what you need to learn. @romeokilo... At the moment I haven't given much thought to the seat and associated controls. I may actually opt for the most comfortable seat I can find and modify it to suit the cockpit rather than go 99% authentic. @BuzzU... Say what! :huh:... You mean there are other planes to fly... :doh: Guess I'll have to build another cockpit... or two. :bounce:

Its getting closer to being finished. :D Still a few gauges/instruments to calibrate and install. The consoles and the MIP are all on casters so I can easily roll them out to work on them as required. The PC is located directly behind the MIP. I have a 12 port industrial based USB HUB mounted on the side of the PC to handle all of the extra devices I use. Most of the pit runs on DCS-BIOS (RS-485) however the MFCD's and part of the left console is using a BBI-64 from Leo Bodnar. I wanted to be able to reprogram the OSB's for other air frames and using the Bodnar HID made that easy to do. There's still a fair bit of work to do but I thought I might present what I have built to date. IMG_1065 by John Wall, on Flickr The display is a 65" 4k Sony which is set back around 36" from where I sit. When finished, the entire cockpit will be surrounded by black curtains to eliminate all visual distractions. IMG_1067 by John Wall, on Flickr I also splurged and purchased the Slaw Device RX Viper pedals. The pedals I originally built did not perform as I wanted and I was getting a bit frustrated with the idea of rebuilding them. I am so glad I purchased the RX Viper pedals. They are amazing in terms of build quality and performance. The price, however, was a bit of a stumbling block. But when I look at how long they will last compared to these lesser quality commercial offerings found in computer stores, it will indeed pay for itself in the long run. No regrets here. IMG_1068 by John Wall, on Flickr IMG_1069 by John Wall, on Flickr Please ignore the dust and sawdust on the consoles. They both need a good cleaning. I also need to paint the unfinished wood and I'll be adding that black fabric to the insides of the consoles. Notice that I included the Buttkicker amp/controller into the left console. I had the room so why not. It just makes things easier. IMG_1070 by John Wall, on Flickr IMG_1071 by John Wall, on Flickr I did break from creating a "replica" cockpit as I added some additional panels to help eliminate the need for a keyboard. I still have one available but its no longer required when I actually start to fly a mission.

Read post number 45 in this thread.

I just received mine last week. Although I haven't had a chance to replace my old Pedals with these beauties, I have to say... they are simply outstanding in every way. A work of art would be an understatement. If their build is a reflection of their performance I expect I will be suitably impressed. They were rather expensive but what do you expect when you buy the very best. Thank you Slaw Device. Update: They were installed yesterday and I now have several hours of flight time with them. My assessment... They perform as well as they look. Smooth motion with excellent precision. I have no regrets with their purchase regardless of price. They will last a lifetime. I could not be more pleased.

Why does ED need to replace the cockpit? Are we just talking about graphics or will there be enhanced features or new functionality added.

The buttons are cut from a sheet of styrene. The sheet is around 2”x3”. I normally cut 20 or so buttons at a time. I haven't been able to source styrene sheet in that thickness so i had to improvise. I glue thinner sheets together until I have the desired thickness. The glue used for styrene bonds the thinner sheets together into one solid, thick styrene sheet. The sheet of styrene is painted with grey acrylic paint. Once the paint has dried, I engrave the tops of the buttons. The sheet is flipped upside down and the mill hollows out each button. It’s then flipped over again and the mill cuts out each button. The styrene sheet has to be registered each time it’s flipped so the mill only cuts where it’s supposed to cut. Hope that helps.

There is a description in the very first post that lists all the steps required to make a button including backlighting the button.

I'm getting exactly the same device ID's as you are. I have a T-50 as well. The only saving grace is that they all have different numerical ID's so when you open the options page you can tell them apart. Not yet sure if they can be modified. But I haven’t given up . Will post solution if there is one.

Just remember to post pics of your build as you progress. It’s inspiring to see how builders solve problems and develop new techniques to handle the various situations that arise. Best of luck with your build.:thumbup:

Well Ian found the problem. There is a function in DCS BIOS that relies on a particular bit of code from DCS. Unfortunately, DCS 1.2 being rather old, does not supply that bit of code. As such, DCS BIOS cannot receive information from DCS 1.2. As you know, you can send info from toggle switch’s to DCS but you are not be able to receive anything in the way of indicators from DCS and that’s the reason why. The fix... use a newer version of DCS (at least 1.5) and everything will work as intended.

If you don't see any data scrolling in the socat window, then there is a problem. That data is the back and forth comms between DCS and the Arduino board. Without that data scrolling, you will not get any cockpit information sent FROM DCS.

You are doing an amazing job Calum. The detailing in your work really shows the amount of thought you've put into each panel. It too bad we all live hundreds to thousands of miles away. It would be wonderful to see each others builds as in close up and personal like, sitting around with a beer, talking about all the things we fracked up during our builds. :lol:

Thanks for posting that info. I don't immediately see a problem with the sketch. Can you try another led indicator to see if its only the master caution led or if it is symptomatic of all inputs from LEDs. Also just make sure there is no pause active at the time you test. I always have the aircraft on the runway sitting with engines running when I test various panels and then I can easily take off if I need to test something in flight. Other than that I will ask Ian if he can diagnose the issue once he arrives here in Canada this Saturday. Probably won't be the same day due to jet lag etc.

Some questions for you: 1. Could you tell me where the above sketch came from? 2. What version of DCS-BIOS are you running? 3. What aircraft are you using when you run the sketch? 4. When you run the sketch is the aircraft actually running. Are you in active pause at the same time as the sketch is running?

Antivirus was turned off during installation...