BESS Simulator Dashboard
Choose a tool to manage and monitor the simulator.
Config Editor
Browse and edit emsConfig JSON files (default and model views), including register values with read/write access controls.
Open →Write Command Monitor
Live monitor of incoming Modbus write commands from remote clients (e.g. EMS), with auto-refresh and a clear option.
Open →EMS Modbus
Read the EMS control mode and write Modbus registers on the EMS, with the register value confirmed after every write.
Open →EMS Registers
Search the EMS register map by address, name or unit to find the address and type to write, then send it straight to the editor.
Open →Alarm Triggers
Every alarm each device's map declares for the model ems_control_setting.json names. Triggering writes the register the rule watches, so the simulator serves the condition and the EMS reports it on its next poll.
Open →Alarm Thresholds
Every alarm map the EMS serves, each device's and the EMS's own, loaded live: change a rule's operator, value, severity or wording, then save that one map.
Open →BESS Site
Component counts and register files from the EMS control settings, with the displayed keys taken from the component map.
Open →OCPP Charging
The simulator's charging pile on the OCPP platform: it connects, sends heartbeats and reports itself available. Plug a vehicle in here and the platform starts the charge.
Open →Scan Config Files
JSON files currently in the backend emsConfig folder and subfolders.
Active Model
Select which simulator model's register files the Modbus servers serve. Variant files are named <base>___<model>.json.
Current: ME231
Active Model per Device
Pin a model to each device individually, including units that share a file name such as pcs1 and pcs2. The models offered come from the register file names, so a new variant appears for selection automatically.
The model selected above still applies to every device with no override.
Register Maps from EMS
Load the device register maps from the EMS backend and apply them over emsConfig. Maps the export carries are written over the local copies; local maps it does not carry are left alone, never deleted.
Replaced maps are kept in emsConfig/.register_map_backup.
Restart BESS Simulator
Restart the bess-simulator-backend container. The Modbus servers read their register files at startup, so this is what applies a changed model or a freshly loaded register map. The frontend stays up and reloads this page once the simulator answers again.
Runs through db-backup, the container that holds the Docker socket. Expect roughly a minute while the Modbus servers come back.
Help & Documentation
Every simulator function is documented. These open the guides for this
deployment; set SIMULATOR_DOCS_BASE_URL if they do not resolve.