Advanced Search

Thanks for all your replies. I managed to do it by deleting all the partitions via the live usb (including one that I didn't recognize). Then reinstall using the whole disk. Sorry for doing it the windoze way!
Thanks again

Did you check product code vs pid?
I just downloaded the ERC60V202.xml esi file, and there is says product code x0A880001,
you have 0x0A880002 in the ethercat-conf.xml you supplied in one of the early posts.
Check Product code and Vendor Information vs vid and pid.
You find it with "ethercat slaves -v" alternatively "lcec_configgen"
 

Yes, to make my idea work you would need to either have pause commands in the G-code to give the Python time to see the new value, or implement some sort of flow control where the G-code sends a pair of values then waits for a rising edge on a third HAL pin pointing the other way.
(See M66 linuxcnc.org/docs/html/gcode/m-code.html#mcode:m66 )

I made some adjustments to the regular expressions, and it seems to be displaying colors correctly now.
Check if everything is OK.

Would Monokrom be a better choice since the customizability is similar to Probe Basic?

Ok, Great.

I will try with the new settings and let you know.

Antony.

 

Erst einmal vielen Dank für dein Interesse an meinem Problem!!
In welcher Sprache bist du aufgewachsen?

Ist die ISO 6.13 RT released?

For a long time, I've been pondering this issue. I can't find any practical difference between free run and DC mode. Even though I've set up my motor to run in both modes, they seem identical or even worse in DC mode. It feels like I've never actually activated DC mode on LinuxCNC. This could really be a big discovery for me. Thank you very much!

Die ISO auf dem link runterladen, neu instalieren, testen.
Diese ISO hab 6.13 RT kernel, soll kein probleme vie die 6.01 im die officielle ISO haben, kan aber andere probleme habben.
Sorry, aber ich schriebe English mehrfah schneller. Und mache wenig fehler...

brewing...

But checking the hash of big file is ssoooo sloooowwwww.....

Ich habe keine Ahnung was du mir damit sagen möchtest.
Es hat schon seinen Grund, warum ich im deutschsprachigen Teil dieses Forums schreibe.

Aber gerne berichte ich, ob der Prozessortausch etwas gebracht hat.

unknown wrote:

iopl() is a system call required to gain access to privileged resources.
It is unclear whether the user has attempted an install from the Linuxcnc ISO or from a vanilla Debian install with a self built kernel or via package manager. Neither is it clear whether this is a RIP install of Linuxcnc or via a package.
If the OP can clarify these items and if self installed give a source for the instructions or elaborate on the process this would be great.

Blindly giving advice such as "reinstall" or redo this or that is the advice that is very common to the "Windows Ecosystem". As ethical Linux users it is far better to establish what the actual issue is and then make recommendations.
Even if one does suspect a corruption of the installation media it would be of great value to suggest, and advise the user how to, check that the ISO is a good download.
Tommy's advice regarding rebooting is a good suggestion regarding a previously "hung" Linuxcnc session.

So once we establish the user's method of install we can hopefully forment a solution.

Agreed.


However, non-Windows OSes can also benefit from clean installs.

Especially on Mac, installing apps leaves leftover gunk and lauch daemons.

Linux is better because apt purge exists, but it's not 100% perfect either.

Some programs (like Java) still create cache directories and stuff.

Try this and report back if it works as is

forum.linuxcnc.org/9-installing-linuxcnc...-1-linuxcnc-2-10-iso

Probably locale setting issues, so set the locale to en_US and UTF-8 and try again.