Jackson5

Wow, that are quite some setups. I imagine you're never bored!! Lights behave different then whithout the GFPower.lua But as you said that might be because of mixing lua and GfConfig.... Yes, that is how it is supposed to work. I use the GFPower.lua to make sure all my modules are off when in cold and dark Cockpit. It's the one you provide with FSUIPC, with no alterations. The GF166's and the GF-LGT I have will never go Dark otherwise. Been doing that for quite some time now, never had problems Oh No, that was not intended to be part of a program or something, just wanted to see if I could get the lights on via a Lua Tried the same with one of my GF-T8's and that worked.... Also added some more lines to first set the color, then the brightness and then one of the buttons. Didn't work... The log saw nothing wrong... I must admit, I don't find it "Easy" ! I hope your GF-WP6 is delivered soon :wink: Best Regards, Jaap

That's great, I'm glad to hear they give you the opportunity do do some thourough testing. Just curious: do you have some kind of Cockpit setup to play around in, or does your interest solely lie in programming? Well I have been playing some with the GF-WCP6. Go-Flight also released new software v2.02, so the Master Caution function is now operative too. I have downloaded the new FSUIPC and WIDEFS you provided in your last post. The Button Programming now shows the expected info. Joystick and Button numbers are correctly recognized. I found the the GFPower.lua I always run at startup reacts strange to the WP6. I have assigned the WP-6 buttons with GFConfig to: Type-----------------Function 0- Master caution---None 1- Fuel Press------Caution 2- Gen Off---------Caution 3- Oil Press-------Caution 4- Volt Low--------Caution 5- Door -----------Caution If any of the last five button/lights is on, the Caution Button/Light starts to blink, until I press it. Whenever a new failure state arises, it starts to blink again. When aircraft is started and all failures have been delt with, all lights are off. When I start with GFPower.lua. The GF-WP6 is not dark as expected. The Master Caution is blinking and when I press it, it starts blinking faster. The other lights don't come on even if failures are present. All starts working normally after I start the APU and turn on the APU generator, but as soon as I turn those off, it's wrong again. Any Idea's? Also I tried to get the lights working via a simple LUA, but no luck so far. BTW. what should the Model designation be? GFWP6, or GFWCP? First I removed all button settings from GFConfig, and removed the ipcready.lua I have for starting the GFPower and GoFlightleds.lua from the modules folder, so nothing else would be starting. I tried this, saved as GF-WP6 Test.lua: gfd.SetLights(GFWP6, 0, On) Also tried GFWCP for model. But in both cases no lights went on. The Log shows that the lua started and ended normally. Must be doing something wrong? Best Regards, Jaap

Hello Pete, Sorry for my late answer, I have been working late the last couple days. Thanks for your hard work, I will test it out tomorrow, and see what functions I can assign to the buttons, and of course if I can set the lights! Have a nice evening! Jaap

Oh, hey. :shock: I must have loaded this page out of my cache or something, because it was not there when I opened it.... Just read it, and I am happy to test for you. There's no hurry from my side at all, just curiousity... And yes I have a Camera, so I can record everything that happens when testing! Let me know what to do when you are ready! Thanks! Jaap

Hi, Small question: Did you get around to solve the GF-WP6 problem today? Thanks, Jaap

Ah, that's great! Ok, I'll test. Hope it rains tomorrow! :rolleyes: Regards, Jaap

It does have six indicators and six buttons (indicators light up the buttons when activated, and colors are programmable via GFConfig), but there are no rotary dials or toggle switches on the device! This looks more like something they might still have in development? I have received my new GF-WP6 last saturday and have downloaded the latest GFConfig and also FSUIPC4 4.70B. FSUIPC does see the button presses, but (in my eyes) in an erratic way. LUA's Disabled, no assignments made in GFConfig All buttons are seen as being on Joy# 152 HW Button 1: first press BTN# 8 Second press BTN# 26, Third press BTN# 28, Fourth press BTN# 26, Fifth press BTN# 28 and so on. HW Button 2: first press BTN# 27, Second press BTN# 28, Third press BTN# 27, Fourth press BTN# 28 and so on HW Button 3: same as Button 2 HW Button 4: same as Button 2 HW Button 5: same as Button 2 HW Button 6: same as Button 2 I hope this makes sense to you, because to me it doesn't ! Thanks, Jaap

