rmiell

That was my intent, after trying for a few months to get the AIC to work correctly. However, now I am having trouble getting Studio to communicate with the ENI. I can while in RSLogix500, but can't while running RSView Studio. Can you give me pointers for setting up my application in Studio? I need to be able to run this ML1200 from 2 different computers. Thanks for the reply. Rick Miell

Ah, therein lies one of my problems. I am not using an panelview. I want to use RSView ME station on a computer to run an application to order the ML1200 around. Rick

Project: control various equipment (door locks and garage door openers) from 2 different desktop pcs (CSF1 & CSF2), at same time. Equipment: MicroLogix 1200 with input/outputs tied to the equipment identified in Project, above. 2 desktop computers, with serial ports, and both connected to citywide network. 3 (three) #1761-NET-AIC units, 1 (one) 1761-NET-ENIW (series D), various AB numbered cables (1761-CBL-PM02, 1747-CP3) Software: RSView ME Station, RSLinx Enterprise, RSView Studio, RSLogix500 One AIC interface is connected at present, to one of the desktops (CSF1), via serial cable to Port1. AIC unit is also connected to ML1200 through Port 2 of the AIC. RSView ME Station will run .mer application in this setup, using CSF1. I tried using the same setup on CSF2, but got a message about no license found on this machine, and will shutdown in 2 hours. Once opened, application ran ok, tho I started getting alarm messages during the running of this application. I did not log these alarms, as I was just verifing that it would run using CSF2, which it did. As stated in Project, above, I would like to have this application running on 2 different desktops, at the same time. Can anyone direct me to the correct layout of equipment.cables, etc…? TIA Rick Miell

I get the error message when I test my application from my laptop, which is connected to the network. My communication is using RSLinx. In Studio, I have my communication setup as AB_ETH-1,ethernet, in which I have the ip address of the ENI, set for the Micrologix 1200 device. This takes a little danciing to get selected, because when browsing in AB_ETH-1, it auto selects the 1761-NET-ENIW as it's device, using the ip address I have set it up for (xxx.xxx.1.100). I have to add a new device (microLogix 1200) with an ip address of xxx.xxx.x.101, then delete the eni, then rename the ML1200 as xxx.xxx.x.100. Am I doing it wrong? Rick

I have a MicroLogix 1200 connected to the 1761-NET-ENIW, networked through company network, connected to my laptop. I can connect to ML1200 via RSLogix 500 ok, but can't in RSView Studio. In Studio, when I test application, I get the following messge " Could not set RSLinx Enterprise data server configuration. Do you wish to continue? (yes or no)" I think I have my communciations set up correctly in Studio. Any ideas? TIA Rick Miell

This could be whats happening. Thanks for that info. Rick Miell

Thanks for the info. I am not using PanelView. What I have is a PC connected to a ML 1200. The pc has a screen that the police dispatcher can click on, using mouse. The pushbuttons on this screen control different things, such as electric door strikes, and 4 garage door operators(open, close, stop). My problems comes into being when the dispatcher clicks on the "close" pb for one of the doors, to close it. The door closes ok, and stays that way until the dispatcher get a request to open that same door. The door will open, correctly, but at the point where the door opens all the way, the operator has a signal from the close output (because it is "stuck on"), and will close the door right away. You can see that this is a problem, since the fire truck driver has started into the bay with the open door. Luckly no damage to trucks yet, but could easily happen. Hence the request, from me, to add ladder instructions to keep this from happening. The RS equipment has replaced a manual pushbutton setup in dispatch, which came about when the dispatch area was remodeled last year. Instead of installing a cheesy pushbutton panel on a brand new console, I talked the powers-to-be into using a ML system, so dispatcher can control these doors from their pc. I don't really want to have to rewire the operators to give me open/close indications at my ML1200, since it is somewhat limited on inputs. I think the post about unlatching the pushbutton might work, but if anyone has any other suggestions, please feel free to contact me, or post the info here, in order to help others who might have this same, or similiar problem. Again, thanks. Rick Miell

I thought a link to the other forum would save me from having to type it all again............ My RSViewME display is where a momentary pushbutton resides. It controls an output in a Micrologix 1200. Intermittenly, after the pushbutton gets pressed, the output stays on, instead of momentary on/off. The question (does this happen, and what to do) was asked by another poster, and he received a few replies that it does happen to others. One poster replied that ..." I found the safest way is to unlatch the bit in the PLC once the action that was supposed to take place (e.g. start a motor) is accomplished. The way I accomplished this is easily is putting all the N.O. buttons in the same word or set of word. Then a put a timer on the word whenever it is not equal to 0 (one of the buttons was pushed) and when the time ends, I set the word to zero". My question is two-fold. #1: What is meant by, or how do I accomplish ..."putting all the N.O. buttons in the same word or set of word"? #2: How do I ... "when the time ends, I set the word to zero"? I am using RSLogix500 for my ladder, and RSViewME for my displays, etc... I replied back to the posting last week, but have not heard anything from that forum yet. TIA Rick

Hello. New to this forum, but it looks like I have come to the right place. I have a similar problems as stated on this other forum PLC.net and I thought I would ask you all about this. Any suggestions/comments would be greatly appreciated. Rick Miell PS. Keep up the good work answering these postings