View source for How to configure Manual CAN I/O parameters

==Manual CAN I/O parameter configuration example==
<br>
{| 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;" |Manual CAN can be tested on FW 55.00.09.rev.04 or newer
|}

{| style="width: 100%"
|[[Image: Manual CAN Baudrate.png|right]]

#In the Manual CAN Settings section the user has to select suitable <b>baudrate</b>. Manual CAN baudrate should be visible in the CAN protocol. If it is not known, the user can try to choose different baudrates to indicate which one works. [[Image: Manual CAN IO Settings.png|center]]
#Select <b>CAN Type</b>. Normally every CAN protocol documentation should mentioned which CAN type to use. If not, select standard.
#Fill in the correct <b>Data mask</b>. This field determines which IO elements of the frame the user will receive. <br>As an example, the part of the CAN protocol was taken. First, the user has to locate the data frame, he/she wants to read, for this situation, data frame „Battery status“ was taken into account. It holds five I/O parameters of the battery. If we would like to receive all the data of the frame, in the configurator the user has to leave the default value in the Data mask field (FFFFFFFFFFFFFFFF) - which will be used in this example.[[Image:Can protocol example.png|center]] <br> If the user would like to get '''everything''' '''except''', for example, the ''Battery temperature'' value, some modifications have to be made on the <b>Data mask</b> field. In this case, if the user does not want to get the <i>Battery Temperature</i> value, he/she should find where this information stands in the data frame (byte orientation). For this example, ''Battery temperature'' parameter can be found between 4th and 5th byte of the frame. In the picture below, it is explained, how the 8 byte CAN frame breaks down and which part of the frame has to be changed according to this example.[[Image: Can frame example.png|center]][[Image: 8 bytes data mask explained.png|600px|center]]
#Write correct <b>CAN ID</b>. In this case the Frame ID in needed to be written. Here the CAN ID is 0x300. So in the configurator the user needs to write 300 instead of last three F values (FFFFF300), and every other F in the field has to be replaced with 0 (00000300). This means that it will take the data only from the ID 300 and nowhere else.
#Other fields of the MANUAL CAN0 are not configured as the data is not requested and is only being read.
#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: Manual CAN data example.png|center]]<br>
[[Image: Can frame data Busmaster.png|center]]
<br>
{| 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;" |Manual CAN protocol should be selected in the CAN I/O section.
|}
|}


[[Category: TFT100 FAQ]]