[kumajaya]

Hello 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 Kumajaya

[kumajaya]

Hello Mikhail,

Thank you for confirming the naming. I have submitted the forms for all three drivers: DrvSigModbus (free), DrvSigPccc, and DrvSig7.

Best regards,
Ketut Kumajaya

[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

[kumajaya]

Correction:

dotnet publish ./ScadaAdmin/ScadaAdmin/ScadaAdmin/ScadaAdmin.csproj \
    -c Release -r win-x64 --self-contained true \
    -o ./artifacts/ScadaAdmin \
    /p:PublishSingleFile=true \
    /p:IncludeNativeLibrariesForSelfExtract=true \
    /p:StripSymbols=true

[kumajaya]

And ScadaAdmin artifacts built on a Windows GitHub runner: [GitHub Actions Run #18769630218](https://github.com/kumajaya/scada-v6/actions/runs/18770372317).

Both versions are set up as portable apps and do not require a local .NET runtime, making them ideal for running under Wine.

The artifacts were built using a self-contained publish command such as:

dotnet publish ./ScadaAdmin/ScadaAdmin/ScadaAdmin/ScadaAdmin.csproj \
    -c $config -r win-x64 --self-contained true \
    -o ./artifacts/ScadaAdmin \
    /p:PublishSingleFile=true \
    /p:IncludeNativeLibrariesForSelfExtract=true \
    /p:StripSymbols=true

[kumajaya]

For anyone still interested, I have ScadaAdmin artifacts built on a Linux GitHub runner. You can download or inspect them here: [GitHub Actions Run #18769630218](https://github.com/kumajaya/scada-v6/actions/runs/18769630218).

These artifacts include all modifications made in the ci/github-action branch, such as the WindowsDesktop SDK injection script and GitHub Actions workflow for both Linux and Windows builds.

[kumajaya]

Hi @Mikhail, since Mimic’s source code is now available, how do I try it?

[kumajaya]

For SCADA 6 I have to create two different scheme components for SCADA 6 runtime and SCADA 5 scheme editor ?

[kumajaya]

Glad to hear the issue get solved.

[kumajaya]

https://github.com/RapidScada/scada-v6/pull/16/commits/6d6d28c5561bf9b56eac7dec7f658af845ab2581 contain launch.json for debugging ScadaAgent.

[kumajaya]

Let me try later today since I have my own Mqtt server locally and on the cloud.

[kumajaya]

Yeah, I created a dumb script to pack Administrator app based on beta rilis file list but somehow my own build searching for dependency library in the current directory, different than official release from the root of Administrator app.

I even build SCADA 5 on VS Code but still need Visual Studio msbuild tools installed, so still Windows only.

[kumajaya]

Hi @Mikhail, how if we set our scheme completely a graphic, text globally not selectable?

[kumajaya]

How about by using a slim custom bootstrap? A bootstrap with tooltip only inside: https://github.com/RapidScada/scada/pull/116

[kumajaya]

No access to iPhone here but working as expected on Android and desktop browser.

[Author]

Posts