Advanced Search

I got the Anilam controller working. It's antiquated, at least as far as I'm concerned; sneaker net file transfer via very slow USB-floppy emulator. I'll run with it for a while before spending any more money. Thanks!

Welcome to the dark side!

So I made a rebuilt config, and can see what went wrong.
The pins were setup correctly. but maybe looks odd, because I have had to use encoder inputs as my switches are 5volt devices.
# --- MIN-X ---
net min-x <= hm2_7i92.0.encoder.03.input-a

# --- MAX-X ---
net max-x <= hm2_7i92.0.encoder.03.input-b

# --- MIN-Y ---   (The index pulses are inverted, so the NOT function reverses that.)
net my-input-signal-1 <= not.0.in hm2_7i92.0.encoder.03.input-index
net min-y => not.0.out

# --- MAX-Y ---
net max-y <= hm2_7i92.0.encoder.04.input-a

# --- MIN-Z --- THIS IS SPINDLE EXTENDED ie DOWN limit
net min-z <= hm2_7i92.0.encoder.04.input-b

# --- MAX-Z --- THIS IS SPINDLE FULLY HOME ie UP limit
net my-input-signal-2 <= not.1.in hm2_7i92.0.encoder.04.input-index
net max-z => not.1.out

Mess up was that all the axes, had a similar mistake. Had only min terms in all three places
Putting the max terms as follows has fixed it.

net min-x => joint.0.home-sw-in
net min-x => joint.0.neg-lim-sw-in
net max-x => joint.0.pos-lim-sw-in

X and Y home on the min end, so need to be told, and also that there is a switch at the other end. (Had min there too instead of max.)

Z homes at the max end, which is fully UP
net min-z => joint.2.neg-lim-sw-in
net max-z => joint.2.pos-lim-sw-in
net max-z => joint.2.home-sw-in

Homing all good now, Thanks

Context:
I want to use Linuxcnc for a Ultra-Precision machine.
For that i need Linuxcnc to tell my drives (via Ethercat) the waypoints with high resolution.
I can get 0.5 nanometer resolution out of the Ethercat bus with the 32bit Integer format at the travels that i need. Which is sufficient.

Now as for my question:
From what i gather the path planner and everything works in single-precision floats.
Doing the math on that at 10mm and 500mm positions tells me the resolution between bits of the float number is not enough.
10mm/2^24=0.59nm
500mm/2^24 = 29.80nm

I dont want to waste that much precision in my control for no reason (plus having to convert to the scaled integer value).

Is there a way to change that to double precision floats (64bit) without having to rewrite the whole control?
Also feel free to tell me that my math is wrong^^

Leo