XEM EtherNet/IP Implicit Scanner EDS Setup - LS Electric XGB PLC from AutomationDirect

if our xgb PLC has an EIP module installed and configured we can set up an implicit ethernet connection the XM CPU is capable of being an implicit scanner that initiates a connection or an implicit adapter that is available to be connected to in this video we will be using the gs20 variable frequency drive EDS file to set up an implicit scanner connection and message in the xg5000 software this will allow the EIP mod module to communicate with and control our gs20 vfd to set up the PLC as an implicit scanner we first must configure the EIP module and the peer-to-peer connection these are both covered in a separate video it is important to note that the ls software and documentation May refer to the scanner as a client and the adapter as a server it is also important to note that data can move in two directions for ethernet IP it can go from the scanner or originator of the message to the adapter or Target it can also go from the target to the originator as such Target to originator or t to O data is called input data since it provides incoming information to the controller and originator to Target or o to T data is called output data since it provides outgoing information to the adapter to set up the PLC as an implicit scanner we can either manually configure the message or we can use an EDS file to configure the connection the xg500 000 software has a pre-made library of various EDS files we can also add or register external EDS files to this Library let's register the gs20 Eds file to allow implicit ethernet IP communication with a gs20 variable frequency drive I have already downloaded the gs20 Eds file from automationdirect.com and have it stored in my downloads folder let's start by going to tools EDS register EDS file the open window pops up and we can navigate to the Eds file we wish to import in our case we will go to downloads and select the gs20 Eds once we select it we can click open this will import the Eds file into our software we can see this if we go to the Eds information tab on the right side of the software window we see a new subsection under the communications adapter section and if we maximize it we see that it imported the gs20 Eds to add a connection using this EDS file we now go to our project window and maximize the P2P 03 connection we created in the video on configuring the EIP module we will doubleclick EIP settings to open the ls PLC EIP settings 03 tab here we can drag and drop the version 1.1 gs20 EDS file that we registered doing this opens the Eds Channel popup window and here we can set the channel number and IP address of of the drive we are connecting to in our case the drive resides at 192.168 27105 the channel number is used by the software to determine which device we are targeting when we set up our Communications Block in The Next Step the system will automatically increment the channel number for each additional device added and it will not allow duplicate Channel numbering we will leave this at zero now that we have added the channel to the connection we are ready to configure a message if we double click on EIP block the software opens the lslc EIP 03 tab the software gives us a warning message because we haven't assigned any variables to be accessible for ethernet IP communication yet since we will create these once we found out the correct data size in the Eds file we will select okay for now if we type the desired channel in this case Zero for R gs20 into the channel column for the first row it adds implicit connection under the operation mode column we can select from two IO type options based on the Eds file we will select the drive control and Status option if we selected Drive status listen only it would allow us to receive information from the drive but not to control it many ethernet IP adapters like the gs20 may have several list and only connections connected simultaneously but can and must have only one control and Status connection controlling them once we add this it adds another row with the channel column grade out this is because the drive control and stat stus connection is an exclusive owner connection that uses an IO message to provide us with both input and output data if we select the listen only connection which will be only input data we see this is set to only one row let's change it back to the drive control and Status connection for our example though as we can see from the selection options in the connection type field the Eds file for the gs20 indicates that it supports both multicast and point-to-point connection types for its ttoo data since we do not have multiple devices needed to consume the gs20 T to input data we will choose pointto point for our example the function column is only used for explicit messaging so we can ignore it for now next we will set up our request packet interval or RPI as well as the tto input and OD output data sizes to do this we click the parameter button this will open the parameter settings popup window we see the T to RPI the o to T RPI the T to O input data size and the OD output data size because we used an EDS file these fields have all been pre-populated we can adjust the RPI as needed but we will leave them at 250 milliseconds if we attempt to change the input or output data sizes the software prevents it this is because the Eds file has already specified the correct sizes scanner and adapter must agree on the correct data size to be transferred a mismatch will lead to message errors when the link is enabled while some adapters have configurable data sizes the gs20 is hardcoded to this data size and the Eds file includes that information once we select okay we can then adjust our timeout setting we will set the timeout to the lowest setting of RPI X4 in our case with a 250 millisecond RPI this will be 1 second finally we will need to set up the memory location the PLC will use to store the input values and the memory location from which the PLC will take the output values to do this we will create two arrays but we need to know what size of array to use ethernet IP uses the 8bit byte as the smallest data size so input data size is 32 bytes and output will be 6 bytes if we look at the manual for the gs20 however we see that the input and output information is held in 16bit 2 byte word registers we could set our variables for input and output data as bite arrays and then deal with high bite and low bite parsing with further copies in the logic however it is much easier to just let the PLC parse the data automatically if we convert 32 from from single byte to a 2 by word we get a value of 16 2 byte words the same math for the output data will give us three 2 by words for the six bytes of output information let's go to the global slir variables Tab and insert two rows if we select a type of array and then click off of the selection the software will open the select array popup window and we will set up a 1D array of 0 to 15 elements this corresponds to 32 bytes of information for 16bit data size the array type can either be word or int if we use word it will display the value in HEX by default so let's use int to see it in dmal we click okay and we will name this array eore input array and make it a global variable it is also important to make sure we check the box for EIP OPC UA this allows the PLC to use this as part of our EIP transfer of information now we do the same for our output array we will make it a 1D array of 0 to2 elements and in type this will again correspond to six bytes of information this one we will name eore output uncore array we will make it a global variable with a checkbox for EIP OPC UA as well now we can add those arrays to our message on the lslc EIP 03 tab we can double click on the local TAG cell on the first row if we attempt to use an array of the wrong dat a size the software will give us a warning and prevent us from using it let's select the output array for the input line which will be the wrong size and there is the software looking out for us to ensure our data transfer makes sense let's go back and use the input array for the input section and the output array for the output section we can now write this to the PLC once complete we will have to reset the PLC as we have made changes to the communication settings we can then reconnect and go into monitor mode if we refer to the gs20 manual again we see that for our input array element three will tell us our Drive output frequency in our output array element Z bit one will put the drive into run mode and Bit Zero will put it back into stop mode element one will allow us to set a Target frequency let's add these three elements to our monitor window we see that currently our actual frequency is zero our Target frequency is zero and our Command data word is also zero since the command word is actually a bit map let's right click on that line and select represent in binary this will show the status of each bit in the 16-bit word let's set our Target frequency to 6,000 as this corresponds to 60 HZ in the gs20 let's turn on bit one the second bit of the command word and sure enough we see that frequency feedback increasing as the drive accelerates and there it stopped at 60 let's change our frequency command to 40 HZ and there's the drive going down to 40 and now let's turn off bit one and turn on Bit Zero to put the drive back into stop mode and the drive executes a deceleration back down and stops at 0o Hertz perfect we have now configured an implicit ethernet IP connection with the PLC acting as the scanner by using the gs20 Eds file we can now control our gs20 vfd from the plc