Advanced Search

I want to start my saying that I have been using Linux for 34 years.  That sounds like a big number but Linux has been around for longer that that.  The first time I ran Linux I down loaded it from a friends server over a modem.  It was 52 3.5" floppy disks.  I was going to collage studying computer science at the time.  Now I have a degree in computer science.  You don't need a degree in computer science to get EtherCAT working.

I designed and build a CNC router 12 years ago.  My original system was LinuxCNC.  I struggled to get everything work for several month but I did get it running.  A friend had build a CNC router at the same time and changed his system to Mach3 so I switched my system to that.  Everything worked but I never really trusted the system.  I managed to get some jobs that paid enough to pay for what I had invested.  I made many things for my self as well.  I could never get past the trust issues so eventually the router went into hibernation.  It hasn't been running for 8 or 9 years.  Now to the meat of the story.

I started reading about LinuxCNC and came across this forum and learned about EtherCAT.  It sounded very interesting so I started reading about it and decided I wanted to resurrect my CNC router.  One of the problems I always had with my system was loosing steps.  I did some research and found that the prices of a closed loop stepper system had reduced dramatically.  So I started planing out an upgrade to my system.  I started buying components.  My first purchases where a Beckhoff EK1100, EL1008, EL2008, and an EL9184.  In addition I bought a Meanwell NDR-240-24 and a NDR-480-48.  The NDR-240-24 to power the Beckhoff components and the NDR-480-48 to power a LiChaun CL57E-4A with 4 NEMA 23 3Nm close looped steppers.  I have yet to receive the LiChaun components.

Knowing nothing about EtherCAT I started reading.  This is the most important part if getting EtherCAT running.  I installed Debian 13 and LinuxCNC per the instructions provided by rodw.  Thank you Rod!  I don't know what I even started with but I got the basic configuration files in place.  The system recognized all the Beckhoff components.  I had my proximity sensors from my original system so I tried to get them working.  This is where my software development skills kicked in.  I use VS Code daily along with AI.  I opened my configuration folder in VS Code and started asking AI to help.  VS Code is a free open source development environment that can be installed on Linux.  With in a few hours I had my proximity sensors working.

I am fully aware that not everyone has my background in programming and using VS Code or AI but it has proven to be an invaluable tool for configuring LinuxCNC.  I will be receiving my driver and stepper in the next few weeks and will report my progress.  This path may not be for everyone but if you have any experience using VS Code with AI I highly recommend giving it a try.  I have found it to be incredibly helpful in getting started.  With that said, the most importing thing to do is RTFM! Read the F*ing manuals.

I hope this help someone!

 

I vaguely recall back some 10 or more years when i was doing VCP panels for everything, i read somewhere here that GladeVCP will ignore inputs if not selected or "in focus" so i never ever used it.
If i press ESC, i want the machine to stop, i do not care if "in focus" or not, it HAS to stop.

I hade the same issue with GladeVCP an Jogging already years ago. I was not able to fix it permanent: forum.linuxcnc.org/21-axis/33925-glade-p...is-blocks-arrow-keys

It made me finally give up with GladeVCP and "downgrade" to a good old PYVCP sidepanel.

Best wishes

Jan

I wrote a lengthy bit on tool offsets here:
forum.linuxcnc.org/38-general-linuxcnc-q...ets-be-stored#342300
it might help a little. Took me a while to "get it"
What I ended up doing is probing each tool and subtracting an arbitrary absolute Z height from the absolute probe Z, so every tool has a "length" that's relative to an arbitrary spindle position. It means no more reference tool, but it also means I always measure tools when I pick them.

OK so I do need help ive tried using this gcode to setup tool measurement but not getting accurate results from first tool I zero off work coordinates go through the gcode but the next tool comes out a few mm above work piece maybe more i didnt mesure the distance but in the gui window its at zero and in the G offset its zero.

What am I dong wrong ?  Please can someone give me the correct way of doing this.

Thanks Fred



g49

