Jump to content

Template:FTX Input/Output (I/O): Difference between revisions

From Teltonika Telematics Wiki
No edit summary
No edit summary
Line 70: Line 70:
==Manual CAN==
==Manual CAN==
[[File:FTX manual can.png|alt=|right|500px]]
[[File:FTX manual can.png|alt=|right|500px]]
Manual CAN functionality allows user to read data via CAN BUS without requiring additional CAN protocol development from the firmware side.
*'''Priority''' – defines the priority of Manual CAN I/O: 0 – disabled, 1 – low, 2 – high.
*'''CAN type''' - defines which CAN ID type will be received and requested (Standard - 11bit, Extended - 29bit).
*'''CAN ID''' – depends on CAN Type parameter and defines which CAN ID will be received by device.
*'''Data mask''' – defines which data bytes are sent to the server (sometimes not all data bytes are necessary). Up to 8 particular data bytes can be selected for each CAN ID.
*'''Operand''' – defines when to generate event: On Exit, On Entrance, On Both, Monitoring, On Hysteresis, On Change or On Delta Change.


==Manual CAN Commands==
==Manual CAN Commands==

Revision as of 08:37, 27 February 2025

When no I/O element is enabled, AVL packet comes with GNSS information only. After enabling I/O element(s) AVL packet contains current value(s) of enabled I/O element(s) along with GNSS information.

Search

Enter the keyword to search for the desired permanent I/O.

More Filters

It provides additional filter options such as Priority, Operand, and rows with currently available values.

View Columns

Filters the necessary tabs when making configuration changes or viewing. Priority, Operand, Low Level, High Level, and Event Only Options are available filters. The Input name and Current Values are permanent columns.

Permanent I/O

I/O element name.

Current Value

If the device is connected to the Configurator, then all the current I/O values can be seen here.

Units

Units of measurement.

Priority

This field allows the enabling of the I/O elements and sets them a priority so they are added to the data packet, which is sent to the server. By default 7 I/O elements with Low priority are enabled: Ignition, Movement, GSM Signal, External Voltage, Battery Voltage, Battery Current, Total Odometer. All records made by FTX are regular, and regular packets are sent as low priority records.

Priority level (AVL packet priority) can be:

None Priority

The module doesn't make additional records.

Low Priority

The module makes an additional record with an indication that the event was caused by an I/O element change (depending on Operands configuration).

High Priority

The module makes an additional record with High priority flag and sends event packet immediately to the server using GPRS.

High and Low Level

These levels define I/O value range. If I/O value enters or exits this range, FTX generates an event.

Event Only

When this is selected, I/O element status value will be appended only to eventual records, otherwise I/O element status value will appear in each AVL record.

Operands

Defines when to generate event: On Exit, On Entrance, On Both, Monitoring, On Hysteresis, On Change or On Delta Change.

Operand On Exit

Record is generated when input value leaves a range between low and high level limits.

Operand On Entrance


Record is generated when input value enters a range between low and high level limits.

Operand On Both


Record is generated by both On Exit and On Entrance operands' logic at same time.

Operand Monitoring


No event at all. Values are recorded only when other triggers worked.

Operand On Hysteresis


Record is generated when input value crosses the high limit value from below the low limit value or vice versa.

Operand On Change


Record is generated when input value changes.

Operand On Delta Change


Record is generated when input value changes and the absolute change becomes equal to or higher than the limit value.

Manual CAN

Manual CAN functionality allows user to read data via CAN BUS without requiring additional CAN protocol development from the firmware side.

  • Priority – defines the priority of Manual CAN I/O: 0 – disabled, 1 – low, 2 – high.
  • CAN type - defines which CAN ID type will be received and requested (Standard - 11bit, Extended - 29bit).
  • CAN ID – depends on CAN Type parameter and defines which CAN ID will be received by device.
  • Data mask – defines which data bytes are sent to the server (sometimes not all data bytes are necessary). Up to 8 particular data bytes can be selected for each CAN ID.
  • Operand – defines when to generate event: On Exit, On Entrance, On Both, Monitoring, On Hysteresis, On Change or On Delta Change.


Manual CAN Commands