322
edits
Changes
→Configuration of Manual CAN commands
1. Select CAN Type. Normally every CAN protocol documentation should mentioned which CAN type to use. If not, select '''Extended'''.
2. Fill in the correct Data mask in Manual CAN command 0 setting. This field determines which IO elements of the frame the user will send via CAN line. As an example, the part of the CAN protocol was taken. First, the user has to locate the data frame he wants to send, for this situation, data frame „Battery fast charge enable/disable “ was taken into account. It holds two states - '''enable''' or '''disable'''. If we would like to send data of frame, in the configurator the user has to configure '''0000000000000000 – to disable''' or '''0000000000000001 - to enable'''.
3. For Manual CAN command 0 settings '''CAN ID''' it must be written with sources addresses '''Frame ID''' and priority – '''19045303.'''
5. Send type Once
4. Request '''data length''' configured as '''8''' bytes.
5. Send type '''Once.'''
[[Image:Manual_can_commands_1.png|left]]
[[Image:Manual_can_commands_1.png|left]]
6. To receive data if the command were permitted correctly in Manual CAN0 we will configure CAN Type Extended.
6. To receive data if the command were permitted correctly in Manual CAN0 we will configure CAN Type Extended.
7. Data mask will have from LSB side selected first two bytes
7. Data mask will have selected first two bytes '''(right to left)''' from LSB side.
8. CAN ID will be FF0452FF as we are only interested to receive information about the command status execution.
8. '''CAN ID''' will be '''FF0452FF''' as we are only interested to receive information about the command status execution.
{| style="width: 100%"
{| style="width: 100%"
[[Image:Manual_can_IO_1.png|left]]
[[Image:Manual_can_IO_1.png|left]]
|}
|}
