Advanced Search

Thanks for the work!

- I ike the Gcode properties tab.

- Not sure I care much for the progress bar under the Gcode display but if it's configurable why not.

- Directory tree would be nice. I often see people using different folders for different projects/customers.

The P1 pinout can be random, it's completely determined by the PIN_XXX file.
(take a look at the source file include in the zip)

The only real pinout limitation is that modules like encoders or stepgens
are enabled by total number (num_stepgens=3 for example) rather than
individually, so you cannot trade off these pins for GPIO on a pin by pin basis
at runtime in hal. This is not actually a hardware limitation but just a choice 
made to simplify the driver command line.

Full disclosure, I know absolutely nothing about CNCs.

I love electronics and automation, and I recently acquired a Unimat SL100 and I decided what a great spare time project.  All my research points me to LinuxCNC, which brings me to my question...  What are some recommendations for USB controller boards compatible with LinuxCNC?

**QUICK EDIT...  I am looking for something inexpensive and entry level to get my feet wet so to speak.  I am not super concerned about performance yet, this is more of a proof of concept.  Once I get basic functionality working, then I will jump in with both feet and sink some $$ into it.

Any guidance is greatly appreciated!

Thank you

blazini36 wrote:

"What would the open function do?"

If you use flexqss to make a qss file then close it, your done. You can't edit it after the fact without some File->open type function. There's an awful lot of different selections to make having to make them in 1 sitting.

"Can you elaborate on apply the background colors?"
How do you change the background color without using a theme in the ini? If you specify a qss, the theme doesn't work.....or at least that's what I'm seeing. From my setup, it's either use a flex theme or the background is white.....and my qt theme is dark on my Debian VM. Designer preview shows my ui as dark, launching LinuxCNC with a qss specified it is white....so maybe I'm missing something.
 

I can see the usefulness of being able to open a qss file and set the various widget stylesheet properties.

Yes it is either use a theme or create your own qss stylesheet and use that.

As for the main window background color I need to add that but in the mean time...

JT

So I understand correctly that you have the Progressbar of the currently running program twice? Once under the G-code and once in the G-code properties?

But usually one have its G-code in one directory

Am I the only one who uses folders for different projects?
I have a huge problem when I upload files to a user's machine and they are in a folder and then I leave. Then they call me and it is very difficult to direct them to the correct folder because they don't know where they are. Plus most of my friends use Windows so they are looking for C:\

No, you do not need two LAN ports, one port and a dedicated Ethernet switch will do,
but you do need two different IP addresses on the 7I92s.

I would suggest 10.10.10.10 and 10.10.10.11 and a host address of 10.10.10.100.

In addition for efficiency the reads should be queued, that is, instead of:

addf 7i92.0.read servo-thread
addf 7i92.1.read servo-thread
__________________________________ bunch of other addfs

addf 7i92.0.write servo-thread
addf 7i92.1.write servo-thread

You should have:

addf 7i92.0.read-request servo-thread
addf 7i92.1.read-request servo-thread
addf 7i92.0.read servo-thread
addf 7i92.1.read servo-thread
__________________________________ bunch of other addfs

addf 7i92.0.write servo-thread
addf 7i92.1.write servo-thread


This is more time efficient as is does not wait for the first 7I92s response
before requesting read data from the second.
 

Recently I had to install linuxcnc on a previously win11 installed hard drive, it was not possible , setup refused to make partitions for new sistem.

Solution was to go into live mode and then from Gparted delete all previous partitions on hard drive, then the install went without problems.

USB receivers are tied to pendant, you can not replace it as I was informed . Only solution is to buy a new set.

If you have not damaged the board it should be repairable , maybe take it to some smartphone repair shop.

Hello Chriss,

History:

Gmoccapy had an integrated functionality. If a tool was changed, the tool correction was automatically turned on.
github.com/LinuxCNC/linuxcnc/blob/e586c3...ccapy.py#L3537-L3541
I named this functionality AUTOMATIC_G43.

The idea of ​​this functionality is great. Unfortunately, this functionality was implemented in the Gmoccapy GUI. This caused race conditions in certain LCNC configurations and on certain hardware. Norbert had a problem simulating these bugs at all.

