We have a system that is using four IRB340’s with 2 camera’s. Basically, we have two pick conveyors running under the four IRB340’s.
On occasion (which is really hard to troubleshoot) pickmaster locks up. Pickmaster looks like it is running, i.e. all the robots are green. However, when you try to click on the start project or stop project buttons the program is not responding. You are able to try and close pickmaster but of course since the project is running you can not close it. And you can not close it because it is not responding. There are no errors in the error log and the operating system is not dead. It is just pickmaster.
Has anyone ever seen this problem before?
Shane
Hi Shane,
Which version of PM are you using ?
I had a lot of lock up before upgrading to PM3.13 perhaps is this also you problem.
BR,
Fabrice
Thanks,
I have finally been able to get back on the plant floor and we are using PM 3.12.0008. I will try and upgrade to PM3.13.
I will let you know if it helps.
Shane
I have upgraded to PM 3.13; we get the same result. On occasion, pickmaster locks up. Here is some additional information. We have four IRB340’s and one IRB260. The 260 is NOT using vision but the 340’s are. All the robots are under the same PM project. When the system locks up the 340’s are the only ones that do not pick. The 260 continues to run just fine. So it is a vision thing right?
Could someone please help troubleshoot this?
Thanks,
Shane
Hi Shane,
I’m guessing you are using an 8100d frame grabber?
There is a driver update available. The problem you describe doesn’t match exactly the problems seen before, but it could be worth a try.
The download is found under the topic “Camera configuration”. Pleasem, follow the instructions included in the zip file.
Also, do you have the “Detailed Vision Information” dialog open when the computer locks up? If yes, try keeping it closed, and see if this makes a difference.
BR
Fredrik
I have now upgraded to PM3.13 and also I upgraded the frame grabber. The only thing I have not done is update from RW5.09 to 5.10. I will try that this week.
Still getting the lock up issue. I have now been able to keep the log file that PM generates. I get the following information:
09:04:07 Status 4098 RIS status: Project A running
09:11:37 A Warning 12309 Failed to get image from camera.
09:12:04 A Warning 12308 Images are triggered too frequently. Time between triggers: 312 ms. Time required for last image: 312 ms
09:12:53 A Warning 12308 Images are triggered too frequently. Time between triggers: 343 ms. Time required for last image: 360 ms
09:13:28 A Warning 4316 Old scene discarded from Rob2 Flip Pick Area. Missing item positions. Scene info more than 10 seconds old.
09:13:28 A Warning 4316 Old scene discarded from Rob4 Flip Pick Area. Missing item positions. Scene info more than 10 seconds old.
09:13:28 A Warning 4316 Old scene discarded from Rob3 Flip Pick Area. Missing item positions. Scene info more than 10 seconds old.
09:13:28 A Warning 4316 Old scene discarded from Rob5 Flip Pick Area. Missing item positions. Scene info more than 10 seconds old.
09:13:31 A Warning 4316 Old scene discarded from Rob4 Flip Pick Area. Missing item positions.
09:13:31 A Warning 4316 Old scene discarded from Rob5 Flip Pick Area. Missing item positions.
…
…
09:13:37 A Warning 4316 Old scene discarded from Rob3 Flip Pick Area. Missing item positions.
As you can see I go from 9:04 to 9:12 without a problem. It looks like I may have a trigger problem? What could I do? Should I lengthen the trigger time? Remember, this is an intermittent problem. The system will run for 3-4 hours just fine and then it will get the “Failed to get image from camera” error and everything hangs up.
Any thoughts?
Shane
What is the search time for one frame for each camera? By opening the PatMax or Blob configuration window you can press the search button and see how long time in miliseconds the analysis is going on. If there is a complex PatMax model (with a search time of 300ms) is performed with 5Hz you would essentially need 1.5 seconds to analyze every 1 second, this will obviously cause problems. Hence, it can be a good idea to summarize how many pictures each camera take and how long time each model consumes that is applied on each picture for each camera. Altogether, the search time may not exceed available search time.
Good luck.
Erik
An update:
Erik, my model is very simple, i.e. no PatMax. It takes under 10ms for the search time.
I have upgraded everything on the system and it seems to have fixed my issue. I upgraded PM, RW, and the frame grabber. I will followup if I have the problem return.
Shane
Hi,
I also face same problem too with the error ‘09:13:28 A Warning 4316 Old scene discarded from Rob2 Flip Pick Area…’ , I have upgrade to PickMaster, and RW5.10. When I upgrade PM 3.1 to PM3.13, I was asked to choose the frame grabber used during PM installation.
In this case, do I still need to do the manual frame grabber upgrade.
Hi BoonHua,
4316 alone does not mean that there is a problem with image acquisition. It simply means that PickMaster was unable to match a picture to a conveyor position. Do you get a lot of these messages, or only single occurrencies?
To answer your question about the framegrabber upgrade: It is not included in any PickMaster release. It is only available as a separate file, and should only be used in case the normal driver does not function properly.
BR Fredrik
Hi Shane,
I would like to know if the lock-up problem was finally solved?
If so, what do you think was the solution to the problem (change of hardware/software etc.)?
As a member of the PickMaster development team, I’m interested to know this so that we can improve our product in the future.
Thanks,
BR
Fredrik
Fredrik,
I would like to say that the problem is fixed. I can not be 100% sure as to the fix though. Of course I was in the middle of a start-up and was under pressure to get it working. So I was unable to do any type of systematic troubleshooting. This is what I did.
- Upgraded the frame grabber driver.
- Upgraded RW to 5.10
- Upgraded PM to 3.13
Our line is not running right now for other reasons. Therefore I can not be 100% sure the problem is fixed.
I will let you know if it comes back,
Shane