{"id":346,"date":"2022-09-19T21:24:48","date_gmt":"2022-09-19T11:24:48","guid":{"rendered":"https:\/\/avimator.net\/buildlogs\/?page_id=346"},"modified":"2022-10-06T22:38:58","modified_gmt":"2022-10-06T12:38:58","slug":"framework","status":"publish","type":"page","link":"https:\/\/avimator.net\/buildlogs\/framework\/","title":{"rendered":"Framework"},"content":{"rendered":"\n

DCS-BIOS Board ‘eco-system’<\/h2>\n\n\n\n

most basic requirement<\/h3>\n\n\n\n

A single Arduino board will suffice for a DCS-BIOS installation, an arduino board, communicating to DCS via USB connectivity, is more than suitable to do this, however it lacks any scalability as you add more pins…<\/p>\n\n\n\n

\"\"
single DCS-BIOS slave board<\/figcaption><\/figure>\n\n\n\n

the solution to this is a or a single (purpose built) DCS-BIOS slave board, also communicating to DCS via USB connectivity.<\/p>\n\n\n\n

then the next step…<\/p>\n\n\n\n

setting up for a modular \/ scalable framework<\/h3>\n\n\n\n

In order to make your DCS-BIOS framework scalable you will need to add <\/p>\n\n\n\n

1x single (purpose built) DCS-BIOS Master board <\/p>\n\n\n\n

Note: only the one master board is required for the entire framework<\/kbd><\/p>\n\n\n\n

+ at least 1x (purpose built) DCS-BIOS slave board (if you’re moving to a scalable solution, its more than likely though that you have already filled all the available output pins on a single card & now need a second slave board.<\/p>\n\n\n\n

Note: the master board can only provide the communication framework for the slave cards, it cannot provide ANY output pins to panels.<\/kbd><\/p>\n\n\n\n

\"\"
minimum scalable framework set<\/figcaption><\/figure>\n\n\n\n

you could also start out with a single master & slave board, if you know you will be expanding short term, realistically it’s not required until you need a second slave card.<\/p>\n\n\n\n

<\/p>\n\n\n\n

\"\"
second bus framework<\/figcaption><\/figure>\n\n\n\n

If you’re intending to, or currently building a full simpit or multiple consoles, optimally you will require at least one slave board per console.<\/p>\n\n\n\n

\"\"
fully populated bus framework (left \/ front \/ right)<\/figcaption><\/figure>\n\n\n\n

the pink board illustrated above is a special high capacity slave board that utilises a mega2560 (instead of a mega328) microcontroller, to allow for more pins available to a single board, this would be useful for panels that are highly saturated with required output pins, (such as a warning panel, with lots of individually lit LEDs) this board is not essential but available as an option.<\/p>\n\n\n\n

next step is populating panels to each board & adding extra slaves to each BUS to accommodate required pin outputs to each panel. <\/p>\n\n\n\n

\"\"
example framework<\/figcaption><\/figure>\n\n\n\n

The example above is probably a massive overkill for any DCS-BIOS requirement, this is simply to illustrate the scability, the actual maximum of slave boards is 128 boards….per BUS! (depending on signal integrity).<\/p>\n\n\n\n

Far more than than would ever be required by your average DCS aircraft module.<\/p>\n\n\n\n

More than likely you will be able to get away with a single DCS-BIOS slave board for each console for all but the most complex of aircraft.
Please refer to the AH64D example below.<\/p>\n\n\n\n

12 Volt DC power distribution<\/h3>\n\n\n\n

This DCS-BIOS board framework can also provide 12Volt DC throughout the pit, with a reasonable amount of current (< 2 Amps per BUS), suffice to run just about anything you could dream of within the pit; <\/p>\n\n\n\n