Advanced Search

Thank you for your quick response! I didn't think about it that way... So I don't have to worry about the pins not being created?
What could be the reason for some of the signals not being connected correctly? I mean, it was working on 2.9.4 after all. I managed to solve a lot of problems while setting up my machine, most of them thanks to posts on this forum. This issue i can not wrap my head around.
But I will do what you suggest and check the signals.

I did some research and it looks like something is wrong with installation. I have no problem of reinstalling it from scratch, if it makes sense.

If your config would need any of those pins it would not start up at all but fail with an error about a missing hal pin. The first place to troubleshoot your issue is to open the halshow tool and check the signals coming from the pendant.

Hey guys,
my config works as i want it on linuxcnc 2.9.4. After updating to 2.9.5 (or 2.9.6) it does not anymore. It mainly is the pendant that is not working as before. I use a china pendant (XHC WHB04B). Most buttons don't work anymore. For example when staring my machine, I hit the "reset" button. With version 2.9.4 I can home my machine after that. With 2.9.6 nothing happens. Control via GUI seems to work just fine.
I think the problem must be related to one of these, or maybe both points in the changelog:

• halui: on startup, set the first configured axis as ‘is-selected’ instead of X
• halui: Don’t create ‘halui.axis.’- pins for unconfigured axes

I looked at all created HAL pins under 2.9.4 and 2.9.6. I compared the output and found some missing pins under 2.9.6. I don't see why i would need these pins, but I figured it maybe where my error is? See the atteched pic for the missing pins.
I hope someone of the pros on this forum can help me. I don't know how to solve this on my own.
 

I've got this replay and I don't understand what is going on.

milos@debian:~$ sudo apt-get install r8168-dkms
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
r8168-dkms is already the newest version (8.048.03-3).
0 upgraded, 0 newly installed, 0 to remove and 6 not upgraded.
2 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n] y
Setting up initramfs-tools (0.142+deb12u1) ...
update-initramfs: deferring update (trigger activated)
Setting up r8168-dkms (8.048.03-3) ...
Removing old r8168-8.048.03 DKMS files...
Deleting module r8168-8.048.03 completely from the DKMS tree.
Loading new r8168-8.048.03 DKMS files...
Deprecated feature: REMAKE_INITRD (/usr/src/r8168-8.048.03/dkms.conf)
Building for 6.1.0-30-rt-amd64
Building initial module for 6.1.0-30-rt-amd64
Deprecated feature: REMAKE_INITRD (/var/lib/dkms/r8168/8.048.03/source/dkms.conf)
Error! Bad return status for module build on kernel: 6.1.0-30-rt-amd64 (x86_64)
Consult /var/lib/dkms/r8168/8.048.03/build/make.log for more information.
dpkg: error processing package r8168-dkms (--configure):
installed r8168-dkms package post-installation script subprocess returned error exit status 10
Processing triggers for initramfs-tools (0.142+deb12u1) ...
update-initramfs: Generating /boot/initrd.img-6.1.0-30-rt-amd64
raspi-firmware: missing /boot/firmware, did you forget to mount it?
run-parts: /etc/initramfs/post-update.d//z50-raspi-firmware exited with return code 1
dpkg: error processing package initramfs-tools (--configure):
installed initramfs-tools package post-installation script subprocess returned error exit status 1
Errors were encountered while processing:
r8168-dkms
initramfs-tools
E: Sub-process /usr/bin/dpkg returned an error code (1)

Hi Tommy,
I did it, and there was no Lan card reported. Even, if I tried to add new connection, didn't work.

  With the RPI4 being a viable contender albeit marginal for linuxcnc I thought I'd share some results i got from a stock RPI5 with a SD and with the addition of a nvme hat. I think they have knocked it out of the park with this one.The first one is with a nvme ssd hat added and the second one is with the standard SD card.  

Hello,

Sometimes try to tinker something that roughly corresponds to functionality, which I am looking for for Qtdragon.
I have little idea what I copied together. But it only runs in studio code how to explain the Linuxcnc, so I am light years away to understand it.
Here is the code snippet:

import cv2

cap = cv2.VideoCapture(0)
cap.set(cv2.CAP_PROP_FRAME_WIDTH, 1600)
cap.set(cv2.CAP_PROP_FRAME_HEIGHT, 1200)

while True:
ret_val, img = cap.read()
down_width = 800
down_height = 600
down_points = (down_width, down_height)
img = cv2.resize(img, down_points, interpolation= cv2.INTER_AREA)
cv2.imshow('my webcam', img)

if cv2.waitKey(1) == 27:
break # esc to quit
cap.release()
cv2.destroyAllWindows()

Best regards and have a nice weekend, Frank.
Translation errors come from Google.

Maybe it is in the homing file? Perhaps I can change the homing file to rehome rather than return to home if that it is indeed the case that it is not actually rehoming?

Ok, thanks

No jumpers need to be changed, and you and run the logic side of the 7I76E on 5V, but
since the field I/O side needs 12/24V, there usually is not much point.

Hello,I would like to operate my Mesa7i76e with an external 5V power supply. Unfortunately, I cannot find any information in the documentation about whether I need to change any jumpers and, if so, which ones. Can you help?Thank you.

thank you as always for your help.
I managed to reverse the encoder scale correctly
I must have something wrong with my closed loop signal
If I jog, on the first order; my pid.x.command is stuck and don't go back to 0. don't pay attention to the enc-count, this is before the *-1 scale

 

Добрый день.
Подключил пульт, в виртуальном станке axis все работает, но реальный постоянно отваливается при попытке передвигать маховиком с ошибкой joint 0 following error при движении осью Х и остальными соответственно.
Управление клавишами при этом происходит штатно.
В чем может быть проблема?

1. Z is not connected to the joint. Check the hal file how it is done for X and Y and do the same way for Z.

2. To enable DC
refClockSyncCycles= -1000 (or any other negative or positive number you like to use, not 0)
Use the line  <dcConf assignActivate="300" sync0Cycle="*1" sync0Shift="0"/>
and remove the watchog line. Normally don't need to specify that, there is a default watchdog of 100 ms
If the drive absolutely wants a watchdog statement, use the line <watchdog divider="2498" intervals="1000"/>