Advanced Search

Search Results (Searched for: )

  • Becksvill
  • Becksvill
04 Jan 2026 05:34

Dual PID loops and appropriate pins for feedback to the Trajectory Planner et al

Category: Advanced Configuration

hey guys i am also about to try scales plus ballscrews and encoders on a larger machine

just posting here to see if Nitram is still online at all?

hoping to make this work and then document it a bit for people and maybe post a config that is working etc

cheers

Andrew
  • bharath12
  • bharath12
04 Jan 2026 03:19

How do i purchase Mesa motion controllers in India?

Category: General LinuxCNC Questions

Is their any update, as I am too looking for a Mesa board
  • cmorley
  • cmorley
04 Jan 2026 01:28
Replied by cmorley on topic Auto Tool Probe - not callable

Auto Tool Probe - not callable

Category: Qtvcp

Can you show the probe parameters on the versa probe page please.
  • freylax
  • freylax
03 Jan 2026 22:56

LinuxCNC-RIO - RealtimeIO for LinuxCNC based on FPGA (ICE40 / ECP5)

Category: Computers and Hardware

Lieber Oliver,

vielen Dank, die option rpi5:true hat geholfen, jetzt funktioniert die Axis App!
Nun kann ich mich in die Konfiguration vertiefen.

sei lieb gegruesst,
Robert
  • tommylight
  • tommylight's Avatar
03 Jan 2026 22:55
Replied by tommylight on topic Mesa Configuration Tool

Mesa Configuration Tool

Category: Configuration Tools

Open a terminal and type:
sudo apt update
type the password and hit enter.
Now try to install MesaCT.
  • tommylight
  • tommylight's Avatar
03 Jan 2026 22:51
Replied by tommylight on topic Servos drives directly start turning

Servos drives directly start turning

Category: General LinuxCNC Questions

Or is it possible that the drifting is normal (approx. 3-5 rpm)?

Yes it is normal for analog drives when there is no controller in use.

As I understand it, the axis should stand still when the OUTPUT_OFFSET is set correct, even in the normal CNC GUI. Is that correct?

Not entirely:
-the axis should stand still if everything is configured properly
-OUTPUT_OFFSET is used for adjusting forward/reverse speed, very rarely used.
-
You have other issues with enable not wired properly and controlled by LinuxCNC, you can NOT continue to do anything before fixing that as it is dangerous to you and to the machine.
The link i posted above, go step by step and check things work as described, no skipping.
  • T_D
  • T_D
03 Jan 2026 22:25

Ich brauche Hilfe bei meiner Konfiguration

Category: General LinuxCNC Questions

Okay , thanks i want to use this board combined with a breakout board where the original flat cable sub d plugs are connected so i want to get +24v input signals and 24v output signals that means i just have to connect field a and b with the +24v from my power supply or do i have to connecht the two a and b with a bridge ?
  • PCW
  • PCW's Avatar
03 Jan 2026 22:15

Ich brauche Hilfe bei meiner Konfiguration

Category: General LinuxCNC Questions

The 7I84/7I84U has split field power supplies so you can have different
voltages (say 5V and 24V) on the inputs and outputs

You can normally ignore VIN as it powered by field power when W1 is in the default
left position.
  • PCW
  • PCW's Avatar
03 Jan 2026 21:37 - 03 Jan 2026 21:40
Replied by PCW on topic Servos drives directly start turning

Servos drives directly start turning

Category: General LinuxCNC Questions

Drifting usually indicates that you do not have the drive enables working.

The drives should be disabled until linuxCNC in running and in the machine-on state.
At this point, the encoder feedback and PID loop will prevent drifting.
If you get drift in the machine-on state that indicates a hal, encoder or PID tuning issue.

This is a safety issue, with analog drives, the drive enable is critical.


 
  • meister
  • meister
03 Jan 2026 21:35

