Template:FMB640 Features settings - Revision history

Mantas.Kraujelis: /* Short burst data settings */

2022-11-14T14:15:21Z

Short burst data settings

← Older revision		Revision as of 17:15, 14 November 2022
Line 125:		Line 125:
	{{{model\|}}} supports Iridium devices which can send short burst data (SBD) to the server. This means that some data can be sent from FM device to the server through satellites.		{{{model\|}}} supports Iridium devices which can send short burst data (SBD) to the server. This means that some data can be sent from FM device to the server through satellites.

	In order to properly connect the Iridium device to {{{device\|}}}, Iridium has to be connected to the device via RS-232 - COM1 or COM2 (with RJ-45 connector, where 4 pin is GND, 5 pin is RS232 Rx and 6 PIN is RS232 Tx). Additionally '''Pin No. 6''' - power control (reference in the image below) must be connected to one of the {{{model\|}}} DOUTs (1/2/3/4), in order to allow the device to power ON/OFF Iridium device on demand. More information about SBD can be found here [[{{{model\|}}} _Short_Burst_Data]].		In order to properly connect the Iridium device to {{{device\|}}}, Iridium has to be connected to the device via RS-232 - COM1 or COM2 (with RJ-45 connector, where 4 pin is GND, 5 pin is RS232 Rx and 6 PIN is RS232 Tx). Additionally '''Pin No. 6''' - power control (reference in the image below) must be connected to one of the {{{model\|}}} DOUTs (1/2/3/4), in order to allow the device to power ON/OFF Iridium device on demand. More information about SBD can be found here [[{{{model\|}}} _Short_Burst_Data\|Short Burst Data]].

	Iridium Edge pinout and RS232 COM 1/2 connection:		Iridium Edge pinout and RS232 COM 1/2 connection:

Mantas.Kraujelis at 14:06, 14 November 2022

2022-11-14T14:06:13Z

← Older revision		Revision as of 17:06, 14 November 2022
Line 37:		Line 37:
	</tr>		</tr>
	</table>		</table>
	{{{pic_accelerometerposition\|[[Image:FMB640accelerometerposition.png\|300px\|right]]}}} ~~[[FMB640]]~~ Device accelerometer position. (With positive Z axis pointing to Ground and antennas face forward in the vehicle). Before operation with the vehicle on level ground user must send “setacc” SMS.		{{{pic_accelerometerposition\|[[Image:FMB640accelerometerposition.png\|300px\|right]]}}} {{{model\|}}} Device accelerometer position. (With positive Z axis pointing to Ground and antennas face forward in the vehicle). Before operation with the vehicle on level ground user must send “setacc” SMS.

	===Auto calibration===		===Auto calibration===
Line 123:		Line 123:


	~~[[FMB640]]~~ supports Iridium devices which can send short burst data (SBD) to the server. This means that some data can be sent from FM device to the server through satellites.		{{{model\|}}} supports Iridium devices which can send short burst data (SBD) to the server. This means that some data can be sent from FM device to the server through satellites.

	In order to properly connect the Iridium device to {{{device\|}}}, Iridium has to be connected to the device via RS-232 - COM1 or COM2 (with RJ-45 connector, where 4 pin is GND, 5 pin is RS232 Rx and 6 PIN is RS232 Tx). Additionally '''Pin No. 6''' - power control (reference in the image below) must be connected to one of the {{{model\|}}} DOUTs (1/2/3/4), in order to allow the device to power ON/OFF Iridium device on demand. More information about SBD can be found here [[{{{model\|}}} _Short_Burst_Data]].		In order to properly connect the Iridium device to {{{device\|}}}, Iridium has to be connected to the device via RS-232 - COM1 or COM2 (with RJ-45 connector, where 4 pin is GND, 5 pin is RS232 Rx and 6 PIN is RS232 Tx). Additionally '''Pin No. 6''' - power control (reference in the image below) must be connected to one of the {{{model\|}}} DOUTs (1/2/3/4), in order to allow the device to power ON/OFF Iridium device on demand. More information about SBD can be found here [[{{{model\|}}} _Short_Burst_Data]].

Mantas.Kraujelis: /* Short burst data settings */

2022-11-14T14:05:14Z

Short burst data settings

