Advanced Search

Thanks, I'm in, it looks fantastic, great work, I should say that I'm an IT guy tinkerer nowhere near as talented as most of the folks on here but LinuxCNC is the only system I've ever used. I love Linux. The HAL still gives me heart palpitations.

Do you think it could also work with a USB blaster?

rthorntn wrote:

If possible, could I have a 5AX please, obviously I'd pay for it?

+13 years linuxcnc.org member. My God, you've been around and respectfully deserve one of those 5ax more than I do. I'll arrange that for you, np.
More or less fifty bucks worth of parts + a $15 jtag programmer. Ball park. Let me know if you're still in. 

Rgs.  

You can sometimes compile the kinematics with halcompile. Whether is works or not depends on what libraries you need.

linuxcnc.org/docs/stable/html/hal/comp.html

There is an existing component to correct XY skew: wiki.linuxcnc.org/cgi-bin/wiki.pl?Contri...y_XY_skew_correction

But building LinuxCNC isn't all that hard once you are set up for it. In fact it is very easy once you are set up, but getting all the build dependencies installed can be a bit tedious.

1) Install Git: sudo apt-get install git git-gui
2) linuxcnc.org/docs/stable/html/code/building-linuxcnc.html - Step 2.1
3) Then step 4.2.2

(But at least skim the whole page, and at this time ignore any mention of RTAI)
 

If possible, could I have a 5AX please, obviously I'd pay for it?

Auto login is covered in my Debian 12 document at point 19  here
docs.google.com/document/d/1jeV_4VKzVmOI...diY/edit?usp=sharing

The Ethercat master we use is a product  from  iGH etherlab.org/en_GB
the linuxcnc-ethercat driver connects Linuxcnc to the iGH master
cia402 is a protocol for motor control over ethercat
cia402.comp is a Linuxcnc component to present a unified Ethercat driven interface for cia402 devices.
QTplasmac is a commercial quality plasma controller available as standard with linuxcnc.

Re your hydraulic torch lifter, its shares some qualities with the 24 volt geared motor lifters (crappy). I am currently helping someone to retrofit a table with Linuxcnc that has one of the motor driven lifters. Our approach is to replace it with a stepper driven torch lifter. I suggest you do the same,


 

As I know no progress. I solved my task other way, with default, not wrapped settings.

It's tiny (90mmx70mm). But big enough to get me started with RIO. Sure packs a great punch!!

Making 5 (five). Four for myself, and one for you You'll need to think of a way to let me know how to get one of those to you in DE.

WOW, looks very nice 

Great insights, thanks for that! That's why it's paramount importance to get the actual physical ISO776x part on the benchtop and oscope each and every single pins' state when powering-up -and- at runtime (MPG, Omron Encoder, Stepper Drive, INs, and OUTs). Only way to confirm!! Pulls HIGH, translates and isolate as advertised!! 3-in-1, highly recommend. Mind you, there is also a pulldown ISO776x variant - if resistors are preferred (ISO7760FDBQR). 

LinuxCNC-RIO 5AX Motion Control Board (9k, 10ins, 5outs, wired mpg, 100mbps, jtag, lightning proof lol). Going out to the pcb fab tomorrow. Should get this back in 5~7 days ready for assembly. Hard work... 

How to add parallel input card in my EtherCAT configuration to control the frequency converter and handwheel with 0~10V input




#*********************
#  手轮设置
#*********************

loadrt hal_parport cfg="1 in"
addf parport.0.read servo-thread

# Jog Pendant
loadrt encoder num_chan=1
loadrt mux4 count=1
addf encoder.capture-position servo-thread
addf encoder.update-counters servo-thread
addf mux4.0 servo-thread

# If your MPG outputs a quadrature signal per click set x4 to 1
# If your MPG puts out 1 pulse per click set x4 to 0
setp encoder.0.x4-mode 0

# For velocity mode, set to 1
# In velocity mode the axis stops when the dial is stopped
# even if that means the commanded motion is not completed,
# For position mode (the default), set to 0
# In position mode the axis will move exactly jog-scale
# units for each count, regardless of how long that might take,
setp axis.x.jog-vel-mode 0
setp axis.y.jog-vel-mode 0
setp axis.z.jog-vel-mode 0

