Menu
▾
▴
qscada-developers — Developers Mailing List
You can subscribe to this list here.
| 2006 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(9) |
Nov
(32) |
Dec
(10) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2007 |
Jan
(7) |
Feb
(3) |
Mar
(17) |
Apr
(3) |
May
(1) |
Jun
|
Jul
(1) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Jovan K. <cho...@gm...> - 2007-01-17 00:22:09
|
Hi, On 1/16/07, wireless <wir...@ta...> wrote: > > Ok Jovan, please let me know if you want to start working as >> the P.L. for QScada. > > I second the motion, JOVAN, you've just been elected! OK, what must be done, must be done :) I'm taking the P.L role. Paolo you will get back the conductor wand whenever you say. I would like to hear from all of the people on the list how we should develop this project, what are our short term and long term objectives and who is willing to do what. We need to create a roadmap for the project. My opinion is that as short term goal we have to create some demo application, "the eye candy" as James said (it doesn't have to be anything complicated), so that we have something to show to the public and atract more people to join us. Parallel on that we have to finish the work on the architecture of QScada, define and document in detail what are we doing and how we'll do it. Paolo I would like you to tell us your vision and share the the plans that you've made so far, so we can start biulding up on the base that you've made. This goes for the rest too. What ever you want to say you can say it and we'll discuss it here on the list. But you should know that "The boss is not always right but the boss is always the boss" :) Just joking, I'm always opened for propositions, from time to time I might run to fast and be stubborn but feel fee to slap me and get me back to reality ;) > My time is limited, but, I can manage 10-20 hours per week, with > some bursts here and there. James 10-20 hours per week are half week working time. That is great contribution > I'm all that familiar with QT, so where are some materials > and examples that I can look at? I'll try to find something and send some links, but please tell me what kind of materials and examples are you looking for. General QT programming, Low level port programing..... This came really suddenly for me, I'll try to give my best and I hope I won't disappoint you. GREETINGS, Jovan |
|
From: wireless <wir...@ta...> - 2007-01-16 17:21:55
|
Paolo Sereno wrote: > Hi, > I=B4m also late in answering... > That=B4s the reason why I=B4m writing to you Jovan and to the whole gro= up. > Few months ago I changed my job and I see, the new job and the new duti= es=20 I have are really heavy. > I thought a lot during the last w-e and I decided to ask you, Jovan,=20 to take the leadership of QScada. > You are really good willing, you have good ideas and experience=20 and I see, you made a lot during the last month for QScada. That=B4s the reason why I=B4m asking you this. > Obviously I won=B4t disappear, I always be here and when my=20 new job will allow me, I will give my contribution, but I think, for the next six months I will do a little for QScada, unfortunately. > Ok Jovan, please let me know if you want to start working as=20 the P.L. for QScada. I second the motion, JOVAN, you've just been elected! Drop me a line, with some tasks, or just post them here. OK with me. Project lead or project steed, I'm ready to get cranking. My time is limited, but, I can manage 10-20 hours per week, with some bursts here and there. I'm all that familiar with QT, so where are some materials and examples that I can look at? > I also want to thank James for the useful ideas and the help he brought to me during the entire project. Yea sure Paolo; Iain is my hero (he always helps me with Gentoo, when nobody's looking...) That said, I finally have enough machines to build a network for Qscada. > As I said, I will be always here, but I can=B4t have enough=20 time for working as a good project leader. > Thank you and take care > paolo Everything will be coo..... James |
|
From: Paolo S. <pao...@ya...> - 2007-01-15 08:08:16
|
Hi,=0AI=B4m also late in answering...=0AThat=B4s the reason why I=B4m writi= ng to you Jovan and to the whole group.=0AFew months ago I changed my job a= nd I see, the new job and the new duties I have are really heavy.=0AI thoug= ht a lot during the last w-e and I decided to ask you, Jovan, to take the l= eadership of QScada.=0AYou are really good willing, you have good ideas and= experience and I see, you made a lot during the last month for QScada. Tha= t=B4s the reason why I=B4m asking you this.=0AObviously I won=B4t disappea= r, I always be here and when my new job will allow me, I will give my contr= ibution, but I think, for the next six months I will do a little for QScada= , unfortunately.=0AOk Jovan, please let me know if you want to start workin= g as the P.L. for QScada.=0AI also want to thank James for the useful ideas= and the help he brought to me during the entire project.=0AAs I said, I wi= ll be always here, but I can=B4t have enough time for working as a good pro= ject leader.=0AThank you and take care=0Apaolo=0A=0A=0A----- Messaggio orig= inale -----=0ADa: Jovan Kostovski <cho...@gm...>=0AA: qscada-develope= rs...@li...=0AInviato: Sabato 13 gennaio 2007, 15:13:24=0AOgge= tto: Re: [Qscada-developers] R: Document templates=0A=0AHi,=0A=0AI'm really= late with this reply, but better ever then never :)=0A=0AOn 12/13/06, wire= less <wir...@ta...> wrote:=0A> Some mechanism to archive the do= cument before the given revision=0A> are made, should be simple to establis= h.=0A=0AWe don't have to care much about that. We will use some versoning s= istem,=0AI prefer SVN, which will take care about that. That way we can mai= ntain our=0Acode easy without getting our hands dirty. Different file versi= ons, backups,=0Arestoring files it's all there.=0A=0AI don't have much to s= ay about the coding style. I'm completely flexible,=0Aso whatever we make a= s a standard I will obey.=0AI like the rules that are shown in the document= sent by Paolo=0Aand I program with some simmilar rules.=0AI agree with Ian= about the underscores, I don't like them too.=0AThe coding style can be ar= ea specific but we should avoid to many=0Aspecific areas.=0A=0A=0A=0A > Doc= uments:=0AI agree that document templates can be tricky, but if we all agre= e=0Ato use this program with that font, or if we create so,e template=0Athe= re shouldn't be any problems.=0A=0A>Alternatively, I can just submit conten= t in some agreeable form=0A>and somebody can put the content into a templat= e form?=0A=0AThis can be one good solution, but the drawback is that someon= e=0Awill have to do the DTP fo the others. As the projects grows, sooner=0A= or later we'll have get a Documentation guy/team, so this would be=0Aa logi= cal solution.=0A=0AAt the end, I would share some book links with you=0A(th= ey are pairs name- download location):=0A=0A"Practical Process Control for = Engineers and Technicians" by Wolfgang Altmann=0Ahttp://rapidshare.com/file= s/2333374/Newnes.Practical.Process.Control.for.Engineers.and.Technicians.eB= ook-TLFeBOOK.rar=0A=0A"Securing SCADA Systems" by Ronald L. Krutz=0Ahttp://= rapidshare.com/files/5092980/Wiley.Securing.SCADA.Systems.Nov.2005.eBook-DD= U.pdf=0A=0A"Practical Data Acquisition for Instrumentation and Control Syst= ems"=0Ahttp://rapidshare.com/files/7680226/e0750657960.pdf=0A=0A=0A=0ATake = care, Jovan=0A=0A----------------------------------------------------------= ---------------=0ATake Surveys. Earn Cash. Influence the Future of IT=0AJoi= n SourceForge.net's Techsay panel and you'll get the chance to share your= =0Aopinions on IT & business topics through brief surveys - and earn cash= =0Ahttp://www.techsay.com/default.php?page=3Djoin.php&p=3Dsourceforge&CID= =3DDEVDEV=0A_______________________________________________=0AQscada-develo= pers mailing list=0AQ...@li...=0Ahttps://lists= .sourceforge.net/lists/listinfo/qscada-developers=0A=0A=0A=0A=0A=0A=09=0A= =0A=09=0A=09=09=0A___________________________________ =0AVinci i biglietti = per FIFA World Cup in Germania! =0Ayahoo.it/concorso_messenger |
|
From: wireless <wir...@ta...> - 2007-01-13 17:07:17
|
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 |
|
From: Jovan K. <cho...@gm...> - 2007-01-13 14:13:27
|
Hi, I'm really late with this reply, but better ever then never :) On 12/13/06, wireless <wir...@ta...> wrote: > Some mechanism to archive the document before the given revision > are made, should be simple to establish. We don't have to care much about that. We will use some versoning sistem, I prefer SVN, which will take care about that. That way we can maintain our code easy without getting our hands dirty. Different file versions, backups, restoring files it's all there. I don't have much to say about the coding style. I'm completely flexible, so whatever we make as a standard I will obey. I like the rules that are shown in the document sent by Paolo and I program with some simmilar rules. I agree with Ian about the underscores, I don't like them too. The coding style can be area specific but we should avoid to many specific areas. > Documents: I agree that document templates can be tricky, but if we all agree to use this program with that font, or if we create so,e template there shouldn't be any problems. >Alternatively, I can just submit content in some agreeable form >and somebody can put the content into a template form? This can be one good solution, but the drawback is that someone will have to do the DTP fo the others. As the projects grows, sooner or later we'll have get a Documentation guy/team, so this would be a logical solution. 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 Take care, Jovan |
|
From: wireless <wir...@ta...> - 2007-01-03 21:22:48
|
Iain Buchanan wrote: > Hi again, its the occasion-poster here :) >=20 > On Wed, 2006-12-13 at 04:22 -0800, Paolo Sereno wrote: >=20 >>Hi all, >> >>thank you for your effort and your ideas. I=B4m honoured to work with >>you all. >> >>Talking about coding convention, I=B4d like to invite you to consider >>something like this >>http://www.cs.rice.edu/~dwallach/CPlusPlusStyle.html >=20 >=20 > Hmm, personally I don't like _some_ of the ideas here - such as its..., > their..., the... >=20 > at work, we use a similar style, with the type of variable / object > preceding it's name, like: >=20 > unsigned short usSomeVar; > int iSomeVar; >=20 > class CoolClass; >=20 > CoolClass oInstance; // o is for object! >=20 > and function names are FirstLetterCapitals or name_with_underscore. >=20 > I personally believe coding styles should be specific in some areas, bu= t > general in others. Specifics include tab widths, or "no tabs"; loop > structure, names, etc, but with a general neatness in layout. >=20 > Making the code easy to read and look "nice" can sometimes override the > coding style. >=20 Well, as I stated, I'm flexible, and maybe we should look, as a group at some more specific examples? Maybe Paolo could offer up some exiting code that he plans to use with Qscada, and we can all hash this out until we are agreeable? >=20 >=20 >>Documents: >=20 >=20 > Making templates can be tricky, given different fonts, sizes, programs, > etc. Perhaps we could provide a latex template for people to edit, and > just some font names and sizes to use for *-office programs. Maybe we > give an example front page, and table of contents, then after that it's > up to the author... Agreed. But, I for one am going to look at some of the existing/earliest documents and try to conform as much as possible to what the most prolific author(s) create. That said, does the form of the documents affect how we will publish the docs on the web (Doxygen, XML, etc etc) or will these just be a collection of pdf/doc/ascii files that are downloaded? No hart_burn either way, just curious. thoughts? James |
|
From: Iain B. <ia...@ne...> - 2007-01-02 03:39:48
|
Hi again, its the occasion-poster here :) On Wed, 2006-12-13 at 04:22 -0800, Paolo Sereno wrote: > Hi all, >=20 > thank you for your effort and your ideas. I=C2=B4m honoured to work wit= h > you all. >=20 > Talking about coding convention, I=C2=B4d like to invite you to conside= r > something like this > http://www.cs.rice.edu/~dwallach/CPlusPlusStyle.html Hmm, personally I don't like _some_ of the ideas here - such as its..., their..., the... at work, we use a similar style, with the type of variable / object preceding it's name, like: unsigned short usSomeVar; int iSomeVar; class CoolClass; CoolClass oInstance; // o is for object! and function names are FirstLetterCapitals or name_with_underscore. I personally believe coding styles should be specific in some areas, but general in others. Specifics include tab widths, or "no tabs"; loop structure, names, etc, but with a general neatness in layout. Making the code easy to read and look "nice" can sometimes override the coding style. > Documents: Making templates can be tricky, given different fonts, sizes, programs, etc. Perhaps we could provide a latex template for people to edit, and just some font names and sizes to use for *-office programs. Maybe we give an example front page, and table of contents, then after that it's up to the author... cya, --=20 Iain Buchanan <iaindb at netspace dot net dot au> "If you want to travel around the world and be invited to speak at a lot of different places, just write a Unix operating system." (By Linus Torvalds) |
|
From: wireless <wir...@ta...> - 2006-12-26 15:56:42
|
Jovan Kostovski wrote: > Dear Friends, > I WISH YOU MARRY CHRISTMAS AND A HAPPY NEW YEAR !!! > ALL THE BEST IN 2007. > I WISH ALL YOUR WISHES TO COME TRUE. Right back at you with a happy_happy and a merry_merry..... > Hope we'll make it to QScada's first release and > finish the year with at least v0.3 Well just let me know as I was curious when we were going to be ready to put a 'das blinkenlights' up on the net: (digital led version of hello world) > May the SCADA control be with us :) may the 'schwartz' be with you (vintage Mel Brooks aka Spaceballs) > GREETINGS, Jovan James |
|
From: Jovan K. <cho...@gm...> - 2006-12-24 16:35:21
|
Dear Friends, I WISH YOU MARRY CHRISTMAS AND A HAPPY NEW YEAR !!! ALL THE BEST IN 2007. I WISH ALL YOUR WISHES TO COME TRUE. Hope we'll make it to QScada's first release and finish the year with at least v0.3 May the SCADA control be with us :) GREETINGS, Jovan |
|
From: Jovan K. <cho...@gm...> - 2006-12-24 16:27:50
|
Hi, On 12/24/06, wireless <wir...@ta...> wrote: > Hello One and all, > > Anyone know of any modbusTCP stacks around where I can set up a master > on linux, just to test a modbusTCP implementation on a MicroChip 18F chip? Here are some links that I found around the net. Don't know if they will be useful to you but they might be a good starting point http://mat.sourceforge.net/ - MatPLC http://mbus.sourceforge.net/ - MODBUS/TCP to MODBUS/RTU gateway server I hope you can find some useful routhines there. > Everyone's been quiet.... Yes it's quiet :) I've been quite busy, still haven't replied on your last mail (need to "play around" a bit before I make some conclusions about the sourse management. probably it will al be handeled by svn) and the mail about the documentation templates. These two things are in my agenda for this year, but you never know :) GRETZ, Jovan |
|
From: wireless <wir...@ta...> - 2006-12-24 04:56:08
|
Hello One and all, Anyone know of any modbusTCP stacks around where I can set up a master on linux, just to test a modbusTCP implementation on a MicroChip 18F chip? Everyone's been quiet.... Jovan? Paolo? Iain? Am I the only one left? Anyone else still in this group? James |
|
From: wireless <wir...@ta...> - 2006-12-23 05:49:21
|
Check out this link.... http://pvbrowser.de/pvbrowser/index.php http://pvbrowser.org/pvbrowser/index.php?menu=1&topic=1&subtopic=3 |
|
From: wireless <wir...@ta...> - 2006-12-23 05:00:55
|
<http://modbusfw.sourceforge.net/> |
|
From: wireless <wir...@ta...> - 2006-12-13 17:53:38
|
Paolo Sereno wrote: > Hi all, >=20 > thank you for your effort and your ideas. I=B4m honoured to work with y= ou all. >=20 Hello Paolo, > Talking about coding convention, I=B4d like to invite you to consider s= omething like this > http://www.cs.rice.edu/~dwallach/CPlusPlusStyle.html It looks reasonable to me. If after we start coding it does not address a particular need, we can discuss that need, modify the scheme (document) and move on. I like the structured approach, as long as we can discuss and update our guiding docs, once we are in agreement. So that's a YES vote. > Source structure: > I agree with you, but I think is not necessary to put my name, I think = is better to put=20 the name of the sw developer who wrote it. Agreed. A revision history could look like this Paolo 13sep06 james 19sep06 Jovan 11nov06 Iain 12dec06 Some mechanism to archive the document before the given revision are made, should be simple to establish. What I do is just duplicate the master file with a copy that has a date extension in the filename, the date of modifcation. Then the next time I edit the doc, the duplicate with the extension gets archive (manually for me) and the current file has (2) copies, one with the doc name, the second with the doc name plus the date of modification extension, right in the filename. just a thought. ? >=20 >=20 > Documents: > When I wrote the first vision document draft I tried to make it clean a= nd simple as much as possible. I think this is what we need in principle. Concerning fonts and templates I=B4ll look if there are any standard we can use. Any idea is welcome at this stage. Yes, I just had trouble using it as a template, some of the auto formating, indexing, outline functions did not work correctly with open office..... But, as other take a document and modify it, we'll flesh out these idiosyncrasies. >=20 > Talking about GUI, yes, I=B4d like to use Qt (GPL version) and the scri= pting engine QSA.=20 I think Qt+QSA can help us to make QScada flexible and powerful. Well, I have no experience with QSA, but, it looks fine from what this page says: http://www.trolltech.com/products/qt/addon/qsa >=20 >=20 > Take care, > paolo >=20 I also like Jovan's suggestions below. Do they conflict with what you are presenting here Paolo? To me they are complimentary. What we need to do is say, here james here is a document. Take it and keep/modify sections 1-3 and 4 and beyond just follow the mechanics of the existing doc. I took one of Paolo's document and tried to just modify it for the hardware doc I sent to the group some time ago. My setup in OpenOffice gaged on some issues. Are we all using OpenOffice? Office on windows can give fits for documents when loaded into OpenOffice. Alternatively, I can just submit content in some agreeable form and somebody can put the content into a template form? I really do not care so much as to the details of how we do this as much as I care about a simple, quick method, so when I get time I can document my work. A lot of what I see myself doing is developing examples, that are centric around actual pieces of hardware, kind of a 'hardware dev kit for Qscada' as to attract other to participate with Qscada. For example, I need to develop or find an existing program to take brand new cisco and Adtran routers out of the box, connect to them using a rs232 serial port, and run a program to so a technician can enter a few pieces of information, and the router will be 'auto_magically' setup to run on a controls network. I'll first document the steps from a linux system, testing the validity of the steps manually. Then I'll script it, write ansi C code, and then finally develop some gui eye candy interface, using java. I could use QT-QSA too? Think about what I'll need and how I should do this, so that QScada can use/leverage the work for Qscada. After all, setting up routers, PLCs, targets(embedded linux systems) is all part of running a large controls network.... I willing to be the 'test_case'. The documents I end up with should be usable with Qscada. thoughts? James >=20 >=20 >=20 > ----- Messaggio originale ----- > Da: Jovan Kostovski <cho...@gm...> > A: qsc...@li... > Inviato: Mercoled=EC 29 novembre 2006, 17:16:53 > Oggetto: [Qscada-developers] Document templates >=20 > Hi all, >=20 > As we said, we need some templates for the documents. >=20 > What kind of templates do we need? > 1. Source code templates > 2. Document templates for documentation, propositions etc. > ... > ... >=20 >=20 > Which parts should we discuss about the document structure >=20 > 1. Sources: > - header comment > - filename > - description > - author ?? ((we'll probably put Paolo's name here, as he > is the project leader) > - revision history > - license > - code formatting > - naming conventions > ... > ... > ... >=20 > 2. General Document contents: > - front page layout > - table of contents > - header > - footer > - fonts to be used ?? > - pictures / diagrams which programs to use for creating them > ... > ... > ... >=20 > Ideas/ Suggestions ??? >=20 >=20 > GREETZ, Jovan >=20 > -----------------------------------------------------------------------= -- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to share= your > opinions on IT & business topics through brief surveys - and earn cash > http://www.techsay.com/default.php?page=3Djoin.php&p=3Dsourceforge&CID=3D= DEVDEV > _______________________________________________ > Qscada-developers mailing list > Qsc...@li... > https://lists.sourceforge.net/lists/listinfo/qscada-developers >=20 >=20 >=20 >=20 > __________________________________________________ > Do You Yahoo!? > Poco spazio e tanto spam? Yahoo! Mail ti protegge dallo spam e ti da ta= nto spazio gratuito per i tuoi file e i messaggi=20 > http://mail.yahoo.it=20 >=20 > -----------------------------------------------------------------------= -- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to share= your > opinions on IT & business topics through brief surveys - and earn cash > http://www.techsay.com/default.php?page=3Djoin.php&p=3Dsourceforge&CID=3D= DEVDEV > _______________________________________________ > Qscada-developers mailing list > Qsc...@li... > https://lists.sourceforge.net/lists/listinfo/qscada-developers >=20 |
|
From: Paolo S. <pao...@ya...> - 2006-12-13 12:22:23
|
Hi all,=0A=0Athank you for your effort and your ideas. I=B4m honoured to wo= rk with you all.=0A=0ATalking about coding convention, I=B4d like to invite= you to consider something like this=0Ahttp://www.cs.rice.edu/~dwallach/CPl= usPlusStyle.html=0A=0ASource structure:=0AI agree with you, but I think is = not necessary to put my name, I think is better to put the name of the sw d= eveloper who wrote it.=0A=0A=0ADocuments:=0AWhen I wrote the first vision d= ocument draft I tried to make it clean and simple as much as possible. I th= ink this is what we need in principle. Concerning fonts and templates I=B4l= l look if there are any standard we can use. Any idea is welcome at this st= age.=0A=0ATalking about GUI, yes, I=B4d like to use Qt (GPL version) and th= e scripting engine QSA. I think Qt+QSA can help us to make QScada flexible = and powerful.=0A=0A=0ATake care,=0Apaolo=0A=0A=0A=0A=0A----- Messaggio orig= inale -----=0ADa: Jovan Kostovski <cho...@gm...>=0AA: qscada-develope= rs...@li...=0AInviato: Mercoled=EC 29 novembre 2006, 17:16:53= =0AOggetto: [Qscada-developers] Document templates=0A=0AHi all,=0A=0AAs we = said, we need some templates for the documents.=0A=0AWhat kind of templates= do we need?=0A1. Source code templates=0A2. Document templates for documen= tation, propositions etc.=0A...=0A...=0A=0A=0AWhich parts should we discuss= about the document structure=0A=0A1. Sources:=0A - header comment=0A = - filename=0A - description=0A - author ?= ? ((we'll probably put Paolo's name here, as he=0Ais the project leader)=0A= - revision history=0A - license=0A - code forma= tting=0A - naming conventions=0A ...=0A ...=0A ...=0A=0A2. Gene= ral Document contents:=0A - front page layout=0A - table of contents=0A= - header=0A - footer=0A - fonts to be used ??=0A - pictures / dia= grams which programs to use for creating them=0A ...=0A ...=0A ...=0A=0A= Ideas/ Suggestions ???=0A=0A=0AGREETZ, Jovan=0A=0A-------------------------= ------------------------------------------------=0ATake Surveys. Earn Cash.= Influence the Future of IT=0AJoin SourceForge.net's Techsay panel and you'= ll get the chance to share your=0Aopinions on IT & business topics through = brief surveys - and earn cash=0Ahttp://www.techsay.com/default.php?page=3Dj= oin.php&p=3Dsourceforge&CID=3DDEVDEV=0A____________________________________= ___________=0AQscada-developers mailing list=0AQ...@li...ur= ceforge.net=0Ahttps://lists.sourceforge.net/lists/listinfo/qscada-developer= s=0A=0A=0A=0A=0A__________________________________________________=0ADo You= Yahoo!?=0APoco spazio e tanto spam? Yahoo! Mail ti protegge dallo spam e t= i da tanto spazio gratuito per i tuoi file e i messaggi =0Ahttp://mail.yaho= o.it |
|
From: Jovan K. <cho...@gm...> - 2006-12-01 11:27:59
|
Hi, On 12/1/06, wireless <wir...@ta...> wrote: > What about CVS vs SVN? Did we ever decide on that? Basically, SVN is better than CVS, it has most of the CVS features, though Here are some links on SVN vs CVS: http://www.pushok.com/soft_svn_vscvs.php http://wiki.scummvm.org/index.php/CVS_vs_SVN http://svnbook.red-bean.com/ - The SVN Book I've used both of them, i use SVN now, so I vote for SVN ;) GREETZ, Jovan |
|
From: wireless <wir...@ta...> - 2006-12-01 04:10:50
|
Jovan Kostovski wrote: > Hi all, > > As we said, we need some templates for the documents. > > What kind of templates do we need? > 1. Source code templates > 2. Document templates for documentation, propositions etc. > ... > ... > > > Which parts should we discuss about the document structure > > 1. Sources: > - header comment > - filename > - description > - author ?? ((we'll probably put Paolo's name here, as he > is the project leader) > - revision history > - license > - code formatting > - naming conventions > ... > ... > ... > > 2. General Document contents: > - front page layout > - table of contents > - header > - footer > - fonts to be used ?? > - pictures / diagrams which programs to use for creating them > ... > ... > ... > > Ideas/ Suggestions ??? > > > GREETZ, Jovan That looks like a hell of a start. Pick an example or 2 and each time we create or modify a document, we can extend the template if needed. The first page should be the same with just the differences in the unique information. Look at the RFC's as they are fine for documents that need content. But if you guys are going to publish the web, and make some live with revision history, then an XML file might be better? In summary, just pick a document or 2, edit them and we'll start there. You know how some wiki's can be edited by users, what about that sort of format? Maybe visitors or new members only get read permission and the devs get read/write? I'm not so hung up on the perfect document, as that will happen over time. I just think we need to get the templates up and agree who gets read/write privileges. The group is small right now, so who ever comes up with something, is the team leader for that issue(doc) or piece of code. What about CVS vs SVN? Did we ever decide on that? James |
|
From: Jovan K. <cho...@gm...> - 2006-11-29 16:36:19
|
Hi, On 11/28/06, wireless <wir...@ta...> wrote: > Hello Iain, Jovan et al, > > > jffnms is a wonderful network management software package seems like a good tool. I wanted to check it when you sent the link for the first time, but didn't get enough time :( > Although SCADA is about controlling remote hardware, particularly > those processes that require one of the various types of PID control, > we, as a project, can look at how this software statuses and manages > all sorts of network based equipment. You're right. Good tool for network diagnostics and monitoring is always welcome. It can be handy for detecting problems in the whole network. In a SCADA system there is one or more servers and many clients so managing and monitoring (for security reasons, traffic etc.) their networking would be nice. GREETZ, Jovan |
|
From: Jovan K. <cho...@gm...> - 2006-11-29 16:17:00
|
Hi all,
As we said, we need some templates for the documents.
What kind of templates do we need?
1. Source code templates
2. Document templates for documentation, propositions etc.
...
...
Which parts should we discuss about the document structure
1. Sources:
- header comment
- filename
- description
- author ?? ((we'll probably put Paolo's name here, as he
is the project leader)
- revision history
- license
- code formatting
- naming conventions
...
...
...
2. General Document contents:
- front page layout
- table of contents
- header
- footer
- fonts to be used ??
- pictures / diagrams which programs to use for creating them
...
...
...
Ideas/ Suggestions ???
GREETZ, Jovan
|
|
From: Jovan K. <cho...@gm...> - 2006-11-29 16:06:05
|
Hi, On 11/28/06, wireless <wir...@ta...> wrote: > How does everyone feel about Eclipse or Anjuta as an IDE? Anjuta is a good IDE but its more GTK oriented. It has integrated features for GTK development. Which GUI Toolkit shall we use for QScada? QT I supose. Eclipse is more robust and modular IDE. It has much more features than Anjuta, and has much more plugins for integrating many other things in it. I choose Eclipse. > Are we going to have/develop templates for documents? Yes we must create some document templates. Lets discuss that in a new thead GREETZ, Jovan |
|
From: wireless <wir...@ta...> - 2006-11-29 01:29:31
|
Hello Iain, Jovan et al, jffnms is a wonderful network management software package, including snmp 1,2.3. It's now an ebuild on gentoo. As a network guy, you might want to check out this package, it blows away nagios/cacti/mrtg. It supports both mysql and postgresql. http://www.gentoo.org/doc/en/jffnms.xml www.jffnms.org (for unix and windoze) Although SCADA is about controlling remote hardware, particularly those processes that require one of the various types of PID control, we, as a project, can look at how this software statuses and manages all sorts of network based equipment. I believe, at the bare minimum, that jffnms is complimentary to QScada, in a twisted-paradyne sort of future. From custom interfaces to SNMP and router/computer monitoring and control are merging. We should think about those implications as we finish the formulation of QScada. At the heart of JFFNMS is rrdtool which is used in all sorts of software: http://oss.oetiker.ch/rrdtool/gallery/index.en.html http://oss.oetiker.ch/rrdtool/ These tools are not real time, or even close to it. They do produce nice graphs of equipment performance for those items that do not need to be controlled (other than on/off) nor status with strict timing constraints. Over the years I have watched JFFNMS grow into a very attractive software package, and the devs are frequently receiving invitations for very attractive consulting work, while continuing the development of JFFNMS...........under GPL. They get paid to customize and extend the software for particular corporate needs, yet the code goes back into the GPL'd software for all to benefit. (does this sound interesting to anyone?) http://www.jffnms.org/features.php enjoy! James |
|
From: wireless <wir...@ta...> - 2006-11-28 18:31:11
|
Jovan Kostovski wrote: > On 11/16/06, wireless <wir...@ta...> wrote: > >>Besides I thought we had agreed on C/C++, QT, and Java? >>Any other languages? > > > XHTML, PHP, JavaScript + XML (AJAX) for web based scada clients, > can't think of anything else at the moment. What will the others say? :) > > GREETZ, Jovan Ok, How does everyone feel about Eclipse or Anjuta as an IDE? Are we going to have/develop templates for documents? Guys like myself really need some attention to this details, so the resultant documents are similarly structured, are easily published on the web and straightforward to update, revise and maintain. The last document I sent was *ugly*..... These above look OK to me. Any comments? If not all we'll need are some templates, which may become self evident after a few more documents are offered up. James |
|
From: wireless <wir...@ta...> - 2006-11-22 15:48:38
|
GPL'd Java http://www.linuxjournal.com/node/1000125 enjoy james |
|
From: Jovan K. <cho...@gm...> - 2006-11-21 01:14:20
|
Hi, On 11/16/06, Jovan Kostovski <cho...@gm...> wrote: > I've written one seminar paper on OPC when I was at college, about 15 pages. > I'll translate it to english and send it here so we can all be familiar with the > concepts used in OPC. As I promissed. Here is a link where you can download the paper http://chombium.awardspace.com/files/qscada/opc_paper.pdf Enjoy. Its a bit outdated though. The current development of OPC foundation is the OPC Unified Architecture (OPC UA) standard GREETZ, Jovan |
|
From: wireless <wir...@ta...> - 2006-11-20 19:32:15
|
Hello Everyone, The attached document is only a *DRAFT*. I spent my time on content and ideas, not making the document look nice. Which brings up a very good point; we need to define a document semantic (xml, doxygen, open_office) that provides templates so all of our docuemts follow the same format, are easy to publish on the web, and are user friendly to add/modify content. However we decide this, I think the webmaster (Iain) should have quite a lot of say, because, he will have to setup and maintain our online docs. Nothing is the document is authoritative. I merely looked at one of Paolo existing document and took a 'first stab' at fluffing out the intention. I tried to provide links to relevant, previous work that we should consider compatibility with or gleen good ideas from. Also, there are many ideas that need to be discussed, before a detailed analysis can be agreed upon. After that, much more depth and detail can be added to these docuemnts. We do not need to work on these documents ad_nosium, we just need to agree on a framework of skeleton documents. As our work progresses, these documents will be modified apppropriately. thoughts? sincerely, James |
