Advanced Search

Might be worth asking in the Remora thread.

Hello forum,
I have 6 x 1KW Lichuan LC20 drives and have been trying to get them to work with Raspberry Pi 4B 4GB and LinuxCNC for about 9 months.  I realised I don't have the technical knowhow to make this work.  Using this forum, youtube and Grok, I was able to get close, getting the Raspberry Pi to work as a master and I even got all 6 drives to work as slaves, but trying to get them in to OP mode proved impossible.  On one occasion, when I unplugged 5 of the 6 drives, I managed to get it to go into OP mode but have not been able to replicate it since.  And I have never been able to understand how to get them to turn using LinuxCNC, that baffles me a bit so I have never actually seen the motors work ever.
I am open to buying hardware that kinda works out of the box but I have no idea what that is.  
Can anybody on this forum work with me over time to help me to get these things to work with LinuxCNC, or even Mach???  I can't return them, and after spending $2K on them, I can't afford to buy something a little more 'out of the box'.
Any assistance would be greatly appreciated.
Andrew.
 

Is it this?  github.com/cakeslob/RRW_LAB
google does not find it but duckduckgo shows it first

I tried Googling the RRW lab board and all found was this thread.

Can you link to a product page or give is more to go on?

Do you have a driver for it?

Hi, I’m new to linuxcnc and I am trying to get the rrw lab board to work. I’m trying to use the SPI sd card firmware with an STM32 Blackpill. The blackpill led is flashing, but there’s no connection. I can’t seem to find anything online about setting up SPI with a pi5. Any help would be appreciated. 
Thanks.

Hi all. I've been playing with a design for a board that will allow me to read arc voltage with a Raspberry Pi. I think I've got something that will plausibly work. I'd appreciate a review of the attached schematic because circuit design is not my core competency.

Here's a quick tour:
1. Inputs are expected to be connected to the arc volt port of a blowback-start plasma power supply. 
2. Input voltage is limited to 250V by a TVS diode
3. Voltage is divided 50:1
4. RCRC filter limits frequency to 14Hz
5. Raspberry Pi reads divided voltage via ADC

Thanks!
 

Hello All,

New to the forum and first of all would like to thank you for the valuable information you guys post, it has helped so much me moving ahead with my build. id appreciate your help with my issue where it cannot activate the thc even when all the settings (that i know of) have been properly adjusted. first my setup:
-LinuxCNC QTPlasmac table
-Rpi5 with image LinuxCNC 2.9.8 Raspberry Pi 4/5 OS based on Debian Trixie
-Mesa 7176s over ethernet
-THCAD2 + 3M resistor array enclosed near the plasma source, F+/F- routed to mesaboard encoder input A with shielded microphone cable grounded at control side, also used a more simple twisted pair for testing.
-Used Pnconf for setting thcad2 trimming and ratio
Tested for correct voltage measuring for example, hooked a power supply from 39 to 56 volts and Main screen voltage readings coincide very accurately to multimeter reading.
-Flaring 65 plasma source with no cnc interface. (HF piercing) voltage probing connected to torch (-) and clamp (+) leads.
-For testing im using a straight line of 100mm at full speed so thc is not affected by speed reduction  (tested from 400 to 1800 mm/min)
-THC is enabled
-Mode 0 is used so arc ok is derived from voltage readings
-setup plasmac.arc_lost_delay =.3 as was having some issues for getting it to start cutting due to initial spike/valley.

I took the follwing HALSCOPE trace where:

 

1)torch on triggers,
2)probe voltage goes to 260 for piercing, then falls, then recovers to around 94v
3)Arc OK signal goes to true
4)Pierce delay elapses
5)Movement starts
6)THC active never goes up and of course  no correction

as Far as I can see voltage is "stable" once cut starts and there is no variation that could lead to deactivation as the tresholds are LOW=39 HIGH 990 (for testing purposes), samples 10 and threshold voltage 10.

has anyone had this issue or any lead on what to look at?

 
Hi all,

I am developing a 4-axis foam cutter using a Bigtreetech Octopus Pro V1.0.1 F429 connected to a Raspberry PI5 via SPI.
I have amended the Config.txt file, the .hal and .ini, and named the axis as X, Y, A and U.

