Advanced Search

no, it would interfere with the mdi tab widgets which are already compressed for the gcode window there. I have a large machine vmc and have not had any issues with the back plotter size, but i could see a large format router perhaps being a bit of a problem. perhaps you could add a large full screen plotter in the user tab to suit your desired needs!

Not the same drives, pretty sure, this one is step/dir only, the above is analog only.

It's a bit of a mystery for me. A ftdi adapter could help to give some more information. Maybe firmware is missing or a driver is as module but should be built in. When you boot from the sd-card with the rt kernel, the nvme is still recognized? If so, can you show the output of blkid and of dmesg after boot and lsmod?
dmesg > dmesg-output.txt
lsmod > lsmod-output.txt
blkid > blkid-output.txt

did you completely uninstall the previous versions of qtpyvcp and probe basic? key error sounds like you may not be getting everything installed correctly or like you said may have some odd security conflicts with your network setup. i would completely reslve those and then report back if the problem perists.

When it gets to that error:
-remove the USB
-wait 15 seconds
-plug in the USB
-wait 15 seconds
-press or click retry

so what is the error message you get? and does the sim open?

Hello,

thank you... I also have an PDF oft the AC-Driver:
 

Martin

Hard to see on the PDF and my glasses, but those look like analog drives, not step/dir so 7i76E would not be the best option.
Can you take a picture of the drives where the pin naming is?

not had this experience and probe daily on my machine running the latest version. sounds like your machine is not properly setup. if your configuration files are setup correctly according to linuxcnc docs and you are seeing probe input activation in halshow than probe basic only needs to have the probing and tool setting parameters correctly entered in order to function as expected. i would start with you config files and get that sorted first!

I'm not sure how this can be done with the PncConf, it was what I tried first. The extended behavior of the pins in the wizard is set to Quad A/B these can't be selected as inputs for limit switches as far as I can tell. The g540x2 firmware is closest to what I need without having to do a custom version.

I mapped the inputs from the card manually to the same nets same as the parport config and confirmed they are activated by the switches.
net home-a <= [HMOT](CARD0).gpio.014.in_not
net home-x-y-z <= [HMOT](CARD0).gpio.013.in_not

and pass these through to what was generated by the PncConf but not sure where to go from here.

Even if I had the HAL setup incorrectly I expected it to try to move when I clicked home (I also tried individual axis too.)

I downloaded the “LinuxCNC 2.9.3  Debian 12 Bookworm PREEMPT-RT ISO ” from the downloads page on this site on a Windows laptop and used Rufus to create a bootable USB flash drive (using a new USB drive).

I put this USB in my industrial PC (IPC) and booted.  Chose the option to boot from the USB iso image and Debian loaded and I was able to run the Linux CNC software.

I then powered off the IPC and rebooted.  This time I chose the “Install” option to install Dorian and LinuxCNC on my SSD.  In this step: “Detect & Mount Installation Media”, I get this error (no matter how many times I retry):

”Your installation media couldn’t be mounted.” (see attached screenshot)

A question about this error:

- is this saying it can’t mount my USB drive? … or can’t mount my SSD?

And a couple of general install questions from a Linux newbie:

- how much space is needed on my SSD for installation of Dorian and LinuxCNC combined?  Note what I’m trying to install listed in previous paragraph).

- any recommendations on how my SSD should be partitioned for best performance?

Thanks for your help.

Ok, I have no idea what is going on here. The program attached above just bores a series of holes. I removed holes from the CAM and tested until it didn't drift after pressing stop. When it did I thought I found the issue, but then adding back another hole brought the issue back again. So then I thought it was a program size issue. So I made a program much bigger and it worked just fine. So then I split my original program into 2 and tested each. Both seemed fine.
Until just now. I had a part that was a little too deep, so I pressed stop and guess what? It plowed through my part before stopping. So that was a $2000 part before we machine it. Turned to trash because something is not right.

