Hello Guest it is October 23, 2019, 04:47:53 AM

Author Topic: New error message: "Radius to end of arc"...  (Read 8907 times)

0 Members and 1 Guest are viewing this topic.

New error message: "Radius to end of arc"...
« on: February 20, 2009, 05:48:55 PM »
Out of nowhere I'm getting this error when generating a path; "Radius to end of arc differs from radius to start line xx". The same files were working yesterday. Any ideas?

Second question; it is possible to seperate M3 and M4 so that they are not mutually exclusive? I'd like to use them as general I/O.

Thanks.

Offline RICH

*
  • *
  •  7,368 7,368
    • View Profile
Re: New error message: "Radius to end of arc"...
« Reply #1 on: February 20, 2009, 06:12:01 PM »
Can you post one of the files.
RICH
Re: New error message: "Radius to end of arc"...
« Reply #2 on: February 20, 2009, 06:17:32 PM »
Out of nowhere I'm getting this error when generating a path; "Radius to end of arc differs from radius to start line xx". The same files were working yesterday. Any ideas?

Second question; it is possible to seperate M3 and M4 so that they are not mutually exclusive? I'd like to use them as general I/O.

Thanks.

Ha!  I've gotten that several times, never figured out why.  Restart Mach and all is fine.

M3, M4, M5 are just macros, in the macros directory for your configuration (mill/turn/etc.).  You can define them to do whatever you want.  You can also define your own M-codes, by simply adding appropriately named macro files to the appropriate macros directory.

Regards,
Ray L.
Regards,
Ray L.

Offline Chip

*
  • *
  •  2,056 2,056
  • Gainesville Florida USA
    • View Profile
Re: New error message: "Radius to end of arc"...
« Reply #3 on: February 20, 2009, 06:44:04 PM »
Hi, Mtripoli

On the MDI line enter a G91.1 or G90.1, Probably some other G-code you were running set the "IJ's" from INC to ABS Mode, Try G91.1 first.

A good habit to get into is, In the top of your G-code files, Insert Pre-Amble code to set Mach to a default State to load your G-code Files.

G-code can set mach in to many states, It for the most part remaines that way till set back again.

G20 G90 ; G20 set's Inch mode G90 set's ABS Dist. mode.
G91.1 ; set's IJ's to inc. mode, need's to be on it's own line.

Might be IT, Chip 
Re: New error message: "Radius to end of arc"...
« Reply #4 on: February 23, 2009, 03:29:24 PM »
Thanks very mcuh; I'll give that a try.

BClemens

*
Re: New error message: "Radius to end of arc"...
« Reply #5 on: February 23, 2009, 05:43:53 PM »
Hi, Mtripoli

On the MDI line enter a G91.1 or G90.1, Probably some other G-code you were running set the "IJ's" from INC to ABS Mode, Try G91.1 first.

A good habit to get into is, In the top of your G-code files, Insert Pre-Amble code to set Mach to a default State to load your G-code Files.

G-code can set mach in to many states, It for the most part remaines that way till set back again.

G20 G90 ; G20 set's Inch mode G90 set's ABS Dist. mode.
G91.1 ; set's IJ's to inc. mode, need's to be on it's own line.

Might be IT, Chip 

Chip, when this happens, wouldn't Mach flash the amber "abnormal" sign? I noticed this when a post processor posted I&J in inclusive so changed Mach to interpret it that way. But the "abnormal" led was flashing...? It flashed until the setting was returned to absolute. Just wondering....?

Bill C.

Offline Hood

*
  •  25,856 25,856
  • Carnoustie, Scotland
    • View Profile
Re: New error message: "Radius to end of arc"...
« Reply #6 on: February 23, 2009, 05:57:16 PM »
Bill you can click on the Abnormal LED and it will allow you to accept it as a normal condition if you wish.
Hood

BClemens

*
Re: New error message: "Radius to end of arc"...
« Reply #7 on: February 23, 2009, 06:37:52 PM »
Thanks, Good info.

Bill C.

Offline jimpinder

*
  •  1,233 1,233
  • Wakefield, West Yorks, UK
    • View Profile
Re: New error message: "Radius to end of arc"...
« Reply #8 on: February 24, 2009, 02:36:58 AM »
To go back to the M3 and M4 - they are mutually exclusive, because on most spindle controllers they must be, or a fault occurs.

They are not general Input/Output commands, they are output only. On the spindle page, you will see in the top left hand corner, that you have to allocate M3 and M4 to outputs, and then allocate the outputs to pins on te Port and Pins/Outputs page. If you do not need M3 and M4, do not allocate them.

You do not say what additional outputs you require, but if they are for your limit switches/home switches, they are already catered for, just allocate them to the pins. If the are general outputs for tiurning something on, then allocate an #output to a pin and turn that on, either by using a button, which you can add to your screen set, or a macro.

When you write the GCode, write M*** in the code and it will turn on the output, you will need an off command as well.

You can limit M3 and M4 by ony using one of them, e.g. do not allocate M4, and use M3 and M5 for on and off, or you could use the coolant commands in a similar way, but I think it is better to write you own command specifically for what you want to do, rather than alter something that is there for a specific purpose.

The various commands and OEM codes are shown in Hoods post at the top of the main forum page, and also in the Wikki.


Not me driving the engine - I'm better looking.

BClemens

*
Re: New error message: "Radius to end of arc"...
« Reply #9 on: February 24, 2009, 05:30:49 AM »
But, only utilizing M3 for the spindle (with M5) and controlling spindle direction with an external switch or controller, why could you NOT utilize M4 for another totally different function? Ray L. eludes to the ability to change M4's function in the main directory and writing another macro to perform a function that includes M4. Looks like a fault would occur only if the established function were not modified. The same for flood and mist M codes. Why waste an output for mist when you only use a flood coolant system? This would require some diving into the workings of Mach but can't it be done? You can always reload Mach if it gets too crazy.

Thanks,
Bill C.