Advanced Search

BINGO, adding the halui line did the trick. Thank you PCW and spumco, you guys are amazing (and lighting fast responders).

After my last post I was trying "machine-is-on" in the lines WITHOUT hm2. I tried your replacement and the result is M3 and M4 no longer do anything. No error.

#net spindle1-enable => hm2_7i76e.0.stepgen.04.enable
net machine-is-on hm2_7i76e.0.stepgen.04.enable

Even tried with the same "=>" and still same behaviour.

Do I have to do something with my regular spindle hal entries for it to play nice?
net spindle-enable => hm2_7i76e.0.7i76.0.0.spinena

PCW wrote:

Simply replacing:

net spindle.1.on hm2_7i76e.0.stepgen.04.enable

with

net machine-is-on  hm2_7i76e.0.stepgen.04.enable

Should fix the issue.
 

PCW - I didn't see the halui signal machine-is-on in his HAL file; maybe I missed it.

OP - if that signal is already in your half file, do what PCW posted.

If it's not already there, you can tweak it to this:

net machine-is-on <= halui.machine.is-on
net machine-is-on => hm2_7i76e.0.stepgen.04.enable

I can confirm this fixed my stepgen spindle after PCW suggested it to me last year.

Simply replacing:

net spindle.1.on hm2_7i76e.0.stepgen.04.enable

with

net machine-is-on  hm2_7i76e.0.stepgen.04.enable

Should fix the issue.

Adding MAX_REVERSE_VELOCITY did the trick for M4 commands. Thanks.

Yes, I do have an abrupt stop with M5 $1, completely ignoring my acceleration parameters. I wonder if there would be any benefit in disabling my stepper motor driver (cheap DM542T) just as the M5 is issued. On one hand, the freewheeling could be more harmful than the coil being energized hard to stop, but on the other hand if the workpiece is delicate, freewheeling for however short of time as it can give it a better chance of survival.

If it's still a bug and 2748 is closed, is there a newer issue open? Does someone have a patch perhaps? Is this my opportunity to dive into the code? 

Thanks for the response. That's what I'm worried about, that they would do things in some weird way that will make it harder to modify. Disappointing if that's the way it is.

The thing is that I don't have time to build the hardware from scratch(base/frame/ ball screws, linear rails electrical cabinet, enclosure, door, etc.) but I do have a good budget, so I'm looking to buy a mill so I can just modify it to make my parts and get started ASAP.

I started looking at Haas, SYIL, etc. but got worried that I might be too locked out of the control to make it work the way I want. That's when I found Tormach and thought since it's based on LCNC I would have the best chance of being able to tweak anything I might need to.

So, I guess a standard LCNC install could work, but I'd still want to buy a mill of some kind. I suppose I could still buy a 1500mx or any mill really, and then install vanilla LCNC. Is that what you were suggesting?
I might keep that as a back up plan, but try to roll with pathpilot first.

Thanks for any thoughts!

So it looks like the drive is software-configurable.

I'd suggest going back to basics and connecting the drive to a Windows PC and verifying all the drive settings via the drive tuning software.

SIDE NOTE: make sure the motor's encoder count (1000/4000) matches what the drive is expecting.

Set the dip switches to 'software' (i.e. all ON). The reason is that you can (probably) set the microsteps to a useful number in software and are not limited to one of the 200/800/1600/etc values as with dip switches.

This will allow you to set the microstepping to a value that makes the steps per spindle rev a whole number, making the math for LCNC much easier.
Since LCNC's rotary axes units are set in INI [TRAJ] ANGULAR_UNITS = DEGREES, you need the [JOINT_N] STEP_SCALE to be in steps per degree.

For a 3:1 belt reduction and a 1.8deg motor, if you set the microsteps to 2400/rev (12x microsteps), you will wind up with 20 steps per spindle degree.

If you find that 12x is too fine and the positional accuracy is kinda 'ish', you can go down to 1200/rev (6x) and adjust INI to 10 steps per degree.  That might give the drive a bit more of a chance to hit a particular position rather than somewhere close-ish on either side of the target.  Either way you're still below the encoder's resolution so the drive isn't going to be totally guessing on a position.

And while you're in there, you should adjust the drive's following error tolerance.  I've found that Stepperonline's drives have a following error alarm set extremely high.  As in the motor could be 1/2 a full rotation out of position before it alarms out - not OK for CNC use.

oh sorry

No double posting, both topics merged due to attachment missing on one of the topics.

20 rdy missing?

15 oz+
14 ob+
13 oa+
11 da ground gnda
10 as-
6 brk
5 alm
2 drive disabled cwl
1 aclr
30 oz-
29 ob-
28 oa-
26 as+
23 do com
17 drive disabled ccwl
16 son
31 com+

Hello, what connections are needed for the 7i97t?
I have this spreadsheet, and these are the connectors.

has no rdy
 

I dont thimk so. when i checked the ini file, there was nothing under Traj, so i added AXES=4, and it worked

Is rdy needed?

In the lay out the X arrow is not correct as it is to the negative, not positive as mine is.
So remove the input pins and put 0.0 in the 3 locations you show, I will try that.
In a new config for the Y axis.
Thanks