Advanced Search

Search Results (Searched for: )

  • tylernyberg
  • tylernyberg
25 Mar 2025 19:36
Replied by tylernyberg on topic New Computer - Error Launching

New Computer - Error Launching

Category: Advanced Configuration

I removed GladeVCP from ini and it boots. The spindle works, but xyz joints are not working. Will not jog. Homing does not fix anything, the values move in LCNC, but no physical machine movement. I get an error for:
cannot jog joint 1 because home_sequence is synchronized (-3)

Joint 0 is X
Joints 1 and 2 are my Y axis that are synced.
Joint 3 is Z
  • PCW
  • PCW's Avatar
25 Mar 2025 19:30

correspondence of unused i/o pins to physical connector location?

Category: PnCConf Wizard

For example on TB2, if you set num_stepgens to 4, the TB2 step04/dir04 pins become
available as GPIO, but they only work as outputs because they have a buffer with its inputs
from the FPGA and outputs on TB2.
  • faeluke
  • faeluke's Avatar
25 Mar 2025 19:09
Replied by faeluke on topic Raspberry Pi 4 and bad latency.. SOLUTIONS?

Raspberry Pi 4 and bad latency.. SOLUTIONS?

Category: Installing LinuxCNC

Well, that was easy! Thank you sirl
I think I'll make some chips!
  • tuxcnc
  • tuxcnc
25 Mar 2025 18:52

Remora - ethernet NVEM / EC300 / EC500 cnc board

Category: Computers and Hardware

External e-stop (fault) on EC500 input.
loadrt estop_latch
addf estop-latch.0 servo-thread
net estop-loopout       iocontrol.0.emc-enable-in       <= estop-latch.0.ok-out
net user-enable-out     iocontrol.0.user-enable-out     => remora.enable
net estop-loopin        remora.status                   => estop-latch.0.ok-in => estop-latch.0.reset
net estop-reset         iocontrol.0.user-request-enable => remora.reset
net remote-estp         estop-latch.0.fault-in          <= remora.input.02.not
 
  • Grotius
  • Grotius's Avatar
25 Mar 2025 18:15 - 25 Mar 2025 18:21
Replied by Grotius on topic scurve trajectory planner

scurve trajectory planner

Category: General LinuxCNC Questions

Hello,

It's solved.
Git is updated.

@Evgen can replace or overwrite the tp_scurve.c from codeberg.
Then do a recompile for cmake : ./buid_cmake

The problem:
    In control.c Line 1867 it looks for 2 types :
    EMC_MOTION_TYPE_FEED
    EMC_MOTION_TYPE_ARC

Clothoid motion was giving no type.
Then the clothoid motion is now set to type EMC_MOTION_TYPE_FEED in the planner.

Now the motion.feed-value flippering is not there anymore.
  • Aciera
  • Aciera's Avatar
25 Mar 2025 17:43
Replied by Aciera on topic scurve trajectory planner

scurve trajectory planner

Category: General LinuxCNC Questions

What is using the hal pin : motion.feed-mm-per-second for example?
 

 
 

from:
linuxcnc.org/docs/devel/html/man/man9/motion.9.html
  • tommylight
  • tommylight's Avatar
25 Mar 2025 17:42
Replied by tommylight on topic Raspberry Pi 4 and bad latency.. SOLUTIONS?

Raspberry Pi 4 and bad latency.. SOLUTIONS?

Category: Installing LinuxCNC

Set the servo period in the ini file to 2000000 (2 million) and set the P value for each joint/axis to 500.
  • faeluke
  • faeluke's Avatar
25 Mar 2025 17:39
Replied by faeluke on topic Raspberry Pi 4 and bad latency.. SOLUTIONS?

Raspberry Pi 4 and bad latency.. SOLUTIONS?

Category: Installing LinuxCNC

So... 

What if LinuxCNC complains while starting...?

When running the latency test Tommy suggested, I saw a similar graph.

