Advanced Search

The problem with the RTAI kernels is that they are stuck at v5 and they don't have such good hardware support as the preempt-rt kernels.

It is also possible that there is a problem with the 5.4.290 kernel as mentioned here:
forum.linuxcnc.org/9-installing-linuxcnc...-2-9?start=60#333143

5.4.279 is supposedly better, but I can't find it.

rodw wrote:

Life has got more complicated. With proper kernel tuning, latency can be better with Debian 13. I am in the process of publishing a second video about this on YouTube. Please refer to my channel. www.youtube.com/@MrRodW
The yet to be published video should be watched before the current one.

I watched the videos, and I have some information.
1. Every time I tried to do a clean install, it returned a firmware error rtl_nic/rtl8168h-2.fw, and I believe that because of this firmware error, the Windows boot option did not appear in GRUB. "When I learned about that utility you used, Balena Etcher, to create the installation pendrive, it solved the problem." Rufus with Windows was the cause of not creating the installation media 100%.
2. Some modifications suggested in the video did not have a better effect for me, and I believe it's because of my CPU; with Debian 13, I didn't have any success with PREEMPT_RT.

3. I did a new procedure with RTAI and observed that if I create a machine without spindle controls, I don't have crashes or the segfault error. But another issue arose: the created machine does not communicate with the LPT.

PCW wrote:

Pretty sure Tommylight has some example files using SSI feedback (which is very similar at the HAL level)

Yes of course, they are attached in the Elumatec SBZ130/01 retrofit page, not sure if i updated to the latest version so you might have to go through quite a long topic to check, although might not need the latest as the encoders were the first thing working, after the initial wiring. The latest should also have the toolchanger with grayscale feedback.

Thank you for your help, I'll check that right away.

 

Thanks for reply. That changes resolved the issue of not compiling on trixie, there was also some error on line 505 column 69 of remora-spi.c. I edited that, I don't if that's correct, but that line will only be used in case of using rpi5, don't bothered and compiled the remora component. But still same issue on trixie and bookworm.

Hope some will help.

I tried countless hours with chatgpt and changing the spindle code for CSS to work but it's hopeless. I'm convinced it's the actual 0-10v signal coming out of the ec500 isn't fast enough. Iv read earlier in the thread people complaining about the op amp been to slow and changing a capacitor. But I think that was slow for ramp up. Mine ramps up fast when commanded but seems to lose it's 10v analog signal when there is a lot of speed changes.

Is there a way to get the pwm signal before the op amp and run an external faster pwm to analog for testing . That can rule out if it's the convertor onboard or actually remora refresh rate ?

Bitfile (and changed source)  for 5i25/6i25 with 7I74 and 4 sserial channels and 4 BISS channels:

 

Pretty sure Tommylight has some example files using SSI feedback (which is very similar at the HAL level)

I've fixed some Ethercat errors using postgui_csp.hal file for csp-mode setup

Hello,

I've also tested several NC programs.
The jerk isn't maintained at transitions and at the end of the movement.
My configuration and the NC programs are attached.

gruß
Rüdiger

 

Hi all, I miss some steps in make command:

Hi all, I’ve followed these steps:I also checked my driver type (igb):Then I ran:After completing this setup, I’m attaching the new dmesg file, but EoE still seems to be active.

Hello,I am new to LinuxCNC and Mesa hardware and I am working on a relatively large project. Before going further, I would like to ask for advice to make sure I am approaching the configuration correctly.
I am on a linux 4.19.0.21 -rt - amd64 smp preempt rt debian.
My hardware configuration: Mesa 6i25 (PCIe) Connected via P3 (external connector) to a Mesa 7i74. It is intended to interface a signal BiSS-C from a RAIK060 BiSS-C rotary encoder used for motor position feedback. A mesa 8i20 Powerdrive for the motor associated with the BiSS-C encoder. A mesa 7i70 and a mesa 7i87 are used for another part of the project: Temperature sensor, Pressure sensor and one servo motor.
II am planning to build a custom wiring setup using a RJ45 cable to carry the BiSS-C signals. To connect this cable to the first RJ45 port on the 7i74.
Current status: I have tried modifying an existing VHD file as a starting point, however I am not confident that the overall architecture is correct or my intended usage. What I am looking for is general guidance on the recommended architecture for this combination of cards ( a bitfile would also be perfect ) any advice on a suitable firmware for the 6i25 + 7i74 (BiSS-C), any pitfalls to avoid or best practices for a setup of this size. I understand this is a complex setup for a beginner, but I would need help and be thankful for your time and help.

Do you need to share the code or any assistance please?

Short segments seems to have some bug, might be next week for a fix...