Advanced Search

The enable is a 5v differential input.
The Manual says:
"Enabling signal: This input signal is used to enable or
prohibit; In addition, it can be used to clear the drive alarm.
When ENA + is connected to +5 V, ENA-is connected to
low power, the drive will cut off the current of each phase
of the motor so that the motor is in a free state, where the
pulse is not responded and the alarm can be cleared; When
this function is not required, the energy signal end is
suspended."

If you have limit switches, why not just home the machine, and set actual soft limits? Everything you are describing is the exact reason to do it that way...

I played around with some HAL components and Classic ladder and I managed to get it working. I used a combination of Timedelay and Or2 to get the m6 command to change tools in mdi and auto. I also had to change my signals for iocontrol. I used classicladder to time the jog fwd command from the carousel component, leaving enough time to unclamp first.

Thanks for the help.

What are the specifications of the enable input?

You may be able to use a 7I77 field output if it will take say a +24V signal
 

As I mentioned, if you want a 7I77 analog configuration, create a 7I92+7I77 configuration
(with either pncconf or MesaCT) and when done, change the boardname in the ini file from
7i92 to 7I95.

Note that following errors are expected until you get the encode scale correctly, in the proper direction,
proper feedback direction, and tuned. This is why you typically set the following error limits quite wide
in initial testing. After the basics are set up you will need to follow on of the tuning guides.



 

Thanks a lot! 
if I understand correctly, you mean the FW is fine for using either step/dir on 7i95T or Analog on the 7i77? All I need to change is in ini, if I at some point have to/want to change motors?

i made it a step further. sadly the mesact tool also knows nothing about that card match, I used the 7i97T in the tool to get a basic Hal/INI and search/changed 7i95 to 7i95T. wich also wanted to startup. I kind of hacked something together. Now the machine starts at least, I see pins in halshow. so a win I guess?!
The conig is quite minimalistic. I just added the Axis xyz. the idea was to start with the basics and just go step by step - adding outputs and inputs later on, to minimize error.

my idea was to just have axis, jog them, watch for +10/-10v output in halshow.

sadly I already ran into another issue I don't quite understand. hope it is fine to ask another question in this thread. 

The issue: I can "power" the machine and as I try to jog an axis I get "follow error". I don't see any feedback/encoders configured. why?!
Also I don't see any voltage output on the analog ports. maybe there is something wrong with my ini/hal or I am looking in the wrong place in halshow. I don't really know...

I share my Hal and ini if someone wants to take a look

I see why that should work.

The problem is that, because the machine is homeless, I set the soft limits to about twice as much as I actually have. This means I can home wherever I like, then set up G54, and it just works, without ever having to move to an actual home position on startup. And I can usually tell if my carve will exceed limits, so it's usually not an issue.

I'll think about changing that workflow.

Well, that's one way to skin the cat.

If you struggle with PathPilot and the USB IO, maybe a combination with the PLC would be the best solution.  Use the last remaining high-speed input and output to trigger the PLC to do the automation stuff and report back to PathPilot?

I'd imagine the cut-off saw spindle motor could be triggered by a USB output, since that can just run all the time.  And the saw motion connected to as the "A" axis so you can control saw infeed speed.

Let the PLC handle the clamping/unclamping, stock advance, and remnant eject, and then signal PathPilot to continue the G-code loop.

theslawek wrote:

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

Thanks for reporting back, and glad to hear it's sorted out.

BTW, the "=>" and "<=" in the line are just characters to help the user visualize the pin to signal connection.  They are not required, and are ignored by LCNC.  I personally find single-line HAL entries nearly impossible to read, but breaking them up in to multiple lines does make for a much longer HAL file.

For example, the single line:
net machine-is-on hm2_7i76e.0.stepgen.04.enable halui.machine.is-on

is the same to LCNC as:
net machine-is-on  <= halui.machine.is-on
net machine-is-on  => hm2_7i76e.0.stepgen.04.enable

It's worth a try, but...

Did you actually disable AMT?

Still don't know where base.tmax" and "servo.tmax" come from.
These are suspicious as they do not exist in a standard LinuxCNC installation.

if I change the VFD to manual control the spindle works fine. Testing the 10V spindle out seems to be fine for the 1 second then drops to 0v. The machine almost always goes to "Machine Off".

The question then would be why you get to the machine off state. (this will certainly turn off the spindle)

If you start LinuxCNC from the command line, are any errors displayed?
 

Not tested, but try:
-home the machine at MACHINE 0 limits with G53
-jog the machine to PART 0 and touch off with G54
If you have the machine limits set correctly in the ini file, if any move would exceed the machine limits, LinuxCNC will show a warning asking you if you want to continue, do not continue if this happens.

I'm working on carving a piece that's really a little too big for my mill.  It barely fits if I rotate it 45 degrees, and carve it that way.  But the size and rotation make it hard to be sure no movement will exceed the machine limits, and sure enough, about halfway through a carving (a draft practice run, happily), I tripped a limit switch.

(I should clarify that my machine is "homeless".  "home" is always relative to the piece, so there's no way for the interpreter to know in advance that I'll be exceeding a limit.)

Are the program's extents (min/max X, min/max Y) available in variables that could be used by a canned subroutine?  I did a quick skim of the source, but didn't find anything obvious.

I connected the 7i77 to p1 and the 7i78 to p2, i assume this is the correct order.
I've tried to modify the hal so that the z-Axis is the stepper connected to the first interface of the 7i78. The encoder for the z-axis is connected to the 7i77. Is this more or less done correctly? (hal is attached).
Since the 7i78 has no enable signals for the steppers, is it possible to use the enable pin from the spindle, since i am not using this? and how do i need to mod the hal?
Thanks! 

Vielen Dank für die Rückmeldung
Welche Version hast du? 8gb?