Home › Programming
Discussion
Back to discussions page
Loïc
Posts: 16 Apprentice
Dashboard start program |
354 views
|
Answered | |
|
/ Most recent by Loïc
in Programming
|
6 comments |
Loïc
Posts: 16 Apprentice
I have a problem of integration. We are using two UR10 piloted by a Siemens automate and Dashboard connection.
We call the program then we send the start command.
Our first problem was that we had to send the start command twice. We tried to delay the sending of the start command and it worked quite fine then.
But now, one of the two cobot doesn't want to start at all. We tried several things but the only way to launch the program is by the play button on the screen of the cobot.
The program is getting bigger but is not finished so it can be a real problem...
Did anyone have this problem before?
Does anyone have an idea or a solution to this problem?
We call the program then we send the start command.
Our first problem was that we had to send the start command twice. We tried to delay the sending of the start command and it worked quite fine then.
But now, one of the two cobot doesn't want to start at all. We tried several things but the only way to launch the program is by the play button on the screen of the cobot.
The program is getting bigger but is not finished so it can be a real problem...
Did anyone have this problem before?
Does anyone have an idea or a solution to this problem?
Tagged:
Best Answer
-
matthewd92
Posts: 827 Handy
I have not seen this exact problem using the dashboard server, we send commands remotely to the robots including the play command. I do know in the latest UR update that came out yesterday they fixed something with sending play over the dashboard server when the robot is safeguard stopped, maybe it also addresses this issue, worth a try. This is software version 3.4.3.77, here are the release notes.
I hope it will work when we'll finish this project because I've written only half of the program...
Hence the program might not be fully loaded, when sending "play" a few ms later. Especially, if the program is rather big.
Since 3.3, the call only returns (e.g. "Loading program: someprogram.urp") after the program is successfully loaded.
Hence this might also be the issue, and resolves the problem, by upgrading to the latest 3.4.3.
We call the program via the Dashboard server. The robot answers well ("Loading program: <program.urp>").
Then we set the input associated to "Start-prog", we see that the input turns On but the program doesn't start.
This problem happens only after loading the program. If we set the "Stop-prog" and then set the "Start-prog", the program restart where it was. What is surprising is that it happens only on one UR10, the other works fine.
Do you have any explanation?
My next idea is to try to send the start with the command "play" via the Dashboard server, but as it's not the only "problem" that we have on this machine, I don't when we can try it...