Відео

Make sure you press enter after typing the sequence name. The Nxxx appears in the yellow buffer until you do press enter, then you'll see the data move up to the restart pop-up. If you dont, the 5230 tells you that we made an oops

@@pocketcharleywithgosigeri cant able to start the program from Nxxxx. I thoguht the previous owner lock it from the parameter. I also have a program with tool dia wear offset . I cant not making the offset bigger than -.002 .

@@simovepsa6462 Super!

Sure looks like a bolt! Guess I should add threads just to keep y'all happy!

Great idea! I'll get on that

Totally! You must either handwheel or command the B axis back to actual zero before you can turn off the B axis mode. If you're lucky, you can simply command G0 B0, but if power has been cycled or E-stop pressed, you'll have to use jog functions to get back to B0

I'm assuming, then, that you have an OSP-P200 control? The SYS2 page only came into play on the P300 and newer. If you have an older control, the spindle center is in the WORK ZERO value instead of SYSTEM 2

@@Open-SourceInsanity touché! That was a poor choice of words: I probably would have better stated that the OSP variables are easier to remember…

Sure! Here is my video on the software available for this typ of stuff:ua-cam.com/video/QvugcXRnThw/v-deo.htmlsi=lCgWIUYDany3PwLz

@@dwaynekinnard3120 every cleaning task is easy if you keep up on it! Once it gets nasty, THEN it becomes a hassle

@@longlee934 the tool that you’re starting with should be in the spindle if you’re starting after the tool call. If you’re restarting BEFORE the tool call, the previous tool should in in the spindle. Bottom line: the tool that should be in the spindle for the restart position

@@centongbuburx PCNC Master is only available thru your local Okuma retailer. It is not downloadable from the web

For each type of tool, that depends on how you programmed the part. If you've used AOT or any other CAM system that does not automatically compensate for tool radius, then the value SHOULD be populated. Many modern CAM software seats will automatically program the toolpath relative to the actual tool radius, so in that case, the comp should remain at zero unless you are actively compensating for a worn tool.

@@pocketcharleywithgosiger Thanks for the clear explanation. This LB3000MYW is my first Okuma, you're videos have been very helpful.

Certainly, if the machine that it is based on has user task III, then the software will too

That's been an argument with AE's on my staff a lot! I always insisted that the Renishaw "Calibrate Z" cycle was the best method, while one of my guys insisted that it was much easier to simply use the freshly calibrated tool setter for the probe. When we disagreed, we set out to prove which was more accurate. Turned out: the results he got were only .0001" different than mine! Bottom line was : do whichever you're more comfortable with. I usually do the Z calibration last, because my final check is to probe a surface to set a G15, touch a tool off the setter, then command the tool to G56 and move above the new G15 by 1" and then use a gauge block to confirm that the tool set cal and the probe cal match. Thanks for the question!

I meant spindle probe tool length.

@@MikeWilliams7180 Yessir! Me too. The XY cal should be done with an artifact like a ring gauge, but the previous comments relate to the probe length

Sure! I'm currently slammed with IMTS prep, but I'll add that to the list

Sounds quite weird... What machine model is doing this?

@@pocketcharleywithgosiger hi Charley, it is a U5000 2SW. We have since been told that it canot simulate tool change unless in machine lock.

Good idea! I'll put that on the list

@@alecmathy Hmmmm… I haven’t heard anything to support your reseller’s statement, but it’s possible they know something I don’t! Since the new software for verification on a PC isn’t available yet, I have customers still taking delivery of 3dvm, so that’s not an issue, plus there are still P300 controls being delivered, so I’m not convinced that Okuma is ready to take a stand like that. I’ll do some digging and reply again once I know something for certain

@@pocketcharleywithgosiger Thank you!

@@alecmathy I just chatted with a contact high up in Okuma America. There has been some confusion over 3dvm, but the official word is that it is still available for all covered controls, but since it has been marked to be superseded by the new Digital Twin (eventually) it has been updated for the last time. Available, but no longer being improved

@@pocketcharleywithgosiger Thank you so much for your time.

Sounds like you either have an encoder issue, or a mechanical issue between the motor and ball screw. Service issues this big are above my paygrade

If the option is installed on the machine, you'll find it on the program operations page (MD1). On the screen showing your programs, there will be a tab on the upper right corner of the program list. The first tab is NC PROGRAMS, but select the second tab IGF-DATA and that houses the AOT data.

@@number2664 it is a different software. PCNC Master is more of a control training device, as it simulates the actual control layout. If you look up my video regarding Okuma Simulation you’ll see the actual software

@@number2664 ua-cam.com/video/QvugcXRnThw/v-deo.htmlsi=ushqyxNmEDE7Fd8V

@@pocketcharleywithgosiger so if we want to simulate programs as if we're on the actual machine we would need 3DVM or would PCNC fill the same need?

@@number2664 Great question! Either will “simulate” as in graphically verify and display alarms, but PCNC does not have the Collision Avoidance package, so you’d be on your own (with that software) to make sure your program is collision free.

@@KafaTek I’m on your side with this one! This tool is so powerful and essential with the complexity of the Multus and MU configuration machines that it would make perfect sense to have it included with those machines… But it remains an option. At this point, I’m just happy it’s available!

No better approach, but you CAN change the behavior of the machine when initializing. By adding a check mark to OPTIONAL PARAMETER LONG WORD BIT 6 bit 7, the machine will no longer erase the wear value when initializing the tool life. Happy turning!

@@pocketcharleywithgosiger thanks for the quick reply.

Great list! I'll add a few of these ideas to my list of videos to produce, but let's talk about the easiest of them here: looping thru AOT. This is a video I created displaying the methods for looping lathe programs. ua-cam.com/video/PhT82zAr0lw/v-deo.html Since two of the looping methods would require use of an NC PROGRAM process, I advocate for using the schedule program method described.

​I got it working with just NC-programs and saved as a .upa for now as a process along with a setup "sheet". In the future I may consider going for a schedule program but I am not this far yet. I am learning automation from 0, looking for error solution for 3 hours realizing that I had to change one command or change key position in loader. Now I closed the loop and am about to start cutting in 5 axis (milling and turning). I wondered why one turret stopped when the other reached destination. I though about collision avoidance but the reality was, it was in sync and after the first part it I should play more with feedrate while the single block is off. Next week I am going to see and lear the true potential of this machine. Definietly worth it. ​@@pocketcharleywithgosiger

Woohoo! Local variables are awesome! No, the variable name does not need to start with a P, but Okuma and many of us in the field prefer starting with a P so a local is readily identifiable. You CAN start a variable with an X, but as you suggest, there must be additional characters to clarify that you're identifying a variable. An X with a number following, for example, is unclear whether you're commanding a motion block or calling a variable. XX, however, is clearly a local and won't alarm out. As for the quantity of locals available, I can't answer that. I have also read that you are limited to 127, but the book is unclear whether that is 127 per level, or total. I have never run any programs with that many locals

@@pocketcharleywithgosiger thankyou. Interesting about quantity of local variables per level. I think you can nest program 6 or 8 levels, which would be too many for 127 on each level. I have only used a maybe a dozen at any time, but I was testing as I wanted to see how the machine handles overuse. It just alarms. I was trying to find a solution to another problem and was going about it from different directions.

I cannot give out a blanket download site publicly, but if you contact Gosiger or Okuma directly, we can provide you with a PDF free of charge

As reporting in the email thread, I know of no system variable to sample the active S code on a turning center