Checksum is a test that is done to verify the integrity of memory devices. There are many ways to
do checksum tests, but in keeping it simple what it means is that once any information is written in to a memory device, the software counts all the digital representation (ONE Bits) that represents the data. That total is placed in a particular part of the memory device as a check sum. During tests the memory device is recounted making sure that the Data stored and recorded earlier (represented by the checksum) on the memory device is equal to the checksum if finds now. If it matches, well no problem, if it doesn’t then a check sum error will be declared.
The possible culprits are the memory devices themselves (bad memory card or bad batch of memory cards, or the memory card reader failure, or bad software.
Try making sure that power is shut off before inserting and removing AVOS memory card to see if problem persists.
Memory card holds IP address and password info for central count. Although insignificant this is still data and it will be checked sum.
Johnson County, Kansas had been receiving a "BAD CHECKSUM" message intermitted on one of their 32mg AVOS cards. We replaced all four of their AVOS 32mg cards with AVOS 128mg cards. Now Kris is getting the "BAD CHECKSUM" message on all of the 128mg cards. As I understand it, in using the AVOS in a central count environment with each scanner connected to the internal network, the main function of the AVOS card is to hold the IP address in memory, meaning that if the cards are not working the worst that is happening is that the IP address has to be re-entered every time want to transmit. Two questions:
1. What is causing the "BAD CHECKSUM" message and how do we fix it?
2. Is the AVOS card doing anything other than holding the IP address in a network connected central count setting?