Advanced Search

Fwiw my calibration routine was inspired by github.com/hausen8/EasyProbe

You'll probably need to complete the missing Z calibration, however the X & Y are completed and functional. Have a look. And let us know how you're doing!

I understand your issue, delay after triggering. Although not a fix (all systems has some sort of delays/accel/decel/ect), the workaround is to use a probe calibration routine. Easier to offset those cal values from the measurement than to real-time the system (imho).

Delay or not, I spec within 5um using cal/offsets.

Hello members,
has anyone gotten the AX5000 drives working correctly with Linuxcnc?

Thinking of a new machine retrofit and I think these would work with old mitsubishi motors.

Kind regards,
Jan

Maybe I am not understanding the question, but after triggering the probe
the joint must obey the ini file set acceleration bounds when coming to a stop
and reversing. This could easily be many mS.
 

Its possible but a bit awkward as it requires +10 and -10V power supplies
Is there a separate spindle enable input? This would be necessary as
the power up state would be with the output at -10V.

It might be easier to use an isolated 10V/12V supply so you get a 0-+10V output
and reverse the output with a DPDT relay.
 

I have a vfd that is controlled by +/-10V signal without a fwd or rev pin. My question is if it still works with the 7i96s because in my understaning it support negative voltage but i needs a fwd and rev pin. so if i use +/-10V then 0V would be 50% max speed and -10V would be 0rpm. Am i right or is it possible so -10V i max rpm ccw and 10v is max rpm cw. 

Update:

Slowing it down worked pretty ok, it was still skipping enough to make a fingernail-width ledge on the skipping axis. I thought that maybe I was getting some interference, and turns out I had forgotten to connect some shield wires to ground. I connected them as close as I could to the signal wires, and that helped immensely. I can still feel a skip every once in a while, and on longer (>15 cm) moves it still has a slight ledge or "lip" from where it is not travelling to where it should on each layer - but it seems to be good enough. If there's any ideas to get rid of that skipping once and for all, please let me know. Note that it does not seem to skip when it's not running gcode. I can jog at the same speed with the spindle on and putting ~15 lbs of force against it and it travels right to the end of each axis and back perfectly.

For steplen, stepspace, dirhold and dirsetup values, I upped those to 30000 each just to be safe with not a lot of improvement. Should they be higher? These are pretty old drivers.

Switched back to the first computer (see comment above) and I'm still getting rtapi realtime delay errors (was not getting these errors when it was connected to the mill computer with a base thread of 21000). My max jitter from the latency test was about 25000, but that value did not work, and neither does 35000 where it currently is set at. Maybe I'll run the latency test for an hour or so and see what that gets me.

Thank you! Now it works! Does the init move and moves the machine. I even managed to get PID so that ferror is less than 0,03 mm up to 17 m/min. There is some noise/vibration but I think that is manageable issue

Thanks for that link, a lot to absorb...
M

Hello everyone,

First post here so forgive me if this is the wrong sub-forum to post.

I'm trying to build a simple 3D touch probe (the "6 balls/3 pins" kind). Probing seems to work but it's currently not very accurate (calculated pretravel variation of ~70um). I'm using LinuxCNC 2.9.2 with Mesa 7i92+7i76 on an i3-2100. Probe Basic as GUI.

While looking at my oscilloscope trace of the trigger signal, I was wondering how fast I should expect the movement to stop once motion.probe-input is triggered. Is it normal to expect a 5-10+ ms delay or there is something wrong with my setup? What I'm seeing is that even though the probe triggers immediately after a light touch to the object, the probe switch opens after some time (as if movement towards the target of G38.2 continues). Is this behavior normal?

Even if there is a significant delay, should I expect the value reported in #5061/#5062/etc. to be the exact position when motion.probe-input has been triggered?

Looking at the code (github.com/LinuxCNC/linuxcnc/blob/master...otion/control.c#L693) the position is saved immediately upon triggering and tpAbort is called (tp == trajectory planner?). Assuming that this code is called from the 25us thread, it seems strange to see the probe switch open after 10ms.

Attached is a capture from the oscilloscope. Channel 1 is the voltage at the probe (probe is the lower leg of a resistive divider) and Channel 2 is the trigger signal.

Thanks in advance.

 
Hi all,

After updating my system from 2.7 to 2.9 I am experiencing a lag when changing directions with my MPG wheel. It is like there is a short period of time (maybe 1/4 second) after changing direction (e.g. +X to -X) when linuxcnc is ignoring the MPG pulses. Otherwise, everything seems to be working fine as it did before the update. Does anyone know if 2.9 has any settings that might cause (or fix) this?

The HAL file is attached. I'm following up with the pendant manufacturer as well, but it looks like they just made changes for the joint/axis separation in 2.8.

updated version LinuxCNC 2.9.3  Debian 12 Bookworm PREEMPT-RT ISO  
Vista cnc M1 USB pendant 
Atom 525MW motherboard
Mesanet 5i25 PCI board--using its parallel port

Thanks,

Rob
 

Yeah, the watchdog they have in Syncthing seems to loop more often than every couple of minutes. I also almost just wrote a simple watch script in python to monitor the folder and pull any changes. Of course pushing is always more ressources economical. I just assumed the mechanism they implemented in Syncthing would be more efficient than any of my poor man's solutions.

Any idea where I can suggest to Probebasic to implement a REFRESH button?

Yes, it's set for 7.5 A full scale
I would set it for 30 A full scale

with

setp xxxx.xxxx.nvmaxcurrent 3000

in the hal file

(this will only take effect after a 8I20 low voltage power cycle)

(pretty sure this will work on a 8I20 Otherwise it will need setsserial)

What are the nameplate ratings of the motor? (voltage and peak amps)
 

You might want to look at this.
www.ametherm.com/inrush-current/transformer-inrush-current.html

-