Advanced Search

It looks like the error is on my side. Lan adapter was disabled in BIOS. After enabling it, Lan connected to network using live installation.

Thank you guys for all your support and suggestions.

M

Yeah it is a bit tricky this one. The basic_cia402 device is a very capable device, but as usual with ethercat one need to know everything in advance.
The documentation github.com/linuxcnc-ethercat/linuxcnc-et...umentation/cia402.md outlines many details and mentions the modParams, with which one can enable and disable features of the drive.

The first error is about sdo 0x6060 and 0x607c, and in the doc one can see what they do.
Your drives don't have those features is my assumption, or not enabled. You need to get rid of all,those sdo download problems.

Anyway, what you should do is take the output of the command "lcec_configgen"
which will have a long list of modParams and select those you are going to use and your drive has.
Not so easy to enable/disable right but give it a go.

Also, errors from ethercat generally goes into syslog, you can see them with the command "sudo dmesg" the last maybe 20 lines are the importqnt.

bentiggin wrote:

Also, do you mean one 1Mohm/2w on each wire for a total of 2 resistors or two 1Mohm/2w on each wire for a total 4 resistors?
 

1 resistor on each wire, two in total.
So my advice on wiring on the rectifier wont work as this seems to be an SCR controlled rectifier, but there is hope, wire resistors to the big terminals on the picture on the left side, use a DVM to find the torch and clamp connections, clamp will be positive and torch will be negative but you have to remove the torch cap to check as the outer torch nozzle is not connected to any of those.
Are the high voltage/high frequency parts on the other side of that metal wall?

From your error report:But that pin is not in your attached hal nor xml file, so wrong files maybe ???

Hello,

I got some trouble - with my ATC
Problem: 
ATC wont align to the right pocket number
Homing works not correct

The ATC has one INI to find Pocket 1 
A servo drives the magazin but i cant use the index for homing because the in comes several times per magazin rev.

my questions:

1. is it possible with the carousel comp to drive these ATC ?
2. if the first answer is yes - can anyone help me finding the errors in my config?

Thanks, bassti

I installed EasyProbe on my gantry mill running AXIS. The probe signal works, the manual zero buttons and the G54 - G59.3 buttons work.
None of the probe motion buttons work.
Any ideas on how to troubleshoot this would be appreciated!
 

Hello,
I am new to LinuxCNC. I am trying to get a Festo CMMT-AS-C2-3A-EC-S1 to work via Ethercat with the CiA402. Unfortunately, I keep getting error messages when I start it up and have no idea what the problem could be.

Error message when starting up.

Debug file information:
Note: Using POSIX realtime
Failed to execute SDO upload: Input/output error
LCEC: slave 0.yaxis: Failed to execute SDO upload (0x6060:0x00, error -5, abort_code 00000000)
Failed to execute SDO download: Input/output error
LCEC: slave 0.zaxis: Failed to execute SDO download (0x607c:0x00, size 4, byte0=1, error -5, abort_code 00000000)
LinuxCNC Ethercat crashed with signal 11
-- STACK TRACE START
0    /usr/lib/linuxcnc/modules/lcec.so(+0xfc8c) [0x7ff70e4ddc8c]
1    /lib/x86_64-linux-gnu/libc.so.6(+0x3c050) [0x7ff70f2f7050]
2    /lib/x86_64-linux-gnu/libc.so.6(+0xa9d76) [0x7ff70f364d76]
3    /usr/lib/linuxcnc/modules/motmod.so(+0xd9b8) [0x7ff70e6309b8]
4    /usr/lib/linuxcnc/modules/motmod.so(+0xd5ad) [0x7ff70e6305ad]
5    /usr/lib/linuxcnc/modules/motmod.so(+0xd2c3) [0x7ff70e6302c3]
6    /usr/lib/linuxcnc/modules/motmod.so(+0x4a46) [0x7ff70e627a46]
7    /usr/bin/rtapi_app(rtapi_print_msg+0xbf) [0x558ee0026f2f]
8    /usr/lib/linuxcnc/modules/lcec.so(+0x11e94) [0x7ff70e4dfe94]
9    /usr/lib/linuxcnc/modules/lcec.so(+0x1316d) [0x7ff70e4e116d]
10    /usr/lib/linuxcnc/modules/lcec.so(rtapi_app_main+0x348) [0x7ff70e4dee76]
11    /usr/bin/rtapi_app(+0xbd67) [0x558ee0029d67]
12    /usr/bin/rtapi_app(+0xc6be) [0x558ee002a6be]
13    /usr/bin/rtapi_app(+0xccbc) [0x558ee002acbc]
14    /usr/bin/rtapi_app(+0x7a04) [0x558ee0025a04]
15    /usr/bin/rtapi_app(main+0x70f) [0x558ee002548f]
16    /lib/x86_64-linux-gnu/libc.so.6(+0x2724a) [0x7ff70f2e224a]
17    /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0x85) [0x7ff70f2e2305]
18    /usr/bin/rtapi_app(_start+0x21) [0x558ee00258f1]
-- STACK TRACE END
./cia402.hal:16: waitpid failed /usr/bin/rtapi_app lcec
./cia402.hal:16: /usr/bin/rtapi_app exited without becoming ready
./cia402.hal:16: insmod for lcec failed, returned -1
HAL: ERROR: pin 'lcec.0.3.out-01' not found
shutdown.hal:2: unlink failed
2648
Stopping realtime threads
Unloading hal components
Waited 3 seconds for master.  giving up.
Note: Using POSIX realtime
lcec: not loaded
<commandline>:0: exit value: 255
<commandline>:0: rmmod failed, returned -1
Note: Using POSIX realtime
motmod: not loaded
<commandline>:0: exit value: 255
<commandline>:0: rmmod failed, returned -1
Note: Using POSIX realtime
trivkins: not loaded
<commandline>:0: exit value: 255
<commandline>:0: rmmod failed, returned -1
Note: Using POSIX realtime
homemod: not loaded
<commandline>:0: exit value: 255
<commandline>:0: rmmod failed, returned -1
Note: Using POSIX realtime
tpmod: not loaded
<commandline>:0: exit value: 255
<commandline>:0: rmmod failed, returned -1
<commandline>:0: unloadrt failed
Note: Using POSIX realtime

I have attached my hal, ini, and xml files below. Does anyone have any idea what I have configured incorrectly?

Thank you.

forum.linuxcnc.org/9-installing-linuxcnc...e-official-amd46-iso

Hey guys
I have similar problem.
When hitting page up or page down button, the z axis starts moving until the end stops. And only stops moving if probe sensor is touched or esc button. 
Why does the probe screen behaves that way? 
is it possible to remove this function? 

I started to read the different py files, but didn't find a clue to this problem.

So I don't have to worry about the pins not being created?

No. Hal connections are created on startup when the hal files are read. If a hal pin used in any of your hal files was missing the config would not start at all. So your problem is not because of 'signals not being connected correctly'.
One thing to do is start your config from the terminal and check the output in the terminal. Another is to check the XHC WHB04B hal component using the halshow tool to confirm button press events are actually reaching your hal connections.

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)