Leds managment

[condor64]

Hello
who could explain OP1 - Alt and Led# ? how to set the both leds on ultimate stick ?

[fallout9]

OP1 is operation number, like for example the button number or axis number to which you want to assign a LED reaction to.
Alt is Alternate color, meaning the color that runs in the background if no other command controls the LED.
The 2 grip LEDs on the MCGU are nr. 10 and 11.
For anything else here's the guide.

[LeLv30_Superbus]

Never mind, I had forgot to add

[Common]
Test Misc Enabled=1
.
.
[User]
User=Developer

in zconfig.ini after I had upgraded. Won't be the last time I'm afraid...

My LED# column is grey and I can't change them like I used to. What gives?

With previous software version I used to flash orange box leds when x,y or z axis was off-centre and it was quite useful. I was able to copy and paste the last two lines with leds 1 and 2 but there is no line to copy with the third led I want to use.

[LeLv30_Superbus]

Is there a hard limit of 12 LED commands? If I hit + button with 12 in place, it kind of pushes 10-11 down and removes the 12th line. I didn't see anything about a limit in the tutorial video.

[Ron61]

Check the correctness of the spelling of the lines and in which file you are writing - according to the screenshot you do not have access to the Leds settings due to the absence of the User=Developer line.

[LeLv30_Superbus]

Thanks for your reply. The above screenshot is not current. I attached it to clear the previous problem which was solved. The LED # looks like this now:

[LeLv30_Superbus]

Anyone? Please try if you can add more than 12 commands.

[Ron61]

The simple version has only 12 events. You can delete something and assign the desired one.
In the NG firmware version, this setting is much wider - 32 events.

[LeLv30_Superbus]

Right, I think I would like that. Could you elaborate what this warning would mean for me, please? Are there potential hazards, is it just a beta version or why is it for testing only with so many exclamation marks?

NG (Next Generation) version is transition to NJoy32 V2.0 - only for testing purposes!!!

Removing some of the existing commands is not ideal for me, because as far as I know all the error indications should be useful, if something breaks down. I have only four commands of my own there: axis centre and shift-button activation. I would like another four or so - if it is safe to do so.

[Ron61]

Without knowing your configuration of the devices connected to the BB, I can only assume that the T-Rudder pedals are connected to the same BB.
Based on this, you can delete the 5th and 6th lines of events (replace with the ones you need). If there are problems with the pedals (they suddenly stopped working), then you can check the connection between the sensor and the controller in the Test-Misc tab along the green arrow. And make decisions based on the result.

NG firmware provides more customization options, but minor bugs are possible. You can always roll back to the previous firmware, which has already "lain down" for some time and did not have these bugs.