You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
within the S7Type the different data types, their converter classes and theirs sizes are described. I think the sizes specified there are the type sizes on the PLC, aren't they? As far as i have seen the S7 PLCs always "reserve" 256 Byte for a STRING type even if the user does not use it completely. I wonder why STRING is specified like that within S7Type:
/** * String type, size must be specified manually */ STRING(StringConverter.class, 2, 0),
and not like this:
STRING(StringConverter.class, 256, 0),
The text was updated successfully, but these errors were encountered:
From my experience (mostly reverse engineered): The S7 String has a dynamic size.
The first byte is the overall size and the second is the current size, but the overall size can't be more than 256 bytes anyway (1 byte length inidicator) and the current size can't be more than the overall size.
within the S7Type the different data types, their converter classes and theirs sizes are described. I think the sizes specified there are the type sizes on the PLC, aren't they? As far as i have seen the S7 PLCs always "reserve" 256 Byte for a STRING type even if the user does not use it completely. I wonder why STRING is specified like that within S7Type:
/** * String type, size must be specified manually */ STRING(StringConverter.class, 2, 0),
and not like this:
STRING(StringConverter.class, 256, 0),
The text was updated successfully, but these errors were encountered: