“Frozen” Teach Pendant

Hello everyone!

Has anyone faced a problem where while using the teach pendant it completely freezes?

We can power it( we see the green light turning on when pressing deadman) but other than that the screen doesn’t move.

It happened twice already and we were obligated to turn off the power of the controller( which can cause more harm than good when doing it constantly)

Can it be a memory problem? Too many programs?

Is there a solution other than turning off the controller power? We really need to avoid this problem .

Rx130 CS8

Best regards

Quote from Galet

Hello,

If you have a other SP1, you can try to change it.

Control the connection and the cable between the SP1 and the controler.

What's happen when you stop all the applications ?

Have a good day...

We do have another teach pendant but it’s not in a better state that the current one 🤔

Quote from ElEsgalho

It happens something similar to me once.

Ensure all tasks continually running do have an instruction to cause an immediate sequence, this is, frees the CPU resources to jump to other tasks avoiding a deadlock.

Example of a deadlock task:

Code

do
   ...Something...
until false

Example of a task that sequenced immediately:

Code

do
   ...Something...
   delay(0)
until false

The delay(0) will free the CPU from the task running too many times, allowing resources to run other tasks, like the pendant update internal task.

Inside VAL3 manual:

The VAL 3 instructions that can cause a task to be sequenced immediately are as follows:

• watch() (condition wait timeout)
• delay() (timeout)
• wait() (condition waiting time)
• waitEndMove() (arm stop waiting time)
• open() and close() (arm stop waiting time followed by timeout)
• taskResume() (waits until the task is ready for restart)
• taskKill() (waits for the task to be actually killed)
• disablePower() (waits for power to be actually cut off)
• The instructions accessing the contents of the disk (libLoad, libSave, libDelete, libList, setProfile)
• The sio reading/writing instructions (operator =, sioGet(), sioSet())
• setMutex() (waits for the Boolean mutex to be false)

Hope this is your problem, otherwise good luck!

Display More

That’s a good idea.

I will see what tasks are running continuously and see if I can add that condition to avoid possible problems

There are tasks that are continuously running while waiting for information from the PLC to start the operation.

Maybe If I add an delay(0) to each one of them it can help?

Best regards