Since the both the pump and fans are meant to be used in PC's they are rated for 12 volts so I added a separate Meanwell 12V/2A power supply for them.

The power supply is constantly powered but I switch the output side using a solid state relay so that the cooling only runs when the spindle is on.

However the pump proved to be a bit noisy and way too powerful give the small diameter hose I'm running. So added a 7.5Ω resistor in series with the pump to bring the voltage down to 8V which made it much quieter and brought the flow down to a more suitable level.



With that done I tackled the cable chain along with all the wires and hoses.

 

 

With that in order I turned my attention to the stainless cover I had laser cut and CNC bent a while back. I had to manually make a cut out for the connector of the spindle servo which I had forgotten to take into account. But I think it came out okay anyway.

 

Fitted it with a rubber strip to cover the sharp edges.

 

Here is how the machine looks with the cover installed.

 

 

 

Thanks for the feedback dbtayl. Don't worry about clutter, forum threads like this are all about dialog and sharing experiences.

For some reason the final bits always take longer than expected to get sorted. I've managed to get the spindle liquid cooling installed and to somewhat button up the build for now.

The first challenge with the spindle cooling was the location of the inlet which is located at the back of the spindle flange.



I didn't want any hoses down there as the hot chips when milling steel could easily damage them. So I did a little workaround using an angled fitting and a bit of pipe originally meant for a grease based central lubrication system.



 

 

Next up I tackled the the cheap PC water cooling radiator I had purchased of Amazon. I 3D printed some wall mounts for it along with two fan grills for the Noctua fans.

 

Here it is mounted on the wall together with the pump/reservoir unit which I also purchased of Amazon. The yellow color is from the special type of antifreeze I use together with deionized water.

 

Hello,

I think I’ve found the reason for the reduced speed at F1000.
It’s the "MAX_FEED_OVERRIDE" setting in the .ini file.
When MAX_FEED_OVERRIDE is set to a value greater than 2.0, the speed is the same as it is for F5000.
Is this behavior intentional?


Gruß
Rüdiger

 

And just because i measured a lot, are all outputs Pull-Up's?
Do i need an Pulldown-resistor to make the card work? 

Strange behavior with the attachments, the files somehow have a date added..   The Bitfile is attached her..

Hi folks!
i'm trying to find my way getting anything to work.

Whats fine: Handwheel / MPG works, the encoder-Pins are on P1 of the MESA, which is working fine.
Machineaxis running fine, reference-switches work fine,
Funfact, The PWM-pin and the encoderpins on P1 are working, which gives me the feeling i forgot to setp something to get the outputs to work..

My Problem: I have a VFD which i wanted to control via LinuxCNC.
The PWM-Pin works fine, i have a 0-10V Card connected to it, that's fine.
But all my outputs to start the VFD or stop it, absolutely no reaction to my commands..

I have a cheap Mach3 Breakoutboard, which sets it's Outputs to 3Volts when nothing is connected, so i started to measure my way to the MESA-Card. At first i thought it is a Pulldownresistor story, but that changed nothing too..

Finally, my outputs 19 / Pin 2 DB25 and 21 / Pin 3 DB25 of the MESA-Card are always 5Volts, when i connect a Pulldown-resistor 1k to ground, i see 0,8V .
I can toggle these outputs ( when commenting out the usage in HAL ) via halshow ui, but still i see 5V. 0,8 if connected to the resistor.
No reaction.

I attached my konfig, and my Pinfile which is on flashed on the card, i had to rename it to txt for the upload..
The HAL-File for the VFD is named "bzt-fu.hal" , all the addf and loadrt commands are transfered to the custom.hal.I commented these out in the halfiles where they came from, just to make it easy to remember from where the loadrt or addf commands are coming from.

I start thinking i somehow fried the card.. Help welcome!
Greets, Tom

"Correct" is subjective. I'm aware of MTConnect, but most people don't have home assistant and would have to build interaction routes. This uses existing, free apps and free brokers to push messages to your phone with no real setup beyond the initial apt install. I don't need the full data available on a dashboard, I just want my phone to ping if the machine has stopped. This maybe my misinterpretation of MTConnect, but it looks like a lot more install/config than I really needed for a simple task (Unless I'm mistaken - what's the route to getting phone notifications for someone without HA/HA companion app?).

