Messages

11

General Mach Discussion / Re: Problem with Arc Center Location Error

« on: January 27, 2013, 03:44:04 PM »

Thank you so much, Hood.  That did indeed fix the problem. 

I'm not sure how the G16 got into the Init string but putting G15 in the string fixed the problem.  (Without the G15, just deleting the G16 did not seem to work - it kept reappearing.)

Anyway, now I can mill!  Also for reference by others, the IJ mode (General Config) has to be "Inc"

12

General Mach Discussion / Re: Problem with Arc Center Location Error

« on: January 26, 2013, 09:02:30 PM »

Again, thanks for your continued help.  Attached is the XML.  By the way, the problem occurs with two different machines using different XML's although they came from the same base.

Brian

13

General Mach Discussion / Re: Problem with Arc Center Location Error

« on: January 26, 2013, 07:39:07 PM »

Thanks for your assistance.  I extracted the bit of code and attempted to run it separately in case there was something else in the file that was causing the problem.  Got the same error.

Here's the entire file (all 18,758 lines).  The first problem occurs at line 7148

Brian

14

General Mach Discussion / Problem with Arc Center Location Error

« on: January 26, 2013, 06:13:04 PM »

I'm having a problem where Mach3 (v. R3.043.066) is giving me error messages "Radius to end of arc differs from radius to start".  As I understand it, this message is only supposed to occur if the error is more than 0.0002".  I've checked the math and my calculations show the error at almost 10x less (0.00003").  The code was generated by MeshcamArt and runs fine under Cutviewer but not when I actually try to cut the part with Mach3.  Here's an example of the issue:

X2.2058 Y1.2136
G2 X2.2737 Y1.4341 I0.7115 J-0.0985 F10.0

Is anyone aware of any other reason this error message might occur?

By the way, I have other similar G2 moves that work just fine in the same program.  This also cannot be a hardware issue as I am getting the error on loading the code into a computer not connected to the NC router.

Thanks for any advice.

15

General Mach Discussion / Re: Probe Ignored Error Message

« on: January 15, 2013, 01:09:16 AM »

Thanks again BR549.  With your suggestion, I checked the wiring and found an intermittent ground in one of the probe circuits.  Problem fixed.

16

General Mach Discussion / Re: Probe Ignored Error Message

« on: January 14, 2013, 11:50:18 AM »

Thanks.  I did not notice the Digitize LED was lit.  I'll check for that and wiring problems.

17

General Mach Discussion / Probe Ignored Error Message

« on: January 13, 2013, 10:23:11 PM »

I've seen a couple of other threads with the same problem I have:  When probing I get the message " probe ignored activated at call for probe" but no one seems to have the answer for what causes this problem or how to avoid it.  Has anyone experienced this problem and found the solution?

18

Brains Development / Re: Problem Linking Brain to Macro

« on: December 25, 2012, 07:02:57 PM »

Still puzzled about this problem.  Anyone got any other thoughts?
Merry Christmas

19

Brains Development / Re: Problem Linking Brain to Macro

« on: December 09, 2012, 02:15:02 AM »

Yeah, that was a problem originally, but I did move them to the right folder.  Still no joy.

20

Brains Development / Problem Linking Brain to Macro

« on: December 08, 2012, 01:05:49 AM »

Hi Guys:

I've been puzzling over this problem for a few days now and think I'm missing something very basic.

Like others in this forum, I'm trying to have a brain trigger a macro.  I've read all the posts I can find and I understand the following steps are required:
a) Define a macro to run in the Init string which uses SetTriggerMacro to set which macro will be the default.  (In my case, M1000 in the init string causes M900 to be set)
b) Define a macro do do what I want when it is called (in my case, M900.m1s works when tested other than by brain activation)
c) Create a brain which waits until a defined input goes active then uses the terminator 1034 "Execute Button Script".  I tested the brain and it goes active when expected and appears to work with other outputs, just not the Execute Button Script output.

So my problem appears to be the linkage between the Execute Button Script terminator in the brain and actually calling the macro M900.m1s

I've tried all the tests I can think of and nothing seems to help.  Is there a way to look and see that M900 actually did get linked to OEMCODE 301 or whatever the brain activates?

Any help would be most appreciated... if I had any hair left I'd have pulled it out over this one!

Brian