Advanced Search

Your driver is probably too small.

It's only rated for 2.8A peak. Your motor is rated for 2.8A RMS (4A peak).

You should have a 4A driver, not a 2.8A one.

You don't necessarily need full motor current, per se.

I actually recommend setting the driver current slightly below the rated current to reduce motor heat, if you can get away with it.

But maybe you can't get away with it!

Try this:

Set the driver to max current, fewest microsteps (lowest number of steps/rev).

Set the power supply to max voltage (not over 45VDC) and max current.

Try putting the biggest capacitors rated for above the supply current across the power input terminals to filter the power supply.

I currently have it on my test bench with a DC power supply set at 24v. Depending on what is doing it typically is drawing around 0.25A. if i turn the current knobs on the power supply it doesnt increase at all.

I have the switch on the driver set to D which according to the data sheet is 2.8 peak or 2 RMS which is alot more than its pulling. Should i switch this to 0-4 according to the datasheet thats about where my current draw is.


I just tried plugging 625 into the arduino code (its not on the machine yet) and its about 1.125 spins.

this is the process I followed to set up a hyperterm 85 SYNC
1 Make sure the Z axis is properly calibrated including trabvel switch if any.
2 Make sure table is properly laveled, so the plate to cut is always perpendicular to the torch
2 From hyperterm Cut tables select a metal plate in the midle range of the plasma power supply and set up the parameters in the proper tool.
3 Disable any THC feature including THC itself.
5 Cut a line of a length that allow you to record the voltage on the screen (May be 8 or 10 inches long), using the previusly ste tool.
6 Adjust the voltage scale to reflect the voltage in the cut table for that cut heigh.
You can repeat with a thicknes on the high range and then one in the low range and then make an average.
this method has worked to me don't need to many maths but for sure should be anothers that work.

What voltage is your driver powered with?

What is the drive current set to?

What type of PSU is powering the driver?

Old-school transformer -> rectifier -> capacitor supplies are generally recommended over regulated power supplies.

Try getting some big caps that are rated for more than the supply voltage and soldering them to a proto board and power the driver through the board to see if power supply instability is part of the issue.

Perhaps filtering the power supply will fix, or reduce, the issue.

Low voltage and/or current can lead to lost steps which will cause weird stuff to happen.

Try out 625 for the steps/rev in stepconf.

Number of teeth might not work.

Enter this in stepconf:

Driver microstepping: 8(maybe 4)
Motor steps/rev: 600

Why the hell would the ratio be 37.49:11.99?

Why not 36:12 (3:1)?

So strange and annoying.

Also... Here is the LinuxCNC post processor from Inventor.

Hi Friends, 


- yes its a hybrid stepper, sorry for the misnomer, i've attached the data sheet of the motor and the drive.

I am using a GT2 timing belt and timing pulleys i got off amazon. The pulley ratio expressed as a fraction is 37.49/11.99. I just realized i should probably use the number of teeth instead which brings that fraction to 60/20 or 3, but this still doesnt get me to the 540 number any easier. How would one measure the pulley ratio with the actual belt? 

I was hoping that the belt system i designed wouldn't slip THAT much. I only have it rotating one way, as belts are good pullers not so good when it comes to pushing. I mean i even have a custom tensioner in there. I can upload cad photos if necessary.

So because i took the head off to redesign it i haven't put it back up on the machine and reset up the drive, all the numbers i am sharing are coming from the little Arduino script i wrote to test this. 


 

Thanks, Andy also made that suggestion. You are right, I am kind of used to thinking in G94. Need to reprogram my brain.

Hi,

So i finally have the tool probe and workpoint figured out (i think*).
Running the code i got from Inventor CAM, with the default LinuxCNC post I run into issues.
I attached the Z-probe and workpiece subroutines as well as the Inventor cam generated code.
It stops on the T1 M6 line (N25). But i can't seem to get it to go beyond that. Pressing the start/pause on the HB04 doesn't do a thing.
Commenting out this line moves the program up to line N60 and throws up error messages about the Z-axis running out (it wants to go to high).
To me it looks like the code has a different idea of where the tool tip is (in Z) than what it gets set at with the Z-probe routine.
Work order:
{The z-probe / toolsetter is fixed to the bed}
Mount the probe. (that's the XYZ probe)
Run the Z-probe to set it's tip.
manually move the spindle/probe to within the bounds of the workpiece probe routine. (The vice for now)
Run the workpiece probe routine (finally got it to set it's coords correctly and it moves perfectly above the corner.)
Then i manually move the spinde to a comfortable place to change out the probe for the tool (round paper lollypop stick for now).
I placed a piece of plastic on the tool probe to create extra Z offset for initial safety so the lollypop stick doesn't plunge into the workpiece (the vice).
Then i load the 19.091 cgode file and "press play".
It moves from the probe XY to a place that is NOT the coords of line N55
Then it runs line N60 and error's out on a Z-axis out of bounds. 13mm above the workpiece is well withing that actual range of my machine with the tool probed as is with the extra spacer. I checked this with the spacer on the vice and the tool touching it (simulating the tool touching Z0 on the workpiece /G54. And then move up 13mm and then i still have plenty of headroom before I run into the Z home/limit switch.

So the 2 issues:
Getting past the M6 on line N25
Correctly using the tool length (?).

* probing the workpiece often fails when i comment out the message and M0 commands, claiming the probe is in contact during rapid movement. Adding the M0 'pause' solves that. But that is not how things should be.
Also, i would like to be able to position the probe during the routine
lines:
(MSG, Plaats probe boven werkstuk\n Hou de probe ong. 5mm binnen de hoek\n en druk daarna op start)
M0                        ; Wacht op bevestiging
The M0 hold doesn't allow moving the spindle about.

Hi,
Linuxcnc works for xenomai 3 only as it is posix based (basically same code but linked to xenomai libraries instead of standard libc libraries)
Xenomai EVL, on the other hand, is not posix based and a wrapper for threads, mutex, etc should be coded

Regards

Hi Spumco,

I can't find any official documentation about caxis.comp, just many forum posts about it from you. Is this something new not in the documentation yet?

My goal is to make my CNC router use the rotary axis and simulate a lathe. I've actually already done this before moving to my Mesa 7i76e but using an external device with a dial ( amazon link ) to control the speed. I'd like to have that programatic control over the speed for obvious reasons. I actually have a YouTube video on what I did then. 

I don't need dynamic change between velocity and position controls. I'm more than happy to restart LinuxCNC with new config when changing operations.

Used keyboard matrix controller for bottoms on the controller cabinet. 
I disassemble a old keyboard and salvage the controller. the connection points has to be cleaned before soldering wires on it. "the black stuff" on the contact points are graphite with normal traces under.  

Keyboard bracket finished with room for extra bottoms and trackpad.