Advanced Search

Bari wrote:

Lots of work to get it done correctly. Look at the challenge many people face just trying to install the debs.

I have mentioned on the mailing list that because RTAI Debs exist, it would be quite easy to build a RTAI ISO  by forking our live installer.
Its not that much harder to get the installer build process to compile the debs

Most GUIs are written in python and use the Linuxcnc python API instead of connecting signals through hal pins:
linuxcnc.org/docs/devel/html/config/python-interface.html

Over time you will find that there usually are several possible ways to get something done in LinuxCNC.

thanks

I'm stuck now anyway. I ordered some "precision collet reducers" and one wound up with 0.0028" runout, and the other was 6.32mm instead of 6mm.

That's worse than even the most garbage $1 aliexpress collet reducer.

Sigh. now I need to figure out something else and likely wait weeks for it to arrive...

Whilst mesa and ethercat might coexist as they NIC they use are defined for each environment, the question is why do that?
Ethercat can do everything a mesa card can do and then some.
Re the tool changer, I have not had any experience with them either but I think using a low cost stepper would make sense.
An ethercat stepper driver from Leadshine or Rtelligent  would solve the problem. Not sure about Leadshine but Rtelligent make both open and closed loop ethercat drivers. For Nema23/24, ECR60 = open loop, ECT60 = closed loop.

That was an intentional change.
Hyphen is the usual thing with HAL names.

Yes, typically all motion commands to lower level hardware come
from motions joint.n.motor-pos-cmd pins.

The basic jog information to motion uses motions jog pins like
axis.x.jog-counts and axis.x.jog-enable

The manual page and the HTML should be identical as they come
from the same source.

An MPG or on screen jog button usually  alters a count variable or pin up or down (plus or minus) and the count is scaled to steps per mm (or inch). That way the system knows how far the axis should move for every click of the MPG
This also explains why the count is not a float type
The jog velocity to use is set in an ini variable

That man pages eg man motion are also published to the Linuxcnc documents web site. I always use the web site. Just make sure you read the docs for your version of Linuxcnc.
The documentation for a component is actually coded into the component itself and extracted to a man page (and the web page) using halcompile when Linuxcnc is built

Keep it up. One day it will eventually click

..."to never command those pocket numbers that don't exist"

[I'm not going to tempt the Forum Editor of Doom]

ihavenofish wrote:

on the topic of my atc. seems a good reason to try and text the lichuan ethercat servos. 40mm 50 or 100w model.

Does ethercat works WITH the mesa card already there? as in, can i use both? or do i need to switch to all ethercat?

Regarding Eth & Mesa, I think they can both work... but you should wait for someone with more experience to confirm.

As for the ATC, I've only read about (far as I remember) one person who reported using an AC servo to control a carousel... and they mentioned quite a bit of fiddling to get the servo tuning right.  Unless you've got a really high ratio gearbox a servo is likely to see a pretty serious inertia mismatch.  Maybe an AC-powered ethercat stepper would be better in this application?  High torque at low speed, no tuning, and stall/alarm feedback via Eth in case of a problem...

And there's no need to 'use up' an axis letter for control of the carousel; you aren't doing coordinated multi-axis moves with the platter.  Carousel.comp works quite well at managing the platter movements & rotation and doesn't require much in the way of sensors.  The tool change sequence is still handled via g-code subroutines and and M6 remap.

In your case (i.e. half-platter), you set up carousel for the full compliment of positions to get the spacing correct, and just write your subroutines to never command those pocket numbers.

So when I pass MDI commands to the G-code interpreter, the position/velocity command "signal/value" gets sent to joint.0.motor-pos-cmd for instance

Where or which pin does the position/velocity command "signal/value" get sent to when I press the jog +x button on Gmocappy GUI? Shouldn't a motion component pin receive this signal/value? If so, which one?

I'm also using linuxcnc.org/docs/stable/html/man/man9/motion.9.html , instead of "man motion"currently. Is the "man motion" more descriptive?

With advances in internet connectivity some of these things are generally unnecessary today
A corporate network or ISP might run a proxy server that cached internet content for preserve bandwidth, Commonly requested content would be cached locally. Content is returned from the cache instead of the real source
A network of Debian mirrors was established around the world so you could download large files like ISO's from a server near to you without resorting to  pulling an image from the other side of the world via a slow link (eg via an undersea cable)

All,
I noticed that there is a variation of variable naming conventions between linuxcnc version 2.8 and the DEVEL version.

The difference I'm seeing is a hyphen and an underscore delimiting variable words.

Here's the related v2.8 docs page and the related DEVEL (2.10) docs page .

The variables that I noticed are as follows:

2.8 Versionqtdragon.modbus-errors
qtdragon.spindle_amps
qtdragon.spindle_fault
qtdragon.spindle_volts

2.10 Versionqtdragon.spindle-modbus-connection
qtdragon.spindle-modbus-errors
qtdragon.spindle-amps
qtdragon.spindle-fault
qtdragon.spindle-volts
Are these typos or a valid change?

blazini36 wrote:

That's exactly what mine "cost" but you got killed on shipping. I bought mine from the Chinese manufacturer on Alibaba. I'd probably do alot better if I ordered several

We Aussies always get killed on shipping and my own freight accounts did not give better rates.
But it was still much cheaper buying direct than sourcing anything  in this country and I had a better choice than on Amazon

The jog information goes from the GUI or hardware (MPG, Buttons etc)
to motion. Motion takes care of things like bounding acceleration and velocity,
and obeying soft limits. All low level hardware joint motion passes through
LinuxCNCs motion component. At some point the jogging information from the GUI,
switches/MPG gets connected to motions joint and/or axis jog pins:


man motion

(search for "jog" = /jog)

2019 is around the time I bought mine.
Below are some pictures of what I did to mount it.  I made a hinge with wavey and nylon washes so the hinge would have some friction and stay in place when I folded it out for use.