[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.

[kumajaya]

No problem so far on SCADA 6 but on SCADA 5, bootstrap remove background color dan image from media print! My scheme with SVG graphic background looks white 🙁 So, based on https://stackoverflow.com/a/36742058 explanation, I made a custom bootstrap without “Common CSS – Print media styles” from https://getbootstrap.com/docs/3.4/customize/ I believe SCADA 5 will be fine with that custom bootstrap version. What do you think @Mikhail?

Bootstrap tooltips placement smarter than balloon.css and my use case need tooltips support on mobile browser but I don’t want my scheme without a background on print 😀

[Author]

Posts