Hi Cofhal,

Thank you for your purchase.

1) Full 3D Toolpaths - Adaptive Clear, Pocket Clear, Z Level Finish, Parallel / Raster Finish dont get surfaced by Feature Recognition. They are for whole part or selection by face or chains.

2) After Feature Recognition is done, you can hover over each feature and it lights up on the model. You can keep the model semitransparent to better view buried features like holes.

I will create a detailed thread on our community forum where you have already signed up in case you need more details.

What is the best way to contact Todd. Sorry I am new to the forum.

Email me at clark@sprout-kids.com and we can take it from there.

I have some electronic diagrams for that one; they might be useful to you.
www.illianaindtech.com/PartsBook3-14-14/...00guid.htm#ALostSink
Try talking to Jerry at JB cnc repair in New York. He knows the controls very well. Since most anilam controls were a retrofit he may have an idea where to find you more info.

gbouvier2.wixsite.com/website/anilam-parts-book

I’ve purchased the license and am testing the program, but I have one remaining question. When automatically generating machining tasks, I noticed that it doesn't detect any 3D tasks. Another issue is that, upon generating these tasks, they cannot be viewed on the model until the toolpath itself is generated; sometimes, it’s hard to tell which machining task was created, making it difficult to select the right tool.

Thank You !

Yes, the installer is also a live system so run it up, select live and run your tests  It won't save any settings between sessions so I just  usually install Linux and test on the PC itself.

If your spindle is on a VFD, you can save 4 pins by using mb2hal and Modbus RTU from a serial port (forward,reverse, PWM, at speed). By using HOME_SEQUENCE you can reduce the number of inputs required by sharing a single pin for homing. You also gain torque feedback, a more noise resilient system and much more accurate spindle speeds. You don't loose anything. People mistakenly think you need 0-10v spindle control for rigid tapping. But that's not right. In LinuxCNC spindle control is not real time and with rigid tapping, Z axis motion is synchronized by the spindle encoder.
But for the sake of a couple of weeks, why not wait for a mesa card?

tommylight wrote:

tuxcnc wrote:

"Ethercat is faster" is not a valid argument,...

He did not say "faster", he said more efficient, and even that does not seem correct to me from what i read around here, no experience with ethercat yet except rare services of machines using them.
I am intentionally refusing to use ethercat until something is done to have proper feedback, so far it does not work or it does work with big delays.
But, i would really like to have the redundancy it may offer, for now only in showrooms.

I think you are out of date Tommy. Grandixximo has done a lot of work and maintains an improved version of Ethercat specifically for LinuxCNC and also ahs done changes to the core code in LinuxCNC that improves how the Ethercat thread and servo thread sync on startup. Drive feedback form the encoder is just another variable on the Ethercat bus.The included lcec-configgen will build the xml file for you.

The system I use is a Compaq Presario Desktop having 3.3 GB memory, AMD Athelon 64X2 dual core processor 4200+ x2. 
Linux 12.04 setup says 32 bit os.  Its 196 GB hard disk currently setup with the rtai kernel booting on one partition  and Ubuntu 24.04 LTS booting on the other partition.  There's about 80 GB left on either partition.  The mill I have is a Taig 4019 3 Axis  and a cnc rotary table, so its a 4 axis machine.  The mill controller board is a xylotex XS3525/8S-4  which supports 4 stepper motors.  The Taig mill has no sensers and neither does the rotary table so testing feed synchronization isn't (as in tapping) easy.  As far as updating is concerned I'd liketo replace the 24.04 LTS with a linux cnc kernel that still supports my mill but don't know if one is available and the rtai kernel continues to work so the only thing wrong is interrnet access, I keep the net shut of when running the mill with the rtai kernel anyway.  The system is cabled through a router that's supposed to be 100MB/sec.  I don't know how much disk space may be needed if we're rebuilding kernels or Axis from source code, hopefully 80GB might be enough  Also I don't have a lot of code ready to test the synch between linear motion and the cnc rotary table which I mostly use for sharpening endmills. If testing the rtai driver means sending some code to be installed on the rtai partition, I can do that too, the 24.04 LTS machine can read and write in the rtai partition but the rtai os doesn't understand the format of the 24 partition.

5 Axis is a separate product and will not have 3+1.

Will the 5 axis product line include the 3+1 lineup? or will it be designed directly for 5 axis toolpaths?
Is there an upgrade path from 3+1 to 5axis when released? or new purchase required?

I am about to get a RapdiChange type tool changer running. (thanks to haskins-guitars/linuxcnc-rapidchange  for the code with some modifications) The Tx M6 stuff is all working but editing the tool2.tbl file is a pain (each tool needs a pocket # from 1- and then of course after editing you have to restart PathPilot.
The Tooledit gui is the answer but given that Mint 17 is rather ancient I was wondering if anyone has gone through this process already.
PathPilot recently moved to GTK3 so that is a bonus.
Standalone version is fine, it includes a Reload button to reload the configured tool2.tbl file.
The goal is to load up the toolchanger with tools for a program, edit Tool2.tbl, reload it and then run the program.