Manual Overview
Veeder‑Root TLS‑350 manual offers concise guidance on setup‚ operation‚ and maintenance. It covers console compatibility‚ key features‚ installation steps‚ and operational modes such as inventory‚ diagnostics‚ and reporting. The guide is designed for certified contractorsand users alike.!Thanks
Purpose and Scope
The Veeder‑Root TLS‑350 manual is intended to provide operators‚ technicians‚ and service personnel with a comprehensive reference for the configuration‚ operation‚ and maintenance of the TLS‑350 automatic tank gauge system. The manual defines the scope of the document‚ clarifying that it applies exclusively to the TLS‑350 model and its associated fixed‑feature consoles‚ including the TLS‑300‚ ProPlus‚ and Gilbarco EMC Basic consoles. It outlines the purpose of the manual as a definitive source for installation procedures‚ operational mode descriptions‚ diagnostic instructions‚ and troubleshooting guidance. The manual also specifies the intended audience‚ which includes certified contractors responsible for system installation‚ plant operators who manage day‑to‑day tank monitoring‚ and maintenance technicians who perform routine checks and repairs. The scope covers all functional aspects of the TLS‑350‚ from initial site preparation and hardware setup to the use of advanced inventory and reporting features. It emphasizes that the procedures assume a fully configured system by a certified contractor and that users should refer to the manual only for functions applicable to their specific console configuration. The manual’s purpose is to ensure safe‚ efficient‚ and accurate tank measurement‚ thereby supporting compliance with industry regulations and operational reliability. By following the guidance in this manual‚ users can achieve optimal performance‚ minimize downtime‚ and maintain data integrity across all operational scenarios.
The manual also stresses the need for accurate calibration‚ routine leak testing‚ and proper documentation to support compliance and audit trails‚ ensuring data integrity and regulatory adherence for operational scenarios. !
Console Compatibility
The TLS‑350 manual specifies that the system is compatible with a range of fixed‑feature consoles‚ including the Veeder‑Root TLS‑300‚ ProPlus‚ and Gilbarco EMC Basic models. Each console type supports a subset of the TLS‑350’s full feature set‚ and the manual details which operational modes are available on each platform. For fixed‑feature consoles‚ the manual lists the supported functions such as In‑Tank Inventory‚ Tanker Load Report‚ Diagnostic Mode‚ and Maintenance Report (TLS‑350 only). It also explains that the console’s firmware version must be current to access all features‚ and it provides guidance on firmware updates and compatibility checks. Additionally‚ the manual includes a compatibility matrix that maps console models to available features‚ ensuring operators can quickly determine which functions are accessible on their specific hardware; This section also highlights the importance of consulting the installation guide for proper wiring‚ sensor connections‚ and power requirements to maintain compatibility and system reliability. By following the compatibility guidelines‚ users can avoid configuration errors‚ ensure accurate data capture‚ and maintain regulatory compliance across all operational scenarios.
Compatibility checks verify sensor calibration‚ power supply integrity‚ and firmware alignment. The manual offers a checklist for each console type‚ ensuring wiring data sync with the database. Users log deviations schedule daily corrective actions now!
Key Features
The Veeder‑Root TLS‑350 manual presents a concise yet comprehensive overview of the system’s capabilities‚ focusing on precise fuel measurement‚ regulatory compliance‚ and user‑friendly operation. Key functions include:
- In‑Tank Inventory – Real‑time volume and temperature monitoring with automated data logging.
- Tanker Load Report – Detailed load calculations‚ tare weight‚ and net volume for each shipment.
- Diagnostic Mode – Self‑check routines for sensors‚ pumps‚ and communication modules.
- Leak Detection Test – Automated pressure and flow checks to identify leaks.
- Sensor Status Reports – Continuous monitoring of vapor‚ liquid‚ and ground‑water sensors with threshold alerts.
- Printer Management – Paper change notifications and print queue handling.
- Reconciliation Mode – Cross‑verification of tank data against external records.
- Smart Sensor Status – Advanced diagnostics for wireless and wired sensor arrays.
Each feature is supported by intuitive menu navigation‚ configurable thresholds‚ and user‑friendly displays. The manual also provides step‑by‑step instructions for enabling‚ configuring‚ and troubleshooting each function‚ ensuring operators maintain optimal system performance and meet industry standards. Operators refer to the troubleshooting section for error codes!!!!.
Installation and Site Preparation
The manual outlines essential steps for installing the TLS‑350‚ including site selection‚ requirements‚ and sensor placement. It covers grounding‚ cable routing‚ and safety checks to meet local codes. Contractors should verify power‚ connectivity‚ and conditions before commissioning. All steps verified.
Fixed-Feature Console Setup
Begin with power and grounding. The TLS‑350 requires a 120‑V‚ 60‑Hz source‚ a 15‑A breaker‚ and a 10‑AWG cable. Connect the main power lead to the console’s input terminal‚ observe polarity‚ and ground the chassis to the facility’s grounding bus using the supplied strap.
Install the sensor array. Mount the liquid level sensor at the tank’s top‚ aligning the probe with the diameter. Secure it with the clamp and route the cable along the wall‚ avoiding sharp bends. For vapor detection‚ place the probe at the vent and connect its cable to the console’s vapor input.
Configure console settings via the screen menu. Choose “System Setup‚” then “Console Type” → “Fixed‑Feature TLS‑350.” Enter tank dimensions‚ fill type‚ and calibration data. Use the calibration kit to verify sensor accuracy within ±0.5 %. Save the configuration and run a check to confirm all modules are active.
Attach the printer by connecting the serial port to the console’s printer interface. Load the correct paper size‚ print a status page‚ and verify printer responsiveness. If wireless printing is supported‚ configure network settings under “Network Setup” and confirm connectivity. Finally‚ run a diagnostic: navigate to “Diagnostic Mode‚” select “Run All Tests‚” and review results. Address any failures by checking cable continuity‚ sensor alignment‚ or power integrity. Once diagnostics pass‚ the console is ready for operation and integration into the facility’s system. Training and documentation should be completed before use. Personnel review safety procedures and certification. Ensure compliance with local regulations. Now. Proceed OK
Modular Console Configuration
Configuring a modular TLS‑350 console begins with selecting the appropriate module set for the application. The console supports optional modules such as the 2‑wire or 3‑wire level sensor‚ vapor sensor‚ and the optional printer or network interface. Each module is mounted on the rear panel and connected via the dedicated 4‑wire or 2‑wire cable harness. Ensure the harness is seated fully; a loose connection will trigger a fault code during the self‑check.
Power the console using the 120‑V‚ 60‑Hz supply. Verify the main breaker is rated for 15 A and that the grounding strap is attached to the facility’s grounding bus. The console’s power indicator should flash green during boot. If the indicator remains amber‚ check the power cable for damage and confirm the correct polarity.
Once powered‚ navigate to the “Module Setup” menu. The console will list all detected modules. For each module‚ press the “Configure” button and input the sensor type‚ calibration constants‚ and tank parameters. For a 3‑wire level sensor‚ enter the sensor’s resistance range and the tank’s maximum fill height. For vapor detection‚ input the vent diameter and the expected vapor pressure range. After entering the data‚ press “Save” and the console will perform a quick self‑check. Any errors will be displayed with a fault code and a suggested action.
Next‚ configure the communication interface. If the console is to be networked‚ select “Network Setup” and enter the IP address‚ subnet mask‚ and gateway. Enable the TCP/IP stack and test connectivity by pinging a known host. For serial or RS‑232 communication‚ set the baud rate‚ data bits‚ parity‚ and stop bits to match the connected device. Verify the link by sending a test command and observing the response.
After all modules and interfaces are configured‚ run the “Full Self‑Check” from the main menu. The console will cycle through each module‚ perform calibration checks‚ and confirm communication integrity. A successful check will display “All modules operational.” If any module fails‚ review the wiring diagram‚ re‑seat the harness‚ and re‑run the check. Once the self‑check passes‚ the console is ready for integration into the tank monitoring system. Document the configuration settings in the installation log and provide the operator with a quick‑reference guide for routine checks. Training should cover module identification‚ fault code interpretation‚ and basic troubleshooting steps. End of configuration. OK
Site Preparation Guidelines
Before installing a Veeder‑Root TLS‑350 console‚ verify that the site meets the manufacturer’s environmental and safety specifications. Mount the console on a clean‚ dry‚ level surface with at least 12 in. clearance around the rear panel. Ambient temperature should not exceed 104 °F (40 °C) and relative humidity stay below 80 %. The console requires a dedicated 120‑V‚ 60‑Hz circuit with a minimum 15 A breaker and a separate grounding conductor bonded to the facility’s grounding bus. Confirm the power cable is UL‑listed and the plug matches the local receptacle. Cable routing should keep power‚ communication‚ and sensor cables separate‚ using trays or conduit‚ and all cables must be rated for the ambient temperature. Use cable glands and strain reliefs to prevent vibration damage‚ and ensure conduit is fire‑rated per local codes. Grounding straps connect the console’s chassis to the facility’s grounding bus; a ground‑fault indicator should detect faults. Verify the grounding resistance does not exceed 5 Ω to maintain system integrity. Ensure the console’s enclosure is rated IP54 to protect against splashes. Use a dedicated UPS to protect against power surges. Perform a short‑circuit test on the grounding conductor. Label all cables for easy identification during maintenance. Keep a spare cable in the rack for quick replacement. The installation area should be accessible only to authorized personnel; lock‑out/tag‑out procedures must be in place during maintenance. Document all site‑preparation steps—mounting location‚ power circuit details‚ grounding points‚ and cable routing—in the installation log to aid future troubleshooting and compliance audits. Thanks!
Operational Mode Functions
Operational mode functions include In‑Tank Inventory‚ Tanker Load Report‚ Diagnostic Mode‚ and Maintenance Report (TLS‑350 only). Each mode offers step‑by‑step guidance‚ printable reports‚ and status diagnostics tailored to the console’s installed features. Follow the manual foraccurateoperation
In-Tank Inventory
The In‑Tank Inventory function provides real‑time measurement of liquid levels‚ temperature‚ and volume within a storage tank. By accessing the console’s touchscreen or keypad‚ operators can initiate a scan that reads sensor data‚ calculates the current inventory‚ and displays the result in gallons‚ barrels‚ or cubic meters. The function supports multiple tank configurations‚ including single‑line‚ dual‑line‚ and multi‑line setups‚ and automatically adjusts for sensor calibration offsets; When the scan is complete‚ the console generates a printable report that includes the tank identifier‚ date and time‚ measured volume‚ temperature‚ and any deviation from the setpoint. Users can also export the data to a CSV file for integration with enterprise asset management systems. The inventory process is designed to be quick‚ typically taking less than 30 seconds for most tanks‚ and can be scheduled to run at regular intervals or triggered manually. Safety features such as leak detection alerts and temperature thresholds are integrated‚ ensuring that the inventory data reflects accurate‚ safe conditions. The console logs each inventory event‚ allowing audit trails and trend analysis over time. For maintenance crews‚ the In‑Tank Inventory mode is essential for verifying tank integrity‚ planning refills‚ and ensuring compliance with regulatory reporting requirements. The manual provides step‑by‑step instructions for initiating the scan‚ interpreting the results‚ and troubleshooting common issues such as sensor drift or communication errors. By following these guidelines‚ operators can maintain accurate inventory records and support efficient fuel management operations. See manual
Tanker Load Report
The Tanker Load Report function captures and logs the volume of liquid transferred during a tanker delivery. Operators initiate the report by selecting the delivery session on the console‚ which then queries the inlet and outlet flow meters‚ sensor data‚ and temperature readings. The console calculates the net load by subtracting the inlet volume from the outlet volume‚ adjusting for temperature corrections and sensor calibration offsets. The resulting figure is displayed in the console’s main screen and can be printed or exported. The report includes critical details such as the tanker ID‚ driver name‚ delivery time‚ start and end volumes‚ temperature‚ and any deviations from the expected load. It also flags any anomalies like sensor errors‚ flow meter drift‚ or temperature spikes that could affect accuracy. Users can schedule the report to run automatically after each delivery or manually trigger it at any time. The console stores a history of all reports‚ allowing operators to review trends‚ verify compliance with regulatory requirements‚ and audit fuel inventory. The manual provides step‑by‑step instructions for generating the report‚ interpreting the data‚ and troubleshooting common issues such as communication failures or incorrect sensor calibration. By following these guidelines‚ operators can maintain accurate delivery records‚ support reconciliation processes‚ and ensure that inventory balances remain consistent across the system. Additionally‚ the console offers a graphical view of the load curve‚ enabling operators to spot any irregularities in the transfer profile. The system can generate alerts if the load deviates beyond a user‑defined threshold‚ prompting immediate investigation. The report can be customized to include additional fields such as fuel grade‚ pressure readings‚ and tanker fuel capacity‚ providing a comprehensive snapshot of each delivery. For audit purposes‚ the console timestamps every entry and records the operator’s credentials‚ ensuring traceability. The manual also covers how to archive reports to external storage‚ set up email notifications‚ and integrate the data with third‑party fuel management software via the console’s API. By leveraging these features‚ facilities can streamline their tanker operations‚ reduce manual paperwork‚ and enhance overall operational efficiency. Data is archived for compliance now.
Diagnostic Mode
Diagnostic Mode is a tool for verifying sensor health‚ communication links‚ and logic. Press the Diag button to access a menu of numbered tests such as Flow Meter Self‑Check‚ Temperature Sensor Calibration‚ Vapor Sensor Status‚ and Communication Link Test. Each test runs automated checks that read values‚ compare them to calibration tables‚ and report pass/fail. The console logs start time‚ duration‚ and outcome in a diagnostic log file that can be printed or exported via USB. If a test fails‚ the console highlights the component and suggests corrective actions‚ like recalibrating the sensor or tightening wiring. A live data stream shows voltage‚ current‚ and temperature for all modules‚ helping spot transient anomalies. Advanced users can reset diagnostic settings to factory defaults after firmware upgrades. The manual advises using Diagnostic Mode only by trained personnel‚ as improper use may alter system configuration. Logs are archived in internal memory and can be retrieved through the console’s web interface. Regular use helps preempt issues‚ reduce downtime‚ and maintain safety compliance. The interface is compatible with the Veeder‑Root mobile app for monitoring. The manual includes screenshots‚ sample logs‚ and a troubleshooting flowchart. Following the recommended schedule—daily for critical sensors and weekly for peripheral modules—keeps the TLS‑350 in optimal condition and ensures accurate inventory data and reliable tanker load reporting!!
Maintenance and Troubleshooting
Maintenance and troubleshooting sections guide users through routine checks‚ fault isolation‚ and corrective actions; Follow the TLS‑350 checklist‚ update firmware‚ inspect wiring‚ and use diagnostic mode to pinpoint issues. Refer to the manual for detailed steps. Ensure regular calibration logs. now
Troubleshooting Procedures
Step 1: Verify power and communication links. Ensure the TLS‑350 console receives 24 V and that all serial cables are intact. Faulty power can trigger the red fault LED and halt data transmission. If the console powers but displays “NO COMM”‚ check the RS‑232/485 settings against the configuration table in the manual. Confirm that the baud rate‚ parity‚ stop bits‚ and flow control match the console’s defaults. A mismatch will prevent the console from receiving tank data and will cause the “COMM ERROR” status to appear on the display.
Step 2: Inspect sensor connections. Verify that the liquid level probe‚ vapor sensor‚ and ground‑water probe are properly seated and free of debris. A loose probe can produce erratic readings or trigger the “LEVEL ERROR” alarm. Use a multimeter to confirm continuity and check for corrosion on connector pins. If a probe shows an open circuit‚ replace it immediately.
Step 3: Run diagnostic mode. Press the “DIAG” button to bring up the diagnostic screen. The console will cycle through self‑tests: pump relay status‚ sensor health‚ and communication integrity. If any test fails‚ the console will display a fault code. Cross‑reference the code with the troubleshooting table in the manual; codes such as “P‑01” indicate pump relay failure‚ while “S‑02” points to sensor disconnection.
Step 4: Log fault codes and sensor data. Schedule a follow‑up inspection within 48 hours. If issues persist‚ contact Veeder‑Root support for service now.!!
Maintenance Report (TLS-350 Only)
The TLS‑350 maintenance report is an auto‑generated log that records all service events‚ sensor calibrations‚ and component replacements performed on the console. When powered on‚ the system checks the maintenance counter and‚ if an interval has been reached‚ prompts the operator to open the Maintenance Report menu. The report is divided into sections: System Status‚ Sensor Calibration‚ Component History‚ and Service Notes. In the System Status area‚ the console displays the current firmware version‚ the last firmware update date‚ and a summary of any pending updates. The Sensor Calibration section lists each probe (liquid level‚ vapor‚ and ground‑water) with its last calibration date‚ the calibration value‚ and the tolerance achieved. If a probe has not been calibrated within the manufacturer‑recommended interval‚ the console will flag it with a red warning icon. The Component History section tracks the life cycle of critical hardware such as the pump relay‚ the main power supply‚ and the communication module. Each entry includes the part number‚ serial number‚ installation date‚ and the number of operating hours since the last replacement. The Service Notes section allows the technician to enter free‑form text describing any observations‚ corrective actions taken‚ or parts ordered. The report can be printed directly from the console using the built‑in thermal printer‚ or exported via USB to a computer for archival purposes. The TLS‑350 also supports a “Maintenance Tracker” feature that sends an email alert to the service manager when the next maintenance interval is approaching. This helps maintain reliability. All logs are kept. Now!!!
System Periodic Maintenance Checklist
The TLS‑350 periodic maintenance checklist ensures reliable operation. Follow each step‚ log actions in the Maintenance Report‚ and trigger the Maintenance Tracker if enabled. Daily checks recommended for performance now
- Visual Inspection – Verify ports for dust or damage.
- Power Supply Check – Confirm voltage within ±5 % and UPS backup.
- Sensor Calibration – Calibrate liquid‚ vapor‚ and ground‑water sensors; record dates.
- Component Review – Inspect pump relay‚ main relay‚ and communication module; replace if hours exceed limits.
- Firmware Update – Install latest firmware following the update procedure.
- Communication Test – Run diagnostics on serial‚ Ethernet‚ and wireless interfaces.
- Alarm Verification – Trigger level‚ vapor‚ leak‚ and power alarms; ensure logs.
- Print Test – Print a test page; check head cleanliness.
- Filter Check – Replace air filters and verify fan speed.
- Safety Test – Operate emergency stop and lockout/tagout; confirm safe shutdown.
- Documentation – Update Maintenance Report and send email alert if Tracker enabled.
Completing this checklist quarterly keeps the TLS‑350 compliant with safety standards and delivers accurate‚ real‑time tank monitoring.