|
| 1 | +--- |
| 2 | +title: Usage |
| 3 | +--- |
| 4 | + |
| 5 | +# Automate |
| 6 | + |
| 7 | +The "Automate" feature can be used to **periodically request one or more PID**s. |
| 8 | + |
| 9 | +First of all **the `Protocol` in the `CAN` section on the "Settings" tab has to be set to `AutoPID`** |
| 10 | + |
| 11 | +Configuration of "Automate" itself is done on the "Automate" tab. |
| 12 | + |
| 13 | +Responses can be monitored: |
| 14 | +- by monitoring the MQTT subject configured if [MQTT is enabled](../MQTT.md) |
| 15 | +  |
| 16 | + |
| 17 | +- pointing the Web browser to `http://<WiCAN IP adress>/autopid_data` if [MQTT is NOT enabled](../MQTT.md) |
| 18 | +  |
| 19 | + |
| 20 | +## Vehicle Profiles |
| 21 | +Initially the download of **vehicle profiles** has to be triggered by pressing the sync button next to the `Vehicle Model` dropdown box. These vehicle profiles are car vendor and/or model specific and contain some popular PIDs (e.g. SoC, SoH). There is a growing [list of supported vehicles](2.Supported_Vehicles.md). |
| 22 | + |
| 23 | +If WiCAN cannot download vehicles profiles for any reason you man also [download in manually](https://github.com/meatpiHQ/wican-fw/blob/main/vehicle_profiles.json) and press the `Choose File` button to select the file downloaded. |
| 24 | + |
| 25 | +In order to use vehicle profiles `Vehicle Specific` has to be set to `Enable`. |
| 26 | + |
| 27 | +If vehicles profiles are available to WiCAN the appropriate `Vehicle Model` should be selected from the drop-down box. Use the reload button next to it to trigger the download of the most up-to-date vehicle profiles. |
| 28 | + |
| 29 | +In `Cycle Time(ms)` the interval is configured after which the PIDs, contained in the vehicle profile, are requested. |
| 30 | + |
| 31 | +The results are posted to the MQTT topic specified in `Destination Topic` if [MQTT is enabled](../MQTT.md). |
| 32 | + |
| 33 | + |
| 34 | + |
| 35 | + |
| 36 | +## Custom PIDs |
| 37 | + |
| 38 | +If there is no vehicle profile for your car, or it does not contain the PIDs you would like to use, the "Custom PIDs" feature should be used. Basically the same parameters as contained in the vehicle profiles can be entered: |
| 39 | + |
| 40 | +- **Custom Initialisation**: will be sent by WiCAN prior requesting particular PIDs |
| 41 | +- **Name**: the attribute name containing the result of the PID request |
| 42 | +- **Init**: will be sent by WiCAN prior requesting this particular PID |
| 43 | +- **Expression**: is used to calculate the attribute value from the bytes returned for this PID |
| 44 | +- **Period**: the interval after which this PID is requested again |
| 45 | +- **Type**: currently only `MQTT_Topic` can be selected |
| 46 | +- **Send_to**: the MQTT topic the result should be sent to |
| 47 | + |
| 48 | +In order to add more PIDs the `New` button can be used. |
| 49 | +The `Delete` button deletes the configuration of the corresponding PID |
| 50 | + |
| 51 | +In order to use Custom PIDs `Vehicle Specific` has to be set to `Disable`. |
| 52 | + |
| 53 | +**At the moment Custom PIDs are only supported over MQTT**. Therefore [MQTT has to be enabled](../MQTT.md). |
| 54 | + |
| 55 | + |
0 commit comments