If I run a suite of 4 machines and want to port their info into a hub for monitoring, sure. For me, in my garage, I don't want to install and secure a public facing HTTP route, then figure out some form of polling/monitoring/MQTT broker to collect the info, then push it to my phone. With this, I install the phone app, install the .deb on the CNC machine, scan a QR code with phone and it's done.

AFAIK MTConnect isn't backported to the current stable build, or any previous, so this won't help anyone with an existing install unless they update to a dev/nightly build?

Might it be said that if there's a rash of these lately, there's a need outside the current offering (or poorly documented within that offering if it exists?).

After updating the mesaflash app, I tried starting mesaflash. No errors were reported, however, the output were not toggling. Checking the man page, I could not identify any option to keep the pins toggling until the app was cancelled. Since the electronics are located on the back of the machine it requires more that 1-3 secs to move from the keyboard to the board to measure the outputs. Checking currently running programs (ps -ef | grep mesa), no app containing the string "mesa" was running. Is there a hidden option that will keep the app running until cancelled?

However, checking all of the outputs, all voltages were sitting at 4.92 v. What are the next steps for diagnosing issues with the 7i76U?

Kind regards,

Ist Ok mein Bedienfehler habe den Hacken bei Längkorr G 43 nicht gesetzt….
Alles gut
King regarde
Jürgen

Hi jjdege,

Thanks for the info, SPDL was intentionally left out as I only wanted one problem at a time to work on.

I am using stepper-online steppers with Lichuan controllers and I expected a few problems.

The axis are now moving so I am looking at how to set up the Stepper-Online A6 servo set up in csv mode.

For now I would set your machine up for immediate homing. Its described here but also read the whole thing (about 8 times as its important)
linuxcnc.org/docs/stable/html/config/ini-homing.html

If you want to use internal homing by the drive, I would leave that for now and set up homing by LinuxCNC until you have a better understanding.

Ok so what changed was the PC I swapped it out from a previous issue with a dell PC. I made this configuration from scratch following my notes from last time. This is my setup for the z axis.
 
Also I tried hitting prob test and that works fine it went down into the metal like its supposed to

Hello,

I tried to place a PayPal order on the website and was unable to complete checkout due to technical issues on your end.

Shipping Name is a required field.
Shipping Name is a required field.
Shipping Street is a required field.
Shipping city is a required field.
Shipping Status is a required field.
Shipping Zip Code is a required field.

These form fields were properly filled in.
Can you look into the website issue?

ich habe jetzt ein bisschen mit KI rumprobiert. Im PP Modus hatte sich der Motor mal gedreht im CSP Modus nicht mehr. Scheinbar hatte irgendwie die DC Synchronisation gefehlt. Hier mein aktueller Stand:Wir haben bereits bewiesen:

• EtherCAT OP ✅
• DC-Synchronisation 1 ms ✅
• CSP PDO-Mapping ✅
• Code:

  0x607A
  über PDO erreichbar ✅
• Motor reagiert auf kleine CSP-Positionsänderungen ✅
• aktueller Fehler
  Code:

  0x603F = 0
  ✅

ich würde jetzt gerne G0 X10 in LinuxCNC eingeben und gucken ob der Motor sich dreht, aber ich kann keine Referenzfahrt durchführen. Und ohne kommt jedes mal die Meldung Bewegung würde pos Anschlag von Achse überschreiten.
 

Take the time to read the cia402.comp source and example. I was wrong, cia492.comp includes a pin to select PV (velocity) mode which is what you want. 

I'd probably edit the name in your XML to be S0 instead of D1. this will make more sense when assiging pins to spindle.0
There are pins for target_velocity and actual_velocity (encoder feedback) so you are getting close. I think that your spindle speed-cmd pin should map to target_velocity and be sure the encoder is properly scaled.
I'm not sure how to map spindle.0.on to enable the motor.
spindle at speed would use the near component between  target_velocity and actual_velocity
to capture a long list of pins you can add > pins.txt to the show pin command to write output to a file