Advanced Search

I would like the same functionality.
I would like the setup page in gmoccapy to toggle the execution of MDI commands either by enter key, double click, button (like now) or by HAL signal.
But I did not have time yet.

This functionality cannot be simply implemented using the HAL pin in HALUI, because the EMC_MDIHistory widget is in Gmoccapy. So a new gmoccapy HAL pin should be created.

EMC_MDIHistory widget is here:
github.com/LinuxCNC/linuxcnc/blob/master...cp/hal_mdihistory.py

The function to confirm the command is here:
github.com/LinuxCNC/linuxcnc/blob/bf71ba...history.py#L151-L200

In gmoccapy.py:
github.com/LinuxCNC/linuxcnc/blob/bf71ba...py/gmoccapy.py#L3444

You can create new HAL pin in Gmoccapy for self.widgets.hal_mdihistory.submit()
linuxcnc.org/docs/devel/html/config/python-hal-interface.html

FWIW, I thought is was nice that pins are named stat_* in Donomik's version.

My mind was into naming pins after the mode they are used in. Problem being there are overlaps.
For example there are many velocities: Homing velocity fast, homing velocity slow, PV velocity,
CSP velocity, CSV velocity, PP velocity, all using different PDOs, except CSP and CSV velocity which is the same PDO.
I would guess also Probe velocity, probably several versions.

On the other hand, it would be a bit convoluted for the user to use .csp-commanded-velocity when they already selected csp mode and see it as natural to use .commanded-velocity.


 

I have installed linuxcnc 2.10pre on raspberry pi4. Now I want to update qtdragonHD to latest GIT version. Can anyone guide me how to do it?

@grandixximo 

Attached are the two NC files.

Set the Mesa board for "single ended" encoder, use only GND, A+ and B+ wiper/pins.
Also, very short wires if the cable is not shielded, otherwise for anything longer than 10-15CM use shielded wire.

I'm not trying to dissuade you from using LCNC with an external PLC, but if you must have a physical PLC handling IO and similar...have you considered a PLC-only solution?

Some PLC's these days are available with high-speed outputs and built-in motion control (trajectory planner) functions.

I have built two automation machines recently using an Automation Direct ClickPlus PLC that drives three axes of coordinated motion via step/dir servos.  Programming was dirt-simple and the resulting motion met our expectations.

The main PLC has the HS outputs - no need for expensive daughter boards just to get the motion control features.

In my case the motion profiles are very simple; I've not explored the full capabilities of these PLCs... but if your needs are also fairly simple something like this might suffice.  Admittedly, the Click PLCs are fairly 'low-end', so higher-end PLC's likely have more sophisticated onboard motion control features.

For step/dir, Mesa 7i96S is the right choice, and if you do need more IO add Mesa 7i84 with 32 inputs and 16 outputs and wires to 7i96S with a simple cut down LAN cable.

TLDR
LinuxCNC has it's own PLS named ClasiLadder.
Either way you look at it, it is much easier to do everything in LinuxCNC as you can add VCP panels and tabs to Axis GUI to your hearts content.
Or am i missing something?

I've not noticed this behavior, but I'm not omniscient, I'd need more information, your pictures are lacking context...

Hello,
I'm new to Linuxcnc, I've been studying it for a month and I'm very happy with it. 
I'm retrofitting a Cortini mill (a very small industrial-grade italian cnc mill) and thanks to this forum I could get a Ethercat system working with Beckhoff hardware and I could add a lot of external hardware buttons to my system.
For example I can have a program run, pause physical button in auto mode.
I cannot have a physical button for the go/run mdi command line.
Please note: this has nothing to do with custom MDI macro buttons.
To be clear: I put the system in MDI mode, type  "G0X10" then I must use the mouse to have it run.
The keyboard enter button is not the same becouse if i recall a previous mdi command from the list touching it on a touchscreen (or selecting with the mouse) the Enter key doesn't work.
I could not find a halui connection to this go button.
The goal would be to connect it to the start program physical button that is already  working in auto mode but this could be a further step. It would just be great to connect it to a new physical button.
Is this in any way possible?
I hope to have been clear despite my bad english.
Many thanks
Alberto
 

