Advanced Search

Doesn't work as the RPi4 image was not created with SPI enable and no way to enable it
Menu-config does not have kernel option
Thus a 7c81 is still useless unless you do a debian install, compile the RT kernel, install LinuxCNC

Hi Lcvette,

It's indeed a alternative controller, once it finished.
This can take a long time. Some are good coding day's, some are bad coding day's without good progress.

It turned out, modifying lcnc's code to do thing's i would see accomplished is almost impossible.
Best reason is entanglement.
Then just writing new code from scratch is 10x faster to get things done.

There are no goals for me. It's just a project to try out new things wich got my interest's.

It's not the purpose to outsmart lcnc or something like that. Or claiming thing are better etc.

Altrough it is interesting to find out differences in lcnc and this approach.

Like this has bi-directional hal pins and used modern boost interprocess for shared memory.

Today did a mayor bug fix. It turn's out that multiple shared memory regions updated by thread's, would not exchange data
properly. Even when mutex etc. was set.
In the end it worked by using a single shared memory region for all thread's.

Does anybody know of a plug-in (does LinuxCNC have these?) that will control lathe spindle speed.
In theory the calculation is simple - the spindle RPM should be inversely proportional to the tool position X value (absolute so that it allows for both front & rear tool posts) and it would be useful to have an option to stop the spindle during a tool change. There should be a variable to allow for different materials too. Simple enough but how would I go about writing it if nothing already exists?
Thanks in advance

Hello,I followed the instructions provided in this forum thread for setting up EtherCAT with LinuxCNC.The installation and configuration seemed to go well; however, I’m facing an issue where my motors are not moving. Specifically:

• The values from STATUS word from the drives is not appearing in the LinuxCNC - 0x000000
• When I start LinuxCNC with

  lathe.ini

  , LinuxCNC loads successfully, but it seems there’s no connection with the drives.

I’ve attached the following files for review:

1. dmesg.txt: Logs showing EtherCAT activity and errors.
2. Relevant configuration files (

   hal

   ,

   ini

   ,

   XML

   , pdos, ethercat master, slaves, lcec during linux operation)

I would greatly appreciate it if someone could review the attached files and help identify any mistakes or missing steps that need to be resolved.Thank you in advance for your support!Best regards,Piotr

Hi Fakename,

The executable "ethercat_twincat" start up with a default none name "EK1100".
See the mainwindow : node_ethercat = new graphics_node("EK1100",ports);

A better name should be something like : "Ethercat".

seems to show the correct process data objects, so I'm not sure what's going on.
This is nice. That means the digital xml config is parsed succesfully.


Maybe this is not the best way to start figuring out things for you.
Best for you is maybe a minimal example where ethercat is showing your pdo config in gui, without
the usage of node's etc.

Then set some test values, to try to run the motors?

royka wrote:

Perhaps something wrong with the kernel config? You could try to install the kernel deb that I uploaded to see if that helps. Otherwise you might need to install more software, just install a complete desktop will be the fastest route to find out.

 
from then I tried so much and still couldn't compiled a real-time image which linuxcnc be installed and its latency shows up.
Could you please guide me after placing patch (patch-6.6.63-rt43) in the /patch/kernel/archive/rockchip64-6.6 and configuring fully preemption option, what changes do I need to do?
 

It's working now! I am not 100% what really the solution was. I did 3 things:

1. Deactivated Twopass
2. Installed the missing libatk-adaptor package.
3. Added some CL nets to the hal file.

Now the GUI starts and CL starts in Modbus mode.

There is no particular hardware requirement for Lathe Macros as it runs standard Gcode files with parameters.
1. I usually have a button for start, stop and pause but you can set your cycle start button up so it starts a program if it is stopped or stops it if it is running.
2. Not necessarily. If you want to use feed/rev (G95) you need software control of the spindle speed but you also need spindle feedback (ie an encoder) for that.
3. Not necessarily, you could just run on soft limits, although depending on the size of the motors and the robustness of your hardware they might be a very cheap way of avoiding expensive mishaps.
4. Depends on you personal preference really. Maybe have a look at some commercial panels for ideas. Most basic decision to make is whether you trust screen buttons to control machine motion (eg cycle start/stop, jogging, spindle on/off)

Note: you will need spindle feedback (ie encoder A/B and index) for threading.

One step forward and one backward:

---

The problem with the rio-generator has been solved in def generate(self, output_path=None, preview=False):

....
else:
os.system(f"{sys.executable} {generator_path} -p {self.config_file} {output_path}") # modified line
# old line os.system(f"{generator_path} {self.config_file} {output_path}")
self.check_status()
except Exception as error:
print(f"ERROR generating output: {error}")

---

There is another problem left in def check_status(self):

The compile button is not enabled after generating:

# checking generated config
path_config_json = os.path.join("Output", config_name, ".config.json")
if os.path.isfile(path_config_json):
ret = os.system(f"diff {self.config_file} {path_config_json} >/dev/null")
else:
ret = 1
if ret == 0:
self.info_generated.setChecked(True)
self.button_generate.setStyleSheet("background-color: green;")
self.button_compile.setEnabled(True)
else:
self.info_generated.setChecked(False)
self.button_generate.setStyleSheet("background-color: red;")
self.button_compile.setEnabled(False)

The problem seems to be in two paths that are compared. I am going to solve it next.

Another thing I want is to re-build the dimensions of the workpiece.

Have a look at how the tool cylinder is created and updated.

try:
- different USB cable
- different USB port
- adding a ferrite bead to the USB cable

Thanks for pointing out. I will keep this in mind.

Though, I am still having a problem with the toolchain on the Raspberry Pi5 running Linux on it:.

Pressing the compile button:

rm -rf rio.fs rio.json rio_pnr.json rio.tcl abc.history impl gw_sh rio.tcl

Gives me following error:

/home/cnc-winder/opt/gowin/IDE/bin/gw_sh: 2: Syntax error: Unterminated quoted string
make: *** [Makefile:34: impl/pnr/project.fs] Error 2

Any idea what could cause this?

Can you post your gcode or at least a section of it?

I do not see Images for LinuxCNC 2.9.3 on the Download page, am I blind?
With the ones provided I ended up in 640x480 display resolution, no idea why. But I could not use it.

To me, this is a big difference.

btw. build time is no issue on the RPI5.

I have such a problem when I turn on the servo driver of the servo drive b3 0121 L model, it connects successfully via mini usb and when I start the servo, that is, turn on the Servo On, the computer loses connection with the sevro driver or the draver stops responding and when this mode is turned on, not much noise is barely audible from the driver. I don't have any ideas about this problem.

The problem is observed both in Linux (ubuntu distribution) and in Windows (11 pro)