Manual CAN Requests: Difference between revisions
No edit summary |
|||
| (15 intermediate revisions by the same user not shown) | |||
| Line 27: | Line 27: | ||
* '''Request Data Length''' - defines data length of requested ID. | * '''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)'''. | * '''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)'''. | ||
If the data must be requested to receive CAN information from a heavy duty vehicle - '''RTR must be enabled'''. If data can be received without requesting it from a heavy duty vehicle - '''RTR can be disabled'''. | |||
[[Image:CAN1_bus_settings.png|right]] | [[Image:CAN1_bus_settings.png|right]] | ||
| Line 103: | Line 105: | ||
| | | | ||
|- | |- | ||
| 0x452 | | '''**0x452''' | ||
| Battery Fast charging mode switch status | | Battery Fast charging mode switch status | ||
| | | | ||
| Line 113: | Line 115: | ||
| 3 | | 3 | ||
|- | |- | ||
| rowspan="2" | 0x453 | | rowspan="2" | '''*0x453''' | ||
| rowspan="2" | Battery Fast charging mode switch | | rowspan="2" | Battery Fast charging mode switch | ||
| rowspan="2" | | | rowspan="2" | | ||
| Line 126: | Line 128: | ||
|} | |} | ||
'''**''' - ''CAN ID to send CAN COMMAND'' <br /> | |||
'''*''' - ''CAN ID to receive value in Manual CAN of CAN COMMAND'' <br /> | |||
1. Enter correct '''CAN ID''' in ''Manual CAN tab''. In this case, the '''Frame ID''' in needed to be entered. Here, CAN ID is 0x300, so in the configurator the user will need to enter 300 instead of last three F values ''(FF0300FF)''. This means that it will take the data '''only''' from the '''ID 300'''. | 1. Enter correct '''CAN ID''' in ''Manual CAN tab''. In this case, the '''Frame ID''' in needed to be entered. Here, CAN ID is 0x300, so in the configurator the user will need to enter 300 instead of last three F values ''(FF0300FF)''. This means that it will take the data '''only''' from the '''ID 300'''. | ||
| Line 136: | Line 140: | ||
5. Received I/O values are RAW and the user has to decode it. The image below is an example of how it can be decoded using additional software (we have used '''''Busmaster''''' for this): | 5. Received I/O values are RAW and the user has to decode it. The image below is an example of how it can be decoded using additional software (we have used '''''Busmaster''''' for this): | ||
[[Image:CAN_IO_1.png|center]]<br /> | |||
[[Image:BatteryStatusFrameID.png|center|]]<br /> | |||
==Important note== | |||
Enabling all commands could drastically '''increase''' delay - sending could take up to '''1.5 s''' (all commands configured with 100 ms period). | |||
We strongly advise: | |||
# If all commands are necessary with certain period - keep all commands with same sending period. | |||
# Do not leave any enabled CAN reading parameters if CAN reading is not used. | |||
# Keep Data Acquisition settings with higher than 15 seconds. | |||
{| class="wikitable" style="border-style: solid; border-width: 0px;" | |||
| style="width: auto; text-align: left; background: #F6F6FB;" |'''NOTE!''' | |||
| style="width: auto; text-align: left; background: #F6F6FB;" |'''Send Period details''' <br />Records could drastically '''increase''' CAN command sending period as records could be generated every second by configured Features records, '''Data Acquisition settings''' or '''IO element operands'''. Each particular case has different affect for CAN Command delay, that depends on configuration and in case of issue should be investigated individually. | |||
|} | |||