Advanced Search

I'm going to assume you are using Debian as you haven't said you are using something else.

sudo apt-get purge package-name

Generally if you right click on a deb file and select "open with gdebi package manager" it will install over the previous version.

This page may of be of help as well.
www.wikihow.com/Install-DEB-Files

Hi ntc490 and egemens,
thanks a lot for these scripts, here is the version that works with windows. My first python script (change) so handle with care!
Reads the local tool library and exports it to the Desktop.
Make sure to convert your cloud library into a local one before, if you only run it on the cloud.

Don't have a fancy github, so here it is - feel free to host it together with the other one or adjust to handle Windows too

Are you using limit switch at end of travel as a home switch and limit switch? (Combined home/limit switch).

LinuxCNC does not know where the hard limits are.
After homing, it knows where home is, and allowed travel in both directions (MIN_LIMIT and MAX_LIMIT).

So you don't tell LinuxCNC where the maximum hard limit is because there is no point - the only time you encounter a hard limit is when something is wrong. If your machine touches a hard limit, this is because LinuxCNC does not know where it is. For example lost steps or interference issues.

The homing docs explain these concepts with helpful pictures.
linuxcnc.org/docs/master/html/config/ini-homing.html

I have this in the usercommand.py. It is working fine

Not sure if this is thread necro, but what if using a Haimer 3D probe rather than an electric touch probe integrated into LCNC? I cant use a probe sensor pin as the inhibit, as it is a purely mechanical probe.

To restate the original question, is there a way to inhibit the spindle based on a certain tool number from the tool table? I will make my Haimer probe tool number one, and reference all other tools from it's offsets.


Cheers,
Mark

Terminology might be an issue.

LinuxCNC uses the term MIN_LIMIT and MAX_LIMIT
These define the maximum travel LinuxCNC will allow/perform
These are soft limits - they are set in software. Soft limits = software limits.

Hard limits = hardware limits.
Usually set by limit switches, or sometimes hard stops.

LinuxCNC needs to know where the axis is in the world / in its travel.
This if what homing is for.
Homing switch can be outside the soft limits or inside the soft limits.

Where is your home switch (in relation to axis travel)?
Where are your limit switches?

Could you explain what is the difference from Marco's implementation? From my point ow view, same file usage in ini and in hal. 

Yes, the components seem to me to be identical. 
1. set the 'joint.n.request_custom_homing' pin for all joints, which presumably sends the homing command to the drives through hal.
2. wait for the 'joint.n.custom_homing_finished', again presumably coming from the drives through a hal connection.
3. Zero the position values and homing is finished.

'home_offset' is not implemented.


[edit]
So i'd suggest you try the modified component I posted above regarding the implementation of 'home_offset' value and report back. Just remember I can't test anything regarding EtherCAT including homing so you'll have to supply as much feedback as possible.

[edit2]
Regarding switching between DEFAULT and CUSTOM homing, is there a hal pin coming from the drive that indicates whether the drive needs homing or do you want to do that manually with a custom gui panel button?

Installed my ATC spindle finally after figuring out why it was overloading. It seems fine, except that it seems to not have the power it should. I assume I botched some settings with all the messing around I've been doing, but I'm not sure what.The spindle is 1.5kw, 0.24nm torque, 60,000rpm, 220vac. However my drive is restricted to 600hz or 36000rpm.As a result I have set the motor voltage to 132V which is 60% of 220v.At idle the spindle uses about 1.4 amps, which is roughly what is expected. Full rated amps is 5.132v at 5 amps is about 900w, which is a bit over 1 horsepower.However, at 5A, I am getting only 2 cubic inches a minute of cutting volume before the spindle begins to bog. Math says I should be getting 5 cubic inches per minute (machine rigidity notwithstanding). So I'm missing basically half my power it seems.What settings should I be looking for to rectify this? The drive is a durapulse G10, which is a stripped down verison of the delta MS300. It is running in vector control mode. The drive will not autotune for some reason, it overloads. I suspect there are some motor parameters I need to manually enter in for it to behave but I'm not sure. My other spindle (also a delta ms300 drive) just autotunes and works as expected no fuss.

I used the files from the firs post, so that is why was an error...
I thought they are the same with the github v3.0, but not.
Now the LCNC is starts. Will test it later.
Thanks!

Hello there, 
I have a problem with my Mesact 2.1.3  when I click to launch the tool, it gives me multiple errors with a message that says to remove and reinstall a new package. The problem I am currently having unable to delete it from the file manager. Every time I right-click on the.deb file and select remove, it won't do anything. my question is how can I delete it from the terminal so I can install the new version 2.1.4. 

thank you 

I'd love to piggy back on this, since I have a similar journey.
I tried the MS300 driver in the current linuxcnc-ethercat/linuxcnc-ethercat package.

I initialized the VFD using a single ethercat-conf.xml line:
This gets me a slave that is OP and all the pins the driver support within linuxcnc. I followed documentation to connect the pins within hal. Also in reference to: github.com/steup-engineering/sbs625-cnc-dk-schlemper. I have also tried the init commands but I have to admit: I don't understand how they work.

What I get puzzles me:
- I have sent S1000 followed by M3, this gives me 1000 rpm and 16.667 rps.
- VFD shows on front display 333.33: Given that it is a 4 pole spindle 33.33 would be correct, but it is an order of magnitude off.
- The VFD will not start. LCEC pins for the MS300 as exposed by the specific driver stat-volt-enabled, stat-switched. stat-op-enabled remain low even though *.enable is high.

I have set up the MS300 via USB interface beforehand and have validated that the spindle works. I would dare say that I trust the spindle related parameters to be correct.

ethercat pdos and ethercat slaves -v appear to be to be in good working order. PDOs shows the expected SMs and all registers one would need.

At this point I am lost.

I suggest we move the discussion about Ethercat drive homing over to the other thread, as we are starting to run things in parallel here:
forum.linuxcnc.org/ethercat/52968-help-n...c-servo-homing-setup

You could either use analog or step/dir
pncconf knows how to setup either mode.

Analog has the advantage that its electrically isolated
but would require and external 10V supply
(most VFDs supply this but servo drives typically do not)

thankyou for the reply, i will try this again as id given up trying to get this to work on my machine

Do you have a program loading on startup?   Typically we load a program file named blank.ngc, it's located in the probe basic examples file.   Try copying it to your nc files folder and setting it as default program in your ini.   This initializes vtk on startup.