bloggoman

Thank you Pete, that has cured the problem. Always the simple things cause the most trouble. Bill

OK thanks, just whenever you have time. Bill.

As requested Hidscan. Device at "\\?\hid#vid_1dc3&pid_1001&mi_00#8&1eb1748&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}" Vendor=1DC3, Product=1001 (Version 16.0) Manufacturer= PoLabs Product= Virtual joystick Serial Number= 2.35939 Usage Page: 1 Input Report Byte Length: 18 Output Report Byte Length: 0 Feature Report Byte Length: 0 Number of Link Collection Nodes: 2 Number of Input Button Caps: 1 Number of InputValue Caps: 7 Number of InputData Indices: 39 Number of Output Button Caps: 0 Number of Output Value Caps: 0 Number of Output Data Indices: 0 Number of Feature Button Caps: 0 Number of Feature Value Caps: 0 Number of Feature Data Indices: 0 Buttons range 1 -> 32 at indices 6 -> 37 Value U/RX at index 0, range 0 -> 4095, using 16 bits Value V/RY at index 1, range 0 -> 4095, using 16 bits Value Z at index 2, range 0 -> 4095, using 16 bits Value Y at index 3, range 0 -> 4095, using 16 bits Value X at index 4, range 0 -> 4095, using 16 bits Value Thr at index 5, range 0 -> 4095, using 16 bits Value POV at index 38, range 0 -> 7, using 8 bits ************************************************************************** Device at "\\?\hid#vid_1dc3&pid_1001&mi_01#8&19aea38d&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}" Vendor=1DC3, Product=1001 (Version 16.0) Manufacturer= PoLabs Product= Communication interface Serial Number= 2.35939 Usage Page: FF10 Input Report Byte Length: 65 Output Report Byte Length: 65 Feature Report Byte Length: 0 Number of Link Collection Nodes: 1 Number of Input Button Caps: 0 Number of InputValue Caps: 1 Number of InputData Indices: 1 Number of Output Button Caps: 0 Number of Output Value Caps: 1 Number of Output Data Indices: 1 Number of Feature Button Caps: 0 Number of Feature Value Caps: 0 Number of Feature Data Indices: 0 Value 0x01 at index 0, range 0 -> 255, using 8 bits ************************************************************************** Device at "\\?\hid#vid_1dc3&pid_1001&mi_02#8&a289a35&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}" Vendor=1DC3, Product=1001 (Version 16.0) Manufacturer= PoLabs Product= Virtual keyboard Serial Number= 2.35939 Device is a keyboard Usage Page: 1 Input Report Byte Length: 35 Output Report Byte Length: 0 Feature Report Byte Length: 0 Number of Link Collection Nodes: 1 Number of Input Button Caps: 2 Number of InputValue Caps: 0 Number of InputData Indices: 110 Number of Output Button Caps: 0 Number of Output Value Caps: 0 Number of Output Data Indices: 0 Number of Feature Button Caps: 0 Number of Feature Value Caps: 0 Number of Feature Data Indices: 0 ************************************************************************** Bill.

I am sorry if I misunderstood you and perhaps I need to reconsider how I word posts. Without knowing the workings of FSUIPC or the Pokeys interface card I thought that once the signal had been received that was all there was to it, but now you have explained I understand better. I do appreciate all the help you have given and any more you can add, whenever you can find time. I am however, worried that this may be time consuming for you as this is FS9 and I doubt many members will benefit from the results as the majority use FSX. If you do feel that it is fairly easy to fix and is worth continuing, then as I say it would be appreciated and any testing you want I can do. As for the Pokeys I would certainly not want you to buy one for this project; if necessary I would send you mine to play with! Bill.

