Advanced Search

Search Results (Searched for: )

  • tommylight
  • tommylight's Avatar
08 Sep 2025 14:39

StepConf - tandem axe Y - comment configurer 2 moteurs synchrones

Category: Français

I can't connect them to the same driver because the motors are symmetrically positioned, meaning the direction of motor Y2 must be reversed.

You can, just switch places of ONE winding on the motor.
  • 3Draf
  • 3Draf
08 Sep 2025 14:02

StepConf - tandem axe Y - comment configurer 2 moteurs synchrones

Category: Français

Hello, thank you for your reply.
I can't connect them to the same driver because the motors are symmetrically positioned, meaning the direction of motor Y2 must be reversed.
In addition, I plan to install two limit switches later to correct for positioning mismatches between the two motors, which requires two independent outputs (and inputs).

P.S.: I'm using LinuxCNC 2.9.4 on an old PC with a parallel port.
Bonjour, merci pour votre réponse.
Je ne peux pas les connecter sur le même driver, car les moteurs sont placés de manière symétrique, ce qui fait que la direction du moteur Y2 dois être inversée.
De plus, je compte par la suite installer deux capteurs de fin de course pour corriger les décalages de positionnement entre les deux moteurs, si qui nécessite d'avoir deux sorties (et entrer) indépendantes.

Ps : j'utilise linuxCNC 2.9.4 sur un vieux PC avec port parallèle.
  • langdons
  • langdons's Avatar
08 Sep 2025 13:57
Replied by langdons on topic task: main loop took 5.019013 seconds

task: main loop took 5.019013 seconds

Category: General LinuxCNC Questions

Python is buggy.

Motors shouldn't exceed their soft limit.

That's weird.
  • andypugh
  • andypugh's Avatar
08 Sep 2025 13:57
Replied by andypugh on topic Rotary Scanning

Rotary Scanning

Category: General LinuxCNC Questions

This might be as simple as setting the G54 (or similar) coordinate offset with a G10 command using the measured value.
Then leave the G-code unchanged, and based on G54 zero as the low point.
  • mBender
  • mBender
08 Sep 2025 13:33

Machine off at the end of the programm. Repeatable!

Category: Milling Machines

Consistent position errors after a long program could indicate a step timing
or polarity issue. Too low direction setup or hold times could cause a lost step
at reversals. Wrong step polarity can also cause this issue as stepping on the
trailing edge of the step pulse (rather then the expected leading edge) will
decrease the expected hold time.

It might be worth either inverting the step polarity or increasing the setup/hold times,
at least to see if it changes anything.
 


Polarity could very well be an issue! I changed a few things on the control unit recently and did not pay close attention to the polarity. I thought that would not matter. I will test that asap and report back. 
  • mBender
  • mBender
08 Sep 2025 13:30

Machine off at the end of the programm. Repeatable!

Category: Milling Machines

Some of the cheaper fixed bearing blocks are sold with non angular contact bearings, this is something to check.
Until you perform a backlash test, and yes this can manifest as repeatable, you can not rule out a mechanical issue.
 


I machined the fixed bearings myself. You can find the parts on cults, the bearing has proper angular contact bearings and the mechanical play is minimal. Keep in mind the pictures are with the old couplings!  cults3d.com/en/3d-model/various/y-achse-kus-frasteile

Let me know how exactly you want me to perform the backlash test and I will give that a try. 
  • andypugh
  • andypugh's Avatar
08 Sep 2025 13:15
LinuxCNC 2.9.5 has been released was created by andypugh

LinuxCNC 2.9.5 has been released

Category: LinuxCNC Announcements

LinuxCNC 2.9.5 has been released.

This is mainly a bugfix release, but includes a new modbus driver for
the Mesa UART (update/replacement for mesa_modbus with more
flexibility and configurability)

Packages for 2.9-uspace for amd64 (PC) for Debian Buster, Bullseye,
Bookworm and Trixie and for arm64 (Raspberry Pi 4/5) for Buster and
Bookworm have been added to the linuxcnc repository.
If you installed from one of our live images or Pi SD-card images then
the update should be available immediately.

