Posts by fastfingers

Quote from HawkME

Sometimes things behave a little differently in teach mode. I've never seen anyone use a time based motion command like that. I'm not sure there are any real world use cases for that.

I found only one use of time based motion years ago in a press tending application. The robot moved into place under the press and waited for the press to finish its cycle and open. The press opening motion was time based and the robot start and end points were taught with a time based move to the end point that matched the press move time. It worked really well.

Other than that, I haven't had any other instances where I used that instruction.

On the R-30iA, I believe you lose the handy CUT function within COPY/PASTE when editing programs.

I have noticed that iRVision processing time is noticeably longer on the R-30iA compared to the current controller generation.

No matter how much of the fancy functionality you lose with the older generation controller, it can still be programmed to do what you need it to do. There are plenty of those old dogs out there running production.

You can map Auto/T1/T2 status through the safe I/O but I don't know of any safe I/O for the TP on/off switch. What are you trying t accomplish?

Roboguide has some good tutorials. Look in the help menu in Roboguide and see what is available. This will not completely solve your problems, but will give you a good base to build upon.

It can be done.

The electrical assembly guys in our shop have done it in the past and claimed it is a pain to hijack the EE wiring.

Quote from DS186

This is indeed unbelievable. This easy and obvious way to get the DCS code makes it a bit useless.

Just wait until Fanuc hears about this. They'll change it.

Quote from 00Red

Do yourselves a favor and create a TP program, chose an open register (in this case Register 1 was open) and put in the following code:

R[1] = $DCS_CODE

Run that line and look up the value in your Data Registers.

Tried this in Roboguide and it works. Who would have thought?

If you need the robot to stop pushing at a certain value of applied force, touch skip might be an option that would work. You would need to determine through initial measurement the force applied based on servo disturbance feedback and use the disturbance values when running in auto mode.

Force sensing, as mentioned above, is the Cadillac and will offer the most flexibility.

If by 'polish' you mean using abrasive belts on the tubes, these are very slick for manual and robotic applications:

https://www.garboli.com/en/products/gr…ines/lpc-90-135

The head and abrasive belts rotate around the tube and there's no need to rotate the part. Bend tubes can also be fed through these machines.

If you are buffing using compound an a fabric wheel, different equipment will be in order.

Maybe reload pendant firmware?

That's a new one! Never saw that before-sorry I can't help.

Quote from SkyeFire

There are vendors that sell robot covers of different kinds, for different environments.

Just one I found after a quick Google: https://roboworld.com/robosuit/overview/

I have used Roboworld suits many times. Very well made and reasonably priced.

If you have Roboguide, you can try some of the tutorials for vision and line tracking. Fanuc does a pretty good job with the tutorials. You can even connect a real camera to Roboguide and experiment with vision setup. There are some threads in this forum that cover camera connection.

The search function under the Roboguide help menu doesn't work very well in my experience.

Good luck!

Highlight line 177: SCR and press DETAIL or Enter key > scroll to $tpmotnenabl > check/change the value.

Check the system variable $SCR.$tpmotnenabl. Jogging is disabled if set to 1. Set the value to zero and you should be good.

Download from home or elsewhere. I had trouble with a corporate firewall stripping the file. This was one of the few instances where I had no choice but to perform the Auto Update. After downloading without the firewall, I ran the apverify successfully.

Rack 48 looks to be mapped I/O for LR Mate peripheral connectors.

SolidWorks for me.

Quote from VS Manufacturing

( with correct Tool Frame – using a pointer that attached to J6 so only Z length entered in Tool Frame)

Forgive me if this has already been addressed... How was the tool frame taught? When jogging about the TCP in Tool mode, does the pointer tip remain stationary?