Advanced Search

As far as I am aware they both use Python but have been developed by different people. QtVCP is part of linuxcnc while QtPyVCP is an external project.
forum.linuxcnc.org/qtpyvcp/40986-differe...vcp-and-qtvcp#193481

Hello,everyone,I 'm considering using QtPyvcp or QtVCP design my machine's UI ,and I know the QTVCP is able to completely customize,but I 'm not sure if  QtPyVCP does since there is little doc about it in the official site.So,my question is maybe QtPyVCP is use python and QtVCP using c++,I prefer to use python because it 's much easier ,but I wonder there is shortcoming or some limit with QtPyVCP comparing to QtVCP ,any comment is welcome,thanks

Hi everybody.
I am new here, how ever this forum is not new to me.
I have a cnc plasma machine with was retrofited 9 years ago. The supplier went bankrupt in 2018 and I was looking into linux cnc ever since. (but not brave enough to install it and experimenting....)
The original machine was a Messer Griesheim Cortina S 2600, the retrofit included the servo, main computer, ac motors and gears, a IHT height control and a Kjellberk High Focus 160i.
Now a small software problem throws this machine out of service and I am looking for a solution.
Who can help me to install and configurate linux cnc on this machine. Is there any service or did anybody know who can do that remotely, I am very happy to pay for the time and effort.
I am not sure whether It is appropriate to offer money on this forum but I am very desperate.
 

Hello Krister,
Did you resolve this?
NaN

There are custom kinematics for 'rotary delta' and for 'linear delta' that come with LinuxCNC. Which kind are you looking for?

Big thanks Aciera!

That code worked on the first time. It sure would have taken me a while to figure out that snippet.

My Probe Basic config already had a SUBROUTINE_PATH set in the INI file and the folder it pointed too already contained a similarly named toolchange.ngc. So I named the new file custom_tool_change.ngc instead and renamed the sub statement inside the file to o<custom_tool_change> to avoid any potential conflicts.

This is going to save a lot of time on my manual tool change machine.

I'll have to buy you a beer for this on the next LinuxCNC meething/gathering.

Hi.

Can anyone help where to start to control a custom delta robot with raspberry pie?

I dont know where to start

Hi
I am tryinh to run linuxcnc on fedora using copr.fedorainfracloud.org/coprs/dwrobel/linuxcnc/ link
Now I am trying to run it as root user because I don't want to give root access to main user.
after running linuxcnc command in terminal I am getting

LINUXCNC - 2.10.0-0.100.20231213git6d8161a.fc38
Machine configuration directory is '/usr/share/doc/linuxcnc/examples/sample-configs/sim/axis'
Machine configuration file is 'axis.ini'
Starting LinuxCNC...
linuxcncsvr (261738) emcsvr: machine 'LinuxCNC-HAL-SIM-AXIS'  version '1.1'
linuxcnc TPMOD=tpmod HOMEMOD=homemod EMCMOT=motmod
Refusing to run as root without fallback UID specified
To run under a debugger with I/O, use e.g.,
    sudo env RTAPI_UID=`id -u` RTAPI_FIFO_PATH=$HOME/.rtapi_fifo gdb /usr/bin/rtapi_app
<commandline>:0: waitpid failed /usr/bin/rtapi_app tpmod
<commandline>:0: /usr/bin/rtapi_app exited without becoming ready
<commandline>:0: insmod for tpmod failed, returned -1
Refusing to run as root without fallback UID specified
To run under a debugger with I/O, use e.g.,
    sudo env RTAPI_UID=`id -u` RTAPI_FIFO_PATH=$HOME/.rtapi_fifo gdb /usr/bin/rtapi_app
<commandline>:0: waitpid failed /usr/bin/rtapi_app homemod
<commandline>:0: /usr/bin/rtapi_app exited without becoming ready
<commandline>:0: insmod for homemod failed, returned -1
milltask (261749) task: machine 'LinuxCNC-HAL-SIM-AXIS'  version '1.1'
halui (261754) halui: machine 'LinuxCNC-HAL-SIM-AXIS'  version '1.1'
Found file(lib): /usr/share/linuxcnc/hallib/core_sim.hal
Refusing to run as root without fallback UID specified
To run under a debugger with I/O, use e.g.,
    sudo env RTAPI_UID=`id -u` RTAPI_FIFO_PATH=$HOME/.rtapi_fifo gdb /usr/bin/rtapi_app
/usr/share/linuxcnc/hallib/core_sim.hal:5: waitpid failed /usr/bin/rtapi_app trivkins
/usr/share/linuxcnc/hallib/core_sim.hal:5: /usr/bin/rtapi_app exited without becoming ready
/usr/share/linuxcnc/hallib/core_sim.hal:5: insmod for trivkins failed, returned -1
Shutting down and cleaning up LinuxCNC...
USRMOT: ERROR: command 30 timeout
emcMotionInit: emcTrajInit failed
USRMOT: ERROR: command 3 timeout
Refusing to run as root without fallback UID specified
To run under a debugger with I/O, use e.g.,
    sudo env RTAPI_UID=`id -u` RTAPI_FIFO_PATH=$HOME/.rtapi_fifo gdb /usr/bin/rtapi_app
