FAQs | Veeder-Root


Common Technical Issues for Veeder-Root ATG Systems and Accessories
1. Business Inventory Reconciliation (BIR)
2. Continuous Statistical Leak Detection
3. Tank Level Sensing (TLS)
4. Magnetostrictive Probes
5. Sensors/Smart Sensors
6. Communication Hardware and Software

FAQ Content


Business Inventory Reconciliation (BIR)
What are the TLS 350 software requirements to support BIR for single and manifold tank applications?
Single Tanks Only—Version 106 to123 Software (ECPU 1 Board) with BIR SEM (330160-1XX) installed. Single or Line Manifold with Single Tank Application—Minimum Version 123 or Higher Software (ECPU 1 Board) with BIR SEM (330160-1xx) installed.
Single or Siphon Manifold Tank Application—Version 310 or Higher Software (ECPU1 with extra RAM or ECPU 2 board) with BIR SEM (330160-1XX) installed.
Single/Siphon or Line Manifold Tank Application—Minimum Version 323 or Higher Software with BIR SEM (330160-1XX) installed. Note: Please see TLS-350 Troubleshooting (Manual # 576013-818) for further details on Software requirements
What hardware must be installed in a TLS 350 to perform BIR?
ECPU1 or ECPU2 upgrade kit.
Dispenser Interface Module (EDIM, CDIM, MDIM).
Appropriate DIM installation Kit or connecting cable.
Does BIR support blended product applications?
Most major manufacturers' ELECTRONIC blend dispensers are supported. The electronic blend dispenser MUST be configured to meter "Pure Product"—BEFORE the actual blending takes place.
Mechanical blend dispensers (with fixed ratio blend valves) are NOT supported.
Note: Please see Point of Sale Application Guide (Manual #577013-401) for further Details on BIR Application
What is required to produce the BIR Report?
Dispenser transactions via the Veeder-Root Dispenser Interface Module (DIM).
Tank Inventory, Delivery information via the Veeder-Root In-tank Magnetostrictive Probe.
Completed Meter to Tank assignment performed by the TLS-350R system.
Does the Meter to Tank Mapping assignments need to be manually programmed by a technician?
No, meter to tank mapping does not need to be performed manually. The BIR program will automatically complete the mapping process as it monitors the dispenser transactions received through the DIM.
Note: Under certain circumstances you maybe required to manually enter the Tank to Meter mapping. Please see System Setup Manual # 576013-623 for details.
How long does it take to complete the auto-mapping process?
The Meter to Tank mapping is completed only when the activity level of each dispenser meter provides adequate data to the TLS. The TLS will assign a Tank to each meter to complete the mapping. Meters with more activity will receive a tank assignment faster. A site with high levels of activity on all meters can typically complete the mapping process within 24 to 48 hours.
What could cause a Periodic BIR report to stop updating data or skip a data entry for a day or more?
An active Tank "Probe Out" Alarm condition—Loss of tank inventory data
Meter/Tank Map status goes "Incomplete."
What could cause a Meter/Tank Map to change to an "Incomplete" status?
Dispenser upgrade/maintenance that changes the Meter configuration.
Adding an additional dispenser to an existing site.
Receiving transaction data from a previously dormant product dispenser—Like Kerosene, a seasonal product.
TLS maintenance-existing map data "Cleared" by a technician.
(top of page)

Continuous Statistical Leak Detection (CSLD)
CSLD collects information during each idle time to form a highly accurate leak detection database. Since the database is constantly being updated, leak test results are always current. Periodic leak tests are performed using the best data from the previous 28 days, and test results are continuously updated as new data is gathered. Invalid data is discarded and only the best data is used to ensure accurate leak test results and fewer false alarms. Test results are provided automatically every 24 hours.
What can cause a CSLD Rate Increases Warning?
Pump leak-air gets into pump and drains column pipe or check valve leak.
Broken or intermittent siphon-check with clear plastic tubing in siphon line.
Vapor recovery—Use a vapor trap to collect liquid.
Thermal expansion—Summertime phenomenon where shallow buried lines expand.
Programming—Verify thermal coefficient and tank charts.
What can cause a Tank Failure alarm?
Bad Probe—Weird inventory/alarms or very strange temperature readings.
Programming—Verify thermal coefficient and tank charts.
Tank is manifold and not programmed as manifold.
Upside down float—Verify float direction.
Evaporation—Air leak into the tank. Check vapor recovery system, pressure vent cap, all tank sump areas, riser caps, delivery sump plunger valve.
Stuck Relay—Artificially warming of the tank causing temperature fluctuations.
Actual leak-verified using a static test.
Previous stuck float, if there was a stuck float do to overfill in the last 28 days.
What will cause a No CSLD Idle Time
Excessive throughput-Site is too busy, doesn’t have 28 consecutive minutes of idle time.
Console is turned off at night.
Defective probe.
Noise on probe wiring.
All tests in the table are being rejected due to increases in excess of +.4gph.
Too soon after startup to get results—Needs 6 hours in first 10 days or 10 hours in first 5 days.
What conditions would generate a NO DATA AVAILABLE WARNING?
Not enough time to generate a result after start-up.
Console is being shut off on a regular basis.
Tank too busy.
(top of page)

Tank Level Sensing (TLS)
TLS-350 does not display readings on the liquid crystal display.
No AC power to TLS monitor.
# 3 Dip Switch (S1 or SW1) on CPU/ECPU board in closed position.
AC fuse blown.
Defective power supply; check the +8 and +20 test points.
Defective liquid crystal display.
What would cause a SETUP DATA WARNING?
A label for a sensor or probe was not entered during the setup of the TLS-350 or TLS-300.
Incorrect sensor type was selected during setup.
The sensor or probe was not configured during setup, but the console measures a resistance value and determines a device is connected to the Console.
Why would a TLS console Warm Boot?
CPU/ECPU failure In proper.
Earth Ground TLS.
Interface module failure.
What would cause the TLS Console to lose memory (Programming)?
Battery Switch on the CPU/ECPU board is set to the OFF position.
Battery is defective—Normal range 3.6 VDC.
Defective CPU/ECPU board.
What would cause the TLS printer not print or feed paper?
Printer traction lever in the down position, or retention spring defective
Printer out of paper
Printer cable loose or defective
Defective printer communication interface module (CPU board only)
If CPU board was upgraded to an ECPU board, and Printer communications interface module is still installed in the communications bay
(top of page)

Magnetostrictive Probes
Why would the Magnetostrictive probe produce an incorrect height/volume reading?
Float size in In-Tank setup is programmed incorrectly.
Programming is missing setup data.
Tank Tilt is programmed incorrectly.
Probe wired to wrong probe channel of probe module.
Probe not sitting on bottom of tank.
Fuel or Water assembly installed upside down.
Dirty Probe Shaft Defective Probe.
What causes an Invalid Fuel Alarm?
Fuel is too low in the tank (Fuel and Water float magnets are too close together).
Defective float magnet.
What conditions would cause the TLS to read a probe out condition?
Corroded splices at the junction box.
Defective probe cable.
Probe Interface Module defective channel.
Defective barrier board,
Defective probe.
Intermittent TLS ground source.
What could cause Ghost Deliveries to occur?
Field wiring splices having moisture build up.
Defective field wiring.
Other control wires in probe conduit.
Grounding improper on conduit.
Variable speed submersible with no shielded cable.
Defective Product float magnet.
Defective Probe.
Defective barrier board.
(top of page)

Sensors/Smart Sensors
Vacuum Sensor Terminology
Vacuum OK—The vacuum pressure piggyback threshold. There is no need to increase the vacuum of the interstitial space. The Vacuum Control Valve (VCV) is closed and the aux hook is off.
No Vacuum—Any time the pressure NO_VACUUM_THRESHOLD (-1.0 PSI) the vac sensor will go into the NO_VACUUM state and a No Vacuum alarm will be posted. A manual test must be run to get out of the NO_VACUUM state and clear the No Vacuum alarm.
Evac Active—A Direct or Piggyback evacuation is running and VCV is open.
Evac Pending—A Direct or Piggyback evacuation is pending and the VCV is closed. A Piggyback evacuation will be pending when there is no dispensing from the vac pump and the pressure is between the Direct threshold and the Piggyback threshold. A Direct evacuation will be pending if the vac pump is off and the pressure is between the No Vacuum threshold and the Direct threshold. It may be pending because another Vac Sensor assigned to the same pump is doing an evacuation.
EVAC Active Manual—Manual Test evacuation is running and the VCV is open.
Evac Pending Manual—Manual Test evacuation has been started but the VCV is closed. Another Vac Sensor assigned to the same pump may be doing an evacuation.
Evac Hold—When an Evacuation Hold is started the state will be set to EVAC_HOLD. If the VCV is open it will closed and stay closed during the Evacuation Hold. Once an Evacuation Hold is started it will remain in-progress until stopped by one of the following:
User aborts the Evacuation Hold
User starts a Manual Test.
The Vacuum Control Valve (VCV) can be in one of three states:
Closed—The VCV is closed. Not evacuating.
Open—The VCV is opened during an evacuation to the allow the pump to bring the pressure of the vacuum space down.
Fault—The VCV will not change position when commanded.
Vac Sensor Hardware Requirements
TLS-350/350R with version 24C or later software.
At least one Smart Sensor/Press Module.
Line leak (PLLD or WPLLD), or without line leak, a Pump Sense and a 4-Relay module is required for STP control.
Siphon manifold tank requirements:
The Red Jacket STP requires a secondary siphon assembly (V-R P/N 410071-002).
The Quantum STP comes with two siphons as standard equipment —no additional parts are required.
FE pumps require a secondary siphon kit (FE P/N 402-507-930).
Available Kits—Vac sensor kits are available in several configurations:
2, 3, or 4 Vac Sensor/Vac Float pre-assembled kits - includes mounting hardware, tubing/connections, and cable (for one sump).
2 Vac Sensor kit w/steel float, 3 Vac Sensor kit w/steel float, or 4 Vac Sensor kit w/steel float.
2, 3, or 4 Vac Sensor kit w/fiberglass 4’, 6’, 8’, or 10’ float (includes relief valve).
2, 3, or 4 Vac Sensor kit w/o tank interstitial sensor Individual kits (requires Vac Sensor/Vac Float field assembly).
Mounting kit - 1 required per sump.
Secondary piping vacuum monitoring system kit—1 each required for product line, vapor recovery line, or sump.
Interstice monitoring—includes mounting hardware, tubing/connections, and cables.
Interstitial sensor kit for steel tank—includes Vac Sensor, mounting hardware, tubing/connections, riser cap, and cables.
4’, 6’, 8’, or 10’ diameter fiberglass tank Interstitial sensor kit—includes Vac Sensor, mounting hardware, tubing/connections, riser cap, relief valve, and cables. NOTE: You do not need to order an additional relief valve for a fiberglass tank installation.
Vacuum Sensor Kits
Secondary Containment Vacuum Sensing (SCVS) System
The Secondary Containment Vacuum Sensing (SCVS) System is designed to detect leaks in double walled tanks and piping systems while helping to contain the release of product while under vacuum.
NOTE WHEN ORDERING WITH TLS-350 SYSTEMS: Secondary Containment Vacuum Sensing Systems require the following:
One Seven-Input Smart Sensor w/ Embedded Pressure Sensor Module (P/N 332250-001), for up to seven vacuum sensors.
For systems with more than seven vacuum sensors, additional: Eight-Input Smart Sensor Modules (P/N 329356-004) can be ordered for up to eight additional smart sensors per module.
Also requires software version 24C or higher (additional hardware).
May be required – requires ECPU2 or ECPU w/ NVMEM1 board.
The Vacuum Sensing System is compatible with TLS-350R/EMC w/BIR, TLS-350Plus/EMC.
The Vacuum Sensing System requires the console to have pump sense and control hardware For example: a Six-Input Pressurized Line Leak Interface Module & Three-Output Pressurized Line Leak Controller Module or a Four-Relay Output Interface Module & Four-Input Pump Sense Interface Module.
The Vacuum Sensing System requires an STP with an available siphon port. STP’ s that are used for siphon manifold tank applications require a second siphon port for the vacuum sensing system.
Field Service Bulletin
Date: 04/21/05
Subject: External Siphon Check Valve Required On All Submersible Turbine Pumps (STPs) Used By The Secondary Containment Vacuum Sensing (SCVS) System
Equipment Type: SCVS System
References: SCVS Manual (p/n 577013-836)
Overview: The following installation message pertains to the Veeder-Root Secondary Containment Vacuum Sensing (SCVS) system for AB 2481 compliance:
An external Siphon Check Valve (Veeder-Root / Red Jacket p/n 188-241-5) must be used when making a vacuum source connection between the SCVS system sensors and the siphon port cartridge for all STPs including the Red Jacket, Red Jacket Standard, Red Jacket Quantum, and FE pumps. Only Veeder-Root supplied Vacuum Hose (Veeder-Root p/n 332310-001,-002,-003) is approved for use with the SCVS system. Failure to install a Veeder-Root external Siphon Check Valve or to use Veeder-Root supplied Vacuum Hose could increase the risk of a product release in the containment sump area. For more information, please see the latest SCVS manual or consult your local Veeder-Root field service representative.
Wireless Pressurized Line Leak Detection (TBD)
Pressurized Line Leak Detection (TBD)
Volumetric Line Leak Detection (TBD)
Wireless Magnetostrictive Probes (TBD)
Mag Sump Sensors (TBD) In-Station Diagnostic (ISD)
(top of page)

Communication Hardware and Software
Interface Requirements/Installation Tips and Proper Procedures
TLS Console System Software minimum requirement of Version 15 or higher. Version 21 or higher is recommended.
NETWORK CONNECTION to a PC requires a hub, connecting to a hub requires a straight CAT 5 cable. DIRECT CONNECT using a laptop requires an Ethernet crossover cable.
Reference the TCP/IP Installation Guide for proper Installation and Illustration of the TCP/IP module for TLS350 and TLS300 Series. You will need to enter this number for the TCP/IP hardware address in the TCP/IP interface module IP address/Configuration Setup. See page 13, on the installation manual. Record the Rev of the board as it may be needed in Setup. See Installation Guide Figure 1, See Page 3 for an illustration. Before installing the TCP/IP interface module, ensure that power has been removed from the TLS console. After installing the interface module in the communications compartment, locate the 4 LED's on the top edge of the TCP/IP Interface Module (see figure 3 on page 5 of Installation Manual). Turn On power to the console, upon Power up the red (ch1) and amber (DIAG) LED’s will flash a few times and then the red LED will remain on and the amber LED will go off. This verifies that the console has read the new interface module and the E/CPU board has established communications with the module. Please see Installation Manual attachment starting on Page 7 for communication programming.
After the TCP/IP Interface Module is installed and set up in the console, it can be connected to a PC over a network (LAN, WAN) or directly. To connect the TCP/IP Interface Module over a Network see Figure 7, page 9 of installation manual, (attachment under Engineering Notes), or Pull down above labeled CONNECTING TO THE TCP/IP INTERFACE MODULE OVER a NETWORK. Insert the RJ-45 plug of the network CAT5 cable into the RJ-45 connector in the end plate of the TCP/IP Interface Module. The green LED (Link On) in the end plate of the TCP/IP Interface Module should remain ON when a proper connection is made. After confirming a successful link between the PC and the TCP/IP module, go to TCP/IP Interface Modules IP Address/Configuration on page 13 of installation manual (attachment) or use database pull down above (Connecting to the TCP/IP Interface Modules IP address/Configuration Setup).
Insert the RJ-45 plug of the network CAT5 cable into the RJ-45 connector in the end plate of the TCP/IP Interface Module. The green LED (Link On) in the end plate of the TCP/IP Interface Module should remain ON when a proper connection is made. After confirming a successful link between the PC and the TCP/IP module, go to TCP/IP Interface Modules IP Address/Configuration on page 13 of installation manual (attachment) or use database pull down above (Connecting to the TCP/IP Interface Modules IP address/Configuration Setup).
Connect the PC to the TCP/IP Interface Module as shown in Figure 8 page 10 of installation manual. Insert the RJ-45 plug of the Ethernet crossover cable into the RJ-45 connector in the end plate of the TCP/IP Interface Module. The green LED (Link On) in the end plate of the TCP/IP Interface Module should be solid when a proper connection is made. Before entering the TCP/IP Interface Modules IP address you must first enter a STATIC IP ADDRESS in your connected laptop. IP Address setup procedures for both Windows 98 and 2000 are discussed in the section. Windows ME or XP procedures may be different. Please check the operating systems manual to verify their method of entering IP Addresses. ARP and Telnet are utilities available in Windows operating systems and are used in the TCP/IP addressing procedure. ARP is a TCP/IP protocol used to convert an IP address into a physical address (Called a DLC address), such as an Ethernet address. A host wishing to obtain physical addresses broadcasts as ARP request onto the TCP/IP network. The host on the network that has the IP address in the request then replies with its physical hardware address. ARP will only work when the console and PC share the same subnet. Telnet is a terminal emulation program for TCP/IP networks such as the Internet. The Telnet program runs on your computer and connects your PC to a service on the network. You can then enter commands through the Telnet program and they will be executed as if you were entering them directly on the server console. This enables you to control the server and communicate with other servers on the network. With the PC connected to the TCP/IP Interface Module as discussed in the Configuration Setup, performing steps below now can commence:
1.) At the DOS command prompt type (the spaces between words and letters in all entries must be entered as shown or the address will not be successfully assigned. Arp -s y.y.y.y 00-20-4a-xx-xx-xx (where y.y.y.y is the IP Address of the TCP/IP module (see your network administrator) and 00-20-4a-xx-xx-xx is the number from the label on the back of your TCP/IP module see Problem Topic 539. Press Enter. The Modules IP address is added to the ARP table and the screen will return to the DOS command prompt. Type ARP -A at the DOS command prompts and press the Enter key to view the contents of the ARP table and verify the presence of the TCP/IP Interface Modules IP Address.
2.) At the DOS command prompt type- telnet y.y.y.y 1, Press Enter. The following message will appear- connecting to y.y.y.y...Could not open a connection to host on port 1. Connect failed or could not open connection to Y.Y.Y.Y. The screen will then display the DOS command prompt.
3.) At the DOS command prompt type Telnet y.y.y.y 9999 (ip address and port #). Press Enter twice.
Depending on the VR software version this will determine the Flow Control (00 versus 02).
We recommend after installation of the TCP IP module to perform a warm start to receive proper communication.
DisConn Time defaults to 1:30 (one minute and thirty seconds). If you change the program time to 10:00 (ten minutes) this will disconnect your connection after ten minutes of being idle and no data packets are being sent or received through the LAN. I suggest if you need to a constant connection to the site you will need to change the settings to 0:0 (zero minutes). If you choose to go this route you will not be able to set the TLS to autodial out for an inbound connection at the monitoring site since the connection is in use. You would need additional IP Card/ IP Address to call into.
We highly recommend a certified Technician to do the installation and to program and configure the card manually without running a script file since ever environment and network is configured uniquely.
To delete the Arp table you need to type Arp -d IP ADDRESS. For example, Arp -d
Most frequent Inform questions asked:
How is the software licensed? named or concurrent.
You can purchase different site license packages such 1-5 sites, 1-20 sites, 1-100, greater than 100 sites. It should be installed on one dedicated host pc. Most current version at this time Inform 3.1 and Inform 4.0 will be released in February 20, 2006. What are the hardware requirements (Workstation or Server)? workstation only, we haven't validated to run on server platform. System minimum requirements are Microsoft Windows: XP, 2000, NT, 98, 95. Pentium class processor: 233 mhz, 50mb available hard drive capacity, 64mb Ram, and Modem/Network Connection.
Does the application require ADMINISTRATOR access? At installation only is OK.
Need admin rights to install the software and to use the application you must have administrator or minimal power user privileges.
Does the application have components that run as a service? We preference the service to run as other than ADMINISTRATOR.
You can have inform auto poll to collect data; such as inventory, deliveries automatically at a scheduled time. Your able to program the tank gauge to auto dial alarms and call into Inform and use the email feature to make aware that an alarm condition has occurred at the site.
What database does the application use? We preference the application not to execute with database accounts that require SA (System Admin) access.
Application used is MS Access, which is accessible to the end user to query and manipulate the data; however, not to modify the original table format.

(top of page)