Arduino Leonardo and linears encoders.

casetero wrote:

So i cant make a Closed loop using the actual pulse count command i have now, can i?

You probably can, but it isn't the way I would choose to do it.

Sorry but i havent fully understand you, when you say an analogue velocity request, are you talking about the velocity request of the linear encoders? Because the linear encoders are digital too. Sorry but i don´t understand why i have to do the pulse train equivalent to an analogue velocity request.

In a typical servo system LinuxCNC uses a PID module to compare where an axis is with where it should be. It then outputs a command signal to move the axis, with the magnitude of the signal related to how fast the axis ought to move. This signal is typically an analogue voltage.
With your current system the situation is that a stepgen is told where the axis should be, it compares that position to the current position, and outputs the correct number of pulses to move the motor to that new position.
One way of combining the two systems would be to use a PID controller (which is comparing command position to linear-scale position) to add an offset to the command value before it is passed to the stepgen. But I am not sure that would work very well.
The idea of using the velocity-mode stepgen is that it converts your system into a much more conventional-looking servo system. The PID outputs a velocity command, then the velocity command is passed to the drive as a pulse train. Instead of how _many_ pulses being used to control the servo position in the drive, it is now how _fast_ the position command changes.

Searching on the web i found that TTL signals were composed by 3 different phases, in this pdf says that the 216 t uses just two.

You don't need index. That is only useful on rotary encoders.

casetero wrote:

Ok, so i understand that i can manage my servos not with a count of pulses (position), yes with a density of pulses (velocity). And this will produce a similar analogue voltage control, isn´t it?
And the same for the inputs from the linear scales, i will have to use this method of density pulses too, won´t i?

Not quite.
The linear encoders will provide position information in absolute mm.
The output to the drives would be pulse rate, ie requested velocity.
You nearly always have an "offset" between the controlled parameter and the input in a PID loop. The classic example is filling a tank, where water level is the controlled parameter, and water flow rate is what is adjusted to achieve that.

If you think it will work better with this method i will do it like this. I suposse to make all this stuff i have to program the hal file.

Yes, this is going to have to be a manual config, though you should probably start with a sample servo config (or a stepconf config) and edit them.

There are lots of ways that you could try this, luckily it's just software and it is "free" to experiment with different control modes.

Try reading the docs here: www.linuxcnc.org/docs/html/hal/intro.html
And the others in the HAL section here: www.linuxcnc.org/docs/html/

But be aware that these docs are rather about "how" to set up a HAL, not "what" you need.

Your control loop will be:

PID command = axis.N.motor-position-cmd
PID feedback = encoder.N.position (from the scales)
PID output => stepgen.N.command (velocity mode stepgen)

Then you have the fun of adjusting PGain, Igain, Dgain etc.

if you start with a servo config then the iNI file will be set up with Pgain and friends, and that means you can use the Machine=>Calibration utility.

casetero wrote:

Hidcomp.0.PIN1.raw are type s32 and with this pin i can manage many buttons, if i hit first button it shows value 6, if i press second button it shows value 12....

That seems a bit painful. is there any underlying bit-pattern logic?
it may be that the pendant is trying to produce keyboard scan codes. :-/

I think the way to do this might be to convert the S32 to a float using
www.linuxcnc.org/docs/html/man/man9/conv_s32_float.9.html
Then set up a set of comparators, then use their "equals" outputs as the bit-values to link to halui etc:
www.linuxcnc.org/docs/html/man/man9/comp.9.html

ie
...
net val_as_float conv_s32_float.0.out => comp.0.in comp.1.in comp.2.in comp.3.in
...
with a comp for each button.

casetero wrote:

Ok, hidcomp creates 4 diferent PINs, and for each PIN 3 diferent type of, and one of them is float. I put you the s32 one because i thought it was the easyer to manage.

Normally it would be, but the "comp" HAL component works with float values.
[/quote]So with the command you have posted every time i push a button, it keep the float value in all comps?[/quote]Sorry, I am not sure what you mean by "keep" in that sentence.
Can you make a table of values for all pins and all buttons? Perhaps I can figure out the logic.

I had a look a the website, and it is a bit too expensive for me to buy one to experiment with.
Interestingly the "support" section of the salecnc website offers a support file called "Shuttlepro.rar" which might indicate that the internals are from
www.thomann.de/gb/contour_av_solutions_s...W_g7UCFYlb3god1y8AqQ
In which case we have:
linuxcnc.org/docs/html/man/man1/shuttlexpress.1.html

What name does our MPG give itself in HID?