Template:FTX Input/Output (I/O): Difference between revisions
Irmantas.K (talk | contribs) No edit summary |
Irmantas.K (talk | contribs) No edit summary |
||
| (5 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
==Input / output (I/O)== | ==Input / output (I/O)== | ||
===Search=== | ===Search=== | ||
Enter the keyword to search for the desired permanent I/O. | Enter the keyword to search for the desired permanent I/O. | ||
| Line 14: | Line 8: | ||
===View Columns=== | ===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. | 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. | ||
===Current Value=== | ===Current Value=== | ||
| Line 41: | Line 32: | ||
===High and Low Level=== | ===High and Low Level=== | ||
These levels define I/O value range. If I/O value '''enters or exits''' this range, {{{model | These levels define I/O value range. If I/O value '''enters or exits''' this range, {{{model}}} '''generates an event'''. | ||
===Event Only=== | ===Event Only=== | ||
| Line 76: | Line 67: | ||
Record is generated when input value changes and the absolute change becomes equal to or higher than the limit value. | Record is generated when input value changes and the absolute change becomes equal to or higher than the limit value. | ||
[[Image:Fmb120_on_delta_change.png|x150px|none]] | [[Image:Fmb120_on_delta_change.png|x150px|none]] | ||
==Permanent I/O== | |||
When no permanent I/O elements are enabled, AVL packet comes with GNSS information only. | |||
[[File:FTX permanent io.png|center|thumb|1100x1100px]] | |||
After enabling I/O element(s) AVL packet contains current value(s) of enabled I/O element(s) along with GNSS information. | |||
<!-- If model supports Manual CAN, then show --> | <!-- If model supports Manual CAN, then show --> | ||
{{# | {{#if: {{FTX Pin Support List|model={{{model}}}|pin=Manual CAN}} | | ||
| | |||
| | |||
==Manual CAN== | ==Manual CAN== | ||
Manual CAN functionality allows user to read data from CAN BUS without requiring an additional CAN protocol development from the firmware side. | Manual CAN functionality allows user to read data from CAN BUS without requiring an additional CAN protocol development from the firmware side. | ||
'''Note:''' Before using Manual CAN, make sure to select the correct CAN settings: [[{{{model}}} Accessories#CAN|{{{model}}} CAN settings]]. | |||
Up to '''70''' Manual CAN I/Os can be configured: | Up to '''70''' Manual CAN I/Os can be configured: | ||
| Line 102: | Line 100: | ||
**For '''SAE J1939''', the first and last bytes can vary depending on the vehicle make or model, while the bytes in between remain the same for all vehicles. Although the first and last bytes may hold any value, it is recommended to use FF for both. | **For '''SAE J1939''', the first and last bytes can vary depending on the vehicle make or model, while the bytes in between remain the same for all vehicles. Although the first and last bytes may hold any value, it is recommended to use FF for both. | ||
*'''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 | *'''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: | *'''Operand''' – defines when to generate event: | ||
**'''Monitoring''' - continuously monitors the current I/O element value in with every periodical record. No eventual records are created when using the "Monitoring" operand. | **'''Monitoring''' - continuously monitors the current I/O element value in with every periodical record. No eventual records are created when using the "Monitoring" operand. | ||
**'''On Change''' - generates an eventual record whenever the input value changes. | **'''On Change''' - generates an eventual record whenever the input value changes. | ||
==Manual CAN Commands== | ==Manual CAN Commands== | ||
Manual CAN Commands functionality allows user to send configurable commands to CAN BUS. | Manual CAN Commands functionality allows user to send configurable commands to CAN BUS. | ||
'''Note:''' Before using Manual CAN, make sure to select the correct CAN settings: [[{{{model}}} Accessories#CAN|{{{model}}} CAN settings]]. | |||
Up to '''10''' Manual CAN Command I/Os can be configured: | Up to '''10''' Manual CAN Command I/Os can be configured: | ||
| Line 147: | Line 144: | ||
**If set to '''0''' - command will be sent '''infinitely''' until it is turned off by the user. | **If set to '''0''' - command will be sent '''infinitely''' until it is turned off by the user. | ||
After configuring, Manual CAN commands can be triggered with SMS/GPRS commands: [[{{{model}}} SMS/ | After configuring, Manual CAN commands can be triggered with SMS/GPRS commands: [[{{{model}}} SMS/GPRS Command List#CAN Commands|{{{model}}} SMS/GPRS Commands]]. | ||
}} | }} | ||
[[Category:{{{model}}} Configuration]] | [[Category:{{{model}}} Configuration]] | ||
Revision as of 20:10, 27 March 2025
Input / output (I/O)
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.
Current Value
If the device is connected to the Telematics Configuration Tool, 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 I/O elements with Low priority are enabled: Total odometer GSM Signal, Battery Voltage, Battery Current, PCB temperature, GNSS PDOP, GNSS HDOP, Ignition, Movement, External voltage.
These records made by {{{model}}} device 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, {{{model}}} 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 Monitoring
No event at all. Values are recorded only when other triggers worked.
Operand On Change
Record is generated when input value changes.
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 On Hysteresis
Record is generated when input value crosses the high limit value from below the low limit value or vice versa.
Operand On Delta Change
Record is generated when input value changes and the absolute change becomes equal to or higher than the limit value.
Permanent I/O
When no permanent I/O elements are 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.
[[Category:{{{model}}} Configuration]]