FB107 Ethernet

review the following information for setting up and configuring the fb107 ethernet driver manufacturing connect edge compatible series 215,272 false true unhandled content type false unhandled content type unhandled content type false unhandled content type unhandled content type false unhandled content type 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 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 setup of your device 193,370 false true unhandled content type false unhandled content type unhandled content type false unhandled content type unhandled content type false unhandled content type unhandled content type false unhandled content type unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type unhandled content type false unhandled content type unhandled content type false unhandled content type unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type 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 device and tag metadata use case docid\ f b720nivllber44rfyhn tag formula variables docid\ pwd 7p kzjxkt pyawaow register table 100,304,137,100,101 false true unhandled content type unhandled content type unhandled content type unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type 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 opcode select the opcode to use 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) supported opcodes 0 obtain a general update of the current state for the physical input/output (i/o) points and the standard application oriented points 6 system configuration 7 read real time clock 8 set real time clock 17 set an operator identification code for the communications port through which communications are occurring 103 determine the current version of firmware residing in the roc, as well as other device specific information 120 send current pointers for the alarm and event logs 121 request alarm data from the alarm log in the roc 122 request up to 10 events from the event log in the roc 123 read user template data up to seven template parameters may be requested 126 request the roc unit’s minute data for a specified history point 130 request a specified number of hourly or daily data values for a specified history point 167 request single point parameters 180 request parameters 181 write parameters supported point types 0 5 8 12 17 19 23 25 28 43 48 55 80 86 88 89 93 94 98 117 118 120 121 122