SImatic OP5 error $115

R

Thread Starter

Ronny

The error sometimes goes away when i pull out the plc cable and reconnect them (sometimes after 10 times...), and then the OP works normal. After a reset, the same error :-( I programm the op with protool lite, the cable is an original siemens. When i pull the cable, the op gives "plc not connected" so i think the cable is ok ? I also tried on a S100 cpu 102 plc -> the same error. The plc setting are correct (or not..) Dit i do something wrong ? is there another setting, i did forget ? I'm a beginner with OP's... Thanks in advance, Ronny
 
P
Ronny: Try calling the Simatic Hotline at 800-333-7421. I personally have not worked with the old S5 PLC but they have and they can be a valuable resource for you. Ron Powers Senior Product Specialist-HMI Siemens Energy & Automation
 
M

Michael Griffin

Siemens manuals are available for download for free from their web site. The OP5-OP15 manual lists error 115 as "$ 115 Establishment of logical link". This is not terribly informative, but I have some experience with Siemens text OPs and S5-95Us and I will try to give you a few suggestions. I don't recall having much trouble getting an OP to communicate, but you have to take care of a few steps first. You mentioned you are using Protool Light, which means you are using the 2nd generation OP5. The earlier ones looked identical but used Comtext and won't work with Protool (and visa versa). This isn't related at all to your problem, but I thought I should bring this to your attention now in case you happen to deal with those as well. As to your problem, you didn't mention whether you performed the other steps required to get an OP to communicate. I will list them all, and you can tell me if you left anything out. 1) Configure an OP program. Make sure you start with the standard example program, as you will want to include the standard OP system screens (which let you do things like let you change modes, etc.). 2) Check the communications options, to make sure they are set to the interface you are using (I think there are various options). 3) Load the program into the OP (you mentioned you did this). You didn't mention the type of interface you are using to connect to the S5-95U. There are a variety of methods. I will assume you are connecting to the program port, as this is the most common method I have seen. 4) Load FB51, and call it appropriately. If you don't know what I am talking about, then this is your problem right here. The OP won't talk to the PLC without this. 5) Create a data block for FB51, and load it also. 6) Set up the appropriate initialisation commands in OB21 and OB22 (the cold and warm start OB blocks). 7) Start the PLC program running. 8) Plug in the OP to the program port. 9) The OP should go through a start up cycle, and then start talking to the PLC. If the above is followed, you shouldn't have a problem. If you are not familiar with using FB51, then reply to the list and I can show you an example. I'm not sure where Siemens documents this, and you can probably comb through the OP manual without finding any reference to it. I think this sort of thing is in a separate communications manual because there are so many possible communications options. If you do need more information, then be sure to describe what type of interface to the S5-95U you are using. I've worked with dozens of S5-95U plus OP systems (OP20, OP5, OP15, OP7, OP17) connected via the program port and also via SI2. I don't recall for sure, but I think if you want to connect the OP to an S5-102, you may need a different version of FB5? (FB fifty-something) than you do for a 95U. I think Siemens wrote a smaller version FB (with fewer features) for the 102 to save memory on this smaller CPU. I've never seen an OP used with a 100 or 102 though. ********************** Michael Griffin London, Ont. Canada [email protected] **********************
 
Michael, Thanks for the explanation ! I ditn't call the FB51, thats probably my problem... I ditn't see it in the OP5 manual, that i downloaded earlier, from the Siemens site, like you suggested. I've been looking for the communication manual, cause i knew they existed, but i can't find them. I'm new to programming displays, and i'm glad you answerd my question ;-) The configuring of the op seems good. I started with the example program, and i took the Simatic S5-AS511 driver, with the following parameters: CPU type: S5 95U, interface: IF1 A(TTY), and a 9600 baud rate. Further, i assign the area pointers for the interface area, screen number, event messages, and alarm messages. I'm connecting the OP on the programming port of the PLC. If you can give me some more information about the FB51 (is this already inside the S95U ?), and how to configure this. The OB21 and 22 also need some explaning ;-) And if you, by any chance know where to download a communications manual... Thanks in advance, Regards, Ronny [email protected]
 
D

Donald Pittendrigh

Hi All PLC restart running is not an error message, it is a status message and means the PLC and OP communications is being initialised. The next message would be PC restart completed, but you will only see this when the comms has been successfully initialised, which is presumably not happening. Cheers Donald Pittendrigh
 
D

Donald Pittendrigh

