adccommunitymod (AutomationDirect) asked a question.
Created Date: April 30,2004
Created By: chris.zeman
**** 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.****
First, here's the setup: DL-250, 6 slot rack, H2-ECOM in last slot (Slot 4) DL-05 with H0-ECOM They are each connected to a 5-port ethernet switch with fiber linking the two switches. The switches are ADAM modules, but I forget which model number. (I'm at home right now. lol) Anyways, I have the module I.D. in the 250 set to 01 and the DL-04 set to 02. There are 2 rungs in the 250's program that perform the RX and WX commands. LD K402 and so on, so forth. The RX run sets C10 locking out the next rung, which performs a WX when C10 is set and SP130 is not true. The only rung in the DL05 is END. There really is not program in it. Last year, I had the two communicating using their secondary ports over fiber through RS-232 to fiber converters and everything worked great. This year I added the ECOM modules and modified the RX/WX rungs for them. Now, the controllers aren't communicating and SP131 in the DL205 is always on. The strange thing is, although I can communicate with the DL05 from DirectSoft on ethernet, when I use NetEdit and view the properties of the H0-ECOM, there are question marks in the "Type " box. It didn't do that the other day. All the firmware is up to date as well. Any ideas or suggestions? I'm hoping it's just something simple that I overlooked. Thank you, Christopher Zeman
Created Date: April 30,2004
Created by: toml
I believe the "comm busy " bit for slot 4 is SP133.
Created Date: April 30,2004
Created by: chris.zeman
I'll have to look again when I get back to work, but I thought SP133 would be the "Communications Error Slot 5 " bit. Oh well, I'll find out in about about an hour. http://forum1.automationdirect.com/board/biggrin.gif
Created Date: April 30,2004
Created by: Mike McClanahan
Welcome to my world. I am having the same problem with Netedit on a 250 ECOM, shows all question marks on the module type, if I rescan the network enough times it will give me the module type. I believe the problem is that netedit is timing out just a little bit early and missing part of the information but that is a guess.
As for your problem, slot 4 is 130 and 131
for the busy and error flags. Your existing logic should have run in this but you have to use the number of the ecom module and not the station address that you used in the serial port version of the RX/WX. Also do not forget to put a normally closed busy flag in line with the WX/RX instruction so it can keep WX/RX from being polled before it completes the last WX/RX.
Created Date: April 30,2004
Created by: chris.zeman
First, here's the setup:
DL-250, 6 slot rack, H2-ECOM in last slot (Slot 4)
DL-05 with H0-ECOM
They are each connected to a 5-port ethernet switch with fiber linking the two switches. The switches are ADAM modules, but I forget which model number. (I'm at home right now. lol)
Anyways, I have the module I.D. in the 250 set to 01 and the DL-04 set to 02. There are 2 rungs in the 250's program that perform the RX and WX commands. LD K402 and so on, so forth. The RX run sets C10 locking out the next rung, which performs a WX when C10 is set and SP130 is not true. The only rung in the DL05 is END. There really is not program in it.
Last year, I had the two communicating using their secondary ports over fiber through RS-232 to fiber converters and everything worked great. This year I added the ECOM modules and modified the RX/WX rungs for them. Now, the controllers aren't communicating and SP131 in the DL205 is always on. The strange thing is, although I can communicate with the DL05 from DirectSoft on ethernet, when I use NetEdit and view the properties of the H0-ECOM, there are question marks in the "Type " box. It didn't do that the other day. All the firmware is up to date as well. Any ideas or suggestions? I'm hoping it's just something simple that I overlooked.
Thank you,
Christopher Zeman