eccentric turning

hi me again...

net spindle-position encoder.0.position => xo.angle gives me 1 count for 1 rev.
ok this works. but i struggle with:

net E:active <= motion.eoffset-activenet E:active => xo.active

the motion.eoffset-active shows everytime false.and i dont know what i must do.i need help...can someone please help... i dont understand it.

i upload my hals and inis.... what do i wrong?!can someone bring me to the right way?!

thanks

Hello, I tried on my side too, with a port // configuration (identical to yours, in fact) I would like to help you, but I am less advanced than you on this configuration (contrary to you, I wish to keep the C axis) I am happy to not be alone on this subject, thank you !

hi and thanks.

i think the bigest problem is to understand all the nets.
what must done to get motion.eoffest-active into true.

and scale the revs to deg. (*360?)
and what is when its 361 degree
. then it must 1 degree...


i hope andy can help.

do you use it on a lathe or a mill?
c axis as spindle?
or spindle as c axis?
or what?

i play on my table with a abz encoder resolution 500 (2000). wired to my parallelport.
the x and z axis are setup but not connected.

if i get movement on the x axis from the encoder i do the next step...

i hope someone help.. or can upload his working inis / hals.


could you upload yours?

thanks

hitchhiker wrote:

i find out that my abz encoder had no working z signal... i done all on my desk... without the lathe.

 

Are you sure about that? The index pulse is generally very short and might be impossible to see if using the HAL probes (and will often not even show up in Halscope)

The way to test it is to set spindle.0.index-enable to 1, then rotate the spindle, and see if it resets to zero at the  index position. 

Use "sets" on the signal that is associated with your encoder index. In your case it looks like 

Will do it. 

For testing, I suggest opening an interactive HAL session. Start LinuxCNC and then open a terminal.

Will start an interactive HAL session ("exit to finish")

Then you can issue commands such as "show pin" to get a list of all the pins and their states (or "show pin *enable*" to see all the enable pins)

If the oeffset enable pin is unconnected then you can set it true with "setp" but if it is connected to a signal then you would need to use "sets" on the signal instead.

Other helpful things to type:
loadusr halmeter (opens a halmeter, repeat the command for more halmeters)
loadusr halscope (open the halscope)
delsig {signal_name} (deletes a signal, and unlinks the pins associates with that signal)

index works... but it reset not the count...