What happens is the following:
1- X and Y axis work fine.
2- If I try to move the A-axis, then both A and U move.
3- If I try to move just the U axis, then nothing happens.

What am I missing?

I have attached the board pin mapping, the Config.txt and my .hal and .ini files, which were modified from those in the remora "ConfigSamples"  directory.

Cheers
Pier


 

Hi i can get cheap a q6a with 8gb ram. I read that its more powerful then a raspberry pi 5.

But here i cant find Informations.

Is it useless for us?

Thanks

Hello everyone, I am working on an upgrade for my old lathe. In short, I want to replace the old main motor with its multiple belt stages as well as the change gear system for the lead screw with two servos (more detail below). I am wondering whether or not LinuxCNC is the right way to go about it. I am a mechanical engineer by trade, but have little to no experience with control systems or LinuxCNC, so I do apologize in advance for any potential stupid questions coming up. 

The long version:
I want to upgrade my lathes drive system. It's an old machine, build somewhere around 1945, and it uses an induction motor followed by two v-belt, one flat belt and an optional gear stage to set the spindle speed, giving me a grand total of 12 possible spindle speeds to select from. Changing speeds therefore also isn't the quickest process. Even worse is the feed gearing driving the lead screw; It's set up as a change gear type system, so to set the feed rate I have to disassemble and then reassemble the drive train, which makes for painfully slow changes in feed rate. While the machine is certainly mechanically beautiful, my shop is not a museum and my time is quite precious to me, so I want to change that. The plan is to replace the main spindle motor and drive train with a big servo, and the feed gearing with another, smaller, servo. That would allow for easy changes of my feeds and speeds, as I just need to set whatever value I want on the controller. The feed rate per revolution would then no longer be controlled mechanically through the feed gearing, but electrically, by the smaller servo acting as a virtual reduction gearing if you will.

I already sourced the servos, a 1kW for the spindle and a 400W for the lead screw. They use EtherCAT for communication. For the controller I was thinking about either a Raspberry Pi 4 or a Kunbus RevPi that I have lying around. To run the machine I want to use LinuxCNC and an open source EtherCAT master, as done by Marco Reps for example.

I am however unsure on how to go about it. I don't yet require the full CNC potential of LinuxCNC; That might come at a later point, but for now, all I need are the following two features:

• Set the spindle's rpm
• Set the feed rate

Both of those options I would like to have on an easy GUI, ideally with as little unused "clutter" as possible. Depending on how hard that is to pull off, I would not mind learning how to program/code/design that myself, it might however quite likely be far above my current skill level. I am a mechanical engineer after all, not a software wizard. 

For the actual servo control I would like the option of having soft start and stop options by controlling the acceleration and jerk, so that the servo doesn't just violently try to reach the set spindle rpm.
Ideally the feed servo would be set up as a slave, following the main spindles rpm precisely, i.e. perfectly mimicking a mechanical gear train. So if for example the main spindle bogs down during thread cutting, the feed servo should ideally not just run it's course and lose synchronization. That should certainly be possible via EtherCAT, I just don't know how hard that would be to set up with LinuxCNC. It would however also be acceptable to solve that via a maximum allowable tracking error for the servos, if full on synchronization doesn't work.

I have a lot of ideas and things I would at some point like to add/have, from motor load indicators, a DRO via linear encoders, small easily programmable cycles all the way up to full on CNCing the lathe. But for now its baby steps, i.e. getting the lathe functional with its new servo drive train.

Is what im having in mind possible with LinuxCNC? Does anyone have pointers to a similar project? Or any advice or resources on how to set this up in LinuxCNC? How do I go about setting up the big servo as a spindle motor? Can I actually use the smaller servo as a slave synchronized to the main spindle motor? Is it possible to create a simple custom GUI showing only spindle speed and feed rate? Or would you guys recommend an entirely different route to set this up?

Any advice is greatly appreciated. I apologize if the post became a bit "rambly" in places and for any stupid/basic questions contained in it.

Cheers,
Nik

Hi there!

my Raspberry Pi5 died so i needed to setup thing new, but I can´t get it working anymore. It worked before... 

