Test OPC UA clients, SCADA and gateways against a server you control
Start one or more OPC UA servers on your own PC, each with its own endpoint, security modes and sign-in rules, and an address space you build from a table or a spreadsheet: folders and variables with data types, units, access and status, and values that move the way you choose. Point your client at it and develop before the real server exists.
Windows. Free for engineers — no account, no licence key.
What it does
Standards-compliant server
Built on the open-source node-opcua stack: GetEndpoints, FindServers, secure channels, sessions, Browse, Read, Write and subscriptions, as a real server answers them.
Security as in the field
Endpoints with None, Sign and SignAndEncrypt (Basic256Sha256, Aes128_Sha256_RsaOaep, Aes256_Sha256_RsaPss), a self-signed certificate made on first start, anonymous sessions allowed or refused, user name and password checked against the users you enter.
An address space from a table
Dotted names become folders and variables (PumpHouse.Pump1.Speed). Boolean to Double, String and DateTime, scalar or array, each with description, unit, writable or read-only access and a status code a read answers with.
Live values and a request log
Fixed, random between limits, incrementing, toggling or pulsed booleans, strings cycling through a list; a value a client writes reads back unchanged. Every service call is logged with client, service, nodes and result.
Moving from testing to production?
When the device is understood and the data needs to go somewhere continuously, Edge Software turns the same tag map into a deployed runtime.