Re: [Qscada-developers] Exciting news

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

Jovan Kostovski wrote:
> Hi,
> 
> HATS DOWN for you James.
> So many great ideas.
> 
> 
> 
>>On 11/10/06, wireless <wir...@ta...> wrote:
>>Jovan: have you guys  what tools/languages we should all install, to
>>work on Qscada?   I need this info to begin recruiting coders and
>>testers.
> 
> 
> At first glance we need:
> 
> 1. C/C++ I/O programming (serial port, parallel port, usb, IR ...)
> 2. C/C++ for industrial protocol programming (Modbus, CANBus, some PLC
> protocols...)
> 3. C/C++ Linux Kernel programming - for drivers for external devices
> (microcontrollers, PLCs...)
> 4. C/C++ QT GUI designers for design time and runtime GUI (examination
> of some scada systems is must: WonderWare Intouch and alike)
> 5. C/C++ QT widget programmers for widget libraries. We must create a
> template for the widget
> 6. C/C++ network and network security programmers
> 7. Web programmers (AJAX, XML, PHP, XHTML) for web based clients
> 8. Some pople with knowledge of linux embedded systems (RTAI, RTLinux...)
> 9. Database developers MySQL and PostgeSQL
> 
> That's all that I can think of for now. 

Good list Jovan. Maybe Iain can parse these email messsages
for such information and put in the web pages to attract folks?

> I'll have to do better
> analysis. I hope I'll do
> that by the and of the week, but first we have to disccuss about the structure
> (building blocks) of QScada.

Yes, I getting ready to take some time off from work. QScada is going to
receive the majoring of my time.... Once I finish the draft(very crude)
for hardware issues, I'll send it to the group. At that point, I'll be
ready to discuss organization and the building blocks. Look for an ugly
first draft soon. I'm not spending anytime on making it pretty, only
content. We can develop a template document  for all future documents
to use. That wany somebody can just fire up openoffice and a template,
stick content into it, and present it back to the group......?
Likewise, if you include revision numbers, others can check out the docs
add material for discussion and then the group(leader?) can make the
final edits? It's be iterative.

>>we need a software oriented person (Jovan?)
> 
> Hey! I want to play with wires to :)
> It's fine by me if I'll be the software guy, but I'll
> play with hardware too ;)

Once the architecure is finished, there will be lots
of hardware, and wires for all to play with. Once we
figure out the configuration and make it secure, I'm quite
certain other will build hardware playgrounds too....

> 
> 
> 
>>I'll be the hardware guy
>>building an online playground for folks to hang out and articulate
>>QScada with actual hardware

I'm not going to be the only hardware guy. It's just I have
a facilty and much equipment already. What I build will become
available for us to use, attract new members and eventually,
others will be encourage to put up 'online labs' too.
It's just expensive.....

> This is great idea. I see that you have good equpemnt.
> You should setup a QScada server and the clients will access
> remotely. It would be nice if there are cameras for every actuator so
> that the real life effects can be seen. The camera can send
> series of consequtive pictures or live stream video. The prblem
> would be colision in controls (two or more clients are accessing
> the same device)


Yes, Yes, we are very big on H.264 here. As soon as possible, when Iain
has an ebuild ready, I'll be the first to test install QScada(?)....
Portage overlay? I have some good links on creating ebuilds.....but,
they are easy to find with google.


>>we can put up QScada for google funding it as a 'Summer of Code' opportunity.
> 
> Another one!
> That's all for now.
> Be well, Jovan

James