# This sets the scale that will be used based on the input to the mux4
setp mux4.0.in0 0.1
setp mux4.0.in1 0.01
setp mux4.0.in2 0.001

# The inputs to the mux4 component
net scale1 mux4.0.sel0 <= parport.0.pin-08-in-not
net scale2 mux4.0.sel1 <= parport.0.pin-07-in-not

# The output from the mux4 is sent to each axis jog scale
net mpg-scale <= mux4.0.out
net mpg-scale => axis.x.jog-scale
net mpg-scale => axis.y.jog-scale
net mpg-scale => axis.z.jog-scale

# The MPG inputs
net mpg-a encoder.0.phase-A <= parport.0.pin-13-in
net mpg-b encoder.0.phase-B <= parport.0.pin-10-in

# The Axis select inputs
net mpg-x axis.x.jog-enable <= parport.0.pin-15-in-not
net mpg-y axis.y.jog-enable <= parport.0.pin-11-in
net mpg-z axis.z.jog-enable <= parport.0.pin-04-in

# The encoder output counts to the axis. Only the selected axis will move.
net encoder-counts  <= encoder.0.counts
net encoder-counts => axis.x.jog-counts
net encoder-counts => axis.y.jog-counts
net encoder-counts => axis.z.jog-counts


#*********************
#  变频器PWM控制
#*********************
loadrt pwmgen output_type=1
net spindle-cmd-rpm => pwmgen.0.value
net spindle-on <= spindle.0.on => pwmgen.0.enable
net spindle-pwm <= pwmgen.0.pwm

setp pwmgen.0.pwm-freq 100.0
setp pwmgen.0.scale 24000.0
setp pwmgen.0.offset 0.0
setp pwmgen.0.dither-pwm true

net spindle-cmd-rpm     <= spindle.0.speed-out
net spindle-cmd-rpm-abs <= spindle.0.speed-out-abs
net spindle-cmd-rps     <= spindle.0.speed-out-rps
net spindle-cmd-rps-abs <= spindle.0.speed-out-rps-abs
net spindle-at-speed    => spindle.0.at-speed
net spindle-cw <= spindle.0.forward

net spindle-pwm     => parport.0.pin-01-out
net spindle-cw      => parport.0.pin-16-out


The above is the HAL file I configured, but it seems that it cannot output PWM signals correctly
 

I'm going to have to disagree with you on the need for pull up or pull down resistors on inputs, especially with switches (unless the switch is switching to either zero or 5v)and rotary encoder that have an open collector output. Without a pullup or pull down resistor the input is going to float, until that input has a definite logic level on it. With high impedance inputs it requires very very little current to switch the input, if the voltage is at the right level. Generally on a chip such as the venerable 74xx245 when the enable inputs are in the disable state the output is considered to be in a "high impedance state" and is unable to "drive" the outputs.
Honestly any input that is connected via a cable needs a pullup or pulldown resistor for the case of a breakage in the signal wire, especially with an MPG, if teh signal wire breaks you want that input at the board end to held at a known level. The last thing you want is for your input to pick up stray noise and start oscillating. The chip wont "know" if it is a legitimate signal or noise and will pass that on to the other side.
That's why sometimes I feel am opto isolator is a bit better in this respect as the current required to drive the LED in normal situations is a little higher than induced noise in the line.

Never in my life have I designed a digital circuit that takes external off board signals with pullup or pulldown resistors, or inputs that get the input from a SPST switch from an on board switch without a pullup or pull down.

Hi all,

I have two NPN NO proximity sensors hooked up on my lathe on input 1,2 in my 7i96s. In the Pncconf wizard, when I am trying to put the 'limit and home shared' on the respective axis and home them together, both axis are moving towards the sensors, then as soon as the one axis reaches the home switch, both the axis starts the homing sequence without the other getting at the home position and then it shows "limit joint 0/1 error". But when I am changing the inputs from 'limit and home shared' to 'home', the homing sequence works properly and it behaves just like a shared limit-home switch.

Since the proper input should be the shared limit-home, is there something that I am doing wrong or am I missing something?

I have a working config running two 8i20 cards driving modified fanuc motors. And haven't been able to get my head around how to control a stepper, there's two steppers included in the firmware and I can't understand how to use them.