Advanced Search

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.

Hi, there's some additional config parameters that can be used to configure the DMA stepgen. "Step Length", "Step Space", "Dir Hold" and "Dir Setup".

From the HBS86H data sheet:

PUL: pulse width should be longer than 10μs
DIR: signal should be ahead of PUL signal by 5μs at least

Therefore I'd suggest these settings in your config.txt as a starting point.

"Step Length": 10
"Dir Setup": 5

The normal stepgen runs at 40Khz so most drivers are happy with the step form being generated.

Seems easy enough, the board has all the pins written on it, so wire a power supply, get an old PC with parallel port and install LinuxCNC from the downloads page, wire the Xclk and Xdir and the rest of Y and Z, test.

Getting this working again.
Poor Phil has been sitting still for 6 years.
I dont know why its named phil.

Its a "training machine from back when.
real solid. Looks skimpy, but it suprised me when i got to test run it.

 

The hal/ini files look basically OK

If you start LinuxCNC, enable the spindle, and set a say 1/2 way up spindle speed

Then running this command in a terminal wndow should provide debug information to post here:

halcmd show all | grep spindle


 

PCW wrote:

Standard 7I96S firmware has 4 built in MPG quadrature counters
overlaid on the first 8 isolated inputs. This means you do not need
to decode individual inputs (which is important since they are typically
only read at the 1 KHz servo thread rate)

The MPG counters have names like:

hm2_7i96s.0.inm.00.enc0-count
hm2_7i96s.0.inm.00.enc1-count
hm2_7i96s.0.inm.00.enc2-count
hm2_7i96s.0.inm.00.enc3-count
 

That's great news.

Thank you

I had the same issue. I did not want to reinstall with internet. I hope this is the only issue caued by that.
Here is how I solved it:


By just overwriting the signature with the latest.

M.De post=317431 identifiant utilisateur=41690

beauxnez post=317414 identifiant utilisateur=22230Merci, je ne sais pas si je l'ai bien fait mais j'ai reçu un message d'erreur.
C'est un avertissement, pas une erreur. Vous pouvez généralement le corriger
en copiant le fichier libusb.dll (bibliothèque de liens dynamiques libusb) dans le chemin de votre installation Python.

Remarque : si vous avez téléchargé Python depuis le Windows Store, vous devez copier libusb.dll dans le répertoire C:/windows/system32.

in the directories VS2013,VS2015,VS2017,VS2022 there is a libusb-1.0.dll in each folder

Your hal/ini files did not get attached.