Re: [Qscada-developers] R: Document templates

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

Jovan Kostovski wrote:
> Hi,
> 
> I'm really late with this reply, but better ever then never :)


I agree with you on every issue. I'm willing to defer to the
group, 99%, and you can decide when you want the (1%)....

What my fear is that we need to start coding and get something
going. If not, we in danger of loosing are small membership.


Maybe we can start by resurrection of Paolo's original code
so we can get something that should work up on the Net.
At that point I can begin interfacing hardware for this
small group (lightweight security).

Then coding and testing can begin? We'd have something
to show others, some 'eye-candy' and live over the net
demo.


> At the end, I would share some book links with you
> (they are pairs name- download location):
> 
> "Practical Process Control for Engineers and Technicians" by Wolfgang Altmann
> http://rapidshare.com/files/2333374/Newnes.Practical.Process.Control.for.Engineers.and.Technicians.eBook-TLFeBOOK.rar
> 
> "Securing SCADA Systems" by Ronald L. Krutz
> http://rapidshare.com/files/5092980/Wiley.Securing.SCADA.Systems.Nov.2005.eBook-DDU.pdf
> 
> "Practical Data Acquisition for Instrumentation and Control Systems"
> http://rapidshare.com/files/7680226/e0750657960.pdf
> 

These are wonderful resources. The third one seems centric on A/D and
digital signals directly entering a PC, which is good, but a well
worn path. What I need is a reference to show how to put modbusTCP
onto a microcontoller (hacking a stack now) and then transmit
the modbusTCP packets to a Linux host, which is running the Qscada
daemon (endless polling loop). Then how do you pump the data
into a simple (QT based) gui. I think if we figure this out
vendors and hardware hackers will feel inclined to participate
with us. At that point, some will be coder and get involved
in fixing or developing modules to add to Qscada.

Once we get a skeleton working, maybe we can just continue
to refine the paradigm (Qscada)?



Paolo is too busy right now. Anybody else want to take the lead
for a while?  I'll be your slave! I just do not know QT, nor
how to architect the over the net data transmission.

ModbusTCP, should be our first knockoff, in my option.....
After all it's the most widely used network controls protocol.

We need to get started, or this project's going to die.....

James