Advanced Search

Bonjour , 
je voudrais mettre le freins sur l 'axe rotatif A, j'ai mis le fichier ini a jours mais je pense que j 'ai quelque chose qui manque , pouvez vous m 'aider?

I have expanded rio so that you can also create rpi5-gpio and parport configs.




it's not direct mixable with the FPGA configs

Hab mal rio aufgebohrt, so das man auch rpi5 gpio configs generieren kann

Hey and thanks for your reply!
I experimented with version 2.9.6 for a bit, but I can not find the fault that causes my problems. It just does not make sense that my config functions perfectly when running 2.9.4 and then goes broken after updating to 2.9.5/6.
I also noticed that calling MDI commands does not work. I have a command that zeroes my z-axis, which I can activate via a pyvcp button. This does not work anymore.
I am a bit relieved that I am not the only one having issues after updating, but I would love to find a solution to all of this!
As for now, I will stick to 2.9.4..

FOUND IT!

After 3 years since I bought the MPG, finally found the cause and solution of the issue of not being recognized on some (or all in my case) USB ports. It probably also solve if somebody got connection problems.

The main issue is that the XHC WHB04b receptor needs quite a lot of power (comparing to other USBs) to maintain a stable connection, and not all USB ports does provide such high current. So if the connection is not stable because the power issure, the kernel does not detect it. This can also happen on windows, but the windows specific drivers solve it on some cases. My computer is an industrial mini PC with external 12V PSU, so all USBs get their 5V from the main board. On desktop computers, front forts have usually lower power than rear ones, causing the issue.

There are a couple of really easy and cheap solutions:
-Use an USB HUB with external 5V power supply
-Use a Y cable (2 male, 1 female USB) either with both male USB connectors to the computer or the power only connector to a 5V PSU.

If your test machine has no external e-stop circuit you shouild simply connect the e-stop out signal to the estop in signal in your hal file. Something like this:

net estop-out <= iocontrol.0.user-enable-out
net estop-in => iocontrol.0.emc-enable-in

Then the e-stop buttons on the userinterface will work. and you will need to toggle them when starting Linuxcnc.

I don't think you would need to change anything in your servo drive. The only changes should be how it is seen and commanded inside Linuxcnc.

How is your servo currently commanded? I presume it is by step/dir commands in position mode? That would not have to change, you would simply have to change what signals are commanding the Mesa hardware stepgen so that they are commanded by the spindle commands instead of the joint that it is currently commanded by.

For weeks, I've been working on my own CNC machine and have made good progress, but I need help with some small details from experts.The machine is a MicroCarve MV3 with 3x 23-305-DS8A steppers in bipolar parallel mode, connected to a TB6600, which is connected to a Raspberry Pi 4. I don’t have a stop button yet.I’ve managed to wire the motors and Pi to test the axes with a Python script. I also created a minimalist INI and HAL file and started TkLinuxCNC. However, I can’t move the motors because the software shows an E-stop, and despite my efforts, I can’t get the machine to move.I access the Pi via VNC without a connected monitor. The image used is rpi-4-debian-bookworm-6.1.54-rt15-arm64-ext4-2023-11-17-1731.img.xz, updated to LinuxCNC 2.9.6.Friends, I need help. I’ve spent many hours on this and am close to getting the machine running.My test script works; HAL and INI files are attached.Thanks,
Dragan

I found a safety issue with the toggle2nist function in my gamepad.hal file.
if you e-stop while switching in pause, than switch on and start program again, pause will often not work.

---

this is a safety problem if you want to trust your pause function.

---

Therfore I use a special version of toggle2nist: forum.linuxcnc post 05 Oct 2025 18:50 #335873 special  toggle2nist.comp from user Aciera. You have to compile that in by hand.
www.forum.linuxcnc.org/24-hal-components...ton-at-the-same-time
With "pulse-length" parameter set to 50 the problem of the hanging pause is gone.
Therefore, the default toggle positioned before the toggle2nist component must be removed across all implementations to ensure correct toggle functionality.

also changed: e-stop with 13 to stop with 13
 
 

Try this small example config. That should make one axis work.
If it doesn't it is much easier to troubleshoot.
github.com/dbraun1981/hal-cia402/tree/main/example

 

Sounds like a user component.

There are some examples, for example the mitsub_vfd.py here github.com/LinuxCNC/linuxcnc/tree/master/src/hal/user_comps

have a look at the example config in the 'sim/axis/remap' folder:
github.com/LinuxCNC/linuxcnc/tree/master...emap/getting-started

Hi All,
I have been playing with this for days and have not cracked it. I was using AI for answers but every solution failed. I want to do the following. I have the python code sorted but getting LinuxCNC to call the python scripts seems to be the problem. The python script sets the Modbus TCP registers on the VFD.Spindle forward, pass the value 1 to my python script as an argSpindle reverse, pass the value 2 to my python script as an argStop spindle, pass the value 5 to my python script as an argSpindle speed, pass a value between 0 and 200 to a python script.can anyone offer a solution. Cheers
 

The last cool thing i remeber reading or putting any effort into was the gentleman from Proma on a Monokrom thread asking people to beta test his. Capactive THC Analog DC converter, I wonder how that went? And then ther was the makerspace that hacked together a usable motion control to build their fiber system from some clever manipulation of QTPlasma . other then finding a laser power source which will happen sooner then laater "fingers cross" 

Since I was last asking for assistance, I opted to switch over to a 7I96s board. I am having issues getting a cheap MPG pendant to jog axes in the Axis GUI. I have confirmed that the encoder works as well as the dead-man switch allows the signals I've designated as axis selectors and step values to trigger appropriately. I have seen forum posts about joint vs axis jog being toggled through the use of homing. (joint vs teleop) I utilize the Home all button to zero out the display before attempting to jog any axis. Using Halshow, I am able to see the joint-select-(a-d) and joint-incr-(a-d) trigger as well as the axis-selected-count value count up and down. I used the PNC wizard to setup the pinouts and didn't see "Axis select" as an option but did have "Joint select" available. I assume, based on what I've read about the 2.9 update that this wouldn't be an issue as I'm just using a standard 3 axis cartesian XYZ setup with possible expansion to XYZA once I have more confidence in using Linux CNC to actually run my machine.
It's probably something overly simple like linking joints to axes in a different way than PNC did by default or just a need to add a switch to convince the machine that it's been homed.
I've attached the Hal and Ini files for review.