Yeah, I can't completely or properly support some datatypes. MESSAGE configurations don't come through. Types supplied by I/O modules are often scrambled. L5X just doesn't contain all necessary details to reconstruct some of these.
Yeah. That servers two purposes: 1) provide type information while browsing, and 2) discourage wholesale dragging and dropping of complete folders. (Don't do that!) You can see that the actual OPC item paths do not have the type info.
Hmmm. That might be due to the base (built-in) datatypes within my module were pulled from a V20 processor. I may have to expand that support. If an item is missing from a user-created UDT, please let me know.
Actually, these do exist in your project. All booleans in a Logix UDT must be "hosted" by an integer datatype. When you create booleans in UDTs in RSLogix, it hides SINTs that hold them. I don't support hiding these members. It is easy to see this in an L5K format export.
RSLogix supports external creation of booleans in UDTs as members of INTs, DINTs, and DWORD types, and they can skip bit numbers. And the host integers can be visible . But if you import such an L5K, those datatypes will not be editable within RSLogix. Many datatypes supplied by I/O modules have such members (to get the control/status bits in the right places).