I migrated my working configuration to the PI4.. Then, I was visited by the dreaded latency complaint. 

Everything appears to work. I am running a Mesa ethernet card. What are the steps to debug and rectify the situation on a PI? 

Frank.hal attached. Do you need to see any more files?


 
  • Aciera
  • Aciera's Avatar
25 Mar 2025 17:37
  • Grotius
  • Grotius's Avatar
25 Mar 2025 17:35 - 25 Mar 2025 17:39
Replied by Grotius on topic scurve trajectory planner

scurve trajectory planner

Category: General LinuxCNC Questions

Hi,

When i run Posix non-realtime or Posix realtime scurve planner, i both get the same results as Evgen is telling us.

The hal pins that are flippering, blinking :
  • motion.feed-mm-per-second
  • motion.feed-mm-per-minute
  • motion.feed-inches-per-second
  • motion.feed-inches-per-minute
  • motion.feed-upm

I didn't look any further.

What is using the hal pin :  motion.feed-mm-per-second for example?
I personally never used it, that's maybe i didn't noticed this behaviour.

@Pcw, link to gcode he posted before:
forum.linuxcnc.org/media/kunena/attachme...i3DRough_target2.ngc
  • PCW
  • PCW's Avatar
25 Mar 2025 17:32
Replied by PCW on topic New Computer - Error Launching

New Computer - Error Launching

Category: Advanced Configuration

All the hardware seems to be detected OK and the error
is gladevcp related.

Does the parallel port configuration have this same error?
and if not, you might compare the hal files for lines involving gladevcp
 
  • PCW
  • PCW's Avatar
25 Mar 2025 17:22
Replied by PCW on topic scurve trajectory planner

scurve trajectory planner

Category: General LinuxCNC Questions

Can you post the gcode?
 
  • Evgen
  • Evgen
25 Mar 2025 17:08
Replied by Evgen on topic scurve trajectory planner

scurve trajectory planner

Category: General LinuxCNC Questions

Yes,I'm sure. Firstly I got this problem on real machine with MESA card.
  • PCW
  • PCW's Avatar
25 Mar 2025 16:17
Replied by PCW on topic scurve trajectory planner

scurve trajectory planner

Category: General LinuxCNC Questions

Are you sure that is not just an artifact of running a non-realtime (SIM) installation?
  • tylernyberg
  • tylernyberg
25 Mar 2025 16:10
Replied by tylernyberg on topic New Computer - Error Launching

New Computer - Error Launching

Category: Advanced Configuration

The test 4x4 file is the one that was working on the other computer, which is why I tried that one.

When I use the test-4x4_1742871679.ini it launchs with an error:

waiting for component 'inihal' to become ready.....
a configuration error is preventing LCNC from starting
....HAL:ERROR exit called before init
<commandline>:0: waitpid failed milltask inihal

it also lists 3x:
USRMOT: ERROR: command timeout
emcMotionInit: emcTrajInit failed


I have another file attached below that I tried called Mesa_4x4, which compared looks the same config. This has an error related to these two lines when I use it:
setp hm2_5i25.0.dpll.01.timer-us -50
setp hm2_5i25.0.stepgen.timer-number 1

if I remove these lines from the hal file I can hear the motors click on LCNC boot, but then get the error for spindle speed GladeVCP

Print file information:
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
LINUXCNC - 2.9.4
Machine configuration directory is '/home/bep/linuxcnc/configs/Mesa_4x4'
Machine configuration file is 'Mesa_4x4.ini'
INIFILE=/home/bep/linuxcnc/configs/Mesa_4x4/Mesa_4x4.ini
VERSION=1.1
PARAMETER_FILE=linuxcnc.var
TPMOD=
HOMEMOD=
TASK=milltask
HALUI=halui
DISPLAY=axis
COORDINATES=XYYZ
KINEMATICS=trivkins coordinates=XYYZ kinstype=BOTH
Starting LinuxCNC...
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
linuxcnc TPMOD=tpmod HOMEMOD=homemod EMCMOT=motmod
Found file(REL): ./Mesa_4x4.hal
Found file(REL): ./custom.hal
Starting TASK program: milltask
Starting DISPLAY program: axis
gtk-builder-error-quark: gvcp-panel.ui:72:38 Invalid property: HAL_Table.n_rows (11)
Warning: Forward kinematics must handle duplicate coordinate letters:yy

