Evento de perda de comunicação – Rapid SCADA 6.2.2

Forum Home Forums Communicating with Devices Modbus Evento de perda de comunicação – Rapid SCADA 6.2.2

Viewing 15 posts - 1 through 15 (of 17 total)
  • Author
    Posts
  • #17664
    isabellacog
    Participant

    Boa tarde,

    Estou utilizando o Rapid SCADA versão 6.2.2.0 e gostaria de esclarecer uma dúvida relacionada à geração de eventos de perda de comunicação com dispositivo.

    Estou utilizando conexão via Modbus TCP e observei que, quando o dispositivo deixa de receber dados, os valores das tags ficam exibidos em cinza claro na tabela. No entanto, não identifiquei claramente como configurar a geração de um evento específico para indicar a perda de comunicação.

    Minha dúvida é:

    Existe alguma função ou configuração nativa na versão 6 para gerar automaticamente um evento quando o dispositivo ficar offline, ou é necessário implementar alguma lógica adicional (por exemplo, via script ou expressão)?

    Poderiam, por gentileza, me orientar sobre a melhor prática recomendada para esse tipo de monitoramento?

    Desde já agradeço o suporte.

    #17665
    manjey73
    Participant

    There is a Status service tag for devices in the Communicator. This is probably the best solution.

    #17666
    isabellacog
    Participant

    Where can I find the ‘status’ service tag in the Communicator? I can’t find it.

    #17667
    manjey73
    Participant

    Just manually create an input channel in the device with the Status tag code in the database. Channel value 0 = Normal, 1 = Error

    #17668
    isabellacog
    Participant

    How would the formula look like? I tried this one, but it didn’t work: CnlStat == 0 ? 1 : 0.

    #17669
    manjey73
    Participant

    The formula is really weird and seems useless. What exactly do you want to do with the channel data?

    #17670
    isabellacog
    Participant

    This is a supervisory system for an operations center. So, when my device stops communicating, I need an alarm for that. If the formula is strange or incorrect, please show me the correct one. Otherwise, I would appreciate your help in clarifying it.

    #17671
    Mikhail
    Moderator

    Hello,
    Just create a new channel of the Calculated type, and set the Tag Code field to Status
    The device field of the channel should refer to the certain device.
    Then upload the project changes and check value of the newly created channel.
    Provide a screenshot of your settings if it doesn’t work.

    • This reply was modified 12 hours, 51 minutes ago by Mikhail.
    #17673
    Mikhail
    Moderator

    Using formula CnlStat > 0 ? 0 : 1 is also possible. But the method described above is simpler.

    #17677
    isabellacog
    Participant

    Channel
    Table

    I did what you suggested. I created a new channel of the calculated type and set the tag code field to status. Now it is returning the value 1, but the device is off, so it should be returning 0, correct? Can you verify if I did something wrong?

    #17679
    manjey73
    Participant

    Status works differently, if it returns 1, it means an error. There is a Normal-Error Format for this.

    #17680
    isabellacog
    Participant

    channel configuration
    status device
    value statustable view

    The value of the channel status is not changing, and I can see in Device 1 that my device is changing in reality. Did I make any configuration mistake?

    #17681
    manjey73
    Participant

    21 – Input, data type – double or empty
    Formula (script) none
    Format – Normal-Error in table Normal; Error

    #17682
    isabellacog
    Participant

    ble view” />
    I followed the steps, but it seems that the value of channel 21 stopped updating along with the other values when the device stopped communicating. I removed the ‘Normal-Error’ format just to observe which value would appear.

    #17683
    manjey73
    Participant

    Show the channel settings with the Status tag again

Viewing 15 posts - 1 through 15 (of 17 total)
  • You must be logged in to reply to this topic.