Posts by Lemster68

We don't either, but if you tell us what version of the controller you have, then someone might.

Do you mean an array?

Why can't you get support from the company that sold it to you?

No, I don't.

You can try it to see if it comes back online. Sounds like you have major power supply or wiring issues that need to be solved.

Have you cycled power? Are there MS and NS status led's on the unit?

Not that one.

I would ask for a replacement under warranty.

The Arm should have a sticker which reads 66-XXXXX 2.5/225, where the XXXXX is the low part of the serial number, the following number is the reach in meters and then the last is payload in Kg.

Be advised that Fanuc does not allow us to publish or post those here (or anywhere, for that matter). Best thing is to pester them and sign up for what you can on their site.

Strange business model, to keep people from being able to readily learn their robot, IMHO.

If that is the same TCP used in all of them.

I think FAT32 is OK. Why not download it directly on the service port?

Are you copying a boot image or did you create the system in robotstudio?

Are these programs taught in user frame coordinates? If so, was that user frame taught with the bad tcp?

The older Robotstudio required an empty USB drive.

What version of Robotware/Robotstudio?

Try running RS as administrator.

Use program shift with your good TCP.

It would probably require some coordination with a PLC programmer so that their code is ready to accept new error messages that are being sent. You might just send over simple group output to the PLC, which you both must agree what number corresponds to what error. Alternatively, you could just send the error number over, but there are so many error numbers that could be a massive task.

Maybe you already have a group output to send error codes. If you don't then you will need to map one and agree on which codes get sent to be displayed on PLC.