Advanced Search

Hello,

I've been following this topic for a long time, great work.

I looked at the jerk with the Hal oscilloscope, there seemed to be outliers.
see image. 

Hi Daz, no issues from my side. I'd probably do the same if I had time.

Well, that was quick. The customizations are all applied. The update script did a good job, but did miss one thing, in case anyone cares: the main HAL file for my mill led with the following loadrt lines:
I think the final "[TRAJ]AXES" should have been changed to "[KINS]JOINTS", at least if I'm reading the update_ini code correctly. But it was not, leading to "Ini variable '[TRAJ]AXES' not found".  Please correct me if I'm wrong, since I've made the change manually.  (For the record, my config file had no [EMC]VERSION line.)

So now all I need is for USPS to deliver my Mesa card.

This work perfectly for me using version 2.9 (Thanks a mil JT !!) My setup uses a Logitech (old) Xbox USB controller to work

Does this help?
linuxcnc.org/docs/html/man/man9/carousel.9.html

Hi Craig!

Those are insane machines! Great job!

Are them all controlled by LinuxCNC?

Hello, could you share these files?
The link has been deleted

Hello, could you share these files?
The link has been deleted

Hello, how are you?
Did you save these files?
I saw that you deleted the link.

Is there a place that has instructions for new users on how to set up an ethercat machine once lcnc and ethercat is installed?

Yes, the docs make it pretty clear I should start with a fresh install.

I'm wondering though: My wheezy-based 2.7.4 system is still running on my old PC. It's been fairly heavily customized, with a custom PYVCP panel addon, a custom POSTGUI_HALFILE to support my gamepad wand, and a custom HALFILE which is used to square up my axes, and which depends on a halcompile'd module (Thanks again for your help, @rodw: forum.linuxcnc.org/10-advanced-configura...rors?start=10#106073)

I'm thinking perhaps I should do a fresh install of 2.9 on the old PC, and get it running all of my customizations on the new release, before moving over to the Rpi+Mesa setup. Just to separate the tasks somewhat. Does that make sense? Or maybe that would just make needless extra work.

So when lines have no intersection, there is no extra torsion turn.

that's quite interesting.

RDA wrote:

Please note that the signal in the drive P1 connector is inhibit, so when the input floats the drive is enabled. This means that in order to disable the drive, you need to provide 5V (from P1 #1) to P1 #11.
For a machine like that, I would just wire a single ”enable” to the drives. Either use the existing relay (most likely NC contacts between P1 #1/#11) or reverse the logic in lcnc.
Relay probably better so that drives are disabled when there is no control to the relay.
 

I did this on my recent mill conversion.  I set up a 3-pole double-throw relay that was activated by the E-stop circuit.  The relay's NC contacts make the disable connection.  When the relay is energized by the control coming out of E-stop, those contacts open and enable the servo amp.  The 3 relay poles make sure there are no connections between the separate servo amps that could cause some crosstalk.
Jon

I would use the higher resolution, perhaps increase the following error limits
and proceed to tuning.

If you have oscillation, reduce your P term.

For velocity mode drives, most of the tuning is setting the correct FF1 term

If you set the analog scaling to machine units per second at 10V, FF1=1.00

You can change the PID values live with the "Calibrate"  window.

I think it's pretty damn cool myself.

JT