joystick configuration problem SOLVED

Please do not bother with my previous questions about the joystick, everything is fine now.
The problem was that i was using the wrong AC_ID
Btw is there any way to make the loystick xml file to apply globally by using some thing like
a broadcast AC_ID?
Chris


_______________________________________________
Paparazzi-devel mailing list
[hidden email]
https://lists.nongnu.org/mailman/listinfo/paparazzi-devel

You mean to send the commands to multiple aircrafts at the same time?

That is not possible, since you need a specific AC_ID to get the correct flight plan in order to resolve IndexOfBlock, etc..

On Wed, Apr 6, 2016 at 12:31 PM, Chris <[hidden email]> wrote:

Please do not bother with my previous questions about the joystick, everything is fine now.
The problem was that i was using the wrong AC_ID
Btw is there any way to make the loystick xml file to apply globally by using some thing like
a broadcast AC_ID?
Chris

_______________________________________________
Paparazzi-devel mailing list
[hidden email]
https://lists.nongnu.org/mailman/listinfo/paparazzi-devel

_______________________________________________
Paparazzi-devel mailing list
[hidden email]
https://lists.nongnu.org/mailman/listinfo/paparazzi-devel

Ok that's what i thought also but i couldn't resist asking....

It is logical after all.

Btw is the actual  AC_ID the number that the GCS presents as "ID" on the left upper corner or it is the string with the aircraft's name?

Chris

On Wed, Apr 6, 2016 at 9:31 PM, Felix Ruess <[hidden email]> wrote:

You mean to send the commands to multiple aircrafts at the same time?

That is not possible, since you need a specific AC_ID to get the correct flight plan in order to resolve IndexOfBlock, etc..

On Wed, Apr 6, 2016 at 12:31 PM, Chris <[hidden email]> wrote:

Please do not bother with my previous questions about the joystick, everything is fine now.
The problem was that i was using the wrong AC_ID
Btw is there any way to make the loystick xml file to apply globally by using some thing like
a broadcast AC_ID?
Chris

_______________________________________________
Paparazzi-devel mailing list
[hidden email]
https://lists.nongnu.org/mailman/listinfo/paparazzi-devel

_______________________________________________
Paparazzi-devel mailing list
[hidden email]
https://lists.nongnu.org/mailman/listinfo/paparazzi-devel

_______________________________________________
Paparazzi-devel mailing list
[hidden email]
https://lists.nongnu.org/mailman/listinfo/paparazzi-devel

AC_ID is the number (ac_id of the aircraft in conf/conf.xml)

There is also the aircraft name, which e.g. input2ivy wants as the -ac parameter...

You can use @AC_ID and @AIRCRAFT in your conf/control_panel.xml to automatically insert the id/name of the currently selected aircraft when starting a tool from the menu.

E.g. for Joystick (input2ivy) is specified with `-ac @AIRCRAFT` to pass the current aircraft as parameter...

On Wed, Apr 6, 2016 at 10:54 PM, hendrixgr . <[hidden email]> wrote:

Ok that's what i thought also but i couldn't resist asking....

It is logical after all.

Btw is the actual  AC_ID the number that the GCS presents as "ID" on the left upper corner or it is the string with the aircraft's name?

Chris

On Wed, Apr 6, 2016 at 9:31 PM, Felix Ruess <[hidden email]> wrote:

You mean to send the commands to multiple aircrafts at the same time?

That is not possible, since you need a specific AC_ID to get the correct flight plan in order to resolve IndexOfBlock, etc..

On Wed, Apr 6, 2016 at 12:31 PM, Chris <[hidden email]> wrote:

Please do not bother with my previous questions about the joystick, everything is fine now.
The problem was that i was using the wrong AC_ID
Btw is there any way to make the loystick xml file to apply globally by using some thing like
a broadcast AC_ID?
Chris

_______________________________________________
Paparazzi-devel mailing list
[hidden email]
https://lists.nongnu.org/mailman/listinfo/paparazzi-devel

_______________________________________________
Paparazzi-devel mailing list
[hidden email]
https://lists.nongnu.org/mailman/listinfo/paparazzi-devel

_______________________________________________
Paparazzi-devel mailing list
[hidden email]
https://lists.nongnu.org/mailman/listinfo/paparazzi-devel

_______________________________________________
Paparazzi-devel mailing list
[hidden email]
https://lists.nongnu.org/mailman/listinfo/paparazzi-devel