How can I discriminate "confirmed service requests", using the magnetic badge, from "non confirmed service requests"?

Jérôme Chambard

27/05/2019 17:36

0 Comments

There are several ways to use the magnetic badge. One of them allows to discriminate "confirmed service requests", using the magnetic badge, from "non confirmed service requests". for instance, a confirmed request could be considered as an urgent request.

To do that, you should use the code mode (RNM 9 in the documentation):

The user has TPB seconds to press one or several buttons corresponding to his request, calculated from the first push.
If a badge is used before expiration of TPB, the radio frame is sent immediatly, with ack = 1 (Skiply API) or a raw payload beginning with 0x03 (direct integration).
If no badge is presented before the expiration of TPB, a frame will be sent with ack = 0 (Skiply API ) or a raw payload beginning with 0x02 (direct integration).

The entire list of parameters to be set to implement this use can can be found on the Skiply configurator.

Tags: use case implementation