stepgen maxvel too big and SRO problem

  I have a problem with the stepgen: the max velocity is too high. Where and which value do I need to adjust? My steps with the Mesa 7i96 are 10,000 steps for the spindle.

The second problem concerns the MVO rotary encoder. The spindle and the normal feed work, but the rapid-feed encoder does not. Even when I swap the inputs for feed and spindle, it still doesn’t work. It seems to be an issue with the GUI/interface? Where can I start looking to solve this?

 

The "Maxvel is to high" error means that the stepgen cannot physically generate
the  requested step rate with the current steplength and stepspace parameters.

Options are to:

Lower the steps per turn on the spindle drive

Lower the spindle maximum RPM

Lower the values of the step length and step space parameters
(as long as they still meet the drives minimum width specifications)

The maximum RPM will be 60/(steps per turn(step_length+step_space))

So for example at 10000 steps per turn and 5000 ns (.000005 seconds) for step length
and step space, the maximum RPM would be 600...

You must degrease maxvel or you must degrease step timmings.

The second problem concerns the SRO rotary encoder. The spindle and the normal feed work, but the rapid-feed encoder does not. Even when I swap the inputs for feed and spindle, it still doesn’t work. It seems to be an issue with the GUI/interface? Where can I start looking to solve this?

We need more information. Specification encoder? Wiring encoder? What SRO mean?

The encoder works on the spindle and for normal feed rates. However, if I switch the input in the Mesa software to rapid feed rate overlay, the bar does not move with the same encoder as for normal feed rates and the same wiring.

I don't actually need the rapid overlay. If I could operate rapid and normal feed with the same encoder, that would also be OK.

The GUI's don't always "know" that you have changed an override.

Which GUI are you using? And how are you overriding (ie, which HAL pins are the counts going to?)

I tested with gmoccapy and dragon.

The MOV doesn't work. The spindle and the normal feed work with enc3.

# ---Überschreibung von Signalen zum Mesa-Geber - mpg (feed override signals to mesa encoder - mpg)---

net fo-count <= [HMOT](CARD0).7i73.0.0.enc1.count

# Vorschub-Override-Schritte verbinden - MPG (connect feed override increments - MPG)

setp halui.feed-override.direct-value false
setp halui.feed-override.scale .01
setp halui.feed-override.count-enable true
net fo-count => halui.feed-override.counts

# ---max Geschwindigkeit Neufestsetzungs-Signale an Mesa Encoder - mpg (max velocity override signals to mesa encoder - mpg)---

net mvo-count <= [HMOT](CARD0).7i73.0.0.enc3.count

# verbinde max Geschwindigkeit Neufestetzung Inkrement - MPG (connect max velocity override increments - MPG)

setp halui.max-velocity.direct-value false
setp halui.max-velocity.scale 0.666667
setp halui.max-velocity.count-enable true
net mvo-count => halui.max-velocity.counts

I was able to solve the error with maxvel too big by changing the steps per revolution to 2500 in the servo controller. Now I just have to solve the problem with the MVO.

Note
For GMOCCAPY 3 some HAL pin names have changed when new controls have been implemented. Max velocity does not exist any more, it was replaced by rapid override due to the demand of many users.

net rro-count <= [HMOT](CARD0).7i73.0.0.enc3.count

# verbinde max Geschwindigkeit Neufestetzung Inkrement - MPG (connect max velocity override increments - MPG)

setp halui.rapid.rapid-override.direct-value false
setp halui.rapid.rapid-override.scale 0.666667
setp halui.rapid.rapid-override.count-enable true
net rro-count => halui.rapid.rapid-override.counts

Is that correct? Does PNCCONF need to be adjusted? Does MESA CT use the new values?