Issues regarding module function testing when studying the CS3000 system*
Thread Content
1. I defined three variables in the %SW interface, then called the LC64 function block in DR0002 and performed a simple AND logic operation there: %SW0401.PV.ON was ANDed with %SW0402.PV.ON, and the result was output to %SW0403.PV.H. However, when I used the Test function to access the faceplates of %SW0401 and %SW0402 and pressed the on button, the PV values for %SW0401 and %SW0402 on those faceplates became 1, but the values displayed on the logic diagram monitoring screen remained 0. The PV value for %SW0403 also did not change and stayed at 0.2. I didn’t use any external devices for testing; instead, I utilized the MC-2E module to control a valve and obtain feedback on its status. During testing, when the button to open the valve was pressed, a signal indicating that the valve was open was received, and the PV value also changed to 2. In other words, both the command to operate the valve and the feedback were normal. Since I wasn’t using any external devices, and I also tried searching by name to find any intermediate logic circuits, I’m not sure why this is happening
1. Would it be better to write %SW0401 and %SW0402 as PV.1? 2. This is simulation
1. I tried using %SW0401.PV.1 as well, and the result was the same: the PV value on the faceplate of %SW0402 changed to 1, but the value shown on the logic diagram monitoring screen remained 0. Is it necessary to download anything when working with the test function? Because when I built this logic on top of projects already created by others and then created a test function, everything worked fine; but when I started a new project and applied this simple logic, I encountered this problem. 2. I didn’t connect the device, so there should be no feedback signal. Testing refers to functional testing, and a signal can be generated manually. I created a new MC-2E module again, connecting only the inputs and outputs; without any other logic, there was no feedback signal, so no alarm was triggered. Because what I opened was a project created by someone else, and this issue occurred; it’s probably because there was some logic involved in it that I just couldn’t find.
The first one is the newly created LC64 block, which is in manual mode. Play automatically. I don’t know the second one
The second simulation state is like this
I created a new MC-2E module based on the original project, connected it with two inputs and two outputs for testing, and an alarm was triggered; it shouldn’t be due to simulation issues.