The core role of TC-100 is to break down the problem of field devices and upper-level systems that “can connect physically but speak different languages” into protocol parsing, data acquisition, address mapping, data-format conversion, and platform upload. The official detail page lists Modbus RTU, Modbus TCP, BACnet/IP, BACnet/MSTP, and OPC UA; an official product article further identifies BACnet → Modbus and OPC UA → Modbus as two typical directions in the current version. 1. Building automation: Establish configurable data exchange between BACnet/IP or BACnet/MSTP systems/devices and Modbus field devices. 2. Industrial platform integration: Bridge OPC UA and Modbus device data according to the project architecture for SCADA, equipment platforms, or upper-level systems. 3. Metering and energy: Connect meters, sensors, PLCs, or controllers so that multi-brand devices can be integrated into a unified energy-management, O&M, or cloud platform. 4. Data mapping: Source address, target address, data type, byte order, scaling factor, read/write permissions, abnormal values, and refresh cycle must be confirmed point by point. Identical protocol names do not mean devices can communicate directly without configuration.

The official product page lists 1 WAN + 1 LAN, DC 12–36 V, RS485/RS232/CAN-type interface, 2×DI + 2×DO, USB 3.0, Micro SD, reset, and status indication. It is suitable for equipment rooms, control cabinets, or distributed sites to connect local devices to upper-level networks/cellular networks. 1. Ethernet: 1 WAN + 1 LAN helps separate the uplink platform network from the local maintenance/device network. Actual network isolation, addressing, and firewall policies should be designed for the project. 2. Serial/bus interface: The specifications show RS485, RS232, and CAN as a “select one” configuration. When ordering, the required interface must be specified in the model, wiring diagram, and BOM rather than assuming all are included simultaneously. 3. Digital I/O: 2×DI + 2×DO can be used for status acquisition, alarms/linkage, and other simple field interactions. Specific logic and electrical characteristics are subject to the datasheet. 4. Cellular/wireless: The product introduction mentions 2G/3G/4G/5G remote transmission as well as Wi-Fi indicators/antenna information. Whether the delivered unit includes cellular, Wi-Fi, the corresponding bands, and antennas should be confirmed item by item with sales. 5. Environment: Representative specifications list -40°C to +75°C, 10%–95% RH, and protection against reverse polarity, overvoltage/overcurrent, lightning, and surge.

The advantages of TC-100 should be expressed around “reducing system-integration complexity” rather than generalized as every gateway capability. Its functional focus is protocol interoperability, field connectivity, and project-configurable implementation. 1. Mainstream industrial/building protocol coverage: Provides protocol access and conversion directions centered on Modbus, BACnet, and OPC UA. 2. Configurable data mapping: Supports protocol parsing, address mapping, data-format conversion, data acquisition, and platform upload, helping unify data from multiple device brands. 3. Multiple physical-interface options: Optional RS485, RS232, or CAN can connect to different field buses and device interfaces. 4. Network segmentation capability: 1 WAN + 1 LAN makes it easier to deploy the local device network separately from the uplink network, improving maintenance and network-planning flexibility. 5. Foundation for remote connectivity: The detail page describes cellular networking and remote-platform access, providing a data channel for distributed industrial and utility projects; the specific network mode must be confirmed in the order. 6. Customization and secondary-development support: The page mentions label/Logo customization and secondary development, suitable for OEM, system integration, and project-specific protocol combinations. Development boundaries, deliverables, and acceptance criteria should be written into the contract.

When existing equipment does not need to be replaced but inconsistent protocols prevent unified monitoring or management, TC-100 can be used as a communication-layer retrofit component. The following six scenarios accurately reflect its positioning. 1. Building BMS integration: Bridge data between HVAC, lighting, pump-room, elevator, and other systems and Modbus devices. 2. Energy management: Integrate data from electricity meters, water meters, heat meters, gateways, and other devices into an EMS or energy-consumption platform. 3. Industrial automation: Connect PLCs, variable-frequency drives, sensors, and instruments to SCADA or upper-level industrial platforms. 4. Legacy system retrofit: Reduce the cost of replacing entire systems when integrating new and old systems, equipment from different vendors, or inconsistent protocol versions. 5. Smart water and municipal utilities: Connect distributed meters, pump stations, or sensing devices to a unified platform through serial or network interfaces. 6. Multi-site remote O&M: Combine WAN/LAN with optional cellular networking to upload remote equipment status, alarms, and data to the operations center.

Protocol conversion must distinguish “source protocol — target protocol — data direction — device role — read/write permissions.” The typical versions listed in the current official product article are BACnet → Modbus and OPC UA → Modbus. The product detail page uses wording such as “etc.” for other combinations and states that project-specific development is available. Therefore, it should not simply be promoted as “arbitrary bidirectional conversion among all protocols.” 1. Step 1: Confirm the source and target protocols, such as BACnet/IP, BACnet/MSTP, Modbus RTU, Modbus TCP, or OPC UA. 2. Step 2: Confirm the conversion direction and roles, such as client/server, master/slave, read/write, one-way reporting, or bidirectional control. 3. Step 3: Provide the point list, addresses, object types, data types, byte order, scaling factors, alarms, and refresh cycles to complete the mapping table. 4. Step 4: Verify exception handling, connection recovery, network security, permissions, logs, upgrades, and platform-side acceptance. 5. Step 5: If MQTT, proprietary protocols, or other combinations are required, confirm with the Tespro sales/technical team during the pre-sales stage whether the corresponding version or customization service can be provided.

The TC-100 detail page provides a free inquiry option, datasheet download, and direct contact entry points, but does not publish a complete retail price or uniform warranty policy. Actual protocol-converter quotations are typically affected by interface version, cellular module, protocol combination, point-list size, secondary development, quantity, lead time, and service requirements. Therefore, written technical confirmation and commercial quotation must prevail. 1. Warranty: It is recommended to specify the standard warranty, optional extended warranty, software/firmware support, protocol-customization maintenance, and on-site service item by item in the contract. A 2–5-year extended warranty should be treated as an optional quotation item rather than a default policy. 2. Sample purchase: Start with one unit or a small sample batch for integration testing, verify protocol direction, point-list mapping, concurrency, network security, and exception recovery, and then proceed to volume purchasing. 3. Quotation contact: sales@tespro.com is used for sales quotations and info@tespro.com for general inquiries. The official website lists +852 4609 4648 and +1-213 610 4797 as telephone/WhatsApp contact numbers. 4. Shop and social media: Small quantities can be viewed in the Tespro Online Shop. Facebook, LinkedIn, YouTube, TikTok, X, and Instagram can be used to browse public information, cases, and product explanations. 5. Inquiry materials: It is recommended to attach the network topology, protocol description, point list, interface type, target platform, country/frequency bands, estimated quantity, sample plan, certification requirements, and lead-time requirements.