Hi All! Hi Tomas!
I'm having different problems with a parser for the machine Okuma (CNC - OSP300).
NX (Machine Configurator) has no quality parser for Okuma. There is only one default "sim05_mill_5ax_okuma". It is bad enough.
But at the same time we have a lot of options of basic parsers for Fanuc, Siemens, Heidenhain. It's good! But for Okuma (OSP200, OSP300) ... This is a problem!
Will the future really working parser for Okuma in the future as for Fanuc, Siemens, Heidenhain?
let me first of all set a correct wording, so that we speak the same.
What do you mean with "NX (Machine Configurator) has no quality parser for Okuma. There is only one default "sim05_mill_5ax_okuma". It is bad enough." ? What problems do you address with this? Do you get error messages? Please let us know in detail what you need. Without detailed feedback/request you can´t expect a detailed answer.
I think there was a misunderstanding. However, the functionality is not comparable with the Sinumerik 840D parser. The parser will grow in the future like any other parser too. With the configurable parser technology, we offer that everyone can enhance the parser if he wants to. With that you don´t have to wait for a NX release. If you need a enhancement, call GTAC that they can create an ER or do it by your own in future (unfortunetaly you have to wait for the release of the python parser). But you don't have to wait for a "final completion" of the Okuma parser!
Hi! Sorry for the obtrusiveness!
What would you recommend as a "starting point" for further elaboration for Okuma-CNC, base CSE-driver?
I guess, should I use only existing in our database - "Okuma.CCF" and "sim05_mill_5ax_okuma.MCF"? Are there other variants?
it depends on what you or the customer needs. A good starting point is a well prepared kinematic model with inculded axis and channel data, the basic.ccf, the Okuma.ccf and a new created MCF for modifications or enhancements of controller functions.