Advanced Search

Yes, regardless of whether you use sinking inputs (Input common = GND, switch common = V+)
or sourcing inputs (input common = V+, switch common = GND), the switch "on" state will be the
high state of the input pin in hal.

That means for things like limit and home switches which are active high in LinuxCNC, you must use
the plain inputs pins for NO contacts and the -not pins for NC contacts.

You would only need external resistors if you needed to mix sourcing and sinking input devices.

Note that sinking inputs are generally preferred as they allow mixing of input voltages so for example
you could use a 24V switch voltage along with 5V MPG signals.

Also, NC contacts are preferred for limit/home switches as a broken wire will cause a fault rather than a crash.
 

Well if it didn't, at least for the Debian install something has gone terribly wrong.
Without the installation of a boot loader, or where you want to install grub, the installation won't boot.
But some of this is starting to sound like a troll, based on your previous answers as to where you installed the boot loader. And the fact you never mentioned you tried installing to an internal hard drive to begin with.

You make it seem so simple. Thank you.

For something small it should be OK, but for anything bigger the belts would have to be way to long and to droopy and vibrate like crazy.
Personally, i have built over 20 Plasma and over 10 of 3D printers (mostly Voron 2.4), i would not even bother with it.

Hello,

I thought I could  give it a try to embed the GUI screen for hobbing. (I could not figure it out when I tried a while ago, but I wanted to give it another try)


I am refering to this page

wiki.linuxcnc.org/cgi-bin/wiki.pl?Hobbing

There are two links "hobbing.zip" and "screenshot.png", they do not work for me.

It would be great if someone could help me out.

YES, found in another thread: halcmd show.

I see my loaded component as mb25ioc32.00 (.00 at the end)

halcmd addf mb25ioc32.00 servo-thread > works.

Maybe someone can explain why the two zeros are added to a custom component and not to an existing components?

halcmd show results:
Exported Functions:
Owner   CodeAddr  Arg       FP   Users  Name
 00036  7f69c97ce908  559cf6208ae0  YES      1   hm2_7i96s.0.read
 00036  7f69c97ce891  559cf6208ae0  YES      0   hm2_7i96s.0.read-request
 00036  7f69c97ce749  559cf6208ae0  YES      1   hm2_7i96s.0.write
 00063  7f69c97af4e9  559cf620b800  YES      1   mb25ioc32.00
 00029  7f69c99143ad  00000000  YES      1   motion-command-handler
 00029  7f69c99149a0  00000000  YES      1   motion-controller
 00039  7f69c97b5240  7f69c9bc2020  YES      1   pid.s.do-pid-calcs
 00039  7f69c97b5240  7f69c9bc1b40  YES      1   pid.x.do-pid-calcs
 00039  7f69c97b5240  7f69c9bc1ce0  YES      1   pid.y.do-pid-calcs
 00039  7f69c97b5240  7f69c9bc1e80  YES      1   pid.z.do-pid-calcs

Realtime Threads:
     Period  FP     Name               (     Time, Max-Time )
    1000000  YES          servo-thread (   251880,  1209506 )
                  1 hm2_7i96s.0.read
                  2 motion-command-handler
                  3 motion-controller
                  4 pid.x.do-pid-calcs
                  5 pid.y.do-pid-calcs
                  6 pid.z.do-pid-calcs
                  7 pid.s.do-pid-calcs
                  8 hm2_7i96s.0.write
                  9 mb25ioc32.00

 

"At the end of the installation when it asks you where you want to install the boot loader" None of the installations that "installed successfully" asked anything about a "boot loader" or where I wanted it to be. I did run across some suggestions that it was left out of the installation repository somehow. I would think it was part of the ISO since it was required for a successful installation.
"The simplest way to install Linux is to a drive that is connected to a SATA or IDE port, or NVME if you have one" The first thing I tried was to install the ISO to the internal hard drive with the suggested partition, formatting, etc. set up for that install.

To be perfectly honest your issue is somewhat out the scope of the support found on the forum.
It is quite obvious you installed the remote software on the RPi, as I didn't build the image with any remote connection software other than SSH.
Your best bet would be to try the various Debian forums, the raspberry pi forums usually deal with issues with Raspios.
The RPi images are Debian Bookworm, with the kernel source from the RPi sources and Linuxcnc packages installed.
The images are not expected to be run via any remote desktop, hence the reason no remote desktop software is included, nor is it expected to be used as a general purpose OS.
What is your reason to run remotely ?
And please no double posting. My apologies I got confused by another user that was having the same issue.

John, tell me! Is it possible to somehow use buttons with the same functions on different forms? It’s just that when you create a button, for example, E-stop (its name is in objectName:estop_pb), when you create the same button on another form/page, its name will become objectName:estop_pb_2 and its function will not work

At the end of the installation when it asks you where you want to install the boot loader it should be installed onto the drive that Linux is installed to.

I believe your biggest hurdle is trying to install to a USB drive. The simplest way to install Linux is to a drive that is connected to a SATA or IDE port, or NVME if you have one.

Gents,

anyone considered core xy kinematics for plasma table? I can see it working perfectly in my 3D printer. Wondering if CoreXY kinematics is no problem in LinuxCNC. Two cheap servos, 20 or 25 mm wide HTD 3M belts well tensioned and Mesa control can keep moving mass pretty low and give decent accelerations for cutting thin sheets.

What ya think about it?
 

Hi,
When I try to log in with rdp from windows 11, it accepts user and pass, but after the image displays something pixelated as if there were 100 miniature desktop . Has anyone else experienced this? (rpi 4 4gb ). Everything else works ok so far..

Yes it can run it easily, the same as OPI5, I have tested it, only need to pin the ethernet irq to an isolated core, isolating only the last core is sufficient. I haven't tried to build from mainline without any patches. At least the dtb is there:
github.com/torvalds/linux/blob/master/ar...-orangepi-5-plus.dts

I'd recommend to build an image (or just the kernel) with Armbian since then some Rockchip specific patches will be included:
github.com/armbian/build/tree/main/patch...rchive/rockchip-6.13

And don't forget to build with mesa-vpu extension:
ENABLE_EXTENSIONS=mesa- vpu

excellent, glad to hear it!

fyi, your jog increments can be set in the ini file to avoid them being stacked on top of each other like that.  the stock increments are typically more than are needed for actual functional use.  I find 3-4 increments plus jog are sufficient for all situations.
 

Sorry, missed that last year when I installed Probe_Basic, I created a seperate machine folder.

Got it sorted now (after some debugging):