Table of Contents |
---|
...
Parameter | Description | |
---|---|---|
Name / IP | The IP address of the target | |
Description | The description of the target is written by the user when adding a new target in HYPERSIM Target Manager. | |
Active | HyCore and HyServer are running, the target can be used. It detects the user and the mode. The following information can be seen in the tooltip:
| |
HyCore is running but HyServer is not reachable. | ||
HyCore is not running. The target is unreachable. | ||
Running Version | Architecture | The target Operating System. |
Build | The current HYPERSIM version used by the target. | |
Protocol | see https://opal-rt.atlassian.net/wiki/spaces/DOCHSPDOCHS/pages/20190803150241935/Target+Manager#Protocol-versions-and-backward-compatibility | |
License (days) | It indicates how many days remain in the target license before it expires. |
...
HYPERSIM version | Protocol | Samba | RMI | gRPC | SystemD | Main change |
---|---|---|---|---|---|---|
2021.2 | 1.0.0 | Initial introduction | ||||
2021.3 | 1.0.0 | |||||
2022.1 | 2.0.6 | HyServer: Start simulation with decimation parameters. Samba is not used anymore for file transfers to target | ||||
2022.2 | 3.0.0 | Replaced all usage of the target from RMI to gRPC, except target manager | ||||
2023.1 | 4.0.0 | RMI removal | ||||
2023.2 | 5.0.0 | Internal changes during simulation setup on target | ||||
2023.3 | 5.1.0 | An additional method for switching target versions on certain target configurations | ||||
2024.1 | 6.0.0 | HyCore and HyServer services are now launched by systemd on OPAL-RTLinux | ||||
2024.3 | 6.0.1 | HyCore is now able to return the target Serial number to the target manager. | ||||
2025.1 | 6.1.1 |
|
|
|
| When setting up a driver during simulation startup on target, use the “Enable simulation Logging” option to determine the log level of each command |
This table explains that a 2022.2 or older HYPERSIM PC version will not be able to communicate with targets where HyCore 2023.1 or higher is running, as RMI technology has been removed, for stability and security reasons. The 2022.1 and 2022.2 versions support both protocols, meaning they can be used to transition from these versions.
...