Advanced Search

I would wire:

VE- --> 7I96S input common (TB3 pin 12)

VE+ --> X,Y,Z switch COM

X,Y,Z N/C or N/O -->  TB3 pins 5,6,7

Pictures?

New operating system and new Linuxcnc version are expected to give you different behavior.
As for the config not starting, uncomment these lines in your ini and try again:

You will likely need to update 'gvcp-panel.ui', opening the file in glade and saving again might already do the trick.

yes

Also, by running linuxcnc -l in terminal, the message found as listed in attachment. However, if I replace the old mSATA drive which has with old version Linuxcnc on this same computer, everything works fine. Don't know why everything goes wrong now including the latency test

Thinking about it, i recal vaguely that 800x600 gui is included in 2.10 so chances are it is in 2.9.3 also.
Still, to small, i am used to at least full HD on 24" and bigger screens.

Normal Axis without any VCP panels should be ok on 1024x768 screens, so probably will be clipped on 1024x600, although there are modified Axis GUI to fit smaller screens, no idea if they are included with LinuxCNC.
The 1920x1200 at 10" will be very small letters and XFCE (the desktop in official Debian) does not support fractional scaling, but Axis can be set to use bigger letters and it expands accordingly so it might be OK.
Personally i would go for higher resolution always, most stuff can be managed on it, it will be pain and suffering on low resolution as even some windows might not fit.

I swapped in my own M6 toolchange code which (mostly) works just fine. Right before grabbing the tool, it runs a command to synchronize grabbing the tool with moving the spindle down slightly:
However, on the first (and only first) tool change operation, and on exactly every new program loaded, the gcode just stops running right when it's about to grab the tool. It doesn't toggle machine power, it doesn't stop or pause the program, it just sits there with the "play" button pressed as if it's running. The only message I see on the terminal (even when running verbose) is:

My workaround is to move the spindle up, retract the tool, and to run the exact same program again, and everything works as it should.Any idea on how to debug this? Or tips on where in LinuxCNC source to add some more debug output around the M63 operation? I'm running 2.9.1 on a system built from LinuxCNC LiveCD. The problem persists in both Axis and QtDragon.

Thanks
 

I'm not sure about axis, but I think it's compatible with most resolutions, but if you're able to find a 1920x1080 display you'll have more choice of user interfaces. For a smoother experience a Raspberry Pi 5 is a better choice.

It this a DIY ?

I'm looking for a suitable small 7-10" touchscreen display for use with LinuxCNC (lor a lathe). I plan to uses a RaspberryPI 4 that has a HDMI interface. The display will be positioned so that my eyes will be quite close ~12" from the display.

This one is cheap enough not sure if 1024x600 is compatible with axis?
www.amazon.ca/gp/product/B0CPM15T7H/ref=...o00_s00?ie=UTF8&th=1

or this one; 1920x1200

www.amazon.ca/Wstirhy-Portable-Kickstand...y%2Caps%2C160&sr=8-9


I have read there are some compatibility issues with some displays, so if anyone can recommend a display that is known to work well, please share the details.

Thanks

Die 'toggle2nist' Komponente sollte nun ohne die zusätzliche toggle Komponente funktionieren (in der master Version):
forum.linuxcnc.org/24-hal-components/405...nent?start=10#315456

Run from terminal again and post the output as there are likely other python2/gtk2 issues..

After deleting stdglue.py in those folders, please see as attachment, and replacing with the one in sim/gmoccapy/python/ for them, when opening LinuxCNC, the Gmoccapy screen still not o.k. (there are stdglue.pyc files, I think they won't have effect, I haven't do anything on them)

To have some 3d model, just to get the thinking going, would be nice.
Provided it is not "top secret" material.