Forum Home › Forums › Development and Integration › [Release] Communication Drivers Collection for Rapid SCADA v6.0
Tagged: technology
- This topic has 10 replies, 2 voices, and was last updated 5 days, 9 hours ago by
Mikhail.
-
AuthorPosts
-
July 2, 2026 at 3:27 pm #18109
kumajaya
ParticipantHello 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!
July 3, 2026 at 12:33 pm #18112
MikhailModeratorHello,
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.July 3, 2026 at 12:36 pm #18113
MikhailModeratorDoes the Sig part refer to the package name, author, or something similar?
July 3, 2026 at 4:00 pm #18114kumajaya
ParticipantHello 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 KumajayaJuly 6, 2026 at 12:32 pm #18118
MikhailModeratorHello Ketut,
The current naming is accepted. It’s clear and unique.
Could you fill out the form to add the drivers to the Store (one submit per driver)?July 11, 2026 at 1:57 am #18127kumajaya
ParticipantHello Mikhail,
Thank you for confirming the naming. I have submitted the forms for all three drivers: DrvSigModbus (free), DrvSigPccc, and DrvSig7.
Best regards,
Ketut KumajayaJuly 14, 2026 at 7:42 am #18141
MikhailModeratorJuly 14, 2026 at 2:03 pm #18147kumajaya
ParticipantHello Mikhail,
Thank you once again for the confirmation and for publishing all three drivers to the Store. I truly appreciate your quick support throughout this process.
I would like to add a small clarification regarding the DrvSigPccc driver for Allen‑Bradley PLCs.
The underlying backend communication library for PCCC that I built, PCCCComm, is released as an open‑source project on GitHub. This library natively supports multiple transports, including DF1, EtherNet/IP, and CSPv4.
The PCCCComm package also includes a standalone PLC emulator (PCCCEmulator) that emulates SLC 5/04 (default), PLC‑5/40E (with
--family plc5), and MicroLogix 1400 (with--family ml1400). It provides DF1 serial, EtherNet/IP, and CSPv4 interfaces, and has been validated against RSLinx with OPC access support. This is extremely useful for development and testing without requiring physical hardware.Additionally, I also provide a standalone PCCC Gateway (PcccGateway), which is also open source. This gateway acts as a transparent protocol bridge, allowing any EtherNet/IP client (such as RSLinx, libplctag, or pycomm3) to communicate with legacy PLCs that only speak DF1 or CSPv4. It is specifically designed for users who need to integrate older systems with whatever solutions they already have in place.
The key point I want to emphasize is: The DrvSigPccc driver for Rapid SCADA does not require this gateway at all, because the driver already supports multi‑transport natively (DF1, EtherNet/IP, and CSPv4) right out of the box. Rapid SCADA users can connect directly to their PLCs without any additional middleware.
With these three projects, I have built a complete ecosystem:
1. PCCCComm (open source) — the foundational communication library for all PCCC needs, complete with a built‑in PLC emulator for testing.
2. PcccGateway (open source) — a standalone bridging solution for users who are not using Rapid SCADA.
3. DrvSigPccc (commercial, affordable) — a fully integrated, production‑ready driver specifically optimized for the Rapid SCADA platform.I hope this approach provides maximum flexibility for the community, whether they are using Rapid SCADA or other solutions entirely.
Once again, thank you for your support, Mikhail.
Best regards,
Ketut KumajayaJuly 15, 2026 at 11:29 am #18150
MikhailModeratorThank you for the developments, Ketut!
They looks very useful for those who use the related popular controllers.November 16, 2026 at 3:02 pm #18598kumajaya
ParticipantUpdate: v6.0.3 released + free license giveaway
Hello everyone,
v6.0.3 of the driver collection is now available on GitHub. Highlights:
- DrvSigPccc – a new zero confirmation filter for PLC data that briefly reads 0 during ladder or block-transfer updates, smarter reconnects, and fixes for PLC-5 Timer/Counter/Control sub-elements.
- DrvSig7 – more robust reconnect and error handling.
- DrvSigModbus – fixes for single-register writes with scaling and for 64-bit values with byte order.
Full changelog: CHANGELOG.md
Giveaway
Many plants still run Allen-Bradley and Siemens PLCs, and the communication driver is often what decides whether Rapid SCADA can be used there. To help more of these systems move to Rapid SCADA, I’m giving away free licenses for DrvSigPccc and DrvSig7.
What you get: a Personal license (100 tags, valid for 12 months). There are 2–3 licenses per driver. After the license expires, the driver falls back to trial mode (10 tags) at the next restart. Free renewal is possible but not guaranteed.
What I ask in return: use the driver with your own PLC and share your experience in this thread. That means problems, logs, configuration issues, or simply “it works with X”.
To apply, email me with:
- the driver you want;
- your PLC model and connection (e.g. SLC 5/05 via EtherNet/IP, S7-1200 via ISO-on-TCP);
- a short description of your use case;
- your HWID. It is shown in the communication line log when the driver starts, e.g.
This machine HWID: A1B2C3D4E5F67890.
I’ll favour hardware and setups that haven’t been tested yet.
About the HWID: the license is bound to the operating system installation, not to the hardware:
- On Windows, it comes from
MachineGuid, which is created when Windows is installed. - On Linux, it comes from
/etc/machine-id.
It stays the same when you change hardware. It changes if you reinstall the OS or move to another machine. Cloned virtual machines may share the same ID.
If the log shows “HWID derived from MAC address and machine name and may change”, the OS identifier is not available. Please fix that first, or mention it in your email.
Send the HWID of the machine where ScadaComm will actually run. Each giveaway license is issued once and cannot be reissued for another HWID.
Please note: the drivers can write to PLC memory. Test them on a bench before using them on a live system. The license is provided as is, without warranty.
Thanks, and good luck!
November 17, 2026 at 11:18 am #18599
MikhailModeratorHi,
I’ve checked that the links to GitHub in the Store are valid for the new version. -
AuthorPosts
- You must be logged in to reply to this topic.