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

ctrlX Core HW version different error during the login

ctrlX Core HW version different error during the login

ericvergara
Occasional Contributor

Hello, 

We have a ctrlX with the 1.14 version and we have programmed an application with the ctrlX PLC 1.14.1,

ericvergara_0-1666867527564.png

The device of the project is a real ctrlX Core with the 1.14 version:

ericvergara_1-1666867585130.png

The problem is that everytime we perform the download the system returns an error, it seems that there is a mismatch between the ctrlX Core configured in the project and the real one, however both of them are in the 1.14 version,

ericvergara_2-1666867719406.png

Does anyone know why is this happening?

Many thanks,

3 REPLIES 3

CodeShepherd
Community Moderator
Community Moderator

We some more information about what your PLC code is using:

  • Do you try to use codesys alarming?
    This is not supported in 1.14.
  • Do you try to use CXA_MOTION/CXA_PLCOPEN/CXA_MOTIONINTERFACE?
    The ctrlX MOTION app would be needed for this.

ericvergara
Occasional Contributor

Hello CodeSheperd,

We do not use the ctrlX Motion libraries, we have performed a test in an empty project and it seems that there are errors in the following libraries:

  • CAA_Storage STO
  • 3S Storage STI
  • CAA DUTIL DTU

If we declare a dtu.GetDateAndTime variable when we compile there are 0 errors (once we install the CAA DUTIL DTU library), however if we download it to the Core the same error appears

ericvergara_0-1667380452025.png

We have upgraded the Core to the 1.16 version but still this error pops up,

I attach here also the test program,

georkueh
Community Moderator
Community Moderator

Hello,

the problem regarding the unresolved externals results from the fact, that the library CAA DTUtils has not been supported with the ctrlX CORE devices. We addressed this issue to our development, but unfortunately it will be RM 23.03 that the bug will be fixed. So please follow the ctrlX CORE release notes!

kind regards

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