paulnd

Your contribution to the sim community continues to be enormous, happy to help where possible.

here it is FSUIPC4.log

Apologies for the delay in responding. I've checked various backup files and the Bodnar board (DC6ADB60-...) was assigned as joystick 4 in 2015 so I don't think that there is any issue with assignments being moved. version e (test) does enumerate the devices in a different order to version c (test) which now matches the joystick assignments version e 125 #### Initialising Dlrectinput Axis Scanning ... 125 EnumDevices: 1.GUID={7290ABA0-80F7-11E6-8003-444553540000} 125 EnumDevices: 2.GUID={E3AFCAF0-288F-11E3-8008-444553540000} 125 EnumDevices: 3.GUID={E3AFCAF0-288F-11E3-8006-444553540000} 125 EnumDevices: 4.GUID={DC6ADB60-5F5B-11E3-8001-444553540000} version c 125 #### Initialising Dlrectinput Axis Scanning ... 125 EnumDevices: 0.GUID={DC6ADB60-5F5B-11E3-8001-444553540000} 125 EnumDevices: 1.GUID={7290ABA0-80F7-11E6-8003-444553540000} 125 EnumDevices: 2.GUID={E3AFCAF0-288F-11E3-8008-444553540000} 125 EnumDevices: 3.GUID={E3AFCAF0-288F-11E3-8006-444553540000} Paul

I replace a yoke recently but though that I had removed all the old assigments No, only one yoke connected. There should also not be a throttle assignment for this yoke, I now have a separate throttle connected to Prosim using Pololu cards

This a "work in progress" sim PC and the button assignments are managed in Prosim, I also moved some of the devices to a 2nd PC recently which may have confused things. Sorry, I'm not helping much.

Hello Pete, Here are the test files from a Windows 10 PC, I hope they're of use? Paul FSUIPC4.log FSUIPC4.ini

Excellent news! Happy to help Paul

thanks Pete, These are pre-SDK, found by logging and trial and error by the Linda team. Now that the SDK is available I'm sure quite a lot of tidying up can be done. I agree, hex values are much better. Paul

I've created a macro file (.mcro) with the following contents [macros] 1=NGX_GEAR_up 1.1=C70087, -2147483648 2=NGX_GEAR_off 2.1=C74184, 536870912 2.2=C74184, 131072 3=NGX_GEAR_down 3.1=C70087, 536870912 [/CODE] You can then assign an axis range to each of these in FSUIPC I copied the values from the Linda lua files which has been an excellent resource. regards Paul

Hello, Apologies for asking a really basic question but unfortunately it's a hazard of teaching oneself... I'm writing the contents of some L:Vars to the free FSUIPC offsets so that they can be displayed by an Opencockpits LCD card which is working well. My question is how do I know whether to write the contents as a byte, word or dword etc? At the moment it's by trial and error by logging the offset and checking that the value is correct, although this works it's a bit time consuming and I would like to increase my knowledge. I've read the pinned post about numbers, bits etc but haven't yet been able to link (in my mind!) this to using the appropriate type. Any assistance will be gratefully received. regards Paul

Dario, Unfortunately building a dll is beyond my current capabilities but it's something that I would like to learn. In the meantime I'm willing to assist where I can particularly with testing etc. regards Paul

Thanks for your help Pete, I don't have the SDK with me but I think they're both numbered and named I'll have a look at the advanced manual when I get home tonight, learning C or C++ is a bit daunting! regards Paul

Hello Pete, I don't know whether you have the PMDG NGX and if so had a chance to look at the SDK that was released over the weekend? The SDK includes a header file with custom event variables to be accessed by C/C++ software through simconnect-assuming I've understood this correctly! As I've a limited understanding of LUA and absolutely no knowledge of C/C++, I was wondering if these simconnect events can be accessed by LUA and FSUIPC or will I need to learn C or C++? regards Paul

Thank you Pete, the logic certainly makes sense. I hadn't thought of using ipc.testbutton which does make it simpler. Have a good weekend, Paul