@grandixximo 

Is it possible that if the maximum speed is not reached (without t3/s3), the jerking exceeds the limits?


   

gruß
Rüdiger

Here is a link to download everything I used to create the touch-off side panel. No installation needed as it just a python script and some support files. I am NOT a developer and this is totally ad hoc software. Also, some functionality is incomplete and if used you should consider it as a template to your specific needs. No instructions are included but the code is well commented and if you are even a novice in python you will have no issue editing it to your particular needs. This was tested on a pi5 8GB running Debian Trixie from the official downloads.

You will need Inkscape to Edit the GUI. I wrote a function in the script that opens and parses an Inkscape file and maps tkinter widgets to the named objects. The Inkscpape objects contain the X and Y position data and the width and height information for the tkinter widget. Doing this allows for super easy GUI creation and edits. The script comments explain this in more detail.

I am not offering support if you decide to use this, hopefully the community can make it better and share with everyone. I am SURE that my mdi commands and general code structure can and should be improved before considering this as a stable and good addition to LinuxCNC.

drive.google.com/drive/folders/1mLqdm_YS...5YEtc?usp=drive_link

To add some more technical context to our use case:

This is a large-format gantry-style machine for laser cleaning and automated spray painting of heavy equipment and large structures. The focus is on robustness, safety, and simple, repeatable operator workflows rather than traditional CNC part programming.

Our current concept is roughly:

• PLC: machine sequencing, state machine, safety logic, interlocks, recipe management, part dimensions, operator interface (HMI), and maintaining machine state independently of the PC
• LinuxCNC: motion control, path execution, coordinated axes, and low-level servo/stepper control

The PLC would command LinuxCNC at a higher level (start cycle, select program, pass parameters, etc.), while LinuxCNC would not be responsible for overall machine state or safety sequencing.

We are particularly interested in hearing from anyone who has implemented a similar architecture with a real industrial PLC + HMI, and how you structured communication, parameter passing, and responsibility boundaries between the PLC and LinuxCNC in production machines.

Any concrete examples or lessons learned from industrial environments would be very valuable.

Thanks for the detailed explanation — that is a very interesting architecture and I appreciate you taking the time to describe it.Thanks for the clarification regarding Beckhoff I/O. Just to be clear, in your setup you are using Beckhoff EtherCAT I/O as remote I/O, but without a Beckhoff PLC runtime (e.g. TwinCAT PLC), correct? In our case, we are specifically looking for architectures where a real PLC runtime (IEC 61131, ladder/ST, etc.) is responsible for machine sequencing and state, and LinuxCNC is used primarily for motion and interpolation.
In our case, one of the main drivers for using a PLC is to keep machine sequencing, state management, and operator workflow independent of the LinuxCNC PC. The goal is that the PLC maintains the machine state and basic operation even if the LinuxCNC PC or software needs to be restarted or serviced.

We are also targeting a more traditional industrial maintenance environment, where ladder/IEC PLC logic and a dedicated industrial HMI are preferred for long-term support by technicians who are not Linux or software specialists.

For that reason, we are specifically interested in experiences using a real PLC (e.g. Mitsubishi, Omron, Siemens, Keyence, Beckhoff, etc.) alongside LinuxCNC, and how people typically split responsibilities between PLC and LinuxCNC in that type of architecture.

Still, your approach with Node-RED, distributed I/O, and web-based HMI is useful as a reference for alternative architectures — thanks again for sharing your experience

I guess an important information is, i plan to run the drives in position control.
I plan to use the Yaskawa in closed loop.

So the drives would receive STEP and DIRECTION signal. According to manual i also has a completion signal called COIN. And obviously some alarm and enable signals as well.

Hope this clarifies a bit.