Advanced Search

So at the beginning of the hal file
there is a commented out loadrt for the
abs function and later on an addf line
for that function that fails because
the function was never installed.

I suspect this is a bug in this pncconf
version when certain spindle functions are not
used. It turns out the the abs function
is never used, so simplest fix would be to delete
the addf abs.spindle line in the hal file.

#loadrt abs names=abs.spindle
#loadrt lowpass names=lowpass.spindle

addf hm2_5i25.0.read servo-thread
addf motion-command-handler servo-thread
addf motion-controller servo-thread
addf pid.x.do-pid-calcs servo-thread
addf pid.y.do-pid-calcs servo-thread
addf pid.z.do-pid-calcs servo-thread
addf pid.a.do-pid-calcs servo-thread
addf pid.s.do-pid-calcs servo-thread
addf abs.spindle servo-thread
addf lowpass.spindle servo-thread
addf hm2_5i25.0.write servo-thread
setp hm2_5i25.0.dpll.01.timer-us -50
setp hm2_5i25.0.stepgen.timer-number 1

Edit:

Note that the same issue is there with the lowpass function.

I suspect these were added for some some spindle speed display
function, that was not used, and only 1/2 removed from the hal
file boilerplate

Thanks. I bought the Stahlwerk 70 P Plasmacutter.

Would this resistor also be possible (Mouser wants 20€ shipping) ?

www.reichelt.de/de/de/shop/produkt/wider...7_250_mw_0_1_-237509

Inside a box outside the pasma-source to avoid warranty-loss (7 Years warranty on the machine).

Hi guys!
I get a VMC-100 as gift from a school.

I owm a F1P which i retrofit to LINUXCNC years ago. works perfect.
Same Machine as the VMC-100 but with manual Toolchange.

Now the VMC-100 has a carousel as Toolchanger.

 

This carousel have 4 proximity switch to operate the Toolchanger.

 

Sensor1 is a sensor to reference tool 1.
Sensor2 counts a hole in a parallel gear. is it counts 2 times the next toolslot is reached.
Sensor3 tells that the tool is engaged.
Sensor4 tells that the tool is disengaged and the mainspindle can rotate the carousel.

 

Main issue for me is that the carousel works above the Z reference sensor.
At Z reference positon the Carousel begins to disengage the tool and when sensor 4 is reached the carousel can rotate.

Does someone ever retrofit this in Linuxcnc and can share his experience?
I searched a bit arround but found only some videos with MACH3 and some dead threads.

I will use the orignial maindrive which has a encoder on it at the beginning.
the maindrive works with step/dir signals.

On my f1p was the same maindrive which i use to tap threads.. spindle orient is used for this but iswitch to a 1kw servo.
this time i will use everything orignial because i have 3 orignial stepperdrivers for the 5 phase steppers. later i would change to nema23 2 phase.
Main focus is to bring everything back to live without changing to different steppermotors or maindrive.

The maindrive is working and the encoder counts.
Steppers working.
all proximity sensors are working.


thanks for any help

the pictures are taken from youtube



 

Einfach sudo dpkg -P raspi-firmware eingeben

Attached are the requested files. 

I have not made any manual changes to either of these files. They are both output from pncconf.

Kind Regards

Hi,

in my eyes the related software (ancdevicestarter) for the stepperonline A6 Servos is a bit confusing in terms of Autotuning.
The manual of the servos and the manual of the software are confusing for me.

Is there any video or tutorial out there bringing light into the darkness or is there anybody who could just give a short goto?

thx in advance

best

Kai

Good evening Tommy

Can i please get a copy of the 19.3 iso? I have finally gotten myself a touch screen for my project mill and ofcourse, it doesnt work as it turns out to be some funky Quanta OpticalTouchScreen device with a ViewSonic sticker. research suggests other linux (not LCNC) users have used this monitor just fine on older kernel builds so im hopefull the 19.3 iso and associated older RT kernal will work.

i use a mpg and i add more smaller step scales. like 0.001 0.005. i was on the wrong way! sry!

Hello,
I was trying figure it out and find answer but without success.
Have You know why in auto mode and MDI sometime machine stuck in reading state without execution of program? Just simple turn off and on again LinuxCNC is helping, but it is not a solution. In machine status I didn't find any interesting thing. Every parameter look same when working normally and when stuck in reading state.
For example if first line is G01 Z5 F100, and when I manually move axis to Z10, then first line of program will be executed, and machine stuck, next line is simple G01 X1 Y1 F100. MDI commands not working then also.
Thank You in advance

tommylight wrote:

 i have resolvers that do not work with 7i49,

your particular resolver type.  

How can I tell what type of resolver I have?

Hi all,
I am running 2.8.4 and only recently noticed that none of my
(indeed very old) touch probe scripts/o-codes do run nowadays.

With this "new" (v2.8) probe behaviour, which seems to be activated
all the time - how am I supposed to move the probe, including bouncy
ones, off the material after it triggered?
As long as the probe is activated, all (G00/G01) commands fail and
immediateely abort the program.

That also was recently added to the repo tracker (not by me though
github.com/LinuxCNC/linuxcnc/issues/292

This behaviour makes it basically impossible to probe more
than one time, e.g. a grid etc.

Is there any workaround or am I missing something (new)?


AS

there are DMC2 31025P for sale on eBay but they are no cheap. As an alternative the Copley Controls Xenus servo drive. they take resolver input but you would need to have look at the manual (manual is online) and determine if it does accommodate your particular resolver type.  

Not sure if this is a pncconf version issue but current pncconf does this:

# external input signals

# --- HOME-X ---
net home-x     <=  [HMOT](CARD0).inm.00.input-00

# --- HOME-Y ---
net home-y     <=  [HMOT](CARD0).inm.00.input-01

# --- HOME-Z ---
net home-z     <=  [HMOT](CARD0).inm.00.input-02

From this:

 


In your hal file you have# --- MIN-X ---
net min-x <= hm2_7i96s.0.gpio.000.in_not

but net-min-x is not connected to anything so is not functional

the actual signals connected are these (also from your hal file)

# ---setup home / limit switch signals---

net x-home-sw => joint.0.home-sw-in
net x-neg-limit => joint.0.neg-lim-sw-in
net x-pos-limit => joint.0.pos-lim-sw-in

so if you changed

# --- MIN-X ---
net min-x <= hm2_7i96s.0.gpio.000.in_not

to
# --- MIN-X ---
net x-home-sw <= hm2_7i96s.0.gpio.000.in_not

you should get some function

(I am glossing over the difference between the INM inputs and GPIO inputs
as they can be used interchangeably on the 7I96/7I96s, that is GPIO 0..10
behave the same as INM 0..10)

It seems that Glentek makes servo drives that can take input from resolvers for commutation, and emulate a quadrature encoder for other uses.
I've sent them an RFQ.

It cuts metal pipes/tubes/profiles using a 4KW laser.
Sorry if i was unclear.
I will fix the tittle now, thank you for pointing it out.