Cockpit Sonic throttle and Ifly disengage

[jhztm]

Hello

My Cockpit Sonic throttle works nice with the standard FSX Boeing 737-800 if I use the PMsystem offset in the CS B737 driver

Then I can start the 737 by the throttle, ARM Toga (in FSX) and use the Toga button on the Trottle device

If I push on CS throttle the disengage button Toga stops (as well as ARM toga goes to off)

Same with Ifly B737-800 works the same up until disengage

the disengage button on the CS throttle will not disengage nothing happens, servo's stay active, and ARM toga button stays armed

I have checked all type off offsets but none seems to be activated directly by the CS button push

In the wideFS log with log=yes I can't see offsets being written

While for the parking brake I can see this event

So someway the buttonpushes must go to FSX as button commands

Does anyone know how to monitor these buttons of an external device and assign proper Lua functions to them

Many thanks

Jan Harskamp

I

[Pete Dowson]

Does anyone know how to monitor these buttons of an external device and assign proper Lua functions to them

If FSUIPC isn't seeing buttons on the device it isn't a Windows-style joystick device, nor a GoFlight or PFC device.

Doesn't the Cockpitsonic driver just write direct to offsets? What exactly do you want to do? I can't really work it out from your message.

Are you trying to use iFly's full cockpit model and PM together? I wouldn't have thought they were compatible.

Regards

Pete

[jhztm]

If FSUIPC isn't seeing buttons on the device it isn't a Windows-style joystick device, nor a GoFlight or PFC device.

Doesn't the Cockpitsonic driver just write direct to offsets? What exactly do you want to do? I can't really work it out from your message.

Are you trying to use iFly's full cockpit model and PM together? I wouldn't have thought they were compatible.

Regards

Pete

Pete

I use Ifly in FSX and only the PMoffset setting in the CockpitSonic B737 driver (so not in FSX)

I use the PMoffset setting just because of then the standard FSX 737-800 does work properly then (can disengage)

As far as I can find the driver does not write directly to the offsets in the button actions

I have tested this by doing a session releasing parking brake, ARM toga, Toga with CSbuttonA, Disengage with CSbuttonB , set parking brake

When I go through the wideclient.log (in log=yes mode) I can easily find parking break release write , and parking brake set write

In between there are several other writes but none connected to the Toga or Disengage action

Those button actions must be transferred by WideFS because only in that way I connected the CS Throttle

I have done simmelar session connecting the CS throttle directly to the (FSX en FSuiPC) computer

Also then there is no button action to be seen in the FSuiPC interface screen

I am assuming that WideFS and FSX only communicate via offsets or via " button/axis" commands , is that correct or are there more ways of communicating?

So if there is a way to see the button commands send by WideFS to FSX , somewhere in there there should be the commands of CSthrottle

I would like to monitor or see a log of the button/axis WideFS send stream just as I can see the Offsets

Many thanks in advance

Jan

[Pete Dowson]

I use Ifly in FSX and only the PMoffset setting in the CockpitSonic B737 driver (so not in FSX)

So iFly gauges and PM do not conflict? That is most odd, because for sure PM and default A/P do so.

I use the PMoffset setting just because of then the standard FSX 737-800 does work properly then (can disengage)

Sorry, I'm lost here. What can disengage? What is this "PMoffset" setting? I don't know the references at all.

As far as I can find the driver does not write directly to the offsets in the button actions

I have tested this by doing a session releasing parking brake, ARM toga, Toga with CSbuttonA, Disengage with CSbuttonB , set parking brake

When I go through the wideclient.log (in log=yes mode) I can easily find parking break release write , and parking brake set write

In between there are several other writes but none connected to the Toga or Disengage action

But if the driver is running on a client under WideFS, there are only offsets for it to do anything with. Unless it has its own communication to the FS PC and another part of Cockpitsonic installed there?

I have done simmelar session connecting the CS throttle directly to the (FSX en FSuiPC) computer

Also then there is no button action to be seen in the FSuiPC interface screen

So, it is certainly using offsets.

Are you sure it isn't simply using the 3110 offset to send FS controls?

I am assuming that WideFS and FSX only communicate via offsets or via " button/axis" commands , is that correct or are there more ways of communicating?

The only way is only offsets for an application program. The joystick buttons are only those it can read from Windows for standard joystick devices or from GFdev.dll for GoFlight devices. No axes at all through WideFS.

I would like to monitor or see a log of the button/axis WideFS send stream just as I can see the Offsets

If there were buttons being sent you'd see them in the FSUIPC Buttons & Switches tab in FS.

Pete

[jhztm]

Pete

Many thanks for your advice

The CockpitSonic throttle indeed works via Commands

I could find it by activating logging of FSUIPC within FSX

the logging is very adequate to find these things

The CSthrottle only operates when AT Arm is engaged

Then offset 0810 has value 1

The autothrottle is activated by button and sends (If AT arm) command Toga 65861

To disengage AT by button on CSthrottle the button sends command AT Arm 65860

In FSX standard 737-800 this resets ATarm and by that also sets offset 0810 to 0 as well as offset 080C

In Ifly 737-800 you can activate (on screen, in cockpit) ATarm but offset 0810 stays 0

If I set offset 0810 manually to 1 it is reset by Ifly almost immediate

On screen the Ifly ATarm switch on screen toggles on and off with every set to 1

Because of the 0 in offset 0810 the CSthrottle will not send AT Arm 65860 command and stays AT engaged

So now I know the commands by which CSthrottle operates

And I have to find something else to get the Ifly CSthrottle combination working

Kind regards

Jan Harskamp

[Pete Dowson]

In Ifly 737-800 you can activate (on screen, in cockpit) ATarm but offset 0810 stays 0

If I set offset 0810 manually to 1 it is reset by Ifly almost immediate

That's probably because, like most PMDG aircraft, and PM, and many other sophisticated add-on aircraft, the iFly 737 implements its own A/T, and probably A/P too.

And I have to find something else to get the Ifly CSthrottle combination working

This is always a problem with add-on aircraft and add-on hardware. I thought iFly were bringing out an SDK to help cockpit builders interface their hardware to their aircraft? That should tell you how to sort it. Otherwise it's a case of the usual detective work -- maybe mouse macros, maybe L:Vars? Depends what they've done, how it's written.

Regards

Pete