Showing results 1 to 4 of 4

Thread: Inrush Current Not captured in trend

  1. #1

    Default Inrush Current Not captured in trend

    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

  2. #2
    Join Date
    01.07.2008
    Location
    Salzburg, AT
    Posts
    808

    Default Re: Inrush Current Not captured in trend

    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.

  3. #3

    Default Re: Inrush Current Not captured in trend

    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

  4. #4

    Default Re: Inrush Current Not captured in trend

    Thank you Mark,

    I got the solution, cycle time was very high.



    Quote Originally Posted by markclemens View Post
    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


Similar Threads

  1. Current alarms and number of invalid
    By Jabbl in forum zenon Supervisor
    Replies: 0
    Last Post: 17th January 2018, 08:52
  2. Replies: 2
    Last Post: 10th March 2017, 04:47
  3. Alarm message compare with current Date
    By navaneet in forum zenon Supervisor
    Replies: 6
    Last Post: 17th November 2014, 13:24
  4. Sending current values via e-mail
    By tihomir in forum zenon Supervisor
    Replies: 3
    Last Post: 17th February 2014, 09:30
  5. Current user in header section of the project
    By yolovs in forum zenon Supervisor
    Replies: 2
    Last Post: 31st July 2013, 10:02

Posting Rules

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •