Doesn't Roboguide output a video file when you run the simulation? I think I've had this problem in the past and I found that the video files had true to life cycle times. My simulations were doubled, but the playbacks were proper.
Posts by AlanL
-
-
ANSI/RIA R15.06 American Standard for Industrial Robots and Robot Systems - Safety Requirements
-
Is there a disabling input in your DCS CPC?
-
Did they change their firewall settings? If you can't ping any of them remotely it sounds like a network issue.
-
You want the key on the controller switched to Auto and the teach pendant off. If you are trying to move manually with the teach pendant you want to switch the key to T1 and turn the teach pendant to on, then set them back to auto and off to start production again.
-
Are you using the Palletizing option? If not, when you have the palletizing option installed you get access to pallet registers that have row, column, and layer.
-
I don't know off hand if there is a direct mapping for a DO to an SOP, but you can use background logic. If you don't have an unused DO you can map one to rack 0, slot 0. Then background logic you can do DO[x]=SO[x]
-
Depending on where it's set you can sometimes get a few more degrees in: Menu > Next > System > Axis Limits
-
You can do ftp backups which are similar to AOTA backups using ftp. To do an image backup you have to use tftp and it requires a restart on the robot. You really only need an image of your robot once. Then you only really need to take a new image if you make a major change, like adding an option. Otherwise regular ftp or AOTA backups get everything you need.
-
-
I'm not sure if the vintage of robot applies to whether the option is available, but you can do a tftp image backup. You just need to download a free tftp app.
-
-
To add to what others said, once you have the problem corrected you'll have to go to your alarms menu and hit F4 "RES_1CH" and then press reset
-
Try this: FCTN > NEXT > QUICK/FULL MENUS
It looks like it's set to quick menus
-
I would take an AoA backup and pick the relevant files. All your .tp files, dicfgsv.io, mixlogic.sv, numreg.vr, posreg.vr, strreg.vr, sysegd.sv, sysframe.sv, and the dcs files (dcsioc.sv, dcspos.sv). There may be a couple more that are helpful, but those will get most everything
-
If you want to restrict the range you can go to menu > system > axis limits. I don't think this lets you extend, only restrict the range.
To extend the range go to system variables, $PARAM_GROUP[1], $LOWERLIMS to change your lower limits and $PARAM_GROUP[1], $UPPERLIMS to change your upper limits.
If you change the limits using the variables you'll have to restart. There is something about the interaction with joints 2 & 3, I don't really know what that is so I leave those joints alone. Also, I don't know how far you can safely push the limits. Whenever I have done it I've only done like 5 or maybe 10 degrees or so.
-
I don't think I've seen a robot run differently from roboguide. In cases where I run into the axis limits I put in a joint move to avoid the axis limit. When you are doing linear moves the robot will try to take the fastest route to the next point, sometimes that route ends up wrapping up the joints. If you put in a joint move that gets you moving in the direction you want while unwrapping your joints it should pick up as normal from there.
Also, you can extend the allowable range on some (maybe all, I don't recall exactly) of the joints. I usually avoid this unless it's needed for reach, not so much to accommodate moves.
-
We have that where I work. It's part of the image on our computers, something to do with security, we are only able to use one network adapter at a time.
-
You'll lose your mastering data. I personally wouldn't do it with an image, but if you do I would recommend talking to Fanuc. I would be concerned about a few things: because the options on each robot are purchased individually for that particular robot I would be worried about the legality of putting on an image that doesn't have the options paid for onto another robot, I would also worry about whether there will be hardware or firmware compatibility problems between the vintages.
-
Standard ftp, you want the directory: /md:\ in the robot. /md:\ is how I have it in WinSCP, something like Filezilla may be something like /md or some variation.
Anonymous login is fine, no encryption, port 21