Page 1 of 3

RADIO PANEL

Posted: 16 Sep 2019, 21:38
by alexis_maria
Goodnight:
I am trying to modify standard COM1 profile

In tuner INNER clockwise and counterclockwise I have in 0.05 and it works changing 135.200 ... 135.250 ....

I can't change 135,200 ... 135,205 ...

Although change tuner INNER clockwise and counterclockwise in 0.005. If I put the latter nothing moves.

Re: RADIO PANEL

Posted: 16 Sep 2019, 21:43
by c0nnex
please attach your profile or open a ticket

Re: RADIO PANEL

Posted: 16 Sep 2019, 21:45
by alexis_maria
c0nnex wrote:
16 Sep 2019, 21:43
please attach your profile or open a ticket
add. Thank´s c0nnex

Re: RADIO PANEL

Posted: 16 Sep 2019, 21:51
by alexis_maria
c0nnex wrote:
16 Sep 2019, 21:43
please attach your profile or open a ticket
if you want we can try this profile of yours

Re: RADIO PANEL

Posted: 16 Sep 2019, 22:06
by c0nnex
Oh Xplane ....
The default profile is programmed to use events, not data changes. The changes will be done by xplane.

Just checked and it works fine.
Increment the HZ 833 data values. It supports 8.3 Hz spacing. (note the values are in Hz not Khz!)

Code: Select all

<EventDefinition xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" Trigger="TUNER_INNER_CLOCKWISE">
  <EventActions xmlns="http://www.fsgs.com/SPAD">
    <EventActionChangeValue TargetDataDefinition="XPLANE:SIM/COCKPIT2/RADIOS/ACTUATORS/COM1_FREQUENCY_HZ_833" Value="5" ValueOperation="Increment" />
  </EventActions>
</EventDefinition>
(Select all , copy to clipboard, paste in SPAD.next)

Re: RADIO PANEL

Posted: 16 Sep 2019, 22:12
by alexis_maria
Ufff Connex as if he spoke to me in Chinese, (it's a language I don't understand).

Fiddling I have made good progress for a320FF and the radio to move.

I'm going to keep fiddling to see if I get everything to work in the a320.

I keep you informed of the progress, because I will surely need your help to finish it

Thanks cOnnex

Re: RADIO PANEL

Posted: 16 Sep 2019, 22:13
by alexis_maria
alexis_maria wrote:
16 Sep 2019, 22:12
Ufff Connex as if he spoke to me in Chinese, (it's a language I don't understand).

Fiddling I have made good progress for a320FF and the radio to move.

I'm going to keep fiddling to see if I get everything to work in the a320.

I keep you informed of the progress, because I will surely need your help to finish it

Thanks cOnnex
I had not seen what you put me to copy and paste in Spadnext

Re: RADIO PANEL

Posted: 17 Sep 2019, 01:04
by c0nnex
- Click on "Select All" next to the Code: in the post viewtopic.php?f=6&p=57604&sid=8fae8877e ... 421#p57602
- Press CTRL-C to copy the code to the Clipboard
- In SPAD.neXt goto Radio-Panel , select COM1 and upper panel
- Click on the little Arrow next to "Edit Event" and select paste

Re: RADIO PANEL

Posted: 17 Sep 2019, 22:25
by alexis_maria
c0nnex wrote:
17 Sep 2019, 01:04
- Click on "Select All" next to the Code: in the post viewtopic.php?f=6&p=57604&sid=8fae8877e ... 421#p57602
- Press CTRL-C to copy the code to the Clipboard
- In SPAD.neXt goto Radio-Panel , select COM1 and upper panel
- Click on the little Arrow next to "Edit Event" and select paste
Thank´s c0nnex. I go to test.

Re: RADIO PANEL

Posted: 22 Sep 2019, 23:28
by alexis_maria
c0nnex i have other problem with the radio panel

I use a dataref to change the stby frequency to active and vice versa.

<EventDefinition xmlns: xsd = "http://www.w3.org/2001/XMLSchema" xmlns: xsi = "http://www.w3.org/2001/XMLSchema-instance" Trigger = "ACTIVATESHORT">
   <EventActions xmlns = "http://www.fsgs.com/SPAD">
     <EventActionControl TargetDataDefinition = "XPLANE: a320 / RMP1 / Exchange_button" Value = "0" ValueOperation = "Set" />
   </EventActions>
</EventDefinition>

The button has to be at 0 but when the active has to go to 1 to run and return to 0 immediately.

I can't get it in spite of changing the event to 1, setting 50m / s delay and identifying event to 0

It has already happened to me with some FF events that when they are at 0 and they have to go to 1 to run and return to 0 immediately, they don't go correctly.