GE Fanuc CMM Serial (Gen1.3)

review the following information for setting up and configuring the ge fanuc cmm serial (gen1 3) driver litmus edge compatible series compatibility parameter compatible items driver type serial 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 record the serial communication parameters for the device otherwise, use plc software on your machine to look up these parameters you use these parameters for setting up the driver in the next step refer to the following device details device ge fanuc ic693cpu363 device type (driver ge snp x (ge cmm) i/f rs485 4w (rs232) step 2 set up the plc device in litmus edge devicehub configure the following parameters when you connect a device docid\ pal6abpzbrimdu9lvgj30 with this driver update default values to the specific setup of your device parameter value type ge fanuc driver ge fanuc cmm serial (gen1 3) communication port local serial connection file path baud rate 19200 data bits 8 parity even, odd, none stop bits 1 step 3 configure the list of registers when you add a tag docid\ tuy hh0gi8djvot70wroh to the connected device, refer to the following register table and tag parameters see the following additional resources if necessary organize device and tag data by using metadata docid\ mu 6j6zhi0cvchdad0w8n tag formula variables docid\ io7xgyrdvv vmpnfxoaci register table name value types access types address format min address max address description i bit r/w ddddd 1 10000 input relay q bit r/w ddddd 1 10000 output relay m bit r/w ddddd 1 10000 auxiliary relay g bit r/w dddd 1 7680 t bit r/w ddd 1 256 sa bit r/w ddd 1 128 sb bit r/w ddd 1 128 sc bit r/w ddd 1 128 s bit r/w ddd 1 128 r word r/w ddddd 1 32640 data register aq word r/w ddddd 1 10000 analog output register ai word r/w ddddd 1 10000 analog input register 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 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)