Advanced Search

Thanks for sharing.

please post your config folder (compress and attach)

Your issue seems to come from your custom mcodes (M300, M500, M600).
Generally we don't want to have toolchange related stuff run on gcode load and the way to make sure it isn't is to check the 'task' parameter which returns 0 on load and 1 during actual gcode execution:

Hello everyone,
I have installed the Probe Basic Lathe version 2.9.4.

1. The simulation works fine, when I want to change a tool I get a popup window and can confirm the tool number - the tool number in each tab changes without error.

When I install it for the 7i96s configuration, I can open it - turn it on - the stepper motors work in MAN mode - referencing also works, but when I want to change the tool, nothing happens and the system freezes. 
I get the message: can`t issue mid unless machine is on, homed and idle.

2. When I want to use the macros in the conversation tab - change values and start - nothing happens.

How can I fix these problems?

Sounds like something for a custom homing component:
linuxcnc.org/docs/devel/html/man/man9/homecomp.9.html

Yes, indeed. However since the drops seem to be random, I am not sure if it is related.

The manual also states that no frequency measurement is possible if the counter is blocked by the gate, but that in this case the period can be measured regardless.

And further: If an encoder signal is only present at input A/A and the frequency/period is to be measured, the terminal must be set to “Enable FWD count” in CoE 0x8000:03 [} 155].

   

Nice! Thanks for sharing.

Hi all,
So my issue is as follows: I want to know if I can use NO with NC switches at the same time easily on the inputs to the MESA card.

My understanding (which could be wrong) is that for switching you should "chose your poison" regarding if you want to use NO or NC switching and wire Ground or Power to common to accommodate. I have 6 NO switches that are configured and operating well (i.e. when switched they close and activate), however, I now want to wire in a Touch off sensor that has a tool touch point (2 wire), and a Master E-stop (2 wire) which are NC and so therefore are always on until switched to open. I am currently running 24V ground to common. IN addition, will be running a probe in separately, and believe this has a 24V input NO to NC (So I think that should be Ok). 

So I guess my question is, do I just wire the same and select "Invert" for the switches that are NC and this is just sorted, or should I re-wire all switches to be NC and run power to common.?

What is the best approach?

Thanks all.

Try a different way

• buy and install a SSD drive
• Download and install Debian Trixie Netinst CD www.debian.org/devel/debian-installer/
• Be sure to select Mate or XFCE desktop 
• in a terminal type:
  • sudo apt update
  • sudo apt install linuxcnc-uspace linuxcnc-uspace-dev

The newer OS should provide better support  for your hardware

For additional tweaking, follow my guide
docs.google.com/document/d/1jeV_4VKzVmOI...diY/edit?usp=sharing

I'm not only a newby, but also a stupid one. You triggered me with asking for hal and ini file.
Initially I got an error on loadrt in my hal file. Then I ran the halcmd loadrt command (in a terminal without linuxcnc running) giving the specific error initially reported. Unfortunately these two errors had nothing to do with eachother. The error reported by the hal load was caused by my issue having no rights at the user/lib/linuxcnc/modules directory (so the modcompile went wrong).
After correcting the rights issue with the help of PCW, I executed the loadrt command without linuxcnc running.

So now loadrt mb25ioc32 ports=hm2_7i96s.0.pktuart.0 works fine and I see the pins with hall show.

At addf mb25ioc32 I now get the message:

corne@linuxcnc:~$ halcmd addf mb25ioc32 servo-thread
HAL: ERROR: function 'mb25ioc32' not found
<commandline>:0: addf failed


To be sure not making more stupid errors:
I run a out of the box config made with Linuxcnc stepconf
PC is connected to a 7i96s Mesa card with a nice pint (0.12 ms average)
Mesa card is on my desk and only connected with RJ45 and power.

Personally I wouldn't install to a USB drive. Far too many reasons to list.

One thing you have to be absolutely sure is that you are loading the boot loader to the correct USB device.

But if you do want to pursue it, the Debian forums would be the best place to look, as Linuxcnc is just plain old Debian bookworm with a real time kernel and the Linuxcnc app suite installed.

yes everything worked out! Thank you!

What PC?????????????
Realtek is the network card, and it will be enabled automatically if no boot devices are found.
In BIOS:
-disable secure boot
-disable TPM
-enable CSM
-enable compatibility mode
And as a general rule, don't look for answers on google anymore, it is useless mostly. Look at the coresponding forums, for Debian = Debian forums, for Mint = Mint forums, etc.

Tried every net solution for days to install linuxcnc, Debian, mint... nothing works. I did get as far as completing the installation successfully a few times, only to have my clean 1TB usb hard drive not be “found” on reboot. Also not showing up in bios “UEFI Boot sources” but the drive is first under bios setup “boot order” The live versions work but not any of the installs. Tried every possible bios setting and disk partition suggestions on the net with no luck. One odd thing that may help find the problem is that “UEFI: IPv4 Realtex PCIe FE family controller” and “UEFI: IPv6 Realtex PCIe FE family controller” keep showing up even after being disabled in “boot order” bios settings. I thought realtex was just for my old HP windows 8 audio system. Even after disabling everything but the USB drive in the boot order bios, the USB drive with the OS is not found. Since the internet came out and after all the OS systems I have installed, Linux OS seems impossible to install. Some Linux user must know what the problem is, but not any I found on the net offering solutions so far have worked.Correction… I misspelled “Realtex” it is “Realtek” 
 

Ethercat Update Sun, 16th Feb 2025

Ethercat installs and kernel modules build, some will build for running kernel, some build for 6.1.x kernel, but load with just a message about tainting kernel in logs. Just need someone with Ethercat hardware to confirm operation.