Do not log, a tool for the advanced user's toolbox

This was done just to see if it could be made to work. ( too much coffee ☕, insomnia & boredom also contributed )
For the advanced FSUIPC user, gauge programmer, cockpit builder, lua tweaker etc.., a problem arises, at times, where the aircraft designer has code that constantly fires commands into the sim. 👎👎👎  

When it comes time to do some logging, for instance, to see what control is being fired, on user input, is tough to find in the FSUIPC console window. The [General] "DontLogThese=" entry in the FSUIPC.ini does a fine job of blocking these. 

Of course, you could do a text log of the Events (non-axis controls), open the log and find the offending controls and then build up an entry for  "DontLogThese=".
This lua does it automatically and appends to a text file, appending it so you can have a library of the offending aircraft.
An output example of my testing :

NOTES :
axis pan heading 66504
axis pan pitch 66503
mouse look toggle 66734
misc maddog 70646
---------------------------------------------

Fly The Maddog X MD-82 - North Central N760NC
[General]
DontLogThese=66557,66556,66523,66479,66478,66466,66463,66442,66239,65962,65836,65833,65832,65709,65708,65707,

PMDG DC-6B PMDG House (N6PM | 2017)
[General]
DontLogThese=66818,66659,66508,66073,66060,65786,

P-51D civ 'Providence Permittin'
[General]
DontLogThese=66508,66507,65764,

Lockheed Constellation L049, C69
[General]
DontLogThese=66507,65922,65921,65920,65919,

666 F-16D AK375 F
[General]
DontLogThese=66707,66073,66065,66057,66031,

When needed :
1) Assign a temporary key to run the lua (as you named it)
2) Run it with the aircraft loaded, keeping your hands off of any controls ( axis or other )
3) When its done, it will report so, making, or appending, a file named "NoLogReport.txt" in the modules folder (or wherever FSUIPC is installed)
4) Copy the aircraft's report and paste in to the FSUIPC.ini [General] section, replacing the line if already there. 
5) In the FSUIPC UI, go to the Axis Assignment tab and click on Reload All Assignments. Done, the offending controls are now blocked. 
This was only tested in FSX, I would imagine it would still work from FS9 thru P3Dv4+.
The lua :

-- USER SETTINGS
local startCtrl = 65537 	-- THE STARTING CONTROL NUMBER TO BE SCANNED
local endCtrl = 68309 		-- THE ENDING CONTROL NUMBER TO BE SCANNED
local runTime = 3				-- RUN THE CONTROL RECORDER FOR HOW MANY SECONDS, >= 2 (NOT REALLY LEGIT, THERE IS A "LOT" OF BACKED UP FUNCTION CALLS!)
-- END USER SETTINGS

local cntrlsOut = {}
local doesContain = 0
local acftTitle = ipc.readSTR(0x3D00, 256)
acftTitle = acftTitle:gsub('%z','')
local outString = "\n\n" .. acftTitle .. "\n[General]\nDontLogThese="

function logControl(controlnum, param)
	doesContain = 0
	for _, value in pairs(cntrlsOut) do
		if value == controlnum then
			doesContain = 1
		end
	end	
	if doesContain == 0 then
		table.insert(cntrlsOut, 1, controlnum)
	end
end

function countDown(timer)
	if runTime == 0 then
		file = assert(io.open("NoLogReport.txt","a+"))		
		for i = 1, #cntrlsOut, 1 do		
			outString = outString .. cntrlsOut[i] .. ","			
		end		
		file:write(outString)
		file:close()
		ipc.display("Modules\\NoLogReport.txt was created", 1)		
		ipc.sleep(1000)
		
		-- !!! OPTION, OPEN UP THE REPORT.TXT AND FSUIPC.INI
		-- !!! UNCOMMENT & CHANGE THE PATHS OF YOUR PREFERRED EDITOR AND OUTPUT FILE(S)
				-- handle1, error1 = ext.runif("E:/Notepad++/notepad++.exe","G:/FSX/Modules/NoLogReport.txt")
				-- handle2, error2 = ext.runif("E:/Notepad++/notepad++.exe","G:/FSX/Modules/FSUIPC4.ini")
		-- !!! UNCOMMENT IF THE ABOVE DOES NOT WORK, PROVIDES ERROR DISPLAY
		-- ipc.display(handle1 .. error1 .. "\n" .. handle2 .. error2, 0, 5)
		-- ipc.sleep(5000)

		ipc.exit()
	end
	runTime = runTime - 1
end

for i = startCtrl, endCtrl, 1 do
		event.control(i, "logControl")
end

event.timer(1000, "countDown")

Roman

[Originally posted in old SimMarket support forums by Roman / spokes2112]