ignore this message...
Posts by panic mode
-
-
[size=2]of course...[/size]
[size=2]only slaves have device description files so that master(s) can know how to use("enslave") them, not the other way around. [/size]
[size=small]you are not exactly mastering your robot configuration... [/size]
[size=small]to become a master it takes effort - you need to train and read a lot. [/size]
[size=2]in comparison, it is a lot simpler to become a slave - one just need a master. (but don't confuse simpler with easier...)[/size]
-
[size=2]of course not... you are not even trying to understand the code. [/size]
-
read CORRECT manual. what you want is available on KRC4 but not on KRC2
-
read the SafeOp manual.
using Ethernet based safety (CIP safety, ProfiSafe, FSoE) gives you access to all signals.
using parallel interface X11+X13 gives you subset of that. for example you cannot change safety tool (it is always 1), plus you only get 8 safe inputs and 8 safe outputs. -
-
-
No.... EL67xx are not IOs, they are bus interfaces. One is master and the other is slave. Neither have IO points but if your gripper has ProfiBus interface, you can connect it to ProfiBus Master (EL6731).
if your gripper requires discrete IO, you can add IO modules to existing bus coupler, for example at the right side.
Then you need to modify current WoV configuration, deploy project and activate it.
After this your IO should be operational. -
-
[size=2]EK1100 is a bus-coupler only - it has no IO points. To actually connect field signals to it, IO modules ('slices') are needed.[/size]
[size=2]You misread - WoV is never installed on KRC4. Copy of installer is placed there. You need to take that copy, put it on your machine and install it there. [/size]
-
this is what windows shows when it detects something but does not have driver for it.
-
when powering off with low batteries, robot looses mastering and sometimes hdd can get corrupt.
-
did you get documentation and software that was supposed to be with it? did you make any backups?
-
robot is checking your preparedness and status of your backups.
-
any blown fuses on ESC board? any cables left unconnected? correct version of board?
-
don't place any installers on C:\, that will reduce amount of free space. installers should be on external drive (USB or shared network drive).
if you still don't have enough of space on C:, you can do what i did:1. backup everything that is on D:\ to your host HDD or external drive
2. delete D:\ partition
3. increase size of C:\partition
4. put back files on D:\ -
check parts and docs DVD, see READ FIRST
-
DEFFCT REAL ASIN(x:IN)
DECL REAL x
RETURN 90-ACOS(x)
ENDFCT -
as far as i know there isn't inverse function for SIN in KRL. it is not needed because there is one for COS.
-
[size=2]1. robots are meant to move and do work. wast majority of applications require robots to move as fast as possible because cycle time correlates with productivity (it is a simple economics).[/size]
[size=2]2. measuring weight requires stopping (settling down of readings) to get any kind of accuracy. [/size]
[size=2]3. determining more parameters such as CoG, inertia requires motion but this is not just time consuming, it is complicated to calculate (require accurate dynamoc model of the mechanism including joint frictions). if it wasn't everyone would just write their own version of LDD instead of paying for tech package. [/size]
[size=2]4. measuring load using motor current is possible but poor. it is comparable to determining weight of a car-driver by looking at fuel consumption. this is why we tell robot what to load is and not the other way around. this is why truck weighing stations [/size]
[size=small]5. why not focus on tasks or solutions that are within your abilities? why use most complicated approach? if you need to measure weight, just add weighing scale and be done with it.[/size]