GTE Omni Si Database Technical Practices Manual
Have a look at the manual GTE Omni Si Database Technical Practices Manual online for free. It’s possible to download the document as PDF or print. UserManuals.tech offer 3 GTE manuals and user’s guides for free. Share the user manual or guide on Facebook, Twitter or Google+.
![Page 682
TL-130200-1001Table 3.1FMS StatusCode and Explanation (Continued
FMS STATUS
CODEEXPLANATION
22Iwrite past physical EOF attempted
23seek past physical EOF attempted
24record sizes not equal
25files open on device
26FID not seized
. 1
27] access is invalid
30device not ready
31device I/O error
32Idevice write protected
34not allowed on mounted disk
35no device attached
36device is private
40invalid commander number
126command awaiting executionM-l 06command executing
61875210](http://img.usermanuals.tech/thumb/5723/83626/w64_fujitsu-omni-si-gte-database-maintenence_d-681.png "Page 682
TL-130200-1001Table 3.1FMS StatusCode and Explanation (Continued
FMS STATUS
CODEEXPLANATION
22Iwrite past physical EOF attempted
23seek past physical EOF attempted
24record sizes not equal
25files open on device
26FID not seized
. 1
27] access is invalid
30device not ready
31device I/O error
32Idevice write protected
34not allowed on mounted disk
35no device attached
36device is private
40invalid commander number
126command awaiting executionM-l 06command executing
61875210")
TL-130200-1001File ManagementWhen loading the FMS files into the system, certain errors may System (FMS) Errorsbe received. For example,“FMS error 14” is received. This means that FILE D is not available for creation, for opening, or for seizure. Refer to Table 3.1 for status code and explanation. Table 3.1FMS StatusCode and Explanation EXPLANATIONfile is not open for output 52108187M-l 05
TL-130200-1001Table 3.1FMS StatusCode and Explanation (Continued FMS STATUS CODEEXPLANATION 22Iwrite past physical EOF attempted 23seek past physical EOF attempted 24record sizes not equal 25files open on device 26FID not seized . 1 27] access is invalid 30device not ready 31device I/O error 32Idevice write protected 34not allowed on mounted disk 35no device attached 36device is private 40invalid commander number 126command awaiting executionM-l 06command executing 61875210
SYSTEM MAINTENANCE GENERAL PRINCIPLES. . Preventive Maintenance System Voltage Checks System Operation Checks Spare Cards Quick Reference Chart 5210TL-130200-1001 4.0 Maintenance commands are input via the maintenance terminal to designate particular parts of the system hardware as “maintenance busy” so that system software will not try to use that hardware during system operation. Hardware is out of service when designated as maintenance busy. That piece of hardware becomes available for maintenance purposes and can be physically removed from the system and replaced with a spare card. This will not cause interruption of service. The maintenance terminal is also used to place parts of the system back into service. However, the part is tested by the system before it is placed back into use. When testing is completed, the system outputs response codes to any attempts to place equipment into service. A response code is outputted if the attempt is successful, or if the equipment fails system testing and is not placed into service. The responses are an aid to maintenance and troubleshooting. 4.1 The system does not require regularly scheduled preventive maintenance. Cabinet cooling is based on natural convection with no fans or air filters to clean or replace. 4.2 Voltage checks are performed as part of troubleshooting and are discussed in the TL-130300-1001. Voltage adjustments are set at the factory and should not be altered as a part of field maintenance. Battery packs are checked during installation and are charged by the system. 4.3 System operation checks simply use the standard functions of the system to ensure proper operation. Checks are usually performed when installation is completed and, selectively, at the conclusion of a corrective maintenance action. Refer to TL-130100-l 001 for detailed operating procedures when attempting to make particular types of calls and execute particular system features. 4.4 Spare cards should be tested for correct operation after the system is completely tested and operational. To test the spare cards, replace a working card with an identical spare and test the feature or function associated with it. Once the function of the spare has been confirmed, remove it and replace the original. 4.5 Table 2.1 is a listing of the fault codes and functions associated with the system.M-l 07
TL-130200-1001Attendant Console4.6 The memory of each CEC provides an area called the fault Code Display Faultlog which records system faults. It records the last 32 faults detected. When a fault is detected, the ALARM LED on each Attendant Console flashes, indicating that a fault has occurred. Each console displays all faults reported in the fault log independently of the other consoles in the system. All of the faults listed on the fault log are displayed by repeated depressions of the ALARM pushbutton. If all faults have been displayed at an Attendant Console, an additional depression ofthe ALARM pushbutton causes the station number display to go off and the ALARM LED to stop flashing, unless a MAJOR alarmexists which will cause the ALARM LED to light steady. A steady ALARM LED should cause the Attendant to call for maintenance assistance. Depressing the ALARM pushbutton associated with the flashing LED displays a three- or four-digit number in the stationnumber display on the Attendant Console. This display is interpreted as follows:l The first two digits indicate the fault type. Refer to Table 4.1 l The third digit indicates in which equipment complex the fault occurred. Refer to Table 4.1. * If provided, the fourth digit gives additional information. Refer to Table 4.1. M-l 0881875210
TL-130200-1001 Table 4.1Attendant Console Fault Log Decoding Summary-..FUNCTIONATENDANT CONSOLE STATIONS NUMBER DISPLAY FAULT TYPE SELECTED OPTIONAL DIGIT DIGIT 1DIGIT 2DIGIT 3 + DIGIT 4 CEC block-parity error CEC dynamic-memory failure CEC network read-after-write-error CEC-PEC common memory read-after-write-error CEC total communication failure CEC single communication failure CEC system network test error Preloading test failure Peripheral Equipment Complex (PEC) Network test error PEC directive test error PEC directive hopper full PEC illegal event error PEC read-in after-write channel memory PEC self-test error PEC lo-ms test error Tl alarm fault CEC lo-ms interval timer failure CEC alarm fault or PEC alarm fault CEC memory block-parity error CEC preloading memory failure Peripheral equipment data hopper failure Peripheral equipment data directive hopper error Spare Real-time clock failure Power failure Station status disk backup failure CAS Main/ACD agent data link error CAS Main/ACD message queue error Attendant Console recovery data check error PEC ODDB backup failure CIp card failure CIp port failure Remote FADS data transmission error Remote FADS reporting error * Not used + Demarcation unit; See CEC Fault Log 0 0 0 0 0 0 0 0 0 0 1 1 1 1 1 1 1 1 1 1 2 2 2 2 2 2 2 2 3 3 3 3 3 3 9 0 1 2 3 4. 5 6 7 8 9 0 1 2-4 * * * *Channel no. Channel no. * * * * * * * * * * * * * *PEC no. PEC no. Peripheral Equipment * ** * *Console no. *Card no. Port no.
TL-130200-1001Fault Code 00Description: Block Parity FailureWhen a program is loaded into the system, the CPU85 willgenerate block parity for each 256 bytes of instruction data and static data. This is done by an exclusive OR of the data table. Periodically, the CPU85 will recalculate the block parity andcompare it with the value calculated earlier (detect memory failures and data mutilation). . .Register Data as System Prints:CECO CECO Fault 00 B C D E H I Test FailureAddress of Faulty Byte IFailing I 00 01 02 03 04 05 06 07 Software Pace: = Instruction Page 0 = Instruction Page 1 = Data Page 0 = Data Page 1 = Instruction Page 2 = Instruction Page 3 = Data Page 2 = Data Page 3 Fault Resolution Steps: 1.Remove fuse on battery pack. 2.Power down - turn off main circuit breaker at rear of OMNI SI cabinet. 3.Remove and replace Ml MB in Y/01, FB-17314-1A (check strapping). 4.Power up and reload system - depress reset on PSUPY card. 5.Monitor PSUPY in P/O1 for ASW LED to light. 6.If fault occurs, power down and reinstall original MlMB card, and replace the MPG16 card. 7.If fault is still present, read the data for the pre-loading, memory test (see disk handling and and Fault Code 19) andreplace the Ml MB card. 8.Power up and reload syste. 9.Monitor PSUPY in P/O1 for ASW LED to light.10. Replace fuse in battery pack. M-11081875210
TL-130200-1001 FAULT CODE 00 POWER DOWN SYSTEM1R&R Ml MB IN Y/O1 FB-17314 (Check Strapping) POWER UPAND RELOAD IIYESPOWER DOWN &REINSTALL ORIGINAL Ml MB CARD 1R&R MP85 IN Y/O2 FB-17213 (Check Strapping) 1 POWER UPAND RELOAD 1MONITOR PSUPY FOR“ASW” TO LIGHT f REPLACEBATTERY PACK FUSE 15210 8187M-111
TL-130200-1001Fault Code 01Description: Dynamic RAM MemoryThe system tests dynamic memory. A block of five bytes is put into a temporary storage area. A series of test patterns is read into the area of memory being tested and then verified. The data is returned to its original location and the test advances to the next five bytes of dynamic memory (interrupts are disabled during this test). . . Register Data as System Prints:CECO CECO Fault 01 B C D E H L 00 00 \02 xx vTest Failure T Address of Faulty Byte Failing1 Software Page: 00= Instruction Page 0 01=InstructionPage1 02=Data Page0 03= Data Page1 04=InstructionPage2 05=Instruction Page3 06= Data Page2 07 zData Page3 M-112 1 Fault Resolution Steps: 1. 2. 3. 4. 5. 6. 7. 8. 9. 10. ai87 Remove fuse on battery pack.Power down - turn off main circuit breaker at rear of OMNI SI cabinet.Remove and replace Ml MB in Y/01, FB-17314-A (check strapping).Power up and reload system - depress “reset“ on PSUPY card. Monitor PSUPY in P/O1 for ASW LED to light.If fault recurs, power down and reinstall original Ml MB card and replace the MPG16 card. Remove and replace MP85 in Y/02, FB-17213-A (check strapping). Power up and reload system. Monitor PSUPY in P/O1 for ASW LED to light. Replace fuse in battery pack.
: ITL-130200-1001 FAULT CODE 01 REMOVE BATTERY PACK FUSE cPOWER DOWN SYSTEM I 1 IR&R Ml MB IN Y/O1 FB-17314 (Check Strapping) 4 1POWER UPAND RELOAD YESPOWER DOWN &REINSTALL ORIGINAL Ml MB CARD 1R&R MPG16 IN Y/O2 FB-17213-BOA (Check Strapping) 1 POWER UPAND RELOAD 1 MONITOR PSUPY FOR “ASW” TO LIGHT5210 8l87M-113
TL-130200-1001Fault Code 02Description: Control MemoryWhen a byte of data is written into the network memory, it is Read-After-Writeimmediately read back and verified. Failure . . .M-114 Register Data as System Prints:CECO CECO Fault 02 6 C D E H L O0 O0 Y xx =-I-- Data iAddress of WrittenFaulty ByteDataRead JFault Resolution Steps: 1.Power down - turn off main circuit breaker at rear of OMNI SI cabinet- 2.Remove and replace EPCMN in Y/09, FB-17217-A (check strapping). 3.Power up system. 4.Monitor PSUPY in P/O1 for ASW LED to light approximately 15 seconds to warm site. 5.If fault recurs, power down and reinstall original EPCMN card. 6.Remove and replace INCKS in Y/l 1 (check strapping). 7.Power up system. 8.Monitor PSUPY in P/O1 for ASW LED to light. 9.If fault recurs, power down and reinstall original INCKS card. 10. Remove battery pack fuse. 11. Remove and replace MPG1 6 in Y/02, FB-17213-BOA(check strapping). 12. Power up and reload system - depress reset on PSUPY card. 13. Monitor PSUPY in P/O1 for ASW LED to light. 14. Replace battery pack fuse. 81875210