From: Jovan K. <cho...@gm...> - 2006-11-16 00:25:47
|
Hi, Great to hear from you Paolo. On 11/15/06, wireless <wir...@ta...> wrote: > On anther note, I rather like Jovan quite a lot. He's very up_tempo > and crazy_maniacs like myself need a good rudder, now and then. Thanks for the complinents :) > Besides, we both agree on pushing the RT needs as close to the > remote hardware as possible. Yes that's right. In some situations we can solve the RT problem by adding two timestamps to the data, one would be the time that the event has occured set by the RTU, and the other would be the time when it has arrived on QScada server, set by the QScada server. That way we'll have the exact time when the event has occured and when it was registered/logged by QScada. > Besides, on the Qscada server end, I'm leaning more to > "openmosix" as a cluster, to provide High Availabilty for QScada. good point > Those companies that do not get on board with Qscada will > have their "proprietary portocols" reverse engineerd so they will be > compatible without consent/control of their destiny..... We don't have to reverse engineer those protocols. If we do that we can not garantee that the protocol is working correctly. I think the best way is those proprietary protocols to be written by the companies themselves and to be given to us as compiled plugins that can be added to QScada. A concept similar to what NVidia is doing with the Linux drivers for their graphic cards. GREETZ, Jovan |