Advanced Search

this is what returned

sudo gdebi '/home/dylan/Downloads/linuxcnc_2.9.3_amd64.deb'
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Reading state information... Done

motion controller for CNC machines and robots
 LinuxCNC is a fully-realised CNC machine controller that can interpret
 machine-control programs (such as G-code), plan trajectories and finally
 output low-level signals to machine control hardware
 .
 LinuxCNC is modular and in principle the HAL (hardware abstraction layer),
 pluggable interpreters and variety of hardware drivers mean that it can
 control almost any software-defined physical system.
 .
 LinuxCNC relies on a realtime kernel to support real-time motion control,
 typically updating the position waypoints every 1mS and reacting to
 input within tens of microseconds.
 .
 Modules exist to use the low-level parts of LinuxCNC as a motion-control
 client for OpenPnP. Interfaces exist for ROS (the Robot Operating System)
 with which LinuxCNC has considerable overlap.
 .
 LinuxCNC supports arbitrary kinematics (the mapping between coordinate
 space and actuator space) and can control both parallel (eg Stewart
 platform) and serial (eg robot arm) systems in addition to conventional
 cartesian machine tools.
 .
 LinuxCNC supports 9 cartesian axes and 16 "Joints" (individual actuators)
 though the joint limit is build-time configurable.
 .
 A variety of interface hardware is supported including Modbus, EtherCAT,
 analogue +/-10V velocity control and Step/Dir. Step/Dir is supported by
 several hardware interfaces, including, but not limited to, the legacy
 Parallel Port.
 .
 A Hardware Abstraction Layer allows for great flexibility in signal
 mapping between the controller and the driver hardware. An extensive
 library of modules allow for complex signal processing within the HAL
 layer. For specialised tasks custom HAL components can be created using
 a C-like syntax and installed with the supplied tools.
 .
 By default LinuxCNC supports RS274 G-code but is extendable to parse
 other grammars such as STEP-NC or Gerber through support for pluggable
 interpreters.
 .
 If you want a computer to control things in the real world
 then LinuxCNC can do it. It is especially applicable to systems that
 are required to follow accurate paths described in cartesian space but
 has been used for numerous other applications.
 .
 This package provides the main package for LinuxCNC.
Do you want to install the software package? [y/N]:y
/usr/bin/gdebi:113: FutureWarning: Possible nested set at position 1
  c = findall("[[(](\S+)/\S+[])]", msg)[0].lower()
(Reading database ... 185376 files and directories currently installed.)
Preparing to unpack .../linuxcnc_2.9.3_amd64.deb ...
Unpacking linuxcnc (1:2.9.3) ...
dpkg: error processing archive /home/dylan/Downloads/linuxcnc_2.9.3_amd64.deb (--install):
 trying to overwrite '/usr/share/applications/linuxcnc-documentation.desktop', which is also in package linuxcnc-doc-en 1:2.9.3
Processing triggers for libc-bin (2.36-9+deb12u7) ...
Processing triggers for desktop-file-utils (0.26-1) ...
Processing triggers for mailcap (3.70+nmu1) ...
Errors were encountered while processing:
 /home/dylan/Downloads/linuxcnc_2.9.3_amd64.deb

The other thing (but maybe of no importance here) is that your ini files use FEATURES in the [RS274NGC] section

which has been replaced by individual entries:

 

 

Just noticed this, there are two ini files in that config. Are you running 'Biesse.ini' or ''racktoolchange.ini'?

'tool_change started' was printed when the read-ahead ingested that line and then it stopped reading due to the queuebuster and waited for code execution to catch up. What this means is that the actual code execution does not reach the 'tool_change' subroutine.
Not sure what's going on but whatever it is it does not seem to be a problem in 'tool_change.ngc'.

Have you tried calling that subroutine directly from MDI:

Ok so what I did and what whas the result is shown in 2 pictures attached.
In the tool_change.ngc I added following lines so that the beginning was this:
The result is that in the terminal only the first message is posted. Meaning that it did not get past that queuebuster line. What was expected behavior there? I do not have anything connected to motion.analog-in-00 so I would expect it to read value "zero" and move on...

@Aleksamc,

But maybe it will be never realized
The linuxcnc sai lib, can maybe run multiple instances of the interpreter.
But that's not tested as this point.
The rs297 lib is tangled with python. Linked to many other lcnc libs.
This makes it hard to decouple and test it stand alone.

But you make it so easy!!! I very impressed about that!
The hardest part to figur out where the "unlimited" nested while loops.
Parsing a raw gcode file to something the interpreter can read is not that hard.

@Spumco,
Such as X1/X2, Y1/Y2, Z1/Z2, C1/C2, etc.
As i understand you want to send a X2 from master to slave machine directly in the gcode.

This is not realised yet. And i think the command should look a little different as the slave's have a name.

prototype : [Command_id] [Name] [Command]

Then you should send a command like "G200 n2 G0 X100 Y100 Z100 C0".
or something like  "SEND n2 G0 X100 Y100 Z100 C0".

Where G200 is a chosen as command_id.
Where n2 is the name of the duplicated axes (XYZC).

@Arciera,
That's exactly how it is!
And it's not easy to code this into lcnc. As everything is based on one instance of lcnc.

However it's interesting to try  to setup multiple hal environments.

This is an idea of how it might work:

Websocket line
    |
    | - GUI Application (websocket client) (user land)
    | - HAL Environment A    (Super-Imposed Interpreter) (websocket server) (kernel space)                    
    | - HAL Environment B    (Machine controller 1) (websocket client) (kernel space) -|
    | - HAL Environment C    (Machine controller 2) (websocket client) (kernel space) -|
    | - HAL Environment D    (Machine controller 3) (websocket client) (kernel space) -|
                                                                                                                                                      |    
                                                                                                                                                      |
                                                                                                                                             Ethercat bus

** Ps, Relating the the lcnc trajectory's planner, soon i have to make a opencascade viewer to check the fillet output's made
in the tpmod.so component. As i can not see anything now.

 

Are the linux commands the problem?

Please use:
sudo apt install linuxcnc-uspace-dev
sudo apt install build-essential

sudo halcompile --install udp.comp

I did insert G0 G53 X20 Y20 Z80 right after that M73 and the move is not executed. Ok, I will go back now and try your suggestion.

Check the green/black header.

That is called a "rack tool changer", i am pretty sure it can be controlled with gcode only, not sure if it needs remaping (i guess it would), so it should be easy to do, although i never tried it.
forum.linuxcnc.org/20-g-code/36441-anyon...-length-probe#131714

You might want to have a look at the example config in 'configs/sim/axis/remap/rack-toolchange' as a starting point.

Note the custom entries at the bottom of the inifile:
github.com/LinuxCNC/linuxcnc/blob/master...e/racktoolchange.ini
and the ngc remap:

github.com/LinuxCNC/linuxcnc/blob/master...ines/rack_change.ngc

I have a spindle equipped with this feature for pidconnection to a relay. I need an approximate code M6 for linear tool change

Hm, as I understand it, this does _not_ give us multi thread gcode execution as that would require multiple parallel motion planners in the same linuxcnc instance. A single instance of linuxcnc cannot interpolate more than one tool path at the same time.

Thank you all.
So, I will give it a try. As far as I can see there is no header on the motherboard (small form factor).

sudo gdebi linuxcnc_2.9.3_amd64.deb
In the same folder where the downloaded files are.