Advanced Search

It's a tool to record positions to a file for later use.

JT

Well, I will need to orientate it for the changer. I was thinking that I can just run it velocity mode and use the encoder to orientate it. I did see something about a homing feature. However I will need to double check that.

HOME_SEARCH_VEL = -0.083333

That's 0.083 inches per second or ~ 5 Inches Per Minute (IPM)
= Really slow

the MAX_ACCELERATION and MAX_VELOCITY is different on my machine right now. (this is before experimenting)

What you are seeing is probably a limit to the speed with which steps can be generated. Once the system hits the maximum step-rate the system will realise that the machine is out of position and trigger a following-error.

What is your step length and step space? Add them together, and divide into one second. That's the maximum number of steps per second that the system can generate. You are probably hitting either this limit, or the limit of the base-thread speed, as the system can generate at most one step per base period. (If you don't see a "reset" function in your HAL then it is one step every two base thread cycles.

If the driver can handle it you can try reducing step length, or the base thread period. But you might find that the only answer is to change the microstep ratio.

Your lathe could be configured as xzuw, which would probably make sense, though I don't think that canned cycles are supported in the uw plane, nor is radius/diameter mode, as far as I can recall.

Note that the mapping between the "joints" and the "axes" is governed by the kinematics module and and configuration. It may be that something is a bit wrong there in your configuration.

If you attach your HAL and INI file we will have more to go on.

Does adding the option here work?

github.com/LinuxCNC/linuxcnc/blob/master/debian/rules.in#L47

Hallo spicer,

hab in der axis_mm.ini bei Achse_0 und Achse_1 auf 0 umgestellt. Bei Achse_2 war default eine 0 schon drinnen.
Ich kann obwohl die Fehlermeldung noch ersheint eine Referenzfahrt durchführen. Das einzige was mir nun aufgefallen ist, das wenn ich mein Programm ablaufen lasse und es irgendwo stoppe wird bei einer erneuten  Referenzfahrt dieser Startpunkt als Referenzfahrt genommen wird. Sollte eigentlich so wie in der axis.ngc in der unteren Ecke liegen. Wo finde ich eigendlich das Startprogramm axis.ngc?

MfG.

 

Dear Andy,
Thank you for your reply.

I would like to install central lubrication on the machine.
FUW400-5A-75E.gpio.25.in-not: this bit is connection oil pressure switch.
FUW400-5A-75E.gpio.26.in-not: this bit is connection oil level switch.

I would like to solve this:
If there is not enough oil level, then there should be no lubrication and write it on the screen.
If there is enough oil level, then lubrication can be set periodically, for a given time.
If lubrication has started, then watch whether the pressure switch switches during a given time. If it does not switch, then write it on the screen.

I don't have any relevant experience but... Does the current driver offer spindle orientation for tool changes, and do you need that?
If so, does the now motor support that (I would be surprised if it doesn't, it seems to be a servo drive)

Here's an example of what I found on the back of the Emco selector 'switch' knob.  There was a spring-loaded ball inside the metal knob that engaged the ring divots.

The slot in the ring engaged with the pot anti-rotation tab and the pot clamping nut kept it in place.  Knob with ball was just pressed on top - leading to a not-so-amusing self-disassembly when the knob was removed.

I like this idea so much I may actually do it on my SRO, FRO, and JRO pots, but I think it'd require a pot with a fairly long mounting thread (or a very thin mounting surface).

Yes it can be difficult to sort everything out but you've made a good starting point of labeling what you want to happen from there it's just a matter of writing the code to match. M6 T5 G43 H5 is calling tools 5 and the z offset from the tool table for tool 5.

You could cancel that with a g49, but the issue you're having is you're trying to measure something from the previously loaded tool and if that's getting stored in the pool table that's probably not going to be good for you.

You may want to take the approach to just reset the z work offset at the tool change and measure the new tool from the known tool setter height and have an entry for the material height off of the table which would be your known working location. With this every time you made a tool touch off with a new tool you'd have something easily calculable.

Your first block of code could be written on a single line,
But I think that there might be a problem with your logic.

What does FUW400-5A-75E.gpio.26 actually indicate? It can't mean Low, OK _and_ warn.

Should these use GPIO 26, 27 and 28 maybe?

If not, and you are deriving different meanings from the GPIO with different logic, then you can only have one signal that represents the value of FUW400-5A-75E.gpio.26-not. It's a bit inconsistent insome ways, as you are allowed to to treat in-not and in as separate inputs, despite the fact that they are the same data.

You can not bother with not.0
(possibly, I don't know how your system is set up)

kcjengr.github.io/probe_basic/machine_config.html

Use this for a starting point, then come back with more narrowed down questions and errors, then we can assist better.

Make backups of your working config folder, that's already important even if you were staying with gmoccapy.

Perhaps that action button could be replaced with a mdi button and add in the mdi code for homing both y's?

I'm not familiar enough with dual drive axis too know how the homing would need to be called for that scenario though.