Advanced Search

Minor clarification on my earlier post

I don't think it matters when carousel.comp is in INDEX mode, but the config above is for a step/dir motor (stepper in my case) run through a 5:1 reducer.

The basic connections should work for a geneva wheel mechanism, too, but I just wanted everyone to be aware that the carousel.comp parameters/settings will need to be adjusted for speed and the fine alignment speed/time.

Chris - if you're contemplating a GUI-facing ATC interface with a 'settings' page to pass values through to carousel.comp (like the probe page does), you'll need to:

• Include ALL the carousel.comp pins/parameters for all the encoding types, or
• Lock it down to INDEX mode, and the user is required to have both sensors

Hello Tommy
Thanks for that - I will look into hal components. I was really not sure where to start. It is only a model engineering lathe so will not be pushed as much as a production machine. I will fit a tachometer to the spindle but accurate feedback is not really of great concern. And yes it was CSS I was referring to. At least I will have continuously variable spindle speeds on the new lathe - the previous one was too much trouble to mess around with the spindle gears and in theory the spindle speed needs to change with the tool X position anyway for optimum results. I have been using LinuxCNC on the lathe (and mill) for at least a decade, but the old lathe was far too crude to be worth messing around with optimisation.

COFHAL wrote:

yes, work.

???

No plugins, but hal components written in C, fairly simple once you have a look at them.
I think you mean CSS or constant surface speed, i am pretty sure LinuxCNC can do that, but it does require having spindle feedback wired to LinuxCNC (physically and in hal), prefferably A, B, and Index to be able to also do threading (it can do with 2 of those, not sure exactly).
Stoping spindle during tool change is built in and can be set in the ini configuration file. Pretty sure it is by default as i had to change that on my Mazak, been over a year since i did that....

Interference/EMI so:
-drive must be grounded
-motor must be grounded from the drive
-ferite bead on motor wires helps a lot
-get a good USB cable, Baseus, Ugreen, Satechi are good quality

Also, what acceleration is set in the ini file?

yes, work.

Here is a nice Video

SPI can be enabled by modifying the config.txt file and enabling the SPI option which is disabled by default.

sudo nano /boot/broadcom/config.txt

# uncomment some or all of these to enable the optional hardware interfaces
#dtparam=i2c_arm=on
#dtparam=i2s=on
dtparam=spi=on

Hallo jacgri24,

das Thema ist schon etwas älter aber vielleicht hilft die Antwort trotzdem jemandem. 

Bei meiner Recherche habe ich leider auch wenige Beispiele zur gesamten Verkabelung gefunden und deshalb die beigefügte PDF erstellt. Dazu muss gesagt werden ich bin Maschinenbauer und kein E-Techniker. Falls jemand Vorschläge für Verbesserungen hat oder gar einen Fehler findet gerne schreiben dann kann ich die Grafik entsprechend anpassen. 

Die Darstellung ist bewusst einfach gehalten um auch für Anfänger ohne E-Technik Erfahrung verständlich zu sein. An meiner Maschine kommen Antriebe von JMC (CL Stepper und Servos) zum Einsatz. Für die Verkabelung habe ich ein Kabel von Lapp mit 2x1 und 4x2x0,25 eingesetzt. Den genauen Typ werde ich nachreichen.

Bei Gelegenheit werde ich die Verkabelung der Spindel in einer weiteren Grafik darstellen. Ebenfalls habe ich Etiketten zur Beschriftung der Stecker erstellt. Das macht die Verkabelung etwas einfacher. Diese werden einfach auf Klebeetiketten für Umschläge ausgedruckt und dann mit der Schere passend zugeschnitten. 
Die Idee dazu ist nicht neu es gibt hier im Forum bereits für einige Karten entsprechende Aufkleber jedoch  habe ich für die 7i96s bisher keine Vorlage gefunden. Falls jemand Bedarf hat gerne melden. 

Grüße 
Erwin 
 

Doesn't work as the RPi4 image was not created with SPI enable and no way to enable it
Menu-config does not have kernel option
Thus a 7c81 is still useless unless you do a debian install, compile the RT kernel, install LinuxCNC

Hi Lcvette,

It's indeed a alternative controller, once it finished.
This can take a long time. Some are good coding day's, some are bad coding day's without good progress.

It turned out, modifying lcnc's code to do thing's i would see accomplished is almost impossible.
Best reason is entanglement.
Then just writing new code from scratch is 10x faster to get things done.

There are no goals for me. It's just a project to try out new things wich got my interest's.

It's not the purpose to outsmart lcnc or something like that. Or claiming thing are better etc.

Altrough it is interesting to find out differences in lcnc and this approach.

Like this has bi-directional hal pins and used modern boost interprocess for shared memory.

Today did a mayor bug fix. It turn's out that multiple shared memory regions updated by thread's, would not exchange data
properly. Even when mutex etc. was set.
In the end it worked by using a single shared memory region for all thread's.

Does anybody know of a plug-in (does LinuxCNC have these?) that will control lathe spindle speed.
In theory the calculation is simple - the spindle RPM should be inversely proportional to the tool position X value (absolute so that it allows for both front & rear tool posts) and it would be useful to have an option to stop the spindle during a tool change. There should be a variable to allow for different materials too. Simple enough but how would I go about writing it if nothing already exists?
Thanks in advance

Hello,I followed the instructions provided in this forum thread for setting up EtherCAT with LinuxCNC.The installation and configuration seemed to go well; however, I’m facing an issue where my motors are not moving. Specifically:

• The values from STATUS word from the drives is not appearing in the LinuxCNC - 0x000000
• When I start LinuxCNC with

  lathe.ini

  , LinuxCNC loads successfully, but it seems there’s no connection with the drives.

I’ve attached the following files for review:

1. dmesg.txt: Logs showing EtherCAT activity and errors.
2. Relevant configuration files (

   hal

   ,

   ini

   ,

   XML

   , pdos, ethercat master, slaves, lcec during linux operation)

I would greatly appreciate it if someone could review the attached files and help identify any mistakes or missing steps that need to be resolved.Thank you in advance for your support!Best regards,Piotr

Hi Fakename,

The executable "ethercat_twincat" start up with a default none name "EK1100".
See the mainwindow : node_ethercat = new graphics_node("EK1100",ports);

A better name should be something like : "Ethercat".

seems to show the correct process data objects, so I'm not sure what's going on.
This is nice. That means the digital xml config is parsed succesfully.


Maybe this is not the best way to start figuring out things for you.
Best for you is maybe a minimal example where ethercat is showing your pdo config in gui, without
the usage of node's etc.

Then set some test values, to try to run the motors?