FMB640 Manual Geofence zones - Revision history

Sandra.Gasyte: Replaced content with "{{Template:FMX640 Manual Geofence zones|model = FMB640 }} Category:FMB640 Configuration"

2020-08-31T09:37:45Z

Replaced content with "{{Template:FMX640 Manual Geofence zones|model = FMB640 }} Category:FMB640 Configuration"

← Older revision		Revision as of 12:37, 31 August 2020
Line 1:		Line 1:
	~~[[Image:Fmb120_geofence_border.png\|400px\|right\|link=https://wiki.teltonika-gps.com/view/File:Fmb120_geofence_border.png]]~~{{~~{model\|FMB640}}} has 100 configurable~~ Geofence zones ~~and it can generate an event when a defined Geofence zone border is crossed.~~		{{Template:FMX640 Manual Geofence zones\|model = FMB640
	''Frame border'' is an additional border around Geofence zone used to prevent false events when object stops on the border of the area and as a result records are made inside and outside the defined area because of GNSS errors. The event is generated only when both (Geofence and frame) 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 a rectangle or a circle as defined by the user.<br />Priority of Geofence event is categorized into Low, High or Panic levels. These levels define the priority of event information that is sent to the server. For more details about priorities look in {{{ctrIO\|[[FMB640_I/O_settings#Operands\|FMB640 ~~I/O settings]]~~}}}.<br />''Generate event'' allows to choose when record will be generated.<br />''Eventual records'' controls where scenario status value appears: when disabled it will exist in each AVL record and when enabled the value will be appended only to eventual records.<br />''OverSpeeding'' helps to configure OverSpeeding scenarios separately for each different ''Geozone''. Regular OverSpeeding and geozones' OverSpeeding function independently. If digital output control is enabled in a regular OverSpeeding scenario, geozones OverSpeeding scenario will control it too i.e when the device is in more than one geozone and OverSpeeding is detected in any zone then the digital output turns on. Digital output turns off only when OverSpeeding is not detected anywhere.<br /><br />''X1'' is used to set geofence zone left bottom corner X coordinate (longitude) while ''Y1'' is used to set Y coordinate (latitude).<br />''X2'' or ''R'' are used to set accordingly geofence zone upper right corner X coordinate (longitude) when Rectangular zone is used or circle radius when Circular zone is used. ''Y2'' sets geofence zone upper right corner Y coordinate (latitude) for a Rectangular zone.[[File:Drawing a Rectangle Geofence.gif\|alt=\|center\|Rectangle Geofence\|link=https://wiki.teltonika-gps.com/view/File:Drawing_a_Rectangle_Geofence.gif]]		}}
	[[Category:FMB640 Configuration]]		[[Category:FMB640 Configuration]]

Sandra.Gasyte at 08:01, 31 August 2020

2020-08-31T08:01:59Z

← Older revision		Revision as of 11:01, 31 August 2020
Line 1:		Line 1:
	[[Image:Fmb120_geofence_border.png\|400px\|right\|link=https://wiki.teltonika-gps.com/view/File:Fmb120_geofence_border.png]]{{{model\|FMB640}}} has 100 configurable Geofence zones and it can generate an event when a defined Geofence zone border is crossed.		[[Image:Fmb120_geofence_border.png\|400px\|right\|link=https://wiki.teltonika-gps.com/view/File:Fmb120_geofence_border.png]]{{{model\|FMB640}}} has 100 configurable Geofence zones and it can generate an event when a defined Geofence zone border is crossed.
	''Frame border'' is an additional border around Geofence zone used to prevent false events when object stops on the border of the area and as a result records are made inside and outside the defined area because of GNSS errors. The event is generated only when both (Geofence and frame) 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 a rectangle or a circle as defined by the user.<br />Priority of Geofence event is categorized into Low, High or Panic levels. These levels define the priority of event information that is sent to the server. For more details about priorities look in {{{ctrIO\|[[FMB640_I/O_settings#Operands\|FMB640 I/O settings]]}}}.<br />''Generate event'' allows to choose when record will be generated.<br />''Eventual records'' controls where scenario status value appears: when disabled it will exist in each AVL record and when enabled the value will be appended only to eventual records.<br />''OverSpeeding'' helps to configure OverSpeeding scenarios separately for each different ''Geozone''. Regular OverSpeeding and geozones' OverSpeeding function independently. If digital output control is enabled in a regular OverSpeeding scenario, geozones OverSpeeding scenario will control it too i.e when the device is in more than one geozone and OverSpeeding is detected in any zone then the digital output turns on. Digital output turns off only when OverSpeeding is not detected anywhere.<br /><br />''X1'' is used to set geofence zone left bottom corner X coordinate (longitude) while ''Y1'' is used to set Y coordinate (latitude).<br />''X2'' or ''R'' are used to set accordingly geofence zone upper right corner X coordinate (longitude) when Rectangular zone is used or circle radius when Circular zone is used. ''Y2'' sets geofence zone upper right corner Y coordinate (latitude) for a Rectangular zone.[[File:Drawing a Rectangle Geofence.gif\|alt=\|center\|Rectangle Geofence\|link=https://wiki.teltonika-gps.com/view/File:Drawing_a_Rectangle_Geofence.gif]]		''Frame border'' is an additional border around Geofence zone used to prevent false events when object stops on the border of the area and as a result records are made inside and outside the defined area because of GNSS errors. The event is generated only when both (Geofence and frame) 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 a rectangle or a circle as defined by the user.<br />Priority of Geofence event is categorized into Low, High or Panic levels. These levels define the priority of event information that is sent to the server. For more details about priorities look in {{{ctrIO\|[[FMB640_I/O_settings#Operands\|FMB640 I/O settings]]}}}.<br />''Generate event'' allows to choose when record will be generated.<br />''Eventual records'' controls where scenario status value appears: when disabled it will exist in each AVL record and when enabled the value will be appended only to eventual records.<br />''OverSpeeding'' helps to configure OverSpeeding scenarios separately for each different ''Geozone''. Regular OverSpeeding and geozones' OverSpeeding function independently. If digital output control is enabled in a regular OverSpeeding scenario, geozones OverSpeeding scenario will control it too i.e when the device is in more than one geozone and OverSpeeding is detected in any zone then the digital output turns on. Digital output turns off only when OverSpeeding is not detected anywhere.<br /><br />''X1'' is used to set geofence zone left bottom corner X coordinate (longitude) while ''Y1'' is used to set Y coordinate (latitude).<br />''X2'' or ''R'' are used to set accordingly geofence zone upper right corner X coordinate (longitude) when Rectangular zone is used or circle radius when Circular zone is used. ''Y2'' sets geofence zone upper right corner Y coordinate (latitude) for a Rectangular zone.[[File:Drawing a Rectangle Geofence.gif\|alt=\|center\|Rectangle Geofence\|link=https://wiki.teltonika-gps.com/view/File:Drawing_a_Rectangle_Geofence.gif]]
			[[Category:FMB640 Configuration]]

Mantas.zemaitis at 13:56, 24 July 2020

2020-07-24T13:56:31Z

← Older revision		Revision as of 16:56, 24 July 2020
Line 1:		Line 1:
	[[Image:Fmb120_geofence_border.png\|400px\|right\|link=https://wiki.teltonika-gps.com/view/File:Fmb120_geofence_border.png]]{{{model\|FMB640}}} has 100 configurable Geofence zones and it can generate an event when a defined Geofence zone border is crossed.		[[Image:Fmb120_geofence_border.png\|400px\|right\|link=https://wiki.teltonika-gps.com/view/File:Fmb120_geofence_border.png]]{{{model\|FMB640}}} has 100 configurable Geofence zones and it can generate an event when a defined Geofence zone border is crossed.
	''Frame border'' is an additional border around Geofence zone used to prevent false events when object stops on the border of the area and as a result records are made inside and outside the defined area because of GNSS errors. The event is generated only when both (Geofence and frame) 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 a rectangle or a circle as defined by the user.<br />Priority of Geofence event is categorized into Low, High or Panic levels. These levels define the priority of event information that is sent to the server. For more details about priorities look in {{{ctrIO\|[[FMB640_I/O_settings#Operands\|FMB640 I/O settings]]}}}.<br />''Generate event'' allows to choose when record will be generated.<br />''Eventual records'' controls where scenario status value appears: when disabled it will exist in each AVL record and when enabled the value will be appended only to eventual records.<br />''OverSpeeding'' helps to configure OverSpeeding scenarios separately for each different ''Geozone''. Regular OverSpeeding and geozones' OverSpeeding function independently. If digital output control is enabled in a regular OverSpeeding scenario, geozones OverSpeeding scenario will control it too i.e when the device is in more than one geozone and OverSpeeding is detected in any zone then the digital output turns on. Digital output turns off only when OverSpeeding is not detected anywhere.<br />{{{model\|FMB640}}} has 100 configurable Geofence zones and it can generate an event when a defined Geofence zone border is crossed.		''Frame border'' is an additional border around Geofence zone used to prevent false events when object stops on the border of the area and as a result records are made inside and outside the defined area because of GNSS errors. The event is generated only when both (Geofence and frame) 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 a rectangle or a circle as defined by the user.<br />Priority of Geofence event is categorized into Low, High or Panic levels. These levels define the priority of event information that is sent to the server. For more details about priorities look in {{{ctrIO\|[[FMB640_I/O_settings#Operands\|FMB640 I/O settings]]}}}.<br />''Generate event'' allows to choose when record will be generated.<br />''Eventual records'' controls where scenario status value appears: when disabled it will exist in each AVL record and when enabled the value will be appended only to eventual records.<br />''OverSpeeding'' helps to configure OverSpeeding scenarios separately for each different ''Geozone''. Regular OverSpeeding and geozones' OverSpeeding function independently. If digital output control is enabled in a regular OverSpeeding scenario, geozones OverSpeeding scenario will control it too i.e when the device is in more than one geozone and OverSpeeding is detected in any zone then the digital output turns on. Digital output turns off only when OverSpeeding is not detected anywhere.<br /><br />''X1'' is used to set geofence zone left bottom corner X coordinate (longitude) while ''Y1'' is used to set Y coordinate (latitude).<br />''X2'' or ''R'' are used to set accordingly geofence zone upper right corner X coordinate (longitude) when Rectangular zone is used or circle radius when Circular zone is used. ''Y2'' sets geofence zone upper right corner Y coordinate (latitude) for a Rectangular zone.[[File:Drawing a Rectangle Geofence.gif\|alt=\|center\|Rectangle Geofence\|link=https://wiki.teltonika-gps.com/view/File:Drawing_a_Rectangle_Geofence.gif]]
	''Frame border'' is an additional border around Geofence zone used to prevent false events when object stops on the border of the area and as a result records are made inside and outside the defined area because of GNSS errors. The event is generated only when both (Geofence and frame) 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 a rectangle or a circle as defined by the user.<br/>Priority of Geofence event is categorized into Low, High or Panic levels. These levels define the priority of event information that is sent to the server. For more details about priorities look in {{{ctrIO\|[[FMB640_I/O_settings#Operands\|FMB640 I/O settings]]}}}.<br/>''Generate event'' allows to choose when record will be generated.<br/>''Eventual records'' controls where scenario status value appears: when disabled it will exist in each AVL record and when enabled the value will be appended only to eventual records.<br/>''OverSpeeding'' helps to configure OverSpeeding scenarios separately for each different ''Geozone''. Regular OverSpeeding and geozones' OverSpeeding function independently. If digital output control is enabled in a regular OverSpeeding scenario, geozones OverSpeeding scenario will control it too i.e when the device is in more than one geozone and OverSpeeding is detected in any zone then the digital output turns on. Digital output turns off only when OverSpeeding is not detected anywhere.<br/><br/>''X1'' is used to set geofence zone left bottom corner X coordinate (longitude) while ''Y1'' is used to set Y coordinate (latitude).<br/>''X2'' or ''R'' are used to set accordingly geofence zone upper right corner X coordinate (longitude) when Rectangular zone is used or circle radius when Circular zone is used. ''Y2'' sets geofence zone upper right corner Y coordinate (latitude) for a Rectangular zone.{{{model\|FMB640}}} has 100 configurable Geofence zones and it can generate an event when a defined Geofence zone border is crossed.
	''Frame border'' is an additional border around Geofence zone used to prevent false events when object stops on the border of the area and as a result records are made inside and outside the defined area because of GNSS errors. The event is generated only when both (Geofence and frame) 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 a rectangle or a circle as defined by the user.<br/>Priority of Geofence event is categorized into Low, High or Panic levels. These levels define the priority of event information that is sent to the server. For more details about priorities look in {{{ctrIO\|[[FMB640_I/O_settings#Operands\|FMB640 I/O settings]]}}}.<br/>''Generate event'' allows to choose when record will be generated.<br/>''Eventual records'' controls where scenario status value appears: when disabled it will exist in each AVL record and when enabled the value will be appended only to eventual records.<br/>''OverSpeeding'' helps to configure OverSpeeding scenarios separately for each different ''Geozone''. Regular OverSpeeding and geozones' OverSpeeding function independently. If digital output control is enabled in a regular OverSpeeding scenario, geozones OverSpeeding scenario will control it too i.e when the device is in more than one geozone and OverSpeeding is detected in any zone then the digital output turns on. Digital output turns off only when OverSpeeding is not detected anywhere.<br/><br/>''X1'' is used to set geofence zone left bottom corner X coordinate (longitude) while ''Y1'' is used to set Y coordinate (latitude).<br/>''X2'' or ''R'' are used to set accordingly geofence zone upper right corner X coordinate (longitude) when Rectangular zone is used or circle radius when Circular zone is used. ''Y2'' sets geofence zone upper right corner Y coordinate (latitude) for a Rectangular zone.[[File:Drawing a Rectangle Geofence.gif\|alt=\|center\|Rectangle Geofence\|link=https://wiki.teltonika-gps.com/view/File:Drawing_a_Rectangle_Geofence.gif]]

Mantas.zemaitis at 13:56, 24 July 2020

2020-07-24T13:56:01Z

← Older revision		Revision as of 16:56, 24 July 2020
Line 1:		Line 1:
	[[Image:Fmb120_geofence_border.png\|400px\|right\|link=https://wiki.teltonika-gps.com/view/File:Fmb120_geofence_border.png]]{{{model\|FMB640}}} has 100 configurable Geofence zones and it can generate an event when a defined Geofence zone border is crossed.		[[Image:Fmb120_geofence_border.png\|400px\|right\|link=https://wiki.teltonika-gps.com/view/File:Fmb120_geofence_border.png]]{{{model\|FMB640}}} has 100 configurable Geofence zones and it can generate an event when a defined Geofence zone border is crossed.
	''Frame border'' is an additional border around Geofence zone used to prevent false events when object stops on the border of the area and as a result records are made inside and outside the defined area because of GNSS errors. The event is generated only when both (Geofence and frame) 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 a rectangle or a circle as defined by the user.<br/>Priority of Geofence event is categorized into Low, High or Panic levels. These levels define the priority of event information that is sent to the server. For more details about priorities look in {{{ctrIO\|[[FMB640_I/O_settings#Operands\|FMB640 I/O settings]]}}}.<br/>''Generate event'' allows to choose when record will be generated.<br/>''Eventual records'' controls where scenario status value appears: when disabled it will exist in each AVL record and when enabled the value will be appended only to eventual records.<br/>''OverSpeeding'' helps to configure OverSpeeding scenarios separately for each different ''Geozone''. Regular OverSpeeding and geozones' OverSpeeding function independently. If digital output control is enabled in a regular OverSpeeding scenario, geozones OverSpeeding scenario will control it too i.e when the device is in more than one geozone and OverSpeeding is detected in any zone then the digital output turns on. Digital output turns off only when OverSpeeding is not detected anywhere.<br/><br/>''X1'' is used to set geofence zone left bottom corner X coordinate (longitude) while ''Y1'' is used to set Y coordinate (latitude).<br/>''X2'' or ''R'' are used to set accordingly geofence zone upper right corner X coordinate (longitude) when Rectangular zone is used or circle radius when Circular zone is used. ''Y2'' sets geofence zone upper right corner Y coordinate (latitude) for a Rectangular zone.{{{model\|FMB640}}} has 100 configurable Geofence zones and it can generate an event when a defined Geofence zone border is crossed.		''Frame border'' is an additional border around Geofence zone used to prevent false events when object stops on the border of the area and as a result records are made inside and outside the defined area because of GNSS errors. The event is generated only when both (Geofence and frame) 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 a rectangle or a circle as defined by the user.<br />Priority of Geofence event is categorized into Low, High or Panic levels. These levels define the priority of event information that is sent to the server. For more details about priorities look in {{{ctrIO\|[[FMB640_I/O_settings#Operands\|FMB640 I/O settings]]}}}.<br />''Generate event'' allows to choose when record will be generated.<br />''Eventual records'' controls where scenario status value appears: when disabled it will exist in each AVL record and when enabled the value will be appended only to eventual records.<br />''OverSpeeding'' helps to configure OverSpeeding scenarios separately for each different ''Geozone''. Regular OverSpeeding and geozones' OverSpeeding function independently. If digital output control is enabled in a regular OverSpeeding scenario, geozones OverSpeeding scenario will control it too i.e when the device is in more than one geozone and OverSpeeding is detected in any zone then the digital output turns on. Digital output turns off only when OverSpeeding is not detected anywhere.<br />{{{model\|FMB640}}} has 100 configurable Geofence zones and it can generate an event when a defined Geofence zone border is crossed.
	''Frame border'' is an additional border around Geofence zone used to prevent false events when object stops on the border of the area and as a result records are made inside and outside the defined area because of GNSS errors. The event is generated only when both (Geofence and frame) 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 a rectangle or a circle as defined by the user.<br/>Priority of Geofence event is categorized into Low, High or Panic levels. These levels define the priority of event information that is sent to the server. For more details about priorities look in {{{ctrIO\|[[FMB640_I/O_settings#Operands\|FMB640 I/O settings]]}}}.<br/>''Generate event'' allows to choose when record will be generated.<br/>''Eventual records'' controls where scenario status value appears: when disabled it will exist in each AVL record and when enabled the value will be appended only to eventual records.<br/>''OverSpeeding'' helps to configure OverSpeeding scenarios separately for each different ''Geozone''. Regular OverSpeeding and geozones' OverSpeeding function independently. If digital output control is enabled in a regular OverSpeeding scenario, geozones OverSpeeding scenario will control it too i.e when the device is in more than one geozone and OverSpeeding is detected in any zone then the digital output turns on. Digital output turns off only when OverSpeeding is not detected anywhere.<br/><br/>''X1'' is used to set geofence zone left bottom corner X coordinate (longitude) while ''Y1'' is used to set Y coordinate (latitude).<br/>''X2'' or ''R'' are used to set accordingly geofence zone upper right corner X coordinate (longitude) when Rectangular zone is used or circle radius when Circular zone is used. ''Y2'' sets geofence zone upper right corner Y coordinate (latitude) for a Rectangular zone.{{{model\|FMB640}}} has 100 configurable Geofence zones and it can generate an event when a defined Geofence zone border is crossed.
	''Frame border'' is an additional border around Geofence zone used to prevent false events when object stops on the border of the area and as a result records are made inside and outside the defined area because of GNSS errors. The event is generated only when both (Geofence and frame) 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 a rectangle or a circle as defined by the user.<br/>Priority of Geofence event is categorized into Low, High or Panic levels. These levels define the priority of event information that is sent to the server. For more details about priorities look in {{{ctrIO\|[[FMB640_I/O_settings#Operands\|FMB640 I/O settings]]}}}.<br/>''Generate event'' allows to choose when record will be generated.<br/>''Eventual records'' controls where scenario status value appears: when disabled it will exist in each AVL record and when enabled the value will be appended only to eventual records.<br/>''OverSpeeding'' helps to configure OverSpeeding scenarios separately for each different ''Geozone''. Regular OverSpeeding and geozones' OverSpeeding function independently. If digital output control is enabled in a regular OverSpeeding scenario, geozones OverSpeeding scenario will control it too i.e when the device is in more than one geozone and OverSpeeding is detected in any zone then the digital output turns on. Digital output turns off only when OverSpeeding is not detected anywhere.<br/><br/>''X1'' is used to set geofence zone left bottom corner X coordinate (longitude) while ''Y1'' is used to set Y coordinate (latitude).<br/>''X2'' or ''R'' are used to set accordingly geofence zone upper right corner X coordinate (longitude) when Rectangular zone is used or circle radius when Circular zone is used. ''Y2'' sets geofence zone upper right corner Y coordinate (latitude) for a Rectangular zone.{{{model\|FMB640}}} has 100 configurable Geofence zones and it can generate an event when a defined Geofence zone border is crossed.
	''Frame border'' is an additional border around Geofence zone used to prevent false events when object stops on the border of the area and as a result records are made inside and outside the defined area because of GNSS errors. The event is generated only when both (Geofence and frame) 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 a rectangle or a circle as defined by the user.<br/>Priority of Geofence event is categorized into Low, High or Panic levels. These levels define the priority of event information that is sent to the server. For more details about priorities look in {{{ctrIO\|[[FMB640_I/O_settings#Operands\|FMB640 I/O settings]]}}}.<br/>''Generate event'' allows to choose when record will be generated.<br/>''Eventual records'' controls where scenario status value appears: when disabled it will exist in each AVL record and when enabled the value will be appended only to eventual records.<br/>''OverSpeeding'' helps to configure OverSpeeding scenarios separately for each different ''Geozone''. Regular OverSpeeding and geozones' OverSpeeding function independently. If digital output control is enabled in a regular OverSpeeding scenario, geozones OverSpeeding scenario will control it too i.e when the device is in more than one geozone and OverSpeeding is detected in any zone then the digital output turns on. Digital output turns off only when OverSpeeding is not detected anywhere.<br/><br/>''X1'' is used to set geofence zone left bottom corner X coordinate (longitude) while ''Y1'' is used to set Y coordinate (latitude).<br/>''X2'' or ''R'' are used to set accordingly geofence zone upper right corner X coordinate (longitude) when Rectangular zone is used or circle radius when Circular zone is used. ''Y2'' sets geofence zone upper right corner Y coordinate (latitude) for a Rectangular zone.{{{model\|FMB640}}} has 100 configurable Geofence zones and it can generate an event when a defined Geofence zone border is crossed.
	''Frame border'' is an additional border around Geofence zone used to prevent false events when object stops on the border of the area and as a result records are made inside and outside the defined area because of GNSS errors. The event is generated only when both (Geofence and frame) 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 a rectangle or a circle as defined by the user.<br/>Priority of Geofence event is categorized into Low, High or Panic levels. These levels define the priority of event information that is sent to the server. For more details about priorities look in {{{ctrIO\|[[FMB640_I/O_settings#Operands\|FMB640 I/O settings]]}}}.<br/>''Generate event'' allows to choose when record will be generated.<br/>''Eventual records'' controls where scenario status value appears: when disabled it will exist in each AVL record and when enabled the value will be appended only to eventual records.<br/>''OverSpeeding'' helps to configure OverSpeeding scenarios separately for each different ''Geozone''. Regular OverSpeeding and geozones' OverSpeeding function independently. If digital output control is enabled in a regular OverSpeeding scenario, geozones OverSpeeding scenario will control it too i.e when the device is in more than one geozone and OverSpeeding is detected in any zone then the digital output turns on. Digital output turns off only when OverSpeeding is not detected anywhere.<br/><br/>''X1'' is used to set geofence zone left bottom corner X coordinate (longitude) while ''Y1'' is used to set Y coordinate (latitude).<br/>''X2'' or ''R'' are used to set accordingly geofence zone upper right corner X coordinate (longitude) when Rectangular zone is used or circle radius when Circular zone is used. ''Y2'' sets geofence zone upper right corner Y coordinate (latitude) for a Rectangular zone.{{{model\|FMB640}}} has 100 configurable Geofence zones and it can generate an event when a defined Geofence zone border is crossed.
	''Frame border'' is an additional border around Geofence zone used to prevent false events when object stops on the border of the area and as a result records are made inside and outside the defined area because of GNSS errors. The event is generated only when both (Geofence and frame) 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 a rectangle or a circle as defined by the user.<br/>Priority of Geofence event is categorized into Low, High or Panic levels. These levels define the priority of event information that is sent to the server. For more details about priorities look in {{{ctrIO\|[[FMB640_I/O_settings#Operands\|FMB640 I/O settings]]}}}.<br/>''Generate event'' allows to choose when record will be generated.<br/>''Eventual records'' controls where scenario status value appears: when disabled it will exist in each AVL record and when enabled the value will be appended only to eventual records.<br/>''OverSpeeding'' helps to configure OverSpeeding scenarios separately for each different ''Geozone''. Regular OverSpeeding and geozones' OverSpeeding function independently. If digital output control is enabled in a regular OverSpeeding scenario, geozones OverSpeeding scenario will control it too i.e when the device is in more than one geozone and OverSpeeding is detected in any zone then the digital output turns on. Digital output turns off only when OverSpeeding is not detected anywhere.<br/><br/>''X1'' is used to set geofence zone left bottom corner X coordinate (longitude) while ''Y1'' is used to set Y coordinate (latitude).<br/>''X2'' or ''R'' are used to set accordingly geofence zone upper right corner X coordinate (longitude) when Rectangular zone is used or circle radius when Circular zone is used. ''Y2'' sets geofence zone upper right corner Y coordinate (latitude) for a Rectangular zone.{{{model\|FMB640}}} has 100 configurable Geofence zones and it can generate an event when a defined Geofence zone border is crossed.
	''Frame border'' is an additional border around Geofence zone used to prevent false events when object stops on the border of the area and as a result records are made inside and outside the defined area because of GNSS errors. The event is generated only when both (Geofence and frame) 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 a rectangle or a circle as defined by the user.<br/>Priority of Geofence event is categorized into Low, High or Panic levels. These levels define the priority of event information that is sent to the server. For more details about priorities look in {{{ctrIO\|[[FMB640_I/O_settings#Operands\|FMB640 I/O settings]]}}}.<br/>''Generate event'' allows to choose when record will be generated.<br/>''Eventual records'' controls where scenario status value appears: when disabled it will exist in each AVL record and when enabled the value will be appended only to eventual records.<br/>''OverSpeeding'' helps to configure OverSpeeding scenarios separately for each different ''Geozone''. Regular OverSpeeding and geozones' OverSpeeding function independently. If digital output control is enabled in a regular OverSpeeding scenario, geozones OverSpeeding scenario will control it too i.e when the device is in more than one geozone and OverSpeeding is detected in any zone then the digital output turns on. Digital output turns off only when OverSpeeding is not detected anywhere.<br/><br/>''X1'' is used to set geofence zone left bottom corner X coordinate (longitude) while ''Y1'' is used to set Y coordinate (latitude).<br/>''X2'' or ''R'' are used to set accordingly geofence zone upper right corner X coordinate (longitude) when Rectangular zone is used or circle radius when Circular zone is used. ''Y2'' sets geofence zone upper right corner Y coordinate (latitude) for a Rectangular zone.{{{model\|FMB640}}} has 100 configurable Geofence zones and it can generate an event when a defined Geofence zone border is crossed.		''Frame border'' is an additional border around Geofence zone used to prevent false events when object stops on the border of the area and as a result records are made inside and outside the defined area because of GNSS errors. The event is generated only when both (Geofence and frame) 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 a rectangle or a circle as defined by the user.<br/>Priority of Geofence event is categorized into Low, High or Panic levels. These levels define the priority of event information that is sent to the server. For more details about priorities look in {{{ctrIO\|[[FMB640_I/O_settings#Operands\|FMB640 I/O settings]]}}}.<br/>''Generate event'' allows to choose when record will be generated.<br/>''Eventual records'' controls where scenario status value appears: when disabled it will exist in each AVL record and when enabled the value will be appended only to eventual records.<br/>''OverSpeeding'' helps to configure OverSpeeding scenarios separately for each different ''Geozone''. Regular OverSpeeding and geozones' OverSpeeding function independently. If digital output control is enabled in a regular OverSpeeding scenario, geozones OverSpeeding scenario will control it too i.e when the device is in more than one geozone and OverSpeeding is detected in any zone then the digital output turns on. Digital output turns off only when OverSpeeding is not detected anywhere.<br/><br/>''X1'' is used to set geofence zone left bottom corner X coordinate (longitude) while ''Y1'' is used to set Y coordinate (latitude).<br/>''X2'' or ''R'' are used to set accordingly geofence zone upper right corner X coordinate (longitude) when Rectangular zone is used or circle radius when Circular zone is used. ''Y2'' sets geofence zone upper right corner Y coordinate (latitude) for a Rectangular zone.{{{model\|FMB640}}} has 100 configurable Geofence zones and it can generate an event when a defined Geofence zone border is crossed.
	''Frame border'' is an additional border around Geofence zone used to prevent false events when object stops on the border of the area and as a result records are made inside and outside the defined area because of GNSS errors. The event is generated only when both (Geofence and frame) 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 a rectangle or a circle as defined by the user.<br/>Priority of Geofence event is categorized into Low, High or Panic levels. These levels define the priority of event information that is sent to the server. For more details about priorities look in {{{ctrIO\|[[FMB640_I/O_settings#Operands\|FMB640 I/O settings]]}}}.<br/>''Generate event'' allows to choose when record will be generated.<br/>''Eventual records'' controls where scenario status value appears: when disabled it will exist in each AVL record and when enabled the value will be appended only to eventual records.<br/>''OverSpeeding'' helps to configure OverSpeeding scenarios separately for each different ''Geozone''. Regular OverSpeeding and geozones' OverSpeeding function independently. If digital output control is enabled in a regular OverSpeeding scenario, geozones OverSpeeding scenario will control it too i.e when the device is in more than one geozone and OverSpeeding is detected in any zone then the digital output turns on. Digital output turns off only when OverSpeeding is not detected anywhere.<br/><br/>''X1'' is used to set geofence zone left bottom corner X coordinate (longitude) while ''Y1'' is used to set Y coordinate (latitude).<br/>''X2'' or ''R'' are used to set accordingly geofence zone upper right corner X coordinate (longitude) when Rectangular zone is used or circle radius when Circular zone is used. ''Y2'' sets geofence zone upper right corner Y coordinate (latitude) for a Rectangular zone.[[File:Drawing a Rectangle Geofence.gif\|alt=\|center\|Rectangle Geofence\|link=https://wiki.teltonika-gps.com/view/File:Drawing_a_Rectangle_Geofence.gif]]		''Frame border'' is an additional border around Geofence zone used to prevent false events when object stops on the border of the area and as a result records are made inside and outside the defined area because of GNSS errors. The event is generated only when both (Geofence and frame) 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 a rectangle or a circle as defined by the user.<br/>Priority of Geofence event is categorized into Low, High or Panic levels. These levels define the priority of event information that is sent to the server. For more details about priorities look in {{{ctrIO\|[[FMB640_I/O_settings#Operands\|FMB640 I/O settings]]}}}.<br/>''Generate event'' allows to choose when record will be generated.<br/>''Eventual records'' controls where scenario status value appears: when disabled it will exist in each AVL record and when enabled the value will be appended only to eventual records.<br/>''OverSpeeding'' helps to configure OverSpeeding scenarios separately for each different ''Geozone''. Regular OverSpeeding and geozones' OverSpeeding function independently. If digital output control is enabled in a regular OverSpeeding scenario, geozones OverSpeeding scenario will control it too i.e when the device is in more than one geozone and OverSpeeding is detected in any zone then the digital output turns on. Digital output turns off only when OverSpeeding is not detected anywhere.<br/><br/>''X1'' is used to set geofence zone left bottom corner X coordinate (longitude) while ''Y1'' is used to set Y coordinate (latitude).<br/>''X2'' or ''R'' are used to set accordingly geofence zone upper right corner X coordinate (longitude) when Rectangular zone is used or circle radius when Circular zone is used. ''Y2'' sets geofence zone upper right corner Y coordinate (latitude) for a Rectangular zone.[[File:Drawing a Rectangle Geofence.gif\|alt=\|center\|Rectangle Geofence\|link=https://wiki.teltonika-gps.com/view/File:Drawing_a_Rectangle_Geofence.gif]]

Mantas.zemaitis at 13:54, 24 July 2020

2020-07-24T13:54:35Z

← Older revision		Revision as of 16:54, 24 July 2020
Line 7:		Line 7:
	''Frame border'' is an additional border around Geofence zone used to prevent false events when object stops on the border of the area and as a result records are made inside and outside the defined area because of GNSS errors. The event is generated only when both (Geofence and frame) 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 a rectangle or a circle as defined by the user.<br/>Priority of Geofence event is categorized into Low, High or Panic levels. These levels define the priority of event information that is sent to the server. For more details about priorities look in {{{ctrIO\|[[FMB640_I/O_settings#Operands\|FMB640 I/O settings]]}}}.<br/>''Generate event'' allows to choose when record will be generated.<br/>''Eventual records'' controls where scenario status value appears: when disabled it will exist in each AVL record and when enabled the value will be appended only to eventual records.<br/>''OverSpeeding'' helps to configure OverSpeeding scenarios separately for each different ''Geozone''. Regular OverSpeeding and geozones' OverSpeeding function independently. If digital output control is enabled in a regular OverSpeeding scenario, geozones OverSpeeding scenario will control it too i.e when the device is in more than one geozone and OverSpeeding is detected in any zone then the digital output turns on. Digital output turns off only when OverSpeeding is not detected anywhere.<br/><br/>''X1'' is used to set geofence zone left bottom corner X coordinate (longitude) while ''Y1'' is used to set Y coordinate (latitude).<br/>''X2'' or ''R'' are used to set accordingly geofence zone upper right corner X coordinate (longitude) when Rectangular zone is used or circle radius when Circular zone is used. ''Y2'' sets geofence zone upper right corner Y coordinate (latitude) for a Rectangular zone.{{{model\|FMB640}}} has 100 configurable Geofence zones and it can generate an event when a defined Geofence zone border is crossed.		''Frame border'' is an additional border around Geofence zone used to prevent false events when object stops on the border of the area and as a result records are made inside and outside the defined area because of GNSS errors. The event is generated only when both (Geofence and frame) 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 a rectangle or a circle as defined by the user.<br/>Priority of Geofence event is categorized into Low, High or Panic levels. These levels define the priority of event information that is sent to the server. For more details about priorities look in {{{ctrIO\|[[FMB640_I/O_settings#Operands\|FMB640 I/O settings]]}}}.<br/>''Generate event'' allows to choose when record will be generated.<br/>''Eventual records'' controls where scenario status value appears: when disabled it will exist in each AVL record and when enabled the value will be appended only to eventual records.<br/>''OverSpeeding'' helps to configure OverSpeeding scenarios separately for each different ''Geozone''. Regular OverSpeeding and geozones' OverSpeeding function independently. If digital output control is enabled in a regular OverSpeeding scenario, geozones OverSpeeding scenario will control it too i.e when the device is in more than one geozone and OverSpeeding is detected in any zone then the digital output turns on. Digital output turns off only when OverSpeeding is not detected anywhere.<br/><br/>''X1'' is used to set geofence zone left bottom corner X coordinate (longitude) while ''Y1'' is used to set Y coordinate (latitude).<br/>''X2'' or ''R'' are used to set accordingly geofence zone upper right corner X coordinate (longitude) when Rectangular zone is used or circle radius when Circular zone is used. ''Y2'' sets geofence zone upper right corner Y coordinate (latitude) for a Rectangular zone.{{{model\|FMB640}}} has 100 configurable Geofence zones and it can generate an event when a defined Geofence zone border is crossed.
	''Frame border'' is an additional border around Geofence zone used to prevent false events when object stops on the border of the area and as a result records are made inside and outside the defined area because of GNSS errors. The event is generated only when both (Geofence and frame) 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 a rectangle or a circle as defined by the user.<br/>Priority of Geofence event is categorized into Low, High or Panic levels. These levels define the priority of event information that is sent to the server. For more details about priorities look in {{{ctrIO\|[[FMB640_I/O_settings#Operands\|FMB640 I/O settings]]}}}.<br/>''Generate event'' allows to choose when record will be generated.<br/>''Eventual records'' controls where scenario status value appears: when disabled it will exist in each AVL record and when enabled the value will be appended only to eventual records.<br/>''OverSpeeding'' helps to configure OverSpeeding scenarios separately for each different ''Geozone''. Regular OverSpeeding and geozones' OverSpeeding function independently. If digital output control is enabled in a regular OverSpeeding scenario, geozones OverSpeeding scenario will control it too i.e when the device is in more than one geozone and OverSpeeding is detected in any zone then the digital output turns on. Digital output turns off only when OverSpeeding is not detected anywhere.<br/><br/>''X1'' is used to set geofence zone left bottom corner X coordinate (longitude) while ''Y1'' is used to set Y coordinate (latitude).<br/>''X2'' or ''R'' are used to set accordingly geofence zone upper right corner X coordinate (longitude) when Rectangular zone is used or circle radius when Circular zone is used. ''Y2'' sets geofence zone upper right corner Y coordinate (latitude) for a Rectangular zone.{{{model\|FMB640}}} has 100 configurable Geofence zones and it can generate an event when a defined Geofence zone border is crossed.		''Frame border'' is an additional border around Geofence zone used to prevent false events when object stops on the border of the area and as a result records are made inside and outside the defined area because of GNSS errors. The event is generated only when both (Geofence and frame) 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 a rectangle or a circle as defined by the user.<br/>Priority of Geofence event is categorized into Low, High or Panic levels. These levels define the priority of event information that is sent to the server. For more details about priorities look in {{{ctrIO\|[[FMB640_I/O_settings#Operands\|FMB640 I/O settings]]}}}.<br/>''Generate event'' allows to choose when record will be generated.<br/>''Eventual records'' controls where scenario status value appears: when disabled it will exist in each AVL record and when enabled the value will be appended only to eventual records.<br/>''OverSpeeding'' helps to configure OverSpeeding scenarios separately for each different ''Geozone''. Regular OverSpeeding and geozones' OverSpeeding function independently. If digital output control is enabled in a regular OverSpeeding scenario, geozones OverSpeeding scenario will control it too i.e when the device is in more than one geozone and OverSpeeding is detected in any zone then the digital output turns on. Digital output turns off only when OverSpeeding is not detected anywhere.<br/><br/>''X1'' is used to set geofence zone left bottom corner X coordinate (longitude) while ''Y1'' is used to set Y coordinate (latitude).<br/>''X2'' or ''R'' are used to set accordingly geofence zone upper right corner X coordinate (longitude) when Rectangular zone is used or circle radius when Circular zone is used. ''Y2'' sets geofence zone upper right corner Y coordinate (latitude) for a Rectangular zone.{{{model\|FMB640}}} has 100 configurable Geofence zones and it can generate an event when a defined Geofence zone border is crossed.
	''Frame border'' is an additional border around Geofence zone used to prevent false events when object stops on the border of the area and as a result records are made inside and outside the defined area because of GNSS errors. The event is generated only when both (Geofence and frame) 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 a rectangle or a circle as defined by the user.<br/>Priority of Geofence event is categorized into Low, High or Panic levels. These levels define the priority of event information that is sent to the server. For more details about priorities look in {{{ctrIO\|[[FMB640_I/O_settings#Operands\|FMB640 I/O settings]]}}}.<br/>''Generate event'' allows to choose when record will be generated.<br/>''Eventual records'' controls where scenario status value appears: when disabled it will exist in each AVL record and when enabled the value will be appended only to eventual records.<br/>''OverSpeeding'' helps to configure OverSpeeding scenarios separately for each different ''Geozone''. Regular OverSpeeding and geozones' OverSpeeding function independently. If digital output control is enabled in a regular OverSpeeding scenario, geozones OverSpeeding scenario will control it too i.e when the device is in more than one geozone and OverSpeeding is detected in any zone then the digital output turns on. Digital output turns off only when OverSpeeding is not detected anywhere.<br/><br/>''X1'' is used to set geofence zone left bottom corner X coordinate (longitude) while ''Y1'' is used to set Y coordinate (latitude).<br/>''X2'' or ''R'' are used to set accordingly geofence zone upper right corner X coordinate (longitude) when Rectangular zone is used or circle radius when Circular zone is used. ''Y2'' sets geofence zone upper right corner Y coordinate (latitude) for a Rectangular zone.[[File:Drawing a Rectangle Geofence.gif\|alt=\|center\|Rectangle Geofence\|link=https://wiki.teltonika-gps.com/view/File:Drawing_a_Rectangle_Geofence.gif]]~~<br />~~		''Frame border'' is an additional border around Geofence zone used to prevent false events when object stops on the border of the area and as a result records are made inside and outside the defined area because of GNSS errors. The event is generated only when both (Geofence and frame) 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 a rectangle or a circle as defined by the user.<br/>Priority of Geofence event is categorized into Low, High or Panic levels. These levels define the priority of event information that is sent to the server. For more details about priorities look in {{{ctrIO\|[[FMB640_I/O_settings#Operands\|FMB640 I/O settings]]}}}.<br/>''Generate event'' allows to choose when record will be generated.<br/>''Eventual records'' controls where scenario status value appears: when disabled it will exist in each AVL record and when enabled the value will be appended only to eventual records.<br/>''OverSpeeding'' helps to configure OverSpeeding scenarios separately for each different ''Geozone''. Regular OverSpeeding and geozones' OverSpeeding function independently. If digital output control is enabled in a regular OverSpeeding scenario, geozones OverSpeeding scenario will control it too i.e when the device is in more than one geozone and OverSpeeding is detected in any zone then the digital output turns on. Digital output turns off only when OverSpeeding is not detected anywhere.<br/><br/>''X1'' is used to set geofence zone left bottom corner X coordinate (longitude) while ''Y1'' is used to set Y coordinate (latitude).<br/>''X2'' or ''R'' are used to set accordingly geofence zone upper right corner X coordinate (longitude) when Rectangular zone is used or circle radius when Circular zone is used. ''Y2'' sets geofence zone upper right corner Y coordinate (latitude) for a Rectangular zone.[[File:Drawing a Rectangle Geofence.gif\|alt=\|center\|Rectangle Geofence\|link=https://wiki.teltonika-gps.com/view/File:Drawing_a_Rectangle_Geofence.gif]]

Mantas.zemaitis at 13:54, 24 July 2020

2020-07-24T13:54:10Z

← Older revision		Revision as of 16:54, 24 July 2020
Line 1:		Line 1:
	[[File:FMB640 Geofence ~~SETTINGS~~ in ~~Configurator~~.~~png~~\|~~thumb~~\|FMB640 ~~Manual~~ Geofence ~~Settings~~]]		[[Image:Fmb120_geofence_border.png\|400px\|right\|link=https://wiki.teltonika-gps.com/view/File:Fmb120_geofence_border.png]]{{{model\|FMB640}}} has 100 configurable Geofence zones and it can generate an event when a defined Geofence zone border is crossed.
	'''~~Frame Border Size~~ (~~meters~~) ~~setting~~''' ~~defines Manual~~ Geofence ~~border size~~ in ~~meters~~.		''Frame border'' is an additional border around Geofence zone used to prevent false events when object stops on the border of the area and as a result records are made inside and outside the defined area because of GNSS errors. The event is generated only when both (Geofence and frame) 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 a rectangle or a circle as defined by the user.<br/>Priority of Geofence event is categorized into Low, High or Panic levels. These levels define the priority of event information that is sent to the server. For more details about priorities look in {{{ctrIO\|[[FMB640_I/O_settings#Operands\|FMB640 I/O settings]]}}}.<br/>''Generate event'' allows to choose when record will be generated.<br/>''Eventual records'' controls where scenario status value appears: when disabled it will exist in each AVL record and when enabled the value will be appended only to eventual records.<br/>''OverSpeeding'' helps to configure OverSpeeding scenarios separately for each different ''Geozone''. Regular OverSpeeding and geozones' OverSpeeding function independently. If digital output control is enabled in a regular OverSpeeding scenario, geozones OverSpeeding scenario will control it too i.e when the device is in more than one geozone and OverSpeeding is detected in any zone then the digital output turns on. Digital output turns off only when OverSpeeding is not detected anywhere.<br/><br/>''X1'' is used to set geofence zone left bottom corner X coordinate (longitude) while ''Y1'' is used to set Y coordinate (latitude).<br/>''X2'' or ''R'' are used to set accordingly geofence zone upper right corner X coordinate (longitude) when Rectangular zone is used or circle radius when Circular zone is used. ''Y2'' sets geofence zone upper right corner Y coordinate (latitude) for a Rectangular zone.{{{model\|FMB640}}} has 100 configurable Geofence zones and it can generate an event when a defined Geofence zone border is crossed.
			''Frame border'' is an additional border around Geofence zone used to prevent false events when object stops on the border of the area and as a result records are made inside and outside the defined area because of GNSS errors. The event is generated only when both (Geofence and frame) 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 a rectangle or a circle as defined by the user.<br/>Priority of Geofence event is categorized into Low, High or Panic levels. These levels define the priority of event information that is sent to the server. For more details about priorities look in {{{ctrIO\|[[FMB640_I/O_settings#Operands\|FMB640 I/O settings]]}}}.<br/>''Generate event'' allows to choose when record will be generated.<br/>''Eventual records'' controls where scenario status value appears: when disabled it will exist in each AVL record and when enabled the value will be appended only to eventual records.<br/>''OverSpeeding'' helps to configure OverSpeeding scenarios separately for each different ''Geozone''. Regular OverSpeeding and geozones' OverSpeeding function independently. If digital output control is enabled in a regular OverSpeeding scenario, geozones OverSpeeding scenario will control it too i.e when the device is in more than one geozone and OverSpeeding is detected in any zone then the digital output turns on. Digital output turns off only when OverSpeeding is not detected anywhere.<br/><br/>''X1'' is used to set geofence zone left bottom corner X coordinate (longitude) while ''Y1'' is used to set Y coordinate (latitude).<br/>''X2'' or ''R'' are used to set accordingly geofence zone upper right corner X coordinate (longitude) when Rectangular zone is used or circle radius when Circular zone is used. ''Y2'' sets geofence zone upper right corner Y coordinate (latitude) for a Rectangular zone.{{{model\|FMB640}}} has 100 configurable Geofence zones and it can generate an event when a defined Geofence zone border is crossed.
			''Frame border'' is an additional border around Geofence zone used to prevent false events when object stops on the border of the area and as a result records are made inside and outside the defined area because of GNSS errors. The event is generated only when both (Geofence and frame) 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 a rectangle or a circle as defined by the user.<br/>Priority of Geofence event is categorized into Low, High or Panic levels. These levels define the priority of event information that is sent to the server. For more details about priorities look in {{{ctrIO\|[[FMB640_I/O_settings#Operands\|FMB640 I/O settings]]}}}.<br/>''Generate event'' allows to choose when record will be generated.<br/>''Eventual records'' controls where scenario status value appears: when disabled it will exist in each AVL record and when enabled the value will be appended only to eventual records.<br/>''OverSpeeding'' helps to configure OverSpeeding scenarios separately for each different ''Geozone''. Regular OverSpeeding and geozones' OverSpeeding function independently. If digital output control is enabled in a regular OverSpeeding scenario, geozones OverSpeeding scenario will control it too i.e when the device is in more than one geozone and OverSpeeding is detected in any zone then the digital output turns on. Digital output turns off only when OverSpeeding is not detected anywhere.<br/><br/>''X1'' is used to set geofence zone left bottom corner X coordinate (longitude) while ''Y1'' is used to set Y coordinate (latitude).<br/>''X2'' or ''R'' are used to set accordingly geofence zone upper right corner X coordinate (longitude) when Rectangular zone is used or circle radius when Circular zone is used. ''Y2'' sets geofence zone upper right corner Y coordinate (latitude) for a Rectangular zone.{{{model\|FMB640}}} has 100 configurable Geofence zones and it can generate an event when a defined Geofence zone border is crossed.
	'''~~Geozones Overspeeding Dout setting~~''' ~~defines DOUT~~ control in '''~~Manual~~ Geofence ~~Zones~~''' ~~overspeeding~~ scenario, ~~which also~~ can be ~~configured~~ in '''~~Manual Geofence Zones~~''' ~~TAB~~.		''Frame border'' is an additional border around Geofence zone used to prevent false events when object stops on the border of the area and as a result records are made inside and outside the defined area because of GNSS errors. The event is generated only when both (Geofence and frame) 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 a rectangle or a circle as defined by the user.<br/>Priority of Geofence event is categorized into Low, High or Panic levels. These levels define the priority of event information that is sent to the server. For more details about priorities look in {{{ctrIO\|[[FMB640_I/O_settings#Operands\|FMB640 I/O settings]]}}}.<br/>''Generate event'' allows to choose when record will be generated.<br/>''Eventual records'' controls where scenario status value appears: when disabled it will exist in each AVL record and when enabled the value will be appended only to eventual records.<br/>''OverSpeeding'' helps to configure OverSpeeding scenarios separately for each different ''Geozone''. Regular OverSpeeding and geozones' OverSpeeding function independently. If digital output control is enabled in a regular OverSpeeding scenario, geozones OverSpeeding scenario will control it too i.e when the device is in more than one geozone and OverSpeeding is detected in any zone then the digital output turns on. Digital output turns off only when OverSpeeding is not detected anywhere.<br/><br/>''X1'' is used to set geofence zone left bottom corner X coordinate (longitude) while ''Y1'' is used to set Y coordinate (latitude).<br/>''X2'' or ''R'' are used to set accordingly geofence zone upper right corner X coordinate (longitude) when Rectangular zone is used or circle radius when Circular zone is used. ''Y2'' sets geofence zone upper right corner Y coordinate (latitude) for a Rectangular zone.{{{model\|FMB640}}} has 100 configurable Geofence zones and it can generate an event when a defined Geofence zone border is crossed.
			''Frame border'' is an additional border around Geofence zone used to prevent false events when object stops on the border of the area and as a result records are made inside and outside the defined area because of GNSS errors. The event is generated only when both (Geofence and frame) 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 a rectangle or a circle as defined by the user.<br/>Priority of Geofence event is categorized into Low, High or Panic levels. These levels define the priority of event information that is sent to the server. For more details about priorities look in {{{ctrIO\|[[FMB640_I/O_settings#Operands\|FMB640 I/O settings]]}}}.<br/>''Generate event'' allows to choose when record will be generated.<br/>''Eventual records'' controls where scenario status value appears: when disabled it will exist in each AVL record and when enabled the value will be appended only to eventual records.<br/>''OverSpeeding'' helps to configure OverSpeeding scenarios separately for each different ''Geozone''. Regular OverSpeeding and geozones' OverSpeeding function independently. If digital output control is enabled in a regular OverSpeeding scenario, geozones OverSpeeding scenario will control it too i.e when the device is in more than one geozone and OverSpeeding is detected in any zone then the digital output turns on. Digital output turns off only when OverSpeeding is not detected anywhere.<br/><br/>''X1'' is used to set geofence zone left bottom corner X coordinate (longitude) while ''Y1'' is used to set Y coordinate (latitude).<br/>''X2'' or ''R'' are used to set accordingly geofence zone upper right corner X coordinate (longitude) when Rectangular zone is used or circle radius when Circular zone is used. ''Y2'' sets geofence zone upper right corner Y coordinate (latitude) for a Rectangular zone.{{{model\|FMB640}}} has 100 configurable Geofence zones and it can generate an event when a defined Geofence zone border is crossed.
	'''~~DOUT ON Duration~~ (ms)''' ~~defines~~ value in ~~miliseconds~~ for ~~how long DOUT should be active~~.		''Frame border'' is an additional border around Geofence zone used to prevent false events when object stops on the border of the area and as a result records are made inside and outside the defined area because of GNSS errors. The event is generated only when both (Geofence and frame) 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 a rectangle or a circle as defined by the user.<br/>Priority of Geofence event is categorized into Low, High or Panic levels. These levels define the priority of event information that is sent to the server. For more details about priorities look in {{{ctrIO\|[[FMB640_I/O_settings#Operands\|FMB640 I/O settings]]}}}.<br/>''Generate event'' allows to choose when record will be generated.<br/>''Eventual records'' controls where scenario status value appears: when disabled it will exist in each AVL record and when enabled the value will be appended only to eventual records.<br/>''OverSpeeding'' helps to configure OverSpeeding scenarios separately for each different ''Geozone''. Regular OverSpeeding and geozones' OverSpeeding function independently. If digital output control is enabled in a regular OverSpeeding scenario, geozones OverSpeeding scenario will control it too i.e when the device is in more than one geozone and OverSpeeding is detected in any zone then the digital output turns on. Digital output turns off only when OverSpeeding is not detected anywhere.<br/><br/>''X1'' is used to set geofence zone left bottom corner X coordinate (longitude) while ''Y1'' is used to set Y coordinate (latitude).<br/>''X2'' or ''R'' are used to set accordingly geofence zone upper right corner X coordinate (longitude) when Rectangular zone is used or circle radius when Circular zone is used. ''Y2'' sets geofence zone upper right corner Y coordinate (latitude) for a Rectangular zone.{{{model\|FMB640}}} has 100 configurable Geofence zones and it can generate an event when a defined Geofence zone border is crossed.
			''Frame border'' is an additional border around Geofence zone used to prevent false events when object stops on the border of the area and as a result records are made inside and outside the defined area because of GNSS errors. The event is generated only when both (Geofence and frame) 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 a rectangle or a circle as defined by the user.<br/>Priority of Geofence event is categorized into Low, High or Panic levels. These levels define the priority of event information that is sent to the server. For more details about priorities look in {{{ctrIO\|[[FMB640_I/O_settings#Operands\|FMB640 I/O settings]]}}}.<br/>''Generate event'' allows to choose when record will be generated.<br/>''Eventual records'' controls where scenario status value appears: when disabled it will exist in each AVL record and when enabled the value will be appended only to eventual records.<br/>''OverSpeeding'' helps to configure OverSpeeding scenarios separately for each different ''Geozone''. Regular OverSpeeding and geozones' OverSpeeding function independently. If digital output control is enabled in a regular OverSpeeding scenario, geozones OverSpeeding scenario will control it too i.e when the device is in more than one geozone and OverSpeeding is detected in any zone then the digital output turns on. Digital output turns off only when OverSpeeding is not detected anywhere.<br/><br/>''X1'' is used to set geofence zone left bottom corner X coordinate (longitude) while ''Y1'' is used to set Y coordinate (latitude).<br/>''X2'' or ''R'' are used to set accordingly geofence zone upper right corner X coordinate (longitude) when Rectangular zone is used or circle radius when Circular zone is used. ''Y2'' sets geofence zone upper right corner Y coordinate (latitude) for a Rectangular zone.{{{model\|FMB640}}} has 100 configurable Geofence zones and it can generate an event when a defined Geofence zone border is crossed.
	'''~~DOUT OFF Duration~~ (ms)''' ~~defines~~ value in ~~miliseconds~~ for ~~how long DOUT should be inactive~~.		''Frame border'' is an additional border around Geofence zone used to prevent false events when object stops on the border of the area and as a result records are made inside and outside the defined area because of GNSS errors. The event is generated only when both (Geofence and frame) 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 a rectangle or a circle as defined by the user.<br/>Priority of Geofence event is categorized into Low, High or Panic levels. These levels define the priority of event information that is sent to the server. For more details about priorities look in {{{ctrIO\|[[FMB640_I/O_settings#Operands\|FMB640 I/O settings]]}}}.<br/>''Generate event'' allows to choose when record will be generated.<br/>''Eventual records'' controls where scenario status value appears: when disabled it will exist in each AVL record and when enabled the value will be appended only to eventual records.<br/>''OverSpeeding'' helps to configure OverSpeeding scenarios separately for each different ''Geozone''. Regular OverSpeeding and geozones' OverSpeeding function independently. If digital output control is enabled in a regular OverSpeeding scenario, geozones OverSpeeding scenario will control it too i.e when the device is in more than one geozone and OverSpeeding is detected in any zone then the digital output turns on. Digital output turns off only when OverSpeeding is not detected anywhere.<br/><br/>''X1'' is used to set geofence zone left bottom corner X coordinate (longitude) while ''Y1'' is used to set Y coordinate (latitude).<br/>''X2'' or ''R'' are used to set accordingly geofence zone upper right corner X coordinate (longitude) when Rectangular zone is used or circle radius when Circular zone is used. ''Y2'' sets geofence zone upper right corner Y coordinate (latitude) for a Rectangular zone.[[File:Drawing a Rectangle Geofence.gif\|alt=\|center\|Rectangle Geofence\|link=https://wiki.teltonika-gps.com/view/File:Drawing_a_Rectangle_Geofence.gif]]<br />

Mantas.zemaitis: Created page with "FMB640 Manual Geofence Settings '''Frame Border Size (meters) setting''' defines Manual Geofence border size in met..."

2020-07-24T13:50:38Z

Created page with "thumb|FMB640 Manual Geofence Settings '''Frame Border Size (meters) setting''' defines Manual Geofence border size in met..."

New page

[[File:FMB640 Geofence SETTINGS in Configurator.png|thumb|FMB640 Manual Geofence Settings]]
'''Frame Border Size (meters) setting''' defines Manual Geofence border size in meters.

'''Geozones Overspeeding Dout setting''' defines DOUT control in '''Manual Geofence Zones''' overspeeding scenario, which also can be configured in '''Manual Geofence Zones''' TAB.

'''DOUT ON Duration (ms)''' defines value in miliseconds for how long DOUT should be active.

'''DOUT OFF Duration (ms)''' defines value in miliseconds for how long DOUT should be inactive.

← Older revision		Revision as of 16:56, 24 July 2020
Line 1:		Line 1:
	[[Image:Fmb120_geofence_border.png\|400px\|right\|link=https://wiki.teltonika-gps.com/view/File:Fmb120_geofence_border.png]]{{{model\|FMB640}}} has 100 configurable Geofence zones and it can generate an event when a defined Geofence zone border is crossed.		[[Image:Fmb120_geofence_border.png\|400px\|right\|link=https://wiki.teltonika-gps.com/view/File:Fmb120_geofence_border.png]]{{{model\|FMB640}}} has 100 configurable Geofence zones and it can generate an event when a defined Geofence zone border is crossed.
	''Frame border'' is an additional border around Geofence zone used to prevent false events when object stops on the border of the area and as a result records are made inside and outside the defined area because of GNSS errors. The event is generated only when both (Geofence and frame) 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 a rectangle or a circle as defined by the user.<br />Priority of Geofence event is categorized into Low, High or Panic levels. These levels define the priority of event information that is sent to the server. For more details about priorities look in {{{ctrIO\|[[FMB640_I/O_settings#Operands\|FMB640 I/O settings]]}}}.<br />''Generate event'' allows to choose when record will be generated.<br />''Eventual records'' controls where scenario status value appears: when disabled it will exist in each AVL record and when enabled the value will be appended only to eventual records.<br />''OverSpeeding'' helps to configure OverSpeeding scenarios separately for each different ''Geozone''. Regular OverSpeeding and geozones' OverSpeeding function independently. If digital output control is enabled in a regular OverSpeeding scenario, geozones OverSpeeding scenario will control it too i.e when the device is in more than one geozone and OverSpeeding is detected in any zone then the digital output turns on. Digital output turns off only when OverSpeeding is not detected anywhere.<br />{{{model\|FMB640}}} has 100 configurable Geofence zones and it can generate an event when a defined Geofence zone border is crossed.		''Frame border'' is an additional border around Geofence zone used to prevent false events when object stops on the border of the area and as a result records are made inside and outside the defined area because of GNSS errors. The event is generated only when both (Geofence and frame) 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 a rectangle or a circle as defined by the user.<br />Priority of Geofence event is categorized into Low, High or Panic levels. These levels define the priority of event information that is sent to the server. For more details about priorities look in {{{ctrIO\|[[FMB640_I/O_settings#Operands\|FMB640 I/O settings]]}}}.<br />''Generate event'' allows to choose when record will be generated.<br />''Eventual records'' controls where scenario status value appears: when disabled it will exist in each AVL record and when enabled the value will be appended only to eventual records.<br />''OverSpeeding'' helps to configure OverSpeeding scenarios separately for each different ''Geozone''. Regular OverSpeeding and geozones' OverSpeeding function independently. If digital output control is enabled in a regular OverSpeeding scenario, geozones OverSpeeding scenario will control it too i.e when the device is in more than one geozone and OverSpeeding is detected in any zone then the digital output turns on. Digital output turns off only when OverSpeeding is not detected anywhere.<br /><br />''X1'' is used to set geofence zone left bottom corner X coordinate (longitude) while ''Y1'' is used to set Y coordinate (latitude).<br />''X2'' or ''R'' are used to set accordingly geofence zone upper right corner X coordinate (longitude) when Rectangular zone is used or circle radius when Circular zone is used. ''Y2'' sets geofence zone upper right corner Y coordinate (latitude) for a Rectangular zone.[[File:Drawing a Rectangle Geofence.gif\|alt=\|center\|Rectangle Geofence\|link=https://wiki.teltonika-gps.com/view/File:Drawing_a_Rectangle_Geofence.gif]]
	''Frame border'' is an additional border around Geofence zone used to prevent false events when object stops on the border of the area and as a result records are made inside and outside the defined area because of GNSS errors. The event is generated only when both (Geofence and frame) 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 a rectangle or a circle as defined by the user.<br/>Priority of Geofence event is categorized into Low, High or Panic levels. These levels define the priority of event information that is sent to the server. For more details about priorities look in {{{ctrIO\|[[FMB640_I/O_settings#Operands\|FMB640 I/O settings]]}}}.<br/>''Generate event'' allows to choose when record will be generated.<br/>''Eventual records'' controls where scenario status value appears: when disabled it will exist in each AVL record and when enabled the value will be appended only to eventual records.<br/>''OverSpeeding'' helps to configure OverSpeeding scenarios separately for each different ''Geozone''. Regular OverSpeeding and geozones' OverSpeeding function independently. If digital output control is enabled in a regular OverSpeeding scenario, geozones OverSpeeding scenario will control it too i.e when the device is in more than one geozone and OverSpeeding is detected in any zone then the digital output turns on. Digital output turns off only when OverSpeeding is not detected anywhere.<br/><br/>''X1'' is used to set geofence zone left bottom corner X coordinate (longitude) while ''Y1'' is used to set Y coordinate (latitude).<br/>''X2'' or ''R'' are used to set accordingly geofence zone upper right corner X coordinate (longitude) when Rectangular zone is used or circle radius when Circular zone is used. ''Y2'' sets geofence zone upper right corner Y coordinate (latitude) for a Rectangular zone.{{{model\|FMB640}}} has 100 configurable Geofence zones and it can generate an event when a defined Geofence zone border is crossed.
	''Frame border'' is an additional border around Geofence zone used to prevent false events when object stops on the border of the area and as a result records are made inside and outside the defined area because of GNSS errors. The event is generated only when both (Geofence and frame) 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 a rectangle or a circle as defined by the user.<br/>Priority of Geofence event is categorized into Low, High or Panic levels. These levels define the priority of event information that is sent to the server. For more details about priorities look in {{{ctrIO\|[[FMB640_I/O_settings#Operands\|FMB640 I/O settings]]}}}.<br/>''Generate event'' allows to choose when record will be generated.<br/>''Eventual records'' controls where scenario status value appears: when disabled it will exist in each AVL record and when enabled the value will be appended only to eventual records.<br/>''OverSpeeding'' helps to configure OverSpeeding scenarios separately for each different ''Geozone''. Regular OverSpeeding and geozones' OverSpeeding function independently. If digital output control is enabled in a regular OverSpeeding scenario, geozones OverSpeeding scenario will control it too i.e when the device is in more than one geozone and OverSpeeding is detected in any zone then the digital output turns on. Digital output turns off only when OverSpeeding is not detected anywhere.<br/><br/>''X1'' is used to set geofence zone left bottom corner X coordinate (longitude) while ''Y1'' is used to set Y coordinate (latitude).<br/>''X2'' or ''R'' are used to set accordingly geofence zone upper right corner X coordinate (longitude) when Rectangular zone is used or circle radius when Circular zone is used. ''Y2'' sets geofence zone upper right corner Y coordinate (latitude) for a Rectangular zone.[[File:Drawing a Rectangle Geofence.gif\|alt=\|center\|Rectangle Geofence\|link=https://wiki.teltonika-gps.com/view/File:Drawing_a_Rectangle_Geofence.gif]]

← Older revision		Revision as of 16:56, 24 July 2020
Line 1:		Line 1:
	[[Image:Fmb120_geofence_border.png\|400px\|right\|link=https://wiki.teltonika-gps.com/view/File:Fmb120_geofence_border.png]]{{{model\|FMB640}}} has 100 configurable Geofence zones and it can generate an event when a defined Geofence zone border is crossed.		[[Image:Fmb120_geofence_border.png\|400px\|right\|link=https://wiki.teltonika-gps.com/view/File:Fmb120_geofence_border.png]]{{{model\|FMB640}}} has 100 configurable Geofence zones and it can generate an event when a defined Geofence zone border is crossed.
	''Frame border'' is an additional border around Geofence zone used to prevent false events when object stops on the border of the area and as a result records are made inside and outside the defined area because of GNSS errors. The event is generated only when both (Geofence and frame) 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 a rectangle or a circle as defined by the user.<br/>Priority of Geofence event is categorized into Low, High or Panic levels. These levels define the priority of event information that is sent to the server. For more details about priorities look in {{{ctrIO\|[[FMB640_I/O_settings#Operands\|FMB640 I/O settings]]}}}.<br/>''Generate event'' allows to choose when record will be generated.<br/>''Eventual records'' controls where scenario status value appears: when disabled it will exist in each AVL record and when enabled the value will be appended only to eventual records.<br/>''OverSpeeding'' helps to configure OverSpeeding scenarios separately for each different ''Geozone''. Regular OverSpeeding and geozones' OverSpeeding function independently. If digital output control is enabled in a regular OverSpeeding scenario, geozones OverSpeeding scenario will control it too i.e when the device is in more than one geozone and OverSpeeding is detected in any zone then the digital output turns on. Digital output turns off only when OverSpeeding is not detected anywhere.<br/><br/>''X1'' is used to set geofence zone left bottom corner X coordinate (longitude) while ''Y1'' is used to set Y coordinate (latitude).<br/>''X2'' or ''R'' are used to set accordingly geofence zone upper right corner X coordinate (longitude) when Rectangular zone is used or circle radius when Circular zone is used. ''Y2'' sets geofence zone upper right corner Y coordinate (latitude) for a Rectangular zone.{{{model\|FMB640}}} has 100 configurable Geofence zones and it can generate an event when a defined Geofence zone border is crossed.		''Frame border'' is an additional border around Geofence zone used to prevent false events when object stops on the border of the area and as a result records are made inside and outside the defined area because of GNSS errors. The event is generated only when both (Geofence and frame) 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 a rectangle or a circle as defined by the user.<br />Priority of Geofence event is categorized into Low, High or Panic levels. These levels define the priority of event information that is sent to the server. For more details about priorities look in {{{ctrIO\|[[FMB640_I/O_settings#Operands\|FMB640 I/O settings]]}}}.<br />''Generate event'' allows to choose when record will be generated.<br />''Eventual records'' controls where scenario status value appears: when disabled it will exist in each AVL record and when enabled the value will be appended only to eventual records.<br />''OverSpeeding'' helps to configure OverSpeeding scenarios separately for each different ''Geozone''. Regular OverSpeeding and geozones' OverSpeeding function independently. If digital output control is enabled in a regular OverSpeeding scenario, geozones OverSpeeding scenario will control it too i.e when the device is in more than one geozone and OverSpeeding is detected in any zone then the digital output turns on. Digital output turns off only when OverSpeeding is not detected anywhere.<br />{{{model\|FMB640}}} has 100 configurable Geofence zones and it can generate an event when a defined Geofence zone border is crossed.
	''Frame border'' is an additional border around Geofence zone used to prevent false events when object stops on the border of the area and as a result records are made inside and outside the defined area because of GNSS errors. The event is generated only when both (Geofence and frame) 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 a rectangle or a circle as defined by the user.<br/>Priority of Geofence event is categorized into Low, High or Panic levels. These levels define the priority of event information that is sent to the server. For more details about priorities look in {{{ctrIO\|[[FMB640_I/O_settings#Operands\|FMB640 I/O settings]]}}}.<br/>''Generate event'' allows to choose when record will be generated.<br/>''Eventual records'' controls where scenario status value appears: when disabled it will exist in each AVL record and when enabled the value will be appended only to eventual records.<br/>''OverSpeeding'' helps to configure OverSpeeding scenarios separately for each different ''Geozone''. Regular OverSpeeding and geozones' OverSpeeding function independently. If digital output control is enabled in a regular OverSpeeding scenario, geozones OverSpeeding scenario will control it too i.e when the device is in more than one geozone and OverSpeeding is detected in any zone then the digital output turns on. Digital output turns off only when OverSpeeding is not detected anywhere.<br/><br/>''X1'' is used to set geofence zone left bottom corner X coordinate (longitude) while ''Y1'' is used to set Y coordinate (latitude).<br/>''X2'' or ''R'' are used to set accordingly geofence zone upper right corner X coordinate (longitude) when Rectangular zone is used or circle radius when Circular zone is used. ''Y2'' sets geofence zone upper right corner Y coordinate (latitude) for a Rectangular zone.{{{model\|FMB640}}} has 100 configurable Geofence zones and it can generate an event when a defined Geofence zone border is crossed.
	''Frame border'' is an additional border around Geofence zone used to prevent false events when object stops on the border of the area and as a result records are made inside and outside the defined area because of GNSS errors. The event is generated only when both (Geofence and frame) 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 a rectangle or a circle as defined by the user.<br/>Priority of Geofence event is categorized into Low, High or Panic levels. These levels define the priority of event information that is sent to the server. For more details about priorities look in {{{ctrIO\|[[FMB640_I/O_settings#Operands\|FMB640 I/O settings]]}}}.<br/>''Generate event'' allows to choose when record will be generated.<br/>''Eventual records'' controls where scenario status value appears: when disabled it will exist in each AVL record and when enabled the value will be appended only to eventual records.<br/>''OverSpeeding'' helps to configure OverSpeeding scenarios separately for each different ''Geozone''. Regular OverSpeeding and geozones' OverSpeeding function independently. If digital output control is enabled in a regular OverSpeeding scenario, geozones OverSpeeding scenario will control it too i.e when the device is in more than one geozone and OverSpeeding is detected in any zone then the digital output turns on. Digital output turns off only when OverSpeeding is not detected anywhere.<br/><br/>''X1'' is used to set geofence zone left bottom corner X coordinate (longitude) while ''Y1'' is used to set Y coordinate (latitude).<br/>''X2'' or ''R'' are used to set accordingly geofence zone upper right corner X coordinate (longitude) when Rectangular zone is used or circle radius when Circular zone is used. ''Y2'' sets geofence zone upper right corner Y coordinate (latitude) for a Rectangular zone.{{{model\|FMB640}}} has 100 configurable Geofence zones and it can generate an event when a defined Geofence zone border is crossed.
	''Frame border'' is an additional border around Geofence zone used to prevent false events when object stops on the border of the area and as a result records are made inside and outside the defined area because of GNSS errors. The event is generated only when both (Geofence and frame) 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 a rectangle or a circle as defined by the user.<br/>Priority of Geofence event is categorized into Low, High or Panic levels. These levels define the priority of event information that is sent to the server. For more details about priorities look in {{{ctrIO\|[[FMB640_I/O_settings#Operands\|FMB640 I/O settings]]}}}.<br/>''Generate event'' allows to choose when record will be generated.<br/>''Eventual records'' controls where scenario status value appears: when disabled it will exist in each AVL record and when enabled the value will be appended only to eventual records.<br/>''OverSpeeding'' helps to configure OverSpeeding scenarios separately for each different ''Geozone''. Regular OverSpeeding and geozones' OverSpeeding function independently. If digital output control is enabled in a regular OverSpeeding scenario, geozones OverSpeeding scenario will control it too i.e when the device is in more than one geozone and OverSpeeding is detected in any zone then the digital output turns on. Digital output turns off only when OverSpeeding is not detected anywhere.<br/><br/>''X1'' is used to set geofence zone left bottom corner X coordinate (longitude) while ''Y1'' is used to set Y coordinate (latitude).<br/>''X2'' or ''R'' are used to set accordingly geofence zone upper right corner X coordinate (longitude) when Rectangular zone is used or circle radius when Circular zone is used. ''Y2'' sets geofence zone upper right corner Y coordinate (latitude) for a Rectangular zone.{{{model\|FMB640}}} has 100 configurable Geofence zones and it can generate an event when a defined Geofence zone border is crossed.
	''Frame border'' is an additional border around Geofence zone used to prevent false events when object stops on the border of the area and as a result records are made inside and outside the defined area because of GNSS errors. The event is generated only when both (Geofence and frame) 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 a rectangle or a circle as defined by the user.<br/>Priority of Geofence event is categorized into Low, High or Panic levels. These levels define the priority of event information that is sent to the server. For more details about priorities look in {{{ctrIO\|[[FMB640_I/O_settings#Operands\|FMB640 I/O settings]]}}}.<br/>''Generate event'' allows to choose when record will be generated.<br/>''Eventual records'' controls where scenario status value appears: when disabled it will exist in each AVL record and when enabled the value will be appended only to eventual records.<br/>''OverSpeeding'' helps to configure OverSpeeding scenarios separately for each different ''Geozone''. Regular OverSpeeding and geozones' OverSpeeding function independently. If digital output control is enabled in a regular OverSpeeding scenario, geozones OverSpeeding scenario will control it too i.e when the device is in more than one geozone and OverSpeeding is detected in any zone then the digital output turns on. Digital output turns off only when OverSpeeding is not detected anywhere.<br/><br/>''X1'' is used to set geofence zone left bottom corner X coordinate (longitude) while ''Y1'' is used to set Y coordinate (latitude).<br/>''X2'' or ''R'' are used to set accordingly geofence zone upper right corner X coordinate (longitude) when Rectangular zone is used or circle radius when Circular zone is used. ''Y2'' sets geofence zone upper right corner Y coordinate (latitude) for a Rectangular zone.{{{model\|FMB640}}} has 100 configurable Geofence zones and it can generate an event when a defined Geofence zone border is crossed.
	''Frame border'' is an additional border around Geofence zone used to prevent false events when object stops on the border of the area and as a result records are made inside and outside the defined area because of GNSS errors. The event is generated only when both (Geofence and frame) 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 a rectangle or a circle as defined by the user.<br/>Priority of Geofence event is categorized into Low, High or Panic levels. These levels define the priority of event information that is sent to the server. For more details about priorities look in {{{ctrIO\|[[FMB640_I/O_settings#Operands\|FMB640 I/O settings]]}}}.<br/>''Generate event'' allows to choose when record will be generated.<br/>''Eventual records'' controls where scenario status value appears: when disabled it will exist in each AVL record and when enabled the value will be appended only to eventual records.<br/>''OverSpeeding'' helps to configure OverSpeeding scenarios separately for each different ''Geozone''. Regular OverSpeeding and geozones' OverSpeeding function independently. If digital output control is enabled in a regular OverSpeeding scenario, geozones OverSpeeding scenario will control it too i.e when the device is in more than one geozone and OverSpeeding is detected in any zone then the digital output turns on. Digital output turns off only when OverSpeeding is not detected anywhere.<br/><br/>''X1'' is used to set geofence zone left bottom corner X coordinate (longitude) while ''Y1'' is used to set Y coordinate (latitude).<br/>''X2'' or ''R'' are used to set accordingly geofence zone upper right corner X coordinate (longitude) when Rectangular zone is used or circle radius when Circular zone is used. ''Y2'' sets geofence zone upper right corner Y coordinate (latitude) for a Rectangular zone.{{{model\|FMB640}}} has 100 configurable Geofence zones and it can generate an event when a defined Geofence zone border is crossed.
	''Frame border'' is an additional border around Geofence zone used to prevent false events when object stops on the border of the area and as a result records are made inside and outside the defined area because of GNSS errors. The event is generated only when both (Geofence and frame) 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 a rectangle or a circle as defined by the user.<br/>Priority of Geofence event is categorized into Low, High or Panic levels. These levels define the priority of event information that is sent to the server. For more details about priorities look in {{{ctrIO\|[[FMB640_I/O_settings#Operands\|FMB640 I/O settings]]}}}.<br/>''Generate event'' allows to choose when record will be generated.<br/>''Eventual records'' controls where scenario status value appears: when disabled it will exist in each AVL record and when enabled the value will be appended only to eventual records.<br/>''OverSpeeding'' helps to configure OverSpeeding scenarios separately for each different ''Geozone''. Regular OverSpeeding and geozones' OverSpeeding function independently. If digital output control is enabled in a regular OverSpeeding scenario, geozones OverSpeeding scenario will control it too i.e when the device is in more than one geozone and OverSpeeding is detected in any zone then the digital output turns on. Digital output turns off only when OverSpeeding is not detected anywhere.<br/><br/>''X1'' is used to set geofence zone left bottom corner X coordinate (longitude) while ''Y1'' is used to set Y coordinate (latitude).<br/>''X2'' or ''R'' are used to set accordingly geofence zone upper right corner X coordinate (longitude) when Rectangular zone is used or circle radius when Circular zone is used. ''Y2'' sets geofence zone upper right corner Y coordinate (latitude) for a Rectangular zone.{{{model\|FMB640}}} has 100 configurable Geofence zones and it can generate an event when a defined Geofence zone border is crossed.		''Frame border'' is an additional border around Geofence zone used to prevent false events when object stops on the border of the area and as a result records are made inside and outside the defined area because of GNSS errors. The event is generated only when both (Geofence and frame) 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 a rectangle or a circle as defined by the user.<br/>Priority of Geofence event is categorized into Low, High or Panic levels. These levels define the priority of event information that is sent to the server. For more details about priorities look in {{{ctrIO\|[[FMB640_I/O_settings#Operands\|FMB640 I/O settings]]}}}.<br/>''Generate event'' allows to choose when record will be generated.<br/>''Eventual records'' controls where scenario status value appears: when disabled it will exist in each AVL record and when enabled the value will be appended only to eventual records.<br/>''OverSpeeding'' helps to configure OverSpeeding scenarios separately for each different ''Geozone''. Regular OverSpeeding and geozones' OverSpeeding function independently. If digital output control is enabled in a regular OverSpeeding scenario, geozones OverSpeeding scenario will control it too i.e when the device is in more than one geozone and OverSpeeding is detected in any zone then the digital output turns on. Digital output turns off only when OverSpeeding is not detected anywhere.<br/><br/>''X1'' is used to set geofence zone left bottom corner X coordinate (longitude) while ''Y1'' is used to set Y coordinate (latitude).<br/>''X2'' or ''R'' are used to set accordingly geofence zone upper right corner X coordinate (longitude) when Rectangular zone is used or circle radius when Circular zone is used. ''Y2'' sets geofence zone upper right corner Y coordinate (latitude) for a Rectangular zone.{{{model\|FMB640}}} has 100 configurable Geofence zones and it can generate an event when a defined Geofence zone border is crossed.
	''Frame border'' is an additional border around Geofence zone used to prevent false events when object stops on the border of the area and as a result records are made inside and outside the defined area because of GNSS errors. The event is generated only when both (Geofence and frame) 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 a rectangle or a circle as defined by the user.<br/>Priority of Geofence event is categorized into Low, High or Panic levels. These levels define the priority of event information that is sent to the server. For more details about priorities look in {{{ctrIO\|[[FMB640_I/O_settings#Operands\|FMB640 I/O settings]]}}}.<br/>''Generate event'' allows to choose when record will be generated.<br/>''Eventual records'' controls where scenario status value appears: when disabled it will exist in each AVL record and when enabled the value will be appended only to eventual records.<br/>''OverSpeeding'' helps to configure OverSpeeding scenarios separately for each different ''Geozone''. Regular OverSpeeding and geozones' OverSpeeding function independently. If digital output control is enabled in a regular OverSpeeding scenario, geozones OverSpeeding scenario will control it too i.e when the device is in more than one geozone and OverSpeeding is detected in any zone then the digital output turns on. Digital output turns off only when OverSpeeding is not detected anywhere.<br/><br/>''X1'' is used to set geofence zone left bottom corner X coordinate (longitude) while ''Y1'' is used to set Y coordinate (latitude).<br/>''X2'' or ''R'' are used to set accordingly geofence zone upper right corner X coordinate (longitude) when Rectangular zone is used or circle radius when Circular zone is used. ''Y2'' sets geofence zone upper right corner Y coordinate (latitude) for a Rectangular zone.[[File:Drawing a Rectangle Geofence.gif\|alt=\|center\|Rectangle Geofence\|link=https://wiki.teltonika-gps.com/view/File:Drawing_a_Rectangle_Geofence.gif]]		''Frame border'' is an additional border around Geofence zone used to prevent false events when object stops on the border of the area and as a result records are made inside and outside the defined area because of GNSS errors. The event is generated only when both (Geofence and frame) 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 a rectangle or a circle as defined by the user.<br/>Priority of Geofence event is categorized into Low, High or Panic levels. These levels define the priority of event information that is sent to the server. For more details about priorities look in {{{ctrIO\|[[FMB640_I/O_settings#Operands\|FMB640 I/O settings]]}}}.<br/>''Generate event'' allows to choose when record will be generated.<br/>''Eventual records'' controls where scenario status value appears: when disabled it will exist in each AVL record and when enabled the value will be appended only to eventual records.<br/>''OverSpeeding'' helps to configure OverSpeeding scenarios separately for each different ''Geozone''. Regular OverSpeeding and geozones' OverSpeeding function independently. If digital output control is enabled in a regular OverSpeeding scenario, geozones OverSpeeding scenario will control it too i.e when the device is in more than one geozone and OverSpeeding is detected in any zone then the digital output turns on. Digital output turns off only when OverSpeeding is not detected anywhere.<br/><br/>''X1'' is used to set geofence zone left bottom corner X coordinate (longitude) while ''Y1'' is used to set Y coordinate (latitude).<br/>''X2'' or ''R'' are used to set accordingly geofence zone upper right corner X coordinate (longitude) when Rectangular zone is used or circle radius when Circular zone is used. ''Y2'' sets geofence zone upper right corner Y coordinate (latitude) for a Rectangular zone.[[File:Drawing a Rectangle Geofence.gif\|alt=\|center\|Rectangle Geofence\|link=https://wiki.teltonika-gps.com/view/File:Drawing_a_Rectangle_Geofence.gif]]

← Older revision		Revision as of 16:54, 24 July 2020
Line 7:		Line 7:
	''Frame border'' is an additional border around Geofence zone used to prevent false events when object stops on the border of the area and as a result records are made inside and outside the defined area because of GNSS errors. The event is generated only when both (Geofence and frame) 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 a rectangle or a circle as defined by the user.<br/>Priority of Geofence event is categorized into Low, High or Panic levels. These levels define the priority of event information that is sent to the server. For more details about priorities look in {{{ctrIO\|[[FMB640_I/O_settings#Operands\|FMB640 I/O settings]]}}}.<br/>''Generate event'' allows to choose when record will be generated.<br/>''Eventual records'' controls where scenario status value appears: when disabled it will exist in each AVL record and when enabled the value will be appended only to eventual records.<br/>''OverSpeeding'' helps to configure OverSpeeding scenarios separately for each different ''Geozone''. Regular OverSpeeding and geozones' OverSpeeding function independently. If digital output control is enabled in a regular OverSpeeding scenario, geozones OverSpeeding scenario will control it too i.e when the device is in more than one geozone and OverSpeeding is detected in any zone then the digital output turns on. Digital output turns off only when OverSpeeding is not detected anywhere.<br/><br/>''X1'' is used to set geofence zone left bottom corner X coordinate (longitude) while ''Y1'' is used to set Y coordinate (latitude).<br/>''X2'' or ''R'' are used to set accordingly geofence zone upper right corner X coordinate (longitude) when Rectangular zone is used or circle radius when Circular zone is used. ''Y2'' sets geofence zone upper right corner Y coordinate (latitude) for a Rectangular zone.{{{model\|FMB640}}} has 100 configurable Geofence zones and it can generate an event when a defined Geofence zone border is crossed.		''Frame border'' is an additional border around Geofence zone used to prevent false events when object stops on the border of the area and as a result records are made inside and outside the defined area because of GNSS errors. The event is generated only when both (Geofence and frame) 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 a rectangle or a circle as defined by the user.<br/>Priority of Geofence event is categorized into Low, High or Panic levels. These levels define the priority of event information that is sent to the server. For more details about priorities look in {{{ctrIO\|[[FMB640_I/O_settings#Operands\|FMB640 I/O settings]]}}}.<br/>''Generate event'' allows to choose when record will be generated.<br/>''Eventual records'' controls where scenario status value appears: when disabled it will exist in each AVL record and when enabled the value will be appended only to eventual records.<br/>''OverSpeeding'' helps to configure OverSpeeding scenarios separately for each different ''Geozone''. Regular OverSpeeding and geozones' OverSpeeding function independently. If digital output control is enabled in a regular OverSpeeding scenario, geozones OverSpeeding scenario will control it too i.e when the device is in more than one geozone and OverSpeeding is detected in any zone then the digital output turns on. Digital output turns off only when OverSpeeding is not detected anywhere.<br/><br/>''X1'' is used to set geofence zone left bottom corner X coordinate (longitude) while ''Y1'' is used to set Y coordinate (latitude).<br/>''X2'' or ''R'' are used to set accordingly geofence zone upper right corner X coordinate (longitude) when Rectangular zone is used or circle radius when Circular zone is used. ''Y2'' sets geofence zone upper right corner Y coordinate (latitude) for a Rectangular zone.{{{model\|FMB640}}} has 100 configurable Geofence zones and it can generate an event when a defined Geofence zone border is crossed.
	''Frame border'' is an additional border around Geofence zone used to prevent false events when object stops on the border of the area and as a result records are made inside and outside the defined area because of GNSS errors. The event is generated only when both (Geofence and frame) 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 a rectangle or a circle as defined by the user.<br/>Priority of Geofence event is categorized into Low, High or Panic levels. These levels define the priority of event information that is sent to the server. For more details about priorities look in {{{ctrIO\|[[FMB640_I/O_settings#Operands\|FMB640 I/O settings]]}}}.<br/>''Generate event'' allows to choose when record will be generated.<br/>''Eventual records'' controls where scenario status value appears: when disabled it will exist in each AVL record and when enabled the value will be appended only to eventual records.<br/>''OverSpeeding'' helps to configure OverSpeeding scenarios separately for each different ''Geozone''. Regular OverSpeeding and geozones' OverSpeeding function independently. If digital output control is enabled in a regular OverSpeeding scenario, geozones OverSpeeding scenario will control it too i.e when the device is in more than one geozone and OverSpeeding is detected in any zone then the digital output turns on. Digital output turns off only when OverSpeeding is not detected anywhere.<br/><br/>''X1'' is used to set geofence zone left bottom corner X coordinate (longitude) while ''Y1'' is used to set Y coordinate (latitude).<br/>''X2'' or ''R'' are used to set accordingly geofence zone upper right corner X coordinate (longitude) when Rectangular zone is used or circle radius when Circular zone is used. ''Y2'' sets geofence zone upper right corner Y coordinate (latitude) for a Rectangular zone.{{{model\|FMB640}}} has 100 configurable Geofence zones and it can generate an event when a defined Geofence zone border is crossed.		''Frame border'' is an additional border around Geofence zone used to prevent false events when object stops on the border of the area and as a result records are made inside and outside the defined area because of GNSS errors. The event is generated only when both (Geofence and frame) 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 a rectangle or a circle as defined by the user.<br/>Priority of Geofence event is categorized into Low, High or Panic levels. These levels define the priority of event information that is sent to the server. For more details about priorities look in {{{ctrIO\|[[FMB640_I/O_settings#Operands\|FMB640 I/O settings]]}}}.<br/>''Generate event'' allows to choose when record will be generated.<br/>''Eventual records'' controls where scenario status value appears: when disabled it will exist in each AVL record and when enabled the value will be appended only to eventual records.<br/>''OverSpeeding'' helps to configure OverSpeeding scenarios separately for each different ''Geozone''. Regular OverSpeeding and geozones' OverSpeeding function independently. If digital output control is enabled in a regular OverSpeeding scenario, geozones OverSpeeding scenario will control it too i.e when the device is in more than one geozone and OverSpeeding is detected in any zone then the digital output turns on. Digital output turns off only when OverSpeeding is not detected anywhere.<br/><br/>''X1'' is used to set geofence zone left bottom corner X coordinate (longitude) while ''Y1'' is used to set Y coordinate (latitude).<br/>''X2'' or ''R'' are used to set accordingly geofence zone upper right corner X coordinate (longitude) when Rectangular zone is used or circle radius when Circular zone is used. ''Y2'' sets geofence zone upper right corner Y coordinate (latitude) for a Rectangular zone.{{{model\|FMB640}}} has 100 configurable Geofence zones and it can generate an event when a defined Geofence zone border is crossed.
	''Frame border'' is an additional border around Geofence zone used to prevent false events when object stops on the border of the area and as a result records are made inside and outside the defined area because of GNSS errors. The event is generated only when both (Geofence and frame) 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 a rectangle or a circle as defined by the user.<br/>Priority of Geofence event is categorized into Low, High or Panic levels. These levels define the priority of event information that is sent to the server. For more details about priorities look in {{{ctrIO\|[[FMB640_I/O_settings#Operands\|FMB640 I/O settings]]}}}.<br/>''Generate event'' allows to choose when record will be generated.<br/>''Eventual records'' controls where scenario status value appears: when disabled it will exist in each AVL record and when enabled the value will be appended only to eventual records.<br/>''OverSpeeding'' helps to configure OverSpeeding scenarios separately for each different ''Geozone''. Regular OverSpeeding and geozones' OverSpeeding function independently. If digital output control is enabled in a regular OverSpeeding scenario, geozones OverSpeeding scenario will control it too i.e when the device is in more than one geozone and OverSpeeding is detected in any zone then the digital output turns on. Digital output turns off only when OverSpeeding is not detected anywhere.<br/><br/>''X1'' is used to set geofence zone left bottom corner X coordinate (longitude) while ''Y1'' is used to set Y coordinate (latitude).<br/>''X2'' or ''R'' are used to set accordingly geofence zone upper right corner X coordinate (longitude) when Rectangular zone is used or circle radius when Circular zone is used. ''Y2'' sets geofence zone upper right corner Y coordinate (latitude) for a Rectangular zone.[[File:Drawing a Rectangle Geofence.gif\|alt=\|center\|Rectangle Geofence\|link=https://wiki.teltonika-gps.com/view/File:Drawing_a_Rectangle_Geofence.gif]]~~<br />~~		''Frame border'' is an additional border around Geofence zone used to prevent false events when object stops on the border of the area and as a result records are made inside and outside the defined area because of GNSS errors. The event is generated only when both (Geofence and frame) 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 a rectangle or a circle as defined by the user.<br/>Priority of Geofence event is categorized into Low, High or Panic levels. These levels define the priority of event information that is sent to the server. For more details about priorities look in {{{ctrIO\|[[FMB640_I/O_settings#Operands\|FMB640 I/O settings]]}}}.<br/>''Generate event'' allows to choose when record will be generated.<br/>''Eventual records'' controls where scenario status value appears: when disabled it will exist in each AVL record and when enabled the value will be appended only to eventual records.<br/>''OverSpeeding'' helps to configure OverSpeeding scenarios separately for each different ''Geozone''. Regular OverSpeeding and geozones' OverSpeeding function independently. If digital output control is enabled in a regular OverSpeeding scenario, geozones OverSpeeding scenario will control it too i.e when the device is in more than one geozone and OverSpeeding is detected in any zone then the digital output turns on. Digital output turns off only when OverSpeeding is not detected anywhere.<br/><br/>''X1'' is used to set geofence zone left bottom corner X coordinate (longitude) while ''Y1'' is used to set Y coordinate (latitude).<br/>''X2'' or ''R'' are used to set accordingly geofence zone upper right corner X coordinate (longitude) when Rectangular zone is used or circle radius when Circular zone is used. ''Y2'' sets geofence zone upper right corner Y coordinate (latitude) for a Rectangular zone.[[File:Drawing a Rectangle Geofence.gif\|alt=\|center\|Rectangle Geofence\|link=https://wiki.teltonika-gps.com/view/File:Drawing_a_Rectangle_Geofence.gif]]

← Older revision		Revision as of 16:54, 24 July 2020
Line 1:		Line 1:
	[[File:FMB640 Geofence ~~SETTINGS~~ in ~~Configurator~~.~~png~~\|~~thumb~~\|FMB640 ~~Manual~~ Geofence ~~Settings~~]]		[[Image:Fmb120_geofence_border.png\|400px\|right\|link=https://wiki.teltonika-gps.com/view/File:Fmb120_geofence_border.png]]{{{model\|FMB640}}} has 100 configurable Geofence zones and it can generate an event when a defined Geofence zone border is crossed.
	'''~~Frame Border Size~~ (~~meters~~) ~~setting~~''' ~~defines Manual~~ Geofence ~~border size~~ in ~~meters~~.		''Frame border'' is an additional border around Geofence zone used to prevent false events when object stops on the border of the area and as a result records are made inside and outside the defined area because of GNSS errors. The event is generated only when both (Geofence and frame) 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 a rectangle or a circle as defined by the user.<br/>Priority of Geofence event is categorized into Low, High or Panic levels. These levels define the priority of event information that is sent to the server. For more details about priorities look in {{{ctrIO\|[[FMB640_I/O_settings#Operands\|FMB640 I/O settings]]}}}.<br/>''Generate event'' allows to choose when record will be generated.<br/>''Eventual records'' controls where scenario status value appears: when disabled it will exist in each AVL record and when enabled the value will be appended only to eventual records.<br/>''OverSpeeding'' helps to configure OverSpeeding scenarios separately for each different ''Geozone''. Regular OverSpeeding and geozones' OverSpeeding function independently. If digital output control is enabled in a regular OverSpeeding scenario, geozones OverSpeeding scenario will control it too i.e when the device is in more than one geozone and OverSpeeding is detected in any zone then the digital output turns on. Digital output turns off only when OverSpeeding is not detected anywhere.<br/><br/>''X1'' is used to set geofence zone left bottom corner X coordinate (longitude) while ''Y1'' is used to set Y coordinate (latitude).<br/>''X2'' or ''R'' are used to set accordingly geofence zone upper right corner X coordinate (longitude) when Rectangular zone is used or circle radius when Circular zone is used. ''Y2'' sets geofence zone upper right corner Y coordinate (latitude) for a Rectangular zone.{{{model\|FMB640}}} has 100 configurable Geofence zones and it can generate an event when a defined Geofence zone border is crossed.
			''Frame border'' is an additional border around Geofence zone used to prevent false events when object stops on the border of the area and as a result records are made inside and outside the defined area because of GNSS errors. The event is generated only when both (Geofence and frame) 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 a rectangle or a circle as defined by the user.<br/>Priority of Geofence event is categorized into Low, High or Panic levels. These levels define the priority of event information that is sent to the server. For more details about priorities look in {{{ctrIO\|[[FMB640_I/O_settings#Operands\|FMB640 I/O settings]]}}}.<br/>''Generate event'' allows to choose when record will be generated.<br/>''Eventual records'' controls where scenario status value appears: when disabled it will exist in each AVL record and when enabled the value will be appended only to eventual records.<br/>''OverSpeeding'' helps to configure OverSpeeding scenarios separately for each different ''Geozone''. Regular OverSpeeding and geozones' OverSpeeding function independently. If digital output control is enabled in a regular OverSpeeding scenario, geozones OverSpeeding scenario will control it too i.e when the device is in more than one geozone and OverSpeeding is detected in any zone then the digital output turns on. Digital output turns off only when OverSpeeding is not detected anywhere.<br/><br/>''X1'' is used to set geofence zone left bottom corner X coordinate (longitude) while ''Y1'' is used to set Y coordinate (latitude).<br/>''X2'' or ''R'' are used to set accordingly geofence zone upper right corner X coordinate (longitude) when Rectangular zone is used or circle radius when Circular zone is used. ''Y2'' sets geofence zone upper right corner Y coordinate (latitude) for a Rectangular zone.{{{model\|FMB640}}} has 100 configurable Geofence zones and it can generate an event when a defined Geofence zone border is crossed.
			''Frame border'' is an additional border around Geofence zone used to prevent false events when object stops on the border of the area and as a result records are made inside and outside the defined area because of GNSS errors. The event is generated only when both (Geofence and frame) 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 a rectangle or a circle as defined by the user.<br/>Priority of Geofence event is categorized into Low, High or Panic levels. These levels define the priority of event information that is sent to the server. For more details about priorities look in {{{ctrIO\|[[FMB640_I/O_settings#Operands\|FMB640 I/O settings]]}}}.<br/>''Generate event'' allows to choose when record will be generated.<br/>''Eventual records'' controls where scenario status value appears: when disabled it will exist in each AVL record and when enabled the value will be appended only to eventual records.<br/>''OverSpeeding'' helps to configure OverSpeeding scenarios separately for each different ''Geozone''. Regular OverSpeeding and geozones' OverSpeeding function independently. If digital output control is enabled in a regular OverSpeeding scenario, geozones OverSpeeding scenario will control it too i.e when the device is in more than one geozone and OverSpeeding is detected in any zone then the digital output turns on. Digital output turns off only when OverSpeeding is not detected anywhere.<br/><br/>''X1'' is used to set geofence zone left bottom corner X coordinate (longitude) while ''Y1'' is used to set Y coordinate (latitude).<br/>''X2'' or ''R'' are used to set accordingly geofence zone upper right corner X coordinate (longitude) when Rectangular zone is used or circle radius when Circular zone is used. ''Y2'' sets geofence zone upper right corner Y coordinate (latitude) for a Rectangular zone.{{{model\|FMB640}}} has 100 configurable Geofence zones and it can generate an event when a defined Geofence zone border is crossed.
	'''~~Geozones Overspeeding Dout setting~~''' ~~defines DOUT~~ control in '''~~Manual~~ Geofence ~~Zones~~''' ~~overspeeding~~ scenario, ~~which also~~ can be ~~configured~~ in '''~~Manual Geofence Zones~~''' ~~TAB~~.		''Frame border'' is an additional border around Geofence zone used to prevent false events when object stops on the border of the area and as a result records are made inside and outside the defined area because of GNSS errors. The event is generated only when both (Geofence and frame) 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 a rectangle or a circle as defined by the user.<br/>Priority of Geofence event is categorized into Low, High or Panic levels. These levels define the priority of event information that is sent to the server. For more details about priorities look in {{{ctrIO\|[[FMB640_I/O_settings#Operands\|FMB640 I/O settings]]}}}.<br/>''Generate event'' allows to choose when record will be generated.<br/>''Eventual records'' controls where scenario status value appears: when disabled it will exist in each AVL record and when enabled the value will be appended only to eventual records.<br/>''OverSpeeding'' helps to configure OverSpeeding scenarios separately for each different ''Geozone''. Regular OverSpeeding and geozones' OverSpeeding function independently. If digital output control is enabled in a regular OverSpeeding scenario, geozones OverSpeeding scenario will control it too i.e when the device is in more than one geozone and OverSpeeding is detected in any zone then the digital output turns on. Digital output turns off only when OverSpeeding is not detected anywhere.<br/><br/>''X1'' is used to set geofence zone left bottom corner X coordinate (longitude) while ''Y1'' is used to set Y coordinate (latitude).<br/>''X2'' or ''R'' are used to set accordingly geofence zone upper right corner X coordinate (longitude) when Rectangular zone is used or circle radius when Circular zone is used. ''Y2'' sets geofence zone upper right corner Y coordinate (latitude) for a Rectangular zone.{{{model\|FMB640}}} has 100 configurable Geofence zones and it can generate an event when a defined Geofence zone border is crossed.
			''Frame border'' is an additional border around Geofence zone used to prevent false events when object stops on the border of the area and as a result records are made inside and outside the defined area because of GNSS errors. The event is generated only when both (Geofence and frame) 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 a rectangle or a circle as defined by the user.<br/>Priority of Geofence event is categorized into Low, High or Panic levels. These levels define the priority of event information that is sent to the server. For more details about priorities look in {{{ctrIO\|[[FMB640_I/O_settings#Operands\|FMB640 I/O settings]]}}}.<br/>''Generate event'' allows to choose when record will be generated.<br/>''Eventual records'' controls where scenario status value appears: when disabled it will exist in each AVL record and when enabled the value will be appended only to eventual records.<br/>''OverSpeeding'' helps to configure OverSpeeding scenarios separately for each different ''Geozone''. Regular OverSpeeding and geozones' OverSpeeding function independently. If digital output control is enabled in a regular OverSpeeding scenario, geozones OverSpeeding scenario will control it too i.e when the device is in more than one geozone and OverSpeeding is detected in any zone then the digital output turns on. Digital output turns off only when OverSpeeding is not detected anywhere.<br/><br/>''X1'' is used to set geofence zone left bottom corner X coordinate (longitude) while ''Y1'' is used to set Y coordinate (latitude).<br/>''X2'' or ''R'' are used to set accordingly geofence zone upper right corner X coordinate (longitude) when Rectangular zone is used or circle radius when Circular zone is used. ''Y2'' sets geofence zone upper right corner Y coordinate (latitude) for a Rectangular zone.{{{model\|FMB640}}} has 100 configurable Geofence zones and it can generate an event when a defined Geofence zone border is crossed.
	'''~~DOUT ON Duration~~ (ms)''' ~~defines~~ value in ~~miliseconds~~ for ~~how long DOUT should be active~~.		''Frame border'' is an additional border around Geofence zone used to prevent false events when object stops on the border of the area and as a result records are made inside and outside the defined area because of GNSS errors. The event is generated only when both (Geofence and frame) 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 a rectangle or a circle as defined by the user.<br/>Priority of Geofence event is categorized into Low, High or Panic levels. These levels define the priority of event information that is sent to the server. For more details about priorities look in {{{ctrIO\|[[FMB640_I/O_settings#Operands\|FMB640 I/O settings]]}}}.<br/>''Generate event'' allows to choose when record will be generated.<br/>''Eventual records'' controls where scenario status value appears: when disabled it will exist in each AVL record and when enabled the value will be appended only to eventual records.<br/>''OverSpeeding'' helps to configure OverSpeeding scenarios separately for each different ''Geozone''. Regular OverSpeeding and geozones' OverSpeeding function independently. If digital output control is enabled in a regular OverSpeeding scenario, geozones OverSpeeding scenario will control it too i.e when the device is in more than one geozone and OverSpeeding is detected in any zone then the digital output turns on. Digital output turns off only when OverSpeeding is not detected anywhere.<br/><br/>''X1'' is used to set geofence zone left bottom corner X coordinate (longitude) while ''Y1'' is used to set Y coordinate (latitude).<br/>''X2'' or ''R'' are used to set accordingly geofence zone upper right corner X coordinate (longitude) when Rectangular zone is used or circle radius when Circular zone is used. ''Y2'' sets geofence zone upper right corner Y coordinate (latitude) for a Rectangular zone.{{{model\|FMB640}}} has 100 configurable Geofence zones and it can generate an event when a defined Geofence zone border is crossed.
			''Frame border'' is an additional border around Geofence zone used to prevent false events when object stops on the border of the area and as a result records are made inside and outside the defined area because of GNSS errors. The event is generated only when both (Geofence and frame) 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 a rectangle or a circle as defined by the user.<br/>Priority of Geofence event is categorized into Low, High or Panic levels. These levels define the priority of event information that is sent to the server. For more details about priorities look in {{{ctrIO\|[[FMB640_I/O_settings#Operands\|FMB640 I/O settings]]}}}.<br/>''Generate event'' allows to choose when record will be generated.<br/>''Eventual records'' controls where scenario status value appears: when disabled it will exist in each AVL record and when enabled the value will be appended only to eventual records.<br/>''OverSpeeding'' helps to configure OverSpeeding scenarios separately for each different ''Geozone''. Regular OverSpeeding and geozones' OverSpeeding function independently. If digital output control is enabled in a regular OverSpeeding scenario, geozones OverSpeeding scenario will control it too i.e when the device is in more than one geozone and OverSpeeding is detected in any zone then the digital output turns on. Digital output turns off only when OverSpeeding is not detected anywhere.<br/><br/>''X1'' is used to set geofence zone left bottom corner X coordinate (longitude) while ''Y1'' is used to set Y coordinate (latitude).<br/>''X2'' or ''R'' are used to set accordingly geofence zone upper right corner X coordinate (longitude) when Rectangular zone is used or circle radius when Circular zone is used. ''Y2'' sets geofence zone upper right corner Y coordinate (latitude) for a Rectangular zone.{{{model\|FMB640}}} has 100 configurable Geofence zones and it can generate an event when a defined Geofence zone border is crossed.
	'''~~DOUT OFF Duration~~ (ms)''' ~~defines~~ value in ~~miliseconds~~ for ~~how long DOUT should be inactive~~.		''Frame border'' is an additional border around Geofence zone used to prevent false events when object stops on the border of the area and as a result records are made inside and outside the defined area because of GNSS errors. The event is generated only when both (Geofence and frame) 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 a rectangle or a circle as defined by the user.<br/>Priority of Geofence event is categorized into Low, High or Panic levels. These levels define the priority of event information that is sent to the server. For more details about priorities look in {{{ctrIO\|[[FMB640_I/O_settings#Operands\|FMB640 I/O settings]]}}}.<br/>''Generate event'' allows to choose when record will be generated.<br/>''Eventual records'' controls where scenario status value appears: when disabled it will exist in each AVL record and when enabled the value will be appended only to eventual records.<br/>''OverSpeeding'' helps to configure OverSpeeding scenarios separately for each different ''Geozone''. Regular OverSpeeding and geozones' OverSpeeding function independently. If digital output control is enabled in a regular OverSpeeding scenario, geozones OverSpeeding scenario will control it too i.e when the device is in more than one geozone and OverSpeeding is detected in any zone then the digital output turns on. Digital output turns off only when OverSpeeding is not detected anywhere.<br/><br/>''X1'' is used to set geofence zone left bottom corner X coordinate (longitude) while ''Y1'' is used to set Y coordinate (latitude).<br/>''X2'' or ''R'' are used to set accordingly geofence zone upper right corner X coordinate (longitude) when Rectangular zone is used or circle radius when Circular zone is used. ''Y2'' sets geofence zone upper right corner Y coordinate (latitude) for a Rectangular zone.[[File:Drawing a Rectangle Geofence.gif\|alt=\|center\|Rectangle Geofence\|link=https://wiki.teltonika-gps.com/view/File:Drawing_a_Rectangle_Geofence.gif]]<br />