Motion Control and Motor Drives

cancel
Showing results for 
Search instead for 
Did you mean: 

SoftMotion timeout minimum value is 1 sec?

Read Motion I/O: Axis Limit Active takes too long.

Got invalid value error when set Axis:Timeout to 0.5 sec, no error for 1 sec.

Not documented.

 

 

George Zou
0 Kudos
Message 1 of 10
(2,788 Views)

Hello Zou!

 

Could you attach a screenshot of that invalid error message you got?

 

0 Kudos
Message 2 of 10
(2,754 Views)

image.png

George Zou
0 Kudos
Message 3 of 10
(2,751 Views)

1 sec is too long.

 

George Zou
0 Kudos
Message 4 of 10
(2,739 Views)

It looks like you are using Ethernet Steppers with SoftMotion (SMD-761x/762x or ISM-741x) which behave a bit differently than other axis types due to the non-deterministic behavior of their Ethernet connection. The minimum timeout for these devices is 1 second due to the Ethernet communication.

 

However, the timeout should only happen if the device is not accessible on the network or the network traffic is so high the communication does not complete in time. If the drive responds, the typical communication delay is ~100ms, so the read should complete much faster if the device is connected.

0 Kudos
Message 5 of 10
(2,738 Views)

Thanks for reply.

The problem is that when something went wrong, it locks up my program for 1 sec.

That's no good.  Could cause catastrophe, such collide with UUT(metal) and demedge the camera/lens.

 

George Zou
0 Kudos
Message 6 of 10
(2,735 Views)

George:

 

Any option to add a limit or photo interrupter switch in the proximity of the lens and wire that to a drive disable input?

Then when the UUT approaches the lens the motor loses power.

 

-AK2DM

~~~~~~~~~~~~~~~~~~~~~~~~~~
"It’s the questions that drive us.”
~~~~~~~~~~~~~~~~~~~~~~~~~~
0 Kudos
Message 7 of 10
(2,728 Views)

I asked our HW design engineer for a limit switch, but did got what I want.

Already have 4 limit switch and 8 collision sensor.

Still rely on software and human intervention to avoid collision.

 

George Zou
0 Kudos
Message 8 of 10
(2,724 Views)

The value you have specified for a software limit position is invalid. The forward software limit position must be greater than the reverse software limit position. You may need to change the order in which you set software limit position values.

Tolerance values must be greater than zero.

All onboard program time slices cannot add up to be greater than 20 ms.


@zou wrote:

I asked our HW design engineer for a limit switch, but did got what I want.

Already have 4 limit switch and 8 collision sensor.

Still rely on software and human intervention to avoid collision.

 


 

0 Kudos
Message 9 of 10
(2,692 Views)

Thanks for reply.

I am not using software limit.  Because it's hard to estimate the value.  It's highly depend on the size of UUT, which varies from 1" to 10" in one direction and up to a few hundreds inch on the other.

 

George Zou
0 Kudos
Message 10 of 10
(2,682 Views)