Changes

333 bytes removed ,  10:42, 27 December 2023
no edit summary
Line 2: Line 2:     
Status info enables the user to monitor real time information of {{{model|FMB1YX}}}. Following fields are displayed: '''Device Info''', '''GNSS Info''', '''GSM Info''', '''I/O Info''', '''Maintenance''' and etc. User is able to export all of the information to '''.HTML''' file using [[File:Export_html.png|15px|link=]] icon which is at the top right corner of the '''Device Info''' area.
 
Status info enables the user to monitor real time information of {{{model|FMB1YX}}}. Following fields are displayed: '''Device Info''', '''GNSS Info''', '''GSM Info''', '''I/O Info''', '''Maintenance''' and etc. User is able to export all of the information to '''.HTML''' file using [[File:Export_html.png|15px|link=]] icon which is at the top right corner of the '''Device Info''' area.
 +
{{{Main_Status_image|}}}
    
==Device Info==
 
==Device Info==
 
+
{{{Device_Info_image|}}}
 
*Device Name
 
*Device Name
 
*Firmware version
 
*Firmware version
Line 17: Line 18:     
==GNSS Info==
 
==GNSS Info==
 
+
{{{GNSS_Info_image|}}}
 
*GNSS status
 
*GNSS status
 
**Module status - ON, [[{{{model|FMB120}}}_Sleep_modes#GPS_Sleep_mode|GPS Sleep]], [[{{{model|FMB120}}}_Sleep_modes#Deep_Sleep_mode|Deep Sleep]], [[{{{model|FMB120}}}_Sleep_modes#Online_Deep_Sleep_mode|Online Deep Sleep]], [[{{{model|FMB120}}}_Sleep_modes#Ultra_Deep_Sleep_mode|Ultra Deep Sleep]] mode.
 
**Module status - ON, [[{{{model|FMB120}}}_Sleep_modes#GPS_Sleep_mode|GPS Sleep]], [[{{{model|FMB120}}}_Sleep_modes#Deep_Sleep_mode|Deep Sleep]], [[{{{model|FMB120}}}_Sleep_modes#Online_Deep_Sleep_mode|Online Deep Sleep]], [[{{{model|FMB120}}}_Sleep_modes#Ultra_Deep_Sleep_mode|Ultra Deep Sleep]] mode.
 
**GNSS packets - the number of GNSS packets the device received from startup.
 
**GNSS packets - the number of GNSS packets the device received from startup.
**Fix Status - Fix/No Fix.
+
**Fix Status - Fix/No Fix. <b>(Note: Fix time strongly depends on indoor/outdoor location. To achieve best performance acquiring GNSS fix device should be used in outdoor locations</b>)
 
**Fix Time - the last GNSS fix time.
 
**Fix Time - the last GNSS fix time.
 
*Satellites
 
*Satellites
**Visible -  the amount and type of satellites that are visible.
+
**Visible -  the number and type of satellites that are visible.
 
**In Use - the number of satellites used for location positioning.
 
**In Use - the number of satellites used for location positioning.
 
*Location
 
*Location
Line 36: Line 37:  
<BR>
 
<BR>
   −
{|
  −
|[[File:Alert.png|left|link=|50px]]||<b>From firmware version 03.27.06.Rev.01 HDOP/PDOP value calculation has been removed. DOP values are taken from GPGSA messages. DOP values are calculated according to constellations that are currently in use. Example: If we have 4 GNSS systems and there will be two in use then average will be calculated from two GNSS systems.</b>
  −
|}
   
Main calculations of separate HDOP/PDOP values of GPS, GLONASS, Galileo and BeiDou are made by GNSS modem. GNSS Modem already  outputs average of HDOP/PDOP from  4 GNSS systems (Used satellites) with a formula below.  
 
Main calculations of separate HDOP/PDOP values of GPS, GLONASS, Galileo and BeiDou are made by GNSS modem. GNSS Modem already  outputs average of HDOP/PDOP from  4 GNSS systems (Used satellites) with a formula below.  
   Line 60: Line 58:     
==GSM Info==
 
==GSM Info==
 
+
{{{GSM_info_image|}}}
 
*GSM status  
 
*GSM status  
 
**Modem Status
 
**Modem Status
Line 84: Line 82:     
==I/O Info==
 
==I/O Info==
 +
*I/O Data - shows the current values from all configurable I/O elements.
 +
{{{IO_info_image|}}}
   −
*I/O Data - shows the current values from all configurable I/O elements.
  −
{{{txt_hide_tmt250|==FMS I/O Info==
  −
* FMS I/O Data - shows the current values from FMS configurable I/O elements.
  −
==Tachograph Data Info==
  −
* Tachograph Data - shows the current values from Tachograph Data configurable I/O elements.
  −
}}}
   
==Maintenance==
 
==Maintenance==
 
+
{{{Maintenance_image|}}}
 
*Log/Dump
 
*Log/Dump
 
**Log - after button is pressed, the device starts log capturing for 10 minutes with configuration download. After this time device .log and configuration .cfg will be in compressed archive. <p>Archive name: <code>YYYY_MM_DD_HH_MM_SS_{{{model|FMB1YX}}}_IMEI_Log.zip</code><br>Default directory: <code>C:\Users\<username>\Documents</code></p>
 
**Log - after button is pressed, the device starts log capturing for 10 minutes with configuration download. After this time device .log and configuration .cfg will be in compressed archive. <p>Archive name: <code>YYYY_MM_DD_HH_MM_SS_{{{model|FMB1YX}}}_IMEI_Log.zip</code><br>Default directory: <code>C:\Users\<username>\Documents</code></p>
Line 100: Line 94:  
*Accelerometer - after the button is pressed, the device starts to capture accelerometer values for 1 second.
 
*Accelerometer - after the button is pressed, the device starts to capture accelerometer values for 1 second.
 
{{{txt_lls|==LLS Calibration==
 
{{{txt_lls|==LLS Calibration==
* LLS calibration - in this section you can calculate calibration values of Analog LLS sensors for AVL server - create a polynom which is needed to convert sensor values to liters:
+
* LLS calibration - in this section you can calculate calibration values of Analog LLS sensors for AVL server - create a polynomial which is needed to convert sensor values to liters:
 
**Table is filled row by row. Each row represents one fuel tank fill. To calculate constants it is needed to select a sensor from ''„Available sensors“'', and fill the „Fuel, L.“ column and capture the current value of a sensor by clicking the ''"Refresh"'' button. Then the next value in liters should be entered by the user and so on.  
 
**Table is filled row by row. Each row represents one fuel tank fill. To calculate constants it is needed to select a sensor from ''„Available sensors“'', and fill the „Fuel, L.“ column and capture the current value of a sensor by clicking the ''"Refresh"'' button. Then the next value in liters should be entered by the user and so on.  
 
**When a table is filled, calculated a0, a1, a2, and a3 values should be seen.
 
**When a table is filled, calculated a0, a1, a2, and a3 values should be seen.
 
**To add a new tank fill row click "Add row". To remove the row click the ''"minus"'' button near the row you want to clear. To Clear all the rows click ''"Clear rows"''.
 
**To add a new tank fill row click "Add row". To remove the row click the ''"minus"'' button near the row you want to clear. To Clear all the rows click ''"Clear rows"''.
 
**By clicking ''"Export"'' data will be exported to .csv file.
 
**By clicking ''"Export"'' data will be exported to .csv file.
**To recalculate the polynom click on ''"Calculate"'' button.
+
**To recalculate the polynomial click on ''"Calculate"'' button.
    
[[File:LLS_Calibration.png]]
 
[[File:LLS_Calibration.png]]
Line 113: Line 107:     
{{{txt_obd|==OBD Info==
 
{{{txt_obd|==OBD Info==
Shows the main OBD parameters with current values when the device is connected to the vehicle via OBDII socket or using [[{{{model|FMB120}}}_Bluetooth_settings#How_to_connect_OBD_II_Bluetooth_Dongle_to_FMB_device|OBDII Bluetooth Dongle]].
+
Shows the main OBD parameters with current values when the device is connected to the vehicle via OBDII socket or using [[{{{model|FMB120}}}_Bluetooth®_settings#How_to_connect_OBD_II_Bluetooth®_Dongle_to_FMB_device|OBDII Bluetooth® Dongle]].
    
'''Note:''' not all parameters which are displayed in the ''"OBD Info"'' tab can be readable from the vehicle.}}}
 
'''Note:''' not all parameters which are displayed in the ''"OBD Info"'' tab can be readable from the vehicle.}}}
    
{{{txt_can|==CAN Adapter Info==  
 
{{{txt_can|==CAN Adapter Info==  
Shows the parameters with current values (including program number and software version) from CAN {{{FMB140_CAN|adapter when the device is connected to [[LV-CAN200]]/[[ALL-CAN300]]/[[CAN-CONTROL]].}}}
+
Shows the parameters with current values (including program number and software version) from CAN adapter when the device is connected to LV-CAN200/ALL-CAN300/CAN-CONTROL.
    
'''Note:''' not all parameters which are displayed in the ''"CAN Adapter Info"'' tab can be readable from the vehicle.}}}
 
'''Note:''' not all parameters which are displayed in the ''"CAN Adapter Info"'' tab can be readable from the vehicle.}}}

Navigation menu