Does anybody have any thoughts?
I will point out again, this is both servos and stepper, so can't be an encoder issue. It does not loose its position - it knows where it is when it stops.
It mostly makes the same move every time if I stop in the same place in the program. But stopping in a different place will have a different move.

I am at my wits end here. I can't imagine this is a bug, but it really feels like it.Could it be a RAM issue somehow?

Hey Philip, someone had issues with the 5.4.279 kernel, which RTAI kernel did you decide to go with?

If you don't remember or not sure, run:

Arrrrgs, im an idiot. forgot to add read to the base thread...

addf hal_gpio.read base-thread

Hello everyone!. please help me to customize the inverter under linuxcnc. i've been struggling for 2 weeks. I’m facing an issue with connecting my Huanyang VFD to LinuxCNC via RS485. It works perfectly in Windows, but I’m having trouble in Linux. I’m using an RS485-RS232 converter through the COM port, and despite configuring everything, the spindle does not respond, and the program either hangs or there’s no communication with the VFD.System:

• LinuxCNC  2.9.3(Debian 12)
• RS485-RS232 converter
• Huanyang VFD configured for Modbus RTU
• What I’ve done so far:
• VFD Settings:
  • The following settings are configured on the VFD:
    • PD001 = 2 — control via Modbus.
    • PD002 = 2 — frequency via Modbus.
    • PD163 = 1 — device address.
    • PD164 = 9600 — baud rate.
    • PD165 = 3 — 8 data bits, no parity, 1 stop bit (8N1).
• Using

  hy_vfd

  : I tried running

  hy_vfd

  , but the program hangs when opening the port. Here’s the command:
   bash
  Копировать код

  hy_vfd -d /dev/ttyS0 --rate 9600 --parity none --stopbits 1 --target 1 -g

  Log output:
   bash
  Копировать код

  hy_vfd: device='/dev/ttyS0', baud=9600, bits=8, parity='none', stopbits=1, address=1, debug=1, PID=1586 Opening /dev/ttyS0 at 9600 bauds (none)

  The program hangs at the stage of opening the port.
• Checking the port via

  minicom

  : I connected to the port via

  minicom

  :
   bash
  Копировать код

  sudo minicom -D /dev/ttyS0

  The port settings are 9600 8N1, but in the terminal, commands do not send and there’s no response from the VFD. The port is not occupied:
   bash
  Копировать код

  lsof /dev/ttyS0

  The output is empty, meaning nothing is occupying the port.
• Testing with

  mbpoll

  : I also tried using

  mbpoll

  to send Modbus messages:
   bash
  Копировать код

  mbpoll -a 1 -b 9600 -P none -d 8 -s 1 -t 3 /dev/ttyS0

  I get the following error:
   objectivec
  Копировать код

  Read input register failed: Connection timed out

• What I’ve tried so far:
• Double-checked all wiring (Data+ and Data-).
• Tried changing the baud rate to 19200, but the result was the same.
• Tried different ports, including

  /dev/ttyUSB0

  (if using a USB-RS485 converter).
• Added my user to the

  dialout

  group:
   bash
  Копировать код

  sudo usermod -aG dialout $USER

• Attempted to reload HAL with

  halrun

  and manually load

  hy_vfd

  :
   bash
  Копировать код

  halrun loadusr -W hy_vfd -d /dev/ttyS0 --rate 9600 --parity none --stopbits 1 --target 1 -g

• Questions:
• What else can I do to debug the connection with the VFD?
• Could my RS485-RS232 converter be the problem? Could you recommend any converters that are known to work well with Linux?
• Are there any special settings for serial ports or Modbus in LinuxCNC that might be causing this issue?
• Thanks for your help! I’d appreciate any advice or recommendations.Additional Info:
• RS485-RS232 converter: Works perfectly in Windows Mach3.
• Linux: Debian 12 running LinuxCNC.