Advanced Search

You need this linuxcnc.org/docs/stable/html/drivers/hal_gpio.html

Rod,

Also a newby here - trying to run LinuxCNC on a Raspberry pi4 and use the GPIO but getting an error that we don't have hal_pi_gpio module. Where do we find this? I've seen reference to this being part of Machinekit. Do we need to replace our existing LinuxCNC install with Machinekit or can we simply install the necessary hal_pi_gpio modules to get the GPIO running with our Pi4?

$5 Raspberry Pi Pico 2 with RP2350 Microcontroller

linuxgizmos.com/introducing-the-5-raspbe...350-microcontroller/

Now we need them to combine the newer 2350 with the W5500.

Hi all, 
I am way to learning about linuxcnc  in that i am trying to run lathe.ini with some modification for my drive sets, but its not working.its showing error like joint 1 following error. below i attached my setup files for your reference. Looking forward for solutions.(AC Servo drive(2No's)-MADLN05BE,motor-MHMF5AZL1U2M,and Raspberry pi-5). Linuxcnc build from source file(Run in place)

The Raspberry pi images do not include the Ethercat repositories but enabling some commented out code should enable it according to feedback from etherlabmaster
Try running a script something like this

Someone got the Vfdmod package for RaspberryPi? (arm)

Orange Pi 5 Plus has better performance than Raspberry Pi 5, but its ecosystem is not as good as Raspberry Pi. Ethercat is easy to install. You can check it out forum.linuxcnc.org/18-computer/48079-can...-to-run-lcnc?start=0

Hello,

Please excuse my crashing into this thread. I've found it very useful so far and managed to set up 6 out of 7 parts of my 30-year-old Gravograph Unica that I'm trying to convert to LinuxCNC running on a Raspberry Pi with a Mesa 7C80.

What's working fine so far are the 3 steppers and corresponding home switches X, Y & Z.

But: The spindle won't turn on.
I'd like to control it via PWM and as far as I can tell there should be PWM output on pin 2 of TB5 of the 7C80.
There's no useable output there, and I'm not sure where to search and what to do next ...

If there's any chance you could have a look at my .hal and .ini files, that would be very much appreciated
I also included the output of the terminal from where LinuxCNC was launched, and the output of "halcmd show signal spin".
Voltage between SINDLE+ and SPINDLE- seems to be just noise or in the mV-Magnitude.

Thank you for reading and best regards,
Erik
captain-panda

 
 
 
 

Wow this is shaping out to be quite tricky! There is probably no useful info in this message, but I found that writing stuff down sometimes reveals a sensible next step in an otherwise blurry mess of ethercat acronyms

By rearranging the PDOs in the manufacturer supplied TwinCAT 2 project slightly I can get the drive to OP state and I can even read cyclic PDO data from it, such as statusword, velocity and position. But the other direction master-> drive PDO transmission is not received no matter what I try.
 

• I have verified equal 1ms cycle time settings in the servo drive config software, in the TwinCAT 2 distributed clock settings, in the TwinCAT 2 axis and PLC
• Even if this was a distributed clock configuration or jitter issue, Metronix ARS 2310 FS claims to be able to synchronize with raw Ethercat frames on the network if no DC is available
• I am seeing 1 (one) successful master->drive PDO transmission per preop->op state transition, where I believe TwinCAT also transfers a lot of SDO settings

It's worse on LinuxCNC, here I don't even receive any PDO data from the drive. But here too the drive reaches OP state and SDO transmissions via ethercat download or ethercat upload work and are evaluated seemingly correctly by Metronix.
 

I am still not quite sure how important the SII EEPROM data is. If I use siitool -m to create an eeprom image from the manufacturer supplied EDS xml profile with PDO mappings, any ethercat sii_write attempts are seemingly dismissed, afterwards the drive is listed only with some IDs in ethercat slaves. An image created without PDO mappings, but only with sync managers and human readable manufacturer strings etc can be written successfully and is listed as such in ethercat slaves even after power cycles.
 

With the diagnostics in my Chinese servo drives I can verify that Linux-dominated Ethercat has the correct sync cycle time of 1ms configured. I've never seen any errors from them, but there does seem to be a non-zero number of SM2 lost times and Sync lost times, maybe 1 per second? Is that normal or could that be a problem for a fastidious German servo drive?
 

The laptop on which I am currently running TwinCAT and the Raspberry Pi on which I am running the Linux Ethercat master are both not equipped with especially reputable Intel NICs ... could that be a fundamental problem? Should I look for some normal office PC for a test run?

read the comments on the downloads page. menu-config should do it for you.

In my case, it would be ethernet, I need the configuration area for the IP/Gateway address, that way, I can study the connection with ethernet cards.

cncmiljc wrote:

Could anyone help, I made the image for the pi4 following the image on the official page, but it doesn't have the area for ethernet configuration, how can I solve this problem?

The current 2.9.2 image  needs updating to 2.9.3 but we no longer install Ethercat repositories for the Raspberry pi.
I am not sure if the pi is supported in their repos for Debian 12 at all
Also I doubt that a linuxcnc-ethercat driver is built for the pi either
Right now your option is to build from source
I have raised an issue with Ethercat to explore a solution for this.

 

Could anyone help, I made the image for the pi4 following the image on the official page, but it doesn't have the area for ethernet configuration, how can I solve this problem?

Dear All,

Figured it out with extended reading - thanks for this great forum! - and a bit of creative try-and-error.
All 3 axes are set up and calibrated, homing works like a charm
Next and last open issue is the spindle - but I don't expect much difficulty with that. Otherwise there'll be another post here ...

ORIGINAL POST:
I've started a project to convert a 30-year-old engraving machine (Gravograph UNICA) to LinuxCNC running on a Raspberry PI 4 with a MESA 7C80. I have several Gravograph machines of various sizes available and am looking to roll out my conversion to most of them, if it works out as planned. These machines may be old, but as such they're solid and reliable. Also they are simple as there's just one stepper and one limit switch per axis and the spindle motor to control. The main reason for conversion is that the UNICA machine only runs on it's own Gravograph-unique operating system with a tiny monochrome CRT screen and propietary keyboard, with no communication port. The other, larger machines can communicate via serial port, but they also require Gravograph-only software ...

So far, I got the Raspberry PI, 7C80 and LinuxCNC up and running to the point that the x-axis stepper is operational by using linuxcnc.hal and linuxcnc.ini from this thread:
forum.linuxcnc.org/42-deutsch/52725-3-ac...esa-7c80-und-raspi-4

As far as I can tell, there's no wizard available (stepconf etc.) for configuring the MESA 7C80, so I need to work with the config files directly(?)

I modified linuxcnc.ini so that the stepper runs smoothly, and added three lines for the limit switch and homing. The stepper now starts running when I home the machine in LinuxCNC, and the program is apparently waiting for the limit switch to be triggered.
This is where I'm currently insecure and would like to ask for assistance:

• What terminals to connect the limit switch to at the 7C80?
• How to set it up as a NC contact (Switch opens when x-axis home position is reached)?
• How to set up homing to move the spindle towards home at first if the home switch is not triggered, and then move a short distance away and back to the final home position? 
  
  This is my current linuxcnc.ini:
   

  File Attachment:

  File Name: linuxcnc.ini
  File Size:4 KB
  
   
  Thank you for reading and thanks in advance for any answers!
  
  Best regards,
  Erik 
  captain-panda

meister wrote:

[code][code]EDIT: the config i build is only for testing, serial port will not work for LinuxCNC,
if you want to run LinuxCNC you need SPI (raspberry) or UDP (W5500 / UDP2SPI-Bridge)

[/code][/code]

Everything set-up & synthetizing-wise is working flawlessly. Said it before and I'll say it again; pretty EPIC work you've done for us   

I took onto your advice and stopped by my local gizmo shop to pick a W5500 Lite. Inserting a visual of my benchtop hardware set-up for inspiration and good luck!