Mitsubishi FX3G ASCII Ethernet (Gen1)

review the following information for setting up and configuring the mitsubishi fx3g ascii ethernet (gen1) driver litmus edge compatible series compatibility parameter compatible items driver type ethernet validated devices/series https //www mitsubishielectric com/fa/products/cnt/plc fx/items/index html 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 note only one connection is allowed per port defined in the plc see the steps below to view and edit the open ports on the plc if the device is configured for ethernet access, find its network parameters otherwise, follow the steps below to configure your device note down the following information and refer to it as needed device mitsubishi fx3ge 24m communication i/f ethernet refer to the following figure connect the device to your pc using usb and launch the gx works 2 v1 560j software click online > read from plc select plc series set up the connection click connection test from the navigation panel, click parameter > plc parameter > ethernet port from the navigation panel, click connection destination > connection1 double click plc module , click search for fxcpu on network , and then select the target device click connection test step 2 set up the plc device in litmus edge 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 mitsubishi driver mitsubishi fx3g ascii (gen1) network address the device address you defined in step 1 port 5001 step 3 configure the list of registers when you docid 8se7z3pmrfwl1nmzcwalx to the connected device, refer to the following register table and tag parameters refer to the following additional resources docid 583p fbuozem6whgrdgkq docid\ ifbwcou90qtfodk hrysr register table name value types address format min address max address description x bit ddd 0 255 input relay y bit ddd 0 255 output relay m bit dddd 0 7999 internal relay t bit ddd 0 511 timer contacts c bit ddd 0 255 counter contacts sm bit dddd 8000 8511 source int relays s bit dddd 0 4095 step relays r word ddddd 0 32767 file register sd word dddd 8000 8511 service data register cv2 word ddd 200 255 counter value d word dddd 0 7999 data registers cv word ddd 0 199 counter value tv word ddd 0 511 timer value 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)