FAQs

Q: Why isn't my simulation starting?

Please try loading one of the provided grids (Basic, Medium, Advanced). If it works with the provided grids then you will need to get a different .aslog file of the grid you want to load. If the provided sample grids also do not work then please check that your antivirus is not deleting some of the necessary files for the SDK. Have your company's IT whitelist the SDK software.

Q: Why are robots not moving or delivering bins?

If your simulation is Running and the bots won't deliver bins try using one of the provided grids (Basic, Medium, Advanced). If it works with the provided grids then you will need to get a different .aslog file of the grid you want to load. If it still does not work then ensure you are using the correct software (Planner/Router) for the modules on your grid. For example: Fusion Port only works with Router software. You can also just test with Planner software if you do not have any of those newer modules.

Q: I clicked the "Export" aslog button and nothing happened?

By default the aslog export saves to the Desktop, check there for your exported aslog file.

Q: Can I run multiple systems?

It is not possible to run multiple simulations from the WMS SDK on the same machine. If one wants to simulate a multi-grid system, the best thing to do is to set up simulations on two separate machines/VMs.

Q: I keep getting "license check failed" does WMS SDK need an active internet connection?

Yes the WMS SDK requires an active internet conenction in order to periodically verify the licence status. The address https://aslic.autostoresystem.com on standard HTTP port 443 must be whitelisted. If you MUST operate WMS SDK without an active internet connection it is possible but please email [email protected] for further assistance.

Q: What are the specs needed to run the WMS SDK Application?

The minimum required system specs are (AutoStore Controller PC has these specs):
CPU Intel i7-6700
Cores: 4
Threads: 8
CPU Cache: 8 MB
RAM 16 GB DDR4 2400 MHz
Windows 10 version 1803 (or greater).
For Windows Server, 2019 or later.