GF-WP6 is what it is called at the GoFlight website, but from what you describe it must be the same Device: 6 buttons, 6 indicators with programmable colors.... I'm sorry about assuming that code for this module would already be done in FSUIPC, because most of the times you're so blazingly fast with updating and implementing, that I never thought it would not be.... ;-) I hope GF-WP6 and GF-WPC are the same so you can continue working on it. Thanks for your comments! Regards, Jaap

I am anxious for that. It also seems that the GFPower.lua (as provided in the FSUIPC install) is not working as expected with the GF-WP6 module: for instance when I set ALT-Warn (ALT meaning alternator here) for one of the GF-WP6 buttons in GFConfig, the button light stays off when alternators are off (it should light up), and when flipping the alternator switches back and forth, the light only blinks briefly. When I don't start up with the GFPower.lua the lights work normal. Regards, Jaap

Dear Mr Dowson, I have written this small Lua, and allthough it does work, I would like to know if I did it in the correct way. It would not be the first time I get something working in a completely wrong or too complicated way....... This is supposed to handle GoFlight Led's when Aircraft doors are opened or closed, APU is started or stopped, APU generator is activated or de-activated. ______________________________________________________________________________________________________________________ function Doors(off, val) if logic.And(val, 1) ==1 then --Opening Doors (Offset 3367/ size1/ read only) gfd.SetLight(GFP8, 1, 0) --Door Led on else gfd.ClearLight(GFP8, 1, 0) end end function ApuStart(off, val) if logic.And(val, 99) >=99 then -- When RPM is at 99% or more (Offset 0B54/ size4/ read only) gfd.SetLight(GFT8, 0, 0) --Apu Led on else gfd.ClearLight(GFT8, 0, 0) end end function ApuGen (off,val) if logic.And(val,1) ==1 then --When Generator is activated (Offset 0B52/ size1/read only) gfd.SetLight(GFT8, 0, 1) --Gen Led on else gfd.ClearLight(GFT8, 0, 1) end end event.offset(0x3367, "UB", "Doors") --Doors Check event.offset(0x0B54, "FLT", "ApuStart") --Apu Starter event.offset(0x0B52, "UB", "ApuGen") --Apu Generator Active? ______________________________________________________________________________________________________________________ Thanks, Jackson

Hello, I have received an answer from Tegwyn West of VoxATC with a small file attachment. This file calle FSUIPCint.dll was to be copied into the VoxATC directory, overwriting the old one. After that VoxATC worked normally again! Phew! Maybe some other users can benefit of this too? Thanks, Jaap

