This is the one of solutions for shure. I am wondering why the quality handling is not consistant through all of Lookout objects?
This method impose a lot of work for developers.
Just imagine that some critical actions in your application depend on quality processing. You need to process data and quality separately for each one connection. If you have more of I/O points like that and use more Lookout clients in your application it is a huge work to implement quality processing correctly and the posibility of error is high. Also, you have to implement the display of quality (red X) for each of that signals to.
I am not shure that whole idea of quality is to double the work for developers. It would be more convinient that quality information is propagated to
gether with data through all of Lookout objects and clients. This is automaticly provided just in case that you use use driver I/O points directly in expresions. Other objects don't use and propagate quality information at all. Furthermore, the end user could have more information about process that he controls:
- comm filure
- sensor filure
- network status
etc.
Maybe someone from NI could tell us more about this? Why the most of the objects don't use quality?
When this would be provided?
Alan Vrana
Alan Vrana
SCADA Projekt d.o.o.
ZAGREB, Croatia