AVID Microchips - Clarification!

Petrelocation.com - A reader of ours has recently pointed out a bit of confusion on our part and the postings we have done in the past on the AVID Microchip.

Here is her response as she sent it as she brings up some great points!

I read your blog regarding Avid chips being ISO compliant. This is an outdated fact and the only chips that meet ISO criteria are a 134kHz microchip.
Pet owners are already confused, your Avid article is clearly bias and skewed their way. Your information should provide unbiased commentary and not from manufacturers.

When ISO standards 11784 and 11785 were developed, there was concern regarding protection of the installed base of microchips, often referred to as backward compatibility. ISO 11785 Annex A was developed to address this issue during the transition period between prior and ISO standard technology and defined the need for readers to read three technologies (Destron, Datamars, and Trovan) for a period of 2 years. AVID was not included in Annex A because they elected not to provide the encryption code with which to read their encrypted microchips. However, this 2-year period has long since passed and this was clearly defined in ISO 11785, Section 2 (Conformance), wherein it states "...transponders meeting the requirements of Annex A may be applied for a transition period of 2 years from the date of the first edition of this international standard." The date of the first edition was 1996, and as this time frame was completed in 1998, Annex A is no longer applicable, hence, Annex A microchips are not true ISO standard microchips.

ISO 11784 and 11785 clearly define the bit content and communication protocol of microchips that adhere to these ISO standards. As such, a true ISO microchip has a 64 bit content resulting in a 15 digit numeric ID code of which the first 3 digits is the manufacturer's code that operates using FDX-B technology at a frequency of 134.2 kHz.


PetRelocation Team





Add a Comment

Name is required

Email is required and must be in the format email@domain.com

Comment is required

Back to top