Advanced Search

theslawek wrote:

BINGO, adding the halui line did the trick. Thank you PCW and spumco, you guys are amazing (and lighting fast responders).
 

Thanks for reporting back, and glad to hear it's sorted out.

BTW, the "=>" and "<=" in the line are just characters to help the user visualize the pin to signal connection.  They are not required, and are ignored by LCNC.  I personally find single-line HAL entries nearly impossible to read, but breaking them up in to multiple lines does make for a much longer HAL file.

For example, the single line:
net machine-is-on hm2_7i76e.0.stepgen.04.enable halui.machine.is-on

is the same to LCNC as:
net machine-is-on  <= halui.machine.is-on
net machine-is-on  => hm2_7i76e.0.stepgen.04.enable

It's worth a try, but...

Did you actually disable AMT?

Still don't know where base.tmax" and "servo.tmax" come from.
These are suspicious as they do not exist in a standard LinuxCNC installation.

if I change the VFD to manual control the spindle works fine. Testing the 10V spindle out seems to be fine for the 1 second then drops to 0v. The machine almost always goes to "Machine Off".

The question then would be why you get to the machine off state. (this will certainly turn off the spindle)

If you start LinuxCNC from the command line, are any errors displayed?
 

Not tested, but try:
-home the machine at MACHINE 0 limits with G53
-jog the machine to PART 0 and touch off with G54
If you have the machine limits set correctly in the ini file, if any move would exceed the machine limits, LinuxCNC will show a warning asking you if you want to continue, do not continue if this happens.

I'm working on carving a piece that's really a little too big for my mill.  It barely fits if I rotate it 45 degrees, and carve it that way.  But the size and rotation make it hard to be sure no movement will exceed the machine limits, and sure enough, about halfway through a carving (a draft practice run, happily), I tripped a limit switch.

(I should clarify that my machine is "homeless".  "home" is always relative to the piece, so there's no way for the interpreter to know in advance that I'll be exceeding a limit.)

Are the program's extents (min/max X, min/max Y) available in variables that could be used by a canned subroutine?  I did a quick skim of the source, but didn't find anything obvious.

I connected the 7i77 to p1 and the 7i78 to p2, i assume this is the correct order.
I've tried to modify the hal so that the z-Axis is the stepper connected to the first interface of the 7i78. The encoder for the z-axis is connected to the 7i77. Is this more or less done correctly? (hal is attached).
Since the 7i78 has no enable signals for the steppers, is it possible to use the enable pin from the spindle, since i am not using this? and how do i need to mod the hal?
Thanks! 

Vielen Dank für die Rückmeldung
Welche Version hast du? 8gb?

Hallo PCW, 
ich habe noch einige andere Einstellungen versucht aber ohne Erfolg.
Eigentlich ist das Hobby fräsen und nicht Einstellungen in Linux CNC zu testen.
Deshalb habe ich überlegt einen Raspberry Pi 5 8gb zu kaufen. Jederzeit verfügbar, ein fertiges Image, kein raten / testen, passt bequem in den Schaltschrank. 

Hältst du das für sinnvoll?

Grüße Erwin 
 

Business Closing
Mesa – Lansing Machine Services Inc. All were purchased new from Mesa or CnC Machines, LLC

Yes it works perfectly. I would have to dig out the fix — it was suggested on the forum and the Pi5 setup has been flawless ever since.

Hello Have you been able to fix the problem in the meantime?I am also thinking about using a pi 5 + 7i96s as I now have a second PC which is apparently not suitable for Linux CNC. If you were able to fix the problem, what was the cause and are you satisfied so far?

Regards Erwin 

Hi,

I was just able to compile the scurve planner with the original linuxcnc Makefile system.

repository
Use the ./install script to install linuxcnc. It first installs the libscurve & libclothoid3d locally.

Then it just runs the axis_scurve_mm.ini config using scurve.

Hmm, interesting development.

Now a dev can make modifications to their needs, and merge it, if they want to.

I don't understand the problem here, really.

But with 1600 pulses per rev and a 3:1 belt ratio, the scale is just 1600/3 = 533.3333333333333333333333

If you see a creep, it could be the missing threes.

But, LinuxCNC expects pulser per _degree_ for a rotary axis, so you might actually want 1.481481481481481

Actually, hal_gpio might "just work" in this case.

Try this command and see if it reports the pins:If you get "command not known" then
If the pins are reported, then:
linuxcnc.org/docs/stable/html/drivers/hal_gpio.html

Note that unless the index pulse is from the spindle shaft, or the gear ratio is exactly 1:1, you can't peck-tap with the encoder on the motor shaft. This probably isn't a problem in most cases, but is worth being aware of.