Products · On the crane

Maxedge

Main crane logger

Edge data logger installed on every crane. Runs as a VM on a Proxmox host (industrial PC in the crane e-house). All Maxedge services are dockerized.

Status 44 units · 43 reporting

Runs onProxmox VM on fanless IPC, DIN-rail in e-house cabinet

VM address192.168.30.111 · VLAN 30 (OT)

Host192.168.30.110 · Proxmox UI :8006

Current versioncore 3.4.1 · export 2.9.0 · datasharing 1.7.2

CredentialsVault → lh/maxedge/ssh · lh/maxedge/dashboard · lh/maxedge/proxmox

OwnerProduct Engineering · #lh-maxedge

Per-unit data: versions, host specs and subscriptions in Masterdata ↗Fleet: Edge Manager ↗

Hosts & addresses

Proxmox host (IPC)

192.168.30.110

Web UI: https://192.168.30.110:8006
Login: root · password in Vault → lh/maxedge/proxmox

Maxedge VM

192.168.30.111

Dashboard: http://192.168.30.111:8080
SSH user: maxedge · key in Vault → lh/maxedge/ssh

IPC hardware

Fanless industrial PC, DIN-rail in e-house cabinet.
Typical: 8-core x86 · 32 GB RAM · 1 TB NVMe · 4× GbE.
Exact spec per unit in Masterdata ↗.

SOURCE

Crane PLC

Signals over OT network
(VLAN 30)

→

EDGE · VM ON PROXMOX

Maxedge

maxedge-core (logging)export-maxcloudrope-analyzerdatasharing (OPC UA / Modbus)

→

MaxCloud · AWS

export-maxcloud pushes logged data to cloud (TLS, outbound only)

Customer datasharing · OPC UA

OPC UA server exposed to customer network

Customer datasharing · Modbus TCP

Mapped registers for customer SCADA

Container	Purpose	Ports	Healthy when
maxedge-core	Signal logging from the PLC; local time-series store; dashboard backend	8080 (dashboard)	`Up`, dashboard tiles green
export-maxcloud	Pushes logged data to MaxCloud over outbound TLS; buffers locally when offline	outbound 443	MaxCloud last-seen < 5 min
rope-analyzer	Rope wear / remaining-life estimation from hoist data. Licensed per customer	—	License valid, analyses updating
datasharing	OPC UA server + Modbus TCP map for the customer SCADA (second NIC, VLAN 40)	4840 · 502	Ports listening, customer tags updating