Re: [Emc-developers] tool database in python
My discussion was to bring to light how Lathe tools are normally used so that a database might keep them in mind when hashing out a protocol. My 'complaint' about linuxcnc offsets for lathes was to point out it's suboptimal, not that it wasn't possible. Using g43.2 to add wear offsets works for sure.. but it a hack and doesn't allow proper standard support in screens. I certainly don't suggest we eliminate g43.2 functionality though. From: andy pugh Sent: June 29, 2022 10:13 PM To: EMC developers Subject: Re: [Emc-developers] tool database in python On Fri, 24 Jun 2022 at 02:46, Chris Morley wrote: > > Different edges of the same tool is done by having different offsets, not > tool number. It certainly _can_ be done that way, but I see no reason to preclude doing it a different way. And (as delivered) LinuxCNC does not handle T11 to mean anything other than Tool 11. If you allow more than one tool in one pocket then you can use M6 T1 G43 / M6 T2 G43 to get the same tool, same pocket, different edge, without having to remember where you kept the second-edge offset (or, more practically, without having to tell the CAM software to use an offset that does not match the too) -- atp "A motorcycle is a bicycle with a pandemonium attachment and is designed for the especial use of mechanical geniuses, daredevils and lunatics." — George Fitch, Atlanta Constitution Newspaper, 1912 ___ Emc-developers mailing list Emc-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-developers ___ Emc-developers mailing list Emc-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-developers
Re: [Emc-developers] tool database in python
Wear offsets are useful when running production jobs. If you make 1000 parts and your insert wears 0.01, you simply put -0.01 in your wear table and it shifts the offset by that much. Beats having to add/subtract from your geometry, especially if you need to make a 0.0062 wear adjustment to an x-12.8753 value. On our machines, when you touch your tools off on the tool setter, the wear offset for that tool zeroes out automatically. It's just beneficial to have, especially on a lathe. Phil T. The Feral Engineer Check out my LinuxCNC tutorials, machine builds and other antics at www.youtube.com/c/theferalengineer Help support my channel efforts and coffee addiction: www.patreon.com/theferalengineer Order one of the coolest label makers on the market at http://labelworks.epson.com, use coupon code "theferalengineer" and receive 20% off of your order On Fri, Jun 24, 2022, 8:15 AM Stuart Stevenson wrote: > In the 1988/1989 timeframe I ran a Mori Seiki (SL25?) with a Fanuc control. > I built a tool holder to hold 3 tools on one tool station on the turret. I > had a spot drill, drill and small boring bar mounted. The tools could be > varied as I used small round shank collet holders. > Ex. > T0101 would be tool station 1 offset 1 > This would spot drill and move back (Z positive to a clearance point) > > T0111 would be tool station 1 offset 11 > This would (without the turret rotating) drill the hole and move back (Z > positive to a clearance point) > > T0121 would be tool station 1 offset 21 > This would (without the turret rotating) bore the hole and move back (Z > positive to a clearance point) > > \Ex. > > One lathe I ran (I wish I could remember what the control was) would allow > me to change the value of the offset while the control was running. The > offset change would be applied (interpolated) during the running of the > next block of code. The control would read the offset value at the > beginning of every line of code and interpolate to the end point while > applying the offset value. I thought this a very useful feature. Never saw > it again. > > Most of the controls I ran have had wear offsets available. I never used > them. I thought they were confusing and just one more opportunity for human > error and forgetfulness (maybe this is just my way of self > protection/compensation). I probably would not use wear offsets today. I > don't see the point. > > Just my 2 cents contribution > Stuart > > > On Thu, Jun 23, 2022 at 8:57 PM Feral Engineer > > wrote: > > > Siemens controls use tool edges to control offsets for each tool. Every > > tool starts with edge 1 > > > > T1 D1 is tool 1 data 1 > > T="end mill" D1 > > T3 D1 > > Etc > > > > You can have like 10 offsets per tool > > > > On a lathe there are two ways you can have your offsets. T0101 as an > > example could either be station 1 / offset 1, wear 1 or T0101 could be > > station 1, offset 1 / wear 1 > > > > Another example would be T0210 > > > > Station 2 > > Offset 10 > > Wear 10 > > > > Or > > > > Station 2 > > Offset 2 > > Wear 10 > > > > Depends on parameter setting. On a Mitsubishi, i think it's 1098. I > forget > > what it is on fanuc. I'd have to look. > > > > Phil T. > > The Feral Engineer > > > > Check out my LinuxCNC tutorials, machine builds and other antics at > > www.youtube.com/c/theferalengineer > > > > Help support my channel efforts and coffee addiction: > > www.patreon.com/theferalengineer > > > > Order one of the coolest label makers on the market at > > http://labelworks.epson.com, use coupon code "theferalengineer" and > > receive > > 20% off of your order > > > > On Thu, Jun 23, 2022, 9:46 PM Chris Morley > > wrote: > > > > > Different edges of the same tool is done by having different offsets, > not > > > tool number. > > > t11 = tool pocket 1 offset 1 > > > t12 = tool pocket 1 offset 2 > > > > > > There is also > > > T111 = tool 1 offset 1 wear offsets 1 > > > > > > To pick a particular tool for a pocket in Gcode is not standard on a > > lathe. > > > I'm quoting Okuma, I believe Fanuc is similar but I'm sure there are > > > exceptions of course. > > > > > > Anyways the problem of the GUI knowing what offset/wear offset is > > > currently set is still the same. > > > > > > Chris > > > > > > From: andy pugh > > > Sent: June 23, 2022 7:29 PM > > > To: EMC developers > > > Subject: Re: [Emc-developers] tool database in python > > > > > > On Thu, 23 Jun 2022 at 06:42, Chris Morley > > > > wrote: > > > > > > > for instance, you can use multiple tool offsets (one at a time) on a > > > single tool position. > > > > > > Indeed, which is why a database needs to allow several tools to be > > > simultaneously in the same pocket. > > > (To store different edges of the same tool as different T-numbers > > > using different offsets) > > > > > > -- > > > atp > > > "A motorcycle is a bicycle with a pandemonium attachment and is > > > designed for the especial use of mechanical geniuses,
[Emc-developers] [Hosted Weblate] New comment in LinuxCNC/LinuxCNC Documentation
# Comment added [ smoe](https://hosted.weblate.org/user/smoe/ "Steffen Möller"): [Hosted Weblate](https://hosted.weblate.org) / [LinuxCNC](https://hosted.weblate.org/projects/linuxcnc/) / [LinuxCNC Documentation](https://hosted.weblate.org/projects/linuxcnc/linuxcnc-docs/) / [English](https://hosted.weblate.org/projects/linuxcnc/linuxcnc-docs/en/) ## Source string '(returns integer)' - Returns either STATE_ESTOP or not. ## Source string description type: Plain text ## Comment Technically, "not" could be confused with "None". Sounds like a tautology. Suggesting to reword this. [Edit this string](https://hosted.weblate.org/translate/linuxcnc/linuxcnc- docs/en/?checksum=e7d130cc5aa8b88a#comments) ## Source string location [src/config/python- interface.adoc:166](https://github.com/LinuxCNC/linuxcnc/blob/master/docs/src/config/python- interface.adoc?plain=1#L166) ## Translation Info All strings| [ 29,213 ](https://hosted.weblate.org/translate/linuxcnc/linuxcnc-docs/en/) | ---|---| Translated strings | [ 29,213 ](https://hosted.weblate.org/translate/linuxcnc/linuxcnc- docs/en/?q=state:>=translated) | [ 100% ](https://hosted.weblate.org/translate/linuxcnc/linuxcnc- docs/en/?q=state:>=translated) Untranslated strings | [ 0 ](https://hosted.weblate.org/translate/linuxcnc/linuxcnc- docs/en/?q=state:empty)| [ 0% ](https://hosted.weblate.org/translate/linuxcnc/linuxcnc- docs/en/?q=state:empty) Unfinished strings | [ 0 ](https://hosted.weblate.org/translate/linuxcnc/linuxcnc- docs/en/?q=state:https://hosted.weblate.org/translate/linuxcnc/linuxcnc- docs/en/?q=state:https://hosted.weblate.org/translate/linuxcnc/linuxcnc- docs/en/?q=state:needs-editing)| [ 0% ](https://hosted.weblate.org/translate/linuxcnc/linuxcnc- docs/en/?q=state:needs-editing) [View](https://hosted.weblate.org/projects/linuxcnc/linuxcnc-docs/en/) [Weblate, the libre continuous localization system.](https://weblate.org/) Generated on June 30, 2022, 3:33 p.m.. ___ Emc-developers mailing list Emc-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-developers
Re: [Emc-developers] linuxcnc is marked for autoremoval from testing
On 29.06.22 19:44, Sebastian Kuzminsky wrote: Note that Jeff already "fixed" this by making LinuxCNC not use the buggy libtk-img library (turns out the functionality we used from that library had become available in core Tk). ;) So LinuxCNC was even improved. I intend to upload a new LinuxCNC deb to unstable that closes this bug, which will prevent us from getting removed from testing. I just checked with the latest upload of libtk-img - it got fixed, i.e. the version prior to Jeff's fix works again. This means we can just close the bug. Best, Steffen On June 29, 2022 10:56:46 AM MDT, "Steffen Möller" wrote: On 29.06.22 17:14, Stuart Stevenson wrote: What does 'autoremoval from testing' mean? Is it good or bad? Harmless. Mostly :) When there is a bug to a package that is not fixed then the package is removed from the testing distribution of Debian that is the next stable release. And with it all packages that depend on that package need to go. Such removals are mighty annoying when the dependency just affects some borderline use of some software. On the plus side, this gets things fixed more quickly. A removal from testing does not mean that it is removed from unstable, i.e. the Debian distribution in which all uploaded packages appear before 5 days later transitioning to testing. This (very ironic) renders unstable sometimes more stable than testing. The background to this bug is that there was this abi change to the tiff library that affected the Img Tk library. This was first spotted from within LinuxCNC. I personally take this as an indication that LinuxCNC is one of the most-used Tk applications these days :) It is not our bug, though. And someone has already or is about to fix this. Such incompatibilities happen all the time. It is the main purpose of a Linux distribution to spot these and fix them. With LinuxCNC now being part of the very latest of Debian in Debian unstable (and unstable+5 bugfree days = testing) LinuxCNC is more exposed to this distribution-development. A year from now the current testing distribution will be frozen, i.e. no more uploads and thus no more sudden incompatibilities, and after loads of bug fixes released as the new stable. Best, Steffen On Thu, Jun 23, 2022 at 11:34 AM gene heskett wrote: On 6/23/22 10:31, Debian testing autoremoval watch wrote: linuxcnc 2.9.0~pre0+git20220402.2500863908-4 is marked for autoremoval from testing on 2022-07-13 It is affected by these RC bugs: 1012789: linuxcnc-uspace: Linux CNC will not start https://bugs.debian.org/1012789 I beg to differ, this mornings install from the buildbot for both wintel and armhf machines is working fine. And has done so for every install here. sometimes at less than daily intervals for an updated install since the last time the buildbot was restarted. Pix of two machines running it are at: This is all on uptodate buster. The last time I tried to build on bullseye was on the rpi4 (armhf) and it failed on both a wintel and on an armhf because the python was too new. This mail is generated by: https://salsa.debian.org/release-team/release-tools/-/blob/master/mailer/mail_autoremovals.pl Autoremoval data is generated by: https://salsa.debian.org/qa/udd/-/blob/master/udd/testing_autoremovals_gatherer.pl Emc-developers mailing list Emc-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-developers . Cheers, Gene Heskett. -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author, 1940) If we desire respect for the law, we must first make the law respectable. - Louis D. Brandeis Emc-developers mailing list Emc-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-developers Emc-developers mailing list Emc-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-developers ___ Emc-developers mailing list Emc-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-developers
