[Emc-developers] custom user components into Linuxcnc distro

[Tom Easterday]

Is it (un)usual to put a random user component into the source distribution for general release? I have a component that talks to a custom arduino-based circuit board to control an EMCO lathe turret. I’m fairly certain we will be making the hardware and various software components open source and am wondering if we should put the component into the general release? That would certainly make my own life easier even for my own machine as I wouldn’t have to worry about making sure it’s there and works if/when the software is updated or the machine controller pc changes. This assumes that anyone else gives a poo about it, which might not even be the case, but just wondering how this is normally handled.
Thanks,
-Tom


------------------------------------------------------------------------------

[Sebastian Kuzminsky]

Post by Tom Easterday
Is it (un)usual to put a random user component into the source distribution for general release? I have a component that talks to a custom arduino-based circuit board to control an EMCO lathe turret. I’m fairly certain we will be making the hardware and various software components open source and am wondering if we should put the component into the general release? That would certainly make my own life easier even for my own machine as I wouldn’t have to worry about making sure it’s there and works if/when the software is updated or the machine controller pc changes. This assumes that anyone else gives a poo about it, which might not even be the case, but just wondering how this is normally handled.

If it's something that can be used without special external software,
it's definitely welcome into LinuxCNC.

If it needs special external software then i think the comp is better
packaged with that software, like my Teensy HAL driver:

https://github.com/SebKuzminsky/linuxcnc-hal-teensy


But if there's a good argument that it makes life better for our users
if we include it, i'm all ears.

[Andy Pugh]

Post by Sebastian Kuzminsky
But if there's a good argument that it makes life better for our users
if we include it, i'm all ears.

I wonder how different on behaviour this comp is from carousel,comp and whether they could converge?

(Not that carousel.comp is included yet either)


------------------------------------------------------------------------------

[EBo]

Post by Andy Pugh

Post by Sebastian Kuzminsky
But if there's a good argument that it makes life better for our users
if we include it, i'm all ears.

I wonder how different on behaviour this comp is from carousel,comp
and whether they could converge?
(Not that carousel.comp is included yet either)

I would ask if there is some extant infrastructure (like drivers,
tools) which would accommodate not only the code under current
discussion, but also things like carousel.comp. Let's first play a
"what if" and see what it would go, and how it would be handled, and in
that discussion we can also discuss if we want to do it at all, how it
would be organized, and if we want that specific functionality...

Just my 2C

------------------------------------------------------------------------------

[Tom Easterday]

I suspect it is different due to the arduino based custom hardware it talks to. But I am unfamiliar with carousel.comp. The component is attached. I will be posting the schematics/board layout, arduino sketch, etc soon to the users list for anyone who might want it.
-Tom

[andy pugh]

Post by Tom Easterday
I suspect it is different due to the arduino based custom hardware it talks to. But I am unfamiliar with carousel.comp.

I think it would need a bit wrapping round it to run the changer in
question. (And would replace the Arduino, rather than work with it).
A gray-coded unidirectional setup of carousel-comp with a oneshot
triggered by the "complete" to run a bit of reverse PWM might work.