SNMP Manager

review the following information for setting up and configuring the snmp manager driver litmus edge compatible series compatibility parameter compatible items driver type ethernet validated devices/series https //www belden com/products/greyhound1040 to set up and configure this device in litmus 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 litmus edge devicehub step 3 configure the list of registers step 1 set up and configure the device find your snmp agent's configuration and note down its settings step 2 set up the device in litmus edge devicehub upload required mib files see docid\ w5xyehtbykya x umzzqo to review the mib files which are already included in the driver enable the litmus edge ftp server and add a user see docid 8wxarubsl0wubj tsl3ha for more information create a folder in the devicehub/ folder and note down the name of the folder upload the required mib files to the folder you created add the device in devicehub configure the following parameters when you docid\ pal6abpzbrimdu9lvgj30 with this driver update default values to the specific setup of your device parameter value type network utility driver snmp manager transport udp network address enter the ip address of your snmp agent network port 161 snmp version select based on your snmp agent's setting enable tls select based on your snmp agent's setting enable trap listener select based on your snmp agent's setting mib folder path enter the name of the folder you created in the ftp server browse root 1 3 browse order alphabetical (by name) if you set snmp version to v1 or v2c , enter the value for the community string parameter based on your snmp agent's settings if you set the snmp version to v3 , all the parameters will have values selected based on your snmp agent's settings the following parameters will be available username context name authentication protocol authentication passphrase privacy protocol privacy passphrase if traps are enabled parameter value trap transport udp trap interface 0 0 0 0 traps port 162 advanced options parameter value request timeout 2000 rquest retries 3 max oid count 25 step 3 configure the list of registers when you docid\ tuy hh0gi8djvot70wroh to the connected device, see the following register table and tag parameters sections you can also docid 8oruw1cmtao49bwbbhwrn for the device see the following additional resources if necessary docid\ mu 6j6zhi0cvchdad0w8n docid\ io7xgyrdvv vmpnfxoaci register table name value types access type r integer32, counter32, gauge32, uinteger32, timeticks, counter64, opaque(float), opaque(double), opaque(count64), opaque(integer64), opaque(uinteger64), opaque, octetstring, octetstring(ascii), objectidentifier, ipaddress, bitstring r/w tag parameters name enter the case sensitive register name exactly as it is defined in the plc value type select a data type from the drop down list 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 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 only publish nats messages when the value parameter changes to a new value 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 metadata 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)