MB_InitTouchProbe error in Motion 2.6

[bschmidt]

Hello,

Since updating to 2.6 software and apps, MB_InitTouchProbe is not working. I have all the parameters for Probe 1 mapped in the Axis Profile. I am doing a basic configuration, enabling positive edge capture of Probe 1. But always I get the same generic error. The same configuration was working fine with 2.4. Please see attached screenshots, system report, and drive parameters.

Best regards,

Brian

[bschmidt]

After further testing, I see that the Execute of MB_InitTouchProbe and Enable of MB_TouchProbeContinuousType01 must occur in the PLC Open state of STANDSTILL. Otherwise an error will be generated if you try to do this in any other state e.g. DISABLED, CONTINUOUS_MOTION, SYNCHRONIZED_MOTION, etc. From this point the blocks will be working when the PLC Open state is changed. 

This was not a requirement in 2.4. It seems odd to require this, since TouchProbe is only a measuring function (not a Motion FB). I did try this in STANDSTILL in earlier testing of 2.6 but still got the error. I must have had something else wrong in that case. 

[bschmidt]

Hello,

Following up on this post. Why does the axis have to be in Standstill for these FB's to Execute without error? This seems to be an unnecessary constraint which adversely affects the customer's working code from previous versions of ctrlX PLC (or MLC/IndraWorks). Could this please be changed to how it was working previously?

Thanks,

Brian

[Jochen_Mueller · Accepted solution]

Hello Brian

we already give this feedback to the development department. It will be fixed in version 3 (next RM24.07).

Regards

Jochen

[bschmidt]

Hello Jochen,

Great, thank you for the update.

Regards,

Brian