Honeycomb Bravo Throttle Config.

[Mugg21B]

21 hours ago, John Dowson said:

I have fixed this issue in the attached beta release, v7.2.17a: FSUIPC7.exe

Please download and use to replace your existing FSUIPC7.exe and test with this version.

John

So I wonder if being a new account if I was restricted in upload size, but anyway, it looks like I'm good to attach logs now. So I may have success, after installing the WASM module and activating it in the addons menu. Turning the right rotary now changes the ALT value and appears to do it based on speed of the turn (which is what I wanted all along!). The issue now is that it's backwards - turning to the right, INC, actually decreases the values, while turning left, DEC, increases them. But this is much better than where I was at before.

 

Edit: may have spoken too soon, no luck change HDG or anything or than the ALT setting at the moment.

Edit edit: Upon further review I can change hdg and IAS but only after i "activate" those knobs in game by using my mousewheel to get, for example, IAS to show up as my current speed. Then rotating the right rotary changes the values. Given the fact the INC/DEC are reversed, I wonder if swapping the values for the INC/DEC in the ini would solve this issue? I added the testflight log to show what was going on during a short flight.

FSUIPC7.log FSUIPC7.luaoff.log FSUIPC7somewhatsuccess.log

FSUIPC7testflight.log

[John Dowson]

3 hours ago, Mugg21B said:

The issue now is that it's backwards - turning to the right, INC, actually decreases the values, while turning left, DEC, increases them. But this is much better than where I was at before.

Then switch your assignments around.

3 hours ago, Mugg21B said:

I wonder if swapping the values for the INC/DEC in the ini would solve this issue?

Don't swap the values, swap the virtual button numbers. Looking at the heading assignments, for example:

Quote

58=CP(+B,18)64,0,C65879,0 	-{HEADING_BUG_INC}-
59=CU(+B,18)64,0,C65879,0 	-{HEADING_BUG_INC}-
60=CP(+B,18)64,1,C1025,0 	-{heading bug inc fast}-
61=CP(+B,18)64,2,C65880,0 	-{HEADING_BUG_DEC}-
62=CU(+B,18)64,2,C65880,0 	-{HEADING_BUG_DEC}-
63=CP(+B,18)64,3,C1024,0 	-{heading bug dec fast}-

Button numbers 0 is being used for slow inc, 1 for fast inc, 2 doe slow dec and 3 for fast dec. To switch these, you would change to:

Quote

58=CP(+B,18)64,2,C65879,0 	-{HEADING_BUG_INC}-
59=CU(+B,18)64,3,C65879,0 	-{HEADING_BUG_INC}-
60=CP(+B,18)64,3,C1025,0 	-{heading bug inc fast}-
61=CP(+B,18)64,0,C65880,0 	-{HEADING_BUG_DEC}-
62=CU(+B,18)64,0,C65880,0 	-{HEADING_BUG_DEC}-
63=CP(+B,18)64,1,C1024,0 	-{heading bug dec fast}-

 

3 hours ago, Mugg21B said:

Upon further review I can change hdg and IAS but only after i "activate" those knobs in game by using my mousewheel to get, for example, IAS to show up as my current speed. Then rotating the right rotary changes the values.

You shouldn't need to do this...Are you its not being changed but you just can't see it? What control do you see (in the FSUIPC7.log file) when you use your mouse to switch to IAS mode? Try assigning the Bravo IAS button to the same control.

FSUIPC provides logging facilities so that you can see what controls are being used when you operate the buttons, switches etc in the UI. You should use the facilities to work out what is happening and then assign your controls accordingly. I really don't have time to do this for every FSUIPC user, sorry.

John

[John Dowson]

By the way, the settings I provided (that you are using) are just general settings. The AP functions work differently in different aircraft/AP systems. For example, to control the IAS in more complex aircraft you may need to use the Autopilot Airspeed Hold Var (see offset 07E2) simvar. This may be indexed (for dialed in and active), but currently only one value (index 1) is held in FSUIPC offsets.

You can set-up profile specific assignments to set up these functions correctly for different aircraft.

John

[John Dowson]