← Older revision		Revision as of 17:05, 14 November 2022
Line 125:		Line 125:
	[[FMB640]] supports Iridium devices which can send short burst data (SBD) to the server. This means that some data can be sent from FM device to the server through satellites.		[[FMB640]] supports Iridium devices which can send short burst data (SBD) to the server. This means that some data can be sent from FM device to the server through satellites.

	In order to properly connect the Iridium device to {{{device\|}}}, Iridium has to be connected to the device via RS-232 - COM1 or COM2 (with RJ-45 connector, where 4 pin is GND, 5 pin is RS232 Rx and 6 PIN is RS232 Tx). Additionally '''Pin No. 6''' - power control (reference in the image below) must be connected to one of the {{{model\|}}} DOUTs (1/2/3/4), in order to allow the device to power ON/OFF Iridium device on demand. More information can be found here [[{{{model\|}}} _Short_Burst_Data]].		In order to properly connect the Iridium device to {{{device\|}}}, Iridium has to be connected to the device via RS-232 - COM1 or COM2 (with RJ-45 connector, where 4 pin is GND, 5 pin is RS232 Rx and 6 PIN is RS232 Tx). Additionally '''Pin No. 6''' - power control (reference in the image below) must be connected to one of the {{{model\|}}} DOUTs (1/2/3/4), in order to allow the device to power ON/OFF Iridium device on demand. More information about SBD can be found here [[{{{model\|}}} _Short_Burst_Data]].

	Iridium Edge pinout and RS232 COM 1/2 connection:		Iridium Edge pinout and RS232 COM 1/2 connection:

Mantas.Kraujelis: /* Short burst data settings */

2022-11-14T14:04:17Z

Short burst data settings

← Older revision		Revision as of 17:04, 14 November 2022
Line 125:		Line 125:
	[[FMB640]] supports Iridium devices which can send short burst data (SBD) to the server. This means that some data can be sent from FM device to the server through satellites.		[[FMB640]] supports Iridium devices which can send short burst data (SBD) to the server. This means that some data can be sent from FM device to the server through satellites.

	In order to properly connect the Iridium device to {{{device\|}}}, Iridium has to be connected to the device via RS-232 - COM1 or COM2 (with RJ-45 connector, where 4 pin is GND, 5 pin is RS232 Rx and 6 PIN is RS232 Tx). Additionally '''Pin No. 6''' - power control (reference in the image below) must be connected to one of the {{model\|}}} DOUTs (1/2/3/4), in order to allow the device to power ON/OFF Iridium device on demand. More information can be found here [[{{{model\|}}} _Short_Burst_Data]].		In order to properly connect the Iridium device to {{{device\|}}}, Iridium has to be connected to the device via RS-232 - COM1 or COM2 (with RJ-45 connector, where 4 pin is GND, 5 pin is RS232 Rx and 6 PIN is RS232 Tx). Additionally '''Pin No. 6''' - power control (reference in the image below) must be connected to one of the {{{model\|}}} DOUTs (1/2/3/4), in order to allow the device to power ON/OFF Iridium device on demand. More information can be found here [[{{{model\|}}} _Short_Burst_Data]].

	Iridium Edge pinout and RS232 COM 1/2 connection:		Iridium Edge pinout and RS232 COM 1/2 connection:

Mantas.Kraujelis: /* Short burst data settings */

2022-11-14T14:03:13Z

Short burst data settings

← Older revision		Revision as of 17:03, 14 November 2022
Line 125:		Line 125:
	[[FMB640]] supports Iridium devices which can send short burst data (SBD) to the server. This means that some data can be sent from FM device to the server through satellites.		[[FMB640]] supports Iridium devices which can send short burst data (SBD) to the server. This means that some data can be sent from FM device to the server through satellites.

	In order to properly connect the Iridium device to {{{device\|}}}, Iridium has to be connected to the device via RS-232 - COM1 or COM2 (with RJ-45 connector, where 4 pin is GND, 5 pin is RS232 Rx and 6 PIN is RS232 Tx). Additionally '''Pin No. 6''' - power control (reference in the image below) must be connected to one of the {{~~{device~~\|}}} DOUTs (1/2/3/4), in order to allow the device to power ON/OFF Iridium device on demand. More information can be found here [[{{{~~device~~\|}}} _Short_Burst_Data]].		In order to properly connect the Iridium device to {{{device\|}}}, Iridium has to be connected to the device via RS-232 - COM1 or COM2 (with RJ-45 connector, where 4 pin is GND, 5 pin is RS232 Rx and 6 PIN is RS232 Tx). Additionally '''Pin No. 6''' - power control (reference in the image below) must be connected to one of the {{model\|}}} DOUTs (1/2/3/4), in order to allow the device to power ON/OFF Iridium device on demand. More information can be found here [[{{{model\|}}} _Short_Burst_Data]].

	Iridium Edge pinout and RS232 COM 1/2 connection:		Iridium Edge pinout and RS232 COM 1/2 connection:
