315
edits
Changes
→Protocol example
==Manual CAN requests I/O settings==
==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)
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 choose 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'''.
{| class="wikitable" style="border-style: solid; border-width: 0px;"
{| class="wikitable" style="border-style: solid; border-width: 0px;"
| 10 - Charge disable
| 10 - Charge disable
|}
|}
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'''.
2. For ''Manual CAN Requests tab'' configuration. In '''Manual CAN0 Request''' will be configured Battery Status message request by the provided documentation. For proper configuration by the protocol, '''Request ID''' should be entered with '''Source addresses''', '''Frame ID''' and '''Priority''' – 18030102, and the payload ''0000000000000002'' to receive all needed information.
3. Additionally there could be configured request period. As example to receive data each 10 seconds In request period will be written 10
# Request data length configured as 8 bytes
# 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):
