I have an Advanced HMI application running my garden watering system. It all works as desired, but whenever the pump runs, the comms to the PLC (Click Koyo using Modbus TCP) drop out until the pump stops. Since the pump only runs for a minute or so every other day, it's not a major drama, but I'd like to get to the bottom of why it's happening - especially since my "stop pump" button doesn't work while the pump is running.
I've ruled out as best I can any physical-level problems - my ethernet infrastructure is very well segregated from the power to the pump, and the pump is just a little single phase DOL unit, so there's no funny business going on with VSD's and interference.
On my main display, there are a few things that happen when the pump starts. There is a water pump object which animates to green. There are some graphics that become visible to indicate watering. There is a basic label which may or may not animate a different colour, depending on which zones are being watered (comms problems exist regardless of which zones are being watered). Various level readings and a tank graphic will update as the tank level changes.
When the pump stops, some VBA runs to log the watering details, which includes data gathered from the PLC. This all happens fine, so apparently the comms come back pretty well immediately once the pump stops.
I'm assuming that there must be some object on the display causing problems when it becomes visible or animates. How might I start trying to track down the culprit? Is there any datalogging/event logging that goes on behind the scenes that I can look at to try and narrow down my search?