Line 140:		Line 140:
	'''''SBD Upload Limit''''' is configurable and resets every month. This option can ensure that no additional data is used so that no unexpected costs are experienced by the customer. The default value is 8000 (for 8KB plan). This option can be disabled by setting the Upload limit to 0. The monthly data usage counter can be reset by using the SMS/GPRS command - '''sbdlimitsreset'''.		'''''SBD Upload Limit''''' is configurable and resets every month. This option can ensure that no additional data is used so that no unexpected costs are experienced by the customer. The default value is 8000 (for 8KB plan). This option can be disabled by setting the Upload limit to 0. The monthly data usage counter can be reset by using the SMS/GPRS command - '''sbdlimitsreset'''.

	'''''SBD IO source''''' configures IO source which can trigger SBD record saving. 9 elements can generate Alarm for SDB sending. These elements are:		'''''SBD IO source''''' configures IO source which can trigger SBD record saving. 9 elements can generate an Alarm for SDB sending. These elements are:
	* Digital input 1		* Digital input 1
	* Digital input 2		* Digital input 2

Mantas.Kraujelis: /* Short burst data settings */

2022-11-14T13:58:09Z

Short burst data settings

← Older revision		Revision as of 16:58, 14 November 2022
Line 125:		Line 125:
	[[FMB640]] supports Iridium devices which can send short burst data (SBD) to the server. This means that some data can be sent from FM device to the server through satellites.		[[FMB640]] supports Iridium devices which can send short burst data (SBD) to the server. This means that some data can be sent from FM device to the server through satellites.

	In order to properly connect the Iridium device to {{{device\|}}}, Iridium has to be connected to the device via RS-232 - COM1 or COM2 (with RJ-45 connector, where 4 pin is GND, 5 pin is RS232 Rx and 6 PIN is RS232 Tx). Additionally '''Pin No. 6''' - power control (reference in the image below) must be connected to one of the {{{device\|}}} DOUTs (1/2/3/4), in order to allow the device to power ON/OFF Iridium device on demand.		In order to properly connect the Iridium device to {{{device\|}}}, Iridium has to be connected to the device via RS-232 - COM1 or COM2 (with RJ-45 connector, where 4 pin is GND, 5 pin is RS232 Rx and 6 PIN is RS232 Tx). Additionally '''Pin No. 6''' - power control (reference in the image below) must be connected to one of the {{{device\|}}} DOUTs (1/2/3/4), in order to allow the device to power ON/OFF Iridium device on demand. More information can be found here [[{{{device\|}}} _Short_Burst_Data]].

	Iridium Edge pinout and RS232 COM 1/2 connection:		Iridium Edge pinout and RS232 COM 1/2 connection:

Mantas.Kraujelis: /* Short burst data settings */

2022-10-18T07:49:25Z

Short burst data settings

