Advanced Search

I just found out that Flex GUI works on Gentoo!

JT

Yes, you can add a checkbox to disable the program view.





JT

Debian dpkg-buildpackage uses perl, perl complains when running menu-config without LANGUAGE set.

So perl hasn't anything to do with Linuxcnc but when building packages, I had to build linuxcnc to have the hm2_spix driver for the Rpi5.

I am following the steps from:
linuxcnc.org/docs/2.9/html/code/building...ding_debian_packages

but how can I disable GTK2 for the debian package build like I can do with "--disable-gtk2" for the normal build?



 

Why on earth are we using perl in a Linuxcnc project? What's wrong with Python? At least its supported by the project.

G05
High-speed and high-precision control Ⅰ
G05 P10000 High-speed and high-precision control opening
G05 P0 High-speed and high-precision control off
G05 P3 High-speed machining on
G05 P0 High-speed machining is off

G05.1
High speed and high precision control Ⅱ
G05.1 Q1 High-speed and high-precision control on
G05.1 Q0 High-speed and high-precision control off
G05.2 Q2 X0 Y0 Z0 Free-form surface high precision mode is on
G05.1 Q0 Free-form surface high precision mode is off

G05.1 Q1 R1 - coarse high-speed processing,
the feed at the corners does not change,
the corners are cut off, the contour does not correspond to the set one.
G05.1 Q1 R5 - high-speed processing, speed-quality balance,
deceleration at the corners, corners can still be cut.
G05.1 Q1 R10 - precise high-speed processing, significant deceleration
at the corners, the corners are not cut off, the contour corresponds
to the one set within the accuracy of the machine.

G64 P 0.01 may help. I think the professionals will correct me.

The RPi 5 has, from memory, has "engery saving malarkey" for it's ethernet, and no it's not on the USB bus, that foolishness was ended with the RPi4 I believe.

With regards to the mesa firmware....it's solid and reliable, a mesa card will need it's firmware updating as often as a Toyota Echo does for it's ECU.

Remember we aint in the Windows world.

Build each version as a Run In Place (RIP) setup.

Check the docs if you don't know what that means.

Perl complains if LC_ALL or LANGUAGE isn't set.

I recently commented on the absence of MDI queuing and Run-From-Here in the AXIS 2.9.1 release on my RPi4 B mill.

I tried going back to 2.8.4, but that seemed a retrograde step.

So I made a new 2.9.1 Gmoccapy adjacent to the AXIS on the same SD card for testing.
The queuing is there, not sure yet of the Run-From-Here.

Both AXIS and Gmoccapy seem to operate independently quite OK.
But, during stress testing of the queuing, I got an occasional Following-Error which prompted me to start reviewing HALShow and HALScope for assistance.

It was then that I realized that Gmoccapy uses names for the various files identical to that of AXIS.

Is it wise to re-name all the Gmoccapy files so that they are different to the AXIS names ?

What is the best way to arrange two or more LCNC versions so that any one can be selected ?

Keep well,
John.