gaab

Posted Saturday at 11:01 PM · Saturday at 11:01 PM

Thanks Ben,

Any ETA ?

Gérard

Posted March 25 · March 25

No,

The "use for" is just not existing and would be of very poor interest compared to the input needed.

Most of the profiles available have a pdf documentation...

Cheers

Gérard

March 22

Hi Ben,

It seams that I have another backward compatibility problem.

In LED section, I get this

Seams to be linked the L:Vars only ... and only at "check variable integrity", because the LED are lighting as expected.

EDIT : deleting the LED conditions and recreating sems to fix the error message, by suppressing the ", Bool" ...

EDIT 2: All LED condition with A:Vars use the format (A:XYZ, unit). So, should I keep the ", Bool" for L:Vars ???

Please help... before I make further updates.

Cheers,

Gérard

March 22

Hi Ben,

On 3/21/2021 at 12:03 PM, BenBaron said:

I am also not seeing this as a valid input anymore.

In a old thread about this ">" question you answered

On 1/4/2021 at 2:18 PM, BenBaron said:

This is, because if the ">" is missing for variables where it needs to be (aka where you want to set a variable), it will be added automatically while parsing the .json. So, basically, it does not matter, if it is in the .json itself, or not.

Easy to fix with Notepad++, but maybe the Import Configurator function should take care of it ???

Just a suggestion for people afraid to tweak the json files (and you don't like it either...)

Cheers,

Gérard

March 20

Ben,

Sorry to bring another topic, but I keep getting configuration issue when using "old" (working) profiles : the ">" is no more recognised with the new bridge

I get it for all the >K: (and >L:) variables...

Cheers

Gérard

March 18

Hi Ben,

My reference is this one Units Of Measurement

And if you try "Pounds per square foot" for ENG OIL PRESSURE, you will get an error in ContentError.txt file.

More interesting, if you look at "GENERAL ENG OIL PRESSURE:index" you will see the unit listed as Psf !

I did not try the Helicopter Specific Variable...

So, once more, we can see inconsistencies on LM officiai documentation... Have fun !

Cheers,

Gérard

March 18

Hi Ben,

I regularly cross-check using the official Learning Center of LM (V5)

- "Pound-force per square foot" is listed in the list of units (as well as Psf), but not "Pounds per square foot"

And there is no such unit as

- PSI scalar 16K

Just to clarify...

Gérard

March 17

Hello Ben,

I want to let you know I had difficulties to install the latest version of the configurator.

The uninstall does not delete the old version and the installer does not overwrite it.

I had to manually remove the old folder to get the last version.

I was "alerted" by the About displaying 2.0 (now shows 2.1, at last...)

Nota :

the Bridge was correctly updated and the Aerosoft Updater reported that

BUT the updater don't take care of the Configurator !

Hope this can help other users.

EDIT : Sorry to let you know that the configurator still use "A:ENG OIL PRESSURE,Pounds per square foot" (instead of Psi) when creating a new condition

and use ""A:ENG FUEL PRESSURE,PSI scalar 16K" ! - never heard about this scalar 16K

Gérard

Posted February 19 · February 19

1 hour ago, BenBaron said:

version 2.1 will also allow you to define multiple press- and release events

Can't wait I was coming to the conclusion that I need multiple press...

Thanks

Gérard

Posted February 18 · February 18

Thanks Ben,

On some "advanced" aircraft the Autopilot is managed by local variable booleans - in order to use the corresponding button on the Bravo, we need to have something like

(L:Switch, bool) ! (>l:Switch, bool)

You convinced my to read and reread this thread ;), and I discovered it was possible to use a variable assignement inside conditions , and found a solution which needs to create 2 conditions for the APMaster "toggle"

          "Conditions": [
            {
              "Variable": "L:ApMaster",
              "Value": "1",
              "VariableIsCustom": true,
              "Condition": "L:ApMaster, bool",
              "ConditionValue": "0",
              "ConditionIsCustom": true
            },
            {
              "Variable": "L:ApMaster",
              "Value": "0",
              "VariableIsCustom": true,
              "Condition": "L:ApMaster, bool",
              "ConditionValue": "1",
              "ConditionIsCustom": true
            }
		  ]

But I would also like to add the condition "ApMaster" true for the other buttons press (HDG, NAV, etc....)

So far, I did not found a solution.... any suggestion ?

Gérard

Posted February 16 · February 16

Hi Ben,

Still asking questions

