Module Error Message When opening Existing Model (AGV Module)

Question

question

Maston Lyons asked Dec 23, '16 Phil BoBo edited Dec 28, '16

Module Error Message When opening Existing Model (AGV Module)

I searched the forum but couldn't find an answer. I installed FS2017 and started working on a model using objects form the AGV module. When I opened the model today I received a module error message. I opened up a new model to see if I could recreate the issue and I found that as soon as I use an object from the AGV Module, save and then reopen I get the same error message. Short of trying to uninstall and reinstall FlexSim, is there anything else I can try in order to resolve this?

Software Version:

FlexSim 17.0.0

agv modules flexsim 2017 module dependency error

module-error-info.png (82.9 KiB)

· 4

Maston Lyons commented · Dec 23, 2016 at 07:06 PM

module-error-test-model1622.fsm module-error-test-model1700.fsm1. I asked a colleague of mine to see if they could replicate this error on their machine running FlexSim 2017. They built the same simple model, saved it and then reopened it and received the same error message.

2. I opened up 16.2.2 and built the same simple model, saved and then opened it in FlexSim 2017. I received the warning about the different versions, but did not get the Module Error. I saved it, and opened it again in FlexSim 2017 and did not receive any Module Errors. When I open the model I built in FlexSim 2017 I still receive a module error message.

0 ·

module-error-test-model1700.fsm (17.2 KiB)

module-error-test-model1622.fsm (17.4 KiB)

Maston Lyons commented · Dec 23, 2016 at 08:00 PM

I uninstalled FlexSim 2017 and reinstalled. Built the same model and still get the error message.

0 ·

Marcello Rosadini commented · Dec 28, 2016 at 08:37 AM

To me, this error appears even if I create a simple model. Source+Processor+Sink

If I delete de Dependency Modules 1.0 it seems to get solved, but not sure about the reason it gets created ??

0 ·

Adrian Haws Marcello Rosadini commented · Dec 28, 2016 at 06:51 PM

@marcello.rosadini The development team is aware of this issue, which will be resolved in a coming update.

1 ·

Answer 1 · 2016-12-23T21:19:46Z

Maston Lyons answered Dec 23, '16 Phil BoBo edited Dec 28, '16

I think I found a work around to make it stop giving me an error message. I'm going to post it here so maybe it can save someone else some time if they run into the same problem.

module-error-workaround.png (178.7 KiB)

· 1

Phil BoBo ♦♦ commented · Dec 28, 2016 at 07:02 PM

Thanks for pointing this out. This is a bug introduced in 17.0. We'll get this fixed for 17.0.1.

Your steps here are a good workaround in the meantime.

1 ·

question