BacnetIP

note this driver is available for manufacturing connect edge version 3 3 1 and later review the following information for setting up and configuring the bacnetip device manufacturing connect edge compatible series compatibility parameter compatible items driver type ethernet validated devices/series bacnet/ip devices to set up and configure this device in manufacturing connect edge, you will need to do the following step 1 set up and configure the plc device step 2 set up the plc device in manufacturing connect edge devicehub step 3 configure the list of registers step 1 set up and configure the plc device important when setting up the plc device, the bacnet driver and your manufacturing connect edge instance must be on the same subnet if they aren't on the same subnet, the bacnet driver won't be able to connect to manufacturing connect edge to find the network parameters of the driver, you have the option of using the device discovery tool docid\ l7q e vvwsb9vujzlhhnh otherwise, set up the device for ethernet access and collect the network parameters to use the device discovery tool navigate to devicehub > devices click add new device click the device type drop down list and select bacnet click the driver name drop down list, and select bacnetip click device discovery the device discovery dialog box appears in the network address field, open the drop down list and select the appropriate ethernet port the available options are based on the interfaces configured in manufacturing connect edge to review interfaces, navigate to system > network > interfaces in the retry count field, review the default value (5) and update it if needed this configures the number of times manufacturing connect edge will attempt to discover devices in the timeout field, review the default value (2) and update it if needed click start discovery when the search is complete, available devices will be listed with the following parameters device id ip address port click the appropriate device, and then click update form with discovery results the connect device dialog box appears with network address , network port , and target device id pre filled based on the discovery results move onto step 2 and continue configuring the device with the remaining parameters step 2 set up the plc device in manufacturing connect edge devicehub configure the following parameters when you connect a device docid\ rfvijdxz7dbad8mwbisma with this driver update default values to the specific set up of your device parameter value type bacnet driver bacnetip network address the device address you defined in step 1 port 47808 target device id the object id of the device instance device id if the default value of 0 is configured, then a random instance id will be generated this id must be unique step 3 configure the list of registers when you add tags docid\ ioanzd2awqnkuppgee3eh to the connected device, refer to the following register table and tag parameters you can also search for pre defined device tags docid\ mocoh 5sebdz22wwbjsuf for this device refer to the following additional resources organize device and tag data by using metadata docid\ f b720nivllber44rfyhn tag formula variables docid\ pwd 7p kzjxkt pyawaow register table note when browsing for tags, only tags with the property of present value will be identified name value types address format min address max address description ai float32 0 2147483647 analog input ao float32 0 2147483647 analog output av float32 0 2147483647 analog value bi uint32, bool 0 2147483647 binary input bo uint32, bool 0 2147483647 binary output bv uint32, bool 0 2147483647 binary value msi int32 0 2147483647 multi state input mso int32 0 2147483647 multi state output msv int32 0 2147483647 multi state value sch float32 0 2147483647 schedule lfsp uint32 0 2147483647 life safety point loctl float32 0 2147483647 local control octstr octet string 0 2147483647 octet string pint uint32 0 2147483647 positive integer chv string 0 2147483647 object character string value f octet string 0 2147483647 file object proprietary bool, int32, uint32, float32, float64, string, octet string 0 2147483647 proprietary tag parameters name select a register name from the drop down list the available options depend on the names in the register table value type select a data type from the drop down list the available options depend on the register name selected polling interval enter a value in seconds this determines how often the tag should poll the register for data tag name enter a name for the tag description (optional) enter a description for the tag address enter a tag address the value must in the decimal format, within the allowed min/max range omit the leading zeros the device might use the decimal (d), hexadecimal (h), or octal (o) address format see the register table at the bottom of the dialog box for bit tags, append the bit address without the bit separator the lowercase letters in the address format indicate how many digits you should enter in the bit address count enter the number of register values to read a count higher than 1 will generate an array of values from the address value configured and respective subsequent address values tag formula enter a formula for the tag to process the generated data two variables are permitted value (current tag value) and timestamp (current tag unix time in milliseconds) the following math functions are available sin cos sqrt tan power power( x ) performs the operation 10^x log log( x ) is the natural logarithm (the logarithm is in base e ) exp exp( x ) performs the operation e^x only publish on change of value select the checkbox to customize nats messages to be published only when the value parameter changes from a previous value to a new one change of value only applies to boolean, numeric (such as int or float), and simple string data types it does not apply to complex types, such as json or array poll once topics will not be affected by change of value settings these topics will still only see a single message meta data metadata summarizes basic information about data this feature allows you to define key value pair data for the device output payload later on it can then be used to find, use, and reuse particular instances of data note if you use special characters in meta data key names, the special characters are replaced with underscore characters in the payload this can cause two key names to be combined into one for example, configuring the key names a b and a&\&b will cause only one key name to be created (a b)