Wow, you are really making some great videos, thank you. I wish you could provide a list of the order that you would suggest a newbie watch the videos. It would also be helpful if you corrected your captioning. Please provide a list of how you would suggest that we watch your video. Great work here
Hi Bro , thank you so much for your helping 🙏. Could you please inform us How to get data print from fanuc robot? An example, robot move to step one and wait for 2 sec. Then move to step 3 wait for 10 sec. Etc.
Quiz questions for this video: 1) Which type of positional data is globally accessible -- a) Positions P[X] *b) Position Registers PR[X] 2) Positional Data is depended on what two frames? -- *a) User and Tool b) Jog and Tool c) Tool and World d) World and User 3) What instruction would increment Data Register 10 (R [10]) by two (2)? -- a) R [10] + 2 *b) R [10] = R [10] + 2 c) R [10] =2 d) R [10] ++
can registers be used to register SCR value's? I did not see SCR when you assigned a variable at 11:29 am specifically interested in :$SCR_GRP[1].$MCH_SPD.
Sure, you need to use ...=(...) formula and inside of "()" you use Parameter name (Variable). So the function will look like R[x]=($SCR_GRP[1].$MCH_SPD)
So when I record a PR and use that PR in a search sequence and I execute that touch sense routine. Then I try to “move to” say PR1 after the search routine is executed. The robot try’s to go under the work table... and I’m so confused on why that is.
could you tell me what do you mean by search routine ? Remember "MOVE TO" will always use a LINEAR motion to get somewhere, so the motion might be different than J PR[1] 100% FINE. Other important thing that I've mentioned when you do MOVE TO you need to select correct User and Tool Frame, the one that was used when saving a PR. I'm working on a PR video now, so I'm planning to finish it by the end of the week
@@FutureRoboticsChannel it’s very hard to explain I’ll just keep watching to see if I can pick up something. But a search routine is just a way to find if a part has changed or in a different location. And you master a part so the robot can find the offset with new part based on the mastered part. “If that makes sense”.
@@MatthewMurry Yeah, sure I understand, I worked with the application like this. Are you using vision for this, or just some sensor ? Also that PR is just and offset or a real position ?
@@FutureRoboticsChannel just a touch sense sensor. And the PR recorded Is an actual position. It’s the start of a weld. And the use of the touch sense is to maintain a decent weld overtime. Just in case the part changes or the operator isn’t paying attention.
@@MatthewMurry I didn't work with touch sense, but I think that your Tool Frame / User Frame might have something to do with it. For most MIG/MAG applications Tool Frame has to be taught according the the rule where Z+ will move torch towards the part. Also have you tried changing the point to regular point and to the test if problem still occurs ?
There is no online classes yet, but I have consultations available if you'd like to broaden their knowledge, you can check them out here: f-robotics.com/consultation
RSR (ROBOT SERVICE REQUEST) - allows you to use 8 numerically identified programs that correspond to 8 input bits, programs has to follow the naming (RSRxxxx). To be honest I've never seen anybody using RSR to run the robot program. There is a option for adding kind of handshake for the program acknowledge as well. PNS - (PROGRAM NUMBER SELECT), works the same as RSR, but in here instead of one bit being assigned to specific value, you are creating a number using 8 bits (so you are getting a wide range of program numbers). Then there is a difference how you select the program (signal sequence that PLC needs to send in order to select and run the program). The most common program select types for FANUC would be: 1. STYLE 2. PNS 3. OTHER I'm going to make a video about program select, but that's later on
The Frame does not matter for Data Registers, only for Position Registers that I describe at the end of the video. I explain Position Registers in another video dedicated to Position Registers