Hello, Sorry to bother you again, but since I upgraded to FSUIPC 3.98 and started working with LUA's, my VoxATC UK 3.72 (FS9) program does not longer work correctly. Each time I try to load a Flight, I get "No Flightplan loaded in FS". Since then I've tried just about everything, like removing and reinstalling Voxatc, removing and reinstalling voicepacks, checking all cfg entries etc. etc. but could not get it to work anymore. Then tonight I started to think back about when this could have happened, and I came to the conclusion that the higher version of FSUIPC was a possibility. So I went back to version 3.817 (found in a backup), and Hooray it worked like it had never been faulty. But no more LUA programming in this version. Hmmm, not quite satisfactory. So I tried version 3.85 and restarted. Wham!! Problem back!! Back to 3.817 again: no more problems...... Did you hear of this yet? Could this be due to the LUA programming addition to FSUIPC? I would like to get VoxATC working, AND have the LUA programming active too (otherwise all the troubles of getting the small lua's to work were in vain, because I definately want to keep VoxATC)..... Could you look in to this? I have also mailed for support to VoxATC, but did not hear from them yet.... Regards, Jaap Both

I have merged the two files now, without problems. I am glad it all works now. Thanks for your help and all your Patience. Have a nice Vacation. Best Regards, Jaap

With the help of your lua file, I was able to make the programming for the generator switches, and as an extra the Altim Metric button: function Generator2(off, val) if logic.And(val, 1) ~= 0 then gfd.SetLight(GFT8, 0, 5) --Gen2 led else gfd.ClearLight(GFT8, 0, 5) end end function Generator1(off, val) if logic.And(val, 1) ~= 0 then gfd.SetLight(GFT8, 0, 4) --Gen1 led else gfd.ClearLight(GFT8, 0, 4) end end function MetricDisplay(off,val) if logic.And(val,16) ~=0 then -- value 2x2x2x2 gfd.SetLight(GFP8, 2, 5) --Metric led else gfd.ClearLight(GFP8, 2, 5) end end event.offset(0x3AB8, "UD", "Generator2") -- Gen2 event.offset(0x3B78, "UD", "Generator1") -- Gen1 event.offset(0x051C, "UW", "MetricDisplay") --Shows metric values in the GC Had some trouble because the offsets for the generators are 32 bit size 2, but with trial and error I got it. It works perfectly, and I even found that when I happen to flip a GoFlight programmed switch and thus the lua programmed lights go of, that after a minute or so doing nothing, the lights come on again. Not really as it should be, but for now I can live with that ! Next I wil try to merge your lua with mine, to make things more simple, or do you recommend to keep them apart? BR Jaap

I tried a couple of them and scanned the lines. Some things I do see, but other things are a complete blur at this time. I guess I have to grow and learn. Goflight seems to let more people down lately, I guess setting up their new website gave them more problems then expected..... I think I did not start GFPower more than once, only after I had assigned a button to start the lua, and reset FS I started the lua. But as I understand correctly, it should be started together with FS via ipc.Ready.lua only? Then I will try that again, because it is a very interesting lua to me! I will True, but my FS setup is for FS only, and all the other things I do are on a small laptop, so working with more programs at the same time can get a bit messy then, opposed to working on a three bigscreen machine (my FS PC) Ok, I wll try to understand that. In the mean time I changed it and edited my post immediately, but at the same time you were probably already answering it (wow, fast!) This time I use PM GC Keys(by Param) with parameter 22 and 23, and that works correct. Now I understand why whenever I was using the No Smoking or Seatbelts button, some glitch alwas happened on my GC displays (little jump but no noticable difference) Wow, you got me there. I think I have to read that 10 times before I even begin to comprihend... :oops: From my part you are now hearing a big sigh from relief! IT WORKS !!!! Boy am I glad with that, thank you so much. I have now moved it back to the previous GFT8 panel that is combined with a couple of GF functions. The GF functions on that panel are : Batt switch, Avionics switch, Engine 1 run switch and Engine 2 run switch. The FSUIPC programmed buttons are: No smoking sign, seatbelt sign, Generator 1, Generator 2. Of course GoFlight messes things up when I flip a GoFlight switch but that is a GoFlight issue, and when I have rearranged my Panels I will keep the FSUIPC programmed buttons on one panel, separated from the GoFlight programmed buttons. For now I can build on your lua to also get the generator switches to light up! Great, thanks again! Regards, Jaap

I understood that, and it was nice to see the test procedure go by. And I did take a look at the lines, but that did not really clear things up for me.... I use FSUIPC version 3.982. What I did was assign a temporary free button to start the lua program, turned everything off (batt, avionics etc), started the lua and turned on the batt. switch (GFT8). My PM displays went on, so did my GF-MCP (at low brightness as defined in the lua). Then I switched the avionics on (GFT8) and saw my GF-LGT light up, the brightness on the MCP went up and the avionics on PMRJ went on too. That was cool! Next I did nothing anymore, just watched my instruments. After a little while FS crashed, the screen turned black and FS came with an "FS encountered an error and needs to be restarted" or something like that. I thought the () were to indicate that something has to be filled in there, and leave out the () afterwards. Wrongly interpreted! I have a very hard time trying to understand this all, numbers, equasions and all that stuff doesn't get through to me. I just now figured out how to get a value from an offset from your explanation about x04FE : 2^7 means 2x2x2x2x2x2x2 It's clear that for doing these things, documentation is needed, and I have it all printed out and laying next to me. All FSUIPC offsets, including the PM ones, the LUA library references, FSUIPC docs, etc. But for me it's hard to get, that's the way it is, and also English is not my native language, so every once in a while I might translate some things in the wrong way. :oops: Correct, it should have been 22 instead of 1. I see now that I took the wrong offset, had to turn a page for that, because the descriptions of offset 04f4 were on the page before all the functions that I had laying open. It indeed says Glass Cockpit ND modes(write only)(*was* read ass well) :oops: So its offset x04fE that I must use. Your assumption was correct, I found out that GF numbers the modules from 1 and on. Also switch 3 was correctly assumed, only the other way around: switch 2 is smoking signs, and 3 Seatbelt signs. Also I understand the bit about the ipc.macro. I have tested the lua as you put it here, and it worked, but with a few strange effects: when I flip either switch (smoking or belts), both lights come on, and they never go off, until I flip another switch on the same panel (battery as example). I remembered reading somewhere that GoFlight is very picky about handling functions on modules that have both Gofllight and FSUIPC actions programmed. As this is the case with this particular Module, I moved the buttons and lights to a module that is not used by Goflight and now the lua looks like this: function operatelights(off, val) if logic.And(val, 256) then -- 256 = 2^8, bit 8 = no smoking gfd.SetLight(GFP8, 2, 2) -- Smoking Led else gfd.ClearLight(GFP8, 2, 2) end if logic.And(val, 128) then -- 128 = 2^7, bit 7 = seat belts gfd.SetLight(GFP8, 2, 3) -- Seatbelt Led else gfd.ClearLight(GFP8, 2, 3) end -- you could add tests for more bits in 04FE here end event.offset(0x04FE, "UW", "operatelights") But whenever I press either button both lights come on, and now because there is no GoFlight programmed button on that module, they never go off until I shut down FS. Nothing I know can make me figure out where this goes wrong. To get the "no smoking" sign on I use FSUIPC tab buttons & Switches: PM GC keys (byParam) param.22. This turns on the sign in both PMRJ displays But either way I try it, the leds on the GF panel both go on, and stay on still..... So close, but still no cigar...... I'll keep staring and trying. Thanks so far. Regards, Jaap

I did now..... Don't install. Clear! I am sorry I never really bothered to read any of the supplied documentation, but I did not have the need to because I always used FSUIPC in the simplest way, by using the buttons and axes programming from the modules menu, also because some programs I use require it (although unregistered) and that's about it. That way always worked fine for me, until I wanted to do something with my GF modules that was not possible from within the FSUIPC menu. That is why I first came upon GFDisplay. Furthermore I have been using an older verion of FSUIPC, and never felt the need to upgrade because it worked fine. Until everything crashed and I decided to get all new versions for all my software. I am sorry if I have offended you. I do not specifically prefer GFDisplay, but simply did not know of lua programming. At first I thought this was for FSX only... I've been at it most part of the day and tried the GFDisplay.lua. This lights up all my Modules in different ways. I also tried GFPower, because that interests me to get a real cold and dark cockpit, but this crashed my Flightsim completely about one minute after turning on the power and avionics. So I tried to start simple by trying to light up all the leds on one of my modules. From the LUA GFD library reference I took gfd.setlights and came up with this: gfd.setlights=GFT8, 1, on and saved that as GFLEDTEST with extension lua. Copied it to the modules folder and started flightsim. Assigned a button for lua GFLEDTEST and lua kill GFLEDTEST. Pushed the assigned first button, but nothing happened. Tried several combinations, and checked the FSUIPC log in between. I had some entry's like: ' "=" expected near GFT8', and 'malformed number near on' while trying, but with the line as above there are no failure entry's, but I did not succeed in lighting anything either. Obviously I doing something wrong, and I'm almost afraid to ask, but what? I have also tried this: if ipc.readUD(0x04F4)==1 then gfd.SetLight=GFT8, 1, 2 else gfd.clearlight=GFT8, 1, 2 end But this did not work, as you would probably see immediately. (I wish I would..) Regards, Jaap

Yes, it is on the same PC as FS. What about this LUA? How does this work and what do I need to use it? It seems even more difficult than GFDisplay to me. I have visited the LUA site and downloaded LUA 5.1.4., but if I understand it right I do not need this ? I couldn't even figure out how to install it..... Also I looked at your zipfile LuaPlugins with examples, it looks a little like the Opencockpits language, that btw. also goes way over my head if I would have to write that without the config_Sioc program. Can you point me in the right direction? Thanks, Jaap

Hello everyone, Can someone help me with this? I want to light up one of the LED's on a GF-T8 panel when I turn on the Smoking sign. I now do that with FSUIPC buttons & Switches via PM RJ glass cockpit offset x04f4, parameter x000001A5 (22). When I flip the switch, the sign goes on, but of course the led on the GF-T8 stays off. So I found Pete's program GFDisplay, and must have read the pdf manual about ten times now, but I still don't understand how to do it. Can you help me with the above example (I want to do more buttons, but once I have a clear example I'll figure it out)? -What needs to be in the GFDisplay ini -Once its there, do I only have to run GFDisplay, or do adjustments need to be made to FSUIPC too? Sorry for being so dumb to not figure it out myself... BR Jaap

