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

API for ctrlX drive

aFouraker
Occasional Contributor

API for ctrlX drive

Does the ctrlX drive have a REST-API that can be used to gather data? The use case would be, for example, to monitor the temperature of a drive with an edge device. In this way, a ctrlX core could be used to make requests through Node-Red to the ctrlX drive. 

Tags (3)
6 REPLIES 6
Jochen_Mueller
Community Moderator

Re: API for ctrlX drive

Hello Alex

as far I know there is no rest API interface for the ctrlX DRIVE.

But if you use it under a ctrlX CORE I would advice to use the DriveConnect app. Here all drive parameters are mirrored into the datalyer which can be read via rest interface.

Regards

Jochen

CodeShepherd
Community Moderator

Re: API for ctrlX drive

There is no REST API directly in the ctrlX DRIVE. But when using a ctrlX CORE you can read drive parameter via the REST API of the Data Layer.

  1. Via the DRIVE Connect App:
    ctrlX CORE Data Layer drivesctrlX CORE Data Layer drives
  2. Via the EtherCat master:
    ctrlX CORE Data Layer device accessctrlX CORE Data Layer device access
aFouraker
Occasional Contributor

Re: API for ctrlX drive

Is this true when the drives are not configured for EtherCAT? For example, when the drives on a system with a different master, say an XM with sercos, will drive connect find and expose the parameters?  

CodeShepherd
Community Moderator

Re: API for ctrlX drive

The Drive Connect App is a function of the ctrlX CORE. So it is not available on a XM controller.

aFouraker
Occasional Contributor

Re: API for ctrlX drive

Yes, that part is clear. The question was if another master control is connected to the drives, an XM using sercos for example, could the drive connect app on the ctrlX core be plugged into the backend of the network and still get access to the drives? 

 

I tested this in the meantime and the answer is yes, this is possible. 

aFouraker
Occasional Contributor

Re: API for ctrlX drive

To elaborate a little more, this is the setup that I was able to get working. The XM controls the real time fieldbus over sercos in a line topology. The ctrlX access the drives with the drive connect app over the NRT channel of sercos by plugging into the last port on the system. The primray purpose here is to get access to the drive data for systems that are not yet compatible with ctrlX. In this case, the ctrlX will gather and send/store data on some interval using node-red to make requests from the data layer. 

aFouraker_0-1655811532432.png

 

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