Regarding the performance of robots

Hello:

I don’t know if you’re aware that the robot only picks up boxes if the seal is facing upwards; it won’t pick them up if they’re upside down. Please see this video:

Hello @amjavi6

Thank you for reporting this.
I looked into it and noticed that the Factory I/O version in the video is 2.4.3. I tested this in the latest version, 2.5.10, and I was unable to replicate it.
My suggestion is to update your Factory I/O version and run the scene again to see if the issue persists. If it continues to happen, please share the scene with us so we can run more detailed tests to identify the cause and resolve the issue.

Hi Adriana;

Here’s everything you need to test any version you want without having to create the scene, and with any PLC by writing a simple program just to lift the box.

The other boxes work perfectly in any position, they don’t have any problems, only the one you see in the video. You can do any tests you need with the scene.

I’m sharing it in case anyone else wants to test their version as well.

Regards

Hello;

How are the box tests going?

I’ve finished contribution project 110 (I’ll upload the final video as usual), and I’ve continued testing the robot. In case it helps, it works in manual mode, so the solution shouldn’t be too complex:

Now we’ll analyze the case of user factoryio2 and their multiple PLC communication controlling the same system. That will be the next contribution to the community.

Regards.

Hello Adriana:

My two most important programming principles are the following:

1- Every part of every project must be compatible with every other part of every other project.

2- The projects I create must be long-lasting.

The first is obvious, and the second concerns updates. For high-level development, I can do it in C# and VB.NET. As you can see, I always use VB.NET whenever possible. Why? Because Microsoft will never update it again, whereas C# can receive updates. Therefore, the likelihood of applications not stopping working in the future is greater with C# than with VB.NET. I was discussing this with a channel user in this video:

Now you might be wondering what this is all about, which is normal. Well, you see, the same thing happens with Factory IO in my case—I repeat, in my case; I don’t know about other cases, I’m only speaking about my own experience.

You see… the version of the simulator I have isn’t the latest, but considering that the vast majority of updates are for platform versions that are updated very frequently, leading to problems for users, the updates don’t affect me at all. And since they don’t affect me, if we stick to principle number 2, the best thing is to continue with the same version so that principle number 1 is fulfilled. If we change, it could happen that scenes created today aren’t compatible with code created yesterday, which would be a problematic situation that needs to be avoided.

It’s different if everything changes; then it would be the same, but with the new simulator.

Regards.

Hello @amjavi6,

I understand what you mean.
When we release updates for Factory I/O, we make sure that our users will be able to continue using their previous projects. So you can update Factory I/O without worrying that your projects won’t work anymore.

You can use the portable version of the latest Factory I/O version, which is a zip file. You can find it here. This way, you don’t have to uninstall the version you currently have, and you can easily go back to it if needed.

Good morning, Adriana:

Obviously, it has to be as you say. In any case, I think the simulator is at its limit. We can’t demand more from it as it is. Any student who makes half the contributions I do will automatically cease to be a student.

I also think the creators of this simulator didn’t expect to see some scenes that challenge not only logic but also the behavior of software that wasn’t designed for such occurrences.

I hope the next version takes into account what has been done with this first one and allows us to overcome the limitations that sometimes prevent us from finishing the scenes as I would have liked.

I insist, I think it has reached its limit. If you know of any reason why this isn’t the case, I’d like you to share it here, and we’ll try to implement it, obviously provided it’s feasible.

Regards.

Hi Adriana:

After testing with the latest version, it still doesn’t pick up the box if it’s upside down:

But no problem, in the next contribution, which will be 113, we’ll invent a mechanism so that if the robot lifts it and the sensor doesn’t detect it, the mechanism will rotate it 90º. We’ll figure something out…

We’ll even take advantage of the simulator’s bugs, but first, contribution 112, which I think will be very interesting.

Regards

Hello @amjavi6,

I opened your scene on my computer and tried it out. Here, it works just fine; it grabs the box from any side.

However, I did it by manually forcing the tags. Could you please try this, instead of using the PLC to control it?

Hi Adriana:

Sorry, I should have uploaded that video nine days ago, but we’re waiting on some work and I thought I’d already shown it to you.

The manual does work, I tried it, but like I said, my boat sank…

Anyway, don’t worry, the box always comes out fine and there’s no problem. I just discovered it by chance…

Now I’m going to assist this user:

Regards

Hi Adriana:

As you can see, we haven’t reached the limits of Factory IO yet; in fact, I think we still have a long way to go.

I’m going to focus on the interesting project about “having a conversation with the machine.” After that, we’ll invent something to rotate the box using code so the robot can pick it up.

By the way, I already uploaded the video about the manual maneuver…

Regards.

Hello @amjavi6,

Thank you for sharing the video of the manual actuation.
Since it works just fine when manually forcing the tags, it should work when a PLC controls the scene. I ran a quick test with Codesys and had no trouble picking up the boxes.

I think this might be related to the logic or to the communication speed between Factory I/O and the PLC, but you’d have to test it further on your end.

Good morning Adriana;

You see, it only happens with the long box and in that position, but don’t worry, as I told you, we’ll rotate it using code and see the result…

Anyway, that bug isn’t important, since the box always comes out with the label facing up. I noticed it by chance (obviously it would be important if the boxes were in bulk). I’m going to make more progress on the “talking to the machines” project and then I’ll address your issue…

Regards

Hi Adriana:

Contribution 113 describes what happens with that box, at least for me, but it’s not important. If anyone wants to try it on their PC, they can download the scene and program it, then share the results.

On another note, I’m hoping for more information about the project we’re analyzing regarding “telegrams.” We’ll see how far it goes…

Regards…