Difference between revisions of "Mappings"
Alkitjohan (talk | contribs) |
Alkitjohan (talk | contribs) |
||
| Line 3: | Line 3: | ||
[[File:Mappings1.png|thumb|frame|Mappings 1: The manual mapping checkbox]] | [[File:Mappings1.png|thumb|frame|Mappings 1: The manual mapping checkbox]] | ||
When creating a SignalReader task (New Task and then selecting the "SignalReader" tab) there is a new checkbox "Manual mapping" as illustrated in illustration "Mappings 1". | When creating a SignalReader task (New Task and then selecting the "SignalReader" tab) there is a new checkbox, "Manual mapping", as illustrated in illustration "Mappings 1". | ||
If you tick this box, the upload of the SignalReader haf-file will work as in previous versions of the portal. If you do not tick this box, then, when a .haf-file is uploaded, the portal will start a process called auto mapping. | |||
==Auto mapping== | |||
[[File:Mappings1.png|thumb|frame|Mappings 2: Auto mapping performed]] | |||
When a .haf file for a SignalReader assignment is uploaded, the portal will start to parse the file and search for references to CAN buses and try to look up the name of the CAN bus. The name of the CAN bus is found in a section named GLOBAL_CAN_API_MODULE_X, as the example below shows. If no such section exists in the .haf file, the parser is unable to look the name of the CAN bus. | |||
<code> | |||
[GLOBAL_CAN_API_MODULE_0]<br> | |||
default_period=10<br> | |||
description_date_time=<br> | |||
description_file=<br> | |||
direction=IN<br> | |||
io=CAN1<br> | |||
name=CAN_HS<br> | |||
</code> | |||
When the .haf file is parsed, the portal will try to match the extracted CAN bus references and its names with the enabled CAN buses and their names (See [[I/O_configurations]] for each selected WCU. If the names for each referenced CAN bus matches the name in the WCU configuration the dialog shown in illustration "Mappings 2" will pop up. This dialog says that auto mapping is performed and that the mappings | |||
Revision as of 10:18, 6 April 2016
The following applies to version >= 2.41 of the portal:
When creating a SignalReader task (New Task and then selecting the "SignalReader" tab) there is a new checkbox, "Manual mapping", as illustrated in illustration "Mappings 1". If you tick this box, the upload of the SignalReader haf-file will work as in previous versions of the portal. If you do not tick this box, then, when a .haf-file is uploaded, the portal will start a process called auto mapping.
Auto mapping
When a .haf file for a SignalReader assignment is uploaded, the portal will start to parse the file and search for references to CAN buses and try to look up the name of the CAN bus. The name of the CAN bus is found in a section named GLOBAL_CAN_API_MODULE_X, as the example below shows. If no such section exists in the .haf file, the parser is unable to look the name of the CAN bus.
[GLOBAL_CAN_API_MODULE_0]
default_period=10
description_date_time=
description_file=
direction=IN
io=CAN1
name=CAN_HS
When the .haf file is parsed, the portal will try to match the extracted CAN bus references and its names with the enabled CAN buses and their names (See I/O_configurations for each selected WCU. If the names for each referenced CAN bus matches the name in the WCU configuration the dialog shown in illustration "Mappings 2" will pop up. This dialog says that auto mapping is performed and that the mappings