LinuxCNC-RIO - RealtimeIO for LinuxCNC based on FPGA (ICE40 / ECP5)

Category: Computers and Hardware

Benutzt du einen RPI5 ?
dann trag mal bitte diese option mit ins json ein:

```
"boardcfg": "Olimex-ICE40HX8K-EVB",
"protocol": "SPI",
"rpi5": true,
"flashcmd": "/home/cnc/prog/olice40prog/spiflash.py -b rio.bin",
```
ansonsten bin ich etwas ratlos.

an welchem CS pin hast du das board ?

per default benutzt RIO CE0 an pin 8:
```
#define SPI_PIN_MOSI 10
#define SPI_PIN_MISO 9
#define SPI_PIN_CLK 11
#define SPI_PIN_CS 8
```
  • T_D
  • T_D
03 Jan 2026 21:29

Ich brauche Hilfe bei meiner Konfiguration

Category: General LinuxCNC Questions

Hello , i had figured out what the mistake was , i think i had taken bad cables because i took other cables and now the connection works and i have made some exercises for myself with a led and some playing with hal commands and now the 7i73 and the 7i84u is connected to the 7i74 per cat 6 cables and with the command " halcmd show pin" i am able to see 7i97t_7i73 and 7i97t_7i84u . Another question , why are there two vfield a and two vfield b screw terminals for the 7i84u for power supply and for what stands VIN ? I couldnt figure that out . Thanks for your answer.
  • JanCNC
  • JanCNC
03 Jan 2026 21:16
Replied by JanCNC on topic Servos drives directly start turning

Servos drives directly start turning

Category: General LinuxCNC Questions

Thanks for your reply. I've read through the entire forum thread, but I haven't found anything specifically related to my problem.

I suspect the OUTPUT_OFFSET value isn't working correctly. When I configure the axis in the pncconf wizard and adjust the offset value so the axis no longer drifts, everything works fine. However, as soon as I switch to the normal Linux CNC environment and enable the axes, they start drifting. I also tried disconnecting the analog signal connector from the 7i77 to see what effect it would have. There's no noticeable change. The axis drifts slightly faster, but that could be misleading.

Could it be that there are missing links in my .hal and .ini files? Or do I need to adjust other settings? I've also experimented with the calibration, increasing the P value or setting all values ​​to 0, but this hasn't helped. The axes are still drifting.

Or is it possible that the drifting is normal (approx. 3-5 rpm)? As I understand it, the axis should stand still when the OUTPUT_OFFSET is set correct, even in the normal CNC GUI. Is that correct?
  • Thllll
  • Thllll
03 Jan 2026 21:05
Replied by Thllll on topic Auto Tool Probe - not callable

Auto Tool Probe - not callable

Category: Qtvcp

Okay figured that out too, the "Tool Measure" needs to be ON in the probe tab. So now I am able to T# M6, it moves to tool sensor, I get the pop up, I change the tool, it starts to probe down...suspense... touches the tool sensor and I get the error below.

On a side note the tool sensor does work. I would say to exclude out the "probe tripped during non-probe move" because when using the offset commands "Go to Sensor" and "Tool Sensor" it works and I do not get that error, what is the difference?  
  • Thllll
  • Thllll
03 Jan 2026 20:46
Replied by Thllll on topic Auto Tool Probe - not callable

Auto Tool Probe - not callable

Category: Qtvcp

Made a solid jump in progress. The issue was the qt_dragon would appear to "freeze" thus looking at the terminal led me down this rabbit hole. The problem was the Message Dialog was not popping up (or maybe it was because you need to acknowelge it to do anything). Either way I am starting to think the "not callable" is normal?

After checking my .hal file and my postgui.hal file the problem was this wasy in my postgui.hal file, I was missing this in my postgui.hal file and I comment out all the unlinkp lines ande uncommented the toolchange signals.
net tool-prepare-loopback  iocontrol.0.tool-prepare  =>  iocontrol.0.tool-prepared

