Axis homing command cannot be started

[CtrlDiogoC]

Hello,

We are using an Indradrive HCS01 (HCS01.1E-W0006-A-02-B-ET-EC-NN-NN-NN-FW) and parametrized it on IndraWorks Ds.

The homing procedure is set to Fixed Stop, as we want the axis to perform the homing by torque. We command the homing routine on the IndraWorks side and it works fine.

However, on the Nexeed side, when we execute the homing command, we get the following error:

We have the axis linked to an NC Axis in TwinCAT Motion.

Could you please help us in this topic?

[Thorsten_Brach]

Unfortunately I am not an Beckhoff NC expert but,
is it possible to home the axis from the TwinCat NC Control-Panel inside TwinCat ?

I think, as long as it does not work directly in the TwinCat NC Console,
you do not have to look for the NexeedAxis object...

Is there a reason why you need to use one single axis as NC ? 
I think it should also be possible to use the IndraDrive natively....

[CtrlDiogoC]

Thanks for your reply.

I don't believe it is possible to home the axis directly through the TwinCAT NC. We can only call the MC_Home function block, which I think Nexeed takes care of, inside the NexeedAxis object homing command.

I was first using NC to jog the axis without accessing IndraWorks Ds.

I think I don't need the NC right now, but it should work both ways, right?

[Thorsten_Brach]

Yes it should work both...

As I said, I am not an NC expert - but in the panel there is the F9 key to execute the homing ?

https://infosys.beckhoff.com/english.php?content=../content/1033/tf50x0_tc3_nc_ptp/10663193867.html&...

This button does not work?

In my experience, the problems with NC are 90% due to the NC configuration - if something doesn’t work...

As you have correctly noticed, the axis object simply calls the homing function of the NC.
If there is an error during the homing, then the problem must be in the NC,
the axis object ony shows the error in the HMI but is not the cause...

This can be deduced from the error number  :

https://infosys.beckhoff.com/english.php?content=../content/1033/tc3ncerrcode/513151243.html&id=1812...

As you can see, this error number 19210 is something which comes from the NC...

[Thorsten_Brach]

Which Firmware / Peripheral do you use ?

I checked the NexeedEcRxIdMPB_NC peripheral and for me it looks like, that the Block-Homing is not supported...

I don’t know if there is a technical reason,
why you can not select it in the NC Peripheral or if it was just not implemented...

You can try to change the homing mode in the code yourself and set it to Block :

Maybe this woks and simply the selection in the OOD is missing...

Please give me a feedback - then we could modify the OOD accordingly

BTW:

In the native Peripheral there is the option to select Block-Homing...