Re: [Qscada-developers] Excellent controls web site

[wireless <wir...@ta...>]

Gentoo Linux Documentation -- Jovan Kostovski wrote:

>Hi,
>
>On 10/25/06, wireless <wir...@ta...> wrote:
>  
>
>>A complete machine (lathe) using RTlinux, postgresql, etc etc.
>>
>>http://www.linuxjournal.com/node/7662/print
>>
>>Maybe some of these guys listed at the bottom of the list are interested
>>in QScada?
>>    
>>
>
>Yes they might be interested, but from a user point of view. They might tell
>us some interesting features to be implemented.
>
>  
>
My goal in this (ADD) document is to highlight work that is related and
if possible we could design hooks into QScada for compatibility
or at the least gleaning the useful features from these efforts.
Others such as 'comedi' are more fundamental in nature to QScada.
Once I flip it (ADD) over to the  group, others would be encourage to
comment or edit the docs.  As an employee at a company that has
developed lots of embedded systems (products) the ones that are the
most successful, are the ones that have excellent specifications. The
best way to minimize costs (maximize potential) is to have a robust
specification *BEFORE* coding begins, in my experience. YMMV.

>Usualy RTLinux and RTAI (https://www.rtai.org/) are used to build embedded
>linux devices that work in real-time. RTAI has a lot more features and supports
>more devices.
>Here is a link with a comparison of them:
>http://rtportal.upv.es/comparative/rtl_vs_rtai.html
>
>I don't think that in this stage we should delve into RTLinux or RTAI.
>They are used for embedded devices that are used the field devices and
>controllers.
>
>  
>
Amazing! We agree. Push RT performance requirements down to the
lowest level.  I do agree that we do not have to 'delve' into RT
issues, in depth, at this time, but, creating a high level document so we
can be sufficiently organized that when that (RT) time comes, we have
something (a stub) for folks to work from.

>Maybe we can use them in the future as RTUs that will some light
>version of QScada, drivers for field devices, some small db (because
>of the limited resources) and a web server.
>
>
>I'm currently working on a document that defines the procecess
>(reading/writing data, stroing data, reporting, udpating the visual
>picture) that are part of QScada. I hope
>I'll finish it by the end of next week.
>
>
>  
>
Excellent. When these 'early docs' are completed, somebody will
need to get us little people (like me) organized so we can begin
to contribute code.    My previous email on which software and
which versions will help the group stay compatible, at least
in the early efforts. I've picked up a book on Java and starting
some simple coding. QT is another area where I could use
a good book && examples to get a feel for QT.... Suggestions?

>>WE should all bear in mind that as we begin to code
>>and deploy QScada, these high level documents will evolve with the
>>project.
>>    
>>
>
>I agree with you completely. It is crucial to share the ideas.
>
>GREETZ, Jovan
>
>-------------------------------------------------------------------------
>Using Tomcat but need to do more? Need to support web services, security?
>Get stuff done quickly with pre-integrated technology to make your job easier
>Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
>http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
>_______________________________________________
>Qscada-developers mailing list
>Qsc...@li...
>https://lists.sourceforge.net/lists/listinfo/qscada-developers
>
>  
>