CLICK343CMORE810 (Customer) asked a question.
In the CLICK program I have a test rung with a N.O. contact (controlled by an HMI pushbutton) that does NOTHING other than turn on the OUT coil (which I sometimes choose to be a "Y" output or sometimes a "C" coil).
However the coil does NOT change state when the N.O. contact closes (?).
BUT, if another HMI pushbutton is pressed to turn it ON.... then the original simple rung DOES start working, with the test OUT coil turning on or off correctly.
I have no idea why this is. The 2 HMI pushbuttons are totally unrelated. The OUT coils are not used anywhere else in the program, just used in my test rung.
This is my 2nd CLICK project so I'm not totally new to CLICK. I AM new to this Version 3.92 (and new to the CMORE ver 8.26) so my next move is reverting back to older versions of the software.
Without seeing your ladder logic, I'm guessing the following:
On a rung you have a N.O. contact (C10 for example) controlled by a HMI pushbutton, turning on/off an output (Y100 for example).
Then on a second rung, below the first rung, you have another N.O. contact (C11 for example) controlled by another HMI pushbutton, turning on/off the same output (Y100 for example).
If this is true, then you should expect the behavior you described. The output Y100 will be controlled by the last command it receives. So even though C10 is closed, calling for Y100 to be on, Y100 will still be off, because the last command is calling for Y100 to be off by the C11 open contact.
If you place C10 and C11 in parallel, in the same rung, then have those parallel contacts control Y100, you should get the behavior you are looking for. You should not have to revert back to older software versions. Does this work as expected?
That makes sense, but in my logic the Y output (or C coil... it happens with either) appears in only 1 place in the entire program, in 1 rung, and is controlled by 1 NO contact (like "C10").
I'll mention something I think is unrelated; the HMI shows PLC-499 error from the PLC, hex code 2. Which appears to be a communications error... related to ETHERNET I believe (and not serial). I was trying to communicate via ethernet originally, but then am communicating via the COM2 serial port currently. This "should" have nothing to do with my ladder issue... but I can not eliminate the PLC-499 error and who knows, maybe it is involved somehow. I deleted the ethernet COM information on the HMI side and "turned off" (unchecked checkboxes) ethernet settings in the CLICK PLC, so not sure why I get the PLC-499. Maybe I should start over from factory settings. :)
It is so easy to misunderstand. "BUT, if another HMI pushbutton is pressed to turn it ON...", I thought this meant you had (2) contacts controlling the same output (Y or C). Perhaps it would help if you could post a screen print of the ladder code in question.
But, yes, you should correct your communication error. Again, if I understand correctly, your error code indicates a Modbus "Illegal Data Address". Check your communications settings in both the HMI and PLC. Of course, there is always ADC tech support, which they are great.
Double check the Cmore Tag database. You may have miss assigned your inactive pushbutton. (Easy mistake, taken from personal experience)
What is the C-More Pushbutton Object Type? It can be:
Toggle: Each press alternately writes a "1" or a "0" to the bit.
Momentary On: Each press writes a "1" then after a delay on the options tab writes a "0".
Momentary off is the same but swap the "1" and "0" in the description above.
Set On or Set Off simply writes a "1" or a "0".
None of these buttons should continue to operate on the tag once their actions have completed.
That last option is probably the best for a Boolean tag and avoids "stuck button syndrome" where one or more of the events gets dropped for any number of reasons. The Set option performs a single write and then you have the PLC handle resetting the tag back to its normal state after it recognizes the button press and takes action.