Fanuc 0T-C, G65 in MDI?

[lobust]

Is this controlled by some esoteric parameter that I can't find, or is it simply not possible?

Parameter 0078#2 suggests that macro variables can be entered in MDI (they can't), but I suspect it is referring to the actual macro screen rather than MDI mode.

In any case setting it either way has no impact on G65 in MDI, and I can't see any other parameters that seem relevant.

I found an ancient post on cnczone where one guy had two OM-C's, and one could do G65 in MDI and the other couldn't, which kind of implies there must be a parameter to enable this - he wanted to know how to enable it on the second machine, but there were no responses.

 

[Herding Cats]

I'll take a look in my manuals this evening.

Bill @angelw is likely your man for this question

 

[Vancbiker]

Is this controlled by some esoteric parameter that I can't find, or is it simply not possible?

Parameter 0078#2 suggests that macro variables can be entered in MDI (they can't), but I suspect it is referring to the actual macro screen rather than MDI mode……

My 0MB will not execute a macro in MDI called by G65 and I have never found a parameter to enable that. It will also not execute a macro called by an M code or G code.

It will allow macro variable assignments be executed in MDI. To do that however, the machine must be equipped with the “full keyboard” rather than the more common “mini keyboard”.

 

[mach ramsey mn]

Why the full keyboard verses the mini keyboard? If the control has soft keys there is an extended key page. The parens and the pound sign are there. I would have be standing in front of one to figure out where it is. The button to get there is “ext. char”
I used to work with Cell Cons these used 0MA’s at the time and the tool change was all macro driven ( fricking macro A) and it worked in MDI.

 

[Vancbiker]

According to my 0B manual macro A calls can be made in MDI but macro B calls cannot. My 0MB originally came with the mini keyboard and has softkeys but it never had an extended character function. It is also not mentioned in my 0MB operation manual. I have seen ext char softkey on newer controls with mini keyboards probably a 16/18 series.

Since macro A does not use brackets, it is possible to create or edit macro A programs with the mini keypad as multiple presses of the EOB button cycles through ;, #, and / characters.

 

[mach ramsey mn]

“ macro A calls can be made in MDI but macro B calls cannot.”
This, I did not know, in their right mind, would program something in macro A when B was available…

 

[lobust]

According to my 0B manual macro A calls can be made in MDI but macro B calls cannot. My 0MB originally came with the mini keyboard and has softkeys but it never had an extended character function. It is also not mentioned in my 0MB operation manual. I have seen ext char softkey on newer controls with mini keyboards probably a 16/18 series.

Since macro A does not use brackets, it is possible to create or edit macro A programs with the mini keypad as multiple presses of the EOB button cycles through ;, #, and / characters.

My OT-C in question has all the necessary keys available to use macro B on the machine, and all works fine in edit/auto mode, but in MDI mode # [ ] are simply ignored and G65 throws an improper G code alarm...

Not the end of the world but kind of annoying.

 

[Vancbiker]

Another minor thing I discovered whilst looking into things in this thread….

Unless you have macro B, you cannot run a subprogram from MDI.

 

[Vancbiker]

…… in their right mind, would program something in macro A when B was available…

Absolutely!! Seems like I recall maybe macro B was not available in early firmware versions for the 0A. I have only used macro A a couple times and only because a machine was not macro B equipped.