From: Jovan K. <cho...@gm...> - 2006-11-13 23:21:24
|
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. 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. > 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 ;) > I'll be the hardware guy > building an online playground for folks to hang out and articulate > QScada with actual hardware 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) > 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 |