Teilen Sie Ihre Erfahrunge und Wünsche mit uns und anderen Usern!
Suspend the use of paths built by IK
Hi,
I created the path after building the robot using the IK component.
When I select the loop, it works the way I want it to.
But now my requirement is that I want it to be able to pause the movement after receiving a certain pause signal value and continue the movement after receiving a move signal value.
May I know how can I implement that functionality.
I see that there is a WaitForSignal property in the Script but it is read only, can I use this property? How can I use this property?
PATH IK and target problem
I followed the inverse kinematics tutorial. I am using the ABB IRB 1300 robot. The issue I am having is that my robot's TCP is not aligned to the root. It is causing issues and when using the Path IK, the target is not showing (red dot) and the robot's not moving at all. My friend is also having a problem with the Path IK, the target was stated to be unreachable.
area read Mode with DB
Hello,
is there anyone who can explain, how I can get the data, when I use Area Read Write Mode in the S7 Interface? I tried to read form a DB, which worked well. So the connection to my CPD is OK.
Thanks
Building to Android compiler error: Missing reference to SharedMemoryInterface in SharedMemoryInterfaceEditor
When switching build mode to Android, the SharedMemoryInterfaceEditor is still compiled but SharedMemoryInterface is not.
First line in SharedMemoryInterface:
#if UNITY_STANDALONE_WIN
First line in SharedMemoryInterfaceEditor:
#if (UNITY_EDITOR && !UNITY_EDITOR_OSX && !UNITY_EDITOR_LINUX)
Clearly, in android, the SharedMemoryInterface is not declared but SharedMemoryInterfaceEditor is, leading to compiler error.
Work around: Change first line in SharedMemoryInterfaceEditor to:
#if (UNITY_EDITOR && UNITY_STANDALONE_WIN && !UNITY_EDITOR_OSX && !UNITY_EDITOR_LINUX)
Thanks a lot - which version are you using. In the current release we are able to build to Android? The compiler define of your work around is a solution - in current release it should be solved by the assembly definition.
Fixer not fixing properly?
Hi,
I am quite stumped by the Fixer's behaviour. This should be simple functionality and it does not seem to work for me. It appears linked to how the "MUs Fixed" array is updating (or not updating).
I have this gripper (grip & sensor) (yellow), MU (blue) and Fixer (red).
Picking works fine.
At this point, the MUS Fixed array is empty and the MU has been picked.
As soon as the MU is moved into the Fixer the MUS Fixed array updates but the MU is not actually fixed. And 'Place Objects' on the Grip has no effect.
At this point, 'Place Objects' was clicked while in the Fixer collider but was not Fixed.
But if I clear the MUS Fixed array then re-enter the Fixer with 'Placed Objects' on, the MU becomes Fixed.
Picking works but the MUS Fixed array is not cleared.
Placing again will not work until the MUS Fixed array is cleared manually. MUS Entered array is never updated.
I notice that in the Gripping MUs sample this does seem to work and arrays are updated properly. But there's a number of signals in use in that demo. Perhaps it works only when PLC signals are used. But it would be nice if it worked without the PLC signals.
Hi,
I have setup the situation as you described.
The settings in my Grip-script are the following:
With this settings it works when you switch between pick and place during the game mode. The Fixer only keep the MU if the gripper is set to place. The gripper always holds the higher priority.
According to your screen shots I'm not quite sure how the picking was able to work because there is no pick mode defined.
(for this have a closer look in out documentation: Grip - realvirtual.io User Documentation (gitbook.com).
Kind regards
Christin
logicstep
I added a Logicstep script, but there is an error in the above screenshot, what is the reason?
Hi, this is a non blocking step - this is why it is getting in a infinite loop.
Assertion failed on expression: 'CompareApproximately(SqrMagnitude(result), 1.0F)'
I played the project on the "Game" screen. However, when I click the right mouse button, I get the following error and nothing is rendered on the "Game" screen.
- Assertion failed on expression: 'CompareApproximately(SqrMagnitude(result), 1.0F)'
UnityEngine.Quaternion:Internal_FromEulerRad (UnityEngine.Vector3)
- transform.position assign attempt for 'Main Camera' is not valid. Input position is { NaN, NaN, NaN }.
UnityEngine.Transform:set_position (UnityEngine.Vector3)
Ubuntu22.04, Unity 2022.3.7f1, realvirtual.io Digital Twin Professional 2022 Ver.2022.6.0Ubuntu22.04, Unity 2022.3.7f1, realvirtual.io Digital Twin Professional 2022 Ver.2022.6.0
Got it - Linux is not supporting Screen.dpi. You should insert this in line 456 in SceneMouseNavigation. It will be part of the next release in 3-4 weeks, for the moment you should change the code manually.
#if (UNITY_EDTOR_LINUX || UNITY_STANDALONE_LINUX)
DPIScale = 1;
#else
DPIScale = 144/Screen.dpi;
#endif
Error importing the Package Ver.2022.6.0
I get this error when I import the package to Unity:
Unable to update following assemblies:Assets/realvirtual/CADLink/private/CMC-Kiesel/Plugins/CMCKiesel.UnityNativeImporter.dll (Name = CMCKiesel.UnityNativeImporter, Error = 131
Ubuntu22.04, Unity 2022.3.7f1, realvirtual.io Digital Twin Professional 2022 Ver.2022.6.0
We changed and adopted all compile switches and Settings to Unity Editor on Linux. It will be in a few hours as a patch on the Unity Asset store. Please note, that SpaceNavigator, some special Interfaces (like SHM based for Simit) and CAD Step Import won't be available on Linux.
Connection with hololens 2
is it possible to use the hololens 2, robo dk and realvirtual.io, so that I can manipulate the robot in augmented reality using the glasses (using my hands to move the robot or use gestures)?
Customer support service by UserEcho
