Hello,

I'm trying to figure out why the LED light won't turn on or off. I created a very simple script where the light is supposed to turn on as soon as I click on "Test."

 

 

 

Working fine for me.

Is your X-Touch in MC mode by any chance?

Edited December 4, 20241 yr by Lorby_SI

7 minutes ago, Lorby_SI said:

Working fine for me.

Is your X-Touch in MC mode by any chance?

MC Mode is turned off, in fact I even made a reset.

New script: 

(A:PITOT·HEAT,·Bool)·0·==·if{0·(>MIDI:3:NoteOn:1:6)}·els{1·(>MIDI:3:NoteOne:1:6)}

As soon as I press the button, it will turn on and off the Pitot Heat, but light wont turn on ( Yes, I added the script in Automated Scripts )
 

Edited December 4, 20241 yr by tangerine

2 minutes ago, tangerine said:

MC Mode is turned off, in fact I even made a reset.

New script: 

(A:PITOT·HEAT,·Bool)·0·==·if{0·(>MIDI:3:NoteOn:1:6)}·els{1·(>MIDI:3:NoteOne:1:6)}

As soon as I press the button, it will turn on and off the Pitot Heat, but light wont turn on ( Yes, I added the script in Automated Scripts )
 

Sorry, no idea. All I can say is that it is working normally for me, no issues.

1 (>MIDI:3:NoteOn:1:6) (SPLIT:1000) 0 (>MIDI:3:NoteOn:1:6)

AAO must be restarted when you disconnect and reconnect the device. Is the XT working normally otherwise? Button events etc. are received? 

11 minutes ago, tangerine said:

(A:PITOT·HEAT,·Bool)·0·==·if{0·(>MIDI:3:NoteOn:1:6)}·els{1·(>MIDI:3:NoteOne:1:6)}

That script is missing a few spaces. Spaces are very important in (AAO) RPN.

(A:PITOT·HEAT,·Bool)·0·==·if{·0·(>MIDI:3:NoteOn:1:6)·}·els{·1·(>MIDI:3:NoteOn:1:6)·}

or you could just do this: (A:PITOT·HEAT,·Bool)·(>MIDI:3:NoteOn:1:6)

But before trying scripts, I would make sure that the basic functionality is there.

 

Edited December 4, 20241 yr by Lorby_SI

1 minute ago, Lorby_SI said:

Sorry, no idea. All I can say is that it is working normally for me, no issues.

1 (>MIDI:3:NoteOn:1:6) (SPLIT:1000) 0 (>MIDI:3:NoteOn:1:6)

AAO must be restarted when you disconnect and reconnect the device. Is the XT working normally otherwise? Button events etc. are received? 

the XT is working normally, Button, events, etc.

3 minutes ago, tangerine said:

the XT is working normally, Button, events, etc.

Then I don't know. Sorry again, but I've never heard of or seen anything like this. Maybe check the device with the Behringer app. And make sure that no other scripts can interfere (= other autoscripts)

Personally, I test these things in offline mode. No need to run the sim just for that.

Edited December 4, 20241 yr by Lorby_SI

12 minutes ago, tangerine said:

(A:PITOT·HEAT,·Bool)·0·==·if{0·(>MIDI:3:NoteOn:1:6)}·els{1·(>MIDI:3:NoteOne:1:6)}

Oh, and I just noticed. The command is "NoteOn" not "NoteOne".

Edited December 4, 20241 yr by Lorby_SI
too many typos - way past my bedtime...

1 minute ago, Lorby_SI said:

Oh, and it just noticed. The command is "NoteOn" not "NoteOne".

Yes, I made the change 5 secs ago and made no difference.

 

6 minutes ago, tangerine said:

Yes, I made the change 5 secs ago and made no difference.

 

Don't know what to tell you.

Use the Behringer X-Touch Editor app to make sure that it is really reset to factory defaults and that the Global Channel is really "1", make sure that MC mode isn't on (then the commands would be different), make sure that no other MIDI device or software (Mobiflight comes to mind) and no other AAO scripts interfere. Restart the PC in case something is stuck in the Windows MIDI pipeline.

Edited December 4, 20241 yr by Lorby_SI

4 minutes ago, Lorby_SI said:

Don't know what to tell you.

Use the Behringer X-Touch Editor app to make sure that it is really reset to factory defaults and that the Global Channel is really "1", make sure that MC mode isn't on (then the commands would be different), make sure that no other MIDI device and no other scripts interfere.

Fixed it!!

I changed the Global Channel from 11 to 1 in the x-Touch Editor, and now everything is working!!!

20 minutes ago, tangerine said:

Fixed it!!

I changed the Global Channel from 11 to 1 in the x-Touch Editor, and now everything is working!!!

I wonder, how could it be 11 after a factory reset? I would expect that to go back to 1 too. How did you reset the device, with the layer a + b buttons?

1 minute ago, Lorby_SI said:

I wonder, how could it be 11 after a factory reset? I would expect that to go back to 1 too. How did you reset the device, with the layer a + b buttons?

Yes, I followed a set of instructions that you shared with someone.

15 hours ago, tangerine said:

Yes, I followed a set of instructions that you shared with someone.

Ok, thanks, thats good to know.