Home

FS-8700-74 Veeder-Root - Chipkin Automation Systems

1. 408 262 9042 Toll_Free 888 509 1970 email support fieldserver com FS 8700 74 Veeder Root Driver Manual Page 14 of 33 Appendix A Advanced Topics Appendix A 1 Data Type and Required Lengths The following table provides a list of possible values for the data type parameter as well as the minimum value that the length parameter should be set to for each Map Descriptor of that data type Data Type Length Parameter Setting Normal 1 System 30 Tank 30 Liquid Sensor 30 Vapor Sensor 30 Input 30 Volumetric Line 30 Groundwater Sensor 30 Type A Sensor 30 Type B Sensor 30 Universal Sensor 30 Auto Dial 30 Mech Dispenser 30 Elec Dispenser 30 Product 30 Press Line 30 WPLLD 30 External 30 Relay 30 Configuration 1 In Tank Inventory 10 Misc 20 In Tank Delivery 100 System Reset 20 Clear Power Reset 20 Remote Alarm Reset 20 Confirm Clear 20 Clear Delivery Reports 20 Start In Tank Leak Detect Test 20 Stop In Tank Leak Detect Test 20 Delete CSLD Rate Table 20 Start P Line Leak Detect Test 20 Stop P Line Leak Detect Test 20 Start WPLLD Leak Detect Test 20 Stop WPLLD Leak Detect Test 20 System Status 1 FieldServer Technologies 1991 Tarob Court Milpitas California 95035 USA Web www fieldserver com Tel 408 262 2299 Fax 408 262 9042 Toll_Free 888 509 1970 email support fieldserver com FS 8700 74 Veeder
2. JJ SPECIAL 3 TANK LINE CONSOLE 00 DISABLE 01 ENABLE nnnnnn vw r SEM Info 3 parts if none NO SOFTWARE MODULE nnnnnn SEM number ASCII text string vvv SEM Software version number ASCII text string r SEM Software revision level ASCII text string Map_Descriptor Name Data_Array_Name Data_Array Offset Scan_interval Function node_name Address Length Veed Function Data_Type System1poll_1 DA_REVISION2 0 3 10 0s f rdoc Node A 1 100 0x905 Misc FieldServer Technologies 1991 Tarob Court Milpitas California 95035 USA Web www fieldserver com Tel 408 262 2299 Fax 408 262 9042 Toll_Free 888 509 1970 email support fieldserver com FS 8700 74 Veeder Root Driver Manual Page 31 of 33 Appendix C 7 Advanced Example 7 Stick Height Report This example reads the Stick height Report from the Veeder Root Panel The result is stored as a scaled if scaling specified in the Map Descriptor real number Use one Map Descriptor per tank Map_Descriptors Map_Descriptor_Name Data_Array_Name Data_Array_ Offset Scan_Interval Function node_name Address Length Data_Type Poll_Height1 DA_STICKHEIGHT 0 3 0 8s rdoc Node_A 1 1 In Tank Stick Height Appendix C 8 Advanced Example 8 Active Alarm Report This example reads the Veeder Root Panel for active alarms includes acknowledged and active If there are any active alarms then the 1 element of the Data Array is set non z
3. not bound to a port Can t be used Read the notes for Error 4 to see how to correct this problem Vroot 22 FYI Config reported zero modules You may ignore this message The Veeder Root device reported zero configured modules in response to a configuration enquiry VROOT 23 Err Address 0 invalid for this command Set the address to a positive number corresponding to the tank sensor input device whose data you are polling for This is a configuration error which can be eliminated by correcting an error in the CSV file and resetting the FieldServer FieldServer Technologies 1991 Tarob Court Milpitas California 95035 USA Web www fieldserver com Tel 408 262 2299 Fax 408 262 9042 Toll_Free 888 509 1970 email support fieldserver com FS 8700 74 Veeder Root Driver Manual Page 24 of 33 Error Action Required Md lt s gt Check the data type s spelling spacing and punctuation If this is correct and you have specified the Veed_Function parameter in VROOT 24 Err the Map Descriptor then check that the function is supported by Function x not supported the driver Table 6 1 and check that you specified it correctly Md lt s gt The functions numbers in table 6 1 are hexadecimal numbers Either convert them to decimal or specify them in the CSV file using the notation Oxnnn where nnn is the function number This message may be safely ignored It does not indicate
4. 1 1000 This is important because the driver uses the length to for example clear Data Array elements when a Tank Sensor has no alarms 4 4 3 Timing Parameters Column Title Function Legal Values Scan_Interval Rate at which data is polled gt 0 1s See Appendix A 1 for Data Type Address and Length Limitations FieldServer Technologies 1991 Tarob Court Milpitas California 95035 USA Web www fieldserver com Tel 408 262 2299 Fax 408 262 9042 Toll_Free 888 509 1970 email support fieldserver com FS 8700 74 Veeder Root Driver Manual Page 10 of 33 4 4 4 Map Descriptor Example 1 Alarms This example provides one Map Descriptor to poll for alarm data and many Map Descriptors to store the response from the poll One Map Descriptor is required for each tank sensor input device defined for the system The address of each of these passive Map Descriptors must correspond to the tank sensor input device number For example where 5 tanks are defined as tanks 1 2 3 6 7 then 5 Map Descriptors with the data type Tank are required and the address of each of these 5 Map Descriptors must be set to 1 2 3 6 7 The length parameter tells the driver how much array space is reserved for each tank sensor for storing alarms Map_ Descriptors Map_Descriptor_Name scan_interval Data_Array_Name Data_Array Offset Function node_name Address Length Data_Type Poller 1 0
5. 7 Sensor Water Out Alarm 8 Sensor High Liquid Alarm 9 Sensor Low Liquid Alarm 10 Sensor Liquid Warning 2 Sensor Setup Data Warning 3 Sensor Fuel Alarm 4 Sensor Out Alarm 5 Sensor Short Alarm 6 Sensor Water Alarm 7 Sensor Water Out Alarm 8 Sensor High Liquid Alarm 9 Sensor Low Liquid Alarm 10 Sensor Liquid Warning k Input Setup Data Warning Input Normal Input Alarm w N VLLD Setup Data Warning VLLD Self Test Alarm VLLD Shutdown Alarm VLLD Leak Test Fail Alarm VLLD Selftest Invalid Warning VLLD Continuous Handle On Warning VLLD Gross Line Test Fail Alarm VLLD Gross Line Selftest Fail Alarm VLLD Gross Pump Test Fail Alarm 10 VLLD Gross Pump Selftest Fail Alarm 11 VLLD Periodic Test Needed Warning 12 VLLD Annual Test Needed Warning 13 VLLD Periodic Test Needed Alarm 14 VLLD Annual Test Needed Alarm 15 VLLD Periodic Line Test Fail Alarm 16 VLLD Periodic Line Selftest Fail Alarm 17 VLLD Periodic Pump Test Fail Alarm 18 VLLD Periodic Pump Selftest Fail Alarm 19 VLLD Annual Line Test Fail Alarm 20 VLLD Annual Line Selftest Fail Alarm 21 VLLD Annual Pump Test Fail Alarm 22 VLLD Annual Pump Selftest Fail Alarm 23 VLLD Pressure Warning 24 VLLD Pressure Alarm 25 VLLD Gross Test Fault Alarm 26 VLLD Periodic Test Fault Alarm 27 VLLD Annual Test Fault Alarm 28 VLLD Fuel Out Alarm OANOAARWD FieldServer Technologies 1991 Tarob Court Milpitas California 95035 USA Web www fieldserver com Tel 408 2
6. DA_S1_CLEAR 0 DA_T1_CLEAR 0 A Data_Array_ Offset node_name Address Node_A ie node_name Address Node A 1 A Node A 1 Length 1 Length Data_Type Active Alarm Report Data_Type System Tank If there are active alarms they will get stored in the primary array The cleared alarm information gets stored in the secondary array specified with the DA_Byte_Name The value stored is a 1 to show alarm cleared Or 1 2 to show alarm occurred The value is stored at the location which corresponds to the alarm type Thus if a 02 Tank Leak Alarm was cleared then at index 2 the value stored will be a one FieldServer Technologies 1991 Tarob Court Milpitas California 95035 USA Web www fieldserver com Tel 408 262 2299 Fax 408 262 9042 Toll_Free 888 509 1970 email support fieldserver com FS 8700 74 Veeder Root Driver Manual Page 33 of 33 This page intentionally left blank FieldServer Technologies 1991 Tarob Court Milpitas California 95035 USA Web www fieldserver com Tel 408 262 2299 Fax 408 262 9042 Toll_Free 888 509 1970 email support fieldserver com
7. Array value 49 indicates product code ASCII 1 1 Tank Status Bit 1 LSB Delivery in Progress Bit 2 Leak Test in Progress Bit 3 Invalid Fuel Height Alarm MAG Probes Only 2 Volume 3 TC Volume 4 Ullage 5 Height 6 Water 7 Temperature 8 Water Volume Map_Descriptor_ Name Data_Array_Name Data_Array_ Offset Function Scan_Interval node_name Address Length Data_Type InventoryPoll1 DA_INVENTORY 0 rdbc_ 1 0s Node A _ 1 10 In Tank Inventory Reading the inventory requires an active Map Descriptor Set the address equal to the This is the minimum number of Data tank number One Map Array elements required to store Descriptor per tank inventory data Tanks 1 s data will be stored in the array DA_LINVENTORY starting at the zero th element offset 0 and 10 elements of the array are reserved for this data Setting the data type generates the correct poll Ensure that spelling periods hyphens in exactly the same as this example FieldServer Technologies 1991 Tarob Court Milpitas California 95035 USA Web www fieldserver com Tel 408 262 2299 Fax 408 262 9042 Toll_Free 888 509 1970 email support fieldserver com FS 8700 74 Veeder Root Driver Manual Page 12 of 33 4 4 6 Map Descriptor Example 3 Most Recent Delivery Report This example illustrates how you can poll for Tank Delivery Data You need one Map Descriptor for each tank Change
8. Root Driver Manual Page 15 of 33 Appendix A 2 Supported Functions The Veeder Root protocol specification defines a large number of enquiries and commands that may be sent to a Veeder Root device This driver supports a limited set of the functions The revision number indicates the minimum Veeder Root firmware revision required for support of th e function Function_ Revision _ Description SYSTEM REPORTS 7 2 1 101 1 System Status Report 102 1 System Configuration Report 113 14 Active Alarm Report 114 19 Cleared Alarm Report IN TANK REPORTS 7 2 2 201 1 In Tank Inventory Report 202 1 In Tank Delivery Report 203 1 In Tank Leak Detect Report 204 1 In Tank Shift Inventory Report 205 1 In Tank Status Report 20C 15 In Tank Most Recent Delivery Report 20D 15 In Tank Stick Height Report SENSOR REPORTS 7 2 3 301 1 Liquid Sensor Status Report 306 1 Vapor Sensor Status Report 311 1 Groundwater Sensor Status Report 341 2 Type A 2 Wire CL Sensor Status Report 346 2 Type B 3 Wire CL Sensor Status Report 34B 4 Universal Sensor Status Report LINE LEAK REPORTS 7 2 4 381 7 Pressure Line Leak Status 386 10 WPLLD Line Leak Status 0 DEVICE REPORTS 7 2 6 401 1 Input Status Report 406 1 Relay Status Report SYSTEM DIAGNOSTIC REPORTS 7 4 1 901 1 Self Test Results Report 902 1
9. System Revision Level Report 905 15 System Revision Level Report II CONTROL FUNCTIONS 7 1 1 1 System Reset 2 1 Clear Power Reset Flag 3 1 Remote Alarm Reset 31 10 Confirm Clear Function 51 1 Clear In Tank Delivery Reports 52 1 Start In Tank Leak Detect Test 53 1 Stop In Tank Leak Detect Test 54 5 Delete CSLD Rate Table 81 7 Start Pressure Line Leak Test 3 0 GPH only in V18 82 7 Stop Pressure Line Leak Test 83 10 Start WPLLD Line Leak Test 3 0 GPH only in V18 84 10 Stop WPLLD Line Leak Test FieldServer Technologies 1991 Tarob Court Milpitas California 95035 USA Web www fieldserver com Tel 408 262 2299 Fax 408 262 9042 Toll_Free 888 509 1970 email support fieldserver com FS 8700 74 Veeder Root Driver Manual Page 16 of 33 The function numbers in Appendix A 1are hexadecimal numbers If you specify them in the CSV file using the Veed_Function parameter then either convert them to decimal or specify them in the CSV file using the notation Oxnnn where nnn is the function number Example Joe Veed_Function PRTA 0x901 ee Appendix A 3 Alarm Types Category Alarm Type amp Description 1 System 1 Printer out of Paper 1 System 2 Printer Error 1 System 3 EEPROM Configuration Error 1 System 4 Battery Off 1 System 5 Too Many Tanks 1 System 6 System Security Warning 1 System 7 ROM Revision Warning 1 System 8 Remote Display Communications Error 1 System 9 Autodial Error 1 System 10 Sof
10. and Current Values in the corresponding array locations Table 6 7 provides a listing of module types Map_Descriptor_Name Data_Array_Name Data_Array_Offset Scan_interval Function node_name Address Length Data_Type Config_poll_1 DA_MODULES 0 i 10 0S rdbc Node A 30 Configuration Map_Descriptor_Name Data_Array_Name DA_Byte_Name DA_Float_Name Data_Array_Offset Scan_interval Function node_name Address Length Data_Type Config_poll_1 DA_MODULES DA_POWER DA_CURRENT 0 10 0s 7 tdbc_ Node A ae 30 Configuration Power On Reset and Current values are also stored if you define the DA_Byte_Name and the DA_Float_Name Make sure that both of these arrays are UINT32 or FLOAT if you use them FieldServer Technologies 1991 Tarob Court Milpitas California 95035 USA Web www fieldserver com Tel 408 262 2299 Fax 408 262 9042 Toll_Free 888 509 1970 email support fieldserver com FS 8700 74 Veeder Root Driver Manual Page 28 of 33 Appendix C 4 Advanced Example 4 System Diagnostics This example reads the System Diagnostics Report from the Veeder Root Panel The results are stored in 3 consecutive array elements If the value is set non zero then the test FAILED A value of zero means the test passed Index Contents I O test result Ram test result Prom test result Map Descriptor Name Data_Array_Name Data _Array_Offset Scan_interval Function node_name Address Length
11. support fieldserver com FS 8700 74 Veeder Root Driver Manual Category 2 2 2 WWWWWWWW WwW RRR HRHRARHRAH anu DADA VDAIVDAADIAANWAAVAWAADAWAAADNAANAAANHAADAD DD D Tank Tank Tank Liquid Sensor Alarm Liquid Sensor Alarm Liquid Sensor Alarm Liquid Sensor Alarm Liquid Sensor Alarm Liquid Sensor Alarm Liquid Sensor Alarm Liquid Sensor Alarm Liquid Sensor Alarm Vapor Sensor Alarm Vapor Sensor Alarm Vapor Sensor Alarm Vapor Sensor Alarm Vapor Sensor Alarm Vapor Sensor Alarm Vapor Sensor Alarm Vapor Sensor Alarm Vapor Sensor Alarm Input Input Input Volumetric Line Leak Volumetric Line Leak Volumetric Line Leak Volumetric Line Leak Volumetric Line Leak Volumetric Line Leak Volumetric Line Leak Volumetric Line Leak Volumetric Line Leak Volumetric Line Leak Volumetric Line Leak Volumetric Line Leak Volumetric Line Leak Volumetric Line Leak Volumetric Line Leak Volumetric Line Leak Volumetric Line Leak Volumetric Line Leak Volumetric Line Leak Volumetric Line Leak Volumetric Line Leak Volumetric Line Leak Volumetric Line Leak Volumetric Line Leak Volumetric Line Leak Volumetric Line Leak Volumetric Line Leak Volumetric Line Leak Page 17 of 33 Alarm Type amp Description 27 Tank Cold Temperature Warning 28 Tank Missing Delivery Ticket Warning 29 Tank Line Gross Leak Alarm 2 Sensor Setup Data Warning 3 Sensor Fuel Alarm 4 Sensor Out Alarm 5 Sensor Short Alarm 6 Sensor Water Alarm
12. 62 2299 Fax 408 262 9042 Toll_Free 888 509 1970 email support fieldserver com Category NNNNNNNNN Type A Sensor Alarm Type A Sensor Alarm Type A Sensor Alarm Type A Sensor Alarm Type A Sensor Alarm Type A Sensor Alarm Type A Sensor Alarm Type A Sensor Alarm Type A Sensor Alarm o 12 Type B Sensor Alarm 12 Type B Sensor Alarm 12 Type B Sensor Alarm 12 Type B Sensor Alarm 12 Type B Sensor Alarm 12 Type B Sensor Alarm 12 Type B Sensor Alarm 12 Type B Sensor Alarm 12 Type B Sensor Alarm 13 Universal Sensor Alarm 13 Universal Sensor Alarm 13 Universal Sensor Alarm 13 Universal Sensor Alarm 13 Universal Sensor Alarm 13 Universal Sensor Alarm 13 Universal Sensor Alarm 13 Universal Sensor Alarm 13 Universal Sensor Alarm 14 Auto Dial 14 Auto Dial 14 Auto Dial 14 Auto Dial 14 Auto Dial 18 Elec Dispenser 18 Elec Dispenser 18 Elec Dispenser 20 Product Alarm 20 Product Alarm 20 Product Alarm 20 Product Alarm 21 Pressure Line Leak 21 Pressure Line Leak FS 8700 74 Veeder Root Driver Manual Page 18 of 33 Alarm Type amp Description Groundwater Sensor Alarm2 Sensor Setup Data Warning Groundwater Sensor Alarm3 Sensor Fuel Alarm Groundwater Sensor Alarm 4 Sensor Out Alarm Groundwater Sensor Alarm5 Sensor Short Alarm Groundwater Sensor Alarm6 Sensor Water Alarm Groundwater Sensor Alarm 7 Sensor Water Out Alarm Groundwater Sensor Alarm8 Sensor High Liquid Alarm Groundwater Sensor Al
13. A_AO_01 UInt16 200 DA_DI_01 Bit 200 DA_DO_01 Bit 200 FieldServer Technologies 1991 Tarob Court Milpitas California 95035 USA Web www fieldserver com Tel 408 262 2299 Fax 408 262 9042 Toll_Free 888 509 1970 email support fieldserver com FS 8700 74 Veeder Root Driver Manual Page 7 of 33 4 2 Client Side Connections Section Title Connections Column Title Function Legal Values Specify which port the device is z pol Pon connected to the FieldServer EVE Serene P 300 9600 standard baud rates Pa SPERI PAUC TAIE only Vendor limitation Parity Specify parity Even Odd None Data_Bits Specify data bits 7 8 Stop_Bits Specify stop bits 1 2 Protocol Specify protocol used Vroot Veeder Handshaking Specify hardware handshaking None Poll Delay Time between internal polls 0 32000 seconds 1 second Example Client Side Connections Connections Port Baud P1 9600 Poll_Delay 0 100s Protocol Vroot Handshaking None Parity None 1 Not all ports shown are necessarily supported by the hardware Consult the appropriate Instruction manual for details of the ports available on specific hardware FieldServer Technologies 1991 Tarob Court Milpitas California 95035 USA Web www fieldserver com Tel 408 262 2299 Fax 408 262 9042 Toll_Free 888 509 1970 email support fieldserver com FS 8700 74 Veeder Root Driver Man
14. DA_101 i 0 rdoc Node_A 1 30 System Status Map_ Descriptors Map_Descriptor_Name fa_Array_Name Data_Array_Offset Function node_name Address Length Data_Type Sys_alms01 4 D _S1 0 passive Node_A 1 30 System Tank_Alms1 CIR 0 passive Node_A 1 30 Tank LiqSensor_Alm1 TA Li i 0 3 passive Node_A 1 k 30 Liquid Sensor VaporSens_Alm1 A_V1 0 passive Node_A 1 5 30 Vapor Sensor Input_Alm1 DA_ 1 0 passive Node A 1 3 30 Input VolLine_Alm1 DA_O1 0 f passive Node A 1 SO Volumetric Line GWater_Alms1 DA_G1 0 gt passive Node_A 1 Sk Groundwater Sensor TypeB_SensALm1 DA_B1 0 5 passive Node_A 1 7 30 Type B Sensor Univ_SensAlm1 DA_U1 0 A passive Node_A 1 30 Universal Sensor AutoDial_Alms1 DA_F1 3 0 A passive Node A 1 30 Auto Dial MechDisp_Alm1 DA_M1 0 a passive Node A 1 80 Mech Dispenser ElecDisp_Alm1_ DA_E1 0 passive Node A 1 i 30 Elec Dispenser Product_Alms1_ DA _P1 3 0 passive Node A 1 a 30 Product PressLine Alm1 DA_R1 0 i passive Node A 1 SO Press Line External_Alm1 DA_X1 0 passive Node A 1 A 305 External WPLLD_Alms1 DA W1 0 f passive Node A 1 30 WPLLD The length parameter tells the driver how much array space must be reserved for storing alarms for a given tank sensor input device These Map Descriptors are passive because they do not g
15. FieldServer Technologies A Sierra Monitor Company Driver Manual Supplement to the FieldServer Instruction Manual FS 8700 74 Veeder Root APPLICABILITY amp EFFECTIVITY Effective for all systems manufactured after May 1 2001 FS 8700 74 Veeder Root Driver Manual Table of Contents TABLE OF CONTENTS 1 Veeder Root Driver DeScription c seeceeeeesssseeeeeeeeeeeseseseeeeneeeeeeeseesensenneneeeeeeeeenseesees 3 2 Driver Scope OL SUPPLY 2iisc cits tes ted oie eke eh che ede Seed 4 2 1 Supplied by FieldServer Technologies for this drivef ccccseesseeeetesneeeeteenneeeeeesenees 4 2 2 Provided by the Supplier of 3 Party EQUIPMENT cscscscsesesecesesesesesesesesesesesesssesseeen 4 2 2 1 Required 3 Party Hardware isons cooctsse cists etatiaosleuginns Sarepdaay du sinhawnenataousntaed 4 3 Hardware Connections s ti2 52etc sss coedis eerdeele tate ile ahs etteee aceasta estes teed 5 4 Configuring the FieldServer as a Veeder Root Client cccccccesssseeeeeeeeeeeenseseeeeeeeeeeeeess 6 4 1 Data Aray S neea ge atthe dle tie E aac e Redon ee aden owen 6 4 2 Glient SIDE CONE CHONS roce e ae a aeaaea oil eats E E a bende ERATOR AiE 7 4 3 Client Side NO OS a e ce tae ae Ea len chs E E aR 8 4 4 Client Side Map Descriptors 3 scexe32tvecsesdsteeelcon ead ddocecucie evaesdrvedeasadoasetedenaderwsste eecniosslebangs 8 4 4 1 FieldServer Specific Map Descriptor Parameters ccccceceeeeeeeneeee
16. LLD Sensor Short Alarm Obsolete V19 16 PLLD Continuous Handle On Alarm 17 PLLD Fuel Out Alarm 18 PLLD Line Equipment Alarm OANDOAARW WPLLD Setup Data Warning WPLLD Gross Test Fail Alarm WPLLD Periodic Test Fail Alarm WPLLD Periodic Test Needed Warning WPLLD Periodic Test Needed Alarm WPLLD Sensor Open Alarm WPLLD Communications Alarm WPLLD Shutdown Alarm WPLLD Continuous Handle On Warning Obsolete V19 10 WPLLD Annual Test Fail Alarm 11 WPLLD Annual Test Needed Warning 12 WPLLD Annual Test Needed Alarm 13 WPLLD High Pressure Warning Obsolete V19 14WPLLD High Pressure Alarm Obsolete V19 15 WPLLD Sensor Short Alarm Obsolete V19 16 WPLLD Continuous Handle On Alarm 17 WPLLD Fuel Out Alarm 18WPLLD Line Equipment Alarm OANDAARWND Externally Detected Communication Alarm Communications Data Reception Timeout Communications Failed Checksum Communications Parity Error Modem Line Busy Modem No Answer Modem No Carrier Modem No Dial Tone Modem Modem Error 10 Modem Modem Not Responding 11 Modem Port Not Available 12 Polling Could Not Update Queue 13 Polling Invalid Data Type Requested OANDOAARWD FieldServer Technologies 1991 Tarob Court Milpitas California 95035 USA Web www fieldserver com Tel 408 262 2299 Fax 408 262 9042 Toll_Free 888 509 1970 email support fieldserver com FS 8700 74 Veeder Root Driver Manual Page 20 of 33 Appendix A 4 Security Codes
17. Milpitas California 95035 USA Web www fieldserver com Tel 408 262 2299 Fax 408 262 9042 Toll_Free 888 509 1970 email support fieldserver com FS 8700 74 Veeder Root Driver Manual Page 21 of 33 Appendix B Trouble Shooting and Driver Error Messages Driver statistics provide an effective troubleshooting method Generally RUINET may be used to monitor the driver stats The connection overview screen displays the number of messages amp bytes sent received as well as the number of errors As a point of departure e The number of messages received should equal the number of messages sent e The number of errors should be zero in a perfect world or should represent a small percentage of the total number of messages sent less then 5 e Several errors in consecutive messages may cause the FieldServer kernel to place the node offline in which case polling is slowed significantly until good communications are re established If the number of messages received is zero and the number of timeouts is equal to the number of messages sent then e The connection is bad Check the cables e The security configuration is invalid e The port settings are incorrect Check the baud rate If the number of messages received and the number of messages sent are roughly equal and the number of errors is small but the Data Arrays do not update then e If you are polling for System Status Check the 1 element of the Data Array associated
18. The RS 232 security code is an optional six digit code used to limit external serial access to the system for security purposes It can be set to any unique set of characters using either the front panel switches or the external communication interface setup commands The system will not respond to a command without the proper security code if the DIP switch is set to enable RS 232 security A four position DIP switch is located on the CPU board which is mounted in the right back of the console printer compartment The DIP switch is next to the battery switch The DIP switch enables the security code and the switch positions are assigned as follows Switch 1 Front Panel Setup Security Enable 2 RS 232 Security Enable 3 4 Unused If RS 232 security is enabled then the Route parameter must be specified for the node Set the route parameter equal to the security code Use a period to separate each digit of the code Example Security Code 234419 Set Route 2 3 4 4 1 9 Special Note for security codes with alphabetic characters Alphabetic characters cannot be directly specified in the route field They need to be specified as ASCII values Example Security Code 123abc Set Route 1 2 3 97 98 99 If the security feature has been disabled on the panel the set the route to zero as illustrated in the following CSV file fragment Nodes Node_Name Port Protocol Route Node_A P1 VEEDER 0 FieldServer Technologies 1991 Tarob Court
19. Veed Function Data_Type System1poll_1 DA SELF TEST 0 10 0s rdbc Node A 1 8g 0x901 Misc FieldServer Technologies 1991 Tarob Court Milpitas California 95035 USA Web www fieldserver com Tel 408 262 2299 Fax 408 262 9042 Toll_Free 888 509 1970 email support fieldserver com FS 8700 74 Veeder Root Driver Manual Page 29 of 33 Appendix C 5 Advanced Example 5 System Revision Level Report This example reads the System Revision Level from the Veeder Root Panel The result is stored in ascii using up to 100 consecutive array elements Use an array whose format is BYTE or STRING for this function The notes below explain how the data should be interpreted YYMMDDHHmmSOFTWARE nnnnnn vw rrrCREATED YY MM DD HH mm amp amp CCCC lt ETX gt Notes 1 YYMMDDHHmnm Current Date and Time 2 nnnnnn vwv Software version number ASCII text string 3 rrr Software revision level ASCII text string 4 YY MM DD HH mm Date and time of software creation 5 amp amp Data Termination Flag 6 CCCC Message Checksum Map_Descriptor Name Data_Array Name Data_Array_Offset Scan_interval Function node_name Address Length Veed_ Function Data_Type System1poll_1 DA REVISION 0 10 0s 5 rdoc_ Node A ies 100 0x902 Misc FieldServer Technologies 1991 Tarob Court Milpitas California 95035 USA Web www fieldserver com Tel 408 262 2299 Fax 408 262 9042 Toll_Free 888 509 1970 email supp
20. ak 21 Pressure Line Leak 21 Pressure Line Leak 21 Pressure Line Leak 21 Pressure Line Leak 21 Pressure Line Leak 21 Pressure Line Leak 21 Pressure Line Leak 21 Pressure Line Leak 21 Pressure Line Leak 21 Pressure Line Leak 21 Pressure Line Leak 21 Pressure Line Leak 21 Pressure Line Leak 21 Pressure Line Leak 26 Wireless PLLD 26 Wireless PLLD 26 Wireless PLLD 26 Wireless PLLD 26 Wireless PLLD 26 Wireless PLLD 26 Wireless PLLD 26 Wireless PLLD 26 Wireless PLLD 26 Wireless PLLD 26 Wireless PLLD 26 Wireless PLLD 26 Wireless PLLD 26 Wireless PLLD 26 Wireless PLLD 26 Wireless PLLD 26 Wireless PLLD 26 Wireless PLLD 99 Externally Detected Alarm 99 Externally Detected Alarm 99 Externally Detected Alarm 99 Externally Detected Alarm 99 Externally Detected Alarm 99 Externally Detected Alarm 99 Externally Detected Alarm 99 Externally Detected Alarm 99 Externally Detected Alarm 99 Externally Detected Alarm 99 Externally Detected Alarm 99 Externally Detected Alarm 99 Externally Detected Alarm Alarm Type amp Description PLLD Annual Test Fail Alarm PLLD Periodic Test Needed Warning PLLD Periodic Test Needed Alarm PLLD Sensor Open Alarm PLLD High Pressure Alarm Obsolete V19 PLLD Shutdown Alarm PLLD High Pressure Warning Obsolete V19 10 PLLD Continuous Handle On Warning Obsolete V19 11 PLLD Periodic Test Fail Alarm 12 PLLD Annual Test Needed Warning 13 PLLD Annual Test Needed Alarm 14PLLD Low Pressure Alarm 15 P
21. an error This message is printed once for each node which does not have a password This message provides confirmation that your configuration is not using a password and suggests that you check the panel configuration for the corresponding node to ensure that the security feature has been disabled Additional information is provided in Appendix A 4 This message may be safely ignored It does not indicate an error This message is printed once for each node which does have a password configured in the CSV file This message provides confirmation that your configuration is using a password and suggests that you check the panel configuration for the corresponding node to ensure that the security feature has been enabled Additional information is provided in Appendix A 4 VROOT 25 FYI Node lt s gt No password Is security disabled on panel VROOT 26 FYI Node lt s gt Password lt s gt Is security enabled on panel Appendix B 1 Driver Stats In addition to the standard FieldServer communication statistics described in the FieldServer User s Manual Veeder Root Driver can also expose some driver statistics by writing data to a Data Array A special Map Descriptor named vroot stats is required The following example shows how this special Map Descriptor can be configured You can copy this section of text directly into your CSV file Nodes Node_name Protocol null_node VRoot Data_Arrays D
22. arm9 Sensor Low Liquid Alarm Groundwater Sensor Alarm 10 Sensor Liquid Warning Sensor Setup Data Warning Sensor Fuel Alarm Sensor Out Alarm Sensor Short Alarm Sensor Water Alarm Sensor Water Out Alarm Sensor High Liquid Alarm Sensor Low Liquid Alarm 0 Sensor Liquid Warning gt OANOAKR WNP 2 Sensor Setup Data Warning 3 Sensor Fuel Alarm 4 Sensor Out Alarm 5 Sensor Short Alarm 6 Sensor Water Alarm 7 Sensor Water Out Alarm 8 Sensor High Liquid Alarm 9 Sensor Low Liquid Alarm 10 Sensor Liquid Warning Sensor Setup Data Warning Sensor Fuel Alarm Sensor Out Alarm Sensor Short Alarm Sensor Water Alarm Sensor Water Out Alarm Sensor High Liquid Alarm Sensor Low Liquid Alarm 0 Sensor Liquid Warning gt OMONOAAHKWND Autodial Setup Data Warning Autodial Failed Alarm Autodial Service Report Warning Autodial Alarm Clear Warning Autodial Delivery Report Warning akon N DIM Disabled Alarm DIM Communication Failure Alarm DIM Transaction Alarm AU BIR Setup Data Warning BIR Threshold Alarm BIR Close Shift Warning BIR Close Daily Warning AONI r PLLD Setup Data Warning PLLD Gross Test Fail Alarm N FieldServer Technologies 1991 Tarob Court Milpitas California 95035 USA Web www fieldserver com Tel 408 262 2299 Fax 408 262 9042 Toll_Free 888 509 1970 email support fieldserver com FS 8700 74 Veeder Root Driver Manual Page 19 of 33 Category 21 Pressure Line Leak 21 Pressure Line Le
23. ata_Array_Name Data_Format Data_Array_Length VROOT_STATS UINT32 1000 Map_ Descriptors Map_ Descriptor Name Data_Array_Name Node_name Length Data_Type VRoot stats VROOT_STATS null_ node 1000 Stats When the driver sees this Map Descriptor it uses the Data Array VROOT _ STATS in this example to store driver specific statistics Only one of these Map Descriptors may be specified per FieldServer This is a configuration error which can be eliminated by correcting an error in the CSV file and resetting the FieldServer FieldServer Technologies 1991 Tarob Court Milpitas California 95035 USA Web www fieldserver com Tel 408 262 2299 Fax 408 262 9042 Toll_Free 888 509 1970 email support fieldserver com FS 8700 74 Veeder Root Driver Manual The driver stores the following data VEED_MASTER_SENDS_MSG VEED_MASTER_SENDS_BYTES VEED_MASTER_TIMEOUT VEED_MASTER_STREAMING VEED_MASTER_RCVS_NAK VEED_MASTER_RCVS_CHECKSUM VEED_MASTER_RCVS_ PROTOCOL VEED_MASTER_COMPLETE_ERR VEED_MASTER_RCVS_MSG 10 VEED_MASTER_RCVS_ BYTES 11 VEED MASTER_IC_TIMEOUT 12 VEED MASTER_SEND_BAD_ MSG 13 VEED_STAT_MSG_IGNORED 14 VEED MASTER_RCV_BAD_FUNC_RESPONSE OONOAaARWND gt Appendix B 2 Table of Module Types Page 25 of 33 00 Not used OA Four Probe w Ground Temp Module 01 FourProbe Module OB Groundwater Sensor Module 02 Vapor Sensor Module OC Type A Sensor Module 03 Liquid Senso
24. chnologies 1991 Tarob Court Milpitas California 95035 USA Web www fieldserver com Tel 408 262 2299 Fax 408 262 9042 Toll_Free 888 509 1970 email support fieldserver com FS 8700 74 Veeder Root Driver Manual Page 23 of 33 Error Action Required VRoot 13 Err Device Rejected message Md lt s gt This message is generated the first time that the Error Statistic Function Error is produced This error can arise in several ways The firmware version of the Veeder Root device may not support the poll generated by the Map Descriptor The Veeder Root device may not have the tank sensor device specified or it may arise if the message received by the Veeder Root device is corrupted If there are a significant number of these errors then use Appendix A 2 to determine if the firmware supports the poll You can also check the devices configured against the address specified in the Map Descriptor VRoot 16 Err Array too short to store Md lt s gt Rqd d When this error is produced incoming data is being discarded and alarm or other data will not be updated There are a few variations on this message Some do not report the Rad length This message is produced as a run time error It may arise from a configuration error that has not been corrected Check for Error 7 messages If there are any correct the errors by editing the CSV file Then reset the FieldServer If the driver is still producing error 16 then y
25. chnologies 1991 Tarob Court Milpitas California 95035 USA Web www fieldserver com Tel 408 262 2299 Fax 408 262 9042 Toll_Free 888 509 1970 email support fieldserver com FS 8700 74 Veeder Root Driver Manual Page 22 of 33 Error Action Required VRoot 1 FYI The mapDesc called lt s gt is too short The length of the Map Descriptor used to expose driver statistics is too short Set the length to at least 600 VRoot 2 FYI You could have used a mapDesc called lt s gt to expose diagnostic info You can safely ignore this message It is a prompt Refer to Appendix B 1 VRoot 3 Err Data Type d is unknown Data will be discarded The driver has encountered a message reporting an alarm for an equipment category data type the driver does not recognize Take a port log and consult with FieldServer Technical Services VRoot 4 FYI If there is more than one VRoot node then connect each node to a dedicated port You may ignore this message if only one Veeder Root node is connected to the FieldServer If more than one node is connected then you must explicitly connect each node to a separate port Do this by editing the CSV file and then reset the FieldServer to eliminate the message The CSV fragment below illustrates explicit connection of a node to a port Connections Port Protocol PT cco VRoot Nodes Port Protocol N1__ P1_ Vroot VRoot 5 Err Da
26. d in Veeder Root Document 576013 635 Revision J The FieldServer emulates a Client The Veeder Root Serial Driver is a poll response driver Only one query or command can be processed at a time A limited set of the queries and commands defined in the protocol specification have been implemented The reason for the limitation is two fold Firstly not all commands queries will have any meaning to a downstream device as they are principally defined to configure the Veeder Root Device Secondly some commands return very complex data sets which cannot be processed in a method suitable for loading into the FieldServer s Data Arrays The driver is capable of exposing its communications statistics This can be useful if you wish to monitor them using a downstream device In this way you can ensure that you are using valid data and can generate alarms if communication problems arise FieldServer Technologies 1991 Tarob Court Milpitas California 95035 USA Web www fieldserver com Tel 408 262 2299 Fax 408 262 9042 Toll_Free 888 509 1970 email support fieldserver com FS 8700 74 Veeder Root Driver Manual Page 4 of 33 2 Driver Scope of Supply 2 1 Supplied by FieldServer Technologies for this driver FieldServer Technologies ae PART Description FS 8915 10 UTP cable 7 foot for RS 232 use FS 8917 01 RJ45 to DB25M connection adapter FS 8700 74 Driver Manual 2 2 Provided by the Supplier of 3 Party Equipme
27. dix C Advanced Map Descriptor Examples cccssseeceessseeeeeeeeseeeeeneeeeeeeeseseeeees 26 Appendix C 1 Advanced Example 1 Polling for Tank Sensor Input Relay Device Status 26 Appendix C 2 Advanced Example 2 Resetting Remote Alar cccccccccccsesssssseeeeeeeeees 27 Appendix C 3 Advanced Example 3 System Configuration cccccccccceeeeeeeeseeeeteeeeneeeees 27 Appendix C 4 Advanced Example 4 System DiaQnoOStiCs 2 ccccccececsseeeeteesneeeeeeenneeeeees 28 Appendix C 5 Advanced Example 5 System Revision Level R DOft ccccccecceeeeeees 29 Appendix C 6 Advanced Example 6 System Revision Level Report Il sccccccccceee 30 Appendix C 7 Advanced Example 7 Stick Height Report cccccccccsseeeeessteeeeeeeneeeees 31 Appendix C 8 Advanced Example 8 Active Alarm Report cccceccccctseeeeeeeseeeeeeeeeeeees 31 Appendix C 9 Advanced Example 9 Cleared Alarm Report ccccccccceccesesessssssesseeeeens 32 FieldServer Technologies 1991 Tarob Court Milpitas California 95035 USA Web www fieldserver com Tel 408 262 2299 Fax 408 262 9042 Toll_Free 888 509 1970 email support fieldserver com FS 8700 74 Veeder Root Driver Manual Page 3 of 33 1 Veeder Root Driver Description The Veeder Root Serial Driver allows the FieldServer to transfer data to and from devices over either RS 232 or RS 485 ports using Veeder Root protocol as define
28. ducing a poll number depending on Vapor Sensor whereas the other the data type Input Groundwater Sensor Type A Sensor Type B Sensor Universal Sensor Press Line WPLLD Relay example is passive relying on the response to a different poll FieldServer Technologies 1991 Tarob Court Milpitas California 95035 USA Web www fieldserver com Tel 408 262 2299 Fax 408 262 9042 Toll_Free 888 509 1970 email support fieldserver com FS 8700 74 Veeder Root Driver Manual Page 27 of 33 Appendix C 2 Advanced Example 2 Resetting Remote Alarms This example provides a write on change Map Descriptor used to send the Veeder Root device a remote alarm reset command When the value of the first element of the array named DA_COMMANDS changes value the driver will send the command The driver stores the Veeder Root System time in the array on completion of the command Map_Descriptor_ Name Data_Array_Name Data_Array_Offset Function node_name Address Length Data_Type Reset_Alms_01 DA COMMANDS 0 wrbx Node A 1 F M Remote Alarm Reset Appendix C 3 Advanced Example 3 System Configuration This example reads the configuration of the Veeder Root Panel The module type is stored in the location corresponding to the slot number Slot 1 s data is stored at index location 0 slot 2 at index location1 and if you define the DA_Byte_Name and DA_Float_Name arrays then the driver also stores the Power on Reset
29. eeeeneeeeeesseeeees 8 4 4 2 Driver Specific Map Descriptor Parameters 0 ccccceceeeeeeeeeeeeeeeeeeeeeeeneeeeeeenaaeeees 9 4 4 3 liming Pa ramete Soniodd ene stars icons a RE TEE NA ar E AG ainia 9 4 4 4 Map Descriptor Example 1 AlarmMS eeeeeeeeeeeeeeeeerereeeerirrrrsssssrrrrnrrssssrerrennna 10 4 4 5 Map Descriptor Example 2 Inventory esseeseeseeeeeeeertrieseerrirrrnssssstrrirrnnssssrerrennna 11 4 4 6 Map Descriptor Example 3 Most Recent Delivery Report ssseceeceeereeeeen 12 5 Configuring the FieldServer as a Veeder Root Driver Server ssssssnnssnnnnnnnennnnnnnnne 13 Appendix A Advanced Topics ccccccecessssseneeceeeesesenseseeeneeeeesesessseneeeeeoeessseseennsanennoeees 14 Appendix A 1 Data Type and Required Length ccsceseccceeeeeeeeeennnneeeeeeeeeetenenneneeeeeeeeens 14 Appendix A 2 Supported Functions vccPss ica 2es bead onnen secbacedentacbaternamebize vlad duace vrolende eecbidhee epee 15 Appendix A 3 Alai TV DCS scto2 cn shiloh i eh ae nen alegre aan 16 Appendix A 4 Security Codes i 2 232c 2icecpepeed otteee ech ea had nd ced ae haeeeie leading eat edc ipidaaneceays 20 Appendix B Trouble Shooting and Driver Error Messages cccsssseeeeeeeeeteeeeeeeeeees 21 Appendix Bd DVGrStAIS 16s taeka hace ea descents sazs tec o aa e O e E 24 Appendix B 2 Table of Module TyP0 s 1222 cccccseeeeseeeneencceneeenennenenonsaaseeeeeeeensnseneneeceenees 25 Appen
30. em status This returns the alarm states for the whole system which includes tank status information In this example we poll directly for the status of a particular tank Only the status of this tank is returned The length parameter reserves space in the array for the driver to store the possible alarm states for the tank The table in section 6 2 provides details of the alarm types The first element of the array is used to store an alarm summary state The array element is set non zero if there are any alarms and is set to zero if there are none The remaining array elements are set non zero based on the types of alarms active for the tank Example Tank 1 has two alarms 02 Tank Leak Alarm 05 Tank Low Product Alarm The driver sets array DA_TANK1_ALMS as follows Index 0 Value 1 Summary Index 2 Value 2 Leak Index 5 Value 5 Product Map_Descriptor Name Data_Array Name Data_Array Offset Function Scan_Interval node_name Address Length Data_Type DA_TANK1_ALMS 0 dbc 1 0s Node_A Tank1_01_ status 1 30 Tank The biggest difference between this Map The address must Descriptor and the one correspond to the tank Amount of array space Other possible values provided in example number in this required to store the are 4 4 4 is that this is an example or the sensor alarm types System active Map Descriptor input relay device Liquid Sensor pro
31. enerate messages They are used to store data returned by the system status poll Only the Map Descriptor used to generate the poll requires a scan interval The address must correspond to the tank sensor input device number When an alarm occurs for tank 1 the driver stores the alarm type by setting the array position corresponding to the alarm type to a non zero value as well as setting the first element of the reserved space non zero as a Summary See Table 6 3 for alarm type numbers and descriptions One Map Descriptor required for each 02 Tank Leak Alarm 05 Tank Low Product Alarm The driver sets array DA_T1 as follows Index 0 Value 1 Summary Index 2 Value 2 Leak Index 5 Value 5 Product FieldServer Technologies 1991 Tarob Court Milpitas California 95035 USA Web www fieldserver com Tel 408 262 2299 Fax 408 262 9042 Toll_Free 888 509 1970 email support fieldserver com FS 8700 74 Veeder Root Driver Manual Page 11 of 33 4 4 5 Map Descriptor Example 2 Inventory This example illustrates how you can poll for Tank Inventory Data You need one Map Descriptor for each tank Change the address to correspond to the tank number The Length parameter DOES NOT tell the driver how many tanks to process but it does tell the driver how much storage space to reserve for storing the inventory data The inventory data is stored as follows Index Contents 0 Product Code Example
32. ero If there are no active alarms then the array element is set to zero You need a number of passive Map Descriptors to store alarms for the tanks Sensor inputs devices just like in example 4 4 4 Map_Descriptors Map_ Descriptor Name Data_Array_Name Data_Array_ Offset Scan_Interval Function node_name Address Length Data_Type AlarmPoll 11 DA_ACTIVEALM 0 2 0s S rdbc Node _A 1 1 Active Alarm Report FieldServer Technologies 1991 Tarob Court Milpitas California 95035 USA Web www fieldserver com Tel 408 262 2299 Fax 408 262 9042 Toll_Free 888 509 1970 email support fieldserver com FS 8700 74 Veeder Root Driver Manual Appendix C 9 Advanced Example 9 Cleared Alarm Report Page 32 of 33 This example reads the Veeder Root Panel for cleared alarms If there are any cleared alarms then the 1 element of the Data Array is set non zero If there are no cleared alarms then the array element is set to zero You need a number of passive Map Descriptors to store the cleared alarm info for the tanks sensors inputs devices just like in example 4 4 4 The data is stored in the array specified using the DA_Byte_Name parameter of the passive Map Descriptors Map_Descriptor_Name AlarmPoll 11 Map_Descriptors Map_Descriptor_Name Sys_alms01 Tank_Alms1 Data_Array_Name DA_ACTIVEALM 0 2 0s Data_Array_Name DA_S1 DA_T1 Data_Array_Offset Scan_Interval DA_Byte_Name
33. nt 2 2 1 Required 3 Party Hardware PART DESCRIPTION Veeder Root Panel FieldServer Technologies 1991 Tarob Court Milpitas California 95035 USA Web www fieldserver com Tel 408 262 2299 Fax 408 262 9042 Toll_Free 888 509 1970 email support fieldserver com FS 8700 74 Veeder Root Driver Manual Page 5 of 33 3 Hardware Connections The FieldServer is connected to the Veeder Root Panel as shown below Configure the Veeder Root Panel according to manufacturer s instructions TLS 350 RJ45 CAT 5 Cable Connect to RS232 port P1 P8 Ni N2 ro 1 L 10 Base T RS232 ETHERNET CE FieldServer 8917 07 WIRE LIST FIELDSERVER FUNCTION COLOR CF CTS 05 BROWN Technologies ieldServer z222 RX 02 WHITE DSR 08 YELLOW GND 07 GREEN DTR 20 BLACK VEEDER ROOT RTS 06 ORANGE TX 03 BLUE CONNECTION DIAGRAM BASE NAME DATE 1 17 02 FILE NAME FS T28700 74 VSD BY MN FieldServer Technologies 1991 Tarob Court Milpitas California 95035 USA Web www fieldserver com Tel 408 262 2299 Fax 408 262 9042 Toll_Free 888 509 1970 email support fieldserver com FS 8700 74 Veeder Root Driver Manual Page 6 of 33 4 Configuring the FieldServer as a Veeder Root Client For a detailed discussion on FieldServer configuration please refer to the FieldServer Configuration manual The information that follo
34. ort fieldserver com FS 8700 74 Veeder Root Driver Manual Page 30 of 33 Appendix C 6 Advanced Example 6 System Revision Level Report Il This example reads additional System Revision Level data from the Veeder Root Panel The result is stored in ascii using up to 100 consecutive array elements Use an array whose format is BYTE or STRING for this function The notes below explain how the data should be interpreted i90500Y YMMDDHHmmSOFTWARE 346abb Tw rrrCREATED YY MM DD HH mmnnAABBCCDDEEFFGGHHIIJJS MODULE nnnnnn vw r YYMMDDHHmzn Current Date and Time 346 Software Base number fixed a Platform 0 Standard CPU PLLD only 1 Enhanced CPU 2 Unused 3 Enhanced CPU 16 Tank 4 Standard CPU without PLLD amp WPLLD 5 Standard CPU WPLLD only bb Version level egg version 15 T Software Type 1 Real 2 Demo 3 IFSF vv Language rrr Revision level e g revision AX1 YY MM DD HH mm Date and time of software creation nn number of 2 byte values to follow Hex AA PERIODIC IN TANK TESTS 00 DISABLE 01 ENABLE BB ANNUAL IN TANK TESTS 00 DISABLE 01 ENABLE CC CSLD 00 DISABLE 01 ENABLE DD BIR 00 DISABLE 01 ENABLE EE FUEL MANAGER 00 DISABLE 01 ENABLE FF PRECISION PLLD 00 DISABLE 01 ENABLE GG TANKER LOAD 00 DISABLE 01 ENABLE HH 0 2 GPH PLLD 00 DISABLE 01 ENABLE Il PRECISION PLLD ON DEMAND 00 DISABLE 01 ENABLE
35. ou should report this to FieldServer support Provide a copy of your configuration file and a port log to assist in the diagnosis of this error VRoot 17 Err Array too short to store Md lt s gt ByteArray This error is similar to 16 except that it applies to the array named in the DA_Byte_Name parameter for the Map Descriptor VRoot 18 Err Array too short to store Md lt s gt Float Array This error is similar to 16 except that it applies to the array named in the DA_Float_Name parameter for the Map Descriptor VRoot 19 Err Cant process msg type x You cannot take any corrective action to eliminate this error Report the message to FieldServer support It will assist in the diagnosis of the error if you can take a port log and provide a copy of your CSV file VRoot 20 FYI Incoming data is being abandoned Func x DT lt S gt Addr d This message is a warning It indicates that a response to a poll contains data for which a Map Descriptor cannot be found to store the data For example The response to poll for System Status returns an alarm for Liquid Sensor 3 but you have not defined a Map Descriptor for Liquid sensor 3 You may be able to use the Data Type and the Address to determine what kind of Map Descriptor is required If however you are satisfied that you have Map Descriptors for the data of interest to you then you may safely ignore this message VRoot 21 Err Md lt s gt
36. r Module OD Remote Display Module 04 FourRelay Module 05 I O Combo Module 06 Printer Module 07 RS 232 Module 08 Modem Module 09 Volumetric Line Leak Module 10 Type B Sensor Module 1A Pressure Line Leak Sensor Module 11 Universal Sensor Module 1B Pressure Line Leak Controller Module 12 Fax Modem 1785 Module 1D Remote Printer Module 13 Remote Local Printer Module 1E External Fax Modem Module 14 Pump Sensor Module 1F RS 485 Module 15 European RS 232 Module 17 EightProbe Module 18 Mechanical Dispenser Interface Module 19 Electronic Dispenser Interface Module 20 Wireless PLLD AC Interface Module 21 Wireless PLLD Communications Module 22 Wireless PLLD Controller Module 23 Hughes Satellite J Box Module 24 Fax Modem 1786 Module 25 Serial Satellite Module 26 Three Probe Three Liquid Sensor Module 27 Three PLLD Sensor Module FieldServer Technologies 1991 Tarob Court Milpitas California 95035 USA Web www fieldserver com Tel 408 262 2299 Fax 408 262 9042 Toll_Free 888 509 1970 email support fieldserver com FS 8700 74 Veeder Root Driver Manual Page 26 of 33 Appendix C Advanced Map Descriptor Examples Appendix C 1 Advanced Example 1 Polling for Tank Sensor Input Relay Device Status In section 4 4 1 we polled for the syst
37. ta Type invalid for this driver Md lt s gt VRoot 6 Err No Default Poll Function for this data type Md lt s gt The Data types must be spelled spaced and punctuated exactly as in Appendix A 1 Some data types require an addition Map Descriptor parameter VEED_Function to be specified Read the notes example in the Advanced Topics section to determine the requirements to correct this error VRoot 7 Err Length too short Rad d Md lt s gt 5 The message reports the offending Map Descriptor and the number of array elements required Adjust the length parameter accordingly Ensure that the new length coupled with the offset fits in the array size VRoot 11 Err Command 0x54 cannot specify all tanks For the Data Type or Veed_Function specified the address may not be set to zero You need one Map Descriptor per tank sensor input device There are a few variations of this error message each reporting the offending function VRoot 12 Err Command 0x54 Bad confirmation code You cannot take any corrective action to eliminate this error Report the message to FieldServer support It will assist in the diagnosis of the error if you can take a port log There are a few variations of this error message each reporting the offending function This is a configuration error which can be eliminated by correcting an error in the CSV file and resetting the FieldServer FieldServer Te
38. the address to correspond to the tank number The Length parameter DOES NOT tell the driver how many tanks to process but it does tell the driver how much storage space to reserve for storing the delivery data The delivery data is stored as follows This function corresponds to the function 20C in the Veeder Root protocol specification Index Contents Product Code Number of Deliveries Start Time Stop Time Starting Volume Starting TC Volume Starting Water Starting Temp Ending Volume Ending TC Volume 10 Ending Water 11 Ending Temp 12 Starting Height 13 Ending Height SCHNAAKRWMYH gt S Map_Descriptor_ Name Data_Array_Name Data_Array_Offset Function Scan_Interval node_name Address Length Data_Type DeliveryPoll01 DA_DELIVERY 0 rdbc 1 0s Node_A 1 30 In Tank Delivery FieldServer Technologies 1991 Tarob Court Milpitas California 95035 USA Web www fieldserver com Tel 408 262 2299 Fax 408 262 9042 Toll_Free 888 509 1970 email support fieldserver com FS 8700 74 Veeder Root Driver Manual Page 13 of 33 5 Configuring the FieldServer as a Veeder Root Driver Server The server functionality of this driver was developed for testing the Client Its features are not documented and not intended for end users It may be possible to extend and document the server at the request of an end user FieldServer Technologies 1991 Tarob Court Milpitas California 95035 USA Web www fieldserver com Tel 408 262 2299 Fax
39. the hardware Consult the appropriate Instruction manual for details of the ports available on specific hardware FieldServer Technologies 1991 Tarob Court Milpitas California 95035 USA Web www fieldserver com Tel 408 262 2299 Fax 408 262 9042 Toll_Free 888 509 1970 email support fieldserver com FS 8700 74 Veeder Root Driver Manual Page 9 of 33 4 4 2 Driver Specific Map Descriptor Parameters Column Title Function Legal Values One of the node names Node Name Name of Node to fetch data from specified in Client Node Descriptor above System Tank Liquid Sensor Vapor Sensor Input Volumetric Line Groundwater Sensor Type B Sensor Universal Sensor Auto Dial Mech Dispenser Elec Dispenser Product Press Line External WPLLD Data_Type Data type The address is used to specify the Tank Sensor Input Relay Number to be used in the poll For some data types the address has no meaning and should be set to 1 Veeder Root Tanks Sensors are numbered from 1 The maximum tank number is 12 and the maximum sensor number if 64 Address 0 1 2 3 When zero is used as the value of the address then in most cases the driver polls for all Tanks Sensors belonging to that data type This is discussed in the Advanced Topics Section Length of Map Descriptor The length is used to tell the driver how many elements of the Data Array are Length under the control of the Map Descriptor
40. tware Module Warning 1 System 11 Tank Test Shutdown Warning 1 System 12 Protective Cover Alarm 1 System 13 BIR Shift Close Pending 1 System 14 BIR Daily Close Pending 1 System 15 PC H8 Revision Warning 1 System 16 System Self Test Error 1 System 17 System Clock Incorrect Warning 1 System 18 System Device Poll Timeout Tank 1 Tank Setup Data Warning Tank 2 Tank Leak Alarm Tank 3 Tank High Water Alarm Tank 4 Tank Overfill Alarm Tank 5 Tank Low Product Alarm Tank 6 Tank Sudden Loss Alarm Tank 7 Tank High Product Alarm Tank 8 Tank Invalid Fuel Level Alarm Tank 9 Tank Probe Out Alarm Tank 10 Tank High Water Warning Tank 11 Tank Delivery Needed Warning Tank 12 Tank Maximum Product Alarm Tank 13 Tank Gross Leak Test Fail Alarm Tank 14 Tank Periodic Leak Test Fail Alarm Tank 15 Tank Annual Leak Test Fail Alarm Tank 16 Tank Periodic Test Needed Warning Tank 17 Tank Annual Test Needed Warning Tank 18 Tank Periodic Test Needed Alarm Tank 19 Tank Annual Test Needed Alarm Tank 20 Tank Leak Test Active Tank 21 Tank No CSLD Idle Time Warning Tank 22 Tank Siphon Break Active Warning Tank 23 Tank CSLD Rate Increase Warning Tank 24 Tank AccuChart Calibration Warning Tank 25 Tank HRM Reconciliation Warning Tank 26 Tank HRM Reconciliation Alarm PNNNNNNNNNNNNNNNNNNNNNNNNDND PP FieldServer Technologies 1991 Tarob Court Milpitas California 95035 USA Web www fieldserver com Tel 408 262 2299 Fax 408 262 9042 Toll_Free 888 509 1970 email
41. ual Page 8 of 33 4 3 Client Side Nodes Section Title Nodes Column Title Function Legal Values Up to 32 alphanumeric Node_Name Provide name for node characters Node_ID This commonly used parameter is not required for this driver Protocol Specify protocol used Vroot Veeder Specify which port the device is connected Port to the FieldServer P1 P8 R1 R2 Only one node per port This parameter is only required if security is enabled on the Veeder Root device In this case the route must be set to a b c d e f Route contain the 6 digits that form the security code a b c d e f must be decimal digits in the range 0 to 9 Example If the security code is 556741 then enter route as 5 5 6 7 4 1 Example Client Side Nodes Nodes Node_ Name Protocol Port VR_Node1 Vroot P1 4 4 Client Side Map Descriptors 4 4 1 FieldServer Specific Map Descriptor Parameters Column Title Function Legal Values Up to 32 alphanumeric Map_Descriptor_Name Name of this Map Descriptor characters Name of Data Array where One of the Data Array names Data_Array_Name data is to be stored in the from Data Array section FieldServer above 0 to maximum specified in Data Array section above RDBC WRBC WRBX Data_Array_Location Starting location in Data Array Function of Client Map Function Descriptor Not all ports shown are necessarily supported by
42. with the poll Map Descriptor The driver sets or clears the element as a summary alarm state for the Veeder root device Check that the data age is no more than the scan interval If the number of messages ignored is non zero then this indicates that some data cannot be stored and is being discarded Generally this arises when the driver cannot find an appropriate Map Descriptor to store data received in response to a poll for composite data such as system status For example A system alarm occurs but you have not defined Map Descriptors to store system alarms or an alarm occurs for a sensor for which you have not defined a Map Descriptor You can monitor the error log to see if the driver has reported any errors or important information These messages arise in two ways Firstly there are configuration errors and warnings which arise from the way that the CSV file has been configured You should eliminate all these errors before putting your system into production Secondly there are errors that arise from some run time condition Many of these errors are produced in the error log only once even though they may be produced over and over The driver suppresses repetition so that the log does not overflow or hide other meaningful information Messages proceeded with an are ones where multiple occurrences are suppressed by the driver Thus the error may occur continuously but only one occurrence will be reported in the error log FieldServer Te
43. ws describes how to expand upon the factory defaults provided in the configuration files included with the FieldServer This section documents and describes the parameters necessary for configuring the FieldServer to communicate with a Veeder Root Device The configuration file tells the FieldServer about its interfaces and the routing of data required In order to enable the FieldServer for Veeder Root Driver communications the driver independent FieldServer buffers need to be declared in the Data Arrays section the destination device addresses need to be declared in the Client Side Nodes section and the data required from the Servers needs to be mapped in the Client Side Map Descriptors section Details on how to do this can be found below Note that in the tables indicates an optional parameter with the bold legal value being the default 4 1 Data Arrays Section Title Data_Arrays Column Title Function Legal Values Data_Array Name Provide name for Data Array SAE ae FLOAT BIT UInt16 SInt16 Packed_Bit Byte Packed Byte Swapped_ Byte Provide data format Each Data Array can only take on one format Number of Data Objects Must be larger than the data storage area Data_Format Daa Array engih required for the data being placed in meee this array Example Data Arrays Data_Arrays Data_Array_Name Data_Format Data_Array_Length DA_AI_01 UInt16 200 D

FS-8700-74 Veeder-Root - Chipkin Automation Systems

Contents

Download Pdf Manuals

Related Search

Related Contents