Advanced Search

Yeah, nice relay/opto isolation is how I have now learned is a way better way to be doing this. Those exact arduino relays are what I use in some of my home IoT projects that I have started months after this CNC was begun.

I've applied some topics I have explored at work that involved signal analysis and curve best fit at 400KHz sample rates and very low voltage and taken some bad conclusions from that in the design of this machine's controls.

My main priority with this post is to confirm that I am not doing something dumb with my ini/hal and that my errors are from voltage latching oddities and not code. I can explain purchases and delays to my wife if I made a mistake, it's a little harder to justify when I only think I have made an error

Thanks for your insight.

5V. GPIO without modification, Mesa default voltage with an inherent 3.3v swing. It's triggering my steppers well doing a 5v to 1.7v swing from high to low. You can see in my configs how I am doing inverted output to get clean steps with sinking vs sourcing. I don't have space in the box for another PSU and the daughter cards, and I am out of time to putz with an ideal solution.

I'm mostly asking if I've done something dumb from a code perspective, and if there is a good way to be more reliable with voltage swing. If my configs are correct I can swap to 5V source and invert my sink/source and be just as voltage tolerant as my step generation.

Professionally I use 3.3v signal logic with a 2.5v swing near amperage's that are an order of magnitude higher than here. I'm a little surprised to see the default as "just go for higher voltage" as my training has more leaned towards isolation being optimal. Again, I am out of my depth on this topic for CNC control so any disagreement or confusion is entirely intended to be constructive and for the purpose of learning.

Hallo,
ich habe mich gerade hier angemeldet weil ich auf eure Hilfe hoffe.
Ich bin recht unerfahren was die Boards für die Fräse angeht.
Also ich habe meine Fräse schon eine ganze Weile und die lief eigentlich. Dann stand sie eine Weile weil mein Projekt beendet war und sie somit nichts zu tun hatte.
Nun wollte ich mal wieder was machen und komischer Weise ging nur noch eine Achse...komisch, aber naja.
Also habe ich mir dieses neue Board gekauft, in der Hoffnung ich brauche an der Verdrahtung und den vorhandenen Anschlüssen, Steckern und Kabeln nicht so viel zu ändern. Es ist mir auch wichtig, das alles auf einem Board ist, also keine extra Driver Module.

Also ich habe mir dieses hier gekauft:
www.amazon.de/Bordstromschalter-%C3%9Cbe...ef_=v_sp_product_dpx

Hier ist ein Foto von dem Board und der CD die ich bekommen habe:
photos.app.goo.gl/hJcqZ8UT4fSkTniS6
photos.app.goo.gl/3wevH6N61yGsL3yE8

Das Problem ist, das auf der CD alles mögliche drauf ist, aber keine Beschreibung zu dem Board welches ich bekommen habe.
Nun weiß ich nicht was ich wo anschließen muss und was ich in Mach3 einstellen muss.
Ich hab ja nun auch keinen Treiben, das ding ist ja per DB25 Port angeschlossen.

Ich hoffe ihr könnt mir da helfen?

Danke
Matthias

 

If you bought the card from Mesa after March 2025, it will already have up-to-date firmware

The firmware is available from Mesa's web store (in the specifications tab of the 7C80)

Hi,
Where can i get the updated firmware?
I have connected the 7C80 to raspberry Pi 5.
Thank you,

Not the same, stat-at-speed looks for two bits in the statusword from the drive.
There is a genuine mistake made there.

But actual speed should work nevertheless, I'll take a look at that also tomorrow.
Do you see any actual speed from the lcec.0 component?

Hi Hakan
thanks for your help , I'm using the cia402pv component you put together, I can't seem to get the drive to feed back the velocity of the motor could this maybe be another issue ?

I seem to have made a mistake in the cia402pv component with the stat-at-speed pin..
I'll look at that tomorrow. If you just want to mill you can comment out the spindle-at-speed signal and
setp Spindle.0.at-speed 1
 

Did you start the spindle with M3 or M4 first?

Try this:

Put M3 at the first line of your program.

Run some random G0 commands to wait until the spindle reaches full speed, then run a G1 and see if it works.

Perhaps the spindle actually just is not at-speed yet.

Hi everyone,I’ve recently finished mounting my machine to its base and tidying up the wiring, so I decided to try running a quick program to see if everything was working properly.Machine Configuration:

• Controller: Raspberry Pi 5
• Servos: 3 × Leadshine EL8 servo drives with 400 W motors (EtherCAT)
• Spindle: 1 kW StepperOnline drive (EtherCAT)

The program starts fine, but the machine seems to get stuck at the first G1 command.After doing some reading, it looks like this could be related to the “spindle-at-speed” signal in the HAL configuration.Because I’m using EtherCAT, I’m not sure where this needs to be handled:
Should the spindle-at-speed signal be configured in the HAL file, or Is it something that needs to be set up in the .comp file for the EtherCAT drive?

Any guidance or examples on how to handle this signal within an EtherCAT setup would be really appreciated. when the spindle is running currently I am having no feedback from the drive to record the actual speed ? 

PCW wrote:

Searching the forum for MPG will finds a number of MPG implementations and hal file examples.
 

Or you could've read the docs.
linuxcnc.org/docs/stable/html/examples/mpg.html
skip using the encoder and use the mesa MPG terminals

some examples form my machines, see on the right side a row of 3 relays, those are for inputs and they isolate the machine part from electronic part, so less interference and no need for good shielded cables (i can no find good cables here):
forum.linuxcnc.org/show-your-stuff/38547...uild?start=30#165873
Or the "arduino" relays as seen here
forum.linuxcnc.org/show-your-stuff/38547...ild?start=110#172157

tommylight wrote:

Found another one
blog.loriowar.com/how-to-reduce-jitter-on-linuxcnc

This one at least mentions network latency. In my view this is more important than system latency where you are not using software stepping.

That should work. It's a 16-bit encoder counter so be prepared to handle overflow.
TIM2/TIM5 are 32-bit so better to use that when you do your own. There is only one 32-bit though.
 

I added the following HAL code to the configuration of my mill to keep the spindle on for a few seconds after the spindle is disabled just to get the nice smooth ramp down you are looking for:

# --- timedelay before disable spindle output for deceleration ramp --- #
loadrt timedelay names=timedelay.spindle-enable-soft-stop
addf timedelay.spindle-enable-soft-stop servo-thread

setp timedelay.spindle-enable-soft-stop.on-delay 0
setp timedelay.spindle-enable-soft-stop.off-delay 3

net spindle-enable => timedelay.spindle-enable-soft-stop.in
net spindle-enable-soft-stop <= timedelay.spindle-enable-soft-stop.out
net spindle-enable-soft-stop => hm2_7i96s.0.7i84.0.0.output-01

For more information see my post here: forum.linuxcnc.org/12-milling/50559-opti...sion?start=70#309845