Advanced Search

Ich bin im programm rumgefahren sodas es verschwindet es ist in der konsole nichts mehr passiert oder habe ich etwas falsch gemacht?

Ah so, nein da hast nix falsch gemacht. Versuchs mal mit den Vorschlägen von phil.

That is an isel IMC4 controller board which has the motor drives integrated. If you want to use LinuxCNC you would have to replace this with standalone motor drives and some simple break out board. What kind of motors does the machine use (likely steppers but maybe DC)?

RUN_IN_PLACE=no
LINUXCNC_DIR=
LINUXCNC_BIN_DIR=/usr/bin
LINUXCNC_TCL_DIR=/usr/lib/tcltk/linuxcnc
LINUXCNC_SCRIPT_DIR=
LINUXCNC_RTLIB_DIR=/usr/lib/linuxcnc/modules
LINUXCNC_CONFIG_DIR=
LINUXCNC_LANG_DIR=/usr/lib/tcltk/linuxcnc/msgs
INIVAR=inivar
HALCMD=halcmd
LINUXCNC_EMCSH=/usr/bin/wish8.6
LINUXCNC - 2.9.2
Machine configuration directory is '/home/aswin/linuxcnc/configs/my_LinuxCNC_machine'
Machine configuration file is 'my_LinuxCNC_machine.ini'
INIFILE=/home/aswin/linuxcnc/configs/my_LinuxCNC_machine/my_LinuxCNC_machine.ini
VERSION=1.1
PARAMETER_FILE=linuxcnc.var
TPMOD=
HOMEMOD=
TASK=milltask
HALUI=halui
DISPLAY=gmoccapy
COORDINATES=XYZ
KINEMATICS=trivkins coordinates=XYZ
Starting LinuxCNC...
Starting LinuxCNC server program: linuxcncsvr
Loading Real Time OS, RTAPI, and HAL_LIB modules
Starting LinuxCNC IO program: io
Starting HAL User Interface program: halui
linuxcnc TPMOD=tpmod HOMEMOD=homemod EMCMOT=motmod
Found file(REL): ./my_LinuxCNC_machine.hal
Shutting down and cleaning up LinuxCNC...
Running HAL shutdown script
hm2: loading Mesa HostMot2 driver version 0.15
hm2_eth: loading Mesa AnyIO HostMot2 ethernet driver version 0.2
hm2_eth: ERROR: Could not retrieve hardware address (MAC) of 10.10.10.1: Connection refused
hm2: unloading
Removing HAL_LIB, RTAPI, and Real Time OS modules
Removing NML shared memory segments

Debug file information:
Note: Using POSIX realtime
hm2_eth: rtapi_app_main: Connection refused (-111)
./my_LinuxCNC_machine.hal:9: waitpid failed /usr/bin/rtapi_app hm2_eth
./my_LinuxCNC_machine.hal:9: /usr/bin/rtapi_app exited without becoming ready
./my_LinuxCNC_machine.hal:9: insmod for hm2_eth failed, returned -1
5811
Stopping realtime threads
Unloading hal components
Note: Using POSIX realtime


 

I am facing joint 0 following error while connecting with mesa board and also hm2_hm2.0/error finishing read iter-13284 {"joint 0 following error" and "hm2_hm2.0/error finishing read iter-13284"}

Hello Aciera,
I could not find "lib/python/gladevcp".
I have Debian 12, 6.1.0-22 RT kernel, LinuxCNC2.9.2.
I only installed glade by command "sudo apt install glade", although there is lot of result if I use "apt search glade".
In other hand, I could not find & install glade-gtk2 by "apt install" command, too.
Did I install gladevcp correctly ?.
Thank you.

 

For installing Klipper use KIAUH, it simplifies everything to some keypresses and it is a bit faster than the normal copy/paste throughout several internet pages of howtos.
It works on Linux Mint and POP OS, not just RPI as most info points out to, so should also work on Debian.
Klipper is the de facto 3D printer software as it has everything needed and is constantly being developed and updated.
There are several pieces to Klipper:
-klipper running on the ST board/micro controller
-klipper running on host PC or RPI
-moonraker - the part that links Klipper to the outside world, like Mainsail or Fluid and Telegram Bot and stuff
-Mainsail or Fluid, both are frond ends or user interfaces, web based
-Klipper Screen does exactly that, shows info on screen and can be controlled from the encoder/buttons/touchscreens
-
-
Added some more info to the above post about Marlin

Könnten Sie die Datei posten, die durch die Schaltfläche „BACKUP CONFIG“ auf der Registerkarte „SETTINGS“ erstellt wurde?

Könnten Sie auch versuchen, eine der QtVCP-Sim-Konfigurationen auszuführen, um zu sehen, ob es sich um ein allgemeines Problem bei Qt handelt.
 
 

Not sure why you would connect the step/dir grounds together
as they are already connected together on the 7I96S.

If you are using differential drive (It appears that you are)
you don't need to connect to the step/dir ground pins at all.

Also the input common (If grounded) would typically be connected to
the switch supply ground

The switch supply is often 12v/24V as this better for proximity switches
or mechanical switches than 5V


As far as EStop goes, removing primary (AC) power from the step motor
supply and spindle supply would be a reasonable  scheme.

Hey, so I was looking through the manual to the 7i96s and can’t find if there’s a way to ground all the step/dir headers ports in series without building a cable harness to do it.  I’ve connected all the step/dir ground pins to the TB3 pin-12 INPUT COMMON.  Is there an easer way to do this?  Maybe there’s a jumper I don’t know of that would activate the same circuit as the cable I built? 

It would be nice if such a cable was included or there be a jumper option on the board with the 7i96s.  Maybe for the next model at least would be a good idea. 

Then another question?  Instead of killing power to all my drives with the estop should I just instead kill the ground to all the step/dir headers so they stop sending movement signals?  Someone earlier said its just best to kill all the drives altogether incase a drive is malfunctioning whereas if you kill just the signal there’s still a chance that hitting the estop isn’t going to stop the malfunctioning drive. Anyways what’s everyone else doing with there 7i96s’s and grounding the step/dir headers?  Thats the main question.  Thanks