← Older revision		Revision as of 10:49, 18 October 2022
Line 125:		Line 125:
	[[FMB640]] supports Iridium devices which can send short burst data (SBD) to the server. This means that some data can be sent from FM device to the server through satellites.		[[FMB640]] supports Iridium devices which can send short burst data (SBD) to the server. This means that some data can be sent from FM device to the server through satellites.

			In order to properly connect the Iridium device to {{{device\|}}}, Iridium has to be connected to the device via RS-232 - COM1 or COM2 (with RJ-45 connector, where 4 pin is GND, 5 pin is RS232 Rx and 6 PIN is RS232 Tx). Additionally '''Pin No. 6''' - power control (reference in the image below) must be connected to one of the {{{device\|}}} DOUTs (1/2/3/4), in order to allow the device to power ON/OFF Iridium device on demand.

			Iridium Edge pinout and RS232 COM 1/2 connection:

			[[File:Iridium Edge pinout.png\|left]]
			[[File:FMX640 and RS232 illustration v1.2.png\|right\|450x201px]]
			<br></br><br></br><br></br><br></br><br></br><br></br>
			[[File:SBD settings.gif\|right]]
	When the Iridium edge device is connected '''''Power control DOUT''''' configures DOUT pin which can control Iridium Edge ON/OFF pin. Configure if DOUT pin is connected. Respective power control DOUT to which the Iridium device's ''PIN6'' is connected must be selected.		When the Iridium edge device is connected '''''Power control DOUT''''' configures DOUT pin which can control Iridium Edge ON/OFF pin. Configure if DOUT pin is connected. Respective power control DOUT to which the Iridium device's ''PIN6'' is connected must be selected.
	~~[[File:SBD settings.gif\|right]]~~

	'''''Save/Send period''''' configures how long will FMB device wait after losing the signal to generate SBD packet. If the signal is not recovered, it will send it indefinitely (or till the SBD Upload limit is reached, if such is set).		'''''Save/Send period''''' configures how long will FMB device wait after losing the signal to generate SBD packet. If the signal is not recovered, it will send it indefinitely (or till the SBD Upload limit is reached, if such is set).

Mantas.Kraujelis: /* Short burst data settings */

2022-10-18T07:44:54Z

Short burst data settings

← Older revision		Revision as of 10:44, 18 October 2022
Line 126:		Line 126:

	When the Iridium edge device is connected '''''Power control DOUT''''' configures DOUT pin which can control Iridium Edge ON/OFF pin. Configure if DOUT pin is connected. Respective power control DOUT to which the Iridium device's ''PIN6'' is connected must be selected.		When the Iridium edge device is connected '''''Power control DOUT''''' configures DOUT pin which can control Iridium Edge ON/OFF pin. Configure if DOUT pin is connected. Respective power control DOUT to which the Iridium device's ''PIN6'' is connected must be selected.
	[[File:SBD settings.gif\|~~centre~~]]		[[File:SBD settings.gif\|right]]

	'''''Save/Send period''''' configures how long will FMB device wait after losing the signal to generate SBD packet. If the signal is not recovered, it will send it indefinitely (or till the SBD Upload limit is reached, if such is set).		'''''Save/Send period''''' configures how long will FMB device wait after losing the signal to generate SBD packet. If the signal is not recovered, it will send it indefinitely (or till the SBD Upload limit is reached, if such is set).

Mantas.Kraujelis: /* Short burst data settings */

2022-10-18T07:44:32Z

Short burst data settings

@@ Line 122: / Line 122: @@
 ==Short burst data settings==
 [[FMB640]] supports Iridium devices which can send short burst data (SBD) to the server. This means that some data can be sent from FM device to the server through satellites.
-[[FMB640]] will enable satellite mode only if a device can not send data via GPRS. Satellite mode has his own Save/Send period. If timeout is set to 0 no periodic records will be made. It is not recommended to save records often because of satellite traffic prices. 8 kilobytes monthly data limit is hardcoded in firmware. If the data limit is reached – the data limit counter will reset automatically only on next month first day or you can rest counter by SMS command ''“sbdlimitsreset”''.
+When the Iridium edge device is connected '''''Power control DOUT''''' configures DOUT pin which can control Iridium Edge ON/OFF pin. Configure if DOUT pin is connected. Respective power control DOUT to which the Iridium device's ''PIN6'' is connected must be selected.
-In addition, you can select which IO element can generate Satellite records. In order to do that you need to go to I/O tab select IO record priority Panic and check the checkbox “Satellite I/O” what you want to get that data through satellites if there is no GSM connection.
+'''''Save/Send period''''' configures how long will FMB device wait after losing the signal to generate SBD packet. If the signal is not recovered, it will send it indefinitely (or till the SBD Upload limit is reached, if such is set).
-{{{pic_connection|[[Image:connection.JPG|300px|center]]}}}
+'''''SBD Upload Limit''''' is configurable and resets every month. This option can ensure that no additional data is used so that no unexpected costs are experienced by the customer. The default value is 8000 (for 8KB plan). This option can be disabled by setting the Upload limit to 0. The monthly data usage counter can be reset by using the SMS/GPRS command - '''sbdlimitsreset'''.
-'''NOTE''': Port1/2 cable from FM package can be used for [[TSM232]] connection. For this you need to cut a D-SUB connector and connect wires according to the instruction above (PIN 4 to TSM GND, PIN5 to TSM Rx, PIN6 to TSM Tx).
+'''''SBD IO source''''' configures IO source which can trigger SBD record saving.  9 elements can generate Alarm for SDB sending. These elements are:
-{{{pic_connector|[[Image:connector.JPG|600px|center]]}}}
+<br></br>
+'''*''' SBD IO source parameter is configured with bitmasks:
-'''NOTE''': SBD data is limited to 8000 Bytes per month. For firmware with a bigger SBD data limit, please ask your sales manager.
+*eSBD_IO_Bit_Disabled     = 0x00,
-If the data limit is reached you can reset it with SMS command ''“sbdlimitsreset”''.
+*eSBD_IO_Bit_Din1         = 0x01,
 ==Impulse Counters Settings==

