I have a brain that writes and reads some data to the modbus.  One of the rungs reads a bit and sets an LED (#1050).  It reads other bits and also sets LED's 1051, 1052 and 1053.  The latter 3 work fine, but the first one does not work when Mach starts.  This is a torch on LED.  After I start Mach3, if I hit the torch on button, the PLC relay clicks on and the status bit mapped to LED 1050 in the brain goes high...but the brain does not switch the LED.  If I turn the torch off then back on, it starts working.  All of the other LEDs, which are handled the same way, work fine.

What happens is when I click the ON button, a script runs that says SetModOutput(2,1).  This sets the output bit in the PLC, the torch relay turns on and status bit V1500.3 is set.  This is mapped as a modbus input in Mach and is mapped to LED 1050.  When V1500.3 goes high, LED 1050 comes on...Except when Mach first opens.

I know the status bit is going high because I can map it to input 4 and the input 4 LED works properly.  Any thoughts on why I have to cycle this particular output in order to get the brain to act on it?

I would pick MUCH higher range of ULEDs, most in that range, have Wizards and all kinds of stuff reading/writing to them...

What's the top of the range for user LED's?