Advanced Search

Just a side question: Why do you need a separate Controller for the manual operation?

Isn*t everything possible to do in the LInux CNC. Slaving axis, Using MPG to move the axis manually?

It doesn't require a tool changer to use as is. It does require the tool be in the table. It uses tool data to call for the tool.

Found it. yay. haha.

So that solves that.

On to the next problem... configuring it

First thing I’ll do is pull the hard drive and try to clone it.

I don't need wait_complete but was trying different things. With a simple M64 P0 it takes 5 seconds for it to command the pin. Feels like a config somewhere in the python plugin maybe?

remap.py:

The hardwired diagram shows two normally open contacts in series  KM1 AND KM2 indicating that the Estop is active. The rest of the circuit is similar to what you had in mind. Please do not add a screen (UI) estop or reset buttons; make it a habit to only use the external hardwired estop and reset push buttons otherwise you defeat the use of a safety system. The hal block diagram I use it to generate the hal file but it might help you understand what the hal net file does.

 

#

---

# Load realtime Components and their counts

loadrt and2         count= 1
loadrt edge         count= 1
loadrt or2            count= 1

#

---

# Add functions to threads

addf and2.0         servo-thread 
addf or2.0            servo-thread 
addf edge.0         servo-thread 

#

---

# Set parameters

setp edge.0.in-edge          0
setp edge.0.out-width-ns   20000   

#

---

# Connect Pins with Wires

net external-ereset        and2.0.in0  
net external-estop         or2.0.in0  
net n.1                           or2.0.out  edge.0.in  
net n.2                           edge.0.out  halui.estop.activate  
net n.5                           halui.estop.reset  and2.0.out  
net soft-estop-active      halui.estop.is-activated  and2.0.in1  
net software-estop         or2.0.in1   

I believed I did all of that, got the Tools from the Probe Basic Library. Created a Conversational for facing like the video, set a tools offset, and then generated the Gcode. The tool path was within the Machine Box, and from all accounts should have worked. Just would not run the gcode as generated. And I missed your "learning question" 

Thanks. I started learning the Gcode, and understanding what it is trying to do. I noticed that the Tool changing is included in the initialisation of the GCode.

So I adjusted the Gcode to exclude the Tool change, and off it went. Thanks for the poke...  

Is there a way to exclude this from the gcode generation? I'm sure there is a simple way until I get n ATC.