Advanced Search

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...

no, the problem are the default PID values,

please try to set your DEADBAND to 0.0005

next testing round in 3d contouring, 25k line and later are critial and we can observing high accel-cmd peaks ... I am not expert, I need to ask you guys before create any outcomes... I can chare gcode file but here it exceeding limit

Thanks nanowhat, I checked my version and it’s actually 1.6Could you help me understand how to disable EoE in this version?

Thanks a lot, Lorenzo.

Does RIO have any additional backlash comp that isn't set in the HAL file?
I seem to be getting a consistent 0.038" of extra steps when changing direction, but it isn't an instant amount as you can see with this logging with a dial indicator.
I also checked my machine with larger repeated moves to see if something was slipping, but it hit the exact same spot repeatedly.

Here is the motion vs dial log:
g1 x0.000 = x0.000
g1 x0.100 = x0.100
g1 x0.150 = x0.150
g1 x0.200 = x0.200
--- Change direction
g1 x0.100 = x0.060
g1 x0.050 = x0.010
g1 x0.000 = x-0.038
--- Change direction
g1 x0.050 = 0.050
g1 x0.200 = x0.200
--- Change direction
g1 x0.000 = -0.038
g1 x0.010 = x-0.019
g1 x0.015 = x-0.009
g1 x0.020 = x0.000
g1 x0.025 = x0.010
g1 x0.030 = x0.021
g1 x0.035 = x0.030
g1 x0.040 = x0.040
g1 x0.100 = x0.100
g1 x0.200 = x0.200
--- Change direction
g1 0.190 = 0.179
g1 0.180 = 0.160
g1 0.170 = 0.140
g1 0.160 = 0.120
g1 0.150 = 0.110
g1 0.140 = 0.100
g1 0.130 = 0.090
g1 0.120 = 0.080
g1 0.000 = -0.038

amanker wrote:

I was using remora on BTT Octopus pro board. Few days back I had to remove the board for some reason. Now it's not working. Nothing has changed. I tried erasing and reflashing remora by stm32 programmer. Tried changing spi cable from board to rpi4. I can see remora firmware is working on board. I added blink module to verify remora, it's working. I can see via UART console that remora ha loaded correctly and comes to idle state.
But on LinuxCNC side machine don't comes out of estop. No configuration changed. Tried new trixie image but can't compile remora due to incomplete pointer error. Don't know what's going wrong?  
 

Hi,

I'm not sure I can help for the estop state in lcnc. I would start by checking the payloads in both BTT firmware and hal component.

For the compilation error, I ran into the same error when I was trying to compile my TMC5160 component and solved the problem by changing the code a bit. As I'm not a coder, I have no big idea what I'm doing, but sounds like a casting problem to me. You can try following changes in the rp1lib.c of the linuxcnc component:

Replace the lines:

dws = &inst->spi[spi_num];
spi = &inst->spi_dev[spi_num];

with

dws = (struct dw_spi*)&inst->spi[spi_num];
spi = (struct spi_device*)&inst->spi_dev[spi_num];

and:

dws = &inst->spi[spi_num];
cfg = &inst->spi_cfg[spi_num];
dev = &inst->spi_dev[spi_num];

with:

dws = (struct dw_spi*)&inst->spi[spi_num];
cfg = (struct dw_spi_cfg*)&inst->spi_cfg[spi_num];
dev = (struct spi_device*)&inst->spi_dev[spi_num];

After those changes I was again able to compile my component and could use it. BUT I didn't try it on a RPi5 actually using the rp1 lib, just on a RPi4.
Hope it helps.

You are right, my apologies, I was looking at it on my phone, and it formatted it intuitively. We'll be looking into it, thank you for reporting

Which error are you referring to?
seems to be caused by PCI-express link power management
Which version of the ethercat library are you using? 1.6 by default has ethernet over ethercat active, and it doesn't seem to be compatible with linuxCNC. With 1.6, one must compile the library from source to disable EoE.

it was true:

16 bit IN TRUE ini.traj_arc_blend_enable

I was running the torus gcode (from the torus.png --> image to gcode with whatever defaults)

EDIT: here's the gcode that triggered the bug:

 
 

Which G-code did you use for the test? I'd like to try it myself.