User Account ID
Assigned by DSS N/A
User Experiment Number


Any number within range following your experiment designator system.

Use a number from 0 to 65535 to reflect this experiment and distinguish it, and associated tag settings, from other experiments.

On-fish mission duration (days)


1-365 depending on your experiment

Per your experiment requirement, up to 365 days. One or a few days may be added if it is anticipated that the tag will be floating in a bucket on deck in on-fish mode ready for deployment once a fish is caught.

Low temperature exposure based crush depth prevention release: Temperature threshold (deg C). When below this temperature, the exposure counter will start running. When above it, the low temperature exposure count is reset again. Tag release will occur when the exposure counter reaches the elapsed time specified in RLT_MINT_TIME. RLT_MINT_TEMP should be generally below what the fish experiences, but above the temperature encountered at 1000m depth (rated tag service depth is 1200m and nominal crush depth is 1800m)



The NOAA Ocena Atlas shows a averge temperature of about 5 deg at 1000m depth off the east coast of Australia. We recommend 7 deg C to provide a safety margin against crushing in this case. Use a lower value if the primary concern is release while the fish is still alive.

Low temperature exposure based crush depth prevention release: Exposure time limit (minutes). Specify the low temperature exposure time in minutes that will trigger a release. This value should be above the time the fish could tolerate at the temperature specified in RLT_MINT_TEMP, but below the time it may take the fish,if dead, to sink to crush depth.



We'll assume a maximum dead fish sinking speed of 0.025m / sec, meaning that the fish when alive would have to provide 2160m per day vertical ascent just to cancel its natural sink speed… which seems a very high energy cost. At this rate, a fish would sink from the 1000m depth for which the temperature cutoff was defined to the 1200m service depth in 133 minutes. Please make sure the fish is unlikely to encounter the resulting exposure when alive. If you think this may happen, take a risk and raise the value above our recommendation.

Low delta-T release - temperature change rate (deg C per minute). Specify a temperature transition rate which if never reached for the number of days specified in RLT_DT_TIME will cause a tag release.



VIMS tagging data for bluefish tuna has shown temperature transitions of at least 2 deg C / minute while on fish, and no more than 0.02 deg C / minute once released from fish. Thus we recommend a threshold of 0.2 deg C /minute. Generally increase the number in waters with large temperature variations near the surface and decrease it when the fish may only encounter limited temperature changes during normal diving.

Low delta-T release - time (days). Specify a temperature transition rate which if never reached for the number of days specified in RLT_DT_TIME will cause a tag release.



As a fairly arbitrary number, we recommend three days of low delta-T observations before the release is triggered. This will limit the amount of time and travel distance since mortality. Adjust as needed.

Darkness release (days). Specify the days of continuous darkness causing a release.



For pelagic species, light should be present every day. So, two days of darkness may indicate ingestion of the tag by another animal, i.e. probable mortality. Adjust as needed.

Post-release Argos Transmit duration (days). The tag will stop transmitting after the specified number of days. This affects only the REPORTING phase. Transmissions are unlimited in all other tag states including ONFISH.


The recommendation is 5 days if only the pop-up location and tag status code is needed, 30 days if archived daily summaries for up to one year on-animal is needed, or a large number such as 3650 days if you prefer to monitor and the request Argos data delivery stop, which is available after 60 days in typical Argos contracts.

Powerloss RESET. Trigger the release if the tag experiences and recovers from a power loss.


Should generally be YES, because recovery from a powerloss means the tag has returned to the light and has probably shedded. Its time since deployment is also unknown; i.e. it may have been in darkness for a long time. Set to NO only for specialty functions, such as to limit release to specific temperature conditions only, ignoring the time factor.