Ошибки блоков VDB

Данные ошибки касаются всех блоков VDB (VDB-XP, VDB-MS)

Error list for LoadPrg 4.0

Error Number: Maning:

Error 1 Program Check Fail (1)

Error 2 Program Check Fail (1)

Error 3 Program Check Fail (1)

Error 4 Program Check Fail (1)

Error 5 Program Check Fail (1)

Error List for GamePrg 4.2e

Test TV Error Number: Meaning:

Error 200 No Communication with TVision (2)

Error 200/1 Unexpected Communication character (2)

Error 200/2 Wrong Character Communication with TVision (2)

Error 200/3 TVision seems okay (2) Error 200/4 Six Seems okay (2)

Error 200/5 Six Communications fail (2)

Error 201 Wrong Character on Tele.bin files (1)

Error 202 TVision Communication failure (3)

Error 203 Camera Fail Check. (4) (If camera is on each lane, error is for left lane)

Error 204 Check Camera right lane (4)

Error 205 TVision Communication failure (3)

Error 206 Wrong header on Tele.bin file (1)

Error 207 Impossible to communicate with PSi (5)

Error 208 Impossible to communicate with F-Box (6)

Error 209 Old F-Box version (version 1.0) (7)

Error 210 TVision hardware not compatible (8)

Error 211 F-Box strike time not valid

Startup Error Number: Maning:

Error 220 Program check Fail (1)

Error 221 Program check Fail (1)

Error 222 VDB Hardware Fail

Error 223 Program check Fail (1)

Error 224 VDB Hardware Fail

Error 225 HiMem fail (3)

Error 226 Alone Fail (10)

Error 227 VDB Hardware Fail

Error 228 Program check Fail (1)

Error 229 Software configuration not valid (8)

Error 230 Bad Q-View file Check (11)

Error 231 VDB98 Hardware Fail

Error 232 Bad Q-Surf file Check (11)

Struct Error Number: Maning:

Error 240 Wrong size of data files (1)

Error 241 Data files check fails (1)

Error 242 File maschera.bin missing

KbdData Error Number: Meaning:

Error 250 Wrong size of keyboard files (1)

Error 251 Keyboard files check fail (1)

Runtime Error Number: Meaning:

Error 1000 Internal Error (8)

Error 1001 Wrong LCOM data format (8)

Error 1002 Bowler terminal board is connected to the LCOM line but the program on the VDB is not configured to use it (9)

Error 1003 Keyboard buffer full (8)

Error 1004 Internal Error (8)

Error 1005 Internal Error (8)

Error 1006 Internal Error (8)

Error 1007 Front Desk is opening a lane in bowler keyboard mode, but the lane is not configured to use it (9)

Error 1008 Stack overflow (8)

Error 1009 Internal Error (8)

Error 1010 LCOM Data error (8)

Error 1011 Psi data format error (8)

Error 1012 Error received league data (8)

Error 1013 Wrong League Handicap mode (8)

Error 1014 Divide by 0 (8)

Error 1015 Heap request error (8)

Error 1016 Code size error (8)

Error 1017 Wrong Animation command (8)

Error 1018 Missing Animation Picture (8)

Error 1019 Animation internal Error (8)

Error 1020 Missing Animation Picture (8)

Error 1021 Animation internal Error (8)

Error 1022 Animation internal Error (8)

Error 1023 Animation internal Error (8)

Error 1024 Animation internal Error (8)

Error 1025 Missing Animation Sound (8)

Error 1026 HxHeap request error (8)

Error 1027 HxHeap init error (8)

Error 1028 Heap init error (8)

Error 1029 Lucky Draw internal error (8)

Error 1030 Sound internal error (8)

Error 1031 Internal Error (8)

Error 1032 Internal Error (8)

Error 1033 VDB Alone hardware Fail

Error 1034 VDB Alone hardware Fail

Error 1035 Video Mode Internal error (8)

Error 1036 31k Internal Error (8)

Error 1037 Internal Error (8)

Error 1038 Internal Error (8)

Error 1039 Internal Error (8)

Error 1040 Internal Error (8)

Error 1041 Internal Error (8)

Error 1042 Internal Error (8)

Error 1043 Internal Error (8)

(1) Error checking the program/data in battery back upped ram: reload the program on VDB

(2) LCOM communications failure: VDB is not able to communicate properly with the TVision board. Wiring Problem or defection of one of the LCOM devices.

(3) Unusual kind of Problem; retry by switching the VDB off and on again.

(4) TVision board not able to work with camera. Problem is usually in the wiring between TVision board and camera.

(5) Lane Configuration needs the presence of a Psi box (String machine ad Gs## interface) but it is impossible to communicate with it. If, the Psi is properly installed, the cause should be wiring problem or a defection of one of the LCOM devices.

(6) Lane configuration needs an F-Box (Enhanced pinsetter interface) but it is impossible to communicate with it.

(7) Microprocessor on the F-Box is an old version, and the lane cannot be configured to handle the strike signal.

(8) Internal errors should be made known to Qubica. Restart the program switch the VDB off and on again.

(9) Is the Front Desk program configured to use the bowler keyboard? Check this condition and reload the programs on the VDB.

(10) To remove the Error, set a valid VDB address.

Hard Drive – Initial Error during Boot.