Advanced Search

the Z-axis still moves in the Z- direction for referencing, but only moves about 30 mm at snail's pace.

first (and only) parallelport p0
weird pinouts? This is my first Linuxcnc-installation ever, so I just followed the stepconf-wizard

Sweet.
Glad you got it sorted.

How is LinuxCNC's spindle speed command communicated to the drive?
(analog, step rate, Modbus etc)

Good evening everyone. i recently got my servo spindle en.bergerda.com/filedown.php?id=49 on my mill so i can control it through linuxcnc. the issue im having; i can only turn the spindle on and off in axis. no speed or reverse adjustment in linuxcnc. the only way i can adjust the speed is through pn33 on the drive. i have the drive setup according to the internal speed run configuration in the drive manual. does anyone have any ideas on how i can configure this drive? as usual, you guys are awesome, and thanks in advance.

Retried the RPI 4B 8GHz in the house near the WiFi router.
Installed the current ISO download, Debian 12 LC 2.9.2

Can reliably get it to connect 2.4 GH Channel 4 and 5GHz Channel 36.

My problem is obviously the WiFi extender in the workshop.

I will mark subject SOLVED, in case someone else gets the wrong impression.
John

It may also help to insert debug printing

I've got a print statement at the end of the Python routine that still gets called, even though the motion stops.

On my machine, spindle.0.at-speed must be true to do a move with G1

This would result in it not moving at all, but it moves an inconsistent amount and then stops.

When I try to install linuxcnc_2.9.2_amd64.deb I get an error.
trying to overwrite '/usr/share/applications/linuxcnc-documentation.desktop', which is also in package linuxcnc-doc-en 1:2.9.2

I removed linuxcnc-documentation.desktop and still get the same error.

I just did the last one:
Package linuxcnc is not available...

So I'm not accessing the right set of files.

-encoder feedback must be wired and used by LinuxCNC
-enable output must be wired to drive enable inputs

In a terminal:
sudo apt update
sudo apt remove linuxcnc-uspace
sudo apt install linuxcnc
-
Does this work?

That is very weird pinout for anything, so what is the parallel port attached to?

hydroid7 wrote:

Hi Everyone,
recently I was trying to get started with EC500. I was able to flash the firmware and was able to ping the board on the 10.10.10.10 address. It worked nicely with a pico probe and pyocd.

However, I continuously get joint following errors on all my joints while jogging and while executing gcodes. I cannot get rid of them.

Also, the following error is very high, even at low speeds it is more than 1mm. I also tried to increase the P gain or to increase the spike filter in remora-eth.c component without success.
My computer has the following latency  values:
 

If I ping the board over a longer period of time, I get following values:
 

There are some outliers with high ping, but they are rare.

I already tried to reduce the jitter:
- Isolated two cores
- Moved kernel threads to the non isolated core
- Moved NIC interrupt to the isolated core

I can think there can be two source of problems now:
1. Latency jitter of the NIC
2. Latency jitter of the PC (Fujitsu Esprimo P556)

Can you give me some advice please how to debug this problem? How could I trace down which one is the issue?
Thank you for your help.

Hi, it's very unlikely that following errors are being caused by jitter. The control loop should compensate for that. Why do you have your [TRAJ] MAX_LINEAR_VELOCITY so much lower than you [JOINT_n] MAX_VELOCITY? 

The [TRAJ] MAX_LINEAR_VELOCITY should be higher than the joint max velocities otherwise the frequency command will be limited.
github.com/scottalford75/Remora-RT1052-c...emora-eth-3.0.c#L545

This means that the control loop would never be able to catch up the following error.

Also, it looks like you are not you loading the latest version of the component. loadrt remora-eth-3.0

Most of the warnings are harmless.
As long as ISE makes a bitfile that meets
timing, you should be OK.

Just make sure you are using the 7C80 project
so the correct .ucf file is included, otherwise you can
brick the card...