Advanced Search

Are you still using the above attached config files? They are missing home switch inputs in hal, and Mesa inputs are in the wrong place.
Make a new config, this is to messed up.

I'm still using the BT40 spindle that this machine came with. However getting the preload right for the spindle and getting the upper bearings for the quill drive to like high rpm milling for prolonged periods has been a challenge. I've been planning to replace the spindle for quite some time but not really taken leap yet.

However after fiddling with the spindle for sometime I've realized that I have to set the preload when the spindle is really warm in order to get a preload that works.

This in turn requires me to do few minutes of spindle warmup at lower rpm when the spindle is cold before I can crank up the rpm. Else I get a really nasty oscillating sound from one of the upper bearings.

Here is a video of the spindle at 3200 rpm roughing 6082 aluminum with a long 24 mm indexed end mill.



This has became a favorite tool for roughing aluminum as it has good reach, removes material at a decent rate and the 1003 inserts are cheap and readily available from many vendors.

Individual homing does not work.

Could it be that I am not using the correct version of LinuxCNC?

No, any version of LinuxCNC from 2.8 on will work with the 7I76E

Like I said you need to check


hm2_7i76e.0.7i76.0.0.spinout-minlim  
hm2_7i76e.0.7i76.0.0.spinout-maxlim   
hm2_7i76e.0.7i76.0.0.spinout-scalemax 
hm2_7i76e.0.7i76.0.0.spinena-invert  

 hm2_7i76e.0.7i76.0.0.spinout
hm2_7i76e.0.7i76.0.0.spinena

with halshow

In axis, you can run halshow with:

Machine --> Show Hal Configuration --> Watch

And also verify that you have +10V on the 7I76E SPINDLE+ pin
(TB4 pin 3) relative to SPINDLE- (TB4 pin 1)

 

Fast-forward 3 years, and FreeCAD is over the version 1.0 hump and the topo-problem has been resolved.  Seems many are still finding it hard to use effectively; perhaps a generational-gap between traditional (geometric) CAD and modern (parametric) CAD.

For 2.5D work from traditional CAD, take a look at QCAD-CAM:  www.qcad.org/en/products/qcad-cam
A quick CAM tutorial:  www.qcad.org/doc/qcadcam/QCADCAM_Tutorial_en.pdf

These pages really don't show off all the features and capability... QCAD is the mothership of the illegitimate LibreCAD; a full-featured (paid) CAD package which should be familiar to anybody with old-school CAD experience.  Free trial version available, reasonable cost / you own it, no cloud, no locks.  Import/export .DXF and many other common formats; has layers, line styles, hatching, blocks, extensive snaps / geometry / tools, dimensions, etc.  With the CAM add-on, there are like 50 pre-defined gcode export styles, including MACH and LinucCNC in both metric and imperial.  It also has an ECMAScript (JavaScript) post-processor that can further tweak the gcode to your heart's content: qcad.org/en/92-qcad-cam  It has an active user forum, with currently 43k posts and seven languages supported.

I'm gonna revive this thread as I'm running into the exact same issue as Ikavan describes.

My g-code files are stored on a Samba and when I open a file from the share in LinuxCNC (Probe Basic in my case) it gets locked.

If it would be possible to add a configuration flag in the INI file or somewhere else that makes LinuxCNC load the file to RAM and then close it to prevent locking I'd pay 200$ without hesitation.

Next step would be to add "Reload" button in the GUI to reload the currently open file. The would save a lot of time during the iterative process of testing new g-code programs.

 

drive.google.com/file/d/1lh_3pexmAgHTyC0.../view?usp=drive_link

Could it be that I am not using the correct version of LinuxCNC?



 

@Aciera
Pecking too small takes too long but I'mma give it a try, my setting was about 1.5 diameter first peck then reduce 2-3 mm till reach 0.25 diameter

I actually tried to keep the layout minimal, including only the essentials.

We've been doing CNC retrofitting for many years, and this layout emerged based on our experience.

unknown wrote:

Like the inclusion of the USB port.
Looking good, wishing many successes.

Did the design and layout come because of the way you work or what would be familiar to someone used to working with big name machines ?
I'm just a hobbyist with a work background in labouring on building sites, they don't trust us with anything that has more than one button or trigger

Thanks friend,

unknown post=335115 userid=42198The connectors do look a little askew, but I just put it down to maybe being a pre production prototype, hand soldered maybe.
Actually IMHO not really worth mentioning.
Sorry not having a lot to say, ethercat is not a technology I can afford to play with.
In saying that I can appreciate the time and effort involved.
Good luck

Like the inclusion of the USB port.
Looking good, wishing many successes.

Did the design and layout come because of the way you work or what would be familiar to someone used to working with big name machines ?
I'm just a hobbyist with a work background in labouring on building sites, they don't trust us with anything that has more than one button or trigger

The connectors do look a little askew, but I just put it down to maybe being a pre production prototype, hand soldered maybe.
Actually IMHO not really worth mentioning.
Sorry not having a lot to say, ethercat is not a technology I can afford to play with.
In saying that I can appreciate the time and effort involved.
Good luck

All the Hal files are useful, with what you supplied there is no telling how your mesa card was setup.
More time wasted with using AI. You don't requires script to assemble the logic for a simple pendant with buttons and an mpg, it can all be done via Hal.
A mesa card does require a seperate Hal component to be loaded for an encoder, if you are using the on board encoder and don't require it for any spindle speed or position feedback. The encoder Hal component is usually used with the parallel port, when no encoder is available, ie with with a mesa card, tho you could set one by using mesa input pins as would you would do via a parallel port.

To tell the truth I did write a Hal component that takes the count from a encoder on the mesa card and some other pin inputs for scale and such, but this was just a way to simplify the Hal file for myself, it is not really required, all the connections can be made using seperate Hal components.
If you do want to use a script, the best way to get the values of the input pins and the encoder counts is to simply create the pins needed.
I would honestly browse the forum, I'm sure a topic came up recently regarding a configuration for a pendant.
Forget AI for Linuxcnc, I have seen some very upset people when it is pointed out the code produced is more or less useless.
One reason for the concept of Hal in Linuxcnc is so that a non programmer can just join this bit to this and this bit to that without having to indulge in programming.

Now my thoughts usually don't run in an ordered manner, what you best might is to describe by words, schematics, drawing on the back of an envelope, blackboard or for us more of a Luddite bent maybe a drawing on a cavewall. Once we know how you want to connect this bit to that bit answers will come.
But yeah read the docs, have a browse of some of the supplied components and see what best fits what you need to do.


What follows is the ranting old man, can be ignored. Or hysterically laughed at.
It does seem quite ironic that AI isn't a great help with a project such as Linuxcnc. CNC controlling the machines and AI replacing the use of the human mind.
Once humanity achieves Actual Intelligence may Artificial Intelligence maybe of some use.

"On the way"
PCB is in production now

On the way,

We will use our EtherCAT 32x Digital IO Board with this panel,