question

Hi Phil and Kavica,

Per Phil's recommendation, I've uploaded a video I just made, "mayer_flexsim_video.mp4", it's about 14MB.

Similar to Phil's video, I created a left, top, right, and bottom path. Those path names are created properly (Path1, Path2, Path3, Path4). In previous models, I was getting just Path1 for all of them, but here path naming worked fine.

I then created a total of 10 Control Points, starting with two on the top path, two on the right path, two on the bottom path, two orphans out in the middle, then finally two on the left path.

All of the CP's on all 4 paths are automatically named ControlPoint1 except for the rightmost control point on the bottom path - it got named ControlPoint2.

The two orphans in the middle got named ControlPoint3 and ControlPoint4. Although those two are numbered sequentially (3 and 4), they are actually not named as the 7th and 8th ones actually created.

Interestingly, ControlPoint2 (bottom path, right) was not the last control point created prior to the two orphans in the center. The Tree view shows the sequence as created by FlexSim.

I hope this helps.

Mike Mayer

Goodyear

Hi Phil,

I did some more digging, by walking backwards in the FlexSim versions, trying the same thing as I did in the test model on the most recent version 22.2.0.

I got the same results (multiple naming ControlPoint1) in versions 22.1.3 and 21.2.4.

However, everything worked fine in 21.1.4. I have uploaded a new model created in 21.1.4, doing the same sequence of path and control point creation as the others. It's called "mayer_test_21.1.4.fsm".

In the screenshot (and model) you can see the sequential auto-numbering worked as expected:

So I wonder if something might have changed in the object auto-increment naming algorithm (at least for Control Points, and maybe Paths too), between FlexSim versions 21.1.4 and 21.2.4.

Mike

Hello Phil, thank you for taking a look.

Yes, I was using FlexSim 2022 update 2 (the most recent version). I dumped the model in XML (*.fsx file) as well, and found a "release" tag near the top with 22.2 as the data element.

Just to be sure though, I started from scratch again, in a new model I've just uploaded to FlexSim's file share site, called "mayer_test.fsm".

This new model has three views - the Start Page showing the version (22.2.0), a Tree view page showing the path and control point names, and then the 3D view below the Tree view.

I created a similar model to the one your short video shows (but not exactly in the order you did). Here's the order I created the objects:

I first created four path starting with the left, then top, then right, then bottom paths. I did not connect their corners. This time, they did get names sequentially automatically assigned - Path1, Path2, Path3, Path4. So far so good, and that's better than my previous model which auto-named all four of them Path1. Unclear why that auto-naming part is working OK now (part of the mystery).

Next, I started dropping-in control points. In order, I started with putting two control points on the top Path2, two on the right Path3, two on the bottom Path4. Did nothing yet on the left Path1.

Instead, I put two control points floating on their own inside the area bounded by the four paths. Of course they show only as empty diamonds, with no crosshair because they are not attached to a path. Those two floating orphan control points were automatically named ControlPoint2 and ControlPoint3, which to me is correct (given that the last control point prior to those, was the leftmost ControlPoint1 on the bottom Path4).

Then lastly, I put two final control points on the left Path1. Those two control points were both auto named ControlPoint1. That's part of where the numbering sequence seems to have "broken", i.e., reverted back to ControlPoint1.

The end result is that all 8 of the the control points I dropped onto all four paths (two on each), were auto-named ControlPoint1.

The two orphan floating control points in the middle, were named ControlPoint2 and ControlPoint3.

Note that in the order in which I created them, I created the two final control points on the left Path4, yet they came up auto-named both ControlPoint1 (instead of perhaps ControlPoint4 and ControlPoint5).

I did not rename any of the control points - what you see are what were named automatically by FlexSim when I dropped the control points into the model.

Here's a screenshot of the model; which is what you should see when you bring the model "mayer_test.fsm" into FlexSim. Interestingly, the path names worked out fine this time. However looking at the Tree view, the naming order that FlexSim assigned for the control points as I created them, is six ControlPoint1's, a ControlPoint2, a ControlPoint3, then two more ControlPoint1's.

Another though I had, is that we could set up a specific day/time where I could share my screen with you (Microsoft Teams or Zoom or something), and we can interactively create a model on my system to see how it goes.

I think I may also try un-installing FlexSim 22.2.0 and re-installing it.

Other than this naming quirk, it seems the AGV system works fine (although I've not gone too deep into it).

You bring up a really good point: "Seeing a model with the names messed up doesn't help explain what caused them to not be named properly "

Is there a debug mode, or logging mode in FlexSim, that tracks or provides an audit trail during the model building process? My guess is that inside the C++ there's something that's supposed to be taking the text string "ControlPoint" and doing a concatenation of an incrementing integer-to-string, in a " += 1" fashion to bump-up the object's name (current.name) by one each time a new control point is created. If we could trap that process, perhaps it would reveal where the numeric suffix is not being updated as expected. Or, that it's thinking it's the very first ControlPoint each time (or just sometimes).

I have seen the Call Stack and Event Log features under the Debug menu, however they only work when running a model - not actually tracking the creation of objects on the front end.

Thank you.

Mike

I can't replicate the issue you are describing. Are you sure you are using FlexSim 22.2 as you tagged in your question? It seems to be working fine to me:

Seeing a model with the names messed up doesn't help explain what caused them to not be named properly. Do you have a set of steps that can be performed to replicate the issue?