paulinyyz

Update, Honeycomb have responded very quickly and the unit has been RMA's and is going back for a replacement. You will be the first to know what happens after I have received the replacement and tried it it out. Paul

No, I can't see them in the way you would press the switch and have it respond with the corresponding number in FSUIPC. What you can do in the Controls section of MSFS is select the Bravo throttle and select the known button position. I know that the first toggle/rocker switch is 34 and 35 so I can assign pitot heat on/off but what happens is the switch on the panel is stuck either up or down, so the button are connected somewhere. It is as if in FSUIPC you could overwrite the joystick button numbers and enter what you liked. The levers each have a detente at the bottom which when moved past the detente becomes a button press, what I just discovered is when moving the lever which when moved through the detente becomes button #33, FSUIPC7 with the new .exe identifies it as #132. But when one of the seven toggles is pressed, nothing.

I don't think so either but will download it anyway. It is so strange because I just assigned button and 34 and 35 to toggle the pitot heat on and off, the switch will go one way but not the other. Thanks again for all your help. Paul

Hi John, I think I am just flogging a dead horse here, the new .dll for FSUIPC6 works with the Alpha but still nothing with the Bravo so I can only assume that the seven switches are defective. I know they are doing something because in MSFS when I assign one of them to a switch function, the switch can no longer be moved with the mouse, it is jammed or jiggles rapidly, just not doing the right thing. I have tried to contact Honeycomb but have not had a reply yet and not sure if I will even receive one. Paul

Thanks for sending John, I will get at it tomorrow. Paul

Will check it out today.

Yes, I can use FSUIPC6, I have the paid version which I use with P3Dv5 which I am going to spend more time on, tried the >32 switched with that but it was so long ago now I can't recall where I left it. Can also try FSUIPC7 with MSFS 2020. Thanks.

The Bravo is/are few and far between so would be easy to get another. I would like to try the FSUIPC version with support up to 128 buttons, who knows what can happen. Thanks for all your effort, I will let you know if anything changes. Paul

Sorry about that. Button presses were 16 (works), 34 (does not work) and 8 (works). Paul FSUIPC7_Buttons_16_34_8.log

Hi John, attached is the latest log using the HidTest.lua script you sent and the v7.0.7b executable. Paul FSUIPC7.log

And I would be willing to try the 128 button of FSUIPC7 when ready.

Brilliant, I will get at it over the weekend, thanks very much. I am about to get back to P3D and FSUIPC6 as well as MSFS. I am spending more time messing about with settings and VR stuff then flying. Cheers.

Not a problem John, I appreciate your efforts to-date. I will keep an eye out for the new script and let you know if I have any luck with vjoy. Paul.

I tried the HidDemo.lua after editing the vendor and product id's and removing the other two scripts but no luck. It was odd because when I pressed one of the <32 switches or buttons, FSUIPC would ID the joystick as F which is correct for the Bravo but as I flipped between position, #64 would flash up, still nothing from any of the seven rocker switches. In FS 2020 controls I tried to assigned one of the seven to a pitot heat switch by manually selecting the switch positions but as before it either froze the toggle on the panel in place or it vibrated, so the rockers are doing something, just not the right thing. Maybe I will try vjoy and the other bits that go along with it and see what happens. For what it's worth I ave attached the FSUIPC log and the HidScanner log. Paul FSUIPC7.log HidScanner.log

Here is the HiDScanner log, if i am looking at it correctly, the buttons seem to be recognised, 'Buttons range 1 -> 48 at indices 6 -> 53'. Paul HidScanner.log

I can see all the numbers <32 in both FSUIPC and the Windows game controller, it's only the rocker/toggle switches which don't appear. In MSFS the picture of the device has the first of the toggles switches starting at 34 up to 47, 33 doesn't seem to feature anywhere. Power management for the port is disabled and changing ports didn't help. I will try some of what you suggested under "Useful additional programs". Paul

Yes, buttons <32 all work and can be assigned, axes assignments are OK as well. I changed the poll rate and that didn't help. It's baffling. Paul

Hello, The Bravo comes with the toggle keys assigned to functions as landing light, beacon, pitot heat etc. If you move the switch, the corresponding assignment does not happen, i.e the pitot heat switch will not move but it seems like this is because the "always on" state is the reason. If I remove one of either the on or off positions, the corresponding switch on the panel will move one way but will not go back the other way. So they have an effect but not really working because they are stuck in one position or another. To recap, the Alpha LUA script will work and is seen by FSUIPC at joystick #64 but the Bravo script is not recognised, I think it should be seen as #65. I have attached the log file, it's a new day so I am now allowed more quota. Paul FSUIPC7.log

Good question, the answer is a bit yes and a bit no! For example if I try to assign one of the switches to operate the parking brake the "always on" either jams the brake on or off so they are doing something. Need to try something else to see if the original assignments are working which I will do tomorrow. Paul

Sadly no change, even vjoy uninstalled, I want to attach the latest FSUIPC7.log but don't have sufficient upload quota, can cut and past but that is a bit messy but can do so if you wish. Paul And sorry, I referred to you as Pete earlier, knee jerk reaction after many years.

I think the previous log file was missing what you wanted to see so have attached another. FSUIPC7.log

Thanks for the speedy weekend reply Pete, Yes, I am using vjoy with Joystick curves to improve A320 control performance in P3D, if need be I can remove it if we don't have any luck. I have added the line and turned on the offset logging. and attached the file. Paul FSUIPC7.log

Hello, I have both the Honeycomb Alpha and Bravo and wanted to address the switch assignments greater than 32 for both devices. I found and followed this topic, "A step by step for FSUIPC7, Honeycomb Alpha Yoke, and MSFS2020" and now have the switches (rotary start switch) working for the Alpha (joystick #64) but not having the same luck with the Bravo, still no response when pressing any of the seven rocker switches. I did see this reference, "The other lines which you might want to change are: Device = 0 -- Multiple devices of the same name need increasing Device numbers." and wondered if this was necessary but there was no mention of what to change it to, 1 or maybe 01, tried both but didn't seem to make a difference and after searching every LUA related PDF in the Documents folder I still could not find anything. I have attached my INI file and the latest FSUIPC7 log. Paul It appears that I can't attach both file because together they greater than what I am allowed to here is the LUA entries in the INI. [AUTO] 1=lua hidAlphaButtons 2=lua hidBravoButtons [LuaFiles] 1=hidAlphaButtons 2=hidBravoButtons FSUIPC7.log