Advanced Search

rdtsc wrote:

Noticed that 2.9.3 starts up with the locales set to "POSIX" or "C", which will cause pncconf to error out... best to add a note that menu-config must be run after after install, and set locale and timezone, then reboot.

There are some notes about using menu-config on the install page. Sounds like pncconf needs to be coded a bit more robustly. It should not fail for issues like that. We do set the locale to reasonable defaults here. github.com/rodw-au/rpi-img-builder-lcnc/...9.3/userdata.txt#L39

Thank you very much, I will try your advice.

In addition to some understanding of hal, you need to learn about the basic
components of LinuxCNC. One major component is called "motion"

You can access the manual page for motion by typing:

man motion

in a terminal window

M3  turns on the spindle so the motion pin:

spindle.0.on

would be a possible pin to connect to the SSR

halui.axis.jog-speed - This pin is for setting jog speed for plus/minus jogging.

To jog an axis you need to select axis, set jog speed using potentiometers and press plus or minus push button (PB) to jog axis. 

Most CNC machines built using Linuxcnc use joint (There is a whole spiel about axis/joint, google it if you would like to learn more about it).

Attached are function blocks of halui pins for axis to help visualize the jungle of pins. Halui has over 100 pins, I divided the related pins into function blocks to ease the visualization.For your info I added an external hadwired PB and UI widgets for +/- jog, you can use either or both.
 

Linuxcnc hal netlisting 

# Load realtime Components and their counts
loadrt or2          count= 2
loadrt scale        count= 1

# Add functions to threads
addf or2.0                    servo-thread 
addf or2.1                    servo-thread 
addf scale.0                  servo-thread 

# Set parameters
setp scale.0.offset                              0.0   
setp scale.0.gain                                0.12    

# Connect Pins with hal signals/Wires
net arduino.ain.0              scale.0.in  
net axis.sel.z.sw               halui.axis.z.select  
net axis.speed.minus       halui.axis.selected.minus  or2.1.out  
net axis.speed.plus           or2.0.out  halui.axis.selected.plus  
net axis.x.sel.sw                halui.axis.x.select  
net axis.y.sel.sw                halui.axis.y.select  
net halui.axis.jog-speed   scale.0.out  halui.axis.jog-speed  
net minus.speed.pb          or2.1.in0  
net minus.speed.ui           or2.1.in1  
net plus.speed.pb             or2.0.in0  
net plus.speed.ui              or2.0.in1  
 

I now I want something like this.
Hit execute gcode file.
g0 x10 y10
m3-> activates hm2_7i97.0.ssr.00.out-00
this should make the thc do its height sense, then fire the arc. Then send arc-ok to hm_7i97.0.inmux.00.input-04.
and linuxcnc should should follow file from there.

​​​​​​​Id also like to send a corner hold signal, but that seems a bit more complicated 

I know it’s hard to tell by my dumb questions, but learning some Hal commands and components is exactly what I’m trying to do.
so I added your joint.0.amp-fault-in and it works exactly as you stated. Awesome.
How do I learn this? I’m currently flipping through the Hal part of the manual and I don’t see anything about amp-fault. 
Is there a reference list for Hal commands?
 I now see it in Hal show, under pin/joint/0/amp-fault-in. Can I find description of these somewhere?
 

spumco wrote:

Maybe setting axis.L.jog-vel-mode to TRUE would cause in-process jogging to respond to speed changes?
 

Thanks for that, I tried but  axis.L.jog-vel-mode  does not help.

At least the feed-override acts dynamically, it even updates the slider in Axis when I twiddle the pot

Noticed that 2.9.3 starts up with the locales set to "POSIX" or "C", which will cause pncconf to error out... best to add a note that menu-config must be run after after install, and set locale and timezone, then reboot.

Aciera wrote:

This certainly works for me using panel buttons connecting to hal pins 'halui.axis.L.plus' and 'halui.axis.x.minus'.
Push the jog button and simultaneously change the jog speed with the potentiometer from 0..100%

[edit]
Just noticed that I also feed the potentiometer signal to 'gmoccapy.jog.jog-velocity.direct-value'. So maybe Gmoccapy has something to do with it.
 

I found a note somewhere that stated in axis the feed slider responds to halui.feed-override.increase and .decrease, however I'm using a pot feeding halui.axis.jog-speed not up and down buttons, so I think I'm out of luck with axis, unless there is some other method?
Thanks for the input.

