Advanced Search

Config is in first post, starts with Biesse.ini
There are no errors, everything looks as if g-code file is being executed - I can pause, resume, execute next line, stop, you name it. But nothing actually happens. Running normal g-code files is ok, I have made quite a few test parts

Should I make a video of that?

Hi guys,

I have been trying for a couple of days to get the e stop to work on my diy cnc router.
I have an safety circuit which connects 24v supply to a relay(which switches on motor powers).  Output 00 of mesa card 7i95t and 4 physical estop NC are wired in series to this safety circuit.
In parallel i have wired this circuit to mesa input 01.

Here is my hal io code.

I have many more attempts but this one came the closest. It triggers the relay for a second but does not 'stick'.
I want to reset with gui request enable en trip the circuit with either estop external button or software internal button on gui.
Can anybody please point me in the right direction, i have tried so many things and i get maybe more confused by the day
 

I had been setting that pin using Halshow for testing, but I will go ahead and net that and add it to my classic ladder file.

But got all kinds of errors that ngc file not found although I could not find any mistake where subroutine folders are specified.

can you post this config and the exact errors you are getting?

What does

ip a

report?

Also, you do need the --addr 10.10.10.10 if the card is set for 10.10.10.10
(or --addr 192.168.1.121 if the card is set for 192.168.1.121)


mesaflash --device ether --addr 10.10.10.10

 

Aciera wrote:

I am using remap/racktoolchange sample config as my starting point. It did work in simulation, but I do not get any movement when I edit ini file for axis/joints sections, add glade panels and my HAL files.


I see. Trying to edit a sim config to run physical hardware comes with a lot of potential pitfalls.
I would very much recommend to do this the other way around. Create a config that runs your hardware and then add the M6 remap to that.

That was my first approach - I had a working config and I copied in all the bits of remap from a config of previous retrofit. But got all kinds of errors that ngc file not found although I could not find any mistake where subroutine folders are specified. I even copied from sample config and recreated the folders but still error. But in sample config it did work so I went the other route of merging my stuff into sample config

Flex as of this morning can import a python module located in the configuration directory. Now you can have a lot more options and control over your GUI. This is so huge I didn't want it to get buried in the Flex Tutorials thread.



JT

Hey. This isn’t working. I have disabled the IRQ coalesce so I’m using eth0 at 10.10.10.100 fixed IP address.

The ETHER card is not found
Neither is ETH0 or other names I tried typing

I am using remap/racktoolchange sample config as my starting point. It did work in simulation, but I do not get any movement when I edit ini file for axis/joints sections, add glade panels and my HAL files.

I see. Trying to edit a sim config to run physical hardware comes with a lot of potential pitfalls.
I would very much recommend to do this the other way around. Create a config that runs your hardware and then add the M6 remap to that.

Aciera wrote:

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

# turn on all optional features except RETAIN_G43
FEATURES= 30



which has been replaced by individual entries:

 [attachment=65601]Features.png[/attachment]

 

I am using remap/racktoolchange sample config as my starting point. It did work in simulation, but I do not get any movement when I edit ini file for axis/joints sections, add glade panels and my HAL files. I do not touch [RS274NGC] and [PYTHON] sections

Aciera wrote:

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

Biesse.ini is my version, based on sample config of racktoolchange.ini

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

You have a conflict due to a previous install of linuxcnc.
The proper way would be to remove the other package but you can also force the overwriting of that file

Tutorial 18



JT

Tutorial 17



JT

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