Changes

Template:FMB640 Features settings (view source)

Revision as of 17:15, 14 November 2022

5,203 bytes added ,  17:15, 14 November 2022
→‎Short burst data settings
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 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==
   −
{{{short_burst|[[Image:Short_burst.JPG|300px|right]]}}}
     −
[[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|Short Burst Data]].
 +
 
 +
Iridium Edge pinout and RS232 COM 1/2 connection:
   −
[[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”''.
+
[[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.
   −
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.
  −
Record which will be sent through the Iridium satellite network will be different than the regular record. It will contain 4 bytes timestamp, 3 bytes longitude, 3 bytes latitude, 1 byte record generation info, 1 byte DIN, DOUT info, 1 byte speed value.
     −
{{{pic_connection|[[Image:connection.JPG|300px|center]]}}}
+
'''''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).
   −
'''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 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'''.
   −
{{{pic_connector|[[Image:connector.JPG|600px|center]]}}}
+
'''''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 2
 +
* Digital input 3
 +
* Digital input 4
 +
* Digital output 1
 +
* Digital output 2
 +
* Digital output 3
 +
* Digital output 4
 +
* Speed
 +
<br></br>
 +
Configurator parameter IDs and their explanation:
 +
{| class="nd-othertables_2" style="width:100%;"
 +
|- style="font-weight:bold; text-align:center;"
 +
! '''Parameter ID'''<br />
 +
! '''Parameter name'''
 +
! colspan="3" | '''Values'''
 +
! '''Explanation'''
 +
|- style="font-weight:bold; text-align:center;"
 +
| style="font-weight:normal;" |
 +
| style="font-weight:normal;" |
 +
| '''Min'''
 +
| '''Max'''
 +
| '''Default'''
 +
| style="font-weight:normal;" |
 +
|-
 +
| 99420
 +
| Iridium Edge
 +
| 0
 +
| 1
 +
| 0
 +
| This parameter enables or disables Iridium Edge functionality
 +
|-
 +
| 99421
 +
| Save/Send period
 +
| 0
 +
| 1440
 +
| 1440
 +
| This parameter lets to configure Iridium Edge sending period
 +
|-
 +
| 99422
 +
| SBD IO source'''*'''
 +
| 0
 +
| 8
 +
| 0
 +
| SBD IO elements which when enabled are included into the SBD record
 +
|-
 +
| 99423
 +
| SBD UploadLimit
 +
| 0
 +
| 30000
 +
| 8000
 +
| Limit to save user from exceeding the monthly plan. Max limit of 30000 due to 30KB plan. If set to 0 – limit will be off.
 +
|-
 +
| 99424
 +
| Power control DOUT
 +
| 1
 +
| 5
 +
| 0
 +
| Device DOUT which can control ON/OFF pin of the Iridium Edge
 +
|-
 +
| 151
 +
| RS232 Mode
 +
| 0
 +
| 23
 +
| 0
 +
| RS-232 mode selection. "Satellite backup" - 15
 +
|}
   −
'''NOTE''': SBD data is limited to 8000 Bytes per month. For firmware with a bigger SBD data limit, please ask your sales manager.
+
<br></br>
−
If the data limit is reached you can reset it with SMS command ''“sbdlimitsreset”''.
+
'''*''' SBD IO source parameter is configured with bitmasks:
 +
*eSBD_IO_Bit_Disabled    = 0x00,
 +
*eSBD_IO_Bit_Din1        = 0x01,
 +
*eSBD_IO_Bit_Din2        = 0x02,
 +
*eSBD_IO_Bit_Din3        = 0x04,
 +
*eSBD_IO_Bit_Din4        = 0x08,
 +
*eSBD_IO_Bit_Do1          = 0x10,
 +
*eSBD_IO_Bit_Do2          = 0x20,
 +
*eSBD_IO_Bit_Do3          = 0x40,
 +
*eSBD_IO_Bit_Do4          = 0x80,
 +
*eSBD_IO_Bit_Speed        = 0x100
 +
<br></br>
 +
For example: to enable Din1, Din3 and Do4: 0x01 + 0x04 + 0x80 = 0x85 convert to decimal --> 133.
    
==Impulse Counters Settings==
 
==Impulse Counters Settings==
Line 136: Line 228:  
{{{Impulse counter settingsFM6|[[Image:Impulse counter settingsFM6.png|300px|right]]}}}
 
{{{Impulse counter settingsFM6|[[Image:Impulse counter settingsFM6.png|300px|right]]}}}
   −
Pulse counter functionality enables the FMX640 devices to count digital impulses going to Digital and Analog Inputs. This means that these inputs of the FMB devices can now be used for precise fuel flow meter data reading. Impulse based fuel usage monitoring is much more accurate than a different type of fuel metering sensors and it makes the FMX640 devices a perfect solution for high fuel usage machines like cranes, construction vehicles, mining machines, agriculture equipment.
+
Pulse counter functionality enables the FMX640 devices to count digital impulses going to Digital and Analog Inputs. This means that these inputs of the FMX640 devices can now be used for precise fuel flow meter data reading. Impulse based fuel usage monitoring is much more accurate than a different type of fuel metering sensors and it makes the FMX640 devices a perfect solution for high fuel usage machines like cranes, construction vehicles, mining machines, agriculture equipment.
 
<br>
 
<br>
 
<br>
 
<br>
 
'''How does it work?'''
 
'''How does it work?'''
 
<br>
 
<br>
−
When Impulse Counter 1/2 input is selected and "Fuel Counter/Impulse Counter 2" IO elements are enabled, device will count every input state change to HIGH and send the counted number with the next record. Pulse counter value is reset after sending the record.
+
When "Impulse Counter 1/2 input" is selected and "Fuel Counter/Impulse Counter 2" IO elements are enabled, device will count every input state change to HIGH and send the counted number with the next record. Pulse counter value is reset after sending the record.
 +
<br>
 +
'''NOTE''': Impulse Counters feature is available from FW ver. 01.02.02
 
------
 
------
 
'''I/O elements''' - Each counter has a corresponding IO elements for "Impulse Frequency" - value in Hz and "Impulse RPM" - impulse count per minute.
 
'''I/O elements''' - Each counter has a corresponding IO elements for "Impulse Frequency" - value in Hz and "Impulse RPM" - impulse count per minute.
 
<br>
 
<br>
 
<br>
 
<br>
−
[[Image:Impulse counter I-O FM6.png]]
+
[[Image:Image-2021-09-07-18-10-28-631.png]]
 
<br>
 
<br>
 
<br>
 
<br>
Line 166: Line 260:  
<br>
 
<br>
 
Note that each Input has a specific requirements for signal frequency and threshold:
 
Note that each Input has a specific requirements for signal frequency and threshold:
 +
<table class="nd-othertables_2" style="width: 30%;">
 +
<tr>
 +
        <th style="width: 10%; text-align:center; vertical-align:middle;">Input</th>
 +
        <th style="width: 10%; text-align:center; vertical-align:middle;">Max frequency (Hz)</th>
 +
        <th style="width: 10%; text-align:center; vertical-align:middle;">Min Voltage threshold (V)</th>
 +
 +
    </tr>
 +
        <tr>
 +
        <td style="width: 10%; text-align:center; vertical-align:middle;">DIN1</td>
 +
        <td style="width: 10%; text-align:center; vertical-align:middle;">50</td>
 +
        <td style="width: 10%; text-align:center; vertical-align:middle;">7.5</td>
 +
    </tr>
 +
        <tr>
 +
        <td style="width: 10%; text-align:center; vertical-align:middle;">DIN2</td>
 +
        <td style="width: 10%; text-align:center; vertical-align:middle;">30 000</td>
 +
        <td style="width: 10%; text-align:center; vertical-align:middle;">2.5</td>
 +
    </tr>
 +
        <tr>
 +
        <td style="width: 10%; text-align:center; vertical-align:middle;">DIN3</td>
 +
        <td style="width: 10%; text-align:center; vertical-align:middle;">30 000</td>
 +
        <td style="width: 10%; text-align:center; vertical-align:middle;">2.5</td>
 +
    </tr>
 +
        <tr>
 +
        <td style="width: 10%; text-align:center; vertical-align:middle;">DIN4</td>
 +
        <td style="width: 10%; text-align:center; vertical-align:middle;">30 000</td>
 +
        <td style="width: 10%; text-align:center; vertical-align:middle;">2.5</td>
 +
    </tr>
 +
        <tr>
 +
        <td style="width: 10%; text-align:center; vertical-align:middle;">AIN1</td>
 +
        <td style="width: 10%; text-align:center; vertical-align:middle;">10 000</td>
 +
        <td style="width: 10%; text-align:center; vertical-align:middle;">2.5</td>
 +
    </tr>
 +
        <tr>
 +
        <td style="width: 10%; text-align:center; vertical-align:middle;">AIN2</td>
 +
        <td style="width: 10%; text-align:center; vertical-align:middle;">10 000</td>
 +
        <td style="width: 10%; text-align:center; vertical-align:middle;">2.5</td>
 +
    </tr>
 +
        <tr>
 +
        <td style="width: 10%; text-align:center; vertical-align:middle;">AIN3</td>
 +
        <td style="width: 10%; text-align:center; vertical-align:middle;">10 000</td>
 +
        <td style="width: 10%; text-align:center; vertical-align:middle;">2.5</td>
 +
    </tr>
 +
        <tr>
 +
        <td style="width: 10%; text-align:center; vertical-align:middle;">AIN4</td>
 +
        <td style="width: 10%; text-align:center; vertical-align:middle;">10 000</td>
 +
        <td style="width: 10%; text-align:center; vertical-align:middle;">2.5</td>
 +
    </tr>
 +
</table>
Retrieved from "https://wiki.teltonika-gps.com/view/Special:MobileDiff/66889...77888"

Navigation menu