Advanced Search

The conflict is between your halfile and 'hallib/qtplasmac_comp.hal':

/usr/share/linuxcnc/hallib/qtplasmac_comp.hal:21: Pin 'halui.machine.is-on' was already linked to signal 'yellow-in1'

Your halfile seems to get called first and 'halui.machine.is-on' is connected to the signal 'yellow-in1'. Then 'qtplasmac_comp.hal' is loaded and it wants to assign the same pin to a different signal which causes the error.

Open '/usr/share/linuxcnc/hallib/qtplasmac_comp.hal' and see which signal name it wants to connect 'halui.machine.is-on' to and use that signal in your halfile:

Change:
To:

in der ini, kommentier mal diese 2 Zeilen (# voranstellen) und schau mal ob der Fehler immernoch erscheint:

This file was updated with the Mesa Configuration Tool on Oct 12 2024 22:27:20
# Changes to most things are ok and will be read by the Configuration Tool

[MESA]
VERSION = 2.1.7
BOARD = 7i92
BOARD_NAME = 7i92t
FIRMWARE = 7i92t_g540d.bin
CARD_0 = None
CARD_1 = None

[EMC]
VERSION = 1.1
MACHINE = testtiff
DEBUG = 0x00000000

[HM2]
DRIVER = hm2_eth
ADDRESS = 10.10.10.10

[DISPLAY]
DISPLAY = axis
EDITOR = mousepad
PROGRAM_PREFIX = /home/ramcnc/linuxcnc/nc_files
POSITION_OFFSET = RELATIVE
POSITION_FEEDBACK = ACTUAL
MAX_FEED_OVERRIDE = 1.2
CYCLE_TIME = 0.1
INTRO_GRAPHIC = emc2.gif
INTRO_TIME = 1
OPEN_FILE = ""
PYVCP = testtiff.xml

[KINS]
KINEMATICS = trivkins coordinates=
JOINTS = 0

[EMCIO]
EMCIO = iov2
CYCLE_TIME = 0.100
TOOL_TABLE = tool.tbl

[RS274NGC]
PARAMETER_FILE = parameters.var
SUBROUTINE_PATH = /home/ramcnc/linuxcnc/subroutines

[EMCMOT]
EMCMOT = motmod
COMM_TIMEOUT = 1.0
SERVO_PERIOD = 1000000

[TASK]
TASK = milltask
CYCLE_TIME = 0.010

[TRAJ]
COORDINATES =
LINEAR_UNITS = mm
ANGULAR_UNITS = degree
MAX_LINEAR_VELOCITY = 0.1
NO_FORCE_HOMING = 1

[HAL]
HALFILE = main.hal
HALFILE = io.hal
HALUI = halui

[HALUI]

[INPUTS]
# DO NOT change the inputs they are used by the configuration tool

[OUTPUTS]
# DO NOT change the outputs they are used by the configuration tool

[OPTIONS]
# DO NOT change the options they are used by the configuration tool
LOAD_CONFIG = True
INTRO_GRAPHIC = emc2.gif
INTRO_GRAPHIC_TIME = 1
MANUAL_TOOL_CHANGE = True
CUSTOM_HAL = False
POST_GUI_HAL = False
SHUTDOWN_HAL = False
HALUI = True
PYVCP = True
GLADEVCP = True
LADDER = False
BACKUP = False

I experience the same from time to time.
try deleting stored session and everything will be as new again:


and then reboot

Please post your ini file.

How important is rigid tapping for the planner?

Certainly an important function (at least on some machines) but likely does not need optimization. Problem might be that the end position is not known before it is actually executed (I think).

[edit]
It might be a good idea to exclude the difficult cases for now. There are likely others, like where the gcode execution depends on input during runtime (eg where probing is run during gcode execution).

I m new to linxcnc and need some help.  I have mesa 7i92TF   and GEKO  controller.
when i run the config i built  - i got error below.  how do i fix it ?  Please advice - Thanks

Can not find -sec TRAJ -var COORDINATES -num 1

Dont know what went wrong with that last one. 

edit to clarify.

When i look at halconfig and PWM enable and value,

00 and 01 enable when i turn on the machine within lcnc
I can jog X and get 00 to flash up a value. 01 and 02 do not do this (02 probably because its not enabled)

Hi PCW.

Attached. I cant do it while actually trying to generate an output as it errors within a moment due to movement error

When linuxcnc is running and you expect an analog output
can you run:

halcmd show all > all.txt

in a terminal window and port all.txt here?

BaxEDM wrote:

Hi,
I am using the motion.adaptive-feed to control my feedrate. The linuxcnc manual states:
"When adaptive feed is enabled with M52 P1, the commanded velocity is multiplied by this value. This effect is multiplicative with the NML-level feed override value and motion.feed-hold. Negative values are valid and will run the G-code path in reverse."

While trying this out, it only seems to work for the range -1...1 any values above or below that are clipped to 1 or -1.

I need to be able to set the value to greater than -1, e.g. -10 or greater. Is this possible and how can that be done?
 

You could set your programmed feed rate to double and set adaptive feed to .5, then you could ramp up and down in feed rate.
 

The GS2 and GS3 are 'older technology' than the GS23/33, but a cursory review of the modbus sections in the manuals suggested to me that the gs2_vfd component may work with all three variations.

The thing to do is make a close comparison of the modbus registers for the GS2 and GS23/33.  If they match, gs2_vfd should work.  If they don't, maybe they're close enough that some minor editing would do the trick.

I haven't looked that close as I'm using analog control and setting up modbus to get info back from the VFD is way down on my priority list.  The 0-10v from the VFD to my Mesa card is working just fine for spindle load right now.

Please see the response from JT. What I referenced is for a much older VFD. I believe your VFD is much newer, as in the latest technology and therfore you would not want to use gs2_vfd.

The GS23 and GS33 are much newer technology, I believe.

Someone can correct me if I am wrong.

Mill belt & drawbar cover with drawbar button.  It's not going to stop some sort of catastrophic belt/pulley failure from coming through, but it should keep most chips & coolant out of that area.  The assembly is remarkably stiff once the mounting screws are snugged down.

Assembly is about 11" (280mm) tall for size reference.  ABS, printed pretty hot for decent layer adhesion.  Surprisingly little warping.