read per axis status / run-stop don't work at low speed

[kazakleyak]

Hello,

This is my fisrt motion program. I don't understand why the "read per axis status" don't send me the correct status for "run/stop" (only this status) when I run a low speed. The other status are all right. Impultions are still generated (In realyty motor run...)

I put a simple example to illustrate. Perhaps is it a wrong configuration in MAX but this seems unlikely. I can't join my Max config because ".nce" are not accepted in attached files.

Thank you wery much

[AndreasStark]

 Do you see run/stop status in when the motor runs faster?

[TroubleTheShoot]

Hi there,

are you running your motor in closed loop mode? Can you make sure that your encoder delivers proper signals?

Look at the following document to see a description of the run status:

http://digital.ni.com/public.nsf/allkb/CFA7691B7E7508DD862567D3006F642D?OpenDocument

Hope this helps.

Best regards,

David

[A_Person]

I realize this is an old post but wanted to post the solution in case others run across it.  The reason the indicator is not working at low speeds is because it operates on a threshold.  The default setting is for it to display false when running under 4000 steps or counts per second.  Refer to KnowledgeBase 4XHD6DZY: Why does my Run/Stop bit not appear active while my motor is running?