Advanced Search

I'm sorry I am not as familiar with iocontrol v2, and missed that. I'm not sure what exactly the lube related pins do other than exactly what it says in the man page. As far as I know the pins will only be true if the machine is out of estop and the halui pin "halui.lube.on" is true. So it might be a rather toothless addition that doesn't really do much of anything, and you will still need to create appropriate logic to control it. I could be completely wrong, but I'm not seeing documentation to say otherwise.

I'm not sure I understand what your trying to do with the fipflop component. I don't think it is necessary. (A hal input pin remembers the value it is given with a setp if it isn't connected to a signal and hal commands like setp in the hal file are only executed once when the hal file is loaded at start up.)

I would probably use a couple of custom M-codes to enable/disable the 2nd probe. In your hal file add a line to setp the value of the and2.0.in0. and remove all other hal file references to that pin. Then in the two M-code files setp the value of and2.0.in0 to true or false to enable and disable the input.


Then to create an M101 M-code create a file containing the following, called M101 save it to your config dir and save as an executable file.
Then you can make another one to disable the probe called M102

Thanks for the overview.

I don't think that will work for me, as my encoder doesn't have a Z pulse. Just an A, B and R one. The motor itself has an origin switch that gives a digital output. The idea is to have that serve as the homing point, probably by using Homing Method 4 for Homing Mode (an operation mode in EtherCAT). I'm going to look into whether or not something like this has been discussed here, but for now it seems I'm the only one with this sort of setup, I think.

You may be able to reduce the overshoot by using
the PID components maxerror pin. This should allow
higher P (and I) terms.

Also anything in the VFD setup that slows response
will limit the highest stable P term.

Hello guys,

i just started taking heavier cuts on my machine (Deckel FP2A) and i noticed that the rpm drops down, sometimes up to 150 rpm. The machine uses a 2.2 kW motor with a huanyang vfd. Between the motor and spindle is a belt drive as well as an gearbox (similar to the MAHO machines). Up until now i ran the spindle open loop. But since i added a encoder directly to the spindle i thought i could close the loop and use pid to counteract the rpm drops. I ran a couple of tests today but i was not able to keep the rpm steady under load. With all PID values at 0, except FF0 that was 1 during all the tests, i was already getting a good response (see halscope below). At around P=2 the over and undershoots started. So i tried P=0.5 and ran a test cut in mild steel (cut conditions below, machine should be more than capable for that). At the halscope you could see how to rpm drops and then oscillates. And the end of the cut the rpm came back up to the commanded speed. You can actually hear the rpm drop and accelerate.

I don't know how to continue from here, so i wish to get help from you guys! The pid with all values at 0 gives the best response but also makes it kind of useless. I attached a couple halscope diagrams of different tests below. They are always three: spindle startup, idling and under load. I also tired higher P values just to see if the pid is working. My spindle hal section is pretty much the default pncconf, only added the gearbox and vfd stuff (gear selection etc.). This might as well be a vfd issue, so i included my parameters that i have changed after a factory reset.

Thank you!

Cut conditions:


Huanyang VFD HY04D043B 4kw 380V motor is wired in star config
Parameters:

Good afternoon! I purchased the same servos, and I can't get them to start. I took the configuration files from this theme, substituted my data, but could not launch it. Could you please share working files or tips on how to get these servos up and running?

The latest RTAI Patches are for Kernel 5.4 but the Support for UHD 730 in the i915 Driver has been added in 5.11 (I think).
Any ideas how to get the Driver working in the 5.4 Kernel?

I'm using a Core i3 14100T on an ASUS Q670EI-IM-A Board.

Thanks

I did some research about the uspace and the general information is: uspace is not intended to control real machines, but used for simulation.

This is still true? Because if it is, I cannot use it as the intention is to really control the machine that was previously working.
Thank you

index enable usually refers to the Index output of the encoder, basically it's a single pules indicating the encoder has reached the reset point of it's wheel. IE every 2048 pules in a 2048 encoder you get a index pulse. if so equipped, often referred to as the Z pulse in many encoders.

I have them in stock as well.
mesaus.com/product/7i76eu/

JT

Thanks for the response, Collins.

That thread is more concerned with the spindle orientation with M19, is it not? Or do you mean to imply I can implement both M6 homing + tool changing and M19 orientation with this? Would this work with an incremental sin/cos encoder with an origin switch instead of an absolute encoder?

One of the responses in that thread was a link to a more recent solution to the spindle homing:
forum.linuxcnc.org/10-advanced-configura...nt-component-revised

I suppose it would be best for me to look into that, as it seems people are pleased with it.

I was under the impression the homing should be handled internally by the drive upon being sent the appropriate command by LinuxCNC over EtherCAT. After all, it does have a "Homing Mode." But it seems that is not necessary and I can handle it all through the orient component (or the more recent solution) which calculates the homing through the encoder feedback? Am I understanding this correctly?

Also, what is the index-enable these components refer to? Is that the origin switch of the motor?

Thanks again for the help.

Here linuxcnc.org/docs/html/config/iov2.html
shows pins relevant to lube and tool change
also halui linuxcnc.org/docs/html/man/man1/halui.1.html#Lube
has pins for lube.

How can use these pins ?

Goto the forum section of Installing Linuxcnc.
Click on the sticky for the RPi images.
Read the whole thread. The answers are there.
That's what the purpose of that particular thread is for.

on the surface this appears like it should be correct , but I am not expert with ethercat, far far from it. it appears your checking for the home comparison and setting 0 or 1 based on that result, then issuing a home command if not homed. The next issue obviously will be having linuxcnc call the homing in the driver. Is this to be used as a C axis, if not just have it call the homing function in your postprocessor iirc

forum.linuxcnc.org/10-advanced-configura...7-homing-the-spindle

Ok all. Im stuck and going around and around in circles. So problem: Have two probes for input. Touch-off (pin0) and Probe (Pin2). But I cannot assign 2 pins to the one probe-input. In addition, want to allow for Probe (Pin2) to be rendered inactive when not connected.

Here is the error: probe2-in cannot be found. Comes up on load.

Here is the logic.
ini file has the inputs defined:
INPUT_0_0 = Probe Input
INPUT_INVERT_0_0 = True
INPUT_SLOW_0_0 = False
INPUT_0_1 = E Stop 0
INPUT_INVERT_0_1 = True
INPUT_SLOW_0_1 = False
INPUT_0_2 = Probe Input
INPUT_INVERT_0_2 = True
INPUT_SLOW_0_2 = False

The io.hal file has a set of logic to select the probe input and check the input for active low before it commences. It looks Ok to me. But I have something screwed up as it seems to be that the flipflop cant/wont work as a storage function. So not sure how to get this actioned. Any ideas?

# Inputs
#net probe-input motion.probe-input <= hm2_7i96s.0.inm.00.input-00-not
#net probe-input motion.probe-input <= hm2_7i96s.0.inm.00.input-02-not

# Define probe inputs (Pin 0 and Pin 2)
net probe1-in       hm2_7i96s.0.inm.00.input-00-not      # Tool Touch-off probe (Pin 0)
net probe2-in       hm2_7i96s.0.inm.00.input-02-not      # Edge Finder probe (Pin 2)

# Load logic components
loadrt and2 count=1
loadrt or2 count=1
loadrt flipflop count=1     # Stores Edge Finder connection status

addf and2.0 servo-thread
addf or2.0 servo-thread
addf flipflop.0 servo-thread

# Flip-flop to store the connected state of the Edge Finder (Pin 2)
net probe2-connected  flipflop.0.data <= probe2-in    # Memory for whether Edge Finder is connected
net probe2-connected-state flipflop.0.out             # Store connected state of Edge Finder

# Enable Edge Finder only when connected
net probe2-allowed and2.0.in0 <= probe2-connected-state
net probe2-final and2.0.out  # Final state of Edge Finder   # Allow probe2 (Edge Finder) if connected

# Send final signal to motion.probe-input
net motion-probe or2.0.out => motion.probe-input