Is it (or will it be) possible to assign a L:Var value in a PressEvent, instead of a fixed value :

     "PressEvent": [
        {
          "Variables": [
            {
              "Variable": "L:ApRudderServoOn",
              "Value": "1",                                               Would like to assign L:MyVar, number
              "VariableIsCustom": true
            }

the objective being to have a ApRudderServoOn toggle

Thanks

Gérard

Posted January 27 · January 27

Hi Ben,

On 1/4/2021 at 2:18 PM, BenBaron said:

Because there are events like with the FCU HDG, ALT, CRS where we just want to increase/decrease and not only set an absolute value. That's why we are making use of what PMDG provides in their SDK.

Could you give us more information about L:Vars Incr/Decr - I would like to use this kind of facility for some aircraft (not PMDG).

Thanks

Gérard

Posted January 24 · January 24

20 hours ago, DaveCT2003 said:

I understand what you're looking for and I believe that is being worked on.

Great - thanks Dave ... and the driver team

Gérard

Posted January 23 · January 23

Hi,

Axis support through P3D for the Yoke made sense (I can't imagine a different configuration for them !)

But now with the Bravo, the 6 axis configuration can change from one aircraft to another and it becomes tedious to separately load a Yoke profile, a Throttle profile, and after in P3D startup screen a P3D configuration file !

A minimalist solution would be to associate for an aircraft these 3 config profile in a single "configuration set".

But the best would be allow axis configuration for each device (one day we should get also a rudder pedal ...)

Please consider this for a future update.

Cheers - Gérard

Posted January 13 · January 13

Hi Ben,

Thanks for your feedback

Gérard

Posted January 9 · January 9

36 minutes ago, BenBaron said:

But I will actually remove the necessity of having a unit defined for "INT" variables at all in one of the future updates and refine the whole parsing process.

Thanks for the feedback.

Great job - I really appreciate the follow up you are doing on this great piece of hardware and software.

Cheers

Gérard

Posted January 8 · January 8

13 hours ago, BenBaron said:

Hi Gérard,

where does this message pop up:

"Error: Invalid variable (missing ':', did you forget a macro?): INT:REV_0." ?

This is internal state and cannot be used anywhere else. In this case, it prevents unlocking engine 1 full reverse, if the reverse lever has not been lifted up.

I understand the idea and found it very insteresting.

I borrowed this approach from one of your PMDG profile - and I saw it first on PMDG forum concerning Bravo and Reverses...

I implemented it in a non-PDMG I built for a turboprop. It is why I was wondering if that could be the reason.

The error is in the infamous(!) ContentError.txt which is always ON on my PC (and helped me to address a lot of XML errors in a lot of aircraft - no name

I have found the reason (my error) and was able to fix it, but the configurator is partly guilty !

When creating a condition, you have a dedicated field for the unit

but when creating the variable, there is no such unit field.

I did not specified in the name field the unit (ok, my fault, but I plead not guilty), and I got the message.

This means that the INT field is not recognized as such and sent to the simulator, which in turn is unhappy

Adding the ",bool" solves the issue.

Please, we definitively need a short document which describes the different syntax cases. Because, if I look in the various profiles published, I don't see a unit specified for the variable, if it is a L:xxx. It is very confusing and it is not the "detail" you pay attention to in a tutorial...

Consider also for the next release, better check of the input by the configurator.

Cheers - Gérard

Posted January 7 · January 7

On 1/3/2021 at 9:28 AM, Bert Laverman said:

Gérard,

AFAIK the "INT" variables are local state for the Honeycomb Bridge, and can be created at will. The "INT:REV_0, bool" and "INT:REV_1, bool" are used to store the current state of the reversers, so you can use these in other buttons' conditions.

Cheers,

Bert

Looks like "INT:REV_0, bool" is not internal to the bridge and P3D dislikes it !

Error: Invalid variable (missing ':', did you forget a macro?): INT:REV_0.

Is this syntax only meaningful with the "PDMG" interface ?

Anyway, this could be replaced by an usual LVar....

I really start to like this Beta Throttle - and Notepad++ is my friend

Gérard

January 7

Hi Ben,

I feel stupid - forgot to desactivate all key assignements automatically done by P3D for a new equipment

Looks like this solved my problems - lesson learned

Gérard

January 6

2 hours ago, BenBaron said:

Hi Gérard,

for the first problem, I cannot really help you but I suggest you monitor if it is coming back. Maybe also try changing your USB port or avoid using a USB hub to see if that solves that issue.

Hi Ben,

My usb connection is directly on the PC (replacing the old Saitek connection).

Is there a log file created somewhere by the AFC ?

Gérard

January 6

I was using the untouched "Default_Throttle"

Got several issues, the most disturbing being (I really fear a short circuit ...)

- Autopilot switch = set on/off autopilot (which is OK) AND activate a "Gear_toggle" which of course does not exist

- few minutes after I got a message from AFCBridge : "Woopsie! Somehow BFC_Trottle got discontected"

- and ONLY the Autopilot switch was acting and continuing to maneuver the GEAR, no other switch recognized and no LED lighted

- nevertheless the Axis assigned throught P3D Axis Management are still acting

Concerning the "Default_Throttle" profile I got 999 errors (the max contenterror.txt reports)

Error: Invalid unit specified for "A:ENG OIL PRESSURE:1": "Pounds per square foot".

Default_Throttle.json
"Condition": "A:ENG OIL PRESSURE:1, Pounds per square foot",

The Learning center P3DV5 specifies
GENERAL ENG OIL PRESSURE:index Engine oil pressure Psf

Will do another test tomorrow.

Posted January 6 · January 6

On 1/5/2021 at 1:44 AM, gaab said:

Some suggestions for the configurator :

- confirm that the profile as been updated (and activated).

- for a next version : allow to customize the name of the buttons. For example your "Bus1 On" is my "Seat Belt Off". (could be a kind a "translation" table...)

After several Configuration Profiles built, considering the number of switches (specially on the Bravo), it would be very useful to have a "Configuration" summary :

An html file, with ONE line per Button (or LED), listing only the variable(s) and assigned value (one extra line only in case of existing Release Event), with the option to list also the unassigned buttons.

Example :

  Elevator Trim A Up    Press [K:ELEV_TRIM_UP]
  Elevator Trim A Down  Press [K:ELEV_TRIM_DN]
....
  Toggle 3 ON           Press [L:DC_Gen1_sw (1)]
  Toggle 3 OFF          Press [L:DC_Gen1_sw (0)]
.....
  MultVariable ex       Press [K:LANDING_LIGHTS_ON, L:MY_LANDING_SW (1)]
.....
  Press/Release         Press [L:MyLVar (1)]
                        Release [L:MyOtherVar (-1)]

If Option not allocated buttons
  Elevator Trim B Up   
  Elevator Trim B Down

Thanks

Gérard

Posted January 5 · January 5

11 hours ago, BenBaron said:

Hi guys,

while we always appreciate your input, naturally the focus lies on having all functionality availabe via the ConfigTool, so it does not make much sense explaining the .json structure.

...bound by fixing bugs, providing basic support and implementing missing items to maximize functionality

I undertand and it's OK.

Some suggestions for the configurator :

- confirm that the profile as been updated (and activated).

- for a next version : allow to customize the name of the buttons. For example your "Bus1 On" is my "Seat Belt Off". (could be a kind a "translation" table...)

Happy new year

Gérard

Posted January 2 · January 2

Hi,

It would be great to get a picture showing the .json button number.

The Pdf supplied with the profiles makes it very difficult to understand, clone and adapt a profile for another aircraft.

Question also.

The button json description for the press event has

- a variable zone

          "Variable": "",
          "Value": "",
          "Condition": "",
          "ConditionValue": "",
          "Conditions": [],
          "Repeat": false

- and a variables array, with other contions array...

          "Variables": [
            {
              "DE": "",
              "EN": "",
              "FR": "",
              "ES": "",
              "Variable": "L:xxxx",
              "Value": "",
              "Conditions": [
                {
                  "DE": "",
                  "EN": "",
                  "FR": "",
                  "ES": "",
                  "Variable": "K:AP_ALT_VAR_INC",
                  "Value": "100",
                  "VariableIsCustom": false,
                  "Condition": "INT:FCU_SELECTOR, string",
                  "ConditionValue": "ALT",
                  "ConditionIsCustom": false
                },
				etc...
    		  ]
              "VariableIsCustom": true
            }
          ]

Is the first syntax a compatibity for the previous version YokeInput ?

I see the first form in used in your converted profile from YokeInput and the second in the new provided profiles...

Would also need to get definitive syntax rules.

In some of my converted profile I have ">K:EventIID"

In your supplid profiles "K:EventId" (without ">")

In variables or conditions, sometimes there is a unit specified but I am not able to find a rule :

"Variable": "INT:REV_0,bool",

but

"Variable": "L:ApDisconnect",

It also look like there are special driver variables like "INT:FCU_SELECTOR, string" or "INT:REV_1,bool"

So, I think we need some more info, and tutorial are not the best way to go (may be I am too old fashion

Too much topics addressed in a single session when there is a need for more formal written document.

Hope I am not asking too much

Thanks - Gérard

Posted January 2 · January 2

Duplicate

Sign In

gaab

Content Count

Joined

Last visited

Content Type

Profiles

Forums

Downloads

Posts posted by gaab

Please explain the format of the profile JSON structure

HC Alpha and Bravo do not accurately reflect loaded profiles - P3Dv4.5

new AFC Bridge issue

new AFC Bridge issue

new AFC Bridge issue

Honeycomb Configurator update issue [Solved]

Honeycomb Configurator update issue [Solved]

Honeycomb Configurator update issue [Solved]

Please explain the format of the profile JSON structure

Please explain the format of the profile JSON structure

Please explain the format of the profile JSON structure

Please explain the format of the profile JSON structure

Please add Axis support in the Bravo profiles.

Please add Axis support in the Bravo profiles.

Please explain the format of the profile JSON structure

Please explain the format of the profile JSON structure

Please explain the format of the profile JSON structure

Please explain the format of the profile JSON structure

First flight with Bravo

First flight with Bravo

First flight with Bravo

Please explain the format of the profile JSON structure

Please explain the format of the profile JSON structure

Please explain the format of the profile JSON structure

Please explain the format of the profile JSON structure

Home

Support & Updates