Advanced Search

Thanks rodw.

Turns out that the error was misreporting the line number. When I parameterized the subroutine I inadvertently left a stray > on line 33.

Here's the result of halshow after following your instructions. Is my drive perhaps not defined correctly or something like that? I don't seem to have any pins like your screen shot shows.

Thanks for looking into this issue.

I opened the attached file I ran the following commands without encountering any issues:

G10 L2 P1 X0 Y0 Z0
G10 L2 P2 X0 Y0 Z0
G10 L2 P3 X0 Y0 Z0

However as soon as I set the value of G56 using the probing function highlighted below the error appears when the probing has finished.

 

This seems to be related some type of state that gets set during the probing of G56. Because if I probe G56 with no file open and then open the attached file it triggers the error immediately without any further input required.

 

hallo, danke für die info. cmos batterie vor 14 tagen getauscht.
festplatte fest..

auf dem foto ist ein warndreieck auf der festplatte zu sehen,
kann ein mbr fehler sein.

karlhe

epineh wrote:

Awesome, those new tabs look great, the invert button on the scale is a nice touch. 
Russell.

I'll second that.

Top work

Danke, habs hinbekommen!

Die Fräse fährt jetzt wie sie soll, beim Verfahren mit den Cursor-Tasten hört man allerdings immer leichte Aussetzer.
Ich nutze eine Logitech Funktastatur, deren Empfänger immer schon etwas heikel war.

Ich werde am Wochenende mal eine meiner größeren G-Code Dateien abfahren lassen (mit Stift statt Fräser), und aufpassen ob das im Normalbetrieb überhaupt auftritt.

Im Anhang noch die Letztversion der Config-Dateien.

Hallo!

Ich hatte das letztens auch, da war es eine schlechte Steckverbindung der Festplatte.

Wird die Platte im Bios denn erkannt, und stimmt die Boot-Reihenfolge im Bios?
Gibt es eine Fehlermeldung?
Eine leere Bios Batterie kann sowas auch auslösen.

A long time since I played with this. I think you should use [ ] symbols. But check the docs

Good luck with this. There is no reason why you can't run a 1.024 Ms servo thread if that's important to remain  synced.. Its just a hal file setting...

Awesome, those new tabs look great, the invert button on the scale is a nice touch. 
Russell.

Hello,
i just try to get my Handwheel to work. Therefore i use these YT Video

At the moment i need to compile i get these error message.

cnc@cnc:~/linuxcnc-dev/src$ ./configure --with-realtime=uspace
checking for c++... c++
checking whether the C++ compiler works... yes
checking for C++ compiler default output file name... a.out
checking for suffix of executables...
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether the compiler supports GNU C++... yes
checking whether c++ accepts -g... yes
checking for c++ option to enable C++11 features... none needed
checking for a BSD-compatible install... /usr/bin/install -c
checking whether c++ supports C++20 features by default... no
checking whether c++ supports C++20 features with -std=gnu++20... yes
checking build toplevel... /home/cnc/linuxcnc-dev
checking installation prefix... run in place
checking for grep... /usr/bin/grep
checking for pkg-config... /usr/bin/pkg-config
checking pkg-config is at least version 0.9.0... yes
checking for gcc... gcc
checking whether the compiler supports GNU C... yes
checking whether gcc accepts -g... yes
checking for gcc option to enable C11 features... none needed
checking for stdio.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for strings.h... yes
checking for sys/stat.h... yes
checking for sys/types.h... yes
checking for unistd.h... yes
checking for rpc/rpc.h... no
checking for get_myaddress in -ltirpc... yes
checking for rpc/rpc.h... yes
checking for rtai-config... none
checking for xeno-config... none
checking for realtime API(s) to use... uspace
checking whether to enable userspace PCI access... yes
checking for libudev... yes - version 252
checking for cc version... not specified
checking whether the compiler supports GNU C... (cached) yes
checking whether gcc accepts -g... (cached) yes
checking for gcc option to enable C11 features... (cached) none needed
checking how to run the C preprocessor... gcc -E
checking for usability of linux/hidraw.h... yes
checking for usability of rpc/rpc.h... yes
checking for libmodbus3... yes - version 3.1.6
checking for libusb-1.0... yes
checking for libgpiod < 2.0.0... no
configure: WARNING: Could not find libgpiod, not building hal_gpio
checking for module installation directory... configuring for run-in-place
/home/cnc/linuxcnc-dev/rtlib
checking for glib... yes - 2.74.6
checking for GTK 3.22.4 or above... yes - 3.24.38
checking whether make sets $(MAKE)... yes
checking for ranlib... ranlib
checking for ar... /usr/bin/ar
checking for install... /usr/bin/install -c
checking for sed... /usr/bin/sed
checking for ps... /usr/bin/ps
checking for kill... /usr/bin/kill
checking for whoami... /usr/bin/whoami
checking for awk... /usr/bin/awk
checking for pidof... /usr/bin/pidof
checking for ipcs... /usr/bin/ipcs
checking for fuser... /usr/bin/fuser
checking for yapps... no
checking for yapps2... no
configure: error: yapps/yapps2 and not found

Iḿ a 2 two weeks linux newbie... so not much experience and google doesn´t really help me. 

Awesome work!

adding some images and tabs:

images for some plugins:


new Tab for all axis configurations in one screen (incl. calculator)


new Tab for the ini


and one for some basic settings


 

Here is a way to check pin names without modifying the hal file.
Use the halrun command (linuxcnc off), load lcec and lcec_config. The start halshow in another window and explore names.

debian@plasma:~/linuxcnc/configs/QtPlasma$ halrun
halcmd: loadusr -W lcec_conf ethercat-conf.xml
halcmd: loadrt lcec
Note: Using POSIX realtime
halcmd:

 

with just one drive, the cia402 is probably numbered 0. Your 3. is coming from these lines in your hal. If in doubt, comment them all out so LinuxCNC ipens, then use halshow to work out the correct pin names# ethercat to cia402 driver
net x-statusword lcec.0.3.cia-statusword => cia402.0.statusword
net x-opmode-display lcec.0.3.opmode-display => cia402.0.opmode-display
net x-drv-act-pos lcec.0.3.actual-position => cia402.0.drv-actual-position

# cia402 driver to ethercat
net x-controlword cia402.0.controlword => lcec.0.3.cia-controlword
net x-modes-of-operation cia402.0.opmode => lcec.0.3.opmode
net x-drv-target-pos cia402.0.drv-target-position => lcec.0.3.target-position