This is what I thought I had done!! But let us leave this fast and slow situation and I will peruse the manual for the umpteenth time, as now it is causing confusion and frustration and I would rather sort out the Joy#64 problem. I am aware of the rotary encoder actions but it was not clear to me that this was how the Lua was meant to be. I have set my interface card rotaries with the same configuration and as it is recognised in FSUIPC as "Joy#2" and is incremented with each encoder, I fail to see that the interface card is a problem. Why, if the card was the problem, would it allow the first two encoders to be acknowledged! This is all new to me and I do not have answers, so if you believe the card to be the problem I can post on one of their sites to see if and further configuration is necessary.

I have done this and as you suggest it increments twice for each click, but this does not allow for fine adjustment. Do the parameters have to be set either 1 or 0 or left blank? I assumed that "Rotaries =" in Lua meant each rotary not that they were pairs. I have set it 1-10 as suggested but I am still unable to get "Joy#64 Btn8" onwards. One thing I have noticed is that although the box remained blank it has increased the amount in the button list in the INI and as well as P64 it now shows U64! INI List: [Auto.A320] 1=Lua Rotaries [JoyNames] AutoAssignLetters=No 0=CH PRO PEDALS USB 0.GUID={36DA8880-FF31-11E5-8005-444553540000} 1=CH FLIGHT SIM YOKE USB 1.GUID={36DCF980-FF31-11E5-8006-444553540000} 2=Virtual Joystick 2.GUID={4B46EE70-15C1-11E6-8001-444553540000} [General] UpdatedByVersion=3999z9b WindSmoothing=No AutoTaxiWind=No PropTaxiWind=No TimeSetMode=Partial WhiteMessages=No ThrottleSyncAll=No GraduatedVisibility=No LowerVisAltitude=0 UpperVisAltitude=25000 UpperVisibility=6000 GenerateCirrus=Yes WindShearSharp=No UpperWindGusts=No ExtendMetarMaxVis=Yes CorrectVSsign=Yes MouseWheelTrim=No MouseWheelTrimSpeed=1 BrakeReleaseThreshold=75 AxisInterceptIfDirect=No DontResetAxes=No DisconnTrimForAP=No ZeroElevForAPAlt=No AutoClearWeather=Yes ExtendTopWind=Yes WindSmoothness=5 SmoothPressure=No PressureSmoothness=5 SmoothVisibility=No VisibilitySmoothness=2 MaxSurfaceWind=0 WindLimitLevel=200 WindDiscardLevel=400 WindAjustAltitude=No WindAjustAltitudeBy=2000 MinimumVisibility=0 MaximumVisibilityFewClouds=0 MaximumVisibility=0 MaximumVisibilityOvercast=0 MaximumVisibilityRainy=0 OneCloudLayer=No ThinClouds=No ThinThunderClouds=No CloudThinness=1000 ThunderCloudThinness=10000 CloudTurbulence=No CloudIcing=No WindTurbulence=No SuppressAllGusts=No ExternalOptionControl=Yes AutoTuneADF=No KeepFS98CloudCover=No ShowPMcontrols=No MagicBattery=No RudderSpikeRemoval=No ElevatorSpikeRemoval=No AileronSpikeRemoval=No ReversedElevatorTrim=No StopAutoFuel=No TrapUserInterrupt=Yes NavFreq50KHz=No ClockSync=No SmoothIAS=Yes SetVisUpperAlt=No VisUpperAltLimit=6000 MaxIce=3 MinIce=-1 WindSmoothingDelay=0 WindSmoothAirborneOnly=No LimitWindVariance=No VisSmoothingDelay=0 VisSmoothAirborneOnly=No TrafficControlDirect=Yes SuppressCloudTurbulence=No SuppressWindTurbulence=No SpoilerIncrement=512 JoystickTimeout=20 PollGFTQ6=Yes BlankDisplays=No ZapSound=firework ShortAircraftNameOk=Substring UseProfiles=Yes TCASid=Flight TCASrange=40 TrafficScanPerFrame=10 AxesWrongRange=No AxisCalibration=No CentredDialogue=Yes ShowMultilineWindow=Yes SuppressSingleline=No SuppressMultilineFS=No ClearWeatherDynamics=Yes OwnWeatherChanges=No FixWindows=No FixControlAccel=No WeatherReadInterval=4 MoveBGLvariables=Yes TimeForSelect=4 WeatherReadsFast=No LuaRerunDelay=66 MainMenu=&Modules SubMenu=&FSUIPC ... [JoystickCalibration] AllowSuppressForPFCquad=Yes ExcludeThrottleSet=Yes ExcludeMixtureSet=Yes ExcludePropPitchSet=Yes SepRevsJetsOnly=No ApplyHeloTrim=No UseAxisControlsForNRZ=No FlapsSetControl=0 FlapDetents=No ReverserControl=66292 Reverser1Control=66422 Reverser2Control=66425 Reverser3Control=66428 Reverser4Control=66431 MaxThrottleForReverser=256 AileronTrimControl=0 RudderTrimControl=0 CowlFlaps1Control=0 CowlFlaps2Control=0 CowlFlaps3Control=0 CowlFlaps4Control=0 MaxSteerSpeed=60 [Sounds] Path=D:\Program Files (x86)\Microsoft Games\Flight Simulator 9\Sound\ Device1=Primary Sound Driver Device2=BenQ GL2250H-8 (NVIDIA High Definition Audio) Device3=BenQ GL2250H-4 (NVIDIA High Definition Audio) [MacroFiles] 1=A320MFD 2=WXRadar [LuaFiles] 1=Airport 2=display vals 3=DynamicFriction 4=EICAS ECAM AC 5=EICAS ECAM DATA 6=EICAS ECAM ENG 7=EICAS ECAM FLT 8=EICAS ECAM FUEL 9=EICAS ECAM HYD 10=Frictions 11=Fuel737 12=gfdDisplay 13=GFpower 14=HidDemo 15=init pos 16=ipcDebug 17=landing 18=liar 19=log lvars 20=MasterClient 21=MFD 10 22=MFD 160 23=MFD 20 24=MFD 320 25=MFD 40 26=MFD 80 27=MFD ARC 28=MFD LS 29=MFD NAV 30=MFD PLN 31=MFD VOR 32=mrudder 33=MyDisplay 34=Payload737 35=record to csv 36=Rotaries 37=Rotaries2 38=SlaveServer 39=SyncAxis 40=testclnt 41=testsrvr 42=textmenu 43=ThrustSym 44=ThrustSym4 45=TileSix 46=TripleUse 47=VRI_SetBaro 48=VRI_SetMach 49=WP6test 50=WXradar [Buttons] ButtonRepeat=20,10 IgnoreThese=2.0, 2.1, 2.2, 2.3, 2.4, 2.5, 2.6, 2.7 0=P64,0,C65663,0 1=P64,1,C1027,0 2=P64,2,C65662,0 3=P64,3,C1026,0 4=P64,4,C65896,0 5=P64,5,C1021,0 6=P64,6,C65897,0 7=P64,7,C1020,0 8=U64,0,C65663,0 9=U64,1,C1027,0 10=U64,2,C65662,0 11=U64,3,C1026,0 [Profile.A320] 1=Airbus A320 IAE British Airways [Keys.A320] 2=116,8,L36:R,0 4=117,8,L36:K,0 6=90,8,65580,0 [Buttons.A320] 0=P64,0,C65663,0 1=P64,1,C1027,0 2=P64,2,C65662,0 3=P64,3,C1026,0 4=P64,4,C65896,0 5=P64,5,C1021,0 6=P64,6,C65897,0 7=P64,7,C1020,0 8=U64,0,C65663,0 9=U64,1,C1027,0 10=U64,2,C65662,0 11=U64,3,C1026,0 Just clutching at straws! I could not find the "j" so I deleted it from the file and it did not return after restarting FS9. Bill

