The IOTA to CygNet SCADA Platform (CygNet) Driver provides connectivity between IOTA Vue and CygNet SCADA Platform. The driver is state-less, i.e. it doesn't maintain source connections and data caches.
The driver supports the following object types:
| IOTA Type | Supported? | Source Type |
|---|---|---|
| Tag | 🟢 | Point Tag |
| Asset | 🟢 | Facility |
| Timeframe | ⚫ |
Diagram
Technical Specification
| Description | Value |
|---|---|
| Development Language | C# |
| Processor Architecture | 64-bit |
| Supported Operating Systems | Windows 2012+ |
| Minimum Requirements CPU/Memory | 4 cores / 8 Gb |
| Deployment Size | 6.72 Mb |
| Data modes | Read |
| Request/Response pattern | Asynchronous |
| Source Communication | CygNet.NET API |
| Back-end Communication | NATs message bus |
| Message bus driver type | cygnet |
| Near Real-Time Data Updates | Yes |
| Multiple CygNet Connections | Yes |
Dependencies
| Name | Version |
|---|---|
| Microsoft Windows | 2012 and above |
| Microsoft .Net Framework | 4.7.2 |
| CygNet 64-bit API | 9.5 |
How to install and register CygNet API
Security
Source Security
By default, the CygNet Driver service uses configured service's user identity for secure connections to CygNet SCADA Platform.
Note, CygNet Driver requires read access for service's user identity to the following CygNet services:
| Service Description | Abbreviation |
|---|---|
| Point Configuration Service | PNT |
| Table Reference Service | TRS |
| Value History Service | VHS |
| Facility Service | FAC |
IOTA API (back-end) Security
The CygNet Driver uses NATs message bus to communicate with the IOTA Vue Cluster. The two-way data traffic is encrypted using Transport Layer Security (TLS) on port 443. In addition, the message bus communication security model uses a public-key signature system based on Ed25519 called NKeys. With NKeys, the server can verify identities without ever storing or seeing private keys. The authentication system works by requiring a connecting client to provide its public key and digitally sign a challenge with its private key. The server generates a random challenge with every connection request, making it immune to playback attacks. The generated signature is validated against the provided public key, thus proving the client's identity. If the public key is known to the server, authentication succeeds.