Embeded tab command "halcmd loadusr -Wn gladevcp gladevcp -c gladevcp -d -x 75497615 -H gvcp_call_list.hal gvcp-panel.ui" exited with error: 1
Shutting down and cleaning up LinuxCNC...
Running HAL shutdown script
task: 173 cycles, min=0.000004, max=0.011021, avg=0.008873, 0 latency excursions (> 10x expected cycle time of 0.010000s)

identityKinematicsSetup: coordinates:XYYZ
   Joint 0 ==> Axis X
   Joint 1 ==> Axis Y
   Joint 2 ==> Axis Y
   Joint 3 ==> Axis Z

hm2: loading Mesa HostMot2 driver version 0.15
hm2_pci: loading Mesa AnyIO HostMot2 driver version 0.7
hm2_pci: discovered 5i25 at 0000:10:00.0
hm2/hm2_5i25.0: Low Level init 0.15
hm2/hm2_5i25.0: Smart Serial Firmware Version 43
Board hm2_5i25.0.7i76.0.0 Hardware Mode 0 = standard
Board hm2_5i25.0.7i76.0.0 Software Mode 0 = io_spin
Board hm2_5i25.0.7i76.0.0 Software Mode 1 = io_ana_spin
Board hm2_5i25.0.7i76.0.0 Software Mode 2 = io_enc_ana_spin_fv
hm2/hm2_5i25.0: 34 I/O Pins used:
hm2/hm2_5i25.0:     IO Pin 000 (P3-01): StepGen #0, pin Direction (Output)
hm2/hm2_5i25.0:     IO Pin 001 (P3-14): StepGen #0, pin Step (Output)
hm2/hm2_5i25.0:     IO Pin 002 (P3-02): StepGen #1, pin Direction (Output)
hm2/hm2_5i25.0:     IO Pin 003 (P3-15): StepGen #1, pin Step (Output)
hm2/hm2_5i25.0:     IO Pin 004 (P3-03): StepGen #2, pin Direction (Output)
hm2/hm2_5i25.0:     IO Pin 005 (P3-16): StepGen #2, pin Step (Output)
hm2/hm2_5i25.0:     IO Pin 006 (P3-04): StepGen #3, pin Direction (Output)
hm2/hm2_5i25.0:     IO Pin 007 (P3-17): StepGen #3, pin Step (Output)
hm2/hm2_5i25.0:     IO Pin 008 (P3-05): StepGen #4, pin Direction (Output)
hm2/hm2_5i25.0:     IO Pin 009 (P3-06): StepGen #4, pin Step (Output)
hm2/hm2_5i25.0:     IO Pin 010 (P3-07): Smart Serial Interface #0, pin tx0 (Output)
hm2/hm2_5i25.0:     IO Pin 011 (P3-08): Smart Serial Interface #0, pin rx0 (Input)
hm2/hm2_5i25.0:     IO Pin 012 (P3-09): IOPort
hm2/hm2_5i25.0:     IO Pin 013 (P3-10): IOPort
hm2/hm2_5i25.0:     IO Pin 014 (P3-11): Encoder #0, pin Index (Input)
hm2/hm2_5i25.0:     IO Pin 015 (P3-12): Encoder #0, pin B (Input)
hm2/hm2_5i25.0:     IO Pin 016 (P3-13): Encoder #0, pin A (Input)
hm2/hm2_5i25.0:     IO Pin 017 (P2-01): IOPort
hm2/hm2_5i25.0:     IO Pin 018 (P2-14): IOPort
hm2/hm2_5i25.0:     IO Pin 019 (P2-02): IOPort
hm2/hm2_5i25.0:     IO Pin 020 (P2-15): IOPort
hm2/hm2_5i25.0:     IO Pin 021 (P2-03): IOPort
hm2/hm2_5i25.0:     IO Pin 022 (P2-16): IOPort
hm2/hm2_5i25.0:     IO Pin 023 (P2-04): IOPort
hm2/hm2_5i25.0:     IO Pin 024 (P2-17): IOPort
hm2/hm2_5i25.0:     IO Pin 025 (P2-05): IOPort
hm2/hm2_5i25.0:     IO Pin 026 (P2-06): IOPort
hm2/hm2_5i25.0:     IO Pin 027 (P2-07): IOPort
hm2/hm2_5i25.0:     IO Pin 028 (P2-08): IOPort
hm2/hm2_5i25.0:     IO Pin 029 (P2-09): IOPort
hm2/hm2_5i25.0:     IO Pin 030 (P2-10): IOPort
hm2/hm2_5i25.0:     IO Pin 031 (P2-11): IOPort
hm2/hm2_5i25.0:     IO Pin 032 (P2-12): IOPort
hm2/hm2_5i25.0:     IO Pin 033 (P2-13): IOPort
hm2/hm2_5i25.0: registered
hm2_5i25.0: initialized AnyIO board at 0000:10:00.0
hm2_5i25.0: dropping AnyIO board at 0000:10:00.0
hm2/hm2_5i25.0: unregistered
hm2_pci: driver unloaded
hm2: unloading
Removing HAL_LIB, RTAPI, and Real Time OS modules
Removing NML shared memory segments

