Veeder-Root TLS-350 to EcoStruxure Integration
Case Study – Veeder-Root TLS-350 to EcoStruxure Integration
Please CONTACT US for questions
Overview
Schneider Electric was attempting to integrate a Veeder-Root TLS-350 into its EcoStruxure BMS using Modbus RTU, but the project had stalled. A third-party gateway failed to communicate with the TLS-350, and a follow-up attempt to configure a FieldServer QuickServer FS-QS-2020-0499 without Chipkin support also failed to produce reliable serial communication.
With the project entering a penalty window, Schneider Electric engaged Chipkin for urgent assistance. Using the FS-8790-33 configuration service, Chipkin developed a working FieldServer configuration and commissioned the integration within 24 hours—resolving multiple technical issues, restoring dependable TLS-350 data flow into EcoStruxure, and preventing further delays for the client.
The combination of a proven FieldServer gateway and Chipkin’s configuration expertise allowed the client to recover a stalled integration and deliver accurate TLS-350 data to EcoStruxure in a very compressed timeframe.
Challenge & Chipkin’s Solution
When Chipkin became involved, the system suffered from incorrect wiring, improper serial settings, and a non-functional configuration file. The TLS-350 uses RS-232 via a DB25-M connector, but the onsite wiring did not follow the required Veeder-Root pinout, preventing communication altogether.
Chipkin reviewed the wiring and confirmed the correct RS-232 assignments (TX → pin 2, RX → pin 3, Ground → pin 7). After guiding the customer through correcting the wiring and enabling RS-232 mode on the FieldServer, Chipkin developed a custom configuration file in under one day. This file correctly mapped TLS-350 tank inventory, temperatures, water levels, alarms, and relays into Modbus registers starting at 30001.
Chipkin also resolved an issue where FLOAT values were being interpreted incorrectly, implementing the proper FLOAT-to-INT16 format and clarifying how the Modbus master should handle paired registers. A network diagram of the integration is shown below.
The following day, Chipkin joined the customer onsite via remote session, uploaded the new configuration, validated communication, and confirmed that the EcoStruxure BMS was reading accurate and stable data from the TLS-350.
Outcome & Real-World Impact
Chipkin successfully recovered a project that had already failed twice and delivered a fully working solution within 48 hours. With Chipkin’s support, Schneider Electric achieved reliable real-time communication with the TLS-350, accurate tank inventory and alarm data, correct Modbus formatting—including proper FLOAT handling—and a fully commissioned system under urgent conditions.
Because TLS-350 systems often support critical operations such as generator fuel supply and environmental monitoring, timely integration is essential. Chipkin’s rapid response and protocol expertise prevented further delays and ensured the client could deliver a stable EcoStruxure integration to their customer.
About Chipkin
Chipkin Automation Systems specializes in protocol gateways, custom integrations, and legacy system modernization. From fuel monitoring and building automation to industrial controls, Chipkin provides FieldServer configuration services, drivers, and engineering support that enable reliable communication between devices and supervisory systems such as EcoStruxure, Siemens Desigo, Metasys, and more.
Whether rescuing a stalled project or designing a new integration, Chipkin helps clients reduce risk, shorten commissioning time, and get the most out of their existing equipment.
FAQ
Can you integrate a Veeder-Root TLS-350 with Schneider EcoStruxure? +
Yes. Chipkin can integrate a Veeder-Root TLS-350 with EcoStruxure by using a FieldServer gateway to convert the TLS-350 serial protocol (RS-232) to Modbus RTU for the BMS. We provide both the configuration file and engineering support to complete the integration.
Do we need to replace our existing gateway if it isn’t working? +
Not always. In this project, the client already had a FieldServer QuickServer onsite. Once they purchased the configuration and support package, Chipkin corrected the wiring and delivered a fully working solution—no new hardware required.
How long does a typical TLS-350 integration project take? +
Under normal conditions, Chipkin recommends a two-week timeline to complete configuration, bench testing, and onsite validation for most gateway integration projects. The duration can vary depending on protocol complexity, device behavior, and the scope of points being mapped.
In many cases, delays occur because clients must first provide accurate wiring diagrams, protocol documentation, device setup reports, and a finalized point list. Timely access to onsite personnel for live testing and troubleshooting is also a key factor in maintaining the schedule.
When all required information is provided up front and the site is ready for real-time testing, Chipkin can expedite the process significantly. As demonstrated in this case study, urgent integrations can be completed in a compressed timeframe when client-side readiness and documentation are available.
What information do you need to start a TLS-350 integration? +
We typically need a TLS-350 setup report, a point list, wiring details, and information about the BMS protocol (e.g., Modbus RTU Master on EcoStruxure). With these, we can design and deliver a custom FieldServer configuration.
Can Chipkin help if we already tried to configure the gateway ourselves? +
Yes. In this case study, the client had already attempted configuration internally and previously tried a third-party gateway. Chipkin stepped in, corrected wiring and configuration issues, and commissioned a working solution.