[Date Prev][Date Next] [Chronological] [Thread] [Top]


Any central count version that is EARLIER than Central Count 2.00h, 128K memory cards are not supported and will not work.  32K memory cards should work however.  Lesley is currently running 2.00g and is the reason why 128K cards do not work.




-----Original Message-----
From: owner-support@gesn.com [mailto:owner-support@gesn.com] On Behalf Of Lesley Thompson
Sent: July 17, 2002 2:45 PM
To: support@dieboldes.com
Subject: Re: AVOS "BAD CHECKSUM" message


Jason, how do I determine what the version of the Central Count chip is?  Are there other version control aspects to the AVOS system?


Jeff Hintz has informed me that with their current version of Central Count chips, 128 meg cards will not work. 


So, we will go back to the 32mg cards.  I only had one 32mg that was intermittently failing (which is why we went to 128mg cards because McK is no longer supplying new 32mg cards).   I've since talked to McKinney again and they happen to have one more 32mg and are sending it out to us tomorrow.  Les

----- Original Message -----

From: Jason Wong

Sent: Wednesday, July 17, 2002 3:10 PM

Subject: RE: AVOS "BAD CHECKSUM" message




Could you specify the version of Central Count you are running.  It is odd that all four memory cards seem to produce a bad checksum and the issue will be looked into.  Please attempt to narrow down your operation before a “BAD CHECKSUM” message occurs if possible.


Juan is correct however in that the memory card only holds little information.  Four parameters to be exact, which is the phone number, user name, password and host IP address.




-----Original Message-----
From: owner-support@gesn.com [mailto:owner-support@gesn.com] On Behalf Of Juan A. Rivera
Sent: July 17, 2002 1:01 PM
To: support@dieboldes.com
Subject: RE: AVOS "BAD CHECKSUM" message


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.




-----Original Message-----
From: owner-support@gesn.com [mailto:owner-support@gesn.com] On Behalf Of Lesley Thompson
Sent: Wednesday, July 17, 2002 1:08 PM
To: support@gesn.com
Cc: jhglobal@earthlink.net
Subject: AVOS "BAD CHECKSUM" message




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?