Hello Again, The problem is solved! It works again as it used to. With Ghostreader I was able to open a very old backup, and I started to compare the Modules folder in FS with what I had in the backup: There was an file called GFmcp2k4.ini missing ! Only four little lines: [Main] Config=E:\GoFlight\DefaultFS9.gfc 3piWrapper1=E:\GoFlight\GF3pLvlD.dll 3piWrapper2=E:\GoFlight\GF3pPM.dll As soon as I copied the file back to the modules folder and started FS, it worked again ! Yippie! :D I guess the GoFlight installer somehow 'forgot' to install it. Still no contact with GoFlight support, but as soon as I do I will report this, so they can check it. Anyway, thanks for your great support; you were right again, it had nothing to do with FSUIPC! Best Regards, Jaap

I did not program anything in FSUIPC, I never did before, because it wasn't required. I use the GFConfig program to tell the GF MCP PRO that it is going to be used wit Project Magenta, that's all Could very well be. But that's the strange thing. Other than that I had to reinstall the main FS PC (that runs FS2004 with FSUIPC and GF software), I never changed anything on the other PC's. I only installed the newer versions of FSUIPC, Wideserver, GFConfig (the GoFlight software) on the main FS PC, and a newer Wideclient on the other PC's True, and I have nothing to say otherwise, but the only difference between my setup before the crash and the setup now, is a different version of FSUIPC. As I said above, the GoFlight MCP is set for operation with Project Magenta with the GFConfig program. I don't know if you are familiar with GFConfig, but it's is a program that starts a GUI in which you can tell what each button on GoFlight modules must do when activated. For the MCP there is not much choice: You can set Project Magenta, FS Default, Level D 767 and Compatible addon. So I presumed that FSUIPC was handling the communications between PM and GF..... I always believed that the PM software could run on any PC and interact via WideFS with other software, so I cannot say if both should be on the same PC. But before the crash it DID work that way....... Luckily I found an older FSUIPC version on one of my backups (v3.85), and I hope that I have some spare time tomorrow evening to give that a try. It's my last resort. I can't get a hold of GoFlight support, don't know what's going on there, but they never answered my inquiry..... Thanks for your insights! Regards, Jaap

