LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

SCADA Sample Project doesn't transmit alarms

Solved!
Go to solution

The behavior for some DSC Alarm APIs had been there for multiple releases, that it will use Computer Name instead of IP address to filter in the Alarm cache. So, I will say this is at least an unexpected behavior for the customers.

Message 11 of 16
(307 Views)

Thank you for your help and explanations, YanYuan. The issue is much clearer now, and you've given us a good workaround.

 

Yes, it's unexpected. Is this documented anywhere?

 

We usually use Network Published Shared Variables (NSVs) as our interface to DSC features. Most features of the NSVs can be accessed through either computer name or IP address. However, with alarms on shared variables, it looks like IP addresses are not supported. This combination is counter-intuitive.

 

Would NI be willing to make changes to the system?

  • Ideally, alarming would work seamlessly when the remote computer is specified by IP address -- the DSC could resolve IP address to hostname behind-the-scenes for filtering
  • If that's not feasible, we should at least get a warning message from DSC to say that the IP address is not recognized by the alarms system

Certified LabVIEW Developer

0 Kudos
Message 12 of 16
(286 Views)
Solution
Accepted by topic author JKSH

Yes, this issue is tracked by NI CAR system, and the fix for that will be prioritized in future releases. Thanks.

Message 13 of 16
(283 Views)

Great! Could you share the CAR number please?

Certified LabVIEW Developer

0 Kudos
Message 14 of 16
(272 Views)

CAR 461470

 

Message 15 of 16
(264 Views)

Thank you again, YanYuan!

Certified LabVIEW Developer

0 Kudos
Message 16 of 16
(256 Views)