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

NIDEC CoE Error when power up

NIDEC CoE Error when power up

Qeslo
Established Member

Hello.

 We try to set up a Nidec Digitax M753 via Ethercat (CoE) with our Core X3. (SM01.20.5)

We managed to set up axis profile and axis. If we move the drive via Inverter, the current position changes on our Web interface (Core).

So communication it self is working.

As soon as we set the power on (either via MC_Power or via Web interface) we get the following error.

Qeslo_0-1697721064990.png

 

We tried several things described in other topics regarding that issue but nithing solved it.

Does anyone has an idea what to do next?

 

Thanks a lot

 

Here are the versions of the used app and other information

Qeslo_1-1697721158493.png

 

Qeslo_2-1697721195970.png

Qeslo_3-1697721218586.png

Qeslo_4-1697721241551.png

Qeslo_5-1697721262744.png

Qeslo_6-1697721303661.pngQeslo_7-1697721319121.png

Qeslo_8-1697721340907.png

 

Thanks a lot

4 REPLIES 4

CodeShepherd
Community Moderator
Community Moderator

So I guess you already have seen e.g. this topic? We think that the drive needs to long to witch power on after it got the command from our control. This happened at some of the other 3rd party drives also.

To get some more insights please switch on traces of the axisprofile (data layer path trace/rexroth-automationcore/units/comm/axisprofile) and create a system report after error occurred. See how to mentioned here.

Hello,

attached you can find the system report from our system.

Thanks in advance

CodeShepherd
Community Moderator
Community Moderator

As assumed we can see in the system report that our ctrlX MOTION shows an error that drive needs to long to react on the power on command. So it seems that probably the 3rd party drive is not following CiA 402 conventions completely or in an other way then expected.

Did you test with an early adopter version 2.4? 

Is this still an issue or can this topic be closed?

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