Skip to Content

Register Login

Industry Online Support

Technical Forum

Navigation

Interpreting NC as NO contacts?

Created by: RAF_Blackace at: 5/20/2014 2:59 PM (24 Replies)

Rating (0)

Thanks 10

Result pages:: |; 1 | 2 | 3; |

25 Entries

Entries per page: 10 | 20 | all

5/20/2014 3:39 PM	Rate (0)
Jens_app Gold Member Joined: 1/5/2011 Last visit: 3/9/2023 Posts: 814 Rating: (119)	RAF_Blackace Using flags does not fix it (see image), these test flags are not used anywhere else in the program.The only thing that seems to fix it is adding any other instruction to the line. Hi RAF, I see you are doing some strange things there, for example you are writing toM1234.1 two times in the same network. Like I suggested before, check crossreferences to see if you haven't got any strange read/write issues in your program. Kind regards, Jens
	Keep it simple and on-topic. A simple straight-to-the-point answer is often of more quality than a complicated one.
Suggestion To thank Quote Answer

5/20/2014 3:49 PM	Rate (0)
RAF_Blackace Posts: 13 Rating: (0)	Jens. There is nothing strange at all going on here other than the interpreter incorrectly treating the NC coil as a NO. The M1234.0 coil is a test coil that is only being read here, itis used nowhere else in the program either directly of indirectly. The M1234.1 coil is simply a coil shoved in to show that adding anything else to the line with a single coil fixes the issue. The fact I am writing to coil M1234.1 twice is completly irrelevent.
RAF_Blackace Posts: 13 Rating: (0)
Suggestion To thank Quote Answer

5/20/2014 3:56 PM	Rate (0)
Jens_app Gold Member Joined: 1/5/2011 Last visit: 3/9/2023 Posts: 814 Rating: (119)	RAF_Blackace Jens. There is nothing strange at all going on here other than the interpreter incorrectly treating the NC coil as a NO. The M1234.0 coil is a test coil that is only being read here, itis used nowhere else in the program either directly of indirectly. The M1234.1 coil is simply a coil shoved in to show that adding anything else to the line with a single coil fixes the issue. The fact I am writing to coil M1234.1 twice is completly irrelevent. Hi Raf, I'm checking out screenshot bool4, and I see you are using M1234.1 asan assignment --( )--at theinput "simovertHealthy" on your FB1089, you are also using an assignment of M1234.1 at input of overloadHealthy, can I ask you why? Why arent you using a NO contact of M1234.1 instead --\| \|--? I also see you are setting M1234.1 with an assignment --( )-- at the output of your FB1089. In my opinion, things like that can cause bugs. Kind regards, Jens
	Keep it simple and on-topic. A simple straight-to-the-point answer is often of more quality than a complicated one.
Suggestion To thank Quote Answer

5/20/2014 3:57 PM	Rate (0)
0_Einstein Diamond Expert Joined: 7/7/2010 Last visit: 3/31/2023 Posts: 13226 Rating: (2150)	And to be clear, you are currently using V12 SP1 Update 3, correct?
	science guy
Suggestion To thank Quote Answer

5/20/2014 4:03 PM	Rate (0)
Jens_app Gold Member Joined: 1/5/2011 Last visit: 3/9/2023 Posts: 814 Rating: (119)	I think in your example you are using assignments and contacts the wrong way. Please correct me if I'm wrong. Quoting the siemens manual: Assignment --( )--: You can use the "Assignment" instruction to set the bit of a specified operand. Normally open contact --\| \|--: The activation of the normally open contact depends on the signal state of the associated operand. When the operand has signal state "1", the normally open contact closes and the signal state at the output of the instruction is set to "1". I hope this helps. Kind regards, Jens
	Keep it simple and on-topic. A simple straight-to-the-point answer is often of more quality than a complicated one.
Suggestion To thank Quote Answer

5/20/2014 4:09 PM	Rate (0)
RAF_Blackace Posts: 13 Rating: (0)	Jens. Just to keep you happy. As you can see (Image BOOL5) the coil memory M1234.0 is in reality OFF, but this network is interpreting it as both ON and OFF. We seem to have a quantum coil. It is not just here on this call, it is everywhere in my program where a single NC contact is used as an input to a function. huggy.. I am using TIA Potral V12 SP1 Update 3. Attachment BOOL5.jpg (88 Downloads)
RAF_Blackace Posts: 13 Rating: (0)
Suggestion To thank Quote Answer

5/20/2014 4:17 PM	Rate (0)
Jens_app Gold Member Joined: 1/5/2011 Last visit: 3/9/2023 Posts: 814 Rating: (119)	RAF_Blackace Jens. Just to keep you happy. As you can see (Image BOOL5) the coil memory M1234.0 is in reality OFF, but this network is interpreting it as both ON and OFF. We seem to have a quantum coil. It is not just here on this call, it is everywhere in my program where a single NC contact is used as an input to a function. huggy.. I am using TIA Potral V12 SP1 Update 3. Hi Raf, No need to keep me happy, I'm just trying to help... I saw screenshot bool4 and what you were doing there wasnotcorrectmy eyes, now I see it corrected in this screenshot so no problem here. Now the thing is, we only get to see a part of your program, we don't know if there is a mistake somewhere else in your program that is causing this so called bug. Like I said before it might be a bug, but no need topanic too early. Kind regards, Jens
	Keep it simple and on-topic. A simple straight-to-the-point answer is often of more quality than a complicated one.
Suggestion To thank Quote Answer

5/20/2014 4:30 PM	Rate (0)
Jens_app Gold Member Joined: 1/5/2011 Last visit: 3/9/2023 Posts: 814 Rating: (119)	RAF_Blackace It is not just here on this call, it is everywhere in my program where a single NC contact is used as an input to a function. Hi Raf, I am sorry, but perhaps if you are having this everywhere in your program my insinuationswhere wrong and you are probably dealing with a bug. My mistake. Sometimes I need to keep to first opinions . Kind regards, Jens
	Keep it simple and on-topic. A simple straight-to-the-point answer is often of more quality than a complicated one.
Suggestion To thank Quote Answer

5/20/2014 4:39 PM	Rate (0)
RAF_Blackace Posts: 13 Rating: (0)	Jens. I have created a new project with only a single call from OB1 followed by a BEU. This calls FB2 that has nothing in it. You can see from the images that the Marker M2345.0 is resolved as both TRUE and FALSE at the same time. There is absolutly nothing else being called as you can see. Attachment OB1.jpg (95 Downloads)
RAF_Blackace Posts: 13 Rating: (0)
Suggestion To thank Quote Answer
This contribution was helpful to 1 thankful Users Jens_app

5/20/2014 4:52 PM	Rate (0)
Jens_app Gold Member Joined: 1/5/2011 Last visit: 3/9/2023 Posts: 814 Rating: (119)	RAF_Blackace Jens. I have created a new project with only a single call from OB1 followed by a BEU. This calls FB2 that has nothing in it. You can see from the images that the Marker M2345.0 is resolved as both TRUE and FALSE at the same time. There is absolutly nothing else being called as you can see. Hi RAF, thanks for doing that andtaking a screenshot of it. If you did it like that from the start you might had your answer sooner This is most definetely a bug! Here are some suggestions you have probably already tried yourself, but I'm going to say them anyway: -Try recompile/rebuild all -Restarting the software I really hope this issue gets solved. Kinds regards, Jens
	Keep it simple and on-topic. A simple straight-to-the-point answer is often of more quality than a complicated one.
Suggestion To thank Quote Answer

|

Share this page:

Share this page on...

Follow us on