I'll be pressing 3 buttons together, NGX_SHIFT is a toggle switch and NGX_NAV_SEL is a pushbutton on a rotary encoder. Shift 'off' and rotary encoder rotated will either increase or decrease whole on nav1 Shift 'off' and rotary encoder pressed in and rotated will increase or decrease fract on nav1 Shift 'on' + the above will do the same for nav2 I have a 2nd rotary encoder that will be used in a similar way for comm radios. Hope this makes sense? Enjoy your dinner and TV, I'm about to do the same! regards Paul

Hello Pete, Thanks as always for your quick reply. I am using a number of Leo Bodnar's cards which I have successfully assigned using Lua (after pulling apart and attempting to understand user scripts posted here and the Linda scripts). I'd therefore prefer to use Lua for all the NGX buttons and I'd also really like to improve my Lua skills and will be very grateful if you could help me with this please? This is only a part of a much larger Lua script. regards Paul

Hello, I have reached the boundary of my limited Lua knowledge, the relevant snippet of the script that I'm having difficulty with is below. I've commented what I hope to achieve which I expect will involve setting flags but I have no idea how to do this... Any assistance will be very much appreciated and hope that my explanation is understandable Thanks in advance Paul function NGX_NAV_INC(joy, btn, state) --if NGX_SHIFT is pressed and NGX_NAV_SEL is pressed then NGX_NAV2_FRACT_INC() --if NGX_SHIFT is pressed then NGX_NAV2_WHOLE_INC() --if NGX_NAV_SEL is pressed then NGX_NAV1_FRACT_INC() --else NAV1_WHOLE_INC() function NGX_NAV_DEC(joy, btn, state) --if NGX_SHIFT is pressed and NGX_NAV_SEL is pressed then NGX_NAV2_FRACT_DEC() --if NGX_SHIFT is pressed then NGX_NAV2_WHOLE_DEC() --if NGX_NAV_SEL is pressed then NGX_NAV1_FRACT_DEC() --else NAV1_WHOLE_DEC() function NGX_NAV1_WHOLE_INC() ipc.control(65641) end function NGX_NAV1_WHOLE_DEC() ipc.control(65640) end function NGX_NAV1_FRACT_INC() ipc.control(65643) end function NGX_NAV1_FRACT_DEC() ipc.control(65642) end function NGX_NAV2_WHOLE_INC() ipc.control(65645) end function NGX_NAV2_WHOLE_DEC() ipc.control(65644) end function NGX_NAV2_FRACT_INC() ipc.control(65647) end function NGX_NAV2_FRACT_DEC() ipc.control(65646) end event.button(4, 23, "NGX_SHIFT") event.button(4, 6, "NGX_NAV_INC") event.button(4, 7, "NGX_NAV_DEC") event.button(4, 30, "NGX_NAV_SEL") [/CODE]

Hello Pete, This was posted by Tim Gregson from the Prepar3D team on the Orbx forum: Could this be causing the FSUIPC crash too? Paul

I had a similar problem with 4.733 but it seems to be fixed in 4.734

I would be also be interested in creating a LUA script. In this thread http://forums.simflight.com/viewtopic.php?f=54&t=80870, Scott has succeeding in reading variables/offsets for the PMDG J41 and I've replied to his thread asking how he found the appropriate variables/offsets on the assumption that if it's possible for the J41 then it should be possible for the 747X. I have run the script and suggestions in this thread http://forums.simflight.com/viewtopic.php?f=54&t=78335 and obtained many variables but with my limited knowledge, these seem to be 'write' variables only not 'read' variables. I also understand that Pete does not approve of PMDG variables/offsets being published here and I respect that view. regards Paul

Hi Steve, I'm trying to create similar scripts for the FSX PMDG 747. I've got most of the buttons and knobs working but am having difficulties with the display. How did you determine which variables to read for each display? Any assistance or guidance will be much appreciated. Regards Paul

Pete, Just to let you know that I haven't had any problems since. Thanks for the prompt support of a really great product! regards Paul

Thanks for your assistance Pete, I've no idea of the coding required but is it not possible to contruct an identifer from a combination of names and serial numbers so that if either one weren't used, the device could still be identified. regards Paul

Pete, According to the BU0836 website : Is it not possible for FSUIPC to use the serial numbers to identify the controllers? Paul

Pete, There are no installers required for the BU0836 controller and according to the website, this is a deliberate design feature. regards Paul