I have looked at the Lua program, although I do not fully understand Lua, but there is a "buttonbit = 4" in the program, would this have any bearing on the lack of "Joy#64". Vendor = 0x1DC3 Product = 0x1001 Device = 0 -- Multiple devices of the same name need increasing Device numbers -- Use separate Lua plug-ins for separate cards! -- NOTE: this can handle up to 16 rotaries only, using the first 64 "virtual buttons" -- List the pairs here: Rotaries = {1,2,3,4,5,6,7} -- Example { 31, 30, 25, 22 } would be 31+30 for one, 25+22 for the next, and so on -- Which is clockwise and which counterclockwise doesn't matter -- you'll get -- fast and slow of each in any case dev, rd, wrf, wr, init = com.openhid(Vendor, Product, Device, Report) if dev == 0 then ipc.log("Could not open HID") ipc.exit() end -- Set the boundary time in milliseconds between -- "fast" (shorter) and "slow" (longer) signalling FastTimeLimit = 40-- Adjust to taste -- Polling time in milliseconds: should be much shorter than -- the boundary time Pollrate = 10 -- same as 50 times per second -- Initialise variables used to keep track of things LastTimes = {} Buttons = 0 PrevButtons = 0 Diff = 0 -- This function will be called by a time event, set at the end of the program before exit. function poll(Time) -- read any data available from the device (only need most recent report) data, n = com.readlast(dev, rd) if n ~= 0 then -- Data was returned, so get the status of all the possible "buttons" we are using -- one value of 32 bits Buttons = com.gethidbuttons(dev, data) -- See if any changes occurred: Diff = logic.Xor(Buttons, PrevButtons) PrevButtons = Buttons if Diff ~= 0 then offset = 0x3340 buttonbit = 1 j = 1 while Rotaries[j] ~= nil do mask = logic.Shl(1, Rotaries[j]-1) if logic.And(Diff,mask) ~= 0 then -- This one changed -- See if changed in less than the "boundary" time thisbutton = buttonbit if (LastTimes[j] ~= nil) and ((Time - LastTimes[j]) < FastTimeLimit) then thisbutton = buttonbit + buttonbit -- Use next higher button for fast end LastTimes[j] = Time -- Toggle a virtual button accordingly ipc.togglebitsUB(offset, thisbutton) end j = j + 1 buttonbit = 4 * buttonbit if logic.And(j,15) == 0 then buttonbit = 1 offset = offset + 4 end end end end end event.timer(Pollrate, "poll") Bill.

