pmProject_diStop Does not stop project [PickMaster 5]

PickMaster
1

We have traditionally used a PLC to signal (pmProject_diStop) when we needed to stop the project to reset everything. When we pusle this signal, the project does not stop. We have tried from both the PLC, and simulating the signal. The stop project on the teach pendant still will stop the project.

Could there be something in one of the modules not working?

Thanks!

John

2

Hi,
first you stop the program execution and then you pulse the pmProject_diStop signal
as described in Users Guide 7.3.4 Extended I/O interface. When the signal is pulsed a trap in the background task will stop the project by executing a PmStopProj. See the PmProjServer.mod in the home directory for details.

BR Anders

3

When I pulse the pmSystemStop, the systems stops. Then when I pulse pmProjectStop, the project does not stop. I see the bit pulse, and it doesnt matter if I do it with the PLC, Robot Studio, or the teach pendant.

I am guessing it is in this trap. I will look to see if I have damaged the trap at all.

4

Hi, sometimes the flexpendant does not update the status of the project when it is controlled via I/O signals. Have you tried to reopen the PM5 FP window ? You can also check the current status (i.e. stopped or running) of the project with pmProject_goStatus.
/Anders

5

I am monitoring the status and it does not change. The only way I can get the project to successfully stop is on the FP and go to Project, Stop Project.

Any other thoughts to look for? Is it worth replacing my PmProjServer.mod or is there not a good chance that is the problem?

6

Hi, I think PmProjServer.mod may as well be the problem.
I would take a backup and compare it with a “clean backup”, i.e. a backup taken after an I-start.

7

I have compared and they are identical. I took an original copy of PmProjServer.mod in its place and I still have the same problem.

8

I have just found out the PMSystem_diStop is not working either. Hopefully this will help. Motors Off is working, and when we were doing a diStop, we also were pulsing the motors off. I was thinking we were stoping the system, but we were actually just turning the motors off.

9

webwiz/3040/API_JOB_5913_BACKUP_2010-03-04.zip

Please find backup attached. Any help on why the pmProject_diStop or pmSystem_diStop not working would be appricieated.
Thanks!

John

10

Hi John,

Where is the Program Pointer located for the background task?
Hint: In RobotStudio, open up the rapid code for the module PmProjServer, right click in the code an select ‘Show Program Pointer’.
It should stand on “WaitUntil PM_PROJECT_STATUS=PM_PROJECT_STOPPED;”

Which system input work/doesn’t work?

/Mats

11

The program pointer is sitting at Loop forever WaitTime 1000;
WHILE SignalsExist=FALSE DO
=>! Loop forever WaitTime 1000;

When I signal the pmProject_diStop, I do get a message on the pendant, but the project does not stop. The message is:

?oTarget reset after move of program pointer?_

12

Hi John,

That explains.
You probably get the warning 112372 “Missing PickMaster signals” when you boot up.
That is because some of the signals monitored by the PmProjServer module is missing. If any of the signals aren’t present, the ConnectAliasSignals function will fail and the task will hang in the loop.
Check the signals pmFlow_diStart and pmFlow_giSelection. They seem to be lost somewhere.

BR
/Mats

13

Thanks! Appears to have worked.