Hal help for home to index with stepgen firmware update

Your example hal file shows the wrong index enable being used

I just uploaded the wrong example here. Uploading the Pin file. You may see something wrong.

 

Without the included index, the machine is HOME close to the switch. When the index is on, the machine moves to the Home switch and then returns 26-45mm.

PS. Now I tested the motor index for repeatability and every time in halshou pin stepgen.00.index-enable clears at the same position.  It is not a problem in the driver and reading the signal.  Maybe something in the ini file is missing or wrong?  When the index is turned on, the Axis returns at the time of starting the HOME procedure And the speed is high

Can you post your current hal/ini files?

Also you can verify index operation by

1. Watching the stepgen feedback position and stepgen index enable in halshow
2. "sets" the stepgen index enable signal
3. Generate an index event

The expected result is that on index event, the stepgen index enable will go false
and the stepgen feedback position should be zeroed.
 

The files are the same ... just index is connected to the correct pin
hm2_7i98.0.stepgen.00.index-enable
I am attaching photos from the test.  The signals are the last two.  It works fine there ...

 

 
 

Can you post your current hal/ini files?

The original one had encoder 0 on an analog axis
so makes no sense to use stepgen index enable 00




 

I think I found the error. When I have duplicated the X axis to make the Z axis. I forgot to change a few Z-specific names . 
Here are the wrong lines in Z configuration :
net x-index-enable joint.1.index-enable <=> hm2_7i98.0.encoder.00.index-enable


 

 


Thanks again for your help!

I have a question . When the index pulse is read. Can I set a fast speed for HOME_SEARCH_VEL and low speed for HOME_LATCH_VEL The pulse from the encoder is read at this speed HOME_LATCH_VEL ?

Just the encoder is with lag

AFAIK the initial search for the home switch is done at HOME_SEARCH_VELOCITY
and any further moves (until index is detected in your case) are done at HOME_LATCH_VEL
and then the final move is done at HOME_FINAL_VEL.

Yes, it works fine now. Stupid mistake. . . I did not expect the solution to the problem to be in the other axis.