I have changed it again and what I get is two or three indents before it increments the display which is slow for three indents then suddenly jumps ten increments. This is the Button configuration from the INI: [Buttons] InitialButton=64,0 IgnoreThese=2.0, 2.1, 2.2, 2.3, 2.4, 2.5, 2.6, 2.7 ButtonRepeat=20,10 0=P64,0,C65663,0 1=P64,1,C1027,0 2=P64,2,C65662,0 3=P64,3,C1026,0 4=P64,4,C65896,0 5=P64,5,C1021,0 6=P64,6,C65897,0 7=P64,7,C1020,0 [Profile.A320] 1=Airbus A320 IAE British Airways [Keys.A320] 2=116,8,L36:R,0 4=117,8,L36:K,0 6=90,8,65580,0 [Buttons.A320] 0=P64,0,C1027,0 1=P64,1,C65663,0 2=P64,2,C1026,0 3=P64,3,C65662,0 4=P64,4,C65896,0 5=P64,5,C1021,0 6=P64,6,C65897,0 7=P64,7,C1020,0 This may need adjusting in the Lua program so I will play with this. The important thing at the moment is that I am still unable to get any joystick numbers above Joy#64 Btn7. I have set the "IgnoreThese" as shown above and this has removed the "Joy2", but the entry box remains blank. I have also tried removing the "InirialButton" from the list but this has made no difference. As there is a profile for the A320 Buttons I also entered the "IgnoreThese" in this list all to no avail. It appears as though anything above "Joy#64 Btn7" is being restricted somewhere, but I am not experienced enough to understand why! One thing I have noticed was that "J=<< MISSING JOYSTICK >>" has been entered in the "Joynames" list as follows: [JoyNames] AutoAssignLetters=No 0=CH PRO PEDALS USB 0.GUID={36DA8880-FF31-11E5-8005-444553540000} 1=CH FLIGHT SIM YOKE USB 1.GUID={36DCF980-FF31-11E5-8006-444553540000} 2=Virtual Joystick 2.GUID={4B46EE70-15C1-11E6-8001-444553540000} J=<< MISSING JOYSTICK >> This was not there originally and even though I have removed all my alterations it is still listed; it seems to be a coincidence that it has the letter "J", perhaps this doesn't matter. Bill.

