Thanks Charlie. I have a 26 tools in my multis 250 with 105 dimensions. Im using common V for the print call out and it works well. Each dim. has a bubble call out # on the print and I have them matched to the print. Now you have my brain thinking again. lol
The legend! Great teaching lesson, tell Sean to buy you a higher end screen recording software for 1080p or up, I had a hard time to read anything on the screen. Looking forward to more videos, Thanks!
RUclips converts videos, it is never the file you made before. It has to have way less weight to store it for their servers. The one way to increase the quality, to render a recorded video in FHD in 1440p. The video will be crispier because other codec in RUclips will be used for higher resolutions.
Hello Charlie: What about getting the program in AOT into the loop from the start to the end and explain P-codes, IF, GOTO statements, VIRD and VORD for chucks. It has to be repeatable. If you could make a tutorial for everyone who works on robots and gantry loaders it would be even better for everyone who struggles or struggled to set it up. As of now, I struggle to get milling and turning independently running after the pick off and raw part loading. It has something to do with P-codes but according to AOT, milling and turning run in different spindles but errors out weirdly. You have to make and save processes in NC-Program and I try to get it working for everything. We use the worst of the worst of the worst uneven house steel castings with a big head (3rd side), tight on top with long tools. Also I found the problem with loader program that is independent. Usually after raw part has been clamped the part should have been clamped but when I restarted the program, well below the raw psrt loading, it unclamped. We had to tell the machine to M83 in NC-program in AOT because M84 was active in LR-Transfer and we had to counter it. The loader checks for a clamp in main and it was alright, I've tested scenarios already. Thank you.
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. ruclips.net/video/PhT82zAr0lw/видео.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
Great video, very good. The only thing I queried is the local variable name, I got the impression that you need to start with ‘P’, however in my understanding you can start with say X, however you need sufficient characters after it, that do not exist in control use or extended address character use. Also the manual says that there are 127 local variables, however our U5000 from testing has 511. Curious to know if that was an option we got or not. It’s a P300SA-H control. Also the way local variables are carried into and out of sub programs might be helpful to some. The manual explains it but not very clearly. I found testing it helped me understand more so then reading.
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.
Thanks Charlie. I have a 26 tools in my multis 250 with 105 dimensions. Im using common V for the print call out and it works well. Each dim. has a bubble call out # on the print and I have them matched to the print. Now you have my brain thinking again. lol
The legend! Great teaching lesson, tell Sean to buy you a higher end screen recording software for 1080p or up, I had a hard time to read anything on the screen. Looking forward to more videos, Thanks!
Funny thing is: the video is recorded in 1080p... It just takes RUclips a couple of hours to process the HD after the low res has been published
RUclips converts videos, it is never the file you made before. It has to have way less weight to store it for their servers. The one way to increase the quality, to render a recorded video in FHD in 1440p. The video will be crispier because other codec in RUclips will be used for higher resolutions.
Tell me x and z tool geometry offset macro safety programming in sequence....
You are my hero! Thank You for lessons :)
You're very welcome!
Hello Charlie: What about getting the program in AOT into the loop from the start to the end and explain P-codes, IF, GOTO statements, VIRD and VORD for chucks. It has to be repeatable. If you could make a tutorial for everyone who works on robots and gantry loaders it would be even better for everyone who struggles or struggled to set it up.
As of now, I struggle to get milling and turning independently running after the pick off and raw part loading. It has something to do with P-codes but according to AOT, milling and turning run in different spindles but errors out weirdly.
You have to make and save processes in NC-Program and I try to get it working for everything. We use the worst of the worst of the worst uneven house steel castings with a big head (3rd side), tight on top with long tools.
Also I found the problem with loader program that is independent. Usually after raw part has been clamped the part should have been clamped but when I restarted the program, well below the raw psrt loading, it unclamped. We had to tell the machine to M83 in NC-program in AOT because M84 was active in LR-Transfer and we had to counter it. The loader checks for a clamp in main and it was alright, I've tested scenarios already.
Thank you.
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. ruclips.net/video/PhT82zAr0lw/видео.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
Can i have a link for downloading the Mill programming manual PDF version please?
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
Great video, very good. The only thing I queried is the local variable name, I got the impression that you need to start with ‘P’, however in my understanding you can start with say X, however you need sufficient characters after it, that do not exist in control use or extended address character use. Also the manual says that there are 127 local variables, however our U5000 from testing has 511. Curious to know if that was an option we got or not. It’s a P300SA-H control.
Also the way local variables are carried into and out of sub programs might be helpful to some. The manual explains it but not very clearly. I found testing it helped me understand more so then reading.
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.
Please show me. Lathe System variable for main spindle speed, Thx
As reporting in the email thread, I know of no system variable to sample the active S code on a turning center