Hello, I have a problem that i can't solve: Since my main Flightsim computer crashed, I needed to reinstall my OS (XPsp2) and Flightsim 2004. Before the crash, everything worked fine, but now I cannot get my MCP-Pro panel to work anymore. To explain what my setup is about: FS2004 is on my Main PC, together with Go-Flight software, WideFSserver and FSUIPC of course. The second PC has PMRJ, PMSounds, GFKeys TheRealCockpit software and WideFS. The third PC has PMRJ, Opencockpits sioc, GFKeys and WideFS The Fourth PC has PM-MCP, PM-CDU and WideFS It was only my main PC that was reinstalled, and I installed it exactly the same as before. All communications are in order (according to PMFileCheck), all other GoFlight panels and buttons work as expected. In the GFConfig program all seems well, all devices recognized and properly set. Because I downloaded all new versions I now have: FSUIPC registered v. 3.982 WideFS registered v 6.78 Client version 6.795 GoFlight software v 1.90 PM-MCP build 447 What happens when I startup: I set GF-MCP Pro to Project Magenta, start all the client software on the other PC's and next FS on the main PC. A soon as the "create a Flight" menu appears, the GF-MCP shows minus signs in the displays. When I start the flight everything on the MCP goes dead. Nothing at all, not even after pressing the buttons. There seems to be no cummunication between the GF-MCP and PM-MCP, because when I set a button on either one, there's no reaction on the other one. However when I open the FSUIPC window and select buttons & switches tab, and press a button on the GF-MCP, FSUIPC sees it..... What I have tried: -Went back to GF software 1.81 (the one I used before the crash) -Set the GF-MCP to Flightsimulator instead of Project Magenta. Then the display stayed on during Flightsim, but still no communication between the GF MCP and PM MCP... -Tried different versions of FSUIPC from 3.98 to 3.982 and 3.983 (I used to have version 3.85, but replaced it with the newer version, so it's gone I'm afraid) -Tried different versions of WideFs, 6.78 to 6.795 for the client All this did not do the trick. And because I have no Idea what's causing this, I don't know what to do other than ask for help.... My suspicion lies with the version 3.98 of FSUIPC, because at this time that is the only bit of software that is different from my previous setup, but I can't tell if that's true.... I hope you can help! Regards. Jaap Both

