Jump to content
The simFlight Network Forums

jmig

Members
  • Content Count

    25
  • Joined

  • Last visited

Community Reputation

0 Neutral

About jmig

  • Rank
    Member
  1. Update to the update. It is working 🙂 Thank you so much for pointing me the right direction and the correction on the UW vs UB. You may not have an idea of how good I feel at the moment. I finally got one of these FM scripts to work. John
  2. Update. I founld the Line 17 error and fixed it. Now I am getting a different error. I am afraid that I have no idea what this means. I will keep looking, however. 238843 *** LUA Error: C:\Users\john\Documents\Prepar3D v4 Add-ons\FSUIPC6\PBNC.lua:41: '<eof>' expected near 'end' 239281 *** LUA Error: C:\Users\john\Documents\Prepar3D v4 Add-ons\FSUIPC6\PBNC.lua:41: '<eof>' expected near 'end' 240203 *** LUA Error: C:\Users\john\Documents\Prepar3D v4 Add-ons\FSUIPC6\PBNC.lua:41: '<eof>' expected near 'end' 241156 *** LUA Error: C:\Users\john\Documents\Prepar3D v4 Add-ons\FSUIPC6\PBNC.lua:41: '<eof>' expected near 'end' 247500 === Closing session: waiting for DLLStop to be called ... 260859 === DLLStop called ...
  3. Thank you, sir, I (think) I made the changes you suggesed. However, it didn't work. Here is the modified script and the FSUIPC log. -- Paramenters -- 1 Park Brake off -- 2 Park Brake on -- 3 Canopy Switch OPEN -- 4 Canopy Switch CLOSE -- Variables Park_Brake = 0x0BC8 -- FSUIPC Offset Values 0=OFF 32767=ON Canopy_Set = 0x3367 -- FSUIPC Offset Values 0=OFF 1=ON - Parking Brakes Set if ipcPARAM == 1 then ipc.writeUW(0x0BC8,0) end if ipcPARAM == 2 then ipc.writeUW(0x0BC8,32767) end -- Canopy Switch OPEN if ipcPARAM == 3 then ipc.writeUB(0x3367,1) end -- Canopy Switch CLOSE if ipcPARAM == 4 then ipc.writeUB(0x3367,0) end end FSUIPC6.log
  4. I am not a programmer. Try as I might, programming languages are all Greek to me. I took a course in Basic while in grad school. The only way I got through it was with lots of help from a friend. That being said, I have managed to hack my way through simple Lua files to activate Lvars through cockpit switches. My goal is to have P3D to recognize the switch positions for Parking Brakes and canopy/door in the cockpit and set the corresponding offsets to match the switches. However, right now I simply want to get the offset to match the switches by using PARMS assigned to the SPST switches Using examples I found on the internet and reading what I can understand I cobbled together a script I thought would work. It doesn't! FSUIPC does recognize and allowed me to set the switches. Would someone be so kind as to help lead an old man out of the darkness. Here is the script. Thanks, John -- PBNC Parking Brake & Canopy Initialization -- John Miguez -- Paramenters -- 1 Park Brake off -- 2 Park Brake on -- 3 Canopy OPEN -- 4 Canopy CLOSE -- Variables -- Park_Brake = 0x0BC8 -- FSUIPC Offset Values 0=OFF 32767=ON -- Canopy = 0x3367 -- FSUIPC Offset Values 0=OFF 1=ON - Parking Brakes Set if ipcPARAM == 1 then ipc.writeUW(0BC8,0) end if ipcPARAM == 2 then ipc.writeUW(0BC8,32767) end -- Canopy OPEN if ipcPARAM == 3 then ipc.writeUW(3367,1) end -- Canopy CLOSE if ipcPARAM == 4 then ipc.writeUW(3367,0) end end
  5. Thank you Peter. I have just downloaded the update. John
  6. OK Pete, please bare with me here. This may sound less than intelligent, however, I have looked in every folder that unzipped from FSUIPC and I cannot find GFDev64.dll. I moved the one from GoFlight, but I think it is just GFDev.dll. I have the system down right now while I do some more work on the cockpit, so I can't check at the moment.
  7. I still need an answer to my question above. I can only get Go-Flight modules to work with Go-Flight software. FSUIPC5 is not recognizing the modules. I am using the most recent Go-Flight software, V2.8.8. Thanks, John
  8. Are we talking about recognizing the Go-Flight modules in Go-Flight or FSUIPC? I have installed Go-Flight software version 2.8.8.0. I can operate the Go-Flight modules through the Go-Flight module software but FSUIPC does not recognize the module key presses. I used the Go-Flig config program to turn off all the Go-Flight module buttons or rotaries. I have the GFDev.dll from version 2.2.8.0 in the FSUIPC modules folder. I do not see a file called GFDEV64.DLL in either the Go-Flight folder or the FSUIPC5 folders. IN PD3V3 I had the Go-Flight modules working through FSUIPC. I would be nice to get them doing the same in V4.
  9. Add me to the list of purchasers. My CC is out. John
  10. Because your program is magic . :) I was reading your documentation when this came in. Thank you for the advice. John
  11. Thanks again Peter, I am sure it can be done. It is done with Project Magenta and iFly. Here is part of the PM version of the script. It looks pretty straight forward. The problem is the FSUIPC offset are reserved for PM or iFly. running those scrips doesn't work unless I am using one of those applications. I have neither nor am I interested in flying that sort of simulator. I will read your SDK again and try and figure out the bit setting. Thanks for responding. John Var 0001, name iocp_teclas Var 0002, name teclado, Link IOCARD_KEYS, Device 22 { if &teclado = 71 // menu { &k = 629 } if &teclado = 79 // perf init { &k = 624 } if &teclado = 78 // rte { &k = 625 } if &teclado = 75 // des { &k = 628 } ............ var 5, name k, link subrutine { if &k <> 0 { if &k = &tempk { &offsetk = &k + &shift if &shift = 0 { &shift = 2048 } else { &shift = 0 } } else { &offsetk = &k &tempk = &k } &k = 0 } } var 6, name tempk var 8, name shift Var 3000, Link FSUIPC_INOUT, name offsetk, Offset $5428, Length 2 // CDU Functions Var 3010, name fmcLeds, Link FSUIPC_INOUT, Offset $052C, Length 2 // FMC LEDs { V3020 = TESTBIT V3010 ,0 // EXEC LED V3030 = TESTBIT V3010 ,1 // MSG LED V3040 = TESTBIT V3010 ,2 // FAIL V3050 = TESTBIT V3010 ,3 // OFST V3060 = TESTBIT V3010 ,4 // DSPY } Var 3020, Link IOCARD_OUT, name OUTPUT2, Device 22, Output 2 // FMC EXEC green led Var 3030, Link IOCARD_OUT, name OUTPUT1, Device 22, Output 1 // FMC MSG amber led Var 3040, Link IOCARD_OUT, name OUTPUT4, Device 22, Output 4 // FMC FAIL red led Var 3050, Link IOCARD_OUT, name OUTPUT0, Device 22, Output 0 // FMC OFST amber led Var 3060, Link IOCARD_OUT, name OUTPUT3, Device 22, Output 3 // FMC DSPY red led
  12. Peter or someone else who is knowledgeable with offsets, Please bear with me. I am a 68 year old pilot who flew both GA and fighters in the USAF. I also studied Chemical engineering in college. However, I went to college before computers took over. I used a slide rule in college. All that is to let you know that I am NOT a programmer, except when forced to in cockpit building. I can copy and modify scripts...most of the time. I am much better at getting hardware to work and woodworking than programming software. I looked up Offset 3340. However, I am afraid I do not understand all of the attributes I need to add after the FSUIPC_INOUT Offset $3340 part. Could someone have sympathy on and old fool (for even attempting to do this stuff) and give me an example of programming one of the buttons. I believe that I can take it from there. Also, I recall that in the early days there was a programming guide in the FSUIPC Documents folder. I couldn't find it with version 4.9? Thanks, John
  13. First of all, thanks for the quick reply Peter. To answer your question, yes, I did look at the offset list. In fact, I have read the entire basic and advanced manuals several times. The problem is that I didn't know what to look for. Thanks for pointing me in the right direction. John
  14. I am trying to get an Opencockpits FMC V3 to work with FSUIPC as a general purpose input device. My goal is to use the device as a FMC and Up Front Control Panel (UFCP) in various aircraft using FSUIPC to assign functions to the various button/keys of the FMC V3. However, I am have trouble getting it to work with the existing SIOC scripts. They work with Project Magenta's offsets or iFly offsets. but I don't know which offset to use in FSUIPC to get the device's keys to be recognized as buttons by FSUIPC. I have it working within the internal IPConsol that SIOC uses to test code. However, the key strokes are not seen in Notepad or recognized by FSUIPC. I am using the most recent version of SIOC and FSUIPC. I am running Prepar3D through Windows 10 Pro. Can anyone help me? John
  15. Thank you for figuring this our and posting. I have long been wanting an ability to quickly enter numbers this way. John
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use. Guidelines Privacy Policy We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.