Advanced Search

Good evening @ my1987toyota,  Thank you for your valuable advice, I understand your explanation on the X and the Y axis. I can picture that in my head.

This Nema 23 motor and the associated driver is only hardware I have, I bought just a single one so can be familiar with the wiring and how stepper motor works.

Originally, I was thinking of Mach3, whereby I can use a cheap, around $AUD 20.00 BOB, and readily available. But LinuxCNC looks more appealing even though it is a bit more involved. I have seen videos where they run motors and spindle with LinuxCNC without any mechanical parts. I would like to take this path as well, once I understand the electronics, I will think about getting the mechanical parts.

I will heed advice and will be reading the LinuxCNC manual I have seen videos on it but I have not done a lot of reading yet.

Thank you and best regards,

...behai.

 

  Well first off welcome to the wonderful world of CNC. Firstly I recommend you read through the Linuxcnc manual, that will get you
going in the right direction. I don't have direct experience with using Raspberry Pi and Linuxcnc. I usually use the Dell Optiplex 9020
and MESA boards
however I recommend using 8 micro steps for most installs. That said you can run the full gamut from full step to 200 micro step
if your driver is rated to handle it.
  Next NO you don't have to run the exact same step setting on all drivers. You could use a belt
drive for one axis, for example a Y axis at say 100 micro steps and a ball screw axis, again for example X axis at say 8 micro step.
At that point you change your step counts in you ini. file accordingly or in your software wizard either Pncconf or Stepconf.
That way you should have accurate calibrated movements on your axis.
  You will have a lot of questions along the way everyone does, so don't get discouraged by it. I would recommend you run a few
simulated setups and play with the system to see how things work before you do your build.
  Lastly keep your build as simple as possible an gradually add in more complexity later if you so desire. It helps keep the
overwhelm from getting to you. I hope this helps and good luck with your CNC endeavors.

Rodw

Thank you just what I needed.

I appreciate your time in creating this.

Cheers

Parameter können nicht mit HAL pins geändert werden.

Aber warum nicht einfach einen stepgen (stepgen.N.velocity-cmd) verwenden?

hm.. und es ist nicht möglich irgendwie die Frequenz zu regeln?
da ich so aktuell 'pwmgen.n.value' auf 0.5 setze, habe ich ein top Rechteck-Signal, so wie ich es brauche.

Habe es als alternative mit einem PDM-Signal versucht (pwmgen.01.output-type 3), jedoch ist da auch nicht immer ein Tastgrad von 0.5 gegeben und zudem ist das Signal nicht konstant (weiß aber noch nicht genau ob die geringe Abweichung etwas ausmacht)

 

I subscribed to them all!

I couldn’t find any video explaining the pipe cuter though. What kind of motor did you use and how did you set it up?

Hey, no problem! I appreciate the hard work you do for this project!!

I increased the deadband to 0.01 and switched the position back to Actual. The jumping of the numbers stopped and the motors don't make that weird noise anymore. I will test it with the oscilloscope, but I am sure that brought me one step more where I want to be. I wanna say that the motors are not stalling as early anymore.

I played around with the PID settings and thought this would help with the problem, but no change so far.

'pwmgen.pwm_frequency' ist ein Parameter, der ist nicht zum Einstellen der Drehzahl dazu ist 'pwmgen.n.value' .

Vielleicht hilt dir das hier weiter:
forum.linuxcnc.org/39-pncconf/38723-pncc...p-pwm-on-7i96#162320

tommylight wrote:

Anything else you look might seem cheaper, it is not, and they will be extremely limited in expansion compared to Mesa.

 

Trying to get a feel for this but I'm a bit overwhelmed.
Is it possible to use my own motion controller with LinuxCNC? I am only interested in closed-loop servo and I want to handle the PID myself. 

Craig

hab die *.hal und *.ini im ersten Post angehängt.
Benutze eine Mesa 7i96s und habe das bitfile angepasst, sodass auf dem step-gen_4 die PWM/Dir Ausgabe stattfindet. 

pwmgen.0.pwm-freq lieferte den gleichen Fehler.
Sowie ich gelesen habe ist die Frequenz für alle PWM-Generatoren gültig, darum wird die "0" weggelassen

Check in the ini TOOL_CHANGE_POSITION = 0 0 0. The third digit (Z) will be added to the length of the tool and will show the excess.

Thank you for your reply.

linuxcnc.org/docs/2.9/html/user/user-con...gramming-the-planner

I have read the following document, Naive CAM Detector section.
"Naive CAM Detector
Successive G1 moves that involve only the XYZ axes that deviate less than Q- from a straight line are merged into a single straight line."

As you said, CAM seems to only work on XYZ? Is there any other solution? except 'output longer segments'.

i get like before

My PC is a Dell Optiflex 3040

That is likely because LinuxCNC falls back to one-line lookahead for moves involving any other axis than XYZ. This means that velocity is no longer blended over multiple path segments. The motion planner sets the speed as to be able to stop the movement at the end of the next segment which means that the shorter the segment the slower the speed.
This is an internal limitation of the current motion planner, as a workaround for multi axis gcode generated by CAM it is usually recommended to output longer segments.

Hi,

I am trying to understand the Nema 23 closed loop CL57T driver. I have zero knowledge of CNC and stepper motors. I am learning with the objective of building my own CNC.

The manual for the driver: www.omc-stepperonline.com/download/CL57T_V4.0.pdf

The factory setting for the Microstep Switches are:

SW1 = ON, SW2 = OFF, SW3 = ON, SW4 = ON

This "Microstep 8" factory setting requires 1600 pulses per revolution. In my Python program, if I send in 1600 pulses the motor makes one revolution: I just observed that by eyes only.

When I set the switches to "Microstep 1": SW1 = ON, SW2 = ON, SW3 = ON, SW4 = ON

Then I send in 200 pulses and the motor makes one revolution: but it runs very fast compared to "Microstep 8".

I understand the relationship between switches and pulses. PLEASE HELP WITH THE QUESTIONS:

- When we use this motor and this driver with LinuxCNC, how do we set the Microstep Switches?

- Must all drivers' Microstep Switches be set the same?

Please pardon me if the questions are ignorant, all I have currently is LinuxCNC installed for Raspberry Pi 4B. I don't have any other relevant hardware, so I can't try anything yet. I am just trying to understand the basics.

I've attempted some settings, I have a video showing the speed at different pulses:



Thank you and best regards,

...behai.