May 24, 2019, 11:44:52 PM
Robotforum | Industrial Robots Community

xxRecent Posts

Pages: [1] 2 3 ... 10
1
Still available, pictures below. Thanks
2
Fanuc Robot Forum / New version of fapt
« Last post by MUNIACO on Today at 07:41:59 PM »
Hi guys,

Anyone have a TRIAL of fapt ?

I need to open a PMC file of a new robot, and my version doesn't support it.

Send pm please.

Thanks

Inviato dal mio Redmi Note 7 utilizzando Tapatalk

3
INTP-348 (%s^4, %d^5) Write I/O value failed

Cause: KAREL program error. The digital output signal cannot be output.
Remedy: Refer to the error cause code. Use MENU to display the Alarm Log screen.

4
Fanuc Robot Forum / Re: Srvo-068 DTERR (GRP 0 Ax1)
« Last post by daniel.piton on Today at 07:24:18 PM »
3.18.10.68 SRVO-068 DTERR alarm (Grp:%d Ax:%d)
Cause: A request signal was sent to the serial Pulsecoder, but no serial data was returned.
Remedy:
1. Check the connection of the cable between the Pulsecoder and servo amplifier. (If the alarm
is occurred at robot axes, check the connection of the robot interconnection cable (for the
Pulsecoder)).
2. Check the shielding of the above cable is connected securely to the grounding plate.
3. Replace the Pulsecoder.
4. Replace the servo amplifier.
5. Replace the robot interconnection cable (for the Pulsecoder).
Refer to the Controller Maintenance Manual for more information.

5
Kawasaki Robot Support Forum / Re: How to modify Position Variable
« Last post by Alexandru on Today at 06:58:45 PM »
Hello, lsd_def is the name of the point.

Type in the terminal or in the keyboard menu list /l lsd_def (location), it will return you the transformation coordinates of the point.

POINT lsd = lsd_def means that a new point lsd is created having the transformation coordinates of the lsd_def point (location).

The robot can move to the lsd_def point as you wrote with LMOVE function, i would do it in CHECK mode. Or if the robot can reach the point without hitting any obstable you can do it in repeat mode having the motor and cycle on by typing in the terminal

DO LMOVE lsd_def

You can save the location of the point again having the same name:

HERE lsd_def
6
Fanuc Robot Forum / Re: Srvo-068 DTERR (GRP 0 Ax1)
« Last post by pdl on Today at 06:45:11 PM »
Do you have a servo gun attached to the robot?

Group 0 is normally a process axis.
7
You have both the KRC and the Cognex set up as Clients.  One has to be a server, the other has to be a client.

Look up "Native Mode Commands" in the Cognex documentation.  That can be carried out using simply ASCII strings, sent Raw via EKI, with no CAST instructions.
8
Kawasaki Robot Support Forum / How to modify Position Variable
« Last post by Ethan Nash on Today at 06:16:40 PM »
Hello all, I've got some Nachi experience and am muddling my way through Kawasaki right now, I have a Series E Controller with programs wrote in AS Language.  I have a line that reads "POINT lsd=lsd_def" and I believe that to mean that we are making the Position Variable "lsd" equal to that of a real point, "lsd_def".  I need to change this point and I have searched through all of the robot programs and I can't seem to find "lsd_def" anywhere.  Is there a specific location that all Position Variables are stored?  Can I just create a LMOVE lsd_def and then modify the point there and then delete it?  Any and all help is appreciated.
9
KUKA Robot Forum / Re: Dynamic Braking Triggered
« Last post by SkyeFire on Today at 05:52:22 PM »
It's not an error, it's a status report.  Dynamic Braking is triggered by other errors that need to halt the robot's motion.
10
KUKA Robot Forum / Re: Offline programming
« Last post by SkyeFire on Today at 05:48:12 PM »
Yes, but...

The first problem is that the CAD file, and the robot, may be using different coordinate systems.  So you would have to correct for that.  There are multiple ways to do this.

You could then extract the XYZ data of points from the CAD and put them into the robot program directly. However, the rotation data (ABC values in KRL) is more tricky -- robot simulation software can usually be used to export this data in the correct format and frame of reference for a specific brand of robot (every brand uses their own), but generic CAD, probably not.  You might have to do some creative translation.  If you want to play in this area a bit, the free version of RoboDK can help you understand just how this works.

The final problem is that the CAD data seldom ever matches the real world closely enough.  Even the major robot users, like Ford, GM, BMW, etc, struggle with this.  The "holy grail" is to build an entire robotic plant in CAD, create all the programs in simulation, then, when the hardware is all in place, simply download all the programs to all the robots and hit Go.

It never works.

Well, it can be made to work, but requires either the real-world and CAD to match in every detail, or some very careful coordinate measurement and conversion work to correct for the differences.

However, you can create a pretty decent "starter" program, this way, that requires only minor touch-up on the shop floor, with the teach pendant.
Pages: [1] 2 3 ... 10