USPACE-KYD-2F
Rev. 1.3:
- BLE & NFC passive tag. Tap-to-connect protocol and secured BLE connectivity
- Alerting though light, vibration and sound
- automatic sleep mode through motion detection (< 50 µA current consumption)
- up to 100 hours of operation ( 2 working weeks)
- Operating temperature: -40 °C to 85 °C
Applications
- respect of minimal distance between humans (COVID-19 sanitary restrictions)
- contamination chain traceback
- proximity of dangerous objects
- entering restricted / special area
- presence detection
- indoor real-time localization
Description:
- The Uspace-KYD-2F is a FCC certified professional distance alerting tag, especially designed to prevent risky situations (FCC ID: 2ARZVUK)
- WizziLab product line at www.wizzilab.com/products
Features:
- Low-latency low-power distance monitoring tag based on DASH7-UWB hybrid technology.
- FCC Certified.
- DASH7 stack, operating in the FCC 915 MHz ISM band under FCC 15.247. GFSK 55.6 / 167.7 kbps modulation schemes. Conducted power at antenna port +11.56 dBm.
- UWB two-way-ranging, operating @ 6.4 GHz (802.15.4a, channel 5).
Hardware specification
Recommended operating conditions
Table 1. Absolute maximum ratings
| Symbol | Parameter | Min. | Typ. | Max. | Units |
| TSTG | Storage temperature range | -40 | 25 | 90 | °C |
| VCHR | Charging voltage (USB port) | – | 5.0 | V | |
| ICHR | Charing current (USB port) | – | – | 500 | mA |
Table 2. Recommended operating conditions
| Symbol | Parameter | Min. | Typ. | Max. | Units |
| TA | Operating ambient temperature range | -40 | 25 | 85 | °C |
Power consumption
Table 3. Power consumption
| Symbol | Parameter | Min. | Typ. | Max. | Units |
| IDLP | Current in deepsleep mode | – | – | 5 | µA |
| ILP | Current in sleep mode | – | 50 | – | µA |
| ION | Current in monitoring mode (*) | – | 10 | – | mA |
| IBAT | Battery capacity | – | 1100 | – | mAh |
| VBAT | Battery voltage | – | – | 3.7 | V |
| TON | Battery lifetime in monitoring mode (*) | – | 100 | – | h |
| TAUTO | Battery lifetime in monitoring mode with autosleep option (8h activity per day) | – | 2 | – | week |
(*) the consumption in monitoring mode depends on the monitoring parameters. Here are provided typical values for the default (factory) configuration.
Functionality
General Purpose – Distance Monitoring
The Uspace-KYD is a professional distance alerting tag, especially designed to detect risky situations, such as human-to-human minimal distance transgression for Covid-19 sanitary protection, or dangerous objects proximity. In active (monitoring) mode, the tag scans for the presence of other tags using the DASH7 sub-GHz protocol (ISM 915 MHz) and makes distance measurements to each of the detected tags using UWB. The tag alerts in case of distance violation using the embedded human-machine-interfaces (HMI) – LED, buzzer, vibrator. When available, the tag can report its measurements to a DASH7 gateway, connected to the cloud, using the DASH7 protocol. In maintenance mode, the tag’s BLE & NFC interfaces are enabled and the tag can be paired and accessed using tap-to-connect.
Monitoring zones and events
Tags are out of the “view zone” if they are not mutually accessible over the DASH7 scan wireless link or when their relative distance, measured in terms of signal attenuation (link budget) exceeds a certain threshold (typically 80 dB). The view zone’s radius is thus typically roughly 10-20m.
When a tag is in the view zone of a distant tag, it first gets the distant tag custom “alert zone” and “safety margin”. The alert zone may differ from one object to another. For example the alert zone for Covid-19 distancing (object = human) is typically 2 meters. It can be set to 5 meters for a moving trolley, a freight elevator, a high voltage transformer or another industrial machine or tool. A safety margin (hysteresis) is provided in order to avoid toggling the alert / contact states. The safety margin is typically 20 cm, in accordance with the UWB measurement error.
When the tag enters the view zone of the distant tag, both generate a “Start Contact” event. The contact continues but alert is not triggers out of the alert zone (in particular it is not triggered in the safety margin zone).
When the tag enters the distant tag’s alert zone, both tags generate a “Start Alert” event and the alarm notification, composed of a LED blinking, buzzer and vibrator patterns, is played. The alert continues while the tag is in the alert zone or in the safety margin zone.
The alert stops when the tag exits the “alert + safety zone” and “End Alert” event is generated. The contact ends when the tag exits the “view zone” and an “End Contact” event is generated.
Contact Events Management:
The tag has different contact events recording/reporting management modes :
- Stand-Alone : Events are not recorded
- Stand-Alone with traceback : Events are recording in internal flash and can be dumped through serial or BLE.
- Real-time monitoring : Events are recorded in internal flash and reported over-the-air immediately to a Cloud service
All gathered contact information is anonymous. Indeed the contact/alert reports contain only information on the tags identifiers and event dates, and cannot be associated to places or persons, unless this is specifically (and manually) assigned by the system administrator.
Autosleep
The tag embeds a motion detector. When the device is motionless for a certain period, the tag stops monitoring and becomes inactive. Monitoring resumes when motion is detected. The autosleep can be disabled.
Default Configuration
By default (factory settings) tags are configured for human-to-human minimal distance monotoring for Covid-19 sanitary protection.
The view zone distance is set to 80 dB link budget on the scan wireless link The alert zone is set to 2 meters
The safety margin is set to 20 cm
Autosleep is enabled, the motionless period is set to 10 minutes.
The tag functions in real-time monitoring mode – the contact events are recorded and reported over- the-air when a DASH7 connectivity is present (a DASH7 gateway is within wireless link range).
How to use
Just charge-and-play
The tag is fully pre-configured and not requiring any initial setup through web or mobile application.
The tag is fully autonomous, its alerting functionality does not depend on the availability of any local or global network connection. In particular, even in real-time monitoring mode, the absence of DASH7 connectivity does not alter the alerting functionality. Reports history, when enabled, remains accessible in the tag’s flash memory.
First enable
When produced and conditioned for shipping, the devices are set in deepsleep mode (aka shelf mode). They are completely inactive, do not scan nor measure distances, the BLE and NFC interfaces are disabled (no any intentional radio emissions). In order to set the device to monitoring mode (aka tag mode), one should connect it to an electronic device’s USB port or 5V DC power supply with USB connector using the provided USB adaptation cable. This will start charging the battery and set the device to charging mode (and exit shelf mode.
Charging:
When the tag is connected to an electronic device’s USB port or 5V DC power supply with USB connector, the tag enters charging mode, and the LED starts blinking in orange. The tag becomes inactive (no scanning). It remains accessible for configuration updates.
When the battery is fully charged, the LED will start blinking in green.
Uplink Messages:
This section describes the reporting formats, which are of interst only the system administrator over the dash7board WizziLab’s Cloud Service.
Status Report (FID 190)
The status message contains the main element of the configuration, the state and the battery voltage in mV.
Example:
{
“status_param_2″=>2, “status_param_2_fields”=>{“upload“=>0, “save“=>1, “deactivate“=>0, “alarm_pattern“=>0},
“status_options”=>18, “status_options_fields”=>{“idx“=>2, “autosleep“=>1, “passive“=>0}, “status_mode“=>1,
“status_state”=>5, “status_state_fields”=>{“stable“=>1, “plugged“=>0, “disco_off“=>1}, “status_vbat”=>4063
}
Contact Report (FID 202)
The contact message always sends the current local timestamp in seconds It is followed of up to 12 contact logs. Each contact log contains:
contact_uid: The UID of the contact
nb_contacts: The number of times the contact occurred (number of time the alarm was triggered)
timestamp_first_seen: The timestamp of the first alarm
seen_time: The duration between the first time the TAG is seen and the last time it has been seencontact_time: The accumulated duration of the alarm situation.
Example:
{
“report_ts”=>9607,
“contact_uid_0_“=>”001BC50C700220E7”, “contact_since_0_”=>2107906, “contact_since_0 fields”=>{“nb_contacts“=>2, “timestamp_first_seen“=>8234}, “seen_time_0_“=>612, “contact_time_0_“=>11,
“contact_uid_1_”=>”001BC50C70022169”, “contact_since_1_”=>3695106, “contact_since_1 fields”=>{“nb_contacts”=>2, “timestamp_first_seen”=>14434}, “seen_time_1_”=>133, “contact_time_1_”=>7,
“contact_uid_2_”=>”001BC50C70022231”, “contact_since_2_”=>3730688, “contact_since_2 fields”=>{“nb_contacts”=>0, “timestamp_first_seen”=>14573}, “seen_time_2_”=>170, “contact_time_2_”=>0
}
Note: To read the complete user manual, please download the following file: