Changes

FMB120 has 50 configurable Geofence zones and it can generate an event when defined Geofence zone border is crossed.

FMB120 has 50 configurable Geofence zones and it can generate an event when defined Geofence zone border is crossed.

Frame border – frame border is an additional border around Geofence zone. It is additional area around defined zone used to prevent false event recording when object stops on the border of the area and because of GNSS errors some records are made inside area and some – outside. Event is generated only when both borders are crossed. See figure to the right for details: blue track is considered to have entered the area while red track is not.<br/>Shape – can be rectangle or circle. User can choose what geozone shape will be.<br/>Priority – priority of Geofence event: low, high or panic. These levels define priority of event information sending to server. See I/O element description for more details about priorities in [[FMB120 I/O settings|I/O settings section]].<br/>Generate event (On entrance, On exit, On Both) – choose when record will be generated.<br/>Eventual records – when disabled scenario status value will be appeared in each AVL record, and when enabled scenario status value will be appended only to eventual records.<br/>OverSpeeding – in each geozone OverSpeeding scenario can be configured separately. Regular OverSpeeding functionality and geozones OverSpeeding funkctionality is working independently. If digital output control is enabled in regular OverSpeeding scenario, geozones OverSpeeding scenario controls it too. If device is in more that one geozone and OverSpeeding is detected in any zone then digital output turns on. Digital output turns off only when OverSpeeding is not detected anywhere (regular OverSpeeding and geozones OverSpeeding).<br/>X1 – geofence zone left bottom corner X coordinate (longitude);<br/>Y1 – geofence zone left bottom corner Y coordinate (latitude);<br/>X2 or R – geofence zone upper right corner X coordinate (longitude) or radius of circle when Circular zone is used (radius in meters);<br/>Y2 – geofence zone upper right corner Y coordinate (latitude).

Frame border – frame border is an additional border around Geofence zone. It is additional area around defined zone used to prevent false event recording when object stops on the border of the area and because of GNSS errors some records are made inside area and some – outside. Event is generated only when both borders are crossed. See figure to the right for details: blue track is considered to have entered the area while red track is not.<br/>Shape – can be rectangle or circle. User can choose what geozone shape will be.<br/>Priority – priority of Geofence event: low, high or panic. These levels define priority of event information sending to server. See I/O element description for more details about priorities in [[FMB120 I/O settings|I/O settings section]].<br/>Generate event (On entrance, On exit, On Both) – choose when record will be generated.<br/>Eventual records – when disabled scenario status value will be appeared in each AVL record, and when enabled scenario status value will be appended only to eventual records.<br/>OverSpeeding – in each geozone OverSpeeding scenario can be configured separately. Regular OverSpeeding functionality and geozones OverSpeeding funkctionality is working independently. If digital output control is enabled in regular OverSpeeding scenario, geozones OverSpeeding scenario controls it too. If device is in more that one geozone and OverSpeeding is detected in any zone then digital output turns on. Digital output turns off only when OverSpeeding is not detected anywhere (regular OverSpeeding and geozones OverSpeeding).<br/>X1 – geofence zone left bottom corner X coordinate (longitude);<br/>Y1 – geofence zone left bottom corner Y coordinate (latitude);<br/>X2 or R – geofence zone upper right corner X coordinate (longitude) or radius of circle when Circular zone is used (radius in meters);<br/>Y2 – geofence zone upper right corner Y coordinate (latitude).