Also, you don't say which aircraft you are using to test this (or I can't remember...!). If using the PMDG aircraft, for example, you should see if any custom controls are provided. See this FAQ entry for setting things up for PMDG aircraft: 

John

 

[John Dowson]

I see you are also using FSUIPC7. You posted in the wrong forum - there is a specific sub-forum for FSUIPC7 - I will move this post.

For FSUIPC7, things can get complicated and (almost) every aircraft requires a different set-up. The latest version of FSUIPC7, v7.2.16, comes with the MobiFlight preset list available for assignment. You should also use the MobiFlight HubHop preset site (https://hubhop.mobiflight.com/) to search for the calculator code to control many functions. MSFS aircraft tend to use lvars and hvars for many functions, if not more complex calculator code. Go to the MF HubHop website, filter by the aircraft you are trying to control, and you will see a list of the presets available. You can also search by subsystem, etc. For example, for the A320, you will see presets for FCU speed inc/dec, as well as pull/push...

You can translate the calculator code shown there for use in FSUIPC7 assignments, if you know what you are doing, but this can be quite complex. In the latest version of FSUIPC7, you can assign directly to these presets (as well as provide your own presets). If not already using the latest version, please download it. Documentation for this functionality is in the Advanced User Guide, under the WASM section.

John

[baronfritz]

Hello

I  know that  you no longer support FSUIPC 3.99 however I don't know where else to turn....

I have been engaged in a running battle trying to get the Honeycomb Bravo to function properly in FS9. It may be of interest to have a look at my posts over at Flightsim.com, " Honeycomb Bravo inFS2004",which will give some idea of where I'm coming from.There have been nearly 1300 views which indicates a significant interest in the subject. A number of people have said that they are using the Bravo in FS2004 successfully however none have come forward and revealed precisely how this was accomplished. 

One of the issues I am unable to satisfactorily deal with is the effective stroke of the throttle,prop and mixture axis.I am using FSUIPC 3.99 (registered version) , to recognize the axis,which it does accomplish,however on the calibration page, (any axis), I am getting only only half a stroke.Specifically, the read outs,in my case, begin at -16256 with the lever down against the detent. Moving the lever upwards, the reading drops down to zero at the halfway point then increase to +16256 at the top of the stoke.(with corresponding bizarre behavior in the 3d view) I was hoping that someone might divulge the workaround to this issue.Then of course,one must continue with the calibration procedure however,I think the axis behavior should be tackled first.

I did set Bravo up in FSX and it seemed to function properly over there,however as I do not care for FSX, I left it at that and returned to the battle of using the Bravo in FS 2004. Just to complicate things, my old clunky CH Throttle (may it R.I.P.), with its neanderthal innards did not have a problem working passably well in both FS9 as well as FSX. However the Honeycomb Bravo,that state of the art technological Wunderkindt seems unable to do so..... Seriously?

If you are unable to offer assistance possibly you could direct me to someone who can? Thanks for any advice you can give!

[John Dowson]

1 hour ago, baronfritz said:

It may be of interest to have a look at my posts over at Flightsim.com, " Honeycomb Bravo inFS2004",which will give some idea of where I'm coming from.

A link would have been useful...but I found that post...

1 hour ago, baronfritz said:

I am getting only only half a stroke

What does this mean? I don't understand what 'half a stroke' means, sorry...

1 hour ago, baronfritz said:

Specifically, the read outs,in my case, begin at -16256 with the lever down against the detent. Moving the lever upwards, the reading drops down to zero at the halfway point then increase to +16256 at the top of the stoke.

Are those the read-outs from the 'on' values? If so, that seems reasonable to me...generally axis ranges go from -16383 to +16383, so  you are missing a bit at the extremes but otherwise it looks ok. Have you calibrated your axis in the windows game controller app - you could try this to get the full range. The 'out' value will depend on the axis control you have assigned to, if you have defined a reverse zone or not,  and any calibration that is applied.

Also, the issue you described over on FlightSim.com is different:

Quote

I discovered during the fight with FSUIPC is that the prop and mixture axis go from min to max during the first half of their travel then star over again in the second half of the stroke then come to the detent.

This sounds like its going from -16256 to +16256 for the first half of your axis, then jumping from +16256 to -16256 half way through the momvement and starting again....that does sound very strange and I really can't see how that can be happening...

Maybe you can attach your ini and log files. For the log, activate axis logging and move your throttle, prop and mixture axis each through its full range and back again. This should show what values are being sent to the FS.

John

[baronfritz]

Hello Jon

I tried to do a log and a fresh reset of all the axis,to illustrate my problems more clearly however, I think I have only succeeded in buggering things up royally...

you may have noticed by now that I am not terribly computer literate - sorry

 

FSUIPC.1.log FSUIPC.2.log FSUIPC.ini FSUIPC.log

[John Dowson]

I don't know why you have attached 3 useless log files.... Can you please not start a new log file, there is no need.

Your axis assignments now look very strange:

Quote

0=0X,256,D,17,0,0,0
1=0U,256,D,18,0,0,0
2=0V,256,D,13,0,0,0
3=2X,256,D,14,0,0,0
4=2Y,256,D,14,0,0,0
5=2Z,256,D,14,0,0,0
6=2R,256,D,17,0,0,0
7=2U,256,D,14,0,0,0
8=2V,256,D,13,0,0,0
 

You have multiple assignments to mixture 1 set (13 - 2 assignments), mixture 2 set (14 - 4 assignments), etc

And your calibration looks even stranger:

Quote

Throttle3=-16380,-512,512,16380/32
Throttle1=0,0,512,16380/40
Throttle2=0,0,512,16380/40
PropPitch1=0,0,512,16380

There is no calibration to the axes you have assigned (e.g. mixture 1 set), and you have strange throttle calibration which you haven't even assigned.

I suggest that you read the user guide and start again. Read the section 'The Easy Step-by-Step Way to Calibrate Your Controls'.
If you want further help after trying to assign and calibrate your controls correctly, show me the updated ini and a single log file where you have activated the correct logging (i.e. axes controls if your issue is with axes) and showing your issue (i.e. move the assigned axis through its full range) together with a relevant description of the problem.

The set-up for ax axis assignment for the Honeycomb Bravo is exactly the same as you would do it for any other device, such as your old CH throttle, so I really don't understand why you are having such difficulty.

John

[sehadi]

On 7/8/2021 at 5:28 PM, John Dowson said:

@Dreamflight767 Did you manage to configure your Bravo AP?

I have just configured mine, for MSFS, but it should be the same for P3D.
This is how I did it.

First, you need the following lua file: Rotaries.lua

Save that file to your FSUIPC6 installation folder. This will give the two rotaries on the Bravo fast/slow support. To use this, you need to have it auto-ran. To do this, add it to your [Auto] section of your FSUIPC6.ini, or create if not there, e.g.

[Auto] 
1=Lua Rotaries

This will convert the rotaries physical buttons to virtual buttons. With this, you don't want to see the physical button presses registered in the assignments UI. To prevent this, add the following line to your [Buttons] section of your FSUIPC6.ini file:

IgnoreThese=B.12, B.13, B.21, B.22

NB. My Bravo is assigned the letter B. If yours is different, change the letter to the one you are using.

Next, you need to add the assignments. You can use the following i.e. copy and paste to your [Buttons] section. When you have done this, you will need to adjust the index numbers (i.e. first number on each line) to make sure that they are all unique (and better consecutive). Also, you again need to change the B in the (+B,??) bit to the letter you are using.

58=CP(+B,18)64,0,C65879,0 	-{HEADING_BUG_INC}-
59=CU(+B,18)64,0,C65879,0 	-{HEADING_BUG_INC}-
60=CP(+B,18)64,1,C1025,0 	-{heading bug inc fast}-
61=CP(+B,18)64,2,C65880,0 	-{HEADING_BUG_DEC}-
62=CU(+B,18)64,2,C65880,0 	-{HEADING_BUG_DEC}-
63=CP(+B,18)64,3,C1024,0 	-{heading bug dec fast}-
64=CP(+B,16)64,0,C65897,0 	-{AP_SPD_VAR_DEC}-
65=CU(+B,16)64,0,C65897,0 	-{AP_SPD_VAR_DEC}-
66=CP(+B,16)64,1,C1020,0 	-{ap spd var dec fast}-
67=CP(+B,16)64,2,C65896,0 	-{AP_SPD_VAR_INC}-
68=CU(+B,16)64,2,C65896,0 	-{AP_SPD_VAR_INC}-
69=CP(+B,16)64,3,C1021,0 	-{ap spd var inc fast}-
70=CP(+B,17)64,0,C65662,0 	-{VOR1_OBI_DEC}-
71=CU(+B,17)64,0,C65662,0 	-{VOR1_OBI_DEC}-
72=CP(+B,17)64,1,C1026,0 	-{vor1 obi dec fast}-
73=CP(+B,17)64,2,C65663,0 	-{VOR1_OBI_INC}-
74=CU(+B,17)64,2,C65663,0 	-{VOR1_OBI_INC}-
75=CP(+B,17)64,3,C1027,0 	-{vor1 obi inc fast}-
76=CP(+B,19)64,0,C65895,0 	-{AP_VS_VAR_DEC}-
77=CU(+B,19)64,0,C65895,0 	-{AP_VS_VAR_DEC}-
78=CP(+B,19)64,1,C1022,0 	-{ap vs var dec fast}-
79=CP(+B,19)64,2,C65894,0 	-{AP_VS_VAR_INC}-
80=CU(+B,19)64,2,C65894,0 	-{AP_VS_VAR_INC}-
81=CP(+B,19)64,3,C1023,0 	-{ap vs var inc fast}-
82=CP(+B,20)64,0,C65893,0 	-{AP_ALT_VAR_DEC}-
83=CU(+B,20)64,0,C65893,0 	-{AP_ALT_VAR_DEC}-
84=CP(+B,20)64,1,C1016,0 	-{ap alt var dec fast}-
85=CP(+B,20)64,2,C65892,0 	-{AP_ALT_VAR_INC}-
86=CU(+B,20)64,2,C65892,0 	-{AP_ALT_VAR_INC}-
87=CP(+B,20)64,3,C1017,0 	-{ap alt var inc fast}-

For the trim wheel, you can also use these:

52=P64,6,Cx32000BC0,x3FFF0018 	-{offset sword increment, offset 0BC0 (Incr=24, Limit=16383)}-
53=P64,7,Cx32000BC0,x3FFF0032 	-{offset sword increment, offset 0BC0 (Incr=50, Limit=16383)}-
54=P64,4,Cx42000BC0,xC0010018 	-{offset sword decrement, offset 0BC0 (Decr=24, Limit=-16383)}-
55=P64,5,Cx42000BC0,xC0010032 	-{offset sword decrement, offset 0BC0 (Decr=50, Limit=-16383)}-
56=U64,7,Cx32000BC0,x3FFF0032 	-{offset sword increment, offset 0BC0 (Incr=50, Limit=16383)}-
57=U64,5,Cx42000BC0,xC0010032 	-{offset sword decrement, offset 0BC0 (Decr=50, Limit=-16383)}-

Hope that helps.

John

Hi if you please help me  on the rotaries issue. I have done every thing according to this post and added lotaries.lua file in main folder . rotaries are working but with problems and those are given below

Altitude:  rotating speed ok but counterclock wise

Heading: very slow rotating speed and takes ages to get from lets say 300 to 340 but direction is clockwise 

Speed:   very very slow rotating speed and counter clock wise.

AND SAME WITH VS

Pls help me where i am wrong

and pls find the ini as well as log files with this post

 

thank you

A Akram

FSUIPC7.ini FSUIPC7.log

[John Dowson]

19 hours ago, sehadi said:

Altitude:  rotating speed ok but counterclock wise

Switch the inc/dec button numbers, so change:

Quote

82=CP(+B,20)64,0,C65893,0     -{AP_ALT_VAR_DEC}-
83=CU(+B,20)64,0,C65893,0     -{AP_ALT_VAR_DEC}-
84=CP(+B,20)64,1,C1016,0     -{ap alt var dec fast}-
85=CP(+B,20)64,2,C65892,0     -{AP_ALT_VAR_INC}-
86=CU(+B,20)64,2,C65892,0     -{AP_ALT_VAR_INC}-
87=CP(+B,20)64,3,C1017,0     -{ap alt var inc fast}-

to

Quote

82=CP(+B,20)64,2,C65893,0     -{AP_ALT_VAR_DEC}-
83=CU(+B,20)64,2,C65893,0     -{AP_ALT_VAR_DEC}-
84=CP(+B,20)64,3,C1016,0     -{ap alt var dec fast}-
85=CP(+B,20)64,0,C65892,0     -{AP_ALT_VAR_INC}-
86=CU(+B,20)64,0,C65892,0     -{AP_ALT_VAR_INC}-
87=CP(+B,20)64,1,C1017,0     -{ap alt var inc fast}-

 

19 hours ago, sehadi said:

Heading: very slow rotating speed and takes ages to get from lets say 300 to 340 but direction is clockwise 

Rather than using the Heading Bug control, switch to using offset 0x07CC (Autopilot heading value) with the Offset Sword increment decrement controls, where you can specify the inc/dec value that works for you. This is explained earlier in this thread... This is also how your elevator trim is configured, so take a look at that to see how this assignment is made.

19 hours ago, sehadi said:

Speed:   very very slow rotating speed and counter clock wise.

AND SAME WITH VS

Again, if the speed is too slow, switch to using the relevant offset instead - check the offset status document to get the right offset. You can log the offsets (using the Log -> Offsets menu item) to see how the values change using the current settings, and to confirm the offset to use. Use the correct (inc or dec) control to get the right direction.

John

[sehadi]

Thank you for your help!

[JeffD]

@John Dowson, I purchased a Bravo a few weeks back and ended up building my own Lua to handle the rotaries, I wasn't aware you had already done so.  I really like the ease of use of your Lua + emulated button setup.  When I tried your Rotaories.Lua, I noticed a bit of lag when using the TrimWheel.  Is this from the pulling of the controller or emulating the joystick button?

My Lua is nowhere near as user friendly but is a bit more performant. instead of pulling the controller I used event.button... (which I'm sure pulls under the hood) and call ipc.control directly from the Lua.  Using event.button, I found that the minimum registered interval between button presses was about 94ms. Is this a limitation of the hardware or is there any setting in the .INI that would allow event.button to pull at a higher rate?  I did a trinary state for slow->medium->fast but since the speed limit is ~94ms hard to separate medium and fast.

Attached is what I made: BravoRotaries.lua any tips on improving appreciated 

Thanks, Jeff

[John Dowson]

I'm on holiday now until next Thursday - I will take a look then....

John

[John Dowson]

On 6/2/2022 at 9:41 PM, JeffD said:

When I tried your Rotaories.Lua, I noticed a bit of lag when using the TrimWheel.  Is this from the pulling of the controller or emulating the joystick button?

There shouldn't be too much of a lag...you could maybe try increasing the poll rate in the lua, although the default of 10ms should be enough.
It may also depend on what the assignment to the button flags are doing. If, for example, they are updating lvars, you could try increasing the lvar update frequency (in the WASM). This defaults to 6Hz, but can be changed to Frame ort VisualFrame for faster lvar updates.

On 6/2/2022 at 9:41 PM, JeffD said:

My Lua is nowhere near as user friendly but is a bit more performant. instead of pulling the controller I used event.button... (which I'm sure pulls under the hood) and call ipc.control directly from the Lua.  Using event.button, I found that the minimum registered interval between button presses was about 94ms. Is this a limitation of the hardware or is there any setting in the .INI that would allow event.button to pull at a higher rate?  I did a trinary state for slow->medium->fast but since the speed limit is ~94ms hard to separate medium and fast.

I also provided a version that uses event.button although not as flexible as yours - I have attached it for your reference: RotariesEvent.lua

The interval between a press and release is usually determined by the hardware driver software, There is the PollInterval ini parameter, which tells FSUIPC how often to read/poll the state of the joystick buttons. However, as this defaults to 20ms (40 times per second) I doubt that this would have any affect, and the limit wo;; be set by the driver...