[Release] Communication Drivers Collection for Rapid SCADA v6.0

[kumajaya]

Hello everyone,

*Built by an automation engineer, for automation engineers.*

I would like to share a collection of communication drivers I’ve developed for **Rapid SCADA v6.0**:

🔗 **https://github.com/kumajaya/scada-drivers**

This repository includes 3 drivers:
– **DrvSigModbus** – Modbus RTU/TCP driver with **driver‑level scaling** (inspired by Citect SCADA). **Free**, unlimited tags.
– **DrvSigPccc** – Allen‑Bradley PCCC driver (SLC, MicroLogix, PLC-5) via DF1, EtherNet/IP, or CSPv4. **Trial** (max 10 tags).
– **DrvSig7** – Siemens S7 driver (S7‑300, S7‑400, S7‑1200, S7‑1500) via ISO‑on‑TCP (Sharp7). **Trial** (max 10 tags).

For commercial drivers (DrvSigPccc and DrvSig7), three license tiers are available:
– **Personal** (100 tags)
– **Professional** (500 tags)
– **Enterprise** (Unlimited)

📌 **Pricing for commercial licenses has not yet been finalized** – I will announce it once determined. For now, please contact me directly if you are interested or need a quote.

📥 Binaries are available for download from the **Releases** tab.

The DrvSigPccc driver is built on top of **PCCCComm** – a complete, self‑contained .NET library I’ve developed for communicating with Allen‑Bradley PLCs using the PCCC protocol over DF1 serial, EtherNet/IP, and CSPv4:

🔗 **https://github.com/kumajaya/PCCCComm**

> *”Built for industrial automation engineers who need open, auditable PLC communication without vendor lock‑in.”*

The PCCCComm suite also includes a standalone PLC emulator (**PCCCEmulator**) for safe development and testing, which is highly recommended before connecting to a production PLC.

These drivers are still under active development, so please be cautious and always test on a test bench first. Feedback and bug reports are highly appreciated!

Thank you!

[Mikhail]

Hello,
This is great news!
We will be glad to add those drivers to the Store. Please check the requirements for driver naming. We use suffix related to the author’s name to avoid driver name duplication.

[Mikhail]

Does the Sig part refer to the package name, author, or something similar?

[kumajaya]

Hello Mikhail,

Thank you for the warm welcome and the positive feedback on the drivers! We’re very excited to contribute them to the Rapid SCADA ecosystem.

Regarding your question about the naming:

“Sig” stands for SIG, the institution that has sponsored the development of these drivers. It also serves as our author prefix to ensure uniqueness across the Store, as you suggested in the driver naming requirements.

The full driver names are:
– DrvSigPccc – for Allen‑Bradley PCCC devices (SLC, MicroLogix, PLC‑5) via DF1, EtherNet/IP, and CSPv4. CSPv4 is a legacy protocol, rarely required in modern networks, but we included it specifically to support older PLC-5 and SLC 5/05 systems where EtherNet/IP might not be the preferred or available option.
– DrvSig7 – for Siemens S7 PLCs (S7‑300, S7‑400, S7‑1200, S7‑1500) via TCP/IP.

We’ve used this prefix consistently across the entire codebase—assembly names, namespaces, class names, file names, and even the XML template files. Changing it at this stage would require significant rework across many files and introduce unnecessary risk, so we would greatly appreciate it if these names could be accepted as they are.

We believe the names are already descriptive and are unique in the Store. If there is a strict requirement to rename them, we’re open to discussing it, but we hope the current naming can be accepted.

We’re committed to maintaining and improving both drivers as they are adopted by the community, and we’re open to feedback. We look forward to seeing them in the Store!

Best regards,
Ketut Kumajaya

[Author]

Posts