Your comments
After writing my question I got an idea. Griping and fixing work now with the following changes in the fixer script.
1.
This change stops double list of Mus in MUS Entered.
2.
Now the fixer can fix Mus even if they are fixed by a grip script.
Please verify if this changes are okay and please take a look on my first question above.
Hello,
if I use PLCSim Advanced I can read/write signals which are used in hardware configuration? I don't understand where the difference is between PLCSim and PLCSimAdvanced.
How is the behaviour if I use a real PLC. Is there also the problem that signals used in hardware configuration can't be changed?
Thank you!
Hi Thomas,
I would like to bring up this old thread again.
1. Do you know why the hardware configured signals can't be changed by realvirtual?
2. Do you know if other simulation software tools have the same problem?
I'm asking because I'm interested in the suggested way how to solve this in the PLC program. The real machine works with the configured Inputs/Outputs.
This means that there is some additional program work necessary in the PLC program. for e.g. mapping to markers and use markers in the simulation.
At the same time I think no machine builder is happy about more coding at the PLC program to make a simulation possible.
Exactly.
I thought I can do a workaround by using the property "Parent Before Fix" but it's not updated in the MU script when MU get gripped by two grip scripts.
Looking forward for your solution. ;-)
I realized that the Property of MU (Script) "Parent Before Fix" doesn't get updated between handover of two Grip (Scripts).
Gripper 1: St.20_RobotGripper
Gripper 2: RT_Pos2_Gripper
Thank you for any advices.
I wanted to add that I think the function to move around MUs and the possibility to delete them by "DEL" keyboard button is necessary to manipulate situations to solve problems without restarting the simulation during test runs.
Looking forward for your solution. I guess it will be much more better than my solution if I get one.
Deleting and re-importing the realvirtual.io asset did solve the problem apparently.
Thank you for your help!
Okay, thank you for your reply.
Good morning,
For some reason I have much trouble with this simple behaviour.
In the demo the box gets lifted out by a drive in linear Y direction. This is what I want without the further guided transport. If I delete the guided transport gameobject in the LiftOut then the lifting stops working.
What Am I missing?
Customer support service by UserEcho
Hello Support,
thank you for the video and the support in this case.
This thread is corresponding the my other thread "Handing over MU between two grippers".
I think I need to clarify what I want to achieve a bit more.
Yes I wanted to use the Fixer function which is implemented into IKTarget.
So the robots are using Fixer to pick/place the MU and the round table is using Grip.
The RT gripping is controlled by PLC and the robots gripping is usually (as far as I know) controlled by the robot program itself in real machines. To me the new fixer function in IKTarget seemed to be created right for this case.
I am not sure why I needed to make the changes in the Fixer (script). But without the changes I couldn't make it work. The robot couldn't pick the MU with the fixer function in IKTarget while the MU was gripped by the Grip (Script).
Ofcourse I am sending you the project.
The bigger and physically unlogical problem is handing over between two grippers/fixers.
1. Gripper A is gripping/fixing the MU.
2. Now Gripper B is also gripping the MU. The new parent for the MU is Gripper B now.
Now we are testing home positioning process by PLC program.
3. Gripper B opens gripping. Gripper A is still gripping the MU and now the MU should change parent to Gripper A.
But currently in simulation the MU is just falling down / not in parent with Gripper A.
I couldn't find an easy solution yet for this by editing Fixer/Grip/MU scripts.