Advanced Search

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.

Pico Systems has a small board that converts a resolver to look like a standard quadrature encoder. Unfortunately, it can't provide commutation signals, but does provide an index pulse. This board will not work with variable reluctance resolvers, but is designed for "brushless" resolvers such as those made by Harowe Controls and Singer Kearfott. See:
picosystems.store/product/resolver-converter/
for more info.
There are AC servo drives that can operate without the commutation signals, these are often called "sensorless drives".
Jon

I am unclear. Does this cut laser tubes, or cut tubes using a laser?

Initially I assumed the former, but looking at it, I think it's the latter?

Weird.. Never seen that before. Have you setup the latest in settings for the last update? We changed a lot with offset table display, drop display and jog key display. If those in settings and yaml settings require some updates. If you would double check the docs and your config if you are running the development version and just make sure you caught all the updates.

Maybe explain what you're trying to do exactly. You want to keep the same tool number but change tools?

Is this to use a stationary probe? Or? Could you just call the same tool number with a different g43 h# to solve your requirement?

QtPlasmaC updates - Master (v2.10):

• "VEL:" label now indicates active velocity reduction and shows commanded feed rate percentage
• suppress gcode filter warnings when material feed rate is 0
• prevent material selector from opening when velocity label or indicator is clicked (when a program is running)
• allow velocity reduction between 1-100, fix documentation inconsistency