Inrush Current Not captured in trend

[azami]

Hello Support,

I am facing one issue that, motor starting current  (Inrush current) is not captured by online/archive trend. Please support on this.
Communication over modbus tcp.
Used zenon-7.20
Win7 professional

[ursulak]

Maybe contact your local COPA-DATA Support (Forum is not Support ) and describe the issue well. From "motor starting current is not captured" is not possible to guess what is going on.
It does not look like an Energy-specific topic, thus you have better chance to get fast answer if you would post in a thread for Supervisor or drivers.

[markclemens]

Hi Azami,

Does the value for the variable have a SPONT status or does it have an INVALID status?

The Modbus TCP protocol does not support spontaneous communication. A Modbus master must cyclically send read requests in order to get the data. When the value of the inrush current is available in the Modbus slave only for a short time period, it may be that the value has dropped again when the next cyclic read request is due. In zenon you can configure the driver global update time down to 100ms (default is 1000ms).

Best regards,
Mark

[azami]

Thank you Mark,

I got the solution, cycle time was very high.

Hi Azami,

Does the value for the variable have a SPONT status or does it have an INVALID status?

The Modbus TCP protocol does not support spontaneous communication. A Modbus master must cyclically send read requests in order to get the data. When the value of the inrush current is available in the Modbus slave only for a short time period, it may be that the value has dropped again when the next cyclic read request is due. In zenon you can configure the driver global update time down to 100ms (default is 1000ms).

Best regards,
Mark