Advanced Search

nope, moving way slower than by hand. It´s not getting any position change at all, even with super slow acceleration/velocity

maybe the move is to fast or the resolution of the encoder too high for parport

Ok, I think I figured out why the label colors weren't changing. In Glade, I had a color defined in the label attributes. After I cleared that entry, then the color changing worked.

Now to work on my further modifications.

It worked for me in the virtual sim environment, debian 12, glade 3.4 installed and axis.mm sim. It was embedded as sidepanel. And the screenshots made when set example pin true/false. 

short version:

i put the ethernet cable in the rj45 socket

longer version:
i used the rio gateware and add an w5500 ethernet board to the spi pins:

 

Could you please explain how you connect the 7c81 via ethernet?

Hello,
i am currently stuck implementing a direct closed loop (2 axis lathe, parallel port, stepper motor, linear scale for closed loop).
The problem is: I do get the right position feedback, when moving manually (DRO display is correct) and i can see the correct encoder positions (in Hal-Scope: encoder.0.position). However, as soon as i try to move the axis, it starts to move and errors out with following error. If i look in the hal-scope, the "encoder.0.position" does not move one bit during the move (stepper is moving). 

--> Why does read out the position while idling but not while moving ?
Thanks 

When I tested the above code, it would change the text, but the color stayed black (no color changes)

Try with synctorefclock false, and see if your reset counter also counts up or not 

@grandixximo
Sync0shift is set to 300000

Note that LinuxCNC only supports Python3/Gtk3 from version 2.9.x so if you are using any custom python or glade code you would have to port those files to python3/gtk3.

In my opinion you'd be better off getting a second ssd and do a fresh install of 2.9.8 on that. Once you get that installed port your config files from the current drive to the new one.

Did you say you had changing values on pll-reset-count? That one should stay on 1, not increase.
Can you perhaps record pll-err in halscope and show?

From google:
Debian 10 "Buster" reached its official End of Life (EOL) and concluded Long Term Support (LTS) on
June 30, 2024. After this date, Debian no longer provides official security updates or bug fixes, making systems vulnerable.
Try this at your own risk.
gist.github.com/ishad0w/6ce1eb569c734880...#gistcomment-5812428
-
Personally, i will never understand why risk a perfectly working system for absolutely no reason, IF there is nothing you absolutely need/require. I have machines with Ubuntu 8.04 still in daily use. No internet, usually, so...

Looks perfectly fine, thank you.

@TAKUYA
Is your
sync0Shift="0"
???
You should set sync0Shift to 250000 or 500000
sync0Shift to 0 is not correct, as per my understanding of the ethercat DC specifications.