Aah, yes that would be a possibility:
- already working connection: PLC is controller, robot is device;
- new connection: PLC is device, robot is controller.
or of course:
robot is controller and both PLC are devices.
Aah, yes that would be a possibility:
- already working connection: PLC is controller, robot is device;
- new connection: PLC is device, robot is controller.
or of course:
robot is controller and both PLC are devices.
Think that's not possible. What do you want to do with a robot that has those four axis? The robot can't make any linear movement, only silly combinations of arcs.
Be patient. If someone here can help, you will get help without bumping every 24 hours.
Members here help in their free time. Bumping and pushing doesn't help either.
No. But the axis was integrated by Fanuc, the robot came complete with axis 7 fro Fanuc.
.. The robot's computer has an embedded version of Windows 7...
So why not using windows shares?
Afair was the software included on drive D of the robot, when interbus option was installed.
Read and understand all of the above posts, everything is said.
You are right, therefore I wrote 'should'.
In case of used interbus cards, it is possible that they where used with CMD tool, then on the card the topology is stored on the card, and the bus will not really run.
There is no solution. The robot has limitations about the occupied amount of bytes in memory. You have to live with it.
Everything is already said, but not from everyone.
Split the motion into segments with different speed.
The process to install I/O with profibus or interbus with krc2 is the same as devicenet ?
No not 100%.
The iosys.ini part nearly is the same, but:
for profibus: you have to generate a .ldb file with Siemens Step7 or NCM Manager and configure pfbms.ini on the robot.
for interbus: you should use Phoenix Contact CMD Tool for configuring the Interbus card.
If you have an actual AOA backup, you can restore the old image, and the restore the AOA.
Somewhere in the menu of the TP you can save the GSD file, can't remember the exact menu position. Have a look around or in doubt rtfm.
You should not choose the robot by the panel you want to use.
For choosing a robot different parameter should be decisive.
Repeatability, rigidity, price, path accuracy....
You can use an access point as wireless client (at least some AP are able to be used as client).
well, I know the math exists to do the 6DOF transform, but I'm not sure how to do it in RAPID.
You can do it in Robotstudio very easy with drag and drop targets from one wobj to the other.
In any case the values for new external axis has to be adjusted for the targets.
In the backup .
The key should be in the file system.xml. Open it in a text editor and search for 'key'.
Shit happens. Happy reteaching.
If you know the distance from old robot mounting position to the actual one you can create a workobject with this distance and change the programs to that workobject.
Das dürfte nicht der Grund sein. Den Treiber kann man in der Datei IOSYS.ini auskommentieren.