Posts by DaveP

so that means that you have only the V8.20 virtual robot controller installed for Roboguide. I just looked in the same directory you listed and and I have V7.70, V8.10, V8.13, V8.20, and V8.30 installed.

You need to install the other versions from your Roboguide CD. If the version is not listed, you can download the roboguide installation files from the Fanuc Robotics website and it will include the latest virtual robot controllers. You don't have to install Roboguide, just the virtual robot controllers. Look for the FRVRC folders in the roboguide install files like bencor21 shows in the image.

I think it is referring to the Virtual Robot Controller version and not the Roboguide software version. You need to install the Virtual Robot Controller version for the robot software version on your real robot. When you install Roboguide it asks you which versions to install. You can manually install them by running the setup.exe file in the FRVRC830 folder (or whatever version desired). These folders are in the Roboguide install folder. I think you have to right click on the setup.exe file and run "as administrator".

Do you know when the Search function showed up in the Robot Home Page, which robot software version? I use it a lot on our newer robots but some of the slightly older ones don't seem to have it. One that I can think of is a M-20iA robot with V7.50P/08 software. Would it be in a software update?

A major advantage to using the SNPX option is no major hassles with configuring the robot to communicate and no size limits that I'm aware of. You have immediate access to DI/DO and access to registers requires setting up the $SNPX_ASG variables, which is not bad. There are some good posts here about doing that part.

Nation, thank you for the information on changing the Timer to Global. We've been fighting with that for several years and never saw that in the Detail window.

Like TitusLepic mentioned, your program names need to match. The program you posted shows the program name in the LS file to be Module, but you say the name of the file is test.tp

You either have to change the your LS file to be /Prog Test or change the file to module.tp

It shouldn't have anything to do with being quicker. A linear move will move in a Straight line from where it currently is to where the next point is. That straight line must have been wrapping up the arm somehow and causing a limit on one of the axes. Or it was trying to move through itself, but your X,Y values don't seem like that was happening.

WARNING Check with Fanuc Robotics before attempting to power your robot with any type of inverter or phase converter.

I don't think you can use a 3 phase inverter to supply power to a robot controller. My understanding is that the inverter you listed is to power a 3 phase motor only. The inverter will supply a voltage and current to the motor and expects a certain load from the motor during acceleration and under normal load. A robot controller does not operate like a 3 phase motor.

A Phase Converter seems like a better fit for your application. It will convert single phase to 3 phase and doesn't have the advanced functionality of the inverter of accel and decel, etc. You will need to size the phase converter based on the manufacturers recommendation for your load. Again, check with Fanuc to make sure you will not damage the robot.

We set most of our robots up to resume with the UI[6] Start input. Go to Menu, Next, System, Config and set START FOR CONTINUE ONLY to FALSE and CSTOPI FOR ABORT to TRUE. This should allow UI[6] to resume the program without going back to the main program. We use the UI[18] PROD START input to return to the top of the main program.

You can set registers equal to the values, then pass the registers to the OFFSET program. I tried using PR[12,1] in the CALL but the build failed.

R[11] = PR[12,1]
R[12] = PR[12,2]
R[13] = PR[12,3]

CALL OFFSET(112, R[11], R[12], R[13])

Set a PR to Joint representation and then specify the degrees to move in the desired axis. Do a Joint move to that PR and only that axis will move.

Is it changing to the User Display and displaying a message to the operator? If so, you would have to remove those commands from the programs to keep the Data window open.

Yes, you can edit registers while the robot program is running.

OK, good to know. Thx. I had them wipe down all the surfaces so we could check for leaks.

Couple of our tech's replaced a M-20iA Joint 5/6 wrist assembly last week. (this robot has the through the wrist tube) We let it sit over the weekend and we are seeing some oil weeping out where the assembly is bolted to the Joint 4 casting (Fanuc Doc. says Joint 3). They cleaned the surfaces and applied the Loctite as instructed from the manual. Let it sit overnight before adding oil, etc. We didn't get to the exercise portion where we move the axes and then check the pressure. It only moved from the Mastering position down to the home position.

Are there any tips/tricks for performing this task? We are going to redo it tomorrow and was hoping one of the Fanuc expert tech's here had some insights. Thanks.

Firewall issue preventing robot ping to the computer? Maybe affecting connection to the robot webpage?

The Ethernet/IP scanner option is when the robot is the "master" and will communicate with remote Ethernet/IP devices "slaves". You will set up the EIP nodes in the robot. The Ethernet/IP adapter option is used when the robot will be a slave on an Ethernet/IP LAN. You would use the adapter option for both robots if the Compactlogix PLC is the Ethernet/IP master. Also, don't confuse the Ethernet/IP options with the Ethernet used in a regular network, they are different. Ethernet/IP is a fieldbus protocol.

Also note that 200 is the highest sensitivity setting and will trip out the easiest.

You can use an indirect reference for the JMP to make it very easy to jump to the LBL. The CALL would be the same as rafahil suggested

BROL2 program
! TEST WELDING PROG
CALL BROL1(1) ---> or 2 or 3 etc

Make sure you BROL1 program has a JMP to the end of the program after the moves so it doesn't continue on to the next LBL

BROL1 program

JMP LBL[AR[1]] Jumps to the label number in AR[1]

LBL[1]
L P[1] ...
L P[2] ...
JMP LBL[999]

LBL[2]
...
...
JMP LBL[999]

You can have the tool changer program set a register with the desired tool number. Then have a background task constantly compare that register to the active UTOOL using the variable mentioned above. $MNUTOOLNUM If they don't match then set it back to the register value of the desired tool.