Line 1: |
Line 1: |
− | AutoCAN function allows user to automatically scan for available messages on CAN bus and configure CAN data sending to server. In order to configure AutoCAN connect {{model=FMB630}} to computer with Port ½ cable. Launch FMB630 configurator version 1.1.1.7 or higher. Push “Connect“ button, then „CAN“ button. CAN configuration menu will be opened. | + | AutoCAN function allows user to automatically scan for available messages on CAN bus and configure CAN data sending to server. In order to configure AutoCAN connect {{{model|FMB630}}} to computer with Port ½ cable. Launch {{{model|FMB630}}} configurator version 1.1.1.7 or higher. Push “Connect“ button, then „CAN“ button. CAN configuration menu will be opened. |
| | | |
| {{{image1|[[Image:FMB630_autoCAN1.png|center|200px]]}}} | | {{{image1|[[Image:FMB630_autoCAN1.png|center|200px]]}}} |
| | | |
− | * SCAN scans once for available messages on CAN bus; | + | * SCAN - scans once for available messages on CAN bus; |
| * Monitoring – toggles scanning of messages on CAN bus every 3 seconds; | | * Monitoring – toggles scanning of messages on CAN bus every 3 seconds; |
− | * Offline Configuration – enables CAN configuration when {{model=FMB630}} is not connected to CAN bus; | + | * Offline Configuration – enables CAN configuration when {{{model|FMB630}}} is not connected to CAN bus; |
| * Auto CAN tab – configure CAN by selecting available messages from CAN bus; | | * Auto CAN tab – configure CAN by selecting available messages from CAN bus; |
| * Manual CAN tab – Configure CAN by manually entering CAN message ID and data mask; | | * Manual CAN tab – Configure CAN by manually entering CAN message ID and data mask; |
Line 11: |
Line 11: |
| {{{image2|[[Image:FMB630_autoCAN2.png|center|250px]]}}} | | {{{image2|[[Image:FMB630_autoCAN2.png|center|250px]]}}} |
| | | |
− | To start CAN configuration push “SCAN“ button. A table of all available CAN messages will appear (Figure 100). Description of columns: | + | To start CAN configuration push “SCAN“ button. A table of all available CAN messages will appear. Description of columns: |
| * Category – shows CAN message; | | * Category – shows CAN message; |
| * Parameter – shows configurable parameter name; | | * Parameter – shows configurable parameter name; |
| * Value – shows scanned value of parameter; | | * Value – shows scanned value of parameter; |
| * Send data to server – allows to choose the type of data when it‘s generated: | | * Send data to server – allows to choose the type of data when it‘s generated: |
− | o Disabled – Data will not be collected
| + | ○ Disabled – Data will not be collected;<br> |
− | o On low priority – records will be generated as low priority events;
| + | ○ On low priority – records will be generated as low priority events; <br> |
− | o On high priority – records will be generated as high priority events and immediately sent to server via GPRS (if GPRS is available);
| + | ○ On high priority – records will be generated as high priority events and immediately sent to server via GPRS (if GPRS is available);<br> |
− | o On panic - records will be generated as panic priority events and immediately sent to server via GPRS, if GPRS is not available records will be sent via SMS messages;
| + | ○ On panic - records will be generated as panic priority events and immediately sent to server via GPRS, if GPRS is not available records will be sent via SMS messages;<br> |
| * Data acquisition type – allows to choose when records are generated: | | * Data acquisition type – allows to choose when records are generated: |
− | oMonitoring – monitors data;
| + | ○ Monitoring – monitors data;<br> |
− | oOn change – record is generated when parameter value is changed;
| + | ○ On change – record is generated when parameter value is changed;<br> |
− | oHysteresis – record is generated when increasing parameter value becomes higher than High value, and decreasing becomes less than Low value
| + | ○ Hysteresis – record is generated when increasing parameter value becomes higher than High value, and decreasing becomes less than Low value;<br> |
− | oEvent on exit – record is generated when parameter value becomes higher than High value or lower than Low value;
| + | ○ Event on exit – record is generated when parameter value becomes higher than High value or lower than Low value;<br> |
− | oEvent on entrance – record is generated when parameter value becomes between High and Low values;
| + | ○ Event on entrance – record is generated when parameter value becomes between High and Low values;<br> |
− | oEvent on both – record is generated when parameter value crosses High or Low values;
| + | ○ Event on both – record is generated when parameter value crosses High or Low values;<br> |
| * Low – allows to choose low value for Data acquisition; | | * Low – allows to choose low value for Data acquisition; |
| * High – allows to choose High level for Data acquisition; | | * High – allows to choose High level for Data acquisition; |
Line 40: |
Line 40: |
| Monitoring filters menu allows choosing which data will be shown in configuration menu. To enable/disable particular data monitoring use checkbox next to data name. To enable all data monitoring click Select all, to disable all data monitoring click Select none. | | Monitoring filters menu allows choosing which data will be shown in configuration menu. To enable/disable particular data monitoring use checkbox next to data name. To enable all data monitoring click Select all, to disable all data monitoring click Select none. |
| | | |
− | Note: CAN monitoring is {{model=FMB630}} configurator function; it does not enable data sending to server. In order to configure data sending to server refer to Configuration section. | + | Note: CAN monitoring is {{{model|FMB630}}} configurator function; it does not enable data sending to server. In order to configure data sending to server refer to Configuration section. |