I understood what the j & b meant and I thought that it was to correspond with the Lua program, but I did replace "InitialButton=j,b" with "InitialButton=64,0" at one point. In the advanced guide it states: "IgnoreThese=j.b,j.b" so I assumed it was meant to be "IgnoreThese=j.b,2.4" which was the joystick and button numbers, otherwise why is it necessary to put j,b twice unless it indicates that it is the joystick numbers to be ignored. I will try again with: IgnoreThese=2.4 Bill.

Didn't expect you to reply on a Sunday! I had already tried this it did but it did not work, but as I said it is not a problem. Yes encoder 1 & 2 show joy#2. I tried setting the ignore parameter in INI and it saved, but when I loaded FS9 and run the lua it somehow removed it from the file. This is how I set it in the INI file: [Buttons] InitialButton=j,b IgnoreThese=j.b,2.4 IgnoreThese=j.b,2.5 ButtonRepeat=20,10 This is how the entry was after running FS9: InitialButton=j,b ButtonRepeat=20,10 I am assuming that this is the way the ignore parameter should be set! I also tried starting the Lua program automatically and manually but this made no difference. Bill.

OK I understand about the virtual joysticks and have set the encoders 1 & 2 with the Joy#64 buttons 0-7. I am however, unable to get fast with fast turn and slow with slow turn whatever configuration I set; it will only work opposite i.e. fast rotation of the encoder increments slowly and slow rotation increments fast. This is not a concern as it is easy enough to work with. When I attempt to set encoder 3 I am unable to get the joy#64 button to display whether I rotate the encoder fast or slow I only get the real joy#2. I thought this may require InitialButton=j,b setting in the INI file, but this made no difference, so what am I doing wrong? Bill.

Thanks for the reply, but I have other problems to sort out before I can carry out your advice. Perhaps these may now be contributing to the original problem so I will keep you informed. Bill.

Could someone advise as to the setting of rotary encoders. I can operate the encoder and get Joy!#2 BTN0 which I set OBS inc, I then get Joy#64 BTN1 which I set to OBS inc fast, then Joy#2 BTN1 for OBS dec and Joy#64 BTN3 as OBS dec fast. All selections have been left at parameter 0. This operates the OBS but if I rotate slowly if moves fast and if I rotate fast it moves slower. What am I doing wrong? I notice there are also Joy#64 BTN 0 and Joy#64 BTN2: do these have to be set? This is the same for spd, but nav, com, hdg, alt and vs do not give me the option of Joy#64, therefore I am unable to set for fast control. This appears to only allow only two encoders to have access to Joy#64, is there a reason for this? In effect this is only Joy#64 BTN0 to Joy#64 BTN 7 I am using PoKeys interface card set for seven encoders and the FSUIPC Lua script is set as: [Vendor = 0x1DC3 Product = 0x1001 Device = 0 -- Multiple devices of the same name need increasing Device numbers -- Use separate Lua plug-ins for separate cards! -- NOTE: this can handle up to 16 rotaries only, using the first 64 "virtual buttons" -- List the pairs here: Rotaries = {1,2,3,4,5,6,7}] Reading the NOTE above 16 encoders should have four Joy# 64 each or am I not understanding this correctly! Thanks Bill. EDIT: I am using FS9