Advanced Search

Better info here
cnc.zone/hardware/controllers/contr-mk3
and here
cnc.zone/tng/tng

There is a demo download, ask the guy from Norway to download and test.
If he is hooked on it he should try it.

Hello gentlmen,

excuse me but have anybody active project with in the moving stage and can share basic code configuration files please?

I am very interested in the this topic because I am working with Metronix ars servo on my table over profibus and finally I have finished with internal acceleration generator and I need to come with external refrence which should be genereted as I think from the component out of @Grotius workshop ...what and which should be declared for basic workbench setup

Really thank you for your experiences ... that SJOB from @Grotius is MAGIC

Regards... 

Hi Arciera,

The scurve planner takes the [TRAJ] trajectory acceleration : MAX_LINEAR_ACCELERATION = 200
When tpAddLine, tpAddCircle is done, it gives this 200 value to the planner.
The scurve acceleration max is then 2*200=400 at inflection point.

However the planner does not lower the acceleration to a specifik max joint acceleration at the moment.
We have acces to all joint max acceleration values.

We could reduce max acceleration to satisfy max joint acc. We implement this without any problems.

If the acc in the ini file is 50, the scurve is max 2*50=100 at inflection point. This is normal.

But the acc-cmd value reaches ~180?


[edit]

I did do a 'git pull' and reran './installer' but I can check again tomorrow.

Hi Arciera,

Thanks for feedback.
If the acc in the ini file is 50, the scurve is max 2*50=100 at inflection point. This is normal.

However. I run the same file, and i got no spikes.
This is the first corner :
 

Maybe you did not update the clothoid lib? U used clone recursive wich is needed.
Or git is messed up.

For sure i just did a push for scurve planner, clothoid lib, scurve as up to date.
That's annoying when you have 3 repository's depending on each other.

Hi guys, the thread has been dormant for a while, but I had implemented homing to max "Z" in the meantime. The challenge is now, that depending on the position of the tail stock, it could be in the way of reaching the max "Z" position. I assume, that this is different for a classical CNC lathe, but since I have a conventional lathe converted to CNC, the tailstock is an issue I have not thought about.

How do other people deal with that ?

Just to expand on what Grotius and Hakan have pointed you in the right direction as they are totally correct for how things are done today, and you are thinking of how it was done the old way.

I remember your name and I'm sure you were using "ec-debianize" and you are most likely still use to the old way of how it was done.  Things changed a few years back as "ec-debianize" has been deprecated and therefore the "sudo update-ethercat-config" command is no longer used.

Just to clarify a little further, you don't have to do a reload for how things are done today whether you do a full source build or Rod's Repo install.  Neither way requires a reload after the install as once you do all the "systemctl enable and systemctl start" commands from the install, then it works over and over and what is confusing you is that you are use to doing a "sudo update-ethercat-config" after setting up the ethercat.conf file.  Trust me, it's fully burned into my brain also... I will never forget that command LOL.

Also this command was used for 2 purposes back in the day.  #1 was for loading the ethercat.conf file and getting E-CAT working from a fresh build, but #2 it was also if you had a setup with startup hardware/permission issues.  So, if you did an "ec-debianize" build and once everything was installed but yet when you did a "ethercat master" you would get a "Failed to obtain number of masters... ", so you could do a "sudo update-ethercat-config" to get it reloaded and working.  For some reason, an ec-debianize build would once in awhile not work on start-up and this was an easy quick fix instead of doing a reboot of the system over and over until the master worked.  If you have this issue with Rod's Repo install or a source build and need to do the same type of fix, use the "sudo chmod 777 /dev/EtherCAT0" command as this will do the same as "sudo update-ethercat-conf" to get the master up and working.  None of the other commands will work for this problem as I have checked all the different ways.  I have several setups that work flawlessly, but I have 2 with hardware issues and this is the quick fix to get the master up.

Hope it helps.
Robert


@Grotius and Hakan: Alway's glad to see you guys here helping us all.