adccommunitymod (AutomationDirect) asked a question.
Redlion Ethernet Communications
Created Date: January 19,2009
Created By: allukes
**** This post has been imported from our legacy forum. Information in this post may be outdated and links contained in the post may no longer work.****
Has anyone connected a G3 to an Ecom100 module? Having no luck with this at all. Tried using the Modbus Master Protocol and they specify an IP address, TCP Port and Unit Number. Do you have to set up a PEER TO PEER link in Net Edit? Also the Modbus adresses they have for digital inputs start at 100000. That seems high, but the Redlion Tech says no. Any help would be appreciated.
Created Date: January 20,2009
Created by: amos
No, you do not have to setup peer to peer on the Ecomm.You only setup peer to peer if you want the module to to be the master. I have done this and it should work fine. Make sure you have the proper Ip Address, also try to ping the Ecomm module. Also modbus Address 10001 = GX0, modbus Address 12049 = X0. You will find some help here http://support.automationdirect.com/technotes.html#plccomm . Download the Excel file it's very handy.
Created Date: January 20,2009
Created by: allukes
Well, I finally was able to figure this out. It is very confusing and not very straight forward. If I didn't need the protocol conversion capability of the display, I probably would not have used it.
I tried the PLC DIRECT/UDP Master first and it did not allow single bit control. So I chose the MODBUS TCIP Master protocol.
To enter the modbus address for each tag, you only enter the offset from the base address. Apparently they are trying to accomodate extended addressing but it is confusing. For example if you want to set the GY0 Coil (Modbus Address # 0001)you choose Digital Coils (Element 0) and enter a 1 into the edit box. That is straight forward. However, you cannot set the GX0 coil (Modbus address 10001). It allows you enter the value into the edit box but the ECOM100 does not allow it to work. There is no way to turn on the GX0 bit in the display. You only use those bits to read bit status from the PLC. To enter that in a tag, you select Element 1 and enter a 1 in the edit box, not 10001. It adds 10000 to the value. Don't pay any attention to the value in the mapping box, it will say 100001. Same for the interger values, for example V2000 (Modbus 41025) enter only 1025 as a holding register, element 4.
Created Date: January 21,2009
Created by: HMI Eng
Out of curiosity, what protocols are you converting?
Created Date: January 21,2009
Created by: allukes
I need to pass information from a Siemans PLC , a third party Soft PLC (X something..), KEP OPC server and a DL260. It's pretty unique how they do it.
They set up a Gateway block of data in the display between the 2 protocols. It has a lot of capability, but you definitely pay for it. I am just not pleased about the Koyo Ethernet driver. I guess they don't see much payback from improving that. It looks like I can do everything I need with the Modbus protocol, just cumbersome.
Created Date: January 22,2009
Created by: jackson
You kind of lost me there. Are you saying that you need the capability to set the Input Bit 100001?
There is no function code to set Input Bits. They are read only bits.
Or are you saying something else?
Created Date: January 22,2009
Created by: allukes
No, not on X bits . I want to set the GX bits. I like to set up my HMI's so that in the PLC the GX coils are Pushbuttons on the display. If I had a real world contact on the operator panel, it would be an Xn input. So to be consistant I use the GX for HMI inputs. However, the way that the Modbus protocol is setup in the ECOM, you can't set a coil in the remote device to turn on a GX coil. You can only set GY coils. It's confusing in the PLC program to have a GY coil as an input contact. I think you should be allowed to set it up either way, afterall the only convention is one set by the user.
Created Date: January 22,2009
Created by: jackson
Typical convention is to set internal (c bits) bits from an HMI.
I believe the GX bits were designed to be used with remote I/O so it would not be a good practice to use them even if it were allowed.
But that's just my opinion...
Created Date: January 23,2009
Created by: allukes
I treat HMI's as remote devices. Plus there are gobs of Gx and Gy memory available. I started using those years ago when we were using 405's and were running out of C coils on larger machines, so we designated the Gx and Gy for the displays and kept the C memory for internal bits in the program. It made sense back then and I kept the convention. In addition to that, later I was working on some machines programmed in Japan and they too used that convention.
Created Date: March 13,2009
Created by: JArriola
That is funny to me because I am also using the Gx/Gy bits for my HMI just because it was just easier for me to keep them straight in my programming. as I had a ton of Cbits that I have used and named with a similiar naming convention to the actual stage numbers or timer numbers to make programming easier. So I know if it is Gx/Gy it is for HMI.I think it is alot of help.
Created Date: January 19,2009
Created by: allukes
Has anyone connected a G3 to an Ecom100 module? Having no luck with this at all. Tried using the Modbus Master Protocol and they specify an IP address, TCP Port and Unit Number. Do you have to set up a PEER TO PEER link in Net Edit? Also the Modbus adresses they have for digital inputs start at 100000. That seems high, but the Redlion Tech says no. Any help would be appreciated.