Important Notice for VEMCO Customers

VEMCO users must configure their receivers with a proper Code Map in order to detect their tags as well as tags of their collaborators or other researchers.

Note: Configuration with the wrong map MAY result in lost detection data.

MAP-110 is the correct map for most users. However, a few users will require MAP-310. For details on which map to use and how to configure your receiver please read on. Note that POST users can continue to use POST 2006 map.

What are Code Maps?
Code Maps are instruction sets which provide VEMCO receivers with all the information necessary to correctly detect and decode VEMCO transmitters. Your VEMCO receivers must be configured with the right Code Map in order to detect your transmitters and/or the transmitters of your collaborators or fellow researchers.

Over the years, VEMCO coding schemes have continuously evolved to keep up with the needs of researchers. As a result, a number of corresponding code maps were developed. However, our overall desire has always been to keep as many of our customers as possible using a common code map. This benefits users by keeping the receivers compatible, allowing for collaboration, and lessens errors in the field (less things to choose from).

In May of 2006, VEMCO issued a new Code Map, called V 1.1 2006 and encouraged users to make the switch. This was an update from our then standard map, VEMCO D51-84 which is now OBSOLETE. At this time, we removed the ability to detect R256 (401.2/22.3) tags in order to make room for additional sensor tags. However, we have found that since then, we have had to develop a custom map for a large group of researchers still using R256 tags due to having older VR1 receivers within their arrays. As issuing custom maps moves us away from having a common map, we have now created a new standard map, MAP-110 which includes support for R256 tags.

The table below shows the details of the new and former Code Maps.

* Code Map names have been updated to MAP-XXX format to simplify the naming.

** Starting in January 2007 with the release of new VEMCO PC Receiver software, transmitters will be assigned a code space label which will unambiguously define all the parameters necessary for a receiver to detect these transmitters. VEMCO will continue to provide both the old and new nomenclature for tags to ease the transition to new names.

*** No users should have their receivers configured with VEMCO D51-84 (also known as 1432-D). This map WILL NOT support current tags.

Why is a common map so important?
More and more users are telling us everyday that they want to be able to collaborate with fellow researchers. This means they want to share data and leverage each others receiving arrays. They can only do this if all their receivers are configured in a common way. As well it greatly alleviates confusion among users and reduces errors in the field if we have less choice about how to configure our receivers.

All VEMCO receivers being shipped today will contain, by default, MAP-110 unless the researcher, in consultation with a VEMCO sales agent, requests or requires an alternate map.

Over time, we will continue to see changes in code maps as we continue to provide new and expanded tags to our users. VEMCO users are encouraged to monitor the VEMCO website for changes in map configurations.

Which map should I use?
For most users, our current standard map, MAP-110, will be the correct map to use. For those who recently upgraded to MAP-310 (V 1.1 2006), you may be okay as well.

The choice of map depends on the type of tags you are trying to detect. Both your own tags as well as those of other researchers with whom you are collaborating. Because there are many tags active in the field which have been sold over the past several years, it is not possible to provide a standard answer that will be correct for all. Please read the following to determine the right map for you.

Selecting the right map
In order to select the right map you need to know which tags you are using. This includes the tags you recently bought as well as tags that you have already deployed and are still active. You may also want to include tags from other researchers if you are expecting to detect their tags as well.

The information you need for your tags is as follows:

• Tag Code Type: e.g. R256, R4k, S256 or R64K
• Sync: e.g. 320 ms
• Bin: e.g. 20 ms

Please note that tags can have the same tag type, i.e. R64K but have different sync or bin numbers. You need all three pieces of information. Note you do not need to include the tag size, such as V7 or V16.

This information will be found on the tag spec sheets that were delivered with your tags. If you cannot find this information, please contact VEMCO Sales. We keep records of what we sold you!

Once you have this information, please refer to the table above to see which of the two valid maps covers your set of tags, either MAP-110 (new) or MAP-310 (V 1.1 2006). Note that you are looking for a code map which can detect ALL of your tags. If both code maps are suitable, the preference is to select MAP-110. However, if both are suitable and you have already updated your receivers to MAP-310(V 1.1 2006), there is no need to rush out to change your receivers again. You may wait until your next convenient opportunity. However, please be aware that MAP-310 (V 1.1 2006) will NOT detect R256 tags which may have been released in your area by other researchers.

Please note that some VEMCO users have been sent a custom map called Custom1432 which is equivalent to MAP-110. In this case you do not need to update your receivers.

If your particular set of tags is not supported by either of these code maps, please contact VEMCO Sales for assistance. We'll figure out a solution that will work for you!

How do I configure my receiver with a new Code Map?
After you've determined that you need to update your receiver, follow the instructions below for each of the various receivers.

• VR2 Map Update Instructions
• VR3 Support
• VR28 Support - Call 1-900-450-1700 ext. 244
• VRAP Support - Call 1-900-450-1700 ext. 244