Advanced Search

Thanks for your reply I will look it over as soon as I have time. (: (:

regarding EtherCAT driver for rpi5 ethernet:

gitlab.com/etherlab.org/ethercat/-/issues/104

RPi 5 uses the

macb

driver (Cadence GEM) and not

genet

. So I guess you have to use a Raspberry Pi 4 if you want a native driver.

I'll have to add the 7i78 spindle.

JT

The spindle basically works now. But... when Linux CNC is not running, the spindle ramps often up to full speed. (I hooked the Enable pin of the drive to a +5V pin of the TB3, so obviously the PWM pin must put out full voltage when the software is not running yet)
What should be the output of the pwmgen, when no linux CNC is running?

I think I could circumvent this by connecting one output of TB6 to the Input of the Spindle drive.
Problem: Output is set up for 24 V and I have no idea if that will damage the Spindle drive.

Is it a usual approach to just put resistors into the wiring?
 
Should it be even O.K. to just install one Resistor (R1) in the output line and cancel R2 altogether?

 

Yes, sorry, did not mention it as that is always implied, normally 4 motors then add as needed.
BTW you can do Voron with just one Z motor and have all side coupled with shafts and pulleys/belts, but that leaves auto squaring/leveling out.
Most of my Vorons have 2 boards, this was very nice for the big one (460x460x1200) as one board is on the gantry and only needs power cable USB cable, while the other board is under taking care of 4 motors and the bed. Any chance i get, i will modify the rest like this, broken cables are the only issues i had with them, ever, due to small radius of cable chains and bad quality cable.

where then in Linux are these signals generated, how to register them for a specific driver And where is the PLC of the machine written?

Interesting development after more testing.

I created a new config which does not use caxis.comp to manage the spindle.  Rather, it has a (poorly tuned) orient component so the spindle can be indexed.

Running a G33.1 cycle resulted in zero pre-synch movement.  No z-axis rapid movement before the spindle 'locked' to the Z-axis.

Just smooth, synchronized movement exactly as expected at all speeds tested - including 1000rpm with a 0.050" pitch.

So now I've got a conundrum:

• Caxis.comp - allows synchronized axis movement, but tapping and (likely) threading are dodgy
  • Non-standard component, no significant troubleshooting/tuning assistance available from community
• Orient.comp - no synchronized axis movement, but tapping/threading are as desired
• Something else?
  • I'd really like a working C-axis on my lathe, but I'm rapidly losing interest experimenting with LCNC.  I want a working lathe and not a perpetual software hobby.
  • My amp can't be externally switched between position & velocity mode
  • LCNC Devs do not appear to have spindle-axis high on the list of upcoming features.

Advice welcome.

Sorry, the tabs got messed up.
Here is the setup once again

Computer                           Debian RT                                                                               XYZ closed
Vision <==(ethernet)==> Linux CNC <=========> Mesa 7i96 <=========> loop rotating
PC                                       PC with dual                                                                           platform
(CVPC)                                ethernet (CNCPC)                                                                   (no encoders)

I guess you didn't use the sysfs patch, this is required for Linuxcnc to recogonise that the environment is a real time one.

Easiest option will be to download the latest RPi4 image on the downloads page, has a 6.12.11 kernel (with the required sys_fs patch), Linuxcnc version 2.9.4. Might pay to backup your home directory.

As usual
user: cnc
pwd: cnc

linuxcnc.org/iso/rpi-4-debian-bookworm-6...25-01-27-0404.img.xz
linuxcnc.org/iso/rpi-4-debian-bookworm-6...7-0404.img.xz.sha256

I use this servo motor.
 

Yes, it is as you say, but I only want to use it for homing. That is, instead of using the limit switch at the start of the movement, when the homing command is sent, it opens the RS485 port, reads the encoder value, and if it receives the result, it considers it as the home position, and then closes the RS485 port.

The real trick is going to be the many stepper driver ports. 7 in the case of the Vor. 2.4.
 

Hi,

Please help with the following problem. On PNCConf when I click the button Test/Tune Axis to test my X-axis, the following message appears:

[
You are using a simulated-realtime version of LinuxCNC, so testing/tuning of hardware is unavailable.
]

WHAT DOES THIS MEAN, PLEASE?

My environment is as follow:

Mesa 7I96S, power supply is MEAN-WELL MDR-10-5 ( 5V, 2A ).
7I96S IP is addres is 10.10.10.10, I can ping it. And PNCConf has been able to discover the card.

Computer: Raspberry PI 4B

Operating system: Debian Bookworm 12,
Kernel: "Linux picnc 6.6.59-rt45-v8-behai-rt-build+ #1 SMP PREEMPT_RT Sat Nov  2 10:20:46 AEDT 2024 aarch64 GNU/Linux"

PNCConf: BETA Version 1
LinuxCNC: 2.9.3

ONLY ONE closed-loop Nema23 driver CL57T: Which I configure to be the X-axis.

The wiring of CL57T to 7I96S is as below. This has been suggested by Mr. PCW.

[
7I96S       CL57T
+5V          PUL+
STEP0-    PUL-
+5V         DIR+
DIR0-      DIR-

CL57T's SW3 Set for 5V mode.
]

Even though I have only one motor and one driver, I still have to configure Y, tandem Y2 and Z axes as per the screenshot below:



On the X Motor page, clicking on the Test/Tune Axis button, the above mentioned message appears:



Please note: I built the kernel myself. I have also built LinuxCNC from the source myself back in November, 2024.

What have I done wrong, and how to fix it, please?

Thank you and best regards,

...behai.
 

Don't overthink it.
The drivers in Ethercat refer to optimised RT Ethernet NIC drivers. There is a generic driver we use and then some hardware specific ones for install and broadcom, I assumed there would be generic driver support.

2 for homing, 1 for bed/height/leveling sensor, 2 analog ones for temperature
2 PWM outputs for heaters, 1 for fan ...
that is the minimum required