Advanced Search

I re-read your initial message here what got out of it: The ELMO CLA6/200CD DC servo drive burnt out. You purchased Fuji alpha smart 5 AC servo and your having problem making it work with Arteco SU310 PLC.  Your servo motor is a Power Tetra 85 BLDC type.  A search for Fuji Alpha smart 5AC reveals that it’s a 3 phase AC servo drive thus compatibility problem. Possible solutions in your case: from best to worst”

• Find used Elmo drive on eBay
• Repair the Elmo drive
• Find BLDC drive that is compatible with your motor and can be adapted to work with the Artco PLC (your wiring diagram, Google and eBay are your friends in this case)
• Keep Fuji drive replace the servo motor with an ac 3 phase motor (same power as the existing motor, same line voltage same as fuji drive and has built in encoder that is compatible with fuji drive). You will also need a new control system such as Arduino or Linuxcnc but you will also need to hardwire it to Citizen CM2-PC805-0.

yes should have ethercat repos set up so follow the sticky

In Sheetcam, edit the post processor and remove materials handling code from the On-pen-down method.  (I might not have the name right, its been a while...)

Hi,
I was using a screen connected to the display port of the RPI, and through this port there is no image.
I used an HDMI screen and it gives an image and the RPI starts up fine, although the behavior of the LEDs is the same.
I will continue testing.

PCW wrote:

I am showing my age here by suggesting rc.local as it no longer is executed by default,

I used it till last year,so i am fully aware of it, but it is easy enough to make it work on Linux Mint.
-
I would stick to editing the networks file since most go that route, so all in one place.

I am showing my age here by suggesting rc.local as it no longer is executed by default,
a better way is probably to setup systemd to launch a script at startup  (if you don't want to use
the interfaces file method)

I will take a look at how this is best done.

I wonder if the LinuxCNC startup script (or a "linuxcnc-extra-setup" script launched by
the LinuxCNC startup script) would be another reasonable place for this.

PCW wrote:

There are two ways to make the change permanent

1. Setup the Ethernet connection in the interfaces file
(and remove the setup created by the network manager GUI)
Typical interface content would be something like:

# interfaces(5) file used by ifup(8) and ifdown(8)
# Include files from /etc/network/interfaces.d:
source-directory /etc/network/interfaces.d
       auto enp0s25
       iface enp0s25 inet static
           address 10.10.10.100
           hardware-irq-coalesce-rx-usecs 0


The other option is to include the

ethtool -C enp0s25 rx-usecs 0

line in the rc.local script that is run at power-up




 

-

man hm2_eth will tell you how

Hi,
I have RPI4 4GB and I used a 32GB SD to flash these 2.9.2 and 2.9.3 images and also from the download link from the linuxcnc site, but the RPI does not boot and the red LED stays on for a few seconds and then turns off and the Green LED keeps flashing for a few more seconds and then both LEDs turn off completely. The screen shows nothing and remains gray.
The RPI works fine with the original raspbian image with the same 32GB SD.

Greetings.

Starting a new thread about this specific problem I'm having (I no longer have the original problem described here ). I have a routine I invoke from my VCP to vacuum the table. It's a bit of Python code that invokes an NC subroutine. You can see the Python code and NC routine on Github.

When I click the button on the VCP to run the routine, it starts, but then stops a few seconds into execution. Where and when it stops is random. However, the code completes execution without any indication of error. The Python code prints this to stdout:

It was suggested to insert lots of `M66 L0 E0` statements in the Gcode, but this strikes me as an unreliable way to ensure code is run. Surely `linuxcnc.command().wait_complete()` should be enough to ensure the code runs to completion?

I think you may be missing the subroutines folder from your machine's config directory. Many UI buttons are linked to such subroutines.

Hi Cakeslob,

The stepgen "PID" was adopted from the PID component. There is some auto tuning code in there but I've not looked closely at it.

github.com/LinuxCNC/linuxcnc/blob/master...hal/components/pid.c

Hello. I'm using probe basic on a parallel port milling machine.
On the one hand I have a problem with changing tools. I use the buttons on the interface but they don't do anything. If I enter the commands via MDI they change correctly.

I also have a problem with the 3D touch probe, basically it doesn't do anything when I try to calibrate it or do anything. In probe basic it shows true and false when I activate it by hand.

I'm attaching my configuration files in case it's of any use.

Hard to know with such limited info, so:
-does jogging the axis work properly or is it inverted also?
-does the nc file contain negative values for Z axis?
-does the machine have homing switch on Z axis?

You are getting the hang of it pretty good, so not "new user" anymore !