in my real model I load paramters from an Excel sheet into a tablefile.
This run fine using the plantsim software.
As this model is supposed to be run as standalone, I create a packandgo.
However reading the Excel file sheet is not possible.
The Excel is located in the same folder as the executable on the disk.
Solved! Go to Solution.
if any interface would be open in a pack&go we could stop selling PS, because one could do anything without a license ... sorry, but this is not our business model
Thanks for the update.
Our intention was to have a parametrization using real data from the existing production line.
So I let our management know that the simulation can only run on a PC with the license installed.
Please keep in mind just to have the need for a Runtime-License ... refer to help: Setting-Up and Starting > Plant Simulation License Types > Available Features of the Individual Licenses
Interface Package would not be required in your case.
Thanks for this info, now I have further questions.
Our company has purchased one license (development) installed on the network.
As a developer, IT installed the plant simulation (v13.1) on my workstation. I use this license for my development.
Is is possible to have anyone else to use this license without having the software installed for development ?
Other people want to run the model without making any changes to the graphics layout and code.
Or so we need another license ?
The intention how to use the model I created is:
Development (Me) creates an executable, releases new version during further developement.
Provide an interface via Excel to allow parametrization
Anybody can run the model using the parametrization.
The question is now:
If you want to be able to:
an additional runtime-lic is to be recommended!
The Pack&Go is not intended to be used for "productive" simulations, main purpose of it is to allow:
To this end there is the Runtime license; it does not allow you to modify models (add/remove objects, SimTalk), but other than that it offers virtually all features and includes the interface package.
So, use your development license (e.g. Standard/Professional) to define te model structure and logic, data interfaces etc. Then this model can be opened and parametrized with a Runtime license.
This set-up is very common.