If you  installed into a normally-installed Debian from the Debian
repositories then hopefully the new version can be queued up for the
next point release. If you can't wait then it is possible to add the
LinuxCNC repositories to the apt sources. One way to do this and
install the security keys is via the shell script here:
linuxcnc.org/docs/stable/html/getting-st...th_preempt_rt_kernel

At the moment the live-image installer and SD card images will install
2.9.4 but update should be trivial (and possibly automatic)

RTAI is still supported, but in the short term building from source is
likely to be the most expedient way to get 2.9.5 on that platform.

Highlights:

 * Backport new hm2_modbus driver to 2.9 branch.
 * Fix probe contact bounce triggering error during decel phase

Abridged list of other updates.

 * gmoccapy: change text to icons of undo/redo buttons to fit window size
 * tests: save.1 test removed. It's been skipped for 19 years.
 * halui: on startup, set the first configured axis as 'is-selected'
instead of X
 * halui: Don't create 'halui.axis.'- pins for unconfigured axes
 * qtvcp versa probe: remember setting of auto skew/zero buttons we reopened
 * PyVCP test: result file formatting fixes (#3551)
 * stepconf -fix human input names in wrong order
 * Tests: Add a test for PyVCP - Specifically Issue #3538
 * Deprecate gantry.comp
 * Fix #3538 - "halparam" tag not working in PyVCP
 * tests: Add a test for spindle INI speed limits function
 * Fix a race; add a test to ensure the 'result' and 'stderr' files
are closed before continuing to run 'checkresult'.
 * Fix command-line directories acceptance by correct expansion.
 * Fix a race between setting the signal handlers and marking hal_ready().
 * Gladevcp: Update the .ui and .glade files in the sample configs to Gtk+3.0
 * clarify documentation on stat 'gcodes' and (spindle)'speed' attributes
 * Merge pull request #3460 from
Sigma1912/2.9-Fix-preview-update-not-respecting-active-wcs
 * Don't use  RS274NGC_STARTUP_CODE when updating the preview
 * Merge pull request #3454 from Sigma1912/2.9_Fix_issue_3447
 * Gmoccapy: Fix very large numbers for spindle speed and 'Vc' in the
gui when using G96
 * Gmoccapy: Fix 'spindle.0.speed-out' pins being reset to wrong value
when using G96
 * Split declaration/assignment with label because it is not accepted
by the compiler in Debian 10 and 11.
 * Fix invalid escape sequence warnings from halcompile and hal components.
 * Fix missing parity error definition
 * Merge pull request #3412 from BsAtHome/backport_2.9_fix_update-pktuart-v3
 * Update, fix and reorganize hostmot2 PktUART to support V3.
 * debian: Updated policy standard to 4.7.2
 * orient: Commit 79c0966 had an un-noticed effect on the behaviour of
M19 reported in issue #3389
 * ServoToGo: remove old weblinks that now redirect to a spam site
 * halui -fix spindle override using direct value.
 * gmoccapy: fix setting to disable "run from line"
 * halscope: set button left and right padding to 0 to allow smaller window size
 * docs: update halscope channel off function + update images
 * qtdragon_hd_vert -add a sample config for vertical layout.
 * qtvcp -qtdragon_hd_vert: add a vertical layout version
 * Merge pull request #3339 from NTULINUX/ntulinux/2.9-fixes
 * interp_o_word.cc: Insert almost-certainly-missing "breaks" addresses #3290
 * qtvcp -vismach config cleanup: gantry_5axis, millturn, vismach_fanuc_200f

The full changelog can be seen at
github.com/LinuxCNC/linuxcnc/blob/2.9/debian/changelog

As always, we couldn't do this without the contributions from the
community, so many thanks to:

Alec Ari
andronick83
Bertho Stultiens
CMorley
DauntlessAq
David
Hans Unzner
Petter Reinholdtsen
Rene Hopf
Sigma1912
Steffen Möller
 
  • scsmith1451
  • scsmith1451's Avatar
08 Sep 2025 12:59
Replied by scsmith1451 on topic Mapping key codes to specific jog rates

Mapping key codes to specific jog rates

Category: Advanced Configuration

Sorry to keep updating this thread.  After a lot of reading this morning, I think I have a workable solution by adding two buttons to my gvcp, one for min jog rate and one for max jog rate.

Given this solution, is there a way to logically press these buttons via a mapped keyboard key?
  • langdons
  • langdons's Avatar
08 Sep 2025 12:43

How to correctly connect stepper drivers to transformer.

Category: Milling Machines

The real problem with 57VAC is the drivers get a bit hot.

The driver for the Z axis has only 100V filter caps, the X and Y axes have 200V caps.

Current wiring scheme:
2 windings in parallel drive the Z axis driver, another winding doubles the voltage to feed the X and Y axes 57VAC.
  • langdons
  • langdons's Avatar
08 Sep 2025 12:32

How to correctly connect stepper drivers to transformer.

Category: Milling Machines

PCW, that's how it is now.

X and Y get 57VAC.

Z gets 28.5VAC


Tommy, you would opt for the one winding per driver isolated winding approach?
  • scsmith1451
  • scsmith1451's Avatar
08 Sep 2025 12:29
Replied by scsmith1451 on topic Mapping key codes to specific jog rates

Mapping key codes to specific jog rates

Category: Advanced Configuration

Andy,
I found the document written by John B that describes key remapping.  The file that holds the mappings is /usr/bin/axis. From what I can decipher There isn't a function to set the jog rate to a specific value only the ability to change the jog rate to one of the predefined values in the ini file.

I also found functions in the green screen UI and the qtvcp UI that can change jog speed. Would either of these functions work in the axis UI?

Also, in section 13.4.4 Functions of the documentation is found these functions:

set_jograte (float) - LinuxCNC has no internal concept of jog rate -each GUI has its own. This is not always convenient. This function allows one to set a jog rate for all objects connected to the signal jograte-changed. It defaults to 15. GSTAT.set_jog_rate(10) would set the jog rate to 10 machine-units-per-minute and emit the jograte-chasignal.

get_jograte() (Nothing) - x = GSTAT.get_jograte() would return GSTAT’s current internal jograte (float).

set_jograte_angular (float) -

get_jograte_angular (None) -

set_jog_increment_angular (float, string) -

get_jog_increment_angular (None) - LinuxCNC V2.9.4, 25 Jan 2025 1268 / 1297

set_jog_increments (float, string) -

get_jog_increments (None) -

These sound promising, but have no documentation for their use. Has anyone documented these functions?

Kind Regards
 
  • hellvetica
  • hellvetica
08 Sep 2025 11:34
Replied by hellvetica on topic task: main loop took 5.019013 seconds

task: main loop took 5.019013 seconds

Category: General LinuxCNC Questions

I don't know, it's the linuxcnc's output.
I just move the robot around when it happens.

However, I realized that every now and then one of my motors goes over its negative soft limit. I increased the soft limit and the issue seems to have stopped happening.
I still don't understand why that would cause the main loop to freeze for 5s.
  • Red_D85
  • Red_D85
08 Sep 2025 10:50
Lichuan Ethercat io was created by Red_D85

Lichuan Ethercat io

Category: Deutsch

Hallo zusammen
mich würde mal interessieren ob es jemand hin bekommen hat die io s der Lichuan Ethercat Servos einzubinden. Ich hatte bisher kein Erfolg weder bei den TLO57E (all-in-one) noch E57H (nur der Driver)
Die Suchfunktion erbrachte leider auch nicht die gewünschten treffer. 


grüsse
  • Kuzma30
  • Kuzma30
08 Sep 2025 10:24
Replied by Kuzma30 on topic AMSAMOTION IO module

AMSAMOTION IO module

Category: EtherCAT

I change name for IN OUT and add halType="bit"
<masters>
  <master idx="0">
    <slave idx="0" type="generic" vid="0x00000b95" pid="0x00001101" name="D1">
      <!--EC3A-IO1632-->
      <syncManager idx="0" dir="in"/>
      <syncManager idx="1" dir="out"/>
      <syncManager idx="2" dir="out">
        <pdo idx="1600">
          <!--DOOutputs process data mapping-->
          <pdoEntry idx="7000" subIdx="01" bitLen="16" halPin="EC3A-do" halType="bit"/>
        </pdo>
      </syncManager>
      <syncManager idx="3" dir="in">
        <pdo idx="1a00">
          <!--DIInputs process data mapping-->
          <pdoEntry idx="6000" subIdx="01" bitLen="16" halPin="EC3A-di" halType="bit"/>
        </pdo>
      </syncManager>
    </slave>
  </master>
</masters>

Now I want run ladder for this module (to make plc program).
cat ec3a.hal ec3a.ini
# Load real-time components
loadrt threads name1=servo-thread period1=1000000  # 1ms servo thread (matches XML appTimePeriod)

# Load EtherCAT driver with config XML
loadusr -W lcec_conf ec3a_io_hal.xml
loadrt lcec

# Load ClassicLadder (nogui mode, loading your project file)
#loadusr -W classicladder --nogui ec3a_ladder.clp

loadrt classicladder_rt
addf classicladder.0.refresh servo-thread

# Connect example I/O pins to ClassicLadder (map %I0-%I3 to inputs, %Q0-%Q3 to outputs)
# Expand to all 16 as needed
#net input-0 classicladder.0.in-00 <= lcec.0.0.EC3A-di.0
#net input-1 classicladder.0.in-01 <= lcec.0.0.EC3A-di.1
#net input-2 classicladder.0.in-02 <= lcec.0.0.EC3A-di.2
#net input-3 classicladder.0.in-03 <= lcec.0.0.EC3A-di.3

#net output-0 classicladder.0.out-00 => lcec.0.0.EC3A-do.0
#net output-1 classicladder.0.out-01 => lcec.0.0.EC3A-do.1
#net output-2 classicladder.0.out-02 => lcec.0.0.EC3A-do.2
#net output-3 classicladder.0.out-03 => lcec.0.0.EC3A-do.3[EMC]
# The version string for this INI file.
VERSION = 1.1

MACHINE = EtherCAT Machine
DEBUG = 1

[DISPLAY]
DISPLAY = axis
EDITOR = gedit

#PYVCP = pyvcp_panel.xml

# places the pyvcp panel at the bottom of the Axis window
PYVCP_POSITION = RIGHT

# Cycle time, in seconds, that display will sleep between polls
CYCLE_TIME =            0.100

# Path to help file
HELP_FILE =             doc/help.txt

# Initial display setting for position, RELATIVE or MACHINE
POSITION_OFFSET = RELATIVE
POSITION_FEEDBACK = ACTUAL
MAX_FEED_OVERRIDE = 1.2
# Prefix to be used
PROGRAM_PREFIX = /home/cnc/linuxcnc/nc_files
INTRO_GRAPHIC = linuxcnc.gif
INTRO_TIME = 0
INCREMENTS = 5mm 1mm .5mm .1mm .05mm .01mm .005mm

[FILTER]
PROGRAM_EXTENSION = .png,.gif,.jpg Greyscale Depth Image
PROGRAM_EXTENSION = .py Python Script
png = image-to-gcode
gif = image-to-gcode
jpg = image-to-gcode
py = python
nc = /usr/bin/axis

[RS274NGC]

PARAMETER_FILE = linuxcnc.var

#[EMCMOT]

#EMCMOT = motmod
#COMM_TIMEOUT = 1.0
#BASE_PERIOD =  0
#SERVO_PERIOD = 1000000

[TASK]
TASK = milltask
CYCLE_TIME = 0.005

[HAL]
HALFILE = ec3a.hal
#SHUTDOWN = shutdown.hal
#HALFILE = custom.hal
#POSTGUI_HALFILE = pyvcp_panel.hal
HALUI = halui

#[HALUI]

[KINS]
KINEMATICS = trivkins coordinates=
JOINTS = 0

[TRAJ]
COORDINATES =
LINEAR_UNITS = mm
ANGULAR_UNITS = degree
DEFAULT_LINEAR_VELOCITY = 1.0
MAX_LINEAR_VELOCITY = 1.0

I have not motion axies. I get such errors during start
linuxcnc ec3a.ini
LINUXCNC - 2.9.4
Machine configuration directory is '/home/cnc/Завантажене'
Machine configuration file is 'ec3a.ini'
Starting LinuxCNC...
[EMCIO] CYCLE_TIME not found in /home/cnc/Завантажене/ec3a.ini; using default 0.100000
halui: no [TRAJ]COORDINATES specified, enabling all axes
linuxcnc TPMOD=tpmod HOMEMOD=homemod EMCMOT=motmod
Note: Using POSIX realtime
Found file(REL): ./ec3a.hal
creating ladder-state
emcTrajSetJoints failing: joints=0
emcMotionInit: emcTrajInit failed
Missing [TRAJ]COORDINATES
Shutting down and cleaning up LinuxCNC...
USRMOT: ERROR: command timeout
HAL: ERROR: exit called before init
<commandline>:0: waitpid failed milltask inihal

<commandline>:0: milltask exited without becoming ready
Note: Using POSIX realtime
LinuxCNC terminated with an error.  You can find more information in the log:
    /home/cnc/linuxcnc_debug.txt
and
    /home/cnc/linuxcnc_print.txt
as well as in the output of the shell command 'dmesg' and in the terminal


cat /home/cnc/linuxcnc_debug.txt
Can not find -sec TRAJ -var COORDINATES -num 1
3767
3797
Stopping realtime threads
Unloading hal components
cnc@cnc:~/Завантажене$ cat /home/cnc/linuxcnc_print.txt
RUN_IN_PLACE=no
LINUXCNC_DIR=
LINUXCNC_BIN_DIR=/usr/bin
LINUXCNC_TCL_DIR=/usr/lib/tcltk/linuxcnc
LINUXCNC_SCRIPT_DIR=
LINUXCNC_RTLIB_DIR=/usr/lib/linuxcnc/modules
LINUXCNC_CONFIG_DIR=
LINUXCNC_LANG_DIR=/usr/lib/tcltk/linuxcnc/msgs
INIVAR=inivar
HALCMD=halcmd
LINUXCNC_EMCSH=/usr/bin/wish8.6
INIFILE=/home/cnc/Завантажене/ec3a.ini
VERSION=1.1
PARAMETER_FILE=linuxcnc.var
TPMOD=
HOMEMOD=
TASK=milltask
HALUI=halui
DISPLAY=axis
COORDINATES=
KINEMATICS=trivkins coordinates=
Starting LinuxCNC server program: linuxcncsvr
Loading Real Time OS, RTAPI, and HAL_LIB modules
Starting LinuxCNC IO program: io
Starting HAL User Interface program: halui
Starting TASK program: milltask
Starting DISPLAY program: axis
Removing HAL_LIB, RTAPI, and Real Time OS modules
Removing NML shared memory segments


Is it possible run linuxcnc without axies (or with simulated axies)?
  • Jonathan_H
  • Jonathan_H
08 Sep 2025 08:53 - 08 Sep 2025 08:54

probe_basic "Latest update requires config modification"

Category: QtPyVCP

Thanks for letting me know.

So the status page says "Action Required" when no action is actually required?

That's just silly, and monumentally unhelpful. I've wasted loads of time on this.
Displaying 2026 - 2040 out of 22570 results.
Time to create page: 0.650 seconds
Powered by Kunena Forum