*[[FMA120 I/O settings|I/O settings]]
**[[FMA120 I/O settings#Monitoring|Monitoring]]
912 bytes (115 words) - 08:19, 6 May 2019
*[[FMA110 I/O settings|I/O settings]]
**[[FMA110 I/O settings#Monitoring|Monitoring]]
912 bytes (115 words) - 00:17, 3 April 2020
*[[FMA202 I/O settings|I/O settings]]
**[[FMA202 I/O settings#Monitoring|Monitoring]]
950 bytes (118 words) - 08:40, 6 May 2019
*[[FMA204 I/O settings|I/O settings]]
**[[FMA204 I/O settings#Monitoring|Monitoring]]
950 bytes (118 words) - 09:04, 6 May 2019
...after fix is obtained. Data could be sent according to I/O parameters in I/O section.
* Device has up to 3 min. hardcoded time to get fixed position while it i's awake from a Sleep Mode. <br>
19 KB (3,110 words) - 11:40, 6 February 2024
...All I/O configuration is as described [[{{{model|FMC640}}}_I/O_settings|I/O elements]].
LVCAN elements can be configured in the same way as normal I/O elements. LVCAN IO elements can also be configured remotely via SMS command
51 KB (7,317 words) - 13:03, 8 February 2023
...All I/O configuration is as described [[{{{model|FMB640}}}_I/O_settings|I/O elements]].
LVCAN elements can be configured in the same way as normal I/O elements. LVCAN IO elements can also be configured remotely via SMS command
44 KB (6,307 words) - 09:25, 9 September 2022
...All I/O configuration is as described [[{{{model|FMM640}}}_I/O_settings|I/O elements]].
LVCAN elements can be configured in the same way as normal I/O elements. LVCAN IO elements can also be configured remotely via SMS command
51 KB (7,317 words) - 13:05, 8 February 2023
...cted to {{{model|FMC640}}} device. All I/O configuration is as described I/O elements}
LVCAN elements can be configured in same way like with normal I/O elements. LVCAN IO elements can also be configured remotely via SMS command
58 KB (8,227 words) - 10:44, 17 January 2024
...cted to {{{model|FMM650}}} device. All I/O configuration is as described I/O elements}
LVCAN elements can be configured in same way like with normal I/O elements. LVCAN IO elements can also be configured remotely via SMS command
58 KB (8,226 words) - 10:44, 17 January 2024
...evices connected to FMB641 device. All I/O configuration is as described I/O elements}
LVCAN elements can be configured in same way like with normal I/O elements. LVCAN IO elements can also be configured remotely via SMS command
58 KB (8,228 words) - 10:45, 17 January 2024
...on your needs). Also set operand and low/high settings in order to receive events based on specific conditions, e.g.: '''Yawning - Low priority - Low/High le
...M''' in the Mode drop-down menu, afterwards '''DSM COM1''' and '''Camera I/O''' should appear in the tab list.
10 KB (1,629 words) - 15:52, 11 April 2024
* Device has up to 3 min. hardcoded time to get fixed position while it i's awake from a Sleep Mode. <br>
...after fix is obtained. Data could be sent according to I/O parameters in I/O section.
15 KB (2,486 words) - 11:39, 6 February 2024
* Device has up to 3 min. hardcoded time to get fixed position while it i's awake from a Sleep Mode. <br>
...after fix is obtained. Data could be sent according to I/O parameters in I/O section.
15 KB (2,486 words) - 11:39, 6 February 2024
* Device has up to 3 min. hardcoded time to get fixed position while it i's awake from a Sleep Mode. <br>
...after fix is obtained. Data could be sent according to I/O parameters in I/O section.
15 KB (2,480 words) - 10:35, 13 March 2024
...n data will be used to determine harsh acceleration, braking and cornering events.<br />
...on the impact magnitude that is required to be detected. TFT100 can detect events ranging between a slight tapping on the device and a severe accident.<br />
10 KB (1,539 words) - 14:24, 23 March 2023
...ion type*. For more settings go to Advanced settings tab to enable various events.
...n: left;" |<br>'''Magnetic field event''' - adjust if the device generates events based on detection or exit (loss) of the magnet.
13 KB (1,817 words) - 15:07, 6 December 2023
..., just that it is included as IO element to have the possibility to create events for it.
* There is a I/O element with ID 37. This is a 1 byte element - it is speed from OBDII data.
732 bytes (145 words) - 10:09, 2 May 2019
..., just that it is included as IO element to have the possibility to create events for it.
* There is a I/O element with ID 37. This is a 1 byte element - it is speed from OBDII data.
732 bytes (145 words) - 10:39, 30 July 2019
..., just that it is included as IO element to have the possibility to create events for it.
* There is a I/O element with ID 37. This is a 1 byte element - it is speed from OBDII data.
732 bytes (145 words) - 09:44, 8 August 2019
