The Brinkhaus openXEdge is built for one task: it records the processes of a machine in the DataStore and shows them on the device and in the browser. There are no other applications on this device, and none can be installed.
What runs on the device
| Service | Purpose |
|---|---|
| Operator interface | Login, settings (gear), updates, diagnosis and the frame the DataStore is shown in. Reachable at https://<edge-ip>:5443 and http://<edge-ip>:5000. |
| DataStore | The only application and the start page: machines, signals, monitoring and history. You sign in once at the operator interface; the DataStore takes over that login. |
| PostgreSQL | The DataStore’s database. Reachable only inside the device. |
| Maintenance Sidecar | Sets up the DataStore on first start, runs maintenance actions and operates the device firewall. |
| UpdateService | Installs firmware updates and returns to the previous state on its own if one fails — see How updates work. |
Only the operator interface (5000, 5443) and the maintenance access (22) can be reached from the network; details on the Security and support page.
How the DataStore is set up at the factory
On first start the device creates in the DataStore:
- the site Hannover,
- in it the machine Testmaschine with an OPC UA source Steuerung, whose signal Drehmoment (torque) is monitored and whose R100 serves as the trigger,
- a canvas for the test machine with a monitoring tile and a history tile.
At the factory the source is connected to the DataStore’s built-in simulation, so monitoring and history show data without a controller attached. How to connect a real controller, choose signals and adapt the canvas is described in the DataStore documentation.
Operating the DataStore
The DataStore has a handbook of its own. It is on the DataStore customer portal and covers sources and signals, monitoring, history and user roles, among other things. We send you the access data for the portal — write to support@brinkhaus-gmbh.de.