After long discussions, Norbert agreed to remove AUTOMATIC_G43 from his Gmoccapy GUI. However, he had a condition that this functionality be preserved at least using REMAP.
github.com/LinuxCNC/linuxcnc/pull/3113/f...d37cd778756e98de8fff
And in the configuration files for Gmoccapy, this Remap should be added.

My wish:

I added this remap to the configurations, but a lot of configurations are done using PNCconf. I wish the configurations from PNCconf included for Gmoccapy:

added in INI file:+ Python and Macro file:
 
 

I think it will be very dangerous when Gmoccapy users switch from version 2.9 to 2.10. If they change the tool and the tool correction does not change as they were used to, it can cause physical crashes of the machines. That is why I would like PNCconf to retain this functionality in version 2.10 using REMAP.

As an advantage of this PNCconf modification, I see that users will have a template for creating Remaps. It is difficult for a beginner to understand what toplevel.py, stdglue.py, remap.py are for. This way they would only modify change_g43.ngc and/or settool_g43.ngc.

I don't know how to approach this:
1) make the above changes only for Gmoccapy
or
2) make the AUTOMATIC_G43 functionality in PNCconf for all GUIs. Gmoccapy should have this functionality enabled by default.

Fortunately, we have enough time, because this will be needed only for LCNC 2.10

Zdeněk

zz912 wrote:

1) What shows the progressbar bar?

Progress of the currently running program

zz912 wrote:

2) Picture of GUI looks good, BUT what is source of data?
Are the data computed automaticaly?
If yes, this is fantastic stuff.

It's calculated by LinuxCNC's gremlin. It has been available in Axis for ages und since 2.9 available as gstat message for everyone (see linuxcnc.org/docs/devel/html/gui/gstat.html --> graphics-gcode-properties)

zz912 wrote:

I dont know, what do you mean by this:

name (string): Name of the loaded file
size (string): Size in bytes and lines
g0 (string): Total rapid distance
g1 (string): Total feed distance
run (string): Estimated program run time
toollist (list): List of used tools
x (string): X extents (bounds) 1
x_zero_rxy (string): X extents without rotation around z (bounds) 1
y (string): Y extents (bounds) 1
y_zero_rxy (string): Y extents without rotation around z (bounds) 1
z (string): Z extents (bounds) 1
z_zero_rxy (string): Z extents without rotation around z (bounds) 1
machine_unit_sys (string): Machine units (Metric or Imperial)
gcode_units (string): Units in G-code file (mm or in)

?

These information are available to be displayed in this tab. See the docs above.

zz912 wrote:

5) The weak point of the chooser page is that it lacks a tree

It also lacks navigate back and forth buttons for example. But usually one have its G-code in one directory so I will not spend much time on this.

 

With the user command file it works perfect. Thank you!

Last time I built the 6.12 rt kernel for the RPi 5 was about 2 months ago and was pretty straight forward (since I don't use it for LinuxCNC so didn't need additional patches). Only installing it was a bit weird as described at github.com/by/RT-Kernel

The 6.12 kernel is with LTS and already released, so that might be a better choice, depending on if you want a more stable kernel vs newest.

You can try remove AUTOMATIC_G43 from gmoccapy.py:
github.com/LinuxCNC/linuxcnc/pull/3113/f...89eab9bcc7a6913808a9

Maybe some kind of burnt offering or sacrifice as well. This is purely meant in jest.

Tho I think my "life choices ability" requires an exorcist or something.

The Rpi5 will work fine with the posted image on the download page. Will be fine for mesa ethernet.
For SPI you'll have to compile Linuxcnc from the most recent sources, master or 2.9.3, as they include the spi driver thats supports the RPi5. If using ethernet nothing needs to be done.

This may be worth a read
github.com/by/RT-Kernel

Along with this post
forum.linuxcnc.org/38-general-linuxcnc-q...6-12?start=40#318767

I'm actually getting fed up with my RPi5, for the second time for Linuxcnc, it's a Me Issue which I fully admit to. Hopefully I'll be able to gently with great care put it back into the container rather than forcibly inserting into the wall, which will make other people mad at me.