I confirm the default post processor for Universal Robots (called Universal Robots) includes the subprograms. I just tested a sample project with the latest version and it works.
What post processor are you using? Can you share your RoboDK project file?
We tried with the default Universal_Robots_URP post processor file and We attached the Post processor file and the station in here. It was working flawlessly with the program generation till now and we just updated RoboDK Because we were having issues with our Dobot CR5 post processor. And now the driver for Dobot CR5 is working the program generation for UR10e is causing trouble. When we generate robot program for the UR10e the script files has all the subprograms but the URP file when we load it in the robot, all the subprograms that should have been added into the main program as one program are now just program calls. In the station We attached here, there is a program called "Laser_base_welding_small_block", which is the one we tested it with now.
It looks like your RoboDK project does not have the UR robot linked with the Universal_Robots_URP post processor. If I try generating the program with the default Universal_Robots_URP post processor I obtain the file attached.
We get the exactly the same script file, it is with the .urp file that we get the errors, it posts fine into the robot via filezilla. Attached are the pictures of the error the UR is giving for the generated .urp file
Not much has changed with the Universal Robots URP post processor in the last few months.
What version of RoboDK were you using before? If you are not sure, just an approximate year/month would be enough to better narrow this issue.
Are you sure you didn't make any changes to your programs or your robot controller?
07-29-2024, 03:18 PM (This post was last modified: 07-29-2024, 03:20 PM by ajit.)
Our current version is 5.7.4 and our previous version was 5.5.2
We did make changes to our station, we added the Dobot section of it. But we have saved versions of the station without it and we get the same results.
What could cause this? it has put a stop to our production completely and we are pulling our hair. We overwrote the .urp that was welding for us everyday when we added the Dobot successfully and now we are at a standstill.
We can run the program from RoboDK with the wrong speeds and some calls are missing for Smartshift integration but production is halted. It's not a connection issue we think more of a configuration that got messed up. Without help we are unable to resolve it.
When we ran into this issue we upgraded our UR from 5.12.4 to 5.17 just to be sure.
If you can provide us more information about the version of Python you used and/or the faulty URP file we can better investigate so this issue does not happen again in the future.
