Search results

Page title matches

• Template:FM36YX Monitoring
  I/O monitoring starts after enabling I/O element and setting up I/O parameters as it is sh
  142 bytes (26 words) - 08:36, 30 July 2018

Page text matches

• Template:FM36 CAN adapters
  ...lture transport and other special transport. Using these adapters {{{model|FM36YX}}} device is able to collect and send vehicle data. ==Connecting {{{model|FM36YX}}} CAN adapters ALL-CAN300 and LV-CAN200==
  27 KB (3,938 words) - 13:31, 9 August 2018
• Template:FM36M1 CAN adapters
  ...lture transport and other special transport. Using these adapters {{{model|FM36YX}}} device is able to collect and send vehicle data. ==Connecting {{{model|FM36YX}}} CAN adapters ALL-CAN300 and LV-CAN200==
  27 KB (3,938 words) - 07:42, 13 August 2018
• Template:FM36YX SMS events
  SMS events functionality allows {{{model|FM36YX}}} to send a configured SMS when an event is * [[{{{model|FM36YX}}}_Features_settings#Green_Driving|Green Driving]]
  4 KB (709 words) - 11:45, 12 June 2018
• Template:FMA1 SMS events
  SMS events functionality allows {{{model|FM36YX}}} to send a configured SMS when an event is * [[{{{model|FM36YX}}}_Features_settings#Green_Driving|Green Driving]]
  4 KB (709 words) - 08:40, 23 August 2018
• Template:FMA1 Scenarios settings
  Five scenarios are available on {{{model|FM36YX}}} device. Green driving, Over speeding, Jamming detection, Immobilizer and * [[{{{model|FM36YX}}}_Features_settings#Green_Driving|Green Driving]]
  5 KB (707 words) - 16:06, 6 February 2019
• Template:FMA1 Trip and Odometer settings
  ...again. Virtual odometer as an I/O element can be also used with [[{{{model|FM36YX}}}_Features_settings#Trip|Trip]]. ...y when trip starts and finishes. This feature is available on all {{{model|FM36YX}}} hardware versions without limitations.
  3 KB (553 words) - 13:33, 6 September 2018
• Template:FM36YX Trip and Odometer settings
  ...again. Virtual odometer as an I/O element can be also used with [[{{{model|FM36YX}}}_Features_settings#Trip|Trip]]. ...y when trip starts and finishes. This feature is available on all {{{model|FM36YX}}} hardware versions without limitations.
  3 KB (503 words) - 10:32, 9 August 2018
• Template:FM36YX I/O settings
  ...tions with Permanent I/O elements: simple monitoring and event generating. Monitoring method is used when current I/O information needed with regular GNSS coordi ==Monitoring==
  24 KB (2,909 words) - 11:05, 10 August 2018
• Template:FM36M1 I/O settings
  ...tions with Permanent I/O elements: simple monitoring and event generating. Monitoring method is used when current I/O information needed with regular GNSS coordi ==Monitoring==
  24 KB (2,905 words) - 07:35, 13 August 2018
• Template:FMA120 I/O settings
  ...tions with Permanent I/O elements: simple monitoring and event generating. Monitoring method is used when current I/O information needed with regular GNSS coordi ==Monitoring==
  25 KB (2,961 words) - 08:33, 23 August 2018
• Template:FMA202 I/O settings
  ...tions with Permanent I/O elements: simple monitoring and event generating. Monitoring method is used when current I/O information needed with regular GNSS coordi ==Monitoring==
  14 KB (1,723 words) - 09:25, 6 September 2018
• Template:FMA110 I/O settings
  ...tions with Permanent I/O elements: simple monitoring and event generating. Monitoring method is used when current I/O information needed with regular GNSS coordi ==Monitoring==
  24 KB (2,920 words) - 13:31, 23 August 2018
• Template:FM36M1 General description
  {{{model|FM36YX}}} is GNSS, LTE CAT M1, NB IoT terminal with backup battery for SPECIAL applications. {{{model|FM36YX}}}is designed for light vehicles tracking but also suitable for advanced
  776 bytes (118 words) - 13:28, 12 August 2018
• Template:I/O events
  ...s configured High/Low boundaries or Hysteresis event generation is chosen (Monitoring does not generate event, so SMS event could not be configured).
  425 bytes (67 words) - 10:31, 1 June 2018