Dear Community User! We have started the migration process.
This community is now in READ ONLY mode.
Read more: Important information on the platform change.

cancel
Showing results for 
Search instead for 
Did you mean: 
SOLVED

bug: Ctrlx I/O Engineering Value Size Error

bug: Ctrlx I/O Engineering Value Size Error

ArcherThompson
Established Member

When configuring Some IO I ran into an issue with the following error message when building:

Value was either too large or too small for a UInt32.

ArcherThompson_0-1690318092730.png

The build however the build does not finish to show errors related to show the value in question.

The value in question was the auto generated values for S-0-0390 which should be a UDint and loads as UDint_hex. So the error pop is correct but the location is not described, the popup also seems to cancel the build instead of letting fail. 

Compiler version: 3.5.19.10

Ctrlx IO Engineering version: 1.20.1

Reloading the project or restarting the program does not resolve the issue.

Expected Behavior:

  1. If an invalid type assignment occurs the location should be recorded and shown in the build report.
  2. Parameter should load the correct value type (UDINT instead of UDINT_hex).
    1. ArcherThompson_2-1690318862597.png
2 REPLIES 2

CodeShepherd
Community Moderator
Community Moderator

If type changed by hand to UDINT is it then working?

In my ctrlX IO Engineering (1.20.1, compiler 3.5.19.10) the value is changed automatically to UDINT when pressing compile.

I will check the warning and behaviour with our R&D.

The shown error is not an compiler message it is an unexpected exception. So there won't be a better hint on the location.
The reason is the invalid data type that is predefined in the ESI file of the drive. When selecting process data or startup parameters the unknown data type was used and this caused problems in further processing.
 
Already in v1.20 (maybe earlier) this was fixed by CODESYS. When selecting a new entry for startup parameter the data type gets set to a correct value.
 
But the fix only applies for new projects. For old projects / archives from older versions / imports the data type has to be fixed manually.
Icon--AD-black-48x48Icon--address-consumer-data-black-48x48Icon--appointment-black-48x48Icon--back-left-black-48x48Icon--calendar-black-48x48Icon--center-alignedIcon--Checkbox-checkIcon--clock-black-48x48Icon--close-black-48x48Icon--compare-black-48x48Icon--confirmation-black-48x48Icon--dealer-details-black-48x48Icon--delete-black-48x48Icon--delivery-black-48x48Icon--down-black-48x48Icon--download-black-48x48Ic-OverlayAlertIcon--externallink-black-48x48Icon-Filledforward-right_adjustedIcon--grid-view-black-48x48IC_gd_Check-Circle170821_Icons_Community170823_Bosch_Icons170823_Bosch_Icons170821_Icons_CommunityIC-logout170821_Icons_Community170825_Bosch_Icons170821_Icons_CommunityIC-shopping-cart2170821_Icons_CommunityIC-upIC_UserIcon--imageIcon--info-i-black-48x48Icon--left-alignedIcon--Less-minimize-black-48x48Icon-FilledIcon--List-Check-grennIcon--List-Check-blackIcon--List-Cross-blackIcon--list-view-mobile-black-48x48Icon--list-view-black-48x48Icon--More-Maximize-black-48x48Icon--my-product-black-48x48Icon--newsletter-black-48x48Icon--payment-black-48x48Icon--print-black-48x48Icon--promotion-black-48x48Icon--registration-black-48x48Icon--Reset-black-48x48Icon--right-alignedshare-circle1Icon--share-black-48x48Icon--shopping-bag-black-48x48Icon-shopping-cartIcon--start-play-black-48x48Icon--store-locator-black-48x48Ic-OverlayAlertIcon--summary-black-48x48tumblrIcon-FilledvineIc-OverlayAlertwhishlist