(measure reference tool)
G91
g38.2 z-190 f250 (measure)
#1000=#5063 (save reference tool length)
(print,reference length is #1000)
G90
G0 G53 Z0 (Retract to safe height)



(msg,insert another tool)
M61 Q

(measure next tool)
G91
g49
g38.2 z-160 f250 (measure)
G10 L1 P#5400 Z[#5063-#1000] (set new tool offset)
(print,new length is #5063)
G90
G0 G53 Z0 (Retract to safe height)


 

Greetings gentlemen,

Our team at EreborCore (based in Peru) recently acquired a legendary piece of Swiss iron: a Mikron WF 40 P from the 1990s. Mechanically, the machine is in pristine condition (beautiful Meehanite cast iron, silent ball screws), but we are doing a complete electronic retrofit to bring it into the 21st century.

First of all, I want to give a massive shoutout to user @Vojta333. We found his Google Sheet detailing the 8-bit logic for the 21-speed gearbox on the WF 40 C, and it is a masterpiece of reverse engineering. We already have the S and M bitcodes (J2/2 to J2/9 pinout) ready to be integrated into our controller's custom Ladder/PLC logic. 

However, we have encountered a historical "ghost" regarding the "P" variant, and we would highly appreciate your collective expertise on two specific matters:

1. The Mystery of the "P": Does anyone have the official electrical or mechanical manuals specifically for the WF 40 P? While the "C" (Contouring) version is widely documented, official schematics for the "P" version seem extremely hard to find. We would love to know the exact technical differences.

2. Gearbox Actuator Design: On our WF 40 P, the shifting mechanism on the side of the head looks like a small, enclosed manifold/box. In some older WF 40 C videos, the mechanism looks slightly more exposed. Does anyone know if Mikron switched to a compact hydraulic shifting manifold for the later "P" series, or is it just a cosmetic/protective cover for the same relay-driven mechanical array?

We are completely modernizing the system: we are getting rid of the old analog electronics and installing a brand new, fully digital SZGH controller along with modern AC servos and drives. 

We are extremely excited about this project and we intend to fully document and share our retrofit journey here with the community. Any advice on the documentation hunt or the gearbox manifold would be gold to us!

Best regards,
Daniel
EreborCore Team

hallo an alle da drausen!
ich bin neu hier
kurze erklärung bin von mach3 auf linux cnc umgeschtiegen, hab mir ein plasma cnc schneider gebaut für hoppy anwendung dieser machte mit mach3 über usb port immer wieder probleme beim starten, (hochfreqenz e klar), daher jetzt linux über pararell port mit einem "TB6560-3V2 china port
soweit so gut funktioniert alles wunderbar, nur das relais aus pin 14 laut port funktioniert nicht habe schon alle versionen probiert , endweder es zieht immer an oder halt nie...
hat jemand eine idee woran das liegt?
danke im voraus

Just so we are on the same page:

1. Are you sure your tool directions when jogging are according to the right hand rule ( tool movement as seen relative to the table)
 

2. After homing the machine which end of the axes is the tool located (ie is it at the positive/negative end of the machine axis)

Ok, I found my one mistake. i was trying to compile "5axiskin.c" but it didnt work so after reading more, I found there is "userkins.comp" file need to be compiled. so i edited file as per attachment and getting error as per screenshot.


 

Hey everyone,
Has anyone been successful in configuring an XYYZ setup and would be happy to share their .ini and .hal files, and possibly the EC500 JSON config file (if modified)?

I've reviewed the suggested example files and mine seem to be correct for a dual Y axis motor gantry, but it's not working correctly and I'm chasing my tail trying to figure it out, so time to ask for some help! If possible!

Are you still stuck? I have some python scripts to load the firmware onto the board using Windows and powershell. Sometimes you need to power cycle the board a few times to validate that it connects.

Pardon my brevity,

Here is detail

I'm trying to compile this kinematics file "5axiskinsN.c" and getting this error

cnc@cnc:~/linuxcnc/configs$ sudo halcompile --install 5axiskinsN.c
Compiling realtime 5axiskinsN.c
Linking 5axiskinsN.so
objdump: section '.rtapi_export' mentioned in a -j option, but not found in any input file
/usr/bin/ld:5axiskinsN.ver:2: syntax error in VERSION script
collect2: error: ld returned 1 exit status
make: *** [/usr/share/linuxcnc/Makefile.modinc:124: 5axiskinsN.so] Error 1



 

In the screenshot of the first post the view is that of the real machine, with x0 y0 at the top right but y moving away becomes negative and if I modify the axis to make it positive, home moves to the left and the backplot is mirrored.

You are looking at the wrong Z.

None of those on the pictures are his.