Fritz

I installed the new FSUIPC Version 4.84 . What tells me the log? 498096 Exception 20 "DATA_ERROR", Ref 2672, Index param 1 on write SetData for "ADF SOUND" 3585028 **** WARNING! Free memory is very low! 3595074 **** WARNING! Free memory is very low! Should I increase my virtual memory? Best regards Fritz

At the cruising altitude the mod was disabled and on the ground enabled. Seems to work. Thanks for the help. Kind regards

The log-file says: 176359 *** LUA Error: C:\Microsoft Flight Simulator X\Modules\SetEmb.lua:4: attempt to index field 'readSD' (a function value) 177389 *** LUA Error: C:\Microsoft Flight Simulator X\Modules\SetEmb.lua:4: attempt to index field 'readSD' (a function value) 178372 *** LUA Error: C:\Microsoft Flight Simulator X\Modules\SetEmb.lua:4: attempt to index field 'readSD' (a function value) Regards

Had made ​​a mistake. :oops: Have now corrected the entry. It still does not work. Too bad.

In FSUIPC I entered: [Auto] 1=SetEmb I named the small program "SetEmb.lua" and placed it in the module directory. I have monitored the offset 0574 . Unfortunately, the ENB Mod do not switched off or or if I passed 4000 Feet.

I have assigned a joystick button to the keystroke Shift+F9 in FSUIPC. Now I can enable or disable the ENB Mod with this joystick button. The mod must be inside FS.

I already thought that this is an important point, however, difficult for me to answer. The ENB mod changes the display in FSX. There is a dll file must be copied together with an ini file into the FSX root directory. This Mod is frequently used in promotional videos for Scenerys which makes the presentation more realistic. On the ground this looks well but in the air, this seems too much bright, particularly when using a Beamer. For this reason I want to disable this mod in the air. Whether altimeter, or true altitude AMSL or AGL is the same. Which is best suited for it. Would be great if we could manage it. Regards

Hello, with Shift + F9, you can enable or disable an ENB Mod.I want to send this keystroke with Lua to this ENB mod when the hight of 4000ft is passed by. I want to ensure that the ENB mod is activated below 4000ft and above disabled. When the hight reaches 4000ft send Shift+F9 to the ENB Mod Is that even possible? If so, how do I program it? have no programming skills. Cheers Fritz

I mean the Master Warning which should flash 3 times when the autopilot is switched off in the A320. Please have a look at this video, you can see it at 1:21. http://www.youtube.com/watch?v=YR5-AWcZEWY In my system, the LED is connected to a FDS Interface Card. I could assign a free offset to the LED but I have no idea how I need to write the LUA-code to make it switch on and off three times. I hope you can give me some advice on that. Regards Fritz

Hi Pete, if I turn the autopilot off, the Caution LED should flash three times. Is it possible to realize this with Lua? If so, would you give me a hint how the code-line should look like? Regards Fritz

That does not sound bad but how does FSUIPC distinguishes between the rudder and tiller?

But you always controls nose wheel and rudder together. Not separated.

