M
1 - a tcl demo. This already exists in the demo/basic directory,
just needs re-organizing into an independent basic_tcl directory.
DONE!
2 - get the modbus modules to compile, i.e. include the function
that was in the old io.c file into the modbus source files.
Philip, I have now inserted the plc_io_status_pt() function
in the generic io library. The modbus modules will still not
compile because they do not conform to the io_hw.h interface.
Are you working on this? If you have any questions,
don't be afraid to ask!
3 - a modbus demo explaining how to configure the module.
Waiting for point 2.
4 - Debug the filtering blocks of the dsp module.
I think we should make the release without this!
5 - have the dio48 module use the new generic io library
6 - a demo directory for the dio48 module
This module is working. We can make the release with the
module as it is and change it later. We'll see if
time allows to do the above before the release.
7 - A user manual, probably in html format.
Curt, do you need help with this?
8 - a demo directory for the il compiler (e.g. implement the chaser
in il).
DONE!
9 - A top level makefile that will make each module, and install
the libraries and executables into apropriate directories,
i.e. get all the executables into a single directory (probably
with sub-directories for io moduls, logic modules, utilities, ...)
Jiri, I know you don't agree with this, but I think if we are
going to make a release we should try and keep to the
sugestions in the Software Release Practice HOWTO
http://www.linuxdoc.org/HOWTO/Software-Release-Practice-HOWTO/index.html
Do you think you could help out here? The top level makefile should
probably also have a make install that installs the plc libraries
in the apropriate directories (/usr/lib).
What I would really like to see is a top level make release
that would make a tar.gz release file. The HOWTO has some
demo code for the makefile to do this. Could you look into
this? Once we have this, we can make releases more often.
10 - A big demo, with some nice graphics, and realistic processes...
Juan, how are you coming along with this?
Do you have any questions?
11 - finish lib/util/puffinplc.c so that it can wait for a quit point,
and
then eliminate the demo/*/demo perl scripts. They were quick and dirty
hacks to begin with and should die (I can say that, I wrote them).
Jiri, I would like to do this properly from the start.
We need to think about this before we go charging ahead.
Do you have any ideas offhand we could start discussing?
Once we get the first release out the door,
Cheers,
Mario.
--
----------------------------------------------------------------------------
Mario J. R. de Sousa
[email protected]
----------------------------------------------------------------------------
The box said it requires Windows 95 or better, so I installed Linux
_______________________________________________
LinuxPLC mailing list
[email protected]
http://linuxplc.org/mailman/listinfo/linuxplc
just needs re-organizing into an independent basic_tcl directory.
DONE!
2 - get the modbus modules to compile, i.e. include the function
that was in the old io.c file into the modbus source files.
Philip, I have now inserted the plc_io_status_pt() function
in the generic io library. The modbus modules will still not
compile because they do not conform to the io_hw.h interface.
Are you working on this? If you have any questions,
don't be afraid to ask!
3 - a modbus demo explaining how to configure the module.
Waiting for point 2.
4 - Debug the filtering blocks of the dsp module.
I think we should make the release without this!
5 - have the dio48 module use the new generic io library
6 - a demo directory for the dio48 module
This module is working. We can make the release with the
module as it is and change it later. We'll see if
time allows to do the above before the release.
7 - A user manual, probably in html format.
Curt, do you need help with this?
8 - a demo directory for the il compiler (e.g. implement the chaser
in il).
DONE!
9 - A top level makefile that will make each module, and install
the libraries and executables into apropriate directories,
i.e. get all the executables into a single directory (probably
with sub-directories for io moduls, logic modules, utilities, ...)
Jiri, I know you don't agree with this, but I think if we are
going to make a release we should try and keep to the
sugestions in the Software Release Practice HOWTO
http://www.linuxdoc.org/HOWTO/Software-Release-Practice-HOWTO/index.html
Do you think you could help out here? The top level makefile should
probably also have a make install that installs the plc libraries
in the apropriate directories (/usr/lib).
What I would really like to see is a top level make release
that would make a tar.gz release file. The HOWTO has some
demo code for the makefile to do this. Could you look into
this? Once we have this, we can make releases more often.
10 - A big demo, with some nice graphics, and realistic processes...
Juan, how are you coming along with this?
Do you have any questions?
11 - finish lib/util/puffinplc.c so that it can wait for a quit point,
and
then eliminate the demo/*/demo perl scripts. They were quick and dirty
hacks to begin with and should die (I can say that, I wrote them).
Jiri, I would like to do this properly from the start.
We need to think about this before we go charging ahead.
Do you have any ideas offhand we could start discussing?
Once we get the first release out the door,
Cheers,
Mario.
--
----------------------------------------------------------------------------
Mario J. R. de Sousa
[email protected]
----------------------------------------------------------------------------
The box said it requires Windows 95 or better, so I installed Linux
_______________________________________________
LinuxPLC mailing list
[email protected]
http://linuxplc.org/mailman/listinfo/linuxplc