AugustasP: /* iButton Read Notification */

2022-09-19T13:04:47Z

iButton Read Notification

← Older revision		Revision as of 16:04, 19 September 2022
Line 102:		Line 102:
	==iButton Read Notification==		==iButton Read Notification==

	~~{{{pic_ibutton\|~~[[Image:~~I button~~.~~JPG~~\|~~300px~~\|right]]~~}}}~~		[[Image:IButton_Read_Notification .png\|{{{general\|size}}}\|\|right]]
			Output control parameter lets the user choose which DOUT will iButton blink. After connecting iButton, DOUT will blink for a period of time, which is configured in DOUT ON Duration parameter. The iButton List checking parameter configures whether the device reads the iButton ID from iButton list or not. For example if configured as Enabled, device will not blink DOUT unless the iButton is in the iButton list.
			If Depend on Ignition parameter is enabled, then Output will be triggered only if ignition is off (in addition to being in a list if iButton List Checking is also enabled).
			Output control examples when iButton is detected (if None is selected in Output Control – all of the following steps will be skipped):

	* If ~~the scenario~~ is ~~enabled, when~~ iButton is ~~attached~~ and is ~~successfully read, configured DOUT goes ON for configurable amount of time (min: 0~~.~~00 s; max: 5~~.~~00 s; default: 0.2 s). <br>~~		*If both iButton List Checking and Depend on Ignition are disabled – Output is triggered.
	* If ~~DOUT ON~~ and ~~DOUT OFF durations~~ are ~~both set to 0, DOUT~~ will ~~be ON until~~ iButton ~~will be removed from~~ the ~~reader~~. ~~<br>~~		*If iButton List Checking is enabled and Depend on Ignition is disabled – Output is triggered only if iButton is in the list.
	* ~~If the Immobilizer~~ scenario ~~is enabled and iButton’s indication scenario is enabled and the same~~ DOUT ~~controls are chosen then~~ in ~~case~~ iButton ~~is attached DOUT is~~ not ~~affected~~.		*If iButton List Checking is disabled but Depend on Ignition is enabled – Output is triggered only if ignition is off.
	~~IButton’s event generation works as a standard IO event generation~~		*If both iButton List Checking and Depend on Ignition are enabled – Output will trigger if iButton is in the list and ignition is off.

			iButton Read Notification parameters:

			*Output control – available scenario settings for module Digital output activation/deactivation
			*DOUT ON duration – a value in seconds, for how long {{{text_dout\|DOUT1/DOUT2/DOUT3}}} should be active.
			*iButton List checking - parameter configures that device reads the iButton ID from list or not.
			*Depend on Ignition - Output will be triggered only if ignition is off
	<br/><br/>		<br/><br/>
	~~'''Confirmation about successful iButton identification with configured DOUT ON indication'''~~
	If DOUTX iButton read notification parameter is configured to control DOUTX and DOUTX is ON, then when new iButton is successfully read, DOUTX is turned OFF for 0,5 seconds and then turned back ON. By “new iButton” it is meant that the value read by (let’s say Driver’s) iButton reader is either different compared to what was read before or it’s the first time this iButton is read.
	~~<br/><br/><br/>~~
	==Short burst data settings==		==Short burst data settings==