{"id":251,"date":"2016-04-29T19:45:20","date_gmt":"2016-04-29T19:45:20","guid":{"rendered":"http:\/\/kentechinc.com\/kipware_blog\/?p=251"},"modified":"2023-01-03T18:29:17","modified_gmt":"2023-01-03T18:29:17","slug":"fadal-to-okuma-g-code-conversion-software","status":"publish","type":"post","link":"https:\/\/kentechinc.com\/kipware_blog\/fadal-to-okuma-g-code-conversion-software\/","title":{"rendered":"Fadal to Okuma G Code Conversion Software"},"content":{"rendered":"

Kentech Inc. has been a pioneer and innovator in the world of G code conversion since 1986. And since that time we have received quite a few requests for a G code conversion application that can convert Fadal G code to Fanuc format. Althogh we do not have a specific hard-coded application for this conversion … our\u00a0KipwareXC\u00ae application can be configured quite easily to perform this\u00a0conversion very well. Fadal machines can be configured by parameter to accept Fanuc style G code (Format2) or the Fadal format (Format1) which is a little more powerful if doing manual type programming. Sub routines and canned cycles are handled a little different in Format1 … but the format is till pretty close to Fanuc format. For this reason … KipwareXC\u00ae has been a good solution.<\/p>\n

However we have recently received many requests for a conversion from Fadal G code to Okuma OSP format … and this one is a little more tricky. Since Okuma format is quite different than Fanuc … and of course Fadal format … we needed a custom, hard-coded app to accomplish this task.<\/p>\n

So we wrote\u00a0one !!<\/span><\/h3>\n

Kentech Inc. is pleased to announce the release of our new Fadal Options for our CNC XChange – Fanuc \/ Haas \/ Okuma Milling Version. For those unfamiliar with CNC XChange … it is a hard-coded application that will automatically convert Fanuc \/ Haas G code to Okuma OSP G code … and reverse. It has options that will auto-convert Fanuc Macro to Okuma User Task … and reverse … as well as auto-convert Live Tool and Y axis programming between the two formats. The term hard coded simply means that all the standard G code conversions are defined inside the source code … so it is specifically designed for Fanuc \/ Haas <–> Okuma conversions.<\/p>\n

For non-standard code … M codes for example … the user can\u00a0use the User Options within the software to customize the conversion. They can … for example … set-up an unlimited number of user defined conversions to handle say M51 to M71 … or convert G91G28Z0 to G00Z50.0. The User Options are very powerful with many options … and now the Fadal Options have been added. A\u00a0screenshot\u00a0is below.<\/p>\n

\"fadal_okuma_options_list\"<\/a><\/p>\n

Let me take a few moments to outline these options.<\/p>\n

    \n
  1. TURN ON FADAL OPTIONS<\/strong> … kind of self-explanatory but this option allows the user to turn the auto-conversion ON or OFF completely.<\/li>\n
  2. STRIP SUBROUTINES<\/strong> … this one is quite powerful. Fadal programs define any subroutines used inside the program at the very top of the program. Subroutines start with an L number followed by the G code routine to repeat and ends with an M17. The last subroutine ends with an M17 and then an M30 on the next line. \u00a0The Fadal control will read the program … record the subroutines and their locations … and then start the machining\u00a0once it finds the M30. Using this option within CNC XChange will cause the software to automatically strip each subroutine out of the code and place it’s contents in a text file and save that text file under the L name for the subroutine. Pretty cool … and very powerful !!<\/li>\n
  3. The SUBROUTINE CONVERSION OPTIONS<\/strong> will now tell\u00a0CNC XChange what to do with those subroutines. The first option will cause CNC XChange to automatically insert the contents of the subroutine called … remember it’s stored in a text file … at each location in the program where it is called. So basically when CNC XChange finds the subroutine call in the program … it dumps the contents of that text file into that location in the converted program. Again … pretty cool. If you don’t want that option … the second choice is to just insert a Fanuc M98P call … calling that subroutine. Of course since we are converting to Okuma … that M98P call will eventually get converted to the Okuma equivalent as the conversion process proceeds.<\/li>\n<\/ol>\n

    There are some other code conversions built into the Fadal conversion routine that are not user\u00a0configurable … they’re just done automatically like :<\/p>\n