System with CompactLogix L35E and communicating with EthernetIP to I/O racks, drives and HMI. I am seeing intermittent problems with BasicButton controls using monetary set. The click does not always get the PLC. I have done some troubleshooting. Appears that the bit set and reset writes are not always getting thru to the PLC. Did a test adding a new button on screen and counter in PLC with me clicking seems to lose 1 in 10-20 clicks. Mechanical engineer and operators are seeing random problems, sometimes having to click button on screen multiple times to get response.
Do see button text change to "error getting tag" sometimes. This appears to be a related to click actually getting thru to PLC. The button highlight is tied to different tag then click.
Is there any way to detect and handle write failure to PLC? I would not mind adding extra code to buttons, forms to detect lost writes and retry/handle in background.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
If you are using the latest version, there is a property for the BasicButton named MinimumHoldTime. You can try setting it to a higher number such a 1000ms.
Line 280 and 307 in the BasicButton.vb code handle errors with reading/writing. You can modify that code.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I am using latest version. I have tried MinimumHoldTime of 0, 250 and 500. Will try the 1000. My PLC scan time is about 3mSec so I don't need much on time for the tag. In testing I had a indicator showing the tag that was being monetary set. I did see times when the tag would be set but not reset. Did some debug to watch the button code and appears the reset write call happened but did not get to the PLC.
In those referenced lines I see the test for code 1808. Is there a list of other error codes that it can return?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
The error code 1808 is a very specific code from the TwinCAT drivers. When an error comes back from the EthernetIP driver, it should also give a code that can typically be found with an internet search.
If the button released code is not being executed intermittently, that is something controlled by windows. I may have to modify the code to execute the release after a short period of time.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
System with CompactLogix L35E and communicating with EthernetIP to I/O racks, drives and HMI. I am seeing intermittent problems with BasicButton controls using monetary set. The click does not always get the PLC. I have done some troubleshooting. Appears that the bit set and reset writes are not always getting thru to the PLC. Did a test adding a new button on screen and counter in PLC with me clicking seems to lose 1 in 10-20 clicks. Mechanical engineer and operators are seeing random problems, sometimes having to click button on screen multiple times to get response.
Do see button text change to "error getting tag" sometimes. This appears to be a related to click actually getting thru to PLC. The button highlight is tied to different tag then click.
Is there any way to detect and handle write failure to PLC? I would not mind adding extra code to buttons, forms to detect lost writes and retry/handle in background.
If you are using the latest version, there is a property for the BasicButton named MinimumHoldTime. You can try setting it to a higher number such a 1000ms.
Line 280 and 307 in the BasicButton.vb code handle errors with reading/writing. You can modify that code.
I am using latest version. I have tried MinimumHoldTime of 0, 250 and 500. Will try the 1000. My PLC scan time is about 3mSec so I don't need much on time for the tag. In testing I had a indicator showing the tag that was being monetary set. I did see times when the tag would be set but not reset. Did some debug to watch the button code and appears the reset write call happened but did not get to the PLC.
In those referenced lines I see the test for code 1808. Is there a list of other error codes that it can return?
The error code 1808 is a very specific code from the TwinCAT drivers. When an error comes back from the EthernetIP driver, it should also give a code that can typically be found with an internet search.
If the button released code is not being executed intermittently, that is something controlled by windows. I may have to modify the code to execute the release after a short period of time.