Template:FTX Input/Output (I/O): Difference between revisions
Irmantas.K (talk | contribs) No edit summary |
No edit summary |
||
| Line 79: | Line 79: | ||
==Manual CAN== | ==Manual CAN== | ||
Manual CAN | == Manual CAN == | ||
[[File:Manual CAN - menu.png|right|500px]] | |||
The user can configure 70 Manual CAN I/O element by setting Priority, CAN Type, CAN ID, Data Mask, Operand. Each CAN I/O has its own parameters and can be configured independentely. | |||
''' | When configuring CAN IO elements, each parameter (like priority, operand, CAN type, CAN ID, etc.) requires a unique '''configuration ID'''. These IDs follow specific formulas to ensure no overlap with other parameters in the system. This guide explains how to calculate them. | ||
==='''Formula:'''=== | |||
Parameter_ID = 1,000,000 + (AVL_ID * 100) + OPTION Parameter_ID = 1,000,000 + (AVL_ID * 100) + OPTION | |||
* 1,000,000: Base offset for CAN-related parameters. | |||
* AVL_ID: The CAN AVL IO element identifier (within certain allowed ranges). | |||
* OPTION: A small integer offset indicating which setting is being adjusted (e.g., priority or operand). | |||
'''Valid AVL Ranges ''' | |||
* [10216:10235] | |||
* | * [10298:10347] | ||
''' | |||
Example:''' If AVL_ID is 10216 and the OPTION for “priority” is 1, then | |||
Parameter ID=1,000,000+(10216×100)+1=1,000,000+1,021,600+1=2,021,601 | |||
=== '''MCAN IO Parameter Calculation''' === | |||
For MCAN IO elements (e.g., MCAN0, MCAN1, MCAN2…), each has three specific parameters: '''CAN Type, CAN ID,''' and '''Data Mask'''. The '''MCAN IO''' '''number''' is the index of the MCAN entry (starting at 0, 1, 2, etc.). | |||
'''''Formulas''''' | |||
1. '''CAN Type''' | |||
Parameter ID=17,000+(10×MCAN IO number) | |||
2. '''CAN ID''' | |||
Parameter ID=17,001+(10×MCAN IO number) | |||
3. '''Data Mask''' | |||
Parameter ID=17,002+(10×MCAN IO number) | |||
*'''Data | '''Examples''' | ||
* '''MCAN0''' (IO number = 0): | |||
** '''CAN Type:''' 17000 + (10 × 0) = 17000 | |||
** '''CAN ID:''' 17001 + (10 × 0) = 17001 | |||
** '''Data Mask:''' 17002 + (10 × 0) = 17002 | |||
* '''MCAN1''' (IO number = 1): | |||
** '''CAN Type:''' 17000 + (10 × 1) = 17010 | |||
** '''CAN ID:''' 17001 + (10 × 1) = 17011 | |||
** '''Data Mask:''' 17002 + (10 × 1) = 17012 | |||
* '''MCAN69''' (IO number = 69): | |||
** '''CAN Type:''' 17000 + (10 × 69) = 17690 | |||
** '''CAN ID:''' 17001 + (10 × 69) = 17691 | |||
** '''Data Mask:''' 17002 + (10 × 69) = 17692 | |||
*''' | '''Putting It All Together''' <br> | ||
* | 1. '''Check Your AVL ID Range''' <br> | ||
* If your CAN IO element has an AVL ID in [10216–10235] or [10298–10347], use the '''first formula''' for Parameter_ID = 1,000,000 + (AVL_ID * 100) + OPTION. <br> | |||
2. '''Identify Your MCAN IO Number''' <br> | |||
* If you have an MCAN entry (e.g., MCAN0, MCAN1), use the '''second set of formulas''' to find the corresponding '''CAN Type, CAN ID, and Data Mask''' parameter IDs. <br> | |||
3. '''Plug In the Numbers''' <br> | |||
* Calculate step by step, ensuring you add the correct base offsets and multipliers. <br> | |||
4. '''Configure Your Device''' <br> | |||
* Once you have the parameter IDs, set or modify them in your configuration tool to match the desired priority, operand, or other CAN-related settings.<br> | |||
}} | |||
==Manual CAN Commands== | ==Manual CAN Commands== | ||
Revision as of 08:14, 12 September 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.
Manual CAN Commands
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:
Configurable settings:
- Command type - defines which CAN ID type will be used to send commands:
- Standard (11-bit) - a maximum value of 7FF.
- Extended (29-bit) - a maximum value of 1FFFFFFF.
- CAN ID – defines command CAN ID.
- If Command type is Standard (11-bit) - a maximum value of 7FF.
- If Command type is Extended (29-bit) - a maximum value of 1FFFFFFF.
- Data - defines command data.
- Data length - defines command data length in bytes.
- Send type - selects command send type:
- Once - command will be sent one time after it is triggered.
- Periodic - command will be sent periodically after it is triggered.
- Response - command will be sent once as a response to received Manual CAN I/O.
- Run on startup - if enabled, command will be triggered automatically on device startup.
- Response - if Send type is Response, defines Manual CAN I/O which will trigger command.
- Send period - defines command send period (in miliseconds) if Periodic send type is selected:
- Minimal command period - 100 ms.
- Period must be configured with a step of 100 ms.
- Send count - defines command sending count if Periodic send type is selected.
- 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/GPRS Command List#CAN Commands|{{{model}}} SMS/GPRS Commands]].
}}
[[Category:{{{model}}} Configuration]]