Attached is what I have as the lastest and I was able to somewhat make progress, it goes to tool senosr and the message dialog appears now! However after I accept I get the next error
Sat03 12:35: Auto Tool probe disabled


 
  • Thllll
  • Thllll
03 Jan 2026 20:36
Replied by Thllll on topic Auto Tool Probe - not callable

Auto Tool Probe - not callable

Category: Qtvcp

I corrected the program prefix, to be one and have the "~" at the start. Ran again I am getting the following from the terminal. The path is valid as well. The following is from the terminal
home/cnc/linuxcnc/configs/New_TAIG_dragon/New_TAIG_dragon.ini:92: executing 'import sys
sys.path.append("/home/cnc/linuxcnc/nc_files/examples/remap_lib/python-stdglue/python")'
PythonPlugin: Python  '3.13.5 (main, Jun 25 2025, 18:55:22) [GCC 14.2.0]'
is_callable(__init__) = FALSE
[QTvcp.QTVCP.QT_ISTAT][WARNING]  Path not valid in INI File [DISPLAY] PROGRAM_PREFIX section (qt_istat.py:96)
[QTvcp.QTVCP.QT_ISTAT][WARNING]  INI Parsing Error, No MAX_LINEAR_VELOCITY Entry in DISPLAY, Using: 5 (qt_istat.py:532)
[QTvcp.QTVCP.QT_ISTAT][WARNING]  INI Parsing Error, No MAX_SPINDLE_POWER Entry in DISPLAY, Using: 1500 (qt_istat.py:532)
is_callable(oword.on_abort) = FALSE
task: main loop took 0.119162 seconds
is_callable(oword.qt_auto_probe_tool) = FALSE

I compared to the sim .ini file and found that the "~" was not part of the program_prefix. Running it again without the "~", cleared the error
[QTvcp.QTVCP.QT_ISTAT][WARNING]  Path not valid in INI File [DISPLAY] PROGRAM_PREFIX section (qt_istat.py:96)

Still does not work but this was noticable
PythonPlugin: Python  '3.13.5 (main, Jun 25 2025, 18:55:22) [GCC 14.2.0]'
is_callable(__init__) = FALSE

Running the sim actually in debug shows the same thing.. 
/home/cnc/linuxcnc/configs/sim.qtdragon.qtdragon_tool_probe/qtdragon_auto_tool_probe.ini:120: executing 'import sys
sys.path.append("/home/cnc/linuxcnc/nc_files/examples/remap_lib/python-stdglue/python")'
PythonPlugin: Python  '3.13.5 (main, Jun 25 2025, 18:55:22) [GCC 14.2.0]'
/home/cnc/linuxcnc/configs/sim.qtdragon.qtdragon_tool_probe/qtdragon_auto_tool_probe.ini:120: executing 'import sys
sys.path.append("/home/cnc/linuxcnc/nc_files/examples/remap_lib/python-stdglue/python")'
PythonPlugin: Python  '3.13.5 (main, Jun 25 2025, 18:55:22) [GCC 14.2.0]'
is_callable(__init__) = FALSE
Unexpected realtime delay on task 0 with period 100000
This Message will only display once per session.
Run the Latency Test and resolve before continuing.

Unexpected realtime delay on task 0 with period 100000
This Message will only display once per session.
Run the Latency Test and resolve before continuing.
is_callable(oword.on_abort) = FALSE
is_callable(oword.qt_auto_probe_tool) = FALSE
tool_result(id=2, xoffset=0.0, yoffset=0.0, zoffset=0.1, aoffset=0.0, boffset=0.0, coffset=0.0, uoffset=0.0, voffset=0.0, woffset=0.0, diameter=0.0625, frontangle=0.0, backangle=0.0, orientation=0)




 
Displaying 301 - 315 out of 20294 results.
Time to create page: 0.198 seconds
Powered by Kunena Forum