The Robot Cell Simulator consists of a basic license and additional modules. Every module is a feature on the HASP key; the number in the first column is the number of this feature (it is also shown in the messages of the program, e.g. License 248 - API / CLI not found). The additional modules work only together with the basic license, some of them also need another module (column Requires).
Modules and what they unlock
| Feature | Name | Requires | Unlocks (functions, menus, API commands) | Without the license |
| 140 | Basic | – |
|
the plugin opens, but no study can be loaded (message License ... not found) |
| 141 | Simulation | 140 |
|
no station run; a single program moves with axis interpolation and its path is drawn with straight lines; no automatic tool change (message in the console); the tab Times stays empty |
| 142 | SPS | 140, 141 |
|
the program can be edited, but the robots start together at Warte auf Folgenstart without the SPS program; the SmartPad buttons show a message |
| 143 | Work Zones | 140 |
|
work zones of the first 2 checked robots (message); the collision check of the run knows only their zones |
| 144 | Robustness test | 140, 141, 143 |
|
the tab opens and plans can be loaded, changed and saved; the test does not start |
| 145 | Collision 3D | 140, 141 |
|
the options can be set; at the start of the run the console says that the license is missing and the run goes on with the collision check from the work zones only |
| 248 | API / CLI | – |
|
the API answers only the reading commands; the AI Agent window answers only /help, /reload, /mode and reading direct commands; the voice control VeRa does not start |
| 247 | AI agent knowledge | – |
|
the AI Agent window works without the knowledge of DrAmaT; the pack is red in the knowledge list of the settings, the reason is in its tooltip (details) |
Test and vendor keys with the feature 250 Experimental unlock all modules of the table
(140 to 145), the knowledge packs (247) and the API / CLI (248), also when their own features are not on the key.
Commands of the API without a license
Without the license API / CLI the command API answers only these reading commands:
ping, status, run_data, wait_times, recent_files,
settings_get, ui_windows, ui_list, ui_get, ui_actions,
ui_shot, scene_shot, robust_test with status or risks,
race_study status, and view, zones_view, report_open without
parameters (reading the state). Any other command gets the answer License 248 - API / CLI not found - only reading
commands are available.
The voice control VeRa needs the license API / CLI (248): without it VeRa does not start and the status bar of DReS shows VeRa: not started - license 248 ... not found.
Where to see the status
- Help → Licenses... of the simulator: every module with its status (lock open / closed), its functions and what works without it.
- A closed lock on a tab of the panel marks a module without license: Simulation, Motion, Times and Auto-Docking (Simulation), SPS, Work Zones, Robustness test. The tooltip of the tab names the module and its status.
- A function without license shows License '...' not found - '...' is not available (window or console), an API command answers with an error.
- Help → License info in DReS: all licenses of the key with type, validity and remaining days, also the knowledge packs of the AI agents.
- Help → Reconnect license in DReS checks the key again at once (e.g. after the key was plugged in).
The licenses are checked on the HASP key – contact dramat.eu for licenses or a trial.