LinuxCNC terminated with an error.  You can find more information in the log:
    /root/linuxcnc_debug.txt
and
    /root/linuxcnc_print.txt
as well as in the output of the shell command 'dmesg' and in the terminal


File: /root/linuxcnc_debug.txt


  260460
  260470
  Stopping realtime threads
  Unloading hal components


File: /root/linuxcnc_print.txt

  RUN_IN_PLACE=no
  LINUXCNC_DIR=
  LINUXCNC_BIN_DIR=/usr/bin
  LINUXCNC_TCL_DIR=/usr/lib64/tcl8.6/linuxcnc2.10.0
  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
  INIFILE=/usr/share/doc/linuxcnc/examples/sample-configs/sim/axis/axis.ini
  VERSION=1.1
  PARAMETER_FILE=sim.var
  TPMOD=
  HOMEMOD=
  TASK=milltask
  HALUI=halui
  DISPLAY=axis
  COORDINATES=X Y Z
  KINEMATICS=trivkins
  Starting LinuxCNC server program: linuxcncsvr
  Loading Real Time OS, RTAPI, and HAL_LIB modules
  Starting TASK program: milltask
  Starting HAL User Interface program: halui
  Removing HAL_LIB, RTAPI, and Real Time OS modules
  Removing NML shared memory segments

 

Here I am sanding the back end of the spindle.

 

I made two parts that grip the spindle Pulley V-groove .This part has a cone from the outer part, the second part (not in the pictures)  presses the first part to the axis of the spindle.

 

 

I keep the original oil pump. It was necessary to make several parts.

 

 

We put linear guides. They had to be level and make holes for threads.

 

 

 



 

It's one of those stupid/crazy CNC lathe projects.  If I could turn back time, this project would not exist.I will try to upload more pictures but not everything is documented ..

We bought an old machine probably 2 tons of iron and immediately begins disassembly, washing and painting  

 

 

 

 

I threw out a lot of parts from the gearbox

 

 

This is the first layout of the electrical cabinet

 


 


I have reached the maximum number of files allowed .I will continue in the next post

Hello
Has anyone been able to do homing in Litex using encoder index pulse?
According to what I observed, when the homing switch signal is received in linuxcnc, the axis value is reset, but the encoder position value is reset when the encoder index pulse is received.
This difference causes an error in homing when the axis and encoder counter are reset.
In litex there is a pin called <board-name>.encoder.<n>.reset (HAL_BIT) which resets the encoder value.
Can anyone tell me how to configure it in Hal so that when the axis is reset the encoder value is also reset?

This is a very nice result, congratulations!

Do you plan to release your code to fellow tinkerers?

PCW will write the firmware for you and post it here. It doesn't have anything to do with your knowledge of linux.

You have to tell him what pinout you need. Since you mentioned DB25 I assume you have a 7i92TM. Look at the manual and find the IO number for the pins you want to do what, make a list and post it here.

Pins are GPIO by default so nothing changes with those, you assign them as input/output in HAL. Encoders, pwmgens, stepgens are modules, a stepgen has 2 pins for example, so list what pins of the connector you need as step and direction.

Meaning edit in the Mesa firmware?
It looks like I can edit it on the 440 HAL file. I just don't understand Linux terms and commands well enough to know how to reassign io db25 pins.
Any advice to help me figure out how?

That error (and others I have seen) seem to be a bug in the mesa-modbus code
The problem is that it does not reset the RX UART before using it, so if it has left over
RX data from the previous run. garbage from power cycles etc etc

Here's my list of know bugs, missing features:

    Current Mesa Modbus issues:

    
    BUGS:
    At startup there can be "call/response function number missmatch"
    error popups or sig11 (segv)s due to the fact that the PKTUART is
    not cleared at startup, so random numbers of garbage characters
    may be present in the RX FIFOs, leftover from the last LinuxCNC run.
    
    A temporary workaround is to run this before launching linuxcnc:
    
    mesaflash --device cardname --addr ipaddr --wpo 0x6800=0x00010000
    
    (writing 0x10000 to 0x6800=pktuartr_mode_reg clears the RX FIFOs)

    If you ever set the update rate to 0 (maximum), changing to a
    non-zero rate will not work (communication stops)
    
    There is a check for TX overflow in the PKTUART code that's
    in the wrong location (TX section) so will print bogus error
    messages with particular outgoing messages.
    
    FEATURES:
    
    Channel setting should not be global but in the .mod file
    to support more than one device.
    
    It would be good to have the error timeout/recovery
    time programmable.
    
    For multiple reads/writes it would be good to have the
    possibility of mixed types,
    This means for modbus devices that support table reads,
    all I/O for a device could be done in a single read and a single
    write.