Panels and gateway from our own production
Touch panels in two classes, plus the GWPro for product business without a display. The same edge client runs on all of them, and you reach all of them remotely without opening a port.
- Pro class TP10 Pro and TP8 Pro
- Smart home class TP4, TP8 and TP10, flush or surface mounted
- GWPro gateway for product business without a display
- Remote access overlay mesh, granted per device, time limited and logged
- Android panel The touch panels are operation and edge client in one. Local HMI with no restriction, including when the line is down.
- Linux gateway For product business without a display. Reads the controller, buffers locally and talks to the cloud.
- Embedded Where there is no room for a device of its own: the same client, built into the assembly.
The devices
-
Pro class
TP10 Pro, TP8 Pro
Touch panel and edge device in one
-
Smart home class
TP10, TP8, TP4
For a flush mounting box or surface mounted
-
GWPro
Gateway for product business, without a display
Pro class: TP10 Pro and TP8 Pro
A touch panel that is also the edge client. The operator works the plant on it, and the same device reads the controller and talks to the cloud. No second device in the cabinet is needed.
Smart home class: TP4, TP8 and TP10
The same job in the form factor made for the wall: for a flush mounting box or surface mounted. The same edge client runs on these too.
GWPro
Where no visualisation is needed on site, for instance in product business with one controller per plant, the GWPro does the same job without a display.
Certified device access
Only approved hardware connects, against documented criteria. That is not an end in itself: a device that supplies your plant data and accepts commands does not belong on an open list.
Which devices are approved is your decision, inside your tenant.
Remote access without an open port
When something is stuck in the field, reaching the device beats sending someone out. The devices bring an overlay mesh for that: the device builds the connection outwards by itself, encrypted and straight to the far end. No inbound port has to be opened in the operator’s network, no port forwarding has to be set up, and there is no VPN concentrator for somebody to run and keep current.
That is the difference that counts day to day: the classic answer to remote service is an entry into the operator’s whole network. A mesh connects two endpoints, and the operator can see which two.
Granted, time limited, logged. Access is granted per device and not for the fleet, it expires by itself, and every session is logged. That log is audited. For an operator this answers the question that always comes up with remote service: who was on which device, and when.
VPN remains possible. Where an operator’s IT requires a VPN, it is supported. The mesh is the way that needs no concentrator, not the only way.
Where to get it
The hardware comes from our own production. sinnotrade carries it.
This is what it looks like
Only approved hardware
The catalogue of devices allowed to connect, with draft, review and release per product.
Better shown than read
We will show you this area on a real plant, set up around the equipment you build.