![]() The Vemco Monitor provides customers, researchers and biologists with up-to-date information on new fish tracking and monitoring products and research and development activities from Vemco |
||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Issue 2, May 2006 Background In actual fact, Sub Map D was never used for R64K since, for a long time, the 4096 Codes provided by Sub Map B were adequate. Instead, the 340 millisecond interval was used for a number of special cases such as providing an additional R256, R4k or S256 Sub Map for custom installations. Changes to the 51 kHz to 84 kHz Standard Map To do this, we are redefining the standard Map (to be called Vemco 1.1 2006 51-84) as shown in the table below. This differs from the previous standard in two respects:
At the same time, Sub Maps B and C, which are used by the vast majority of 69 kHz Transmitters sold, have not been changed. Implications for Users Since there are not enough IDs to meet the requirement of all those deploying pingers, Sub Map B needs to be treated as a scarce resource and, therefore, we will be encouraging customers using pingers to move to the 64k Sub Map D. To meet concerns of users who want to do testing before committing to longer 64k codes, we will try to meet the 2006 needs from the 4k Sub Map B. At the same time, we will ask them to try some 64k tags with a view to committing to R64k for 2007. The following table summarizes modifications users will need to make to receiver configurations to support these changes. We will be providing detailed instructions to support users needing to reconfigure their receivers as well as the appropriate configuration files for Vemco 1.1 2006 and selected custom Maps. Users requiring assistance or more information should call 1-902-852-3047 or email Customer Support. As well, users who feel they may require a configuration change before full instructions should also contact Customer Support for assistance. New Nomenclature to be Introduced Planned future coding enhancements which will support new capabilities such as more ID Codes, more robust error detection and/or correction, more sensor data (number of sensors, bits per sensor), etc. will not fit very well, if at all, into the "Sub Map" structure. Therefore, we plan to introduce a new nomenclature which will be used for all coding schemes and will provide a unique, unambiguous characterization for each current and future coding scheme ("sub map" in the current definition). The introduction of this new nomenclature will coincide with the planned release of a new generation of Receiver PC software later this year. More details will be provided in our next Newsletter to be published late this Summer.
|
||||||||||||||||||||||||||||||||||||||||||||||||||||