That's exactly it. PMSystems is not (yet) designed to be used with the Learjet 45. So I need to use FSUIPC buttons and switches, select "Offset byte set" 0x560f and set the parameter. I have learned that this Offset has three positions: 0 for Off, 1 for On and 2 for Start. Do I just fill in 0, 1 or 2 at the parameter section, or something else? Because when I fill in one of these numbers, and try, it does not work and when I reopen FSUIPC, it has changed it into something else. And that's the part I dont' get..... Thanks for the help, Jaap

Hello Mr. Dowson, I want to do something with the APU, but I don't know how. Maybe it's not even possible.... This is just to simulate real startup procedures, because I know FS2004 does not support the APU (no power provision or fuel consumption). I have been studying your documents about FSUIPC and its Offsets, bits and bytes, but I must be an idiot, because it completely dazzles me..... I have the Project Magenta RJ displays in my cockpit, and they have a small APU section. To simulate the APU operation I tried to get this to work with buttons from a GoFlight module, and FSUIPC. With a demo version of PMsystems I was able to start the APU, and see the result in the PM RJ displays, but since PMsystems is not designed for the Lear 45, it gives to many problems with the other Lear operations. I did see that the Offset used for the APU was 0X560F. Can this be used to tell PMRJ that the APU is started, running or being shutdown? And if so, how must this be done? I have FS2004 with SP1, PMRJ build 100, Goflight GF-P8, GF-T8, FSUIPC registered version 3.82 Thanks in advance. Jaap

Hello Pete, I am not using squawkbox or any other add-on that is meant for online flying, because I do not do that at all (not interested yet). I was happy with the VoxATC UK possibility to get interaction with AI aircraft and VoxATC, because without it, it happened quite often that I was cleared by ATC for Runway Line-up , and then suddenly an AI aircraft comes right through me.. That is solved in VoxATC UK multiplayer. VoxATC uses my addon AI aircraft (MyTraffic2006) but they don't show up on my TCAS in MP. That annoyed me. I have found several versions of AIBridge (1.0 , 2.0, 2.3 , 3.0)but they are not documented, and maybe I do something wrong, but I cannot get it working. Programming something like this myself? I wish !! I have the SDK for reference only.... I am sorry for not making sense, that might be a language problem. I'm Dutch, and might have misinterpreted some points. You are right of course that a solution for the AI traffic is already in FSUIPC, and i think you are right about Tegwyn not having enough time or not looking in to this far enough. Anyway thanks for your comments. Best Regards, Jaap