Advanced Search

Hey Bari do you have any pictures of it or so, plans. I was thinking about doing the same for my build.

Thanks,

Hi all. I think I have issues with how the paths are defined in my INI file. As for as I can tell they all point to the correct folder but perhaps not. I think the errors saying "pycall(remap.change_prolog) failed" reflect this but I am quite possible wrong. Can anyone see the problem?
I copied the nc files from the examples folder up a level. Should I go back to changing the path to /home/luke/linuxcnc/nc_files/examples/ ? 
Thanks
Luke 

Thanks for the hint, already did that but haven't updated repo yet.

I noticed that following joint error happens a lot when moving with encoder wheel on nvmpg even that gcode results in much higher speeds. For now I limited jog speed to 40mm/s.

Hello,i've followed this  thread and i've got the CCAT driver installed so far, but i was realy confused i've got so many warning while compailtion, so what...
The question is how do i mount or assgin the

Beckhoff pci ethcatmaster{(08:00.0 Unassigned class [ff00]: Beckhoff GmbH Device 5000 (rev 0)) => which seem is the interface for the onboard KL-modul of the plc/ipc }

as master device to the ethercat stack?
i add a copy of my terminal log

the actual master you see is an Beckhoff CX2500 module and runs good so far.

might anyone has an idea

kind regards,
Christoph

zelo, make your stepgen maxaccel higher than your regular max accel

To expand a little on Aciera's response...

Starting/stopping the sub-spindle is pretty straightforward, but as I've recently found there aren't many sub-spindle lathe configurations posted on the forum (or other places), so setting one up isn't really a simple cut-paste from someone else's config.

There are a couple of considerations if you are retrofitting (or building) a sub-spindle lathe:

• Spindle direction and main-sub synchronization
  • To make programming easier, the sub needs to rotate opposite the main when the sub is sent an M3 command.  If not, then back-working tools (for the sub) would need to all be programmed opposite than main tools.
  • This makes synchronizing the main and sub for a parting hand-off a little more complicated than just setting them both to "M3 Sxxxx".  I won't post the gory details right now, but on my DIY lathe (with sub) I created an M-code activated 'switch' that basically sends the main spindle's inverted position feedback to the sub's command input.
  • Result - when the synch M-code is activated, the main spindle is programmed and the sub is slaved to the main - both rotate at the same speed and direction until the de-activate M-code is triggered.
  • Both my main and sub motors are servos controlled via step & direction; I don't know how accurate 0-10v (or -10/+10v, or Ethercat, etc.) would be during a main-sub synchronization attempt.  
• Sub axis naming
  • LinuxCNC doesn't allow (as far as I know), axes to have an 'alias' applied.  If you're used to programming a sub's linear axis as "Z2" you'll have to get used to using a different letter.  LCNC can control up to 9 axes, but since the Z-axis is already (likely) the turret, then the logical letter for the sub's linear axis is 'W,' since UVW generally represent linear axes parallel to the primary XYZ axes.

Note that my lathe isn't finished yet and I've not done much cutting, but the main/sub config appear to be working OK... so take the above with a large grain of salt.