TAC-I/Net - Server only
This technical note details the specific use cases for the TAC-I/Net Client and Server drivers. Understanding the relationship between the FieldServer and TAC-I/Net hardware is essential for a successful integration.
In most field applications involving hardware like the 7793 MCI, the FieldServer must be configured as a Server, not a Client.
TAC-I/Net - Server vs. Client Role Definition
The role of the FieldServer is determined by which device initiates communication. For TAC-I/Net systems, the hardware typically takes the lead.
- The Server Driver (Standard): Use this when connecting to TAC-I/Net hardware. Since devices like the 7793 MCI initiate polls and send commands, the FieldServer must act as the Server to receive and respond to these requests.
- The Client Driver (Emulation Only): The TAC-I/Net Client driver is exclusively intended for emulating TAC-I/Net hardware. It should not be used under normal operational circumstances.
Installation Recommendations & Diagrams
To avoid compatibility problems and ensure network stability, follow these two critical hardware recommendations:
- Dedicated I/Net Port: The FieldServer should always have a dedicated port for I/Net traffic.
- Dedicated Controller: Use a dedicated 7793 controller for the interface to prevent interference from other devices on the network.
FAQ – TAC-I/Net Driver Logic
1) Which device is the Client in a standard setup?
In a typical installation, the TAC-I/Net hardware (such as the 7793 MCI) is the Client because it initiates the communication.
2) When would I use the FieldServer as a Client?
Only when you are attempting to emulate the behavior of a TAC-I/Net device (like an MCI) for testing or specialized simulation purposes.
3) How do I prevent network compatibility issues?
By providing the FieldServer with its own dedicated I/Net port and a dedicated 7793 controller, you isolate the communication and reduce the risk of collisions.
Need a Modbus Integration Solution?
Chipkin provides expert-level tools and gateways for Modbus RTU/TCP. If your TAC-I/Net project requires a Modbus bridge, we have the solutions:
