GE Fanuc 90-30 Ethernet (Gen1)

review the following information for setting up and configuring the ge fanuc 90 30 ethernet (gen1) driver litmus edge compatible series compatibility parameter compatible items driver type ethernet validated devices/series ge fanuc series 90 30 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 plc device if the device is configured for ethernet access, find its network parameters otherwise, use otherwise, use plc software on your computer to configure the device for ethernet access refer to the following device details device ge fanuc 90 30 ic693cpu363 device type (driver) ge 90 30 series (ethernet) i/f ethernet step 2 set up the plc device in litmus edge devicehub configure the following parameters when you connect a device docid 3eyafppweuvmblcey17sq with this driver update default values to the specific setup of your device parameter value type ge fanuc driver ge fanuc 90 30 ethernet (gen1) network address the device address you defined in step 1 port 18245 step 3 configure the list of registers when you add tags docid 8se7z3pmrfwl1nmzcwalx 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 583p fbuozem6whgrdgkq tag formula variables docid\ ifbwcou90qtfodk hrysr register table name value types access types address format min address max address i bit bit r/w ddddd 1 32768 q bit bit r/w ddddd 1 32768 m bit bit r/w ddddd 1 32768 g bit bit r/w ddddd 1 32768 t bit bit r/w ddddd 1 32768 sa bit bit r/w ddddd 1 32768 sb bit bit r/w ddddd 1 32768 sc bit bit r/w ddddd 1 32768 s bit bit r/w ddddd 1 32768 i word r/w ddddd 1 32753 q word r/w ddddd 1 32753 m word r/w ddddd 1 32753 g word r/w ddddd 1 32753 t word r/w ddddd 1 32753 sa word r/w ddddd 1 32753 sb word r/w ddddd 1 32753 sc word r/w ddddd 1 32753 s word r/w ddddd 1 32753 r word r/w ddddd 1 32768 ai word r/w ddddd 1 32768 aq word r/w ddddd 1 32768 w word r/w ddddddd 1 5000000 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)