Yes, I mean nothing and it is also true that I have the internal variable from the log lvars.lua. I replaced ipc.writeLvar with ipc.macro. The Name of the Macro is IgnitionSwitch.MCRO. Now the Lua script looks like this: - Ignition Switch IgnitionSwitch function (offset, val) ipc.macro("L:IgnitionSwitch") end event.offset (0x66C0, "UD", "IgnitionSwitch) I see In the log that the value of offset 66C0 is set from 0 to 1 by operate the switch. The macro is not able to run. Is the ipc.macro line not correct?

First of all thank you for your help and for your patience. What I intend to do does not work because the internal variable triggers anything. So then I tried it with a mouse macro. With this I can trigger the Ignitionswitch, but must use an offset whitch I have to mapped to the macro. Now then if for example Offset 66C0 == 1 then execute the macro "Ignitionswitch". Is that also possible in Lua by event?

Yes, I mean L:FT_IgnitionSwitch. Thanks for the quick help but unfortunately I fail at the correct syntax. What is wrong here? -- Ignition Switch function IgnitionSwitch(offset, val) if ipc.readUD(0x66C0) == 1 then ipc.writeLvar("L:FT_IgnitionSwitch", 1) else if ipc.readUD(0x66C0) == 0 then ipc.writeLvar("L:FT_IgnitionSwitch", 0) end end event.offset(0x66C0, "UD", "L:FT_IgnitionSwitch")

The Wilco Airbus is working with many internal variables. My interface software works only with offsets. Now I want to assign an internal variable (for example FT_IgnitionSwitch) to an unused offset. I want to achieve if the Switch is pressed, the value of the offset (eg, on = 1) is transferred to the internal Vaiable (FT_IgnitionSwitch = 1). If this is pssible, how must the Sysntax in Lua look like? Thanks for any help.

Problem solved. I have assigned in the FSUIPC Spoiler Settings a value 0 - 4800 to the null zone. :D I found out that when the offset 0BCC is set to 1, the value jumps to 0 again. Therefore, in the position spoilers armed, the value 1 must been set for disarmed again. regards Fritz

To control the speed brake in my A320 cockpit, I use an on-off switch and a potentiometer. The on-off switch is for the offset 0BCC armed position. With the potentiometer I control the offset 0BD0 with the value between –16384 to 16384. When the potentiometer with offset 0BD0 achieved the value 4800, the FS interpreted this as the speed brake is in armed position. That would be as i was braking and accelerating my car at the same time. Is there any way in the FSUIPC settings to solve this problem? regards Fritz

You will not believe it but it runs now. :D I think the key note was ipc.sleep (500). I've changed it from 250 to 500 and now it seems that the third command is also running well. Many thanks for your help and especially for your patience. Regards Fritz P.S.: I hope that now the sun comes out again. :wink:

I 've tried to assign 3 actions to button 2 but it seems that the third action is not executed. Thats why Im asking you if this is generally possible. What I do not even understand that it is not possible to executed two consecutive queries in a loop like you did in your examples. -- Sidestick Prioritiy Airbus A320 while 1 do -- Sidestick Prioritiy light CPT/FO off when Autopilot is on if ipc.readUD(0x07BC) == 1 then ipc.writeUD(0x07C8, 1) ipc.writeUB(0x6DF1, 0) ipc.writeUB(0x6DF2, 0) end -- Sidestick Prioritiy CPT if ipc.readUD(0x07BC) == 0 and ipc.readUB(0x6DF1) == 1 then ipc.writeUD(0x07C8, 0) ipc.writeUB(0x6DF2, 0) end ipc.sleep(50) end If the autopilot is on than first loop is working. If I pushed the button than the loop stops and when I turn the autopilot on again than the first loop is working again. Now back to my current configuration. [Buttons.Feelthere Airbus A320-210 Lufthansa] ButtonRepeat=20,00 0=P0,2,Cx01006DF1,x01 1=P0,2,Cx010007BC,x00 2=P1,2,Cx01006DF2,x01 3=P1,2,Cx010007BC,x00 -- Sidestick Prioritiy Airbus A320 while 1 do -- Sidestick Prioritiy FO if ipc.readUD(0x07BC) == 1 then ipc.writeUD(0x07C8, 1) ipc.writeUB(0x6DF1, 0) ipc.writeUB(0x6DF2, 0) end ipc.sleep(250) end I'm curious how we can solve this by 'events' Regards Fritz

I'm not ignore your suggestions, I could not managed it. Sorry. I have tried many variants but could not solve the problem. As you have suggested, I reduced the complexity. I use the simply loop in Lua and have assigned two offsets to each button . It worked well so far with exception to switch over from Cpt priority to FO priority and vice versa. Is it possible to assign more than two offsets to a button in the FSUIPC INI? That would be the easiest solution for me. Regards Fritz

Yes. That could be, yes. But I found out, that Offset 07C8 is changing, therefore I check the status of this offset. This would be the easiest way for me but I do not have expected. I have not yet understood where must I include this into program. Do I have add my query for like if x ~= MemoryOfX then if ipc.readUB(0x6DF1) == 1 then ipc.writeUD(0x07BC, 0) ipc.writeUB(0x6DF2, 0) end end or do I have to put the query (MemoryOfX) at first an then the other querys? regards Fritz

Thank you for your example. As I said with my very limited LUA knowledge i do not get this to working. I hope that I do not overstrain your patience. I want to try to explain the logic. Autopilot is on. If Cpt Sidestick priority button pressed then 1. the Autopilot should set off (07BC = 0) 2. the Autopilot light should set off (078C = 0) 3. the Priority light at the Cpt Side and the red arrow on the FO side illuminates (6DF1 = 1). 4. the Priority light at the FO Side and the red arrow on the Cpt side set off (6DF2 = 0). If then the Autopilot turned on again (with the button at the FCU) 1. the Autopilot should set on (07BC = 1) 2. the Autopilot light should set on (078C = 1) 3. the Priority light at the Cpt Side and the red arrow on the FO side set off (6DF1 = 0). 4. the Priority light at the FO Side and the red arrow on the Cpt side set off (6DF2 = 0). Autopilot is on. If FO Sidestick priority button pressed then 1. the Autopilot should set off (07BC = 0) 2. the Autopilot light should set off (078C = 0) 3. the Priority light at the FO Side and the red arrow on the Cpt side illuminates (6DF2 = 1). 4. the Priority light at the Cpt Side and the red arrow on the FO side set off (6DF1 = 0). Cpt has the priority and if FO Sidestick priority button pressed then 1. the Autopilot is still set off (07BC = 0) 2. the Autopilot light is still set off (078C = 0) 3. the Priority light at the Cpt Side and the red arrow on the FO side set off (6DF1 = 0). 4. the Priority light at the FO Side and the red arrow on the Cpt side illuminates (6DF2 = 1). FO has the priority and if Cpt Sidestick priority button pressed then 1. the Autopilot is still set off (07BC = 0) 2. the Autopilot light is still set off (078C = 0) 3. the Priority light at the Cpt Side and the red arrow on the FO side illuminates (6DF1 = 1). 4. the Priority light at the FO Side and the red arrow on the Cpt side set off (6DF2 = 0). Does this makes it more clear what I want to do . regards Fritz

I'm trying to solve the problem all day. I'm sorry but I don't know how I could explain it better. Here is an excerpt of the FSUIPC4.log. It seems that the loop runs endlessly when I press the Joy button. 221037 WRITElua 6DF1, 1 bytes: 00 . 221069 WRITElua 6DF2, 1 bytes: 00 . 221147 WRITElua 6DF1, 1 bytes: 00 . 221178 WRITElua 6DF2, 1 bytes: 00 . 221256 WRITElua 6DF1, 1 bytes: 00 . 221287 WRITElua 6DF2, 1 bytes: 00 . 221349 WRITElua 6DF1, 1 bytes: 00 . 221381 WRITElua 6DF2, 1 bytes: 00 . 221443 WRITElua 6DF1, 1 bytes: 00 . 221474 WRITElua 6DF2, 1 bytes: 00 . 221537 WRITElua 6DF1, 1 bytes: 00 . 221583 WRITElua 6DF2, 1 bytes: 00 . 221646 WRITElua 6DF1, 1 bytes: 00 . 221693 WRITElua 6DF2, 1 bytes: 00 . 221771 WRITElua 6DF1, 1 bytes: 00 . 221802 WRITElua 6DF2, 1 bytes: 00 . 221880 WRITElua 6DF1, 1 bytes: 00 . 221911 WRITElua 6DF2, 1 bytes: 00 . 221989 WRITElua 07BC, 4 bytes: 00 00 00 00 .... <== after pushed Joy Button P0,2 222036 WRITElua 07C8, 4 bytes: 00 00 00 00 .... 222067 WRITElua 6DF2, 1 bytes: 00 . 222145 WRITElua 07BC, 4 bytes: 00 00 00 00 .... 222176 WRITElua 07C8, 4 bytes: 00 00 00 00 .... 222207 WRITElua 6DF2, 1 bytes: 00 . 222270 WRITElua 07BC, 4 bytes: 00 00 00 00 .... 222317 WRITElua 07C8, 4 bytes: 00 00 00 00 .... 222348 WRITElua 6DF2, 1 bytes: 00 . 222441 WRITElua 07BC, 4 bytes: 00 00 00 00 .... 222473 WRITElua 07C8, 4 bytes: 00 00 00 00 .... 222519 WRITElua 6DF2, 1 bytes: 00 . 222566 WRITElua 07BC, 4 bytes: 00 00 00 00 .... 222613 WRITElua 07C8, 4 bytes: 00 00 00 00 .... 222660 WRITElua 6DF2, 1 bytes: 00 . 222738 WRITElua 07BC, 4 bytes: 00 00 00 00 .... 222769 WRITElua 07C8, 4 bytes: 00 00 00 00 .... 222785 WRITElua 6DF2, 1 bytes: 00 . 222878 WRITElua 07BC, 4 bytes: 00 00 00 00 .... 222909 WRITElua 07C8, 4 bytes: 00 00 00 00 How can I achieve that the loop runs only once when the condition is met? I guess the solution would be a short LUA command that I'm not aware of yet due to my very limited LUA knowledge.

Offset 6DF1 and 6DF2 I got from here http://pd-datentechnik.de/A320/pdf/Dualontrol.pdf. I had assumed that they are free Offsets. I modified the fsuipc.ini and ipcReady.lua once again. I think I'm very close to the solution but I produce an endless lop when I turn the autopilot on again. fsuipc.ini [Buttons.Feelthere Airbus A320-210] ButtonRepeat=20,00 0=P0,2,Cx01006DF1,x01 1=P1,2,Cx01006DF2,x01 ipcReady.lua -- Sidestick Prioritiy Airbus A320 while 1 do -- Sidestick Prioritiy FO if ipc.readUB(0x6DF2) == 1 then ipc.writeUD(0x07BC, 0) ipc.writeUD(0x07C8, 0) ipc.writeUB(0x6DF1, 0) end -- Sidestick Prioritiy CPT if ipc.readUB(0x6DF1) == 1 then ipc.writeUD(0x07BC, 0) ipc.writeUD(0x07C8, 0) ipc.writeUB(0x6DF2, 0) end -- Sidestick Prioritiy light CPT/FO off when Autopilot heading lock is on if ipc.readUD(0x07C8) == 1 then ipc.writeUB(0x6DF1, 0) ipc.writeUB(0x6DF2, 0) end ipc.sleep(250) end I use my own Airbus Homecockpit and I have the FCU and EFIS from CP Flight. I also use the Wilco Airbus in FSX. For usinge the FCU with the Wilco Airbus, I had to buy an extra module, because the Wilco Airbus works with many internal variables for which there is no standard offsets compatible. With FSInterrogate I found out which offstes I have to set that the autopilot (07BC) is turned off and the AP controllight in the FCU (07C8) extinguish. I hope it was a bit understandable why it is not so easy. Regards Fritz