https://forge.codesys.com/forge/talk/Motion/thread/e697baacf0/2021-01-21T06:13:04.904000ZRecent posts to SMC_FB_WASN'T_CALLED_DURING_MOTION Error With MC_Home2021-01-21T06:13:04.904000Z2021-01-21T06:13:04.904000Zeschwellingerhttps://forge.codesys.com/u/eschwellinger/https://forge.codesys.comcfe4667cb6c0657b67289bf525d3047388d9e8ac

<div class="markdown_content"><p>If you use the generic DS402 driver these parameter should be there.<br/> In which version is SoftMotion?<br/> You could update SoftMotion by updating the SoftMotion package, current version is 4.9.0.0</p></div>

2021-01-20T22:18:44.470000Z2021-01-20T22:18:44.470000Zmike-at-gmshttps://forge.codesys.com/u/mike-at-gms/https://forge.codesys.com8ed2547b55df2ed59670de293dca3ec268fe43b1

<div class="markdown_content"><p>I did not know about the device configuration option, thank you.</p> <p>I have an 'axis' function block that encapsulates all the functionality of an axis. All the MC function blocks are included and cyclically called based on inputs to the main FB. My motion FB's are all called the same way, which is why this error is so frustrating. I cannot see any difference between my calls to MC_Power or MC_MoveAbsolute and my call to MC_Home. I would expect a different error if my drive object was not configured correctly.</p> <p>Under the new Parameter tab, I do not have the same 'DSP402 configuration' fields as in your picture (I only show DSP402.bImmediateDisabling). Does this mean Homing (with MC_Home) is not supported? That would explain a lot.</p> <p>Thank you.</p></div>

2021-01-20T20:00:18.701000Z2021-01-20T20:00:18.701000Zeschwellingerhttps://forge.codesys.com/u/eschwellinger/https://forge.codesys.com887fc6a51e94d71429b210e205c79a31996ce339

<div class="markdown_content"><p>The drives are different in case the behavior, which bit should bei set etc...<br/> There are some Parameter to set may this helps.<br/> Another point to check in which task die you call mc_home FB?</p></div>

2021-01-20T19:17:10.908000Z2021-01-20T19:17:10.908000Zmike-at-gmshttps://forge.codesys.com/u/mike-at-gms/https://forge.codesys.com6a72417d40270cafcec06e5a40f8ad3cec80d986

<div class="markdown_content"><p>I am using Servotronix CDHD, Yaskawa Sigma 7 and Oriental Motor stepper drives. The CDHD is the drive I am currently trying to home. I can also home the axis directly so that is not the problem.</p> <p>Thank you.</p></div>

2021-01-20T19:09:03.909000Z2021-01-20T19:09:03.909000Zeschwellingerhttps://forge.codesys.com/u/eschwellinger/https://forge.codesys.comfbe5c1522645cc9f2dac24a9633581436dbc744e

<div class="markdown_content"><p>Hi,<br/> Which drive is connected?<br/> BR<br/> Edwin</p></div>

2021-01-20T14:53:50.664000Z2021-01-20T14:53:50.664000Zmike-at-gmshttps://forge.codesys.com/u/mike-at-gms/https://forge.codesys.coma07805e5e2b536ea3efe88edbf6f16297e211531

<div class="markdown_content"><p>Hi,</p> <p>I have a motion project that is working fine except when I call MC_Home. My axis (AXIS_REF_SM3) is enabled, at Standstill, and I can move the axis just fine. But, when I enable my MC_Home FB, it aborts right away and the axis object (not the FB) gets a "smc_fb_wasn't_called_during_motion" error. One odd thing is that the 'instance' of the SMC_FBError is zero:<br/> <img src="./attachment/HomeError.png" width="100%"/></p> <p>All of my motion FB's are on the EtherCat task so that is not the issue. If I replace the axis object with a virtual axis (AXIS_REF_VIRTUAL_SM3) MC_Home exits normally with Done (not CommandAborted like with the real axis).</p> <p>What am I doing wrong?</p> <p>Thank you.</p> <p>PS, I cannot use SMC_Home because this axis does not have inputs to change the direction. I am using the 'find reference mark' in the drive.</p></div>