Debug file information:
Note: Using POSIX realtime
note: MAXV     max: 3.333 units/sec 200.000 units/min
note: LJOG     max: 3.333 units/sec 200.000 units/min
note: LJOG default: 2.000 units/sec 120.000 units/min
note: jog_order='XYZ'
note: jog_invert=set()
[GladeVCP][[36mINFO[0m]  Logging to: [33m/home/bep/gladevcp.log[0m (logger.py:106)
[GladeVCP.QTVCP.QT_ISTAT][[33mWARNING[0m]  INI Parsing Error, No DEFAULT_SPINDLE_0_SPEED Entry in DISPLAY, Using: 200 (qt_istat.py:532)
[GladeVCP.QTVCP.QT_ISTAT][[33mWARNING[0m]  INI Parsing Error, No MIN_SPINDLE_0_SPEED Entry in DISPLAY, Using: 100 (qt_istat.py:532)
[GladeVCP.QTVCP.QT_ISTAT][[33mWARNING[0m]  INI Parsing Error, No MAX_SPINDLE_0_SPEED Entry in DISPLAY, Using: 2500 (qt_istat.py:532)
[GladeVCP.QTVCP.QT_ISTAT][[33mWARNING[0m]  INI Parsing Error, No MAX_SPINDLE_0_OVERRIDE Entry in DISPLAY, Using: 1 (qt_istat.py:532)
[GladeVCP.QTVCP.QT_ISTAT][[33mWARNING[0m]  INI Parsing Error, No MIN_SPINDLE_0_OVERRIDE Entry in DISPLAY, Using: 0.5 (qt_istat.py:532)
[GladeVCP][[34mDEBUG[0m]  **** GLADE VCP INFO:    Not a builder project, trying to load as a lib glade project (gladevcp:205)
**** GLADE VCP ERROR:    With xml file: gvcp-panel.ui : 'gi.repository.Gtk' object has no attribute 'glade'
<commandline>:0: gladevcp exited without becoming ready
5919
5954
Stopping realtime threads
Unloading hal components
RTAPI_PCI: Unmapped 65536 bytes at 0x7f0f704a9000
Note: Using POSIX realtime
Displaying 16876 - 16890 out of 18505 results.
Time to create page: 0.631 seconds
Powered by Kunena Forum