Difference between revisions of "Manual CAN Requests"
m |
|||
| Line 6: | Line 6: | ||
* '''FMC650/FMM650/FMB641''' device | * '''FMC650/FMM650/FMB641''' device | ||
| − | |||
* '''03.01.00.Rev.00''' or newer firmware (for '''FMB641/FMC650/FMM650''') | * '''03.01.00.Rev.00''' or newer firmware (for '''FMB641/FMC650/FMM650''') | ||
* Transport or equipment with CAN interface which works via ''J1939 protocol'' | * Transport or equipment with CAN interface which works via ''J1939 protocol'' | ||
| Line 21: | Line 20: | ||
Baudrates are configurable in ''CAN \ Tachograph'' tab settings for connected CAN line which could be CAN1 or CAN2. | Baudrates are configurable in ''CAN \ Tachograph'' tab settings for connected CAN line which could be CAN1 or CAN2. | ||
| − | For Manual CAN request functionality CAN is selected in Manual CAN IO tab | + | For '''Manual CAN request''' functionality, CAN is selected in ''Manual CAN IO tab''. In ''Manual CAN IO,'' the input which should receive value must be '''enabled'''. |
| + | |||
| + | * '''Request ID/PGN''' - depends on CAN Type parameter and defines which CAN ID will be requested by device. | ||
| + | * '''Payload''' - defines data bytes, which are send if '''RTR''' (Remote Transmission Request) is disabled. | ||
| + | * '''Request Period''' - defines how often the request will be send. If 0 is selected - ID will not be requested. | ||
| + | * '''Request Data Length''' - defines data length of requested ID. | ||
| + | * '''RTR -''' Remote Transmission Request, is the choice if data frame needs to be send '''(if disabled)''' and if data frame needs to be requested '''(if enabled)'''. | ||
Revision as of 13:28, 31 August 2023
To use Manual CAN request functionality user should select Manual CAN Requests tab in configurator. Afterwards, user will be able to configure CAN parameters in Manual CAN Request settings tab.
Manual CAN Requests
The main benefit of using Manual CAN requests functionality is that the user is able to read data via CAN BUS without requiring additional CAN protocol development from the device's firmware side, if parameters needed to be requested more frequently or vice versa. To read data with this functionality, the user must have:
- FMC650/FMM650/FMB641 device
- 03.01.00.Rev.00 or newer firmware (for FMB641/FMC650/FMM650)
- Transport or equipment with CAN interface which works via J1939 protocol
- Transport or equipment CAN communication protocol (with information about frames, parameters, ID‘s, Baudrate)
Manual CAN requests I/O settings
User can configure up to 70 Manual CAN Request elements by setting CAN ID/Request ID, Request Period, Request Data Length, RTR parameters. Additionally, in Manual CAN I/O tab, user needs to select by configured Manual Request input name – CAN type, Data mask Data Source, CAN ID Each CAN I/O has its own parameters and can be configured independently. Configured CAN request will be shown by Manual CAN IO AVL ID. (CHECK THIS FOR GRAMMAR)
| (!) Functionality will work only when Ignition is ON |
Baudrates are configurable in CAN \ Tachograph tab settings for connected CAN line which could be CAN1 or CAN2.
For Manual CAN request functionality, CAN is selected in Manual CAN IO tab. In Manual CAN IO, the input which should receive value must be enabled.
- Request ID/PGN - depends on CAN Type parameter and defines which CAN ID will be requested by device.
- Payload - defines data bytes, which are send if RTR (Remote Transmission Request) is disabled.
- Request Period - defines how often the request will be send. If 0 is selected - ID will not be requested.
- Request Data Length - defines data length of requested ID.
- RTR - Remote Transmission Request, is the choice if data frame needs to be send (if disabled) and if data frame needs to be requested (if enabled).
