Posts by Lemster68

Did you save it back to the HOME directory before restarting?

Connect how? With robotstudio? If so, do you have a license for RS?

Did you make sure that your PC IP and subnet are compatible? I think that just the service port is DHCP.

Probably didn't set the payloads right is the usual reason.

Autostop should never stop the robot in teach, are you sure that is the only part of the runchain that opens? Are ES, GS and SS BOTH light on for each?

So you have safemove, it should still be telling you why it is not allowing motors on. Have you tried another pendant? Maybe the enabling device is faulty.

Yes

So you need to ensure that the GS, ES and SS runchains are closed (lights ON).

The ability to read a manual and to understand it, maybe not completely the first time, but persevere. Read others and re-read, things will reinforce each other and make it click. Study as many different programs as you can get a hold of when you understand how instructions, motions and data all interact. When you get pretty good, you will be able to read a program and decide if they did something really clever or something really dumb or unnecessary. Hopefully you will be presented with challenges to write your own programs, tackle tasks that you never had to do yourself before. Unfortunately, that does not happen to many programmers and they lack the desire to rise above being just a "teach monkey".

Get filezilla.

The only times I had to use the IPPNIO.xml was when the robot had a slave device that it needed to communicate with. I think that you need to use Netnames+ that comes with the utilities to give the controller a Profinet name.

In order for data to be shared between tasks, they Must have the same name in all tasks and they must be declared as PERS.

Use a text editor instead of RS, It is likely that it is saving in an incompatible way for S4C+. Add it to CAN2 if it is external.

Quote from Nation

That is what I am not sure of.

One way to test would be to put in a really heavy payload when you actually have a light payload and see if the arm overshoots its programmed points a little bit.

And you could adjust the collision guard to be more sensitive, triggering a false collision.

Save your EIO.cfg and edit it using a text editor. You will find the necessary information for vendor ID and all that in the EDS file. You will have to read it and take the info you need from it into your unit type in the EIO.

You can see where I did something similar with the ArgName function like I mentioned here:

Code to share

You can add a description to the EIO signal definition and then you would need to use ReadCfgData to retrieve that description also.

Use the Function ArgName(signalname) if you have it available. If fetches the original data object's name.

Yes, the PLC side will be in the portal, but I don't do PLC's. Maybe there is someone else here that knows about that. You will need to configure the robot as needed also. Use robotstudio or the control panel.

Did you make sure that the robot and PLC match in the configuration of both input size and output size?