Enron Modbus

notes this driver is available for manufacturing connect edge version 3 11 0 and later if multiple stations are connected to the rs 485 bus, then use the modbus ascii advanced docid\ m6jotcrga 7nvysszh9lr driver instead of this one review the following information for setting up and configuring the enron modbus driver manufacturing connect edge compatible series compatibility parameter compatible items driver type serial (rs 485) or ethernet when to use serial connection or tcp connection to a modbus device 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 if you are setting up an ethernet connection, find the device's network parameters if you are setting up a serial connection, record the serial communication parameters for the device 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 setup of your device parameter value type modbus driver enron modbus override station id override registers' station id setting false true override bw order override registers' "bytes and words order" setting false true protocol mode rtu ascii request timeout (ms) 2000 transport type serial tcp/ip network address if tcp/ip selected the device address you recorded in step 1 network port if tcp/ip selected 502 device file if serial selected the file of the serial port you are using baud rate if serial selected 1200 2400 4800 9600 19200 38400 57600 115200 230400 460800 921600 data bits if serial selected 5 6 7 8 stop bits if serial selected 1 1 5 2 parity if serial selected even mark none odd space 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 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 name value types address format min address max address description 1x bool 1ddd 100 1999 boolean registers 3x int16 3ddd 3001 1999 short 16 bit integer registers 5x int32 5ddd 5001 1999 long 32 bit integer registers 7x float32 7ddd 7001 65535 floating point registers eventalarm json event/alarm register acknowledgment bool event/alarm acknowledgment (write only) archive json 7dd 701 799 hourly and daily archive 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 record number (not available for all names) enter the record number 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 station id enter the value that indicates the position of the tag bytes and words order (not available for all names) this option configures how the tag data will be formatted and whether bytes and/or words will be counted from the start (big endian style) or end (little endian style) of strings of data select one of the following options bytes bigendian only bytes will be formatted in big endian style (counted from the start) bytes littleendian only bytes will be formatted in little endian style (counted from the end) bytes bigendian, words bigendian both bytes and words will be formatted in big endian style (bytes and words counted from the start) for example ab cd bytes bigendian, words littleendian bytes will be formatted in big endian style and words will be formatted in little endian style for example cd ab bytes littleendian, words bigendian bytes will be formatted in little endian style and words will be formatted in big endian style for example ba dc bytes littleendian, words littleendian both words and bytes will be formatted in little endian style (counted from the end) for example dc ba 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)