Suppanel

No tag browser, there's a way to do this, VTscada does it somehow and a few others, I assume it's rather complicated. That's fine.
Global tags only, expected this without a tag browser, that's fine and rather common.
Cannot access bit address of Global INT i.e. CRITICAL_ALARMS.3 , That's where my Generator Alarm bit is stored. Unusual not to support this as older programmers love to bit pack words. Probably the only thing on this list I'd suggest you work on next.
Cannot access Discrete Input address i.e. Local:5:I.Data.15 , Also doesn't do the analog inputs but I usually have them scaled. About 50% of scada platform have this limitation.
Cannot use separate Data and Write tags in widgets, as far as I know only Maple systems HMI's and VTscada allow this, everybody else makes you layer the widgets. Really not much of an issue.

Handles UDT dot fields just fine.
Immobilize, oh thank you!
Changing Connections IP address on the panel, sweet! Nobody does this and that's is why I bought it.
Error codes on screen with the list easily found in the menu! Nobody does this!

Overall, five stars, does what I need it to.

Thank you very much for your excellent review !

It was complicated for me to program the Ethernet/IP driver for CLX since the published Rockwell documentation is very little and incomplete.

I think that those who have managed to do more things have achieved it by reverse engineering, but I do not have the means to do something similar.

The tests of the driver were made with a Micro820 PLC, I have no budget to get a CompactLogix.

I will study the possibility of being able to read and write individual bits in integer values in the future.

Thank you !!

16 tag limit per connection widget?

The EIP connection control tries to read all the tags in a single request, although not all the PLC models support it. You can see if several tags are read in a single request by not hiding the control at run time, if an m appears after % means that the multiple reading is active.

On the other hand, no Rockwell published document specifies the maximum size of the request, it seems that in your case that length is exceeded. I will study the problem, in the while try to use several connection controls.

Thank you !!