Unfortunately to do this by hand does require learning some hal
commands and components because on most there would be some
logic or gating involved, but as a very simple example with no added
logic:

net breakaway joint.0.amp-fault-in  hm2_7i97.0.inmux.00.input-05

Note that joint.0.amp-fault-in and hm2_7i97.0.inmux.00.input-05 are both pins that
exist in your running LinuxCNC configuration, the net command simple connects them.
The "breakaway"  is the name of the signal that connects the pins. Its an arbitrary name
unless it's already defined somewhere else.

For example:

net brown_wire joint.0.amp-fault-in  hm2_7i97.0.inmux.00.input-05

will function identically (though perhaps be a bit harder to understand)


This statement will cause a fault and stop motion if hm2_7i97.0.inmux.00.input-05 goes high

You might need to use hm2_7i97.0.inmux.00.input-05-not depending on your
switch wiring.

(the input number is up to you, just used 05 in this example)
 

kiwiscanfly wrote:

please can those that have this working say the model. I've been looking at 3/4 80 series 23bit absolute with brake.

i would like to hear if there is a working config for the 32bit and brake before ordering.

I can confirm, everything works fine. Just in case, you can additionally compare this configuration with the documentation for your driver.

My model is LC10E, motor with 17 bit absolute multi turn encoder. 

I am having an issue with a machine using probe basic where the post gui hal files are not loading. Looking at the console output when running linuxcnc from the terminal does not show an obvious error to me. It just gets to the line where it is trying to load the first post gui hal file and stops. I have tried removing any customizations but it has no effect. Attached are my hal and ini files.

Another possibly related issue I am having is that if I ever use the e-stop, I get 2 "Bad character '[' used" errors. The error shown in the terminal is "emc/task/emctask.cc 68: interp_error: Bad character '[' used" and it happens even if I have no file loaded.

Has anyone encountered either of these problems? I am at a loss of where to look next on either and would appreciate any help.

I gave up on them after they cancelled my last order with no reason given. Wasn't worth pursuing.
I'd use RS & Element14 more often if they didn't take forever, both of their warehouses are within 20 minutes of where I live. Even still, Digikey or Mouser are quicker.
THB I haven't used either in 2 years as I just got fed up with them.

Well, I guess I’m stuck and didn’t explain my issue.
I set up a config in axis. X and y axis move appropriately when jogged, and the dro displays accordingly.
My 4 limit/home switches trigger in halshow. The limits will trigger machine power button.
My 2 inputs trigger digital inputs in halshow.
My 2 outputs get triggered when commanded in halshow.
And I don’t know where to go from here. I’m stuck. If I bought a new lifter, I’d be stuck in the same spot.

I obviously need to link the I/o’s to functions/buttons/gcode, but I don’t know how.
Im reading the manual and trying sample axis configurations, but I just can’t get anywhere.
Like input 1 is the breakaway. But I can’t figure out how to tell that to linuxcnc. 
I thought maybe I can just copy the limit switches, but I don’t even see how they trigger the machine off button in any of the hal or ini files.
And if I can’t figure out the breakaway, I don’t have much hope for cycle start or thc hold.

Is it rude to ask for a plasma specific axis configuration?

I appreciate the input, I just wish knew enough to ask the right questions.

Rodc, I assumed you suggested the lifter for functionality, but maybe you’re actually telling me to use a lifter that integrates with qtplasmac. I did consider using Linuxcnc to control the z motor and read arc volts with a mesa thcad instead of the standalone hypertherm phc control, but I thought that just sounded like more work, more money, and more potential pit falls. But in retrospect maybe I should’ve done that just to make it easy to use qtplasmac. And a mesa card that works with pncconf instead of mesact 

sudo ethtool -C enp0s25 rx-usecs 0

Will only work until you power cycle/reboot
but it should allow you to see if it fixes the problem

So I would try that, followed by a ping test
and then running the machine.

There are two ways to make the change permanent

1. Setup the Ethernet connection in the interfaces file
(and remove the setup created by the network manager GUI)
Typical interface content would be something like:

# interfaces(5) file used by ifup(8) and ifdown(8)
# Include files from /etc/network/interfaces.d:
source-directory /etc/network/interfaces.d
       auto enp0s25
       iface enp0s25 inet static
           address 10.10.10.100
           hardware-irq-coalesce-rx-usecs 0


The other option is to include the

ethtool -C enp0s25 rx-usecs 0

line in the rc.local script that is run at power-up