SLC Gateway (Gen1)

review the following information for setting up and configuring the slc gateway (gen1) driver manufacturing connect edge compatible series compatibility parameter compatible items driver type ethernet validated devices/series slc 500 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 the device is configured for ethernet access, find its network parameters otherwise, use plc software on your computer to configure the device for ethernet access 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 allen bradley driver slc gateway (gen1) network address the device address you defined in step 1 port 44818 channel a/b node id 1 slot 1 slots <#> type input/output word <#> 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 device and tag metadata use case docid\ f b720nivllber44rfyhn tag formula variables docid\ pwd 7p kzjxkt pyawaow register table name value type address format min address max address description i bit ssoo 0 9977 input bit o bit ssoo 0 9977 output bit s int ddd 0 255 status bit b3 bit ddddd 0 25515 bit data file (b3) bfn bit fffddddd 0 25525515 t4 acc int ddd 0 255 timer accumulator (t4) t4 pre int ddd 0 255 timer preset (t4) tfn acc int fffddd 0 255255 tfn pre int fffddd 0 255255 c5 acc int ddd 0 255 counter accumulator (c5) c5 pre int ddd 0 255 counter preset (c5) cfn acc int fffddd 0 255255 cfn pre int fffddd 0 255255 r6 pos int ddd 0 255 control file pointer position (r6) r6 len int ddd 0 255 control file length (r6) rfn pos int fffddd 0 255255 rfn len int fffddd 0 255 n7 int ddd 0 255 integer data file (n7) nfn int fffddd 0 255999 f8 float ddd 0 255 floating point data file (f8) ffn float fffddd 0 255999 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 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)