Advanced Search

Does the sim/tklinuxcnc config start OK? That uses the same loop.

github.com/LinuxCNC/linuxcnc/blob/master...lib/core_sim.hal#L46

gui is launching i cant move the stepper with arrows because i am locked and i can not turn the machine on

Are you saying the GUI never launches?

import linuxcnc and hal into the Python script, then create HAL pins to receive the spindle commands from HAL.

Load the Python script at load-time with a "loadusr" command in the HAL.

c@raspberrypi:~/linuxcnc/configs/microcarve$ LINUXCNC - 2.9.6
Machine configuration directory is '/home/cnc/linuxcnc/configs/microcarve'
Machine configuration file is 'microcarve.ini'
Starting LinuxCNC...
linuxcnc TPMOD=tpmod HOMEMOD=homemod EMCMOT=motmod
Note: Using POSIX realtime
Found file(REL): ./microcarve.hal
task: main loop took 0.100768 seconds
task: main loop took 0.113741 seconds
task: main loop took 0.140260 seconds



this is what i get running it from commandline. task: main loop ........

Can you report this problem on the issue tracker?

github.com/LinuxCNC/linuxcnc/issues

if this:

net estop-loop =>iocontrol.0.user-enable-out
net estop-loop => iocontrol.0.emc-enable-in

does not work, it's most likely because you have
estop-loop connected to another pin in the hal file.

Starting LinuxCNC from the command line will show the actual error.

Hendrixx wrote:

it's almost like multiprocess welders, unless you drop some serious money, you're compromising. 
 

Off-topic but I am impressed with the multiprocess welder at my local Hackspace. It allows you to keep both MIG and TIG torches permanently connected and has separate gas input spigots for each process gas. 
You are not wrong about the "serious money" part, though. 

parweld.com/product/xtm211di/

(#notsponsored )

axis not working over vnc in my setup,

net estop-loop =>iocontrol.0.user-enable-out
net estop-loop => iocontrol.0.emc-enable-in

this is resulting in tklinuxcnc not starting, maybe its working with older software versions.

Oh, and why tklinuxcnc? There's nothing wrong with it, but it's rather outmoded and hasn't had a lot of developer attention for a while.

Todd wrote:

net estop-out =>iocontrol.0.user-enable-out
net estop-in => iocontrol.0.emc-enable-in

 

I think these need to be the same signal name to work as described. Try:

(note that the signal name is nothing special, there is no significance in changing it to loop, other than clarity. The important thing is that it should be the same name on both lines) 
 

Is this with the LinuxCNC install image?

If your Glade UI element is of type "Hal button" then the HAL pin will be created automatically and no handler file is needed.

(This is stated with 93% confidence, I don't have easy access to a LinuxCNC machine at the moment to test this assertion)

[Gmoccapy.GMOCCAPY.GETINIINFO][[33mWARNING[0m] No DEFAULT_SPINDLE_SPEED entry found in [DISPLAY] of INI file (getiniinfo.py:282)
[Gmoccapy][[33mWARNING[0m] No virtual keyboard installed, we checked for <onboard>. Try 'sudo apt-get install onboard'. (gmoccapy:2112)
gmoccapy_postgui.hal:24: Pin 'gmoccapy.toolchange-change' was already linked to signal 'tool-change-request'
10530

If you have proved that you can control the drive from Python then I would suggest carrying on with that.
You can "import linuxcnc" and "import hal" into your Python script then create HAL pins to recieve the position commands from HAL.

linuxcnc.org/docs/stable/html/config/python-interface.html
linuxcnc.org/docs/stable/html/config/python-hal-interface.html