Invalid Timing Marks Error Scanning Forms
The invalid timing marks error could be caused be several things.
First, check the template in the Template Editor to make sure the correct number of timing marks was entered in the template's properties by clicking File|Properties. If the number is correct compared to the form, check the form itself to be sure that the timing line is in the correct position.
Also try scanning several copies of the same form- do they all yield the error or just a few? If only some of the forms produce the error, it could be due to the way the form was printed. Ensure the forms are being properly placed in the scanner to avoid skewing. If all of the forms produce the error, the problem may be related to communications between the scanner and the system.
First try increasing the reader timeout setting under Tools|OMR Scanner. Doubling it is a good starting point. You can try several settings to see if there is improvement.
If the increased timeout does not resolve the issue, use the following checklist to ensure proper communications:
- Ensure that the right port is being used under Tools|OMR Scanner.
- If you are using a Scantron OpScan OMR scanner and you still cannot get a response from the OMR scanner, check the scanning mode on the scanner. OpScan scanners must be set to Image Mode, not 3000 emulation mode.
- Ensure that no other software is using the same port as the scanner. For example, mobile devices often have syncing software that runs in the background and will keep the port open.
- Check the OMR scanner's baud rate, which controls the speed of data transfer. The scanner and software must be set to the same baud rate. You may adjust this rate for better communication; remember to adjust the OMR scanner's baud rate accordingly.
Note: the above information can also apply to an Invalid Page ID Marks error.
|Posted - Tue, Aug 5, 2014 at 4:02 AM. This article has been viewed 4829 times.
|Online URL: https://support.gravic.com/remark/kb/article/invalid-timing-marks-error-scanning-forms-33.html
Powered by PHPKB (Knowledge Base Software)