Advanced Search

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.

There is a fixed but parametric G-code file as part of the config that does the feeding / multiple passes.

You should definitely look at that file to see what it does, and also what it assumes. The system assumes that the tip of the cutter is touched-off to the workpiece radius (ie Z = 0 is on the work axis)
Also note that the axis assignment is a little unusual, with hobbing radius as Z and work axis along X.

"shift" is a profile shift, simply a radial offset of the hob relative to the workpiece centreline.

Hi,
thanks for the help.
I've been messing around with the project but can't seem to get it to work.
I compiled ethercat_twincat and ran it but it's not reading any ports from my ethercat device. There are no input/outputs. Is there somthing else i need to configure?
My device is in PREOP mode and erroring because of:
"The current and the projected module list do not match. The data
exchange is still in progress." or
"The gateway is still in INIT status, the module list has not yet been
written to the gateway."

I should be actively writing something to the gateway to configure it i guess...

I would suggest that you connect iocontrol.0.tool-prepare to the turret-unclamp output pin, and then connect carousel.0.enable to the turret-unclamp-ready pin.

That way a tool change request will immediately unclamp the turret, and the carousel component will only start up once the turret is actually unclamped.

Probably, some experimentation may be needed, especially regarding how the re-clamping happens.

For the benefit of anyone else using the L510 (or the RS-branded RS510) VFD this component seems to work:
github.com/gitcoffey/l510_vfd
after making this change
github.com/gitcoffey/l510_vfd/pull/1
Install with

I assume that you are using the tool-number in HAL rather than pocket-number to bypass the tool/pocket swapping inherent to a random TC?

Is it possible that you could save a copy of the tool.tbl file before and after the problem and attach the two files here? That might help work out what is going on.

Check in hawshow if there is an enable pin for this window glade ...

If you have a different theme color, you can fix it by looking at the last comment on this post.

forum.linuxcnc.org/gmoccapy/45856-spindl...capy?start=40#313268