Hi All This solution depends the use of FAP ar Free ASCII Protocol, if you are using Profibus interface for comms, (and I am sorry I missed the earlier posting so I don't know if you told us this) then the problem may lie elsewhere, so lets start by getting the hardware definition straight. Cheers Donald Pittendrigh
 
M

Michael Griffin

At 08:13 30/01/01 +0200, Donald Pittendrigh wrote: <clip> >This solution depends the use of FAP ar Free ASCII Protocol, if you are >using Profibus interface for comms, (and I am sorry I missed the earlier >posting so I don't know if you told us this) then the problem may lie >elsewhere, so lets start by getting the hardware definition straight. <clip> Well, no actually it doesn't. I don't believe I've ever seen FAP used for the connection I described, and this is by far the most common connection I have seen with a 95U. AS511 seems to be the more common selection for this. The original question from "Ronny" didn't mention the type of connection he was using. Going from previous experience though, I would guess that he didn't realise that he had to have a program running with the special function block in the PLC in order to get the OP to talk to it through the program port. This seems to be a common mistake people make when dealing with this for the first time. ********************** Michael Griffin London, Ont. Canada [email protected] **********************
 
M

Michael Griffin

The web address for Siemens manuals is at: http://www4.ad.siemens.de/csinfo/livelink.exe?func=cslib.csinfo&objtype=9000 &objAction=cshbprompt&lang=en&siteid=cs The web site was not functioning properly when I went to look for the manual, so I couldn't identify it for you. I think if you follow my instructions below though, you should be able to get your OP working without one. The manual I read was a printed one which I got several years ago. FB51 is a function block written by Siemens which you must include in your program. It is not one of the built in function blocks. I think the original copy I am using was from an example which came with the Comtext software (for the previous two generations of OP). There are other FB blocks for other protocols. Please note that I believe there are different versions of the FBs for different classes of S5 PLC (some models don't implement all the instructions). For example, you would use a different FB for an S5-90U than you would for an S5-95U. This is explained in the OP communications manual if you can ever find it. If you look in the samples provided with your Protool software, you should see a couple of Step 5 programs which are intended as examples. These may contain FB51. The following shows how to call FB51. In this example, PB2 is a program block which is called from OB1 every scan. I use this PB to gather the general OP related functions together. - Load FB51 into your program. This is for AS511 (which you are using). There are other FBs for other protocols. AS511 seems to be the most common method though. - Create a data block for FB51 to use (in this example, DB51). I have set my block to 255 words long. Consult the communications manual to see if it can be any shorter than this. This block is for FB51 to use, don't touch it except for initialisation (see below). - Next, load accumulator 1 with the byte constant KY 51 0 (L KY 51 0). The accumulator is used to pass parameters to FB51. The "51" in the constant tells FB51 that the data block to use is "DB51". - Next call FB51 (JU FB51). - After FB51, a transfer of accumulator 1 to a flag word (FW254 in this example) will save information from FB51 (T FW254). You can look in this word to see error information, but I've never had any reason to look at it. PB002 This block handles all communications and interaction with the OP17. SEGMENT 1 Call the OP17 interface function block to enable communications with the OP. : L KY 51 0 : JU FB51 NAME: TDOP:511 : T FW254 : OB21 and OB22 should be set up to initialise communications with the OP when the PLC starts up. This is done as follows: OB021 SEGMENT 1 : C DB51 : L KF +1 : T DW64 : BE OB022 SEGMENT 1 : C DB51 : L KF +1 : T DW64 : BE All this is doing is to write a constant of "1" into dataword 64 of the communications data block on start up. One of the OBs is called on a "cold start", while the other is called on a "warm start" before OB1 is executed. I usually create a data block dedicated to acting as a "mailbox" for OP communications. The OP reads from and writes to this area, while the PLC program also reads from and writes to there. This allows me to concentrate the reads and writes close together, which makes for more efficient communications. Please note, I am not talking about the DB51 data block, but rather another one. The DB51 in this example is for FB51 to use, not for you to play with, other than to initialise it. The above is all you need to get the OP communicating. If you look in the PLC Archive, you will see some examples of FBs which I wrote for working with OPs which simplify things like acknowledging alarms. I've found the Siemens OPs very nice to work with for the sort of applications I have. The alarm features make displaying and acknowledging alarms (faults) very easy. The screens are also very handy. I understand there are bugs in the recipe system though, and I haven't found a use in any of my applications yet for events. Be sure to include the standard screens in your OP program. They give you some very useful utility features. I usually renumber them to some high numbers (90 - 99) and include the main system screen at the bottom of the screen directory. The OPs have a lot of features and can save you a lot of PLC programming if you know how to use them. The original trouble I had was to figure out how to use those features to do what I wanted with the least amount of work. I've put a lot of thought into that, and have come up with some general principles that seem to work well for me. If you want to carry on this thread to discuss that, let me know. ********************** Michael Griffin London, Ont. Canada [email protected] **********************
 
Top