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

Accessing drive parameters from PLC Engineering software

Accessing drive parameters from PLC Engineering software

Lide
Member

I have created three virtual axes and I am trying to access their parameters from the PLC Engineering software. To do this, I have tried using the CXA_DATALAYER and CXA_PLCOPEN libraries, but the MB_ReadParameter function does not appear. How can I do this?

5 REPLIES 5

CodeShepherd
Community Moderator
Community Moderator

Please always add full screen sceenshots so we get a better overview.

What exactly do you mean by "but the MB_ReadParameter function does not appear"? 

Virtual axes do not have Servodrive (SoE) or CAN (CoE) parameter at all.

You can use the CXA_EtherCatMaster library for accessing drive parameter directly.

Thank you for your reply.

I understand that virtual axes do not have Servodrive (SoE) or CAN (CoE) parameters, and that the CXA_EtherCatMaster library should be used for accessing drive parameters directly.

In my case, I am working on my final degree project, and I have created a VirtualCORE with three virtual axes within it. I am currently programming the operation of these axes using PLC Engineering. I would like to check that the axes are referenced for the initial conditions program.

For this reason, I am trying to find out how to access the parameters of the virtual axes (if possible), since I would like to access the parameter S-0-0403.0.0.

However, from your response, I understand that this may not be possible. If so, is there any other way to know if the axis is referenced? (Although I imagine that since it is a virtual axis, it will always be referenced, I would like to be able to include the referenced check in the initial conditions program, as would be done with a real axis).

I would appreciate any guidance you can provide on this matter.

Thank you for your reply.

I understand that virtual axes do not have Servodrive (SoE) or CAN (CoE) parameters, and that the CXA_EtherCatMaster library should be used for accesing drive parameters directly.

 

In my case, I have created a VirtualCORE with three virtual axes within it. I am currently programming the operation of these axes using PLC Engineering. I would like to check that the axes are referenced for the initial conditions program.

 

For this reason, I am trying to find out how to access the parameters of the virtual axes (if possible), since I would like to access the parameter S00403.0.0.

 

However, from your response, I understand that this may not be possible. If so, is there any other way to know if the axis is referenced? (Although I imagine that since it is a virtual axis, it will always be referenced, I would like to be able to include the referenced check in the initial conditions program, as would be done with a real axis).

 

I would appreciate any guidance you can provide on this matter.

Jochen_Mueller
Community Moderator
Community Moderator

short additonal information:

We are currently working at a Datalayer struct which displays some drive data automatically. This you can use for your PLC sequence. At the screenshot you see the availalbe drive data, e.g. the homing status you want to check. This will be availalbe for version 2.6.

All other drive information you have to use FB of the CXA_DATALAYER, as you mentioned. And you have to make a selector if you have connected "real" drives or not.

By the way if you use our recommended motion interface you will have the data directly inside the PLC, and can use it very comfortable. ( see second screenshot)

note: the screenshot shows a virtual axis. you see here the reference status = FALSE. It is still a bug and will be corrected soon. So virtual axis should always homed...

Jochen_Mueller_0-1716568334685.png

Jochen_Mueller_1-1716568460230.png

Thank you for the detailed explanation and guidance.  I'll explore these options in my PLC program.

In my current setup using CXA_MOTION_IF_USER library version 10.20.1.7, I'm unable to see the DeviceStatus within arAxisStatus_gb[1].Data. I'll download the recommended version to see if this resolves the issue.

Thank you for your valuable assistance!

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