- Posts: 143
- Thank you received: 0
Spindle Pulses Lost in System
1 year 9 months ago #320259
by 10K
Replied by 10K on topic Spindle Pulses Lost in System
The counts are all negative, that is they get more negative when the spindle is turning. Same for the RPM. I have an entry in my postgui that flips it:
Code:
setp scale.0.gain 60
setp lowpass.0.gain 0.010000
net spindle-velocity-feedback-rps => lowpass.0.in
net spindle-fb-filtered-rps lowpass.0.out => abs.0.in
net spindle-fb-filtered-abs-rps abs.0.out => scale.0.in
net spindle-fb-filtered-abs-rpm scale.0.out => gmoccapy.spindle_feedback_bar
Please Log in to join the conversation.
1 year 9 months ago #320266
by PCW
Replied by PCW on topic Spindle Pulses Lost in System
That fixes the display, but doesn't allow spindle synchronized motion.
The way to fix this is to set the encoder scale to -180
The way to fix this is to set the encoder scale to -180
Please Log in to join the conversation.
1 year 8 months ago #320327
by 10K
Replied by 10K on topic Spindle Pulses Lost in System
Yes, changing the sign on the scale flips over the following PINs:
(all begin with hm2_7i92.0.encoder.00.)
position
velocity-rpm
velocity
the change has no effect on:
count
rawcounts
As it turned out, I fixed it another way. I had the ESD button connected to the encoder-B DB-25 P11 (14) input. I moved the ESD to my BOB #2 and left no input for encoder-B. This flipped the encoder.00 inputs to all positive and I was able to leave the encoder scale at +180..
Now I can thread again, so problem solved! Thanks for the help!
(all begin with hm2_7i92.0.encoder.00.)
position
velocity-rpm
velocity
the change has no effect on:
count
rawcounts
As it turned out, I fixed it another way. I had the ESD button connected to the encoder-B DB-25 P11 (14) input. I moved the ESD to my BOB #2 and left no input for encoder-B. This flipped the encoder.00 inputs to all positive and I was able to leave the encoder scale at +180..
Now I can thread again, so problem solved! Thanks for the help!
Please Log in to join the conversation.
Time to create page: 0.031 seconds
