Advanced Search

Hi,

let you know the links in deb install are faiing.. kcjengr.github.io/probe_basic/quick_start.html repository.qtpyvcp.com/repo/probe-basic-...0.6.0-24.dev_all.deb
Fail to find
repository.qtpyvcp.com/repo/qtpyvcp-dev/...4.1.2-77.dev_all.deb
Fail to find.

Redone from Old gmoccapy and all working correctly. So will try from there.

I would not permanently enable the pwmgen with setp  but rather enable it by
connecting it to spindle-on as shown.

Inverting the PWM output and using the STEP- pin is needed because it guarantees that the
PWM pin is low before LinuxCNC is running, during power up, and after a fault (watchdog bite)

This is controlled by the homing parameter settings in the ini file:


linuxcnc.org/docs/html/config/ini-homing.html
 

How’s it going.  So, I'm trying to make my mill use only one limit switch for both the minimum and maximum travel of the table.  Every time the machine is homed the table moves to the minimum hits the switch it then does a second shorter slower home cycle but then parks with the switch engaged.  How do I make it so after the last short slow home cycle it then parks so the switch is not engaged?  I need to have it parked off the switch so I can configure it to also serve as my max travel limit switch.  If I’m configured for the same limit switch to also be the max I can never move the table after it has been homed. 

Which setting or file do I need to modify to make this functionality so lates say immediately after homed move slowly till the switch is disengaged?

 

ooh ok thanks

yeah oversight, should be channel 1 if im using step/dir4

# Enable PWM generator on channel 1
setp hm2_7i96s.0.pwmgen.01.enable true

or do i not need this command if im replacing it with the invert

# invert pwm output
setp hm2_7i96s.0.pwmgen.01.out0.invert_output true

to get the most out of qtdragon's tool handling, you need repeatable tooling and premeasured tools.

With Tormach TTS tooling, they sell a small granite plate
tormach.com/small-granite-surface-plate-...tool-hole-31713.html
And you use a height gauge to measure the height of your probe and your tools
en.wikipedia.org/wiki/Height_gauge

TTS can be used in R8 and MT3 spindles found on small machines, many people use at home.

This does work a treat when you have it all set up.

There's no information that I can recall for cross compiling Linuxcnc.

When compiling Linuxcnc for the RPi platform (4/400 or 5) I've either done it natively or via QEMU.

For those that are unaware Buildroot is a cross compiling system for building Linux file systems, generally aimed at embedded systems.

Dave2024 wrote:

I bet you just sold allot of Mesa 7i76e's with this video!  Cool, thanks

Nah, but perhaps PCW did!

I bet you just sold allot of Mesa 7i76e's with this video!  Cool, thanks

there is an error in the commandtry this, it doesn't give me any errors

Hi everyone

So I am also trying to setup an Ethercat drive (Stepper) from Lichuan CL3-E86H. These are my first steps with Ethercat, so far I only worked with MESA cards.

From reading through the thread Lichuan (servo) drives seem to be working now. Is this correct? Is it relevant which firmware the drive uses? (I got mine delivered two weeks ago). I have not yet checked the version.

I still get the PREOP + E message when starting Linuxcnc. Also have an EK1100 running on the same loop, which works fine. XML is from page 6 or 7 of this thread (which is supposed to work). I can clear the error by manually putting the drive into PREOP mode again.

Plugging in the cable won't work because LinuxCNC gives an error when the drive is not connected on startup.

The address settings on top of the drive does not seem to affect the address in the ethercat slave listing.

Dave

EDIT: So I was able to fix the problem by changing vendor ID to : 00000766 and PID to: 00011000.

In the ini, under Versaprobe there is Diameter. Maybe you can add below HEIGHT = nnn and use it as #<_ini[VERSA_TOOLSETTER]HEIGHT>
It could look like this:

I will measure this from Z0 to table top but, what's the VAR that I add it to?

I just realized, there is something missing. You need to know the distance from   #<_ini[VERSA_TOOLSETTER]Z_REF>  (-183.97) to table surface. This must be added to toollength. Then you can work with table as base.
I think the toollength probing result you get now, is wrong by exactly this value.