Software components by professionals, for professionals.
We build PLCcom, a family of industrial communication SDKs for .NET and Java developers: Siemens S7, OPC UA, Modbus and MQTT. They are not loose libraries you adopt and then maintain yourself — they are professionally maintained SDK components with a maintenance plan, documentation and support that comes from the people who wrote them.
This account hosts the open example repositories for those SDKs: runnable workshops, quick-start projects and reference applications, all under the MIT license.
Every SDK ships for both platforms — same feature set, same version numbers, NuGet for .NET and Maven Central for Java.
| SDK | What it talks to | .NET | Java |
|---|---|---|---|
| PLCcom for S7 | Siemens S7-200/300/400/1200/1500, WinAC, Logo!, VIPA — symbolic and direct access | Examples · NuGet | Examples · Maven |
| PLCcom OPC UA SDK | OPC UA client and server, plus PubSub — address nodes by browse path, not just NodeId | Examples · NuGet | Examples · Maven |
| PLCcom for Modbus | Modbus TCP master/slave, Secure Modbus TCP with mutual TLS, CANopen transport | Examples · NuGet | Examples · Maven |
| PLCcom MQTT | MQTT 3.1.1 and 5.0 — a high-level client and a broker you can embed in your own application | Examples · NuGet | Examples · Maven |
All Java artifacts live under the group id com.indi-an.plccom.
Leave the licence fields blank and the library runs with full functionality for 15 minutes per debug session — enough to open a connection, read real values and judge whether the API fits your code. For uninterrupted work, generate a free 14-day trial licence yourself on the download page. No sales call in between.
| Download & trial licence | |
|---|---|
| PLCcom for S7 | https://www.indi-an.com/en/plccom/for-s7/fors7-download/ |
| PLCcom OPC UA SDK | https://www.indi-an.com/en/plccom/opc-ua-sdk/opcua-download/ |
| PLCcom for Modbus | https://www.indi-an.com/en/plccom/modbus/modbus-download/ |
| PLCcom MQTT | https://www.indi-an.com/en/plccom/mqtt/mqtt-download/ |
Every example repository in this account is MIT-licensed and runs against that trial. The SDKs themselves are commercial products under their own EULA.
Choosing a communication component means committing to it for the life of your product. That is what the rest of the package is for:
- Maintenance plan and changelog — you can see what changed and plan your updates around it
- Support directly from the vendor — the people answering wrote the library
- Documentation and API reference for every protocol line
- Workshops and reference applications, not just snippets — this account
- Transparent licensing — terms you can read in full before you buy
- CRA-relevant documentation for products developed to those requirements
- One clearly identified vendor responsible for the component
The PLCcom SDKs are the communication layer inside QuickHMI, our SCADA and data hub platform. The same protocol stacks that run in QuickHMI installations are the ones you link into your own application — they are proven in production before they reach you as a component.
| 🏠 Home | https://www.indi-an.com/en/ |
| 🔌 PLCcom SDKs | https://www.indi-an.com/en/plccom/plccom-overview/ |
| 🖥️ QuickHMI | https://www.indi-an.com/en/quickhmi/quickhmi-overview/ |
| 📦 NuGet | https://www.nuget.org/profiles/indi-systems |
| ☕ Maven Central | https://central.sonatype.com/namespace/com.indi-an.plccom |
| ✉️ Contact | https://www.indi-an.com/en/contact/ |
Indi.An GmbH · Bremen, Germany · industrial automation and software since 2006