Multi-protocol access and conversion
Modbus, RS485/232, SNMP, MQTT, DI/DO, LoRa, 4G, plus meters and third-party APIs.
Product Complement
Standard Product Complement
Without replacing your core equipment or system, we complement it with proven gateways, modules and interfaces for connectivity, acquisition, alarms and remote access.
Who it is for
- Equipment makers
- Control-cabinet builders
- Low-voltage contractors
- System integrators and solution firms
- OEM partners
No in-house development: add connectivity, acquisition, alarms and remote access in weeks
The problem
What you are dealing with now
Shipped machines go dark, building your own gateway and platform is slow and expensive, and field protocols make it hard to plug into the customer's existing platform.
- Once shipped, status is invisible; faults arrive as phone calls and on-site visits.
- Building a gateway and platform in-house is costly and slow, with protocol work repeated.
- Sites mix brands and protocols, so connecting to the customer's platform is messy.
The difficulty is the data, not the device
Why this is not solved by adding a sensor
Inside the machine you may find a PLC, VFD, proprietary board or private protocol, with point tables in drawings and engineers' heads. For product complement, the customer can take device and edge only and keep their own platform — one protocol stack and data model, not a new integration every time.
Standard capability
What this line includes by default
This is the standard scope. Protocol adaptation, custom development, OEM pages, third-party integrations and advanced reporting are scoped and quoted separately.
Offline buffering and local interlock
Buffer locally during outages and backfill on recovery. Critical interlocks run at the edge, not on the cloud.
Remote access, alarms and configuration
Online status, threshold and trend alarms, remote view and configuration — connectivity as a complement to existing machines.
SaaS / on-premise / OEM / API
Deliver under your brand and deployment model. Data returns through MQTT, REST or tcp-json into your own system.
How we work
The path for this line
Standard selection → sample integration → volume supply. OEM branding and OMD customisation available. For product complement, take device and edge only and keep your own platform.
Architecture
How data travels from the field into the loop
- 01
Field machine / control cabinet / meters
- 02
SG-series or BEC-series industrial gateway
- 03
SDS / IOC expansion modules (as needed)
- 04
Platform account, OEM pages or open API
- 05
Customer's own system, or Tongwei Cloud / app
How to verify
What you can check yourself during the pilot
We do not substitute percentage promises for acceptance. Each item below can be checked by you during the PoC, and used to decide whether to widen scope.
- After sample integration, online status and key parameters are acquired.
- Simulate an outage and confirm local buffering, backfill and edge interlock still work.
- Simulate a fault and confirm the alarm reaches the named endpoint or the customer's platform.
- Check that the agreed OEM pages or API fields are available.
Scope limits for this solution
We do not replace core controllers or field safety systems. Connectivity is assessed from the equipment list, protocol and point table; lead time and custom work are confirmed per project.
FAQ
What customers ask most during evaluation
Our machines use a proprietary protocol — can you still complement them?
Usually yes, but it must be assessed first. Provide the model, comms interface and protocol document or point table. If the protocol is undocumented, key states can often be obtained via DI/DO, analog inputs or serial traffic analysis. Protocol adaptation is scoped and quoted separately.
Will this replace our controller or our platform?
No. Product complement does not replace your core controller or field safety systems. You can take device and edge only and keep your own platform, or use a Tongwei account, OEM branding or APIs to feed your existing system.
Can the platform be delivered under our brand?
Yes. OEM branding covers name, logo, colours and domain; hardware/software customisation (OMD) is also available. Alternatively use the API only and keep Tongwei UI out of sight. OEM pages, dedicated models and integrations are scoped and quoted separately.
What is the path from selection to volume?
The standard path is selection, sample integration, then volume supply. Timing depends on protocol complexity, point-table size and field conditions, and is committed only after assessment. Samples are chargeable in principle, with credit possible against volume orders.