Teltonika FMB630 User Manual
  1. Manuals
  2. Brands
  3. Teltonika Manuals
  4. GPS
  5. FMB630
  6. User manual

Teltonika FMB630 User Manual

Hide thumbs Also See for FMB630:
Table of Contents

Advertisement

Quick Links

Download this manual
FMB630 User Manual
V1.8

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the FMB630 and is the answer not in the manual?

Questions and answers

Related Manuals for Teltonika FMB630

Summary of Contents for Teltonika FMB630

  • Page 1 FMB630 User Manual V1.8...

  • Page 2: Table Of Contents

    Battery Disposal instructions: ................. 12 ....................12 LECTRICAL CHARACTERISTICS ....................13 BSOLUTE AXIMUM ATINGS CONNECTION AND PINOUT ....................14 ...................... 14 CARD INSERT SCHEME FMB630 ....................16 NSTALLING DRIVERS LED ........................17 AVIGATE LED ........................17 TATUS 210 ......................18...
  • Page 3 IButton List ......................... 49 6.3.7 CAN ......................... 49 6.3.7.1 CAN Bus settings ........................ 49 6.3.8 I/O ........................... 52 6.3.8.1 FMB630 available I/O list ....................52 6.3.8.2 I/O configuring ........................56 6.3.8.3 I/O properties ........................57 6.3.8.4 SMS event configuration ....................59 6.3.8.5 LVCAN/ALL-CAN300 I/O elements..................
  • Page 4 13.1.1 Mounting Requirements ..................87 13.1.2 Configuration ......................89 13.1.3 Data output ......................89 13.2 ...................... 90 VERSPEEDING CENARIO 13.2.1 Mounting Requirements and Working Conditions ..........90 13.2.2 Configuration ......................90 13.3 ................. 90 MMOBILIZER UTHORIZED RIVING CENARIO 13.3.1 Configuration ......................91 13.3.2 Configuration ......................
  • Page 5 14.23 ........................104 CRASHLOG 14.24 ........................104 BRAMINFO 14.25 ........................104 ODINFO FMB630 WITH LV-CAN 200 AND ALL-CAN 300 CAN ADAPTER ........... 105 15.1 LV-CAN200 ALL-CAN300 ........... 105 URPOSE OF DAPTERS 15.2 LV-CAN200 ALL-CAN300 ..........106 PROGRAM NUMBER SELECTION 15.2.1 LV-CAN200 and ALL-CAN300 program number configuration via SMS command106 15.2.2...
  • Page 6 MVC300 CAMERA ......................159 22.1 ........................159 NTRODUCTION 22.2 ..................... 159 TARTUP AND ONFIGURATION 22.2.1 Camera parameters in FMB630: ................161 22.2.2 Camera parameters in MVC300: ................161 22.3 FMB630 MVC300 .................. 162 CONNECTION GPRS COMMANDS ......................162 DEBUG MODE ........................164 FMB630 REMOTE LOG ......................

  • Page 7: Introduction

    FMB630 has USB interface; Please use cables provided with FMB630 device. Teltonika is not responsible for any harm caused by using wrong cables for PC <-> FMB630 connection. This sign on the packaging means that the electric and electronic equipment to be utilized must be stored separately.

  • Page 8: Instructions Of Safety

    To avoid mechanical damage, it is advised to transport the FMB630 device in an impact- proof package. Before usage, the device should be placed so that its LED indicators are visible, which show the status of operation the device is in.

  • Page 9: Basic Description

    It is important to mention that FMB630 has additional inputs and outputs, which let you control and monitor other devices on remote objects. FMB630 also has a USB port for device status log output and for saving configurations.

  • Page 10: Mechanical Features

    Protection turns on, device turns off. Unlimited Maximum voltage <70V Unlimited Maximum voltage impulse 5 miliseconds 2.3 Mechanical features Table 2 FMB630 physical interfaces and operation environment Part name Physical specification Operation environment Navigation LED Power supply 10...30 V DC 2 W Max Modem LED...

  • Page 11: Technical Information About Internal Battery

     In sleep mode a new FMB630 device, operating time approximately 5 hours  In deep sleep mode – 35 hours  Operating time for a new FMB630 device, working in normal mode (records are being acquired every 10 sec. and sent in packets of 4 records every 60 sec.), is approximately 2 h 10 min.

  • Page 12: Battery Disposal Instructions

    2.4.1 Battery Disposal instructions: Battery should not be disposed of with general household waste. Bring damaged or worn-out batteries to your local recycling center or dispose them to battery recycle bin found in stores. 2.5 Electrical characteristics Table 3 Electrical characteristics VALUE Min.

  • Page 13: Absolute Maximum Ratings

    Common mode input voltage When connecting a COM port to an active external device keep in mind that the first power supply must be connected to FMB630, and then the external device should be powered. Connecting external devices when FMB630 is powered off is not recommended.

  • Page 14: Connection And Pinout

    Voltage on CANH, CANL (Absolute Maximum Ratings) 3 CONNECTION AND PINOUT 3.1 SIM card insert scheme  Gently open FMB630 case using screwdrivers...
  • Page 15   Take off FMB630 case and insert SIM cards as shown. SIM1 SLOT (default, recommended Assemble device as shown and put screws for 1 SIM mode) is closer to PCB, SIM2 SLOT into the holes is the upper one ...

  • Page 16: Installing Fmb630 Drivers

    Please download Virtual COM Port drivers from Teltonika website: FMB630 VCP Driver Installing drivers Extract and run VCPDriver_V1.3.1_Setup.exe. This driver is used to detect FMB630 device connected to the computer. Click 'Next' in driver installation window (figures below): Figure 2 Driver installation window This will launch the device driver installation wizard.

  • Page 17: Navigate Led

    Figure 4 Driver installation window You have now installed drivers for FMB630 device successfully. 3.3 Navigate LED Table 5 Navigate LED operation Behaviour Meaning Permanently switched on GPS signal is not received Blinking every second Normal mode, GPS is working GPS is turned off because: ...

  • Page 18: Socket 210 Pinout

    3.5 Socket 210 pinout AIN 3 K-Line OUT 2 OUT 1 OUT 3 OUT 4 AIN 2 AIN 1 CAN2 L CAN2_H DIN 2 IGN (DIN1) DIN 4 DIN 3 1W. PWR 1W. data CAN1 L CAN1 H (-)GND (+)VCC (1030)V DC Figure 5 2x10 socket pinout Table 7 2x10 SOCKET PINOUT DESCRIPTION Pin Name...

  • Page 19: Usb

    3.6 USB When FMB630 is connected to a PC it creates a STM Virtual COM Port, which can be used as a system port (to flash firmware and configure the device). Figure 6 COM-Ports 3.7 Accessories Note: Teltonika does not provide any additional equipment like panic buttons, door sensors etc, except 1 –...
  • Page 20 Figure 7 Temperature sensors connection scheme Left row of pins Right row of pins 1W. PWR (FMB630 – pin3) Vpp(+5 Volts DC) – 1W. Data power (FMB630 – pin13) source for external digital sensor Output (FMB630 – pin1) from external...
  • Page 21 A fuel tank level sensor exists in most of the cars, which shows the approximate fuel level in the driver’s indicator panel. It is possible to connect FMB630 Analog input (if sensor returns analogue signal proportional to fuel level). Figure 10 describes the connection scheme to the FMB630 and fuel tank sensor.
  • Page 22 Impulse counters Figure 11 describes the connection scheme to the FMB630. Here two pulse meters are used, where one is mounted on the direct flow valve and the other on the return flow valve. Data from both meters is sent to the FMB630. Then FMB630 calculates DIN3-DIN4. Resulting difference equals to fuel consumption.
  • Page 23 Figure 13 Inverting relay connection Immobilizer relay When connected a shown below, FMB630 disables engine starter when output is ON. More details about relays can be found below. Figure 14 Immobilizer relay connection Relays A simple automotive relays is used to invert input signal or to immobilize engine starter.
  • Page 24 LV-CAN200 Light vehicle CAN adapter, which allows reading CAN data from light vehicles. LV-CAN200 supports more than 1200 models of vehicles. Readable data:  Vehicle Driven Distance  Total fuel consumption  Fuel level (Dashboard)  Engine speed (RPM)  Vehicle speed (wheel) ...
  • Page 25 ALL-CAN300 ALL-CAN300 is designed to acquire CAN data from any kind of transport (light vehicles, trucks, buses, agriculture transport, special transport). ALL-CAN300 supports more than 1800 models of vehicles. Figure 17 ALL-CAN300 adapter Supported OnBoard computer data:  Ignition indication ...

  • Page 26: Firmware

    See configuration description for details. Contact sales manager to get the latest firmware. Connect FMB630 to PC with the USB cable. Launch “Firmware Updater”, select COM port to which device is connected, click connect, and when IMEI and Firmware version fields are filled, start the update.

  • Page 27: Operational Basics

    OPERATIONAL BASICS 5.1 Operational principles FMB630 module is designed to acquire records and send them to server. Records contain GPS and I/O information. Module uses GPS receiver to acquire GPS data and is powered with 3 data acquire methods: time-based, distance-based, angle-based and speed-based. Method’s details are described in Data Acquisition chapter 9.

  • Page 28: Operational Modes

    FMB630 perform while in this mode can be found in chapter 11. 5.3 Accelerometer FMB630 has a built in 3 axis accelerometer which allows the device to indicate if vehicle is moving or not, as well as measure acceleration. Accelerometer sensitivity can be configured – it has 2 configurable global parameters: start and stop timeouts that define time intervals in seconds.

  • Page 29: Features

    You are allowed to setup up to 4 different module behaviours. Global parameters contain settings that are common for all 4 profiles. This means that if FMB630 is set to call to predefined number, you will be able to call it while using any profile.

  • Page 30: Excessive Idling

    5.6.1.5 Excessive idling. If ignition (DIN1 or Power Voltage) is on and vehicle is not moving, FMB630 after configured time period generate event. When vehicle starts moving FMB630 after configured time period generate event that vehicle idle time ends. 5.6.1.6 Jamming detection.

  • Page 31: Ibutton List

    Figure 21 FMB630 Configurator window 6.2 Configurator structure FMB630 has four user editable profiles, which can be both loaded and saved to the device. User can also revert to default settings, by pressing Load Defaults button. Any modification of configuration settings has to be saved to FMB630 device; otherwise it will not be written to device flash memory.

  • Page 32: Buttons Area

    Keyword is of 4 - 10 symbol length (Latin text and/or numbers). If a keyword is set, every time user reconnects FMB630 to USB or COM ports he will be asked to enter a valid keyword when connecting FMB630 to...

  • Page 33: Information Area

    6.2.2 Information area FMB630 information area is divided into 2 parts located on the top right and bottom of the configurator. When configurator is connected to the device via USB or COM2 port all necessary information about the device is shown here: ...

  • Page 34: Parameters Configuration

    Parameter Name Parameter description Allows selecting profile switching method. When 'Profile change on Profile change on event' is disabled – FMB630 switches profiles depending on GSM event operator code method. Otherwise it switches profiles depending on I/O events. Are used to switch between two data sending modes: starting from newest records or starting from oldest record.

  • Page 35: External Devices Settings

    External Devices do not depend on selected profile; they are common for all profiles. To configure these parameters choose the TAB named “External Devices” and make all necessary changes (Figure 26) Figure 26 FMB630 External Devices Table 10 External Devices parameters description Parameter Name...

  • Page 36: Settings And Configurable Parameters Menu

    LLS Sensor Settings Allows user to set LLS sensors addresses in preffered order 6.3.3 Settings and configurable parameters menu Every FMB630 profile has seven main groups of parameters: 1. System – main parameters for all device; 2. GSM has 7 subgroups: a.

  • Page 37: Gsm Settings

    IP or domain name) and port. Also both TCP and UDP protocols are supported. Server Response Time defines the time how long device will wait for response from server before device denies the connection between FMB630 and server. Server 2 is used as dublicated server (not back up server).

  • Page 38: Data Limits Functionality

    Essential fields in ‘SMS Security’ part are ‘SMS Login’ and ‘SMS Password’ (Figure 29). This login and password is used with every SMS sent to FMB630. If login and password are not set, every SMS sent to FMB630 device has to include two spaces before command (<space><space><command>).

  • Page 39: Sms Data

    Figure 29 GSM->SMS Security Settings 6.3.5.4 SMS Data SMS data sending Settings enables or disables periodic data and event SMS sending to server (Figure 30). Configuration is divided into 4 main parts: 1. SMS data sending settings; 2. SMS Week Time button; 3.

  • Page 40: Sms Events

    Figure 30 GSM->SMS Settings Configuration (2) Using these settings FMB630 can send SMS with 24-coordinates in one SMS; it is used in areas where no GPRS coverage is available. Module collects data and sends to server binary SMS containing information about last 24 collected points. SMS sending schedule is set in SMS Week Time tab.

  • Page 41: Operator List

    Figure 32 SMS Events Numbers list 6.3.5.6 Operator List FMB630 is able to use GPRS with all operators but if any operator is entered in the preferred operator list, FMB630 is allowed to connect to GPRS only when operating in listed operator’s network.

  • Page 42: Connection To Device Via Bluetooth

    FMB630 will not connect to GPRS using network of operator which is listed in black list. Figure 33 FMB630 Operator List Configuration 6.3.5.7 Connection to device via Bluetooth FMB630 can connect to Bluetooth handsfree adapter for two way communication and also you can connect device to ‘bluetooth terminal’...

  • Page 43: Features

    6.3.6 Features 6.3.6.1 sMode FMB630 is able to collect records using four methods at the same time: time, distance, speed and angle based data acquisition (Chapter 9) Send and Save Parameters configuration is available in Features->sMode category (6.3.6.1):  Min Period – time period change that initializes record save.

  • Page 44: Trip

    DOUT. Scenarios configurable parameters are shown in Figure 36. All values of these parameters are described in Chapter 12. Figure 36 FMB630 Scenarios configuration 6.3.6.3 Trip Trip window offers user to configure Trip feature. If Trip is enabled configuration of parameters is available: ...

  • Page 45: Geofencing

    IO (set to 0) when trip end event occurs. 6.3.6.4 Geofencing Geofencing settings: FMB630 has 20 configurable Geofence zones and it can generate event when defined Geofence zone border has been crossed. Or overspeeding is occured in a configured geofence zone.
  • Page 46 Figure 38 FMB630 Features->Geofencing Configuration (1) Configuration of the parameters is available in Features->Geofencing (Figure 38)  Frame border – frame border is an additional border around Geofence zone. It is additional area around defined zone used to prevent false event recording when object stops on the border of the area and because of GPS errors some records are made inside area and some –...

  • Page 47: Autogeofencing

    – you can be notified. The shape and size of the geofence zones are configurable. There is a possibility to state whether entering in or out of the geofence triggers an asynchronous message. Figure 40 FMB630 Features->Geofencing Configuration (2) Auto Geofencing option can be configured by following parameters (Figure 40): ...

  • Page 48: Towing Detection

    Ignition state. If Ignition is still OFF according to configured "Ignition check after Event" time, then event is generated and can send sms or make call if configured. Function will be reactivated after FMB630 again detects change of Ignition state from ON to OFF. Figure 41 Towing Detection Configuraton ...

  • Page 49: Ibutton List

    6.3.6.7 IButton List IButton list is used to enter authorized iButton ID codes, which are used to authenticate driver in Immobilizer scenario or Auto Geofencing options. Figure 42 Features->iButton Configuration IButton value must be entered as it is written on it. User can save 500 iButtons to .csv file and read them from same file using Read from File and save to file buttons.
  • Page 50 CAN 1 Baud Rate (ID=147) Parameter defines CAN 1 bus baud rate. For Auto Baud rate value is 0. Available baud rates are 50, 100, 125, 250, 500 and 1000 kbps. Table 12 CAN 1 Baud Rate Minimum Maximum Recommended Value type value value...
  • Page 51 CAN#0 I/O OutputDataMask CAN#0 I/O CAN ID CAN#0 I/O CAN Type ID Parameter defines CAN element ID length. CAN element ID could be 11 or 29 bits length. For 11 bits ID parameter value is 0, for 29 bits ID – 1. Table 17 CAN#0 CAN Type ID Minimum Maximum...

  • Page 52: I/O

    If all I/O elements are disabled AVL packet comes with GPS information only. After enabling I/O element(s) AVL packet in couple with GPS information contains current value(s) of enabled I/O element. 6.3.8.1 FMB630 available I/O list Table 21 PERMANENT I/O elements list description Permanent I/O elements...
  • Page 53 Permanent I/O elements (are always sent (with every record) to server if enabled) Property Name Bytes Description Digital Input Status 3 Logic: 0 / 1 Digital Input Status 4 Logic: 0 / 1 Digital Output Status 1 Logic: 0 / 1 Digital Output Status 2 Logic: 0 / 1 Digital Output Status 3...
  • Page 54 Permanent I/O elements (are always sent (with every record) to server if enabled) Property Name Bytes Description Fuel Counter Difference of generated impulses on two signal lines Ignition 0 – ignition is off, 1 – ignition is on RFID COM1 Displays activated RFID card ID from COM1 Total Odometer Total odometer value km...
  • Page 55 Eventual IO elements (generated and sent record to server only if appropriate conditions are met) Property Name Bytes Description CAN2 2 Varying ID Specific data CAN2 3 Varying ID Specific data CAN2 4 Varying ID Specific data CAN2 5 Varying ID Specific data CAN2 6 Varying...

  • Page 56: I/O Configuring

    7.2). SW2X priorities switch profiles on event (SW21 – Profile 1, SW22 – Profile 2 and so on). High Level - define I/O value range. If I/O value enters or exits this range, FMB630 generates event. Low Level – define I/O value range. If I/O value enters or exits this range, FMB630...

  • Page 57: I/O Properties

    Pos. DESCRIPTION generates event. Generate event – defines when to generate event. When value enters defined range, exits it or both enters and exits. Averaging Constant – it is an I/O event delay parameter. In some applications there is no need to generate events on every I/O range enter/exit immediately.
  • Page 58 I/O#0 property parameter priority I/O#0 9999999 I/O#0 Low level I/O#0 logic operand I/O#0 averaging constant I/O#0 Low level Parameter defines low value of triggered I/O property. This parameter is used to set thresholds for I/O properties to generate events. Table 26 I/O Low Value Minimum Maximum Recommended...

  • Page 59: Sms Event Configuration

    “ setparam 1300 1,0,0,1,1” (“ setparam 1300 <priority>,<HighLevel>,<LowLevel>,<Operand>,<AvgC onstant>”) Other I/O property elements can be configured in the same logic. All I/O element parameters are listed below. Table 29 I/O Elements I/O element I/O element I/O Element Number I/O Element Number parameters parameters I/O#0 –...

  • Page 60: Lvcan/All-Can300 I/O Elements

    6.3.8.5 LVCAN/ALL-CAN300 I/O elements LVCAN IO elements can be configured remotely via SMS command. Table 30 LVCAN elements and parameters Element name (default SMS Event Text) x399 [LVC Vehicle Speed] x400 [LVC Acce Pedal Position] x401 [LVC Fuel Consumed] x402 [LVC Fuel Level Liters] x403 [LVC Engine RPM]...

  • Page 61: K-Line Parameters

    x490 [LVC Driver1 Cumulative Driving Time] x491 [LVC Driver2 Cumulative Driving Time] x492 [LVC Driver1 ID High] x493 [LVC Driver1 ID Low] x494 [LVC Driver2 ID High] x495 [LVC Driver2 ID Low] x496 [LVC Battery Temperature] x497 [LVC Battery Level (percent)] x498 [LVC Door Status] x514...
  • Page 62 Parameter Name Configuration ID Available Values Name High level Low level 3 – Monitoring Generate event 5 – On change 0 – disable Priority 1 – low 2 – high KLINE Driver 1 card X054 High level Low level 3 – Monitoring Generate event 5 –...
  • Page 63 Parameter Name Configuration ID Available Values Name 0 – disable Priority 1 – low 2 – high KLINE Odometer High level X059 Low level 3 – Monitoring Generate event 5 – On change 0 – disable Priority 1 – low 2 –...

  • Page 64: Configurable Parameter Values And Global Parameter Values

    Parameter Name Configuration ID Available Values Name 2 – high High level Low level 3 –Monitoring Generate event 5 – On change 0 – disable Priority 1 – low 2 – high KLINE Card 2 issuing number state High level X068 Low level 3 –Monitoring...
  • Page 65 Parameter value Value Parameter type Default Recommended Server 1 GPRS Context Activation 0 (Disable) 1 (Enable) Protocol 0 (TCP) 1 (UDP) Server Response x240 Timeout Domain Empty 56 char Empty Target Server Port 65535 Configuring format: <Enable>,<IP>,<port>,<protocol>,<Server Reponse Tmo> Server 2 GPRS Context Activation 0 (Disable) 1 (Enable)
  • Page 66 Parameter value Value Parameter type Default Recommended (in degrees) Min Speed (in km/h) 0/1/2/3/4 (0-GPS, 1-LVCAN, 2- Min Speed Source ALLCAN, 3-FMS, 4-KLINE) Min Saved Records Min Send Period (in seconds) 9999999 <minperiod>,<mindistance>,<minangle>,<minspeed>,<minspeedsource>,<minsavedrec>, Configuring format: <sendperiod> Geofencing settings (6.3.6.4) Frame Border (in 9999999 1000 meters)
  • Page 67 Parameter value Value Parameter type Default Recommended Geofence Zone #9 x038 Geofence Zone #10 x039 Geofence Zone #11 x040 Geofence Zone #12 x041 Geofence Zone #13 x042 Geofence Zone #14 x043 Geofence Zone #15 x044 Geofence Zone #16 x045 Geofence Zone #17 x046 Geofence Zone #18 x047...
  • Page 68 Parameter value Value Parameter type Default Recommended Eco/Green driving settings (Chapter 13.1) Eco driving type Disable No DOUT control DOUT1 control DOUT2 control DOUT3 control DOUT4 x910 control Eco source 1 (GPS) (accelerometer) Max Acceleration Force Float Max Braking Force Float Max Cornering Force Float...
  • Page 69 Parameter value Value Parameter type Default Recommended control DOUT3 control DOUT4 control iButton List checking 0 (Disable) 1 (Enable) Ignition Timeout Configuring format: <ImmobMode>,<button_enable>,<TMO> Excessive Idling settings (Chapter 13.4) Excessive Idling 0 (Disable) 1 (Enable) Time to stationary x913 Time to movement Configuring format: <Enable>,<Time to stationary>,<Time to movement>...
  • Page 70 Parameter value Value Parameter type Default Recommended Scenario 0 (Disable) 1 (Enable) Acceleration Threshold 8000 4000 X918 Duration Configuring format: <Scenario>,<Threshold>,< Duration> Trip settings (6.3.6.3) Trip 0 (Disable) 1 (Enable) Start Speed Ignition Off Timeout x280 65536 Remember iButton ID, 0 (Disable) 1 (Enable) while Trip detected...
  • Page 71 Parameter Possible Parameter Value Default Value 177 – COM TCP Link Mode Binary, 203 – DTO 1731, 204 –SE500, 10-11 – reserved) COM2 Baudrate 0 – 115200 COM1 start byte 0 - 255 0 – 255 (5 - Silent, 13 - FM Log, 15 – NMEA, 97 - LLS, 98 - LCD, 99 - RFID, 100 - RFID M7, COM2 Mode 115200...

  • Page 72: Profile Switching

    4 profiles. This means that if you set FMB630 to call to a predefined number, you will be able to call it while using any profile. Basic scheme of Global parameters, external devices and profiles is shown below.
  • Page 73 If there are no operator codes entered in all profiles after operator search task FMB630 will check all 3 profiles and won’t find any operators in any list. In such a case, FMB630 will switch to profile 3. Note that before switching to profile 3, the device closes the GPRS session.

  • Page 74: Profile Switching Dependence On I/Oevent

    Figure 45 GSM Operator code profile switching (…) 7.2 Profile switching dependence on I/O event Another profile switch method is based on I/O event. Events happen when the value of enabled I/O intersects thresholds (enter, exit, on both, hysteresis) predefined by High and Low level thresholds.

  • Page 75: Example #1

    FMB630 switches to a defined profile. Using profile switching you can create smart applications. SW2X actions can be performed only if “Profile change on event” is enabled in Global parameters. Pictures below illustrate profile switching depending on digital events:...

  • Page 76: Dual Sim Functionality

    SIM1 slot for FMB630 to switch minimum times. If SIM card is inserted into SIM 2 slot and 1 SIM operator list mode is used, FMB630 will work normally, but there will be more switching activities. In addition, APN settings in Global parameters should be entered for SIM 1 and SIM 2 to avoid not sending records over GPRS.

  • Page 77: Home Network

    SIM 1 Roaming operator list. If there are no available operators from SIM 1 Operator list or the list is empty, FMB630 scans the SIM 2 Roaming operator list for available operators.

  • Page 78: Sim 2 Roaming

    Roaming operators list, FMB630 scans for available operator in the SIM 2 Roaming operator list. If there is an available SIM 2 Roaming operator in the list, FMB630 switches the profile to SIM 2 Roaming, switches the SIM card to Slot 2 and connects to available operator from the SIM 2 Roaming operator list.

  • Page 79: Unknown Operator

    The FMB630 switches to Unknown operator profile using the SIM card it has used before (FMB630 doesn’t switch the SIM cards) when SIM 1 and SIM 2 operator lists are empty and there is no possibility to connect to SIM 1 and SIM 2 Home operators. In this profile FMB630 connects to an operator from the list, received from the network, with the best signal quality.

  • Page 80: Dual Sim Algorithm

    Figure 54 Unknown Operator List 8.1.5 Dual SIM algorithm Two SIM cards use algorithm is shown in the diagram (Figure 55). Figure 55 Dual SIM connection algorithm...

  • Page 81: Data Acquisition

    The FMB630 is always trying to connect to Home operator. If it cannot connect, then it goes to Roaming Operator. The Roaming Operator is chosen by priority. Higher placed operator in the operators list has higher priority. If impossible to connect to Roaming Operator from operator’s list or the operators list is empty, then the FMB630 connects to Unknown operator.

  • Page 82: Min. Distance

    Min. time period Figure 57 Time based tracking 9.1.2 Min. Distance Distance based data acquiring (Figure 58) – records are being acquired when the distance between previous coordinate and current position is greater than defined parameter value. Entering zero means that data won’t be recorded. This method is suitable for non-urban territories where moving trajectory is straight.

  • Page 83: I/Odata Acquisition

    Figure 60 Speed based tracking 9.2 I/O data acquisition Data also can be acquired using input output elements (it’s change). All base elements are declared in sMode and in I/O 9.2.1 Configuration Data acquisition by I/O elements can be configured selecting I/O menu in configurator (refer to Chapter 6.3.8.2).

  • Page 84: Sleep Mode

    Event on Change: record is generated on every source value change. 10 SLEEP MODE While in sleep mode, FMB630 sets GPS receiver to sleep mode but GSM/GPRS module stays active, in Sleep mode power usage can be decreased to save vehicle’s battery, because GPS module is turned off.

  • Page 85: Deep Sleep Mode

     can save periodical or eventual records;  send data to server; Note: If there is no need to save or send periodical data FMB630 has to be configured to switch to another profile on Deep Sleep Event where Min Period...

  • Page 86: Online Deep Sleep Mode

    13 FEATURES AND SCENARIOS 13.1 ECO driving or Green driving Scenarios Six scenarios are available on FMB630 device. All scenarios can be activated at the same time and all activated scenarios can be configured to control the same DOUT (expect excessive idling).

  • Page 87: Mounting Requirements

    (Figure 66) mounting recommendations are displayed. Please note that beside those recommendations 1. You can choose how FMB630 is deployed. It means that that there is no effect to measurements if FMB630 top/bottom side points up or down. 2. Device can be deployed at any place in the car.
  • Page 88 Deviations of maximum +/- 15 are allowed (Figure 67) Figure 67 MAX deviation from horizontal plane of FMB630 mounting Figure 68 Horizontal position MAX deviation of FMB630 mounting Horizontal position must be as flat as possible – parallel with vehicle plain.

  • Page 89: Configuration

    13.1.2 Configuration Parameters used with ECO driving or Green driving functionality. Figure 69 ECO driving or Green driving configuration parameters Table 34 ECO driving or Green driving parameters description ECO driving/Green driving configuration Description parameter name ECO driving type Selects which DOUT will control scenario Data source Selects from where data will be taken Value which can be reached while accelerating without triggering harsh...

  • Page 90: Overspeeding Scenario

    If any of three cases are satisfied event is generated. Record is saved and sent to server (FMB630 must be configured properly). Event value is multiplied by 10 before sending/saving record to get more precision when displaying data*.

  • Page 91: Configuration

    13.3.1 Configuration Figure 71 Immobilizer configuration parameters Immobilizer. Selects which DOUT will control Immobilizer Scenario. IButton list checking. When disabled turn on Immobilizer Scenario. Ignition timeout. Time that need to be passed when ignition (DIN1) turns off to reactivate scenario. Authorized Driving (iButton list checking enabled).

  • Page 92: Jamming Detection Scenario

    Figure 73 Excessive Idling Configuration 13.5 Jamming Detection Scenario Scenario is activated and DOUT can be control when jamming is detected 13.5.1 Configuration Figure 74 Jamming Detection Configuration Jamming Detection: Scenario Enable, Disable and DOUT selection Sesitivity: Sensitivity to control false jamming detection Timeout: Jamming timeout is the duration after how much time device should initiate jamming event after detecting jamming.

  • Page 93: Crash Detection Scenario

    COM1 and Com2 are used to connect external devices. 13.8.1 Silent Mode FMB630 doesn't do any activity in silent mode. Logs aren’t saved and any data isn’t sent. 13.8.2 FM Log Mode This is default mode of the FMB630. It is suitable for debugging.

  • Page 94: Rfid Hid Mode Configuration

    * From Hercules (server) Send "#DO DAT=you text here" (in special packet) Notes: #DO DAT= command prints only to COM2 Link between FM and server has to be established for this functionality to work On Valid data Receive Status LED will blink. 13.8.5 RFID HID Mode Configuration 1.

  • Page 95: Tcp Link Mode

    2. External Devices ->COMx Settings->Mode = TCP Link Mode(Binary) FMB630 supports buffering messages when there is no data link, messages will be saved to flash with a timestamp. Space reserved for buffering is 64 kB. By default buffering is disabled. To enable set “TimeStamp”...

  • Page 96: Nmea Log Mode

    After turning bluetooth module ON you need to pair it with your phone or tablet. 1. Download ‚Bluettoh Terminal‘ app and scan for visible BT devices using your Android smartphone connect FMB630 device. default name: FMB630_last_7_imei_digits 2. To start log enter the command in terminal: .log:1 then wait few minutes while log is running.

  • Page 97: Bluetooth Headset

    . To check if adapter is successfully connected, call to FMB630 device, Hands Free device should start ringing. If you later restart FMB630 it will automatically connect to this adapter. Hands Free device Bluetooth connection pairing instructions depends on specific model.

  • Page 98: Sms Command List

    14 SMS COMMAND LIST SMS commands are used to identify FMB630 current state, possible configuration errors, perform reset, set parameters, switch on/off outputs, etc. SMS commands should be sent along with module login and password and sender number must be entered in the authorized number list (if at least one other number is entered). Please see SMS settings in Chapter 6.3.5.3 for more details.

  • Page 99: Getstatus

    Command Description Response flush Initiates all data sending to specified target server #,#,#,#,#,#,# 1.# - IMEI 2.# - APN 3.# - LOGIN 4.# - PASS 5.# - IP 6.# - PORT 7.# - MODE (0-TCP/1-UDP) sn x [x=0;1] Enable/disable static navigation banlist Banlist information crashlog...

  • Page 100: Getops

    Day Of Week – indicates current day of week starting from 1 – Monday, 2 – Tuesday, etc. Time Indicates current GMT time WeekTime Indicates time in minutes starting from Monday 00:00 GMT Answer Example: Clock Sync: 1 DOW: 4 Time 12:58 Weektime: 6538 14.3 getops Table 38 getops command response Response details...

  • Page 101: Loadprofile

    BL Ver Bootloader Version Modem App Ver Version of modem application Hardware type Answer Example: Code Ver:00.02.72 Device IMEI:352094087256621 Device ID:000014 BL Ver:06.45 Modem Ver:Teltonika TM25Q TM25Q_R_01.00.00.00_001, 2016/12/20 12:46 Hw:K- Line TM25Q 14.12 getio Table 44 getio command response Response details...

  • Page 102: Deleterecords

    Restart Counter Error Counter Number of Sent Records Number of broken records Profile CRC Fail counter Failed GPRS counter Failed link counter UPD Timeout counter Current profile #;#;#;#;# # - how many times appropriate profile ( Profile0; Profile1; Profile2; Profile3; Profile4 ) was loaded Sent SMS Counter NOGPS No GPS Timer...

  • Page 103: Setparam

    Table 47 getparam#### Response details Description Profile number and parameter ID Value Parameter value Example: ‘getparam 240’ command will request SIM1 APN. 14.18 setparam #### # Sets new value for parameter. ID consists of 4 digits – first digit identifies profile, second, third and fourth identifies parameter ID as described in Parameters Configuration chapter 6.3.

  • Page 104: Getgnss

    14.20 getgnss Table 49 getgnss Response details Description GPS fix SAT GL Total glonass sattelites Total gps sattelites Answer Example: FIX:1 SAT GL:5 GP:10 14.21 sn x Returns state of static navigation and previous state: Static Nav is Disabled. Was:X or Static Nav is Enabled.

  • Page 105: Fmb630 With Lv-Can 200 And All-Can 300 Can Adapter

    LV-CAN200 is used to listening data from light vehicles, while ALL-CAN300 is used to listening data from any type of transport: light vehicles, Trucks, busses, agriculture and other special transport. With those adapters FMB630 device is able to collect and send vehicle data.

  • Page 106: Can200 And All-Can300 Program Number Selection

    Figure 80 connection block diagram FMB630 shares the same USB port for connecting adapter and configuring device with PC. LV-CAN200 and ALL-CAN300 Technical characteristics: PARAMETER VALUE Supply voltage 9 to 50V Power supply current Average 10mA Max (peak) 100mA Working temperature -40..85 ºC...

  • Page 107: Program Number Logic Change

     Hold SWITCH down till LED stars blinking  Release the SWITCH  Then LED starts blinking and counting first digit of program number, (one blink means digit 1, two blink digit 2 etc.)  To stop counter push SWITCH ...
  • Page 108 Example: If use oldest connection schemes where program number displayed as 3 digit program number: Using LV-CAN200/ALL-CAN300 Bootloader from soft version 2017-09-27 need add "1" before it:...

  • Page 109: Simple-Can - Contactless Can-Bus Reader

    15.3 SIMPLE-CAN - contactless CAN-BUS reader SIMPLE-CAN is contactless adapter used to read vehicle CAN data with LV-CAN200, ALL- CAN300. If LV-CAN200 or ALL-CAN300 connection requires two CAN lines to get all data, then you need two SIMPLE-CAN readers TECHNICAL DETAILS ...

  • Page 110: Connecting Fmb630 Can Adapters All-Can300 And Lv-Can200

    15.4 Connecting FMB630 Can adapters ALL-CAN300 and LV-CAN200 Connect USB Plug to FMB630 device, connect Light Vehicles Can adapter to other end of the cable. Connect Light Vehicles Can adapter Pin 1 and Pin 2 to cars CAN bus. CAN interface location of the supported light vehicle is described on mounting scheme.

  • Page 111: Fmb630 Configuraton

    FMB630 can be configured using “SCAN” function or “Offline Configuration” SCAN function – is in use when FMB630 is connected to CAN adapter (Figure 79), then wait 10s (Note, that car engine must be started), disconnect adapter from FMB630, and connect PC USB cable to FMB630 Device, It is very important not to disconnect FMB630 from power source during this operation, because if FMB630 is reconnected all received CAN bus data will be lost.
  • Page 112 For example Speed changes, low fuel level, engine temperate, etc. Send data to server field – allows enabling CAN element so it is added to the AVL data packet and sent to the server. By default, all CAN elements are disabled and FMB630 records only GPS data.

  • Page 113: Lvcan Mode (Id=903)

    Send data with 0, if ignition is off. Depending on LVCAN/ALLCAN I/O parameters and ignition status, FMB630 can send locked (last known) LVCAN/ALLCAN I/O parameters values, reset values (set to 0) and active (real time) parameters values. When ignition is off, LVCAN/ALLCAN I/O parameters values sent to server are:...

  • Page 114: Send Data With 0, If Ignition Is Off (Id=904)

    Tachograph Vehicle Speed reset Tachograph Driver Card Presence active Driver1 States active Driver2 States active Driver1 Continuous Driving Time active Driver2 Continuous Driving Time active Driver1 Cumulative Break Time active Driver2 Cumulative Break Time active Driver1 Selected Activity Duration active Driver2 Selected Activity Duration active Driver1 Cumulative Driving Time...
  • Page 115 Table 54 ACQUIRED ALL-CAN300 PARAMETRS IO ID Property ID in AVL Property Name Bytes Description packet LVCAN Engine Work Engine work time in minutes Time LVCAN Engine Work Total Engine work time in minutes Time (counted) LVCAN Total Mileage Total Vehicle Mileage, m (counted) LVCAN Fuel Consumed Total Fuel Consumed,liters * 10...
  • Page 116 Property ID in AVL Property Name Bytes Description packet LVCAN Driver1 Continuous Driving Driver1 Continuous Driving Time, minutes Time LVCAN Driver2 Continuous Driving Driver2 Continuous Driving Time, minutes Time LVCAN Driver1 Driver1 Cumulative Break Time, minutes Cumulative Break Time LVCAN Driver2 Driver2 Cumulative Break Time, minutes Cumulative Break Time LVCAN Driver1 Duration...
  • Page 117 Table 55 ALLCAN300 IO element values Description Size, Value bitmasks Bytes Control state flags Byte0 (LSB): 0x01 – STOP 0x02 – Oil pressure / level 0x04 – Coolant liquid temperature / level 0x08 – Handbrake system 0x10 – Battery charging 0x20 –...
  • Page 118 0x04 – Air filter is plugged 0x08 – Alarm oil temperature in hydraulic system of chasis 0x10 – Alarm oil temperature in hydraulic system of drive cylinders 0x20 – Alarm oil pressure in engine 0x40 – Alarm coolant level 0x80 –...
  • Page 119 0x80 – immobiliser, bit appears during introduction of a programmed sequence of keys in the car. Byte1: 0x01 – the key is in ignition lock 0x02 – ignition on 0x04 – dynamic ignition on 0x08 – webasto 0x20 – car closed by factory's remote control 0x40 –...

  • Page 120: Can

    0x3X – limit #3: 15 minutes before optional warning 1 0x4X – limit #4: optional warning 1 reached 0x5X – limit #5: 15 min before optional warning 0x6X – limit #6: optional warning 2 reached Door status value: Min – 0, Max – 16128 Door status is represented as bitmask converted to decimal value.

  • Page 121: General Description

    Available parameters: • Total Fuel • Total Distance • Status of brake pedal * • Engine Torque * • Actual fuel • Accelerator pedal position * • Status engine brake • Speed * • RPM • Engine hours • Vehicle Weight * •...

  • Page 122: Example

    Figure 88 CAN configuration window CAN message ID type: Message ID type (Figure 89) two types according to SAEJ1939 standard: Standard ID (value: 0 to 0x7FFh) and Extended ID (value: 0 to 0x1FFFFFFFh). Figure 89 CAN message ID types Message ID value is entered in hex format. This parameter is used to configure hardware message filter (Figure 90).
  • Page 123 All Mercedes Benz Actros 2 models with Vehicle Identification Number (VIN) starting with WDB93 have a possibility to connect FMB630 module to CAN bus. This can be done by connecting to special PSM module (which may or may not be included in the truck) or ground module of the vehicle.
  • Page 124 (Figure 93). Figure 93 Example When certain message is filtered, FMB630 checks which data bytes should be sent to server. Document indicates that 5-8 bytes are used in FMS standard. Table 57 FMS standard – fuel consumption (5-8 bytes)

  • Page 125: Fmb630 J1708 Connection

    HEX. 00 03 84 23(HEX) = 230435(DEC). Notice, that data resolution is 0.5L/bit gain – value has to be multiplied by 0.5, therefore vehicle used a total 115217,5 liters of fuel. 16.4 FMB630 J1708 Connection Figure 95 FMB630 diagram...

  • Page 126: Software Configuration Of Fmb630 With J1708

    J1708-A J1708A J1708+ J1708-B J1708B and J1708- Figure 97 Example of Diagnostic port 16.5 Software Configuration of FMB630 with J1708 Firmware version: 00.00.24 or above Configurator version: 1.0.0.12 Step 1 Enable J1708 Line in External Devces Tab Figure 98 J1708 Line configuration...

  • Page 127: Autocan Description

    AutoCAN function allows user to automatically scan for available messages on CAN bus and configure CAN data sending to server. In order to configure AutoCAN connect FMB630 to computer with Port ½ cable. Launch FMB630xx configurator version 1.1.1.7 or higher. Push “Connect“button, then „CAN“button (Figure 101).
  • Page 128  Category – shows CAN message;  Parameter – shows configurable parameter name;  Value – shows scanned value of parameter;  Send data to server – allows to choose the type of data when it‘s generated: o Disabled – Data will not be collected o On low priority –...

  • Page 129: Can Monitoring

    Configuration section. 16.6.3 Offline configuration When FMB630 device is not connected to CAN bus you can configure CAN data sending by pushing “Offline configuration” button. When offline configuration is enabled a configuration table of all FMS standard CAN data is shown.
  • Page 130 Category name Par Nr in Par Nr. In (signal) name Size (Bytes) Param IO Value range P:FMS: P:FMSDAT: 61444 – engine speed X 0 – 8031,875 (rpm)* Electronic Engine Controller #1 Axle location 1-15 65258 – Vehicle [11-25] Tire location 1-15 Weight ** (Tire No 1 -...
  • Page 131 Category name Par Nr in Par Nr. In (signal) name Size (Bytes) Param IO Value range P:FMS: P:FMSDAT: Driver 1 time rel. 0 – Normal states 1 – 15min bef. 4,5h 2 – 4,5h reached 3 – 15min bef. 9h 4 –...
  • Page 132 park brakes). It is necessary for safe drivetrain behavior that the switch activates before the physical braking components are activated (i.e. Disengage the cruise control function prior to the activation of friction brakes). 00 – Brake pedal released 01 – Brake pedal pressed 10 –...
  • Page 133 01 – Clutch pedal pressed 10 – Error 11 – Not available Data Length: 2 bits Resolution: 4 states/2 bit, 0 offset Data Range: 0 to 3 Operational Range: same as data range Type: Measured Supporting information: PGN 65265 Note: Firmware captures only [0, 1] values. [2, 3] – are ignored. PTO state information: This parameter is used to indicate the current state or mode of operation by the power takeoff (PTO) governor.
  • Page 134 Set 00101b — Used to indicate that the PTO governor is establishing current speed as the operating speed (captured value). Decelerate/Coast 00110b — Used to indicate that the PTO governor is in the process of ramping down, or coasting, from the current operating speed. Resume 00111b —...
  • Page 135 The ratio of actual position of the analog engine speed/torque request input device (such as an accelerator pedal or throttle lever) to the maximum position of the input device. This parameter is intended for the primary accelerator control in an application. If an application has only one accelerator control, use SPN 91.
  • Page 136 Data Length: 1 byte Resolution: 0.4 %/bit, 0 offset Data Range: 0 to 100 % Operational Range: same as data range Type: Measured Supporting information: PGN 65276 Note: Value sent to server is already adjusted with bitgain. Since data is sent as U32, value after floating point is ignored.
  • Page 137 Resolution: ASCII, 0 offset Data Range: 0 to 255 per byte Operational Range: same as data range Type: Measured Supporting information: PGN 65260 Note: Firmware expects VIN to fit into 24 bytes. According to captured VIN length either 1/2/3 IO ID’s will be sent to server (8 Bytes each).
  • Page 138 Type: Status Supporting information: PGN 64977 Note: Firmware captures all values [0x00-0x03]. FMS-standard requests supported: Status signal which indicates if the FMS Vehicle Interface (FMS Gateway) will respond to requests from the FMS device for the PGNs listed in the FMS Interface Specification. This mode is to support FMS gateway devices that only operate in a ‘Request’...
  • Page 139 Note: Value sent to server is already adjusted with bitgain. Vehicle motion: Indicates whether motion of the vehicle is detected or not. 00 Vehicle motion not detected 01 Vehicle motion detected 10 – Error 11 – Not available Data Length: 2 bits Resolution: 4 states/2 bit, 0 offset Data Range: 0 to 3 Operational Range: same as data range Type: Measured...
  • Page 140 Indicates if the driver approaches or exceeds working time limits (or other limits). 0000 Normal/No limits reached 0001 Limit #1 – 15 min before 4 ½ h 0010 Limit #2 – 4 ½ h reached 0011 Limit #3 – 15 min before 9 h 0100 Limit #4 –...
  • Page 141 Tachograph performance: Indicates the tachograph performance; including electronic or mechanical analysis, instrument analysis, speed sensor analysis, mass storage analysis, and printer analysis. 00 – Normal performance 01 – Performance analysis 10 – Error 11 – Not available Data Length: 2 bits Resolution: 4 states/2 bit, 0 offset Data Range: 0 to 3 Operational Range: same as data range Type: Status...
  • Page 142 Data Length: 2 bytes Resolution: 1/256 km/h per bit, 0 offset Data Range: 0 to 250.996 km/h Operational Range: same as data range Type: Measured Supporting information: PGN 65132 Note: Since FM FW sends this parameter as U16 (2 Bytes), value after floating point is discarded. So data limit becomes [0-250].
  • Page 143 Data Length: 2 bytes Resolution: 0.05 L/h per bit, 0 offset Data Range: 0 to 3,212.75 L/h Operational Range: same as data range Type: Measured Supporting information: PGN 65266 Note: Since FW sends this parameter as U32, value after floating point is discarded. Data limit becomes [0-3,212].

  • Page 144: Autocan Configuration Over Sms

    <[0-7]>,<int32>,<int32>,<[0-5]>,<int32> For example: <space><space>setparam 3347 2,70,50,3,10 Here we set FMB630 to make a high priority event once the FMB630 either reaches higher than 70km/h speed or starts going lower than 50km/h. **If we want to configure FMB630 to make a panic event everytime brake pedal is either pushed or released, the SMS we would have to send is: <space><space>setparam 3346 3,0,0,1,10 (here we skip HighLevel and LowLevel so we write 0)

  • Page 145: Using Tachograph

    17 USING TACHOGRAPH FMB630 device can read tachograph data. User can connect FM to vehicle unit tachograph device. Supported devices are: Siemens VDO Digital Tachograph – DTCO 1381 (release 1.3a, 1.4 or later) and Stoneridge Tachograph – SE5000 (release 7.1 or later) 17.1 Connecting to tachograph...
  • Page 146  Measure resistance between the C5 (CAN2 H) and C7 (CAN2 L) contacts;  If the multimeter shows ~120 Ohms, skip the next step;  If the multimeter shows kiloOhms resistance then it is needed to connect tachograph C8 (CAN-RES) and C7 (CAN2 L) contacts with wire and then perform further actions;...

  • Page 147: Web Tacho

    FM functionality, parameters described in table 32 17.2 WEB Tacho WEB Solution for Tachograph files download. Teltonika Tacho WEB Solution is a big forward leap in remote tachograph data files download. Solution is easily manageable and does not require any complex software* installation. Everything is accessible via web page. Now you can download tachograph files from any place and from any PC with internet access.

  • Page 148: Tachocheck Sms

    FMB630 device has a possibility to connect to WebDDD IP every 1 hour and check if there are any schedules for downloading DDD files. If FMB630 connects to WebDDD server, and there is a planned schedule but other device is already downloading and company card is in use, device keeps link with WebDDD server but still sends data to main server with AVL data.

  • Page 149: Rs485 Interface

     Non-zero – FMS data detected on bus. FMS data value is shown in hexadecimal system and it is not important for the client. 18 RS485 INTERFACE RS485 supports only Half Duplex communication. It means that at the same time you can’t send/receive Data.

  • Page 150: Rs485 Receive - Silent Mode

    18.1.1 RS485 Receive - Silent Mode Figure 110 Silent Mode RS485 Works in receive mode. Support debug and testing commands. When command is received answer is sent after that it back up to Receive mode. 18.1.2 RS485 Transmit - FM Log Mode Figure 111 FM Log Mode RS485 works in transmit mode, it prints FM log.

  • Page 151: Rs485 Receive -Tcp Link Mode

    Figure 113 LLS Mode The mode supports up to five LLS. Baud rate must be 19200. LLS have receiver id. 18.1.5 RS485 Receive -TCP Link Mode Figure 114 TCP Link Mode RS485 works in receive mode. When data received from server RS485 is switched to transmit mode.

  • Page 152: Rs485 Interface

    Figure 117 RFID I/O parameter To set up FMB630 so it can be connected to an RFID reader, Global parameters have to be set up. Go to extermal devices and set up COM1 or COM2 settings to RFID Mode or RFID MF7 Mode (the used mode depends on the mode that the RFID reader works).

  • Page 153: Garmin

    Figure 118 RFID Global parameter settings The difference between RFID Mode and RFID MF7 Mode is that in RFID Mode FMB630 understands RFID messages that are in hexadecimal format and RFID MF7 Mode understands messages that are in decimal format. For example: RFID Mode message –...

  • Page 154: Standard Protocols

    products and FMI versions, please go to Garmin Products. Notice that some Garmin products use different connection cables than others. 20.1.1 Standard protocols Text Message Protocol: • Allows text messages sent to device to be displayed in "inbox" on unit. •...

  • Page 155: Supported Features On Tavl Client Application

    • Drivers can store up to 120 canned messages, eliminating the need to type while driving. Status Protocol: • Up-to-the-minute communications that allow drivers to automatically send status updates. • Driver's units can store up to sixteen status indicators such as start/stop shift, on/off break, etc.

  • Page 156: Connection And Pinout

    Figure 120 RJ45 Pinouts In order to connect Garmin PND to FMB630 , Garmin mode has to be set in Global parameter settings ( Figure 121 ). Simply choose Garmin mode in COM2 settings mode, but you cannot activate Garmin mode in both ports at the same time.

  • Page 157: Lls Sensor

    Teltonika or a representative. Firmware is updated over GPRS or using cable update method (see chapter 4 for more information). The LLS fuel sensor must be connected to the FMB630 device. The FMB630 -LLS fuel sensor schemes are shown below Figure 122.
  • Page 158 FMB630 -LLS fuel sensor connection scheme RJ-45 male plug _____________________________ *Teltonika is not responsible for any changes made by the manufacturer, which is not declared in fuel level sensor documentation. Then FMB630 must be configured. Both fuel level and fuel temperature has to be set up by configurator’s I/O menu (see Figure 123):...

  • Page 159: Mvc300 Camera

     MVC300 operational principals; 22.2 Startup and Configuration To get FMB630 ready for downloading pictures from MVC300 camera, you need to use base fw 00.01.09 or newer. In configuration, you must set server IP, port and APN of SIM card,...
  • Page 160 Figure 125 Simple Configuration To set up picture creation configuration, select Advanced Configuration, which is in lower right corner of configuration. Select Camera page Figure 126 Camera Configuration...

  • Page 161: Camera Parameters In Fmb630

    Between pictures will be 3 sec time gap. 22.2.2 Camera parameters in MVC300: To prepare MVC300 connection with FMB630, following steps must be done: MVC300 must have firmware version - MVC330_WebUI_FW_MVC330_F_00.01.599 or newer. Main thing is, that firmware must be with F marking, which means, FM device support. To check what firmware version your MVC300 have, you need to go - http://192.168.1.10, it is camera‘s...

  • Page 162: Fmb630 And Mvc300 Connection

    It is possible to send commands to FMB630 using GPRS. When FMB630 sends records periodically to a server, a message could be sent from the server and FMB630 will reply to it. FMB630 has to be connected to the server in order to receive commands.
  • Page 163 Command Description #GET VERSION Receive firmware version #GET NETWORK Get GSM operator to which device is connected #GET IMSI Get IMSI of the device #GET OUT Get DOUT values #DO REPORT Save a record #GET ROAMINGX=Y Get operator from the list of a certain profile, X – profile, Y – operator number in a list #GET REMIPX Get IP and port number from the configuration of a certain profile, X –...

  • Page 164: Debug Mode

    FMB630 is able to transmit its current state when connected to PC using PORT1/2 and USB cable. To debug FMB630 with USB cable, in terminal you should set high level to DTR pin. It is used to detect errors and provide information to possible solutions when operating as unexpected.

  • Page 165: Fmb630 Remote Log

    – none. Click on ‘Start Log’ button and save a new file. Then click ‘Connect’ to start receiving messages from FMB630 (see Figure 130) Figure 130 Terminal Window To debug NMEA GPS data, connect PORT3 cable to COM2 port, or connect PORT2 cable and enable nmea log mode, or via USB cable activating nmea log mode by sending .log_nmea:1...
  • Page 166  modem (4) – send just AT commands  NMEA (5) – send NMEA log. o <APN> - operators’ APN which will be used for data sending; o <username> - operators’ username; o <password> - operators’ password; o <IP> - servers’ IP address to which offline/online log will be send after request (“log2srvstart”);...
  • Page 167 Figure 131 STEP 2  click Log to File, then choose the directory where you want to log it in, give your log a name and click open  Right click again and click on Log Enable OR just use Ctrl + L combination instead.
  • Page 168 Figure 132 STEP 3  Sending “Terminal’s” commands through Hercules server Figure 133...

  • Page 169: Mounting Recommendations

    These points in the car are the battery terminals. Therefore, we recommend connecting the power of FMB630 (wire GND and POWER) directly to the battery terminals. Another valid option is to connect the wires to the main POWER cable inside the fuse box (if there is none, then to the power supply where the fuses of vehicle’s computer...

  • Page 170: Connecting Antennas

     When placing antennas avoid easily reached places.  Avoid GNSS antenna placement under metal surfaces.  Avoid placing FMB630 device near car radio, speakers or alarm systems.  GNSS antenna must be placed so its state is as horizontal as possible (if antenna is leant more than 30 degrees, it is considered incorrect mounting).

  • Page 171: Ec Declaration Of Conformity

    26 EC DECLARATION OF CONFORMITY...

  • Page 173: Warranty Policy

    27 WARRANTY POLICY Teltonika provides a One (1) year manufacturer’s warranty, which covers all of Teltonika products. Batteries are covered by 6 month warranty support. 28 CHANGE LOG Date Version Comments 2017-05-12 v1.0 Initial Release 2017-05-25 v1.1 Updated LVCAN200 and ALLCAN300 description.

Table of Contents