as andy stated Message: 4 Date: Sat, 13 Apr 2013 16:33:39 +0100 From: andy pugh <[email protected]> Subject: Re: [Emc-developers] [ emc-Bugs-3610734 ] G10 L10 run from line, without tool loaded error To: EMC developers <[email protected]> Message-ID: <can1+yzxyl9i54fc+jka6n7p3mahxdetw1pe4pcwcbdodxfz...@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1
On 13 April 2013 13:56, Schooner <[email protected]> wrote: > Does not the line chosen to 'run from' have to be a linear move? That is what I am suspecting is the problem here. But why? -- guys this is anything but intuitive the need for run from should pick up from a tool change , i right m0 due to lack of a changer . but in use having to launch from a linear move seems almost outright dangerous . just my .02 i will be quiet now :) and thanx for working on these projects guys On Tue, Apr 16, 2013 at 8:34 PM, < [email protected]> wrote: > Send Emc-developers mailing list submissions to > [email protected] > > To subscribe or unsubscribe via the World Wide Web, visit > https://lists.sourceforge.net/lists/listinfo/emc-developers > or, via email, send a message with subject or body 'help' to > [email protected] > > You can reach the person managing the list at > [email protected] > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of Emc-developers digest..." > > > Today's Topics: > > 1. [ emc-Bugs-3610734 ] G10 L10 run from line without tool > loaded error (SourceForge.net) > 2. [ emc-Bugs-3610734 ] G10 L10 run from line without tool > loaded error (SourceForge.net) > 3. Re: [ emc-Bugs-3610734 ] G10 L10 run from line, without tool > loaded error (Schooner) > 4. Re: [ emc-Bugs-3610734 ] G10 L10 run from line, without tool > loaded error (andy pugh) > 5. [ emc-Bugs-3604558 ] probe trips message while G38.2 or G38.3 > (SourceForge.net) > 6. [ emc-Bugs-3604558 ] probe trips message while G38.2 or G38.3 > (SourceForge.net) > 7. Re: [ emc-Bugs-3604558 ] probe trips message while G38.2 or > G38.3 (Gene Heskett) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Sat, 13 Apr 2013 05:39:24 -0700 > From: SourceForge.net <[email protected]> > Subject: [Emc-developers] [ emc-Bugs-3610734 ] G10 L10 run from line > without tool loaded error > To: SourceForge.net <[email protected]> > Message-ID: > < > mailman.79225.1366158868.2279.emc-develop...@lists.sourceforge.net> > Content-Type: text/plain; charset=UTF-8 > > Bugs item #3610734, was opened at 2013-04-13 01:25 > Message generated for change (Comment added) made by mahsofo > You can respond by visiting: > > https://sourceforge.net/tracker/?func=detail&atid=106744&aid=3610734&group_id=6744 > > Please note that this message will contain a full copy of the comment > thread, > including the initial issue submission, for this request, > not just the latest update. > Category: G-code Interpreter > Group: None > Status: Open > Resolution: None > Priority: 5 > Private: No > Submitted By: grandixximo (grandixximo) > Assigned to: Nobody/Anonymous (nobody) > Summary: G10 L10 run from line without tool loaded error > > Initial Comment: > The Example G-code runs smooth if played from the beginning, but upon > running it from line 6 (T2M6), without a tool loaded, the P value out of > range error will come up, the #5400 stores the current loaded tool, so if > no tool is loaded that is 0, loading any tool will do the trick, still the > interpreter should account that in the first G10 L10 the #5400 should have > been one and not zero, because at that point in the G-code tool one was > supposed to be loaded. > > To put it simply, the interpreter doesn't account for read only parameters > changes due to tool change in the code, when doing a check of the code to > run from line. > > ---------------------------------------------------------------------- > > >Comment By: Michael Haberler (mahsofo) > Date: 2013-04-13 05:39 > > Message: > and exactly which version of LinuxCNC is this? > > ---------------------------------------------------------------------- > > Comment By: andypugh (andypugh) > Date: 2013-04-13 04:33 > > Message: > I was confused by the description, and having checked it it appears that > the issue is that run-from-line does not perform the tool-change if the > selected line is a tool change. This does seem unexpected. > > ---------------------------------------------------------------------- > > You can respond by visiting: > > https://sourceforge.net/tracker/?func=detail&atid=106744&aid=3610734&group_id=6744 > > > > ------------------------------ > > Message: 2 > Date: Sat, 13 Apr 2013 06:01:51 -0700 > From: SourceForge.net <[email protected]> > Subject: [Emc-developers] [ emc-Bugs-3610734 ] G10 L10 run from line > without tool loaded error > To: SourceForge.net <[email protected]> > Message-ID: > < > mailman.79226.1366158868.2279.emc-develop...@lists.sourceforge.net> > Content-Type: text/plain; charset=UTF-8 > > Bugs item #3610734, was opened at 2013-04-13 01:25 > Message generated for change (Comment added) made by grandixximo > You can respond by visiting: > > https://sourceforge.net/tracker/?func=detail&atid=106744&aid=3610734&group_id=6744 > > Please note that this message will contain a full copy of the comment > thread, > including the initial issue submission, for this request, > not just the latest update. > Category: G-code Interpreter > Group: None > Status: Open > Resolution: None > Priority: 5 > Private: No > Submitted By: grandixximo (grandixximo) > Assigned to: Nobody/Anonymous (nobody) > Summary: G10 L10 run from line without tool loaded error > > Initial Comment: > The Example G-code runs smooth if played from the beginning, but upon > running it from line 6 (T2M6), without a tool loaded, the P value out of > range error will come up, the #5400 stores the current loaded tool, so if > no tool is loaded that is 0, loading any tool will do the trick, still the > interpreter should account that in the first G10 L10 the #5400 should have > been one and not zero, because at that point in the G-code tool one was > supposed to be loaded. > > To put it simply, the interpreter doesn't account for read only parameters > changes due to tool change in the code, when doing a check of the code to > run from line. > > ---------------------------------------------------------------------- > > >Comment By: grandixximo (grandixximo) > Date: 2013-04-13 06:01 > > Message: > version 2.5.2 updated just now. > > I wanted to change the description to make it clearer, but I don't see how > to modify it... > > ---------------------------------------------------------------------- > > Comment By: Michael Haberler (mahsofo) > Date: 2013-04-13 05:39 > > Message: > and exactly which version of LinuxCNC is this? > > ---------------------------------------------------------------------- > > Comment By: andypugh (andypugh) > Date: 2013-04-13 04:33 > > Message: > I was confused by the description, and having checked it it appears that > the issue is that run-from-line does not perform the tool-change if the > selected line is a tool change. This does seem unexpected. > > ---------------------------------------------------------------------- > > You can respond by visiting: > > https://sourceforge.net/tracker/?func=detail&atid=106744&aid=3610734&group_id=6744 > > > > ------------------------------ > > Message: 3 > Date: Sat, 13 Apr 2013 13:56:46 +0100 > From: Schooner <[email protected]> > Subject: Re: [Emc-developers] [ emc-Bugs-3610734 ] G10 L10 run from > line, without tool loaded error > To: [email protected] > Message-ID: <[email protected]> > Content-Type: text/plain; charset=ISO-8859-1; format=flowed > > >> Comment By: andypugh (andypugh) > > >> Date: 2013-04-13 04:33 > > >> Message: > >> I was confused by the description, and having checked it it appears that > >> the issue is that run-from-line does not perform the tool-change if the > >> selected line is a tool change. This does seem unexpected. > > > Does not the line chosen to 'run from' have to be a linear move? > > I have obviously read this somewhere because that is what I always do > and it seems to work. > > > > > > ------------------------------ > > Message: 4 > Date: Sat, 13 Apr 2013 16:33:39 +0100 > From: andy pugh <[email protected]> > Subject: Re: [Emc-developers] [ emc-Bugs-3610734 ] G10 L10 run from > line, without tool loaded error > To: EMC developers <[email protected]> > Message-ID: > < > can1+yzxyl9i54fc+jka6n7p3mahxdetw1pe4pcwcbdodxfz...@mail.gmail.com> > Content-Type: text/plain; charset=ISO-8859-1 > > On 13 April 2013 13:56, Schooner <[email protected]> wrote: > > > Does not the line chosen to 'run from' have to be a linear move? > > That is what I am suspecting is the problem here. But why? > > -- > atp > If you can't fix it, you don't own it. > http://www.ifixit.com/Manifesto > > > > ------------------------------ > > Message: 5 > Date: Tue, 16 Apr 2013 13:29:15 -0700 > From: SourceForge.net <[email protected]> > Subject: [Emc-developers] [ emc-Bugs-3604558 ] probe trips message > while G38.2 or G38.3 > To: SourceForge.net <[email protected]> > Message-ID: > < > mailman.79227.1366158868.2279.emc-develop...@lists.sourceforge.net> > Content-Type: text/plain; charset=UTF-8 > > Bugs item #3604558, was opened at 2013-02-13 10:45 > Message generated for change (Comment added) made by jeromepilot22 > You can respond by visiting: > > https://sourceforge.net/tracker/?func=detail&atid=106744&aid=3604558&group_id=6744 > > Please note that this message will contain a full copy of the comment > thread, > including the initial issue submission, for this request, > not just the latest update. > Category: G-code Interpreter > Group: None > Status: Open > Resolution: None > Priority: 5 > Private: No > Submitted By: JeromePilot (jeromepilot22) > Assigned to: Nobody/Anonymous (nobody) > Summary: probe trips message while G38.2 or G38.3 > > Initial Comment: > With 2.5.1, with 2 different controlers , I want to use the G38.2 or the > G38.3 G-code to set the zero of my machines. > The movement and touching detection is OK BUT I have sometime (more than > 50%) an error message just when contacts saying me that the probe trips > during a non-probe MDI command. But the G38 is a probe MDI command I think > ?!?? > > ---------------------------------------------------------------------- > > >Comment By: JeromePilot (jeromepilot22) > Date: 2013-04-16 13:29 > > Message: > I've add a debounce to my hal file, even with a small number it seems to be > working. You were right about a noiy signal. > > ---------------------------------------------------------------------- > > Comment By: JeromePilot (jeromepilot22) > Date: 2013-02-22 12:35 > > Message: > You are probaly right even if with the scope it's not very clear. After > grounding everything, changing the power supply, i tried to find a software > improvement adding a timer but up to now it's not 100 % working. A g38 > choosen without error code was looking like an answer :o) > > ---------------------------------------------------------------------- > > Comment By: Sebastian Kuzminsky (seb_kuzminsky) > Date: 2013-02-22 07:43 > > Message: > Did the suggestions you got about signal bounce help? Can we close this > issue, or is there more debugging we can help you with? > > ---------------------------------------------------------------------- > > Comment By: Sebastian Kuzminsky (seb_kuzminsky) > Date: 2013-02-13 10:49 > > Message: > Maybe the electrical signal from your probe is noisy? If your probe move > finished because the probe tripped, but then the electrical signal from the > probe to LinuxCNC kept bouncing, that might generate this error message. > > Inspect the value on the probe input pin using halscope to see if this is > the case. If it is, you can probably fix it easily. > > ---------------------------------------------------------------------- > > You can respond by visiting: > > https://sourceforge.net/tracker/?func=detail&atid=106744&aid=3604558&group_id=6744 > > > > ------------------------------ > > Message: 6 > Date: Tue, 16 Apr 2013 13:30:04 -0700 > From: SourceForge.net <[email protected]> > Subject: [Emc-developers] [ emc-Bugs-3604558 ] probe trips message > while G38.2 or G38.3 > To: SourceForge.net <[email protected]> > Message-ID: > < > mailman.79228.1366158868.2279.emc-develop...@lists.sourceforge.net> > Content-Type: text/plain; charset=UTF-8 > > Bugs item #3604558, was opened at 2013-02-13 10:45 > Message generated for change (Settings changed) made by jeromepilot22 > You can respond by visiting: > > https://sourceforge.net/tracker/?func=detail&atid=106744&aid=3604558&group_id=6744 > > Please note that this message will contain a full copy of the comment > thread, > including the initial issue submission, for this request, > not just the latest update. > Category: G-code Interpreter > Group: None > >Status: Closed > Resolution: None > Priority: 5 > Private: No > Submitted By: JeromePilot (jeromepilot22) > Assigned to: Nobody/Anonymous (nobody) > Summary: probe trips message while G38.2 or G38.3 > > Initial Comment: > With 2.5.1, with 2 different controlers , I want to use the G38.2 or the > G38.3 G-code to set the zero of my machines. > The movement and touching detection is OK BUT I have sometime (more than > 50%) an error message just when contacts saying me that the probe trips > during a non-probe MDI command. But the G38 is a probe MDI command I think > ?!?? > > ---------------------------------------------------------------------- > > Comment By: JeromePilot (jeromepilot22) > Date: 2013-04-16 13:29 > > Message: > I've add a debounce to my hal file, even with a small number it seems to be > working. You were right about a noiy signal. > > ---------------------------------------------------------------------- > > Comment By: JeromePilot (jeromepilot22) > Date: 2013-02-22 12:35 > > Message: > You are probaly right even if with the scope it's not very clear. After > grounding everything, changing the power supply, i tried to find a software > improvement adding a timer but up to now it's not 100 % working. A g38 > choosen without error code was looking like an answer :o) > > ---------------------------------------------------------------------- > > Comment By: Sebastian Kuzminsky (seb_kuzminsky) > Date: 2013-02-22 07:43 > > Message: > Did the suggestions you got about signal bounce help? Can we close this > issue, or is there more debugging we can help you with? > > ---------------------------------------------------------------------- > > Comment By: Sebastian Kuzminsky (seb_kuzminsky) > Date: 2013-02-13 10:49 > > Message: > Maybe the electrical signal from your probe is noisy? If your probe move > finished because the probe tripped, but then the electrical signal from the > probe to LinuxCNC kept bouncing, that might generate this error message. > > Inspect the value on the probe input pin using halscope to see if this is > the case. If it is, you can probably fix it easily. > > ---------------------------------------------------------------------- > > You can respond by visiting: > > https://sourceforge.net/tracker/?func=detail&atid=106744&aid=3604558&group_id=6744 > > > > ------------------------------ > > Message: 7 > Date: Tue, 16 Apr 2013 20:34:18 -0400 > From: Gene Heskett <[email protected]> > Subject: Re: [Emc-developers] [ emc-Bugs-3604558 ] probe trips message > while G38.2 or G38.3 > To: [email protected] > Message-ID: <[email protected]> > Content-Type: Text/Plain; charset="windows-1256" > > On Tuesday 16 April 2013 20:16:45 SourceForge.net did opine: > > > Bugs item #3604558, was opened at 2013-02-13 10:45 > > Message generated for change (Comment added) made by jeromepilot22 > > You can respond by visiting: > > https://sourceforge.net/tracker/?func=detail&atid=106744&aid=3604558&gro > > up_id=6744 > > > > Please note that this message will contain a full copy of the comment > > thread, including the initial issue submission, for this request, > > not just the latest update. > > Category: G-code Interpreter > > Group: None > > Status: Open > > Resolution: None > > Priority: 5 > > Private: No > > Submitted By: JeromePilot (jeromepilot22) > > Assigned to: Nobody/Anonymous (nobody) > > Summary: probe trips message while G38.2 or G38.3 > > > > Initial Comment: > > With 2.5.1, with 2 different controlers , I want to use the G38.2 or the > > G38.3 G-code to set the zero of my machines. The movement and touching > > detection is OK BUT I have sometime (more than 50%) an error message > > just when contacts saying me that the probe trips during a non-probe > > MDI command. But the G38 is a probe MDI command I think ?!?? > > I don't know about the MDI, but I use the command to locate work fairly > often, and have noted that I must keep the backlash setting at some value > that just exceeds the actual. I appears to me that when you double up the > G38, once fast, once slow, backing away 2 or 3 thou in between, that a > contact make or break during the backlash move is ignored, so this requires > a backlash setting sufficient to break the contact during the backlash > move. An extra .0002" in the axis backlash setting seems to reduce that > noise to just a very occasional occurrence instead of almost every time. > YMMV, but thats what I sort of read between the lines. > > I also have a .1 capacitor on that line so the rise time at break is > slowed, and so that a momentary contact is held long enough for linuxcnc to > recognize it. I often probe with the cutting tool, turning backwards when > looking for an edge, fast enough that combined with the hold the capacitor > gives, say 200 rpm in reverse, so the tool effectively represents a > cylinder of that diameter. With the tool blown clean, the repeatability is > in the .0002" range with my old worn conventional acme screws. > > Not perfect of course, but then I'm not grinding a new mirror for the > Hubble either. :) > > Cheers, Gene > -- > "There are four boxes to be used in defense of liberty: > soap, ballot, jury, and ammo. Please use in that order." > -Ed Howdershelt (Author) > My web page: <http://coyoteden.dyndns-free.com:85/gene> is up! > My views > <http://www.armchairpatriot.com/What%20Has%20America%20Become.shtml> > Murphy's Law is recursive. Washing your car to make it rain doesn't work. > A pen in the hand of this president is far more > dangerous than a gun in the hands of 200 million > law-abiding citizens. > > > > ------------------------------ > > > ------------------------------------------------------------------------------ > Precog is a next-generation analytics platform capable of advanced > analytics on semi-structured data. The platform includes APIs for building > apps and a phenomenal toolset for data science. Developers can use > our toolset for easy data analysis & visualization. Get a free account! > http://www2.precog.com/precogplatform/slashdotnewsletter > > ------------------------------ > > _______________________________________________ > Emc-developers mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/emc-developers > > > End of Emc-developers Digest, Vol 84, Issue 6 > ********************************************* > -- jeremy youngs ------------------------------------------------------------------------------ Precog is a next-generation analytics platform capable of advanced analytics on semi-structured data. The platform includes APIs for building apps and a phenomenal toolset for data science. Developers can use our toolset for easy data analysis & visualization. Get a free account! http://www2.precog.com/precogplatform/slashdotnewsletter _______________________________________________ Emc-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-developers
