Well, do remember one thing, if your lights work with BMS without DCSbios, then these lights should work on their own with DCStoF4 without DCSbios with DCS

The same was true for my simshaker issue:

- Simshaker has 2 versions depending if you use DCS or BMS
I was using the DCS version that required a declaration in the DCS scrip file which as I said above, does not work
But basically, The simshaker BMS version works with DCS as well through DCStoF4 and that one does not required the script.
So you basically can avoid the declaration in the script file and have the simshaker work through BMS shared mem, like the rest of things

The trick is to have as few as possible declarations in that scrip file of BMS to avoid potential conflicts, pass everything through BMS sharedmem with DCStoF4 and it works much better.

You'd think that...but I've been doing software testing for aircraft avionics and systems for 35 some years now and watching the screw-ups due to over-reach almost daily.  Which usually begin with - "it's just software".  Best approach is to select the best approach for the tasking.

I totally agree with doing a lighting controller/box because that's what they do on a real jet...but it's a chunk of hardware and on software is involved.  At least for Interior Lighting.

But my thoughts for my pit have more to do with functions or operational procedure not included in BMS base software that can be easily incorporated with wiring.  Some of my thoughts on lighting and power management fall into that category.

Don`t make just what your sim does, make all that is available, no matter if actual used or not

+1   

(that is, make it "future-proof")

Are there any plans or measurements for the bits where the switches are mounted?  Would be nice if I can 3D print these and get them working.  I believe I already have a copy of the spider switch and the hinge assembly to connect it to the cockpit, but that's it.

I've just tried it with version V0.10.0 and no problems.
The DCS-BIOS WEB page displays the DCS F-16 instrument values in real time. And DCStoF4 too.

The .lua export file looks like this:

-- Data export script for DCS, version 1.2.
-- Copyright (C) 2006-2014, Eagle Dynamics.
-- See http://www.lua.org for Lua script system info
-- We recommend to use the LuaSocket addon (http://www.tecgraf.puc-rio.br/luasocket)
-- to use standard network protocols in Lua scripts.
-- LuaSocket 2.0 files (*.dll and *.lua) are supplied in the Scripts/LuaSocket folder
-- and in the installation folder of the DCS.

-- Expand the functionality of following functions for your external application needs.
-- Look into Saved Games\DCS\Logs\dcs.log for this script errors, please.

--dofile(lfs.writedir()..[[scripts\WitchcraftExport.lua]])

-- DCStoF4
local xflight=require('lfs');dofile(xflight.writedir()..[[Scripts\DCS-XFLIGHT\Util-Dial.lua]])
-- WinWing
local wwtlfs=require('lfs');dofile(wwtlfs.writedir()..'Scripts/wwt/wwtExport.lua')
-- TacView
local Tacviewlfs=require('lfs');dofile(Tacviewlfs.writedir()..'Scripts/TacviewGameExport.lua')
-- Helios
--dofile(lfs.writedir()..[[Scripts\Helios\HeliosExport16.lua]])

--dofile(lfs.writedir() .. [[Scripts\DCS-BIOS\BIOS.lua]])
--[[DCS-BIOS Automatic Setup]]
BIOS = {}; BIOS.LuaScriptDir = [[C:\Program Files\DCS-BIOS\dcs-lua\]];
BIOS.PluginDir = [[C:\Users\Sharknoir\AppData\Roaming/DCS-BIOS/Plugins\]];
if lfs.attributes(BIOS.LuaScriptDir..[[BIOS.lua]]) ~= nil then dofile(BIOS.LuaScriptDir..[[BIOS.lua]]) end

I'd notived you had disable helios lines, do you ever run it together successully? (I mean run DCStF4、DCSbios、Helios at same time）