I have two Ethercat modules which need "speical care"
1. its the external "EP1809-0021" this is identical to the EL1809, so just replicating the last line in the el1xxx.c with the correct PID, works
2. the EL2564, this is a dedicated "driver" which is copied into the linuxcnc-ethercat/src/devices which gets compiled, works... 

LinuxCNC runs in the SIM Modes... also with ProbeBasic
EtherCat works - ethercat master and slave commands...
but LinuxCNC with ProbeBasic and Ethercat doesn´t want to start.

Here you can see my terminal-log when starting LinuxCNC
 
here you see my Ethercat terminal Outputs...
the EP1809 wasn´t connected...

so what can it be? I followed the "EtherCat installation from repositories" from Rod... i tried multiple images, 2.94~2.98 on Bookworm and Trixie... 

thank you

miniwini

maruf1777 wrote:

DRO shows identical position at arc entry and exit — LinuxCNC believes the machine returned to the correct point. But probing a fixed reference shows X shifted +9.3mm and Y shifted -12.2mm. HLFB is configured at 20 counts and did NOT trigger. This means every commanded step was executed by the motor. The error is in the arc interpolation — the step path LinuxCNC generates to trace the circular arcs does not sum back to the correct physical position.
LinuxCNC version: Master (2.9), running on Raspberry Pi 5 (4GB), Debian Bookworm, Mesa 7i96s over ethernet (hm2_eth), SERVO_PERIOD = 1000000.
 

Linuxcnc doesn't generate a step signal. All planner calculations are based on position (float64 number) and velocity signals.These numbers (not steps or pulses) for each servo cycle are sent to the Mesa board, where "stepgens" converts them into pulses.

These are the connections in hal:
joint.N.pos-cmd -> hm2.N.stepgen.position-cmd;

Each cycle, Mesa sends back the counted number of generated pulses for reporting:
joint.N.pos-fb <- hm2.N.stepgen.position-fb;

The difference between the sent position and the feedback is tracked using the joint.N.f-error pin.The path planner (on the computer) and stepgen (inside the Mesa board) do not influence each other, but each performs its own role in the chain.

I hope you understand that, in this logic, the position can't simply shift in the planner. If there was an error, it would mean it was transmitting an incorrect coordinate to the mesa, and the same incorrect coordinate would be visible in your DRO (since it's also connected to the joint.N.pos-cmd == axis.N.pos-cmd signal). And the incorrect path would be drawn in the graphics window. The "live plot" draws either based on the pos-cmd or pos-fb numbers. there's a switch for this.

If "LinuxCNC believes the machine has returned to the correct point," then the planner has indeed returned to that point and is transmitting that exact position command to mesa.If the error occurred in stepgen inside mesa, then the position-fb counter would have returned an incorrect number of counts (as a float64 number, not pulses).

If your servos don't report their own following error, then there remains the possibility of an error between Mesa => Servo. Due to electrical interference/noise, not all pulses could have been received by your servo - it thinks it's following the path, but in fact, not all the pulses reached it.
This is confirmed by the fact that you saw a connection between the error and pulse timings.

I have been working with linuxcnc and fusion 360 for a long time as post programmer, so I can assure you - there is no connection between the post processor, pathplanner and your problem. Both work fine.

DRO shows identical position at arc entry and exit — LinuxCNC believes the machine returned to the correct point. But probing a fixed reference shows X shifted +9.3mm and Y shifted -12.2mm. HLFB is configured at 20 counts and did NOT trigger. This means every commanded step was executed by the motor. The error is in the arc interpolation — the step path LinuxCNC generates to trace the circular arcs does not sum back to the correct physical position.
LinuxCNC version: Master (2.9), running on Raspberry Pi 5 (4GB), Debian Bookworm, Mesa 7i96s over ethernet (hm2_eth), SERVO_PERIOD = 1000000.

Very nice, thank you, and also thank you for sharing the files on GitHub.

Hi,

Just wanted to share the control panel I've built for my VM32 CNC conversion project. The aim was to get away from a typical PC+Monitor setup and build an all-in-one control panel for LinuxCNC which can be mounted on the mill cabinet and control the mechanics through MESA board. I published the resulting models for this build in a Github repo:  github.com/belovictor/linuxcnc-control-panel
You can also find the panel build video on my YouTube: 

Best regards,
Victor Belov