December 10, 200421 yr Hi everybody!I need help from some fsbus specialists!I want build a homecockpit with an overhead panel.The software for the overhead is the hcsdt software (OHL-logic)For the controlling i want use a keyboard (USB).Now i want see the position of the switch with a LED.z.B. APU-Master Switch LEDI define an LED in FSBUS but i don
December 10, 200421 yr We need more informations because I don't understand really want you wanna do ...You build and Overhead panel with switches which are connected to your PC by a USB-keyboard to drive a software which emulate the functions of the panel ... it that correct ?First of all using a keyboard you'll just emulate toggle switchSecond FSBUS can link LED only to an FSUIPC offset or direct an FSBUS KEY so if you software HCSDT use its own offsets and you've the specification in the docs or the SDK of the software it's OK you can easy add these offsets into the command menu of FSBUS and assign it to a LED.But if it don't I don't know how to read the information of the switch position for FSBUS led ....Tell us more ...BYeBOB
December 10, 200421 yr Thats it correct!The connection between the Overhead and the computer via USB is not the problem!The problem is the LED! How can i light them via FSBus.How can i get the FSUIPC offset in the fsbus.fb or programm!In the documentation of the HCSDT-Software is an offset adresse includet but i don
December 10, 200421 yr If you've the offset of the Soft which encode the status of the ledIt's easy to add it in the FSBUS function:Extract of the read-me file of FSBUS---------------------4. The file fsif.ini contains all predefined fsuipc values. It comes with fsbus setup and is overwritten each time an update is made. To maintain and keep own extensions, you may add your extensions to "myfsif.ini". Fields from left to right: Lvl hierarchical depth of a parameter. Top Level is 0, which is shown below "MyFS" Name the name of the parameter as shown in Explorer ID internal id of parameter. Must be between 0 and 299 Mode not used Offset offset as defined in fsuipc Type type of data (I8,I16,I32,I64,DOUBLE,BIT,STRING) Opt if type = BIT, this is the bitnumber flags various flags for this parameter R read value from fs W write value to fs + add the object value to the fs value D delayed read back of a previous written value scan how often is this parameter polled. mul multiplier for the value div divisor for the valueExample:========0, "MyOffset", 1, 0, 0x0b74, I32, 0,RW, 50,1,82321,------------------------------You just have to create your own offset list in "myfsif.ini" fileMaybe you've to make some test to find the good Type (I8,I16...)I'll post you a part of my own Myfsif.ini file. Maybe some functions are not working I'm testing it ...0, "Engine"1, "Left Prop RPM",1,0,0x2400,DOUBLE,0,R,50,1,11, "Right Prop RPM",2,0,0x2500,DOUBLE,0,R,50,1,10, "Surface controls"1, "FlapsLeftIndicator",3,0,0x0be0, I32,0,R,1,1,11, "G-Force",4,0,0x11ba,I16,0,R,1,1,11, "Prop 1 Autofeather armed",29,0,0x2430,I16,0,RW,50,1,11, "Prop 2 Autofeather armed",30,0,0x2730,I16,0,RW,50,1,10, "Gauges"1, "Succion pressure",7,0,0x0b18,DOUBLE,0,R,1,1,10, "Electric"1, "Total Load amps",31,0,0x2824,DOUBLE,0,R,50,1,11, "Battery amps",32,0,0x282c,DOUBLE,0,R,50,1,11, "Battery volt",33,0,0x2834,DOUBLE,0,R,50,1,11, "Main Bus volt",34,0,0x2840,DOUBLE,0,R,50,1,11, "Main Bus amps",35,0,0x2848,DOUBLE,0,R,50,1,11, "Avionics Bus volt",36,0,0x2850,DOUBLE,0,R,50,1,11, "Avionics Bus amps",37,0,0x2858,DOUBLE,0,R,50,1,11, "Hot Battery Bus volt",38,0,0x2860,DOUBLE,0,R,50,1,11, "Hot Battery Bus amps",39,0,0x2868,DOUBLE,0,R,50,1,11, "Battery Bus volt",40,0,0x2870,DOUBLE,0,R,50,1,11, "Battery Bus amps",41,0,0x2878,DOUBLE,0,R,50,1,11, "Alt 1 Bus volt",42,0,0x2880,DOUBLE,0,R,50,1,11, "Alt 1 Bus amps",43,0,0x2888,DOUBLE,0,R,50,1,11, "Alt 2 Bus volt",44,0,0x2890,DOUBLE,0,R,50,1,11, "Alt 2 Bus amps",45,0,0x2898,DOUBLE,0,R,50,1,10, "TEST"1, "On Fuel Station",8,0,0x032c,I16,0,R,50,1,11, "Engine 1 active",10,0,0x032c,BIT,0,RW,50,1,11, "Engine 2 active",11,0,0x032c,BIT,1,RW,50,1,11, "failure Altimeter",12,0,0x0b66,I8,0,RW,50,1,11, "failure HSI",13,0,0x0b67,I8,0,RW,50,1,11, "failure COM1",14,0,0x0b68,I8,0,RW,50,1,11, "failure Electrics",15,0,0x0b6a,I8,0,RW,50,1,11, "failure engine1",16,0,0x0b6b,I8,1,RW,50,1,11, "failure engine2",17,0,0x0b6b,I8,2,RW,50,1,11, "failure fuel gauge",18,0,0x0b6c,I8,0,RW,50,1,11, "failure gyro",19,0,0x0b6d,I8,0,RW,50,1,11, "failure VSI",20,0,0x0b6e,I8,0,RW,50,1,11, "failure XPNDR",21,0,0x0b6f,I8,0,RW,50,1,11, "failure NAV1",22,0,0x0b70,I8,0,RW,50,1,11, "failure NAV2",23,0,0x3bd6,I8,0,RW,50,1,11, "failure pitot",24,0,0x0b71,I8,0,RW,50,1,11, "failure TC",25,0,0x0b72,I8,0,RW,50,1,11, "failure vacuum",26,0,0x0b73,I8,0,RW,50,1,11, "EFIS on/off",27,0,0x0e5a,I16,0,RW,50,1,11, "GPS NAV switch",28,0,0x132c,I16,0,RW,50,1,11, "Standby Vacuum",46,0,0x2e90,I16,0,RW,50,1,11, "Propeller Synchro",47,0,0x2ec8,I16,0,RW,50,1,1Try and ask me if you've some problems ...ByeBOB
Create an account or sign in to comment