2eaaff4ebe
* add ads hub and switch * add ads binary sensor * add ADS sensor * fix version numbers * separate configuration tag * remove device notification config * fix configuration schema. * replace tabs with spaces * add type key-value-pairs
1.6 KiB
| layout | title | description | date | sidebar | comments | sharing | footer | logo | ha_category | ha_release | ha_iot_class |
|---|---|---|---|---|---|---|---|---|---|---|---|
| page | ADS | Connect Home Assistant to TwinCAT devices via the ADS interface | 2017-12-05 12:00 | true | false | true | true | home-assistant.png | Hub | 0.60 | Local Push |
The ADS (automation device specification) describes a device-independent and fieldbus-independent interface for communication between Beckhoff® automation devices running TwinCAT® and other devices implementing this interface.
Configuration parameters:
{% configuration %} device: required: true description: The AMS NetId that identifies the device type: string port: required: true description: The port that runs the AMS server on the device, typically this would be 801 or 851 type: integer ip_address: required: false description: The IP-Address of the ADS device, if not set the first 4 bytes of the device id will be used type: string {% endconfiguration %}
# Example configuration.yaml entry
ads:
device: '127.0.0.1.1.1'
port: 48898
Service
The ADS component will register the service write_by_name allowing you to
write a value to a variable on your ADS device.
{
"adsvar": ".myvariable",
"adstype": "int",
"value": 123
}
Service parameters:
- adsvar: name of the variable on the ADS device. To access global variables
on TwinCAT2 use a prepending dot
.myvariable, for TwinCAT3 useGBL.myvariable - adstype: specify the type of the variable. Use one of the following:
int,byte,uint,bool - value: the value that will be written in the variable