Advanced Search

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

I can try it, but since ethercat at the command line (linuxcnc isn't even running) shows ~50% lost uploads, what's the point?

I don't think this is a linuxcnc problem, but rather some networking or drive problem.

I think that the problem is inconsistent HAL signal naming.

You haveThen later in the file:
You need to connect the hm2_,,, pins to the halui.... (and motion....) pins.
Use the same signal name (the first term after "net") to link:

hm2_select pin / axis.L.jog-enable / joint.N.jog-enable

hm2_mpg_counts / axis.L.jog-counts / joint.N.jog-counts

You will also need to work out logic to set the scale:

(probably a mux block) axis.L.jog-scale joint.N.jog-scale

For initial testing, try:

(change the setp to 0.01 if using inches)

If that works, then configure the jog scale (but to help with that we wiuld need to know whether the MPG binary-codes the speed selector or has a pin for each speed)

(This is using the pins from "motion" which are slightly preferable to the halui pins. However HALUI supports analog jog mode, so has its uses.)

linuxcnc.org/docs/stable/html/man/man9/motion.9.html

Looks like mine has two sensors for the tool turret and the z limit switch.

Hi,
I am working on a FlexGui for a waterjet and I want to have some custom buttons that call hal and emc functions. 
I see I can import a python module and do the "from functools import partial" to get the parent, but does the parent also pass access to hal and emc?

I am trying to make a custom stop button that will turn off some hal output pins with hal.set_p() and then call emc.abort() in python so it will turn off the jet and sand when pressed. I also need to make one that will pause by setting the hal pins off and setting the motion.adaptivefeed to 0.

Any help would be appreciated

Made the change net tool-change-request iocontrol.0.tool-change.
 

I have made some progress:

I have had to set the axis velocities to constant values (500000, where the encoder has 524288 counts per revolution), since I don't see any HAL pins from the motion planner that carry that information. I will see about writing a custom HAL component that can interpolate velocity from waypoints.

I assembled a MB2HAL config file, and loaded it as a userspace component through halrun. With that, I could control each motor, with no perceptible lag between command entry and motion.

I can control the motors through Axis, but in G1 feed mode at the MDI, I get one step every second or so. For instance, I will command one axis to G1 Z1.0 F5.0 and it will move ~60° every second or so until the move is done. In G0 rapid mode at the MDI, there is a significant delay, again roughly one second between the time I press Enter and the time the motor begins to move. While the move is in progress, distance to go changes smoothly, but actual position (and the motor shaft) move in steps.

Can you help me understand how Glade and Handler work? I've already created the switch and the LED. How do I now connect them so that pin 17 switches on and off? I'm completly stuck.