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 ------------------------------------------------------------------------------ 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
