Understandably. I still have to look up datatypes sometimes when I forget which size a SINT has or how high a TIME can go.
Hey Bruno, did you apply the discussed changes to the documentation yet?
Renaming Int and Float (to DINT and REAL, for instance) would compel us to review all the documentation and rewrite Control I/O and the SDK. We believe in “If you break it, break it good”. So we are rethinking how to make Factory I/O compliant with IEC 61131 standard and how drivers and data types should work together. There is definitely a lot of work to be done on the drivers side in order to improve user experience and driver flexibility.
Okay.
Even if it’s not compliant, that’s not that big of a deal if it’s documented properly. For now I think to update the documentation (to write that INT takes 4 bytes and not 2) and to add some more details to the documentation of the RFID reader (Array starts at 0 for example) would be good.
Agree, added to the dev roadmap. Most likely it will be included in the next release.