Your comments
Hi,
in the Starter Version there is no direct robot interface (e.g. Universal Robots or RobotStudio) included. Also the inverse kinematics (https://realvirtual.io/documentation/current/robotik.html) is not included which we have in the professional version.
For moving a robot the possiblities in Starter are very limited:
- you could move the axis itself - but this is very uncomfortable if you would like to reach a certain TCP-Position
. you could use the Simit interface (which is included in Starter) and use Simit robot interfaces - but you would need to get a Simit version and I am not sure if the robot interfaces will work in Simit demo. Here you can see which kind of interfaces are supported by Simit (https://support.industry.siemens.com/cs/document/109795246/simit-kopplungen-applikative-erweiterungen-der-schnittstelle?dti=0&lc=de-DE)
You can use Drive_Simple
https://realvirtual.io/documentation/current/drivebehaviour.html#Drive-Simple
and connect this to the UI Button
https://realvirtual.io/documentation/current/uicomponents.html#UIButton
by using a Signal PLCInput
https://realvirtual.io/documentation/current/interface.html#Connecting-Signals
With Connect Signal you can connect the PLCInput (of the Button) to the PLCOutput (to control the Drive).
We are currently working on a totally new UI overlay system for easily controlling things in the 3D scene but it will still take some weeks until it is getting released.
Hi Bo, the Version of the TransportSurface, in combination with ParentDrives, in our Release 2021.07 had a Bug. We moved in current Release 2021.08 back to Version 2021.06 - with some minor enhancements. We are still not sure if your use case will fully work (Christin is testing tomorrow) but 2021.08 takes back a severe Bug of 2021.07. Sorry - we will tell you asap as we thing that all use cases are supported in combination with ParentDrives.
Hello,
we are currently working on a solution to solve both problems with the transport surface by making it more flexible and independent in terms of possible use cases. We use your scenario for testing.
Ah ok sorry - this is a know issue - we already described it here:
Current working coupler.exe is available in the download area:
A meeting today afternoon between 14:00 and 16:00 is also possible
The problem is, that this is somehow a timing issue. We can't reproduce it on our computers and I thought that it is fixed because it was fixed in a Teams meeting with another customer. So only solution is that we closely work together, I will need to check your logs on your computer and maybe add additional debug infos.
Customer support service by UserEcho
Hello,
I sent the revised version of the Transportsurface as a script by e-mail. It has fixed the errors that I was able to reproduce with the test model.
Please check with your scene and give me a short feedback. Thanks.
For all other users there will be the release 2021.09 on Monday.