I am receiving a MEMO-073 Program does not exist error message. I am not sure what is the cause. Is there a way of determining what programs are being called? Any help would be greatly appreciated.
MEMO-073 error
-
sjkent -
December 28, 2016 at 10:50 PM -
Thread is marked as Resolved.
-
-
If the program is being called from a parent program then it will stop on that line of code, and you should see what it's trying to call or run.
It also could be a program select issue such as pns, rsr, style, or other. Are you using any of those methods?
Finally it could be a macro triggered by IO.
Sent from my VS985 4G using Tapatalk
-
In the process of re-purposing robot with SpotTool to do simple pick and place. I had deleted all the existing programs and reconfigured IO. Tired to set up to start RST remotely from PLC via Enet. All the communications between PLC and Robot were working however I could not get the I/O to show enabled on TP and could not start program remotely.
I ended up restoring image back to where I started. I did not delete any programs only reconfigured I/O and parameters required to start from RSR.
I also did a controlled start and disabled the Spot Tool.Now get
INTP-347 (SWGMRS4,234) Read I/O values f..
PRIO-002 Illegal port numberWhen robot initially starts up, I/O enabled goes green and then goes yellow. I suspect that there is some program being run on startup that is causing this, but I can't figure it out.
PMC is also installed, I am not familiar with this, I looked at it on TP but it just ladder logic and it doesn't look like its calling any programs.
-
Is the PMC turning on or off any UOP signals? Are sure that the PLC to robot Ethernet is set up correctly?
Sent from my VS985 4G using Tapatalk
-
I went through the ladder display of PMC and it does not appear to be manipulating the the UOP signals. There are a couple of branches where there is some parallel logic to set bits but end result is that the UOP signal look correct. I went into parameters and Enabled 'Stop PMC At Startup'.
Communications with the PLC is working correctly. I see all outputs from robot and robot sees all inputs that I turn on.
-
Are you running any auto-execute programs? Check in menu>system>config. INTP-347 is a Karel error, so are you running a karel program? May be helpful for you to post a screenshot of your IO config as well.
-
I have RSR0001 in auto-exec. I don't believe there is a karel program running. IO config screenshots are attached.
When I have 'Stop PMC At Startup' enabled and try to step through TP program, I get MTCL-013 ENBL input is off. When i start PMC and then I am able to step through even when I stop it again.
-
There could be some conflicting items here. I would try to simplify and get rid of what you're not using. You have Ethernet ip and a PLC, so why do you also have PMC and device net? The robot can only have 1 master controlling the UOP. I
Next you have an auto execute program, rsr0001. Why do you need this if the PLC is starting the program? This could be a conflict as well.
Finally, are you sure RSR is what you want to use? The "other" method Is pretty much foolproof. Is RSR0001 a program you created for this application or is it a leftover.
Sent from my VS985 4G using Tapatalk
-
Thanks for your help thus far.
The robot was purchase used. It came with PMC, DN, and Ethernet ip options as well as Spottool. I do not have the original image so I have to work with what I have. I do not know if it is possible to remove the PMC and DN options.
RSR001 is a program I created.
Other robots in our plant use RSR so I was just trying to keep it all the same. I am not overly familiar with 'other'. I did change to 'other' and selected RSR0001 however it still did not work.
-
Did you try clearing out the auto exec program?
I don't think you can completely remove PMC but you should be able to disable it. Is there a reason you have it running. Is your PLC holding on the correct UI signals. 1,2,3 & 8.
Sent from my VS985 4G using Tapatalk