|
Addtime：2013-07-22
1、Terminal Troubleshooting | 1.Phenomenon | Reason | Workaround | | Handheld terminal garbled | Dead battery causes the parameter reset | Please re-set the font number“6” | | Font file is missing | Please re-upload the font file | | Handheld terminals andPCInability to communicate | Handheld terminal, transfer software, there is no uniform rate of cradle | Need to reset | | Handheld terminal parameters reset | | Communications software problems path settings and other parameters | | Handheld terminal could not correctly placed in the cradle, line or connection problems. | 1． Check the connections. 2． Hardware problems, please contact Victoria deep service. | | Handheld terminal hardware failure | | Cradle hardware failure | | Handheld terminal and the terminal can not communicate | Handheld terminal, the cradle, terminal velocity is not uniform | Reset | | Handheld terminals and terminal parameter settings problem | | Line connection problems | Reconnect,Hardware problems, please contact Victoria deep service | | Hardware failure | | Can not run the program | Open the program displays "...... illegal ......" | Please contact after-sales service to solve deep-dimensional | | Handheld terminal can not boot | Dead battery. | Replacing the battery | | Hardware problems | If you still can not boot the suspect is a hardware failure, please send to the dimensional deep technology overhaul |
2、Cradle Troubleshooting| 1Symptom | Cradle state | Cradle POWER lamp is not lit, DATA light does not shine, LINE lamp is not lit. | | Logger status | After some time, the collector exit communication status, suggesting that 'communication failure'. | | Production System Status | After some time, quit the communication status, suggesting that 'timeout did not receive the information.' | | Reason | Cradle's power supply or the cradle itself is not a circuit problem | | Workaround | 1, check the cradle's power connection is normal, if not connected then connected to the power supply. 2 Check the power is turned on, if not then turn on the power. 3, check the power connection socket has power. 4, if the above steps have been tested normal, replace a power supply or cradle. | | | | 2Symptom | Cradle state | Red cradle POWER, DATA light does not shine, LINE lamp is not lit. | | Logger status | After some time, the collector exit communication status, suggesting that 'communication failure'. | | Production System Status | After some time, quit the communication status, suggesting that 'timeout did not receive the information.' | | reason | Collector is not placed in the cradle good. | | Workaround | The collector placed in the cradle good cradle green light indicates the POWER collector positioned correctly. | | | | 3Symptom | Cradle state | Cradle POWER light green, DATA light does not shine, LINE lamp is not lit. | | Logger status | After some time, the collector exit communication status, suggesting that 'communication failure'. | | Production System Status | After some time, quit the communication status, suggesting that 'timeout did not receive the information.' | | reason | Communication configuration errors or communication connection is not normal. | | Workaround | 1, check the cradle RS232 communication cable is normal, if not then connect the communication cable. 2, check collection, cradle and configuration files to set communication speed is consistent, if not adjust the consistency.
The default baud rate is 9600 B / S. In [System logger function] - [Settings], set baud rate communication speed is 9600 B / S; cradle's DIP switch is set to (1,2,5 is ON, the rest OFF); communication profile (comm . cfg) the communication rate is set to 9600.3, check the connection of the auxiliary communication port is set in the configuration file is the auxiliary port. Default is to use auxiliary port three. 4, if the above steps have been tested normal, replace the RS232 communication cable or cradle. | | | | 4Symptom | Cradle state | Cradle POWER light green, DATA light flashes, LINE lamp is not lit. | | Logger status | After some time, the collector exit communication status, suggesting that 'communication failure'. | | Production System Status | After some time, quit the communication status, suggesting that 'timeout did not receive information', network terminal screen appears random characters. | | reason | Communication requires a configuration file (comm.cfg file) does not exist or the configuration file format error. | | Workaround | 1, if the home under the etc directory does not exist in the desired configuration file, add comm.cfg file. 2, if the configuration file exists, then check the file format is correct, because the cause of the problem is not in the configuration file command on the terminal configuration, add the terminal commands. About the file format, see: Configuration Files. | | | | 5Symptom | Cradle state | Cradle POWER light green, DATA light yellow or red, LINE lamp is not lit. | | Logger status | After some time, the collector exit communication status, suggesting that 'communication failure'. | | Production System Status | After some time, quit the communication status, suggesting that 'timeout did not receive the information.' | | reason | Cradle problems. | | Workaround | Replace with a new cradle. | | | | 6Symptom | Cradle state | Cradle POWER light green, DATA light flashes at intervals, LINE lamp is not lit. | | Logger status | After some time, the collector exit communication status, suggesting that 'communication is successful | | Production System Status | After some time, quit the communication status, suggesting that 'New data exchange file failed'. | | reason | Data conversion error occurs, usually the system convert the text file type definitions needed file does not exist, the data file does not exist or exists but does not meet the document type definition format caused. | | Workaround | 1, check the desired document type definition file exists, it exists in the home under the etc directory, if this directory is not the file you need to copy the file. 2, check the document type definition file format is correct, refer to Appendix: Document Type Definition file. 3, check whether the data generated is empty, even if the data is empty, the data file must have the format defined in line with the text file data. For example downloaded from the system maintenance information to the collector, if you choose to maintain information data is empty, then the data is converted when an error occurs. | | | | 7Symptom | Cradle state | Cradle POWER light green, DATA lights flickered, LINE lamp is not lit. | | Logger status | Communication schedule has not been completed, the collector exit, whether the communication is successful and no tips. | | Production System Status | After some time, quit the communication status, suggesting that 'protocol error'. | | Reason | Acquisition of the remaining space. | | Workaround | A disk check collector remaining memory space, if the space is too small, then in ensuring data backup disc collector A case of success, formatting collector A disk, re-transmission applications. |
|