M
Hugh Jack wrote:
>
> Hi,
>
> Please give me some time to look over the docs and source code - a
> couple of days would work. In the mean time you can have a look at my
> specs at;
>
> http://claymore.engineer.gvsu.edu/lpcd/lpc.0.0.7.4/docs/io_spec.doc
>
> The basic architecture is a central process loader that loads modules as
> dynamically linked libraries. Each library is linked to a common set of
> routines that handle execution. They can exchange data and messages
> through the loader. The loader is very lightweight. This is by design so
> that it can be replaced easily to switch between pthreads, rtlinux, or
> roll your own OS.
>
Hi Hugh,
I seem to remember we started discussing this privately, but I started concentrating on other details and never really got back to you. Sorry
Hugh!
I think Hugh's modules and our own are similar, but different in that our modules include a main() function and only use the library to
interface to the common data. Hugh's modules are library functions that get called by the main program (the loader - it actually creates a
pthread for each). Without really thinking too much on the subject, what I sugest is to:
- write a generalised linuxplc wrapper module (with a main function) that loads a PPLC module and implements the functions provided by Hugh's
loader.
We could then run any PPLC module as a linuxplc module.
I'll have to take some time out to look into it more thoroughly though.
I would like to press on with the effort of producing a binary release, but I think this merging of efforts is also important. What should we concentrate on now?
-------------
Things left to do until a binary release:
- finish the oven demo
Juan is working on this...
- add a few features to the dsp to support the oven demo
I am working on this. It shouldn't take too long.
- get the tcl code to compile.
This should take 5 minutes for somebody who knows how to configure autoconf. We merely need to link the current code with the librt library (i.e. add -lrt to the linker)
- get the modbus code to compile
This should take 10 minutes using the quick hack of inserting the missing function (now in the io library) directly into the modbus code.
- create demos for the dio and modbus modules.
- create the binaries for release...
Jiri, do you think you could add a top-level Makefile so we can do a '$make dist' whenever we want to make a release. This would do a '$make dist-compile' followed by a 'make dist-clean' that would delete all the intermediate .o files, and finished by a '$make dist-tarball' that would make the tarball file whose name would include the release version. This would make further relaeses much easier.
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
>
> Hi,
>
> Please give me some time to look over the docs and source code - a
> couple of days would work. In the mean time you can have a look at my
> specs at;
>
> http://claymore.engineer.gvsu.edu/lpcd/lpc.0.0.7.4/docs/io_spec.doc
>
> The basic architecture is a central process loader that loads modules as
> dynamically linked libraries. Each library is linked to a common set of
> routines that handle execution. They can exchange data and messages
> through the loader. The loader is very lightweight. This is by design so
> that it can be replaced easily to switch between pthreads, rtlinux, or
> roll your own OS.
>
Hi Hugh,
I seem to remember we started discussing this privately, but I started concentrating on other details and never really got back to you. Sorry
Hugh!
I think Hugh's modules and our own are similar, but different in that our modules include a main() function and only use the library to
interface to the common data. Hugh's modules are library functions that get called by the main program (the loader - it actually creates a
pthread for each). Without really thinking too much on the subject, what I sugest is to:
- write a generalised linuxplc wrapper module (with a main function) that loads a PPLC module and implements the functions provided by Hugh's
loader.
We could then run any PPLC module as a linuxplc module.
I'll have to take some time out to look into it more thoroughly though.
I would like to press on with the effort of producing a binary release, but I think this merging of efforts is also important. What should we concentrate on now?
-------------
Things left to do until a binary release:
- finish the oven demo
Juan is working on this...
- add a few features to the dsp to support the oven demo
I am working on this. It shouldn't take too long.
- get the tcl code to compile.
This should take 5 minutes for somebody who knows how to configure autoconf. We merely need to link the current code with the librt library (i.e. add -lrt to the linker)
- get the modbus code to compile
This should take 10 minutes using the quick hack of inserting the missing function (now in the io library) directly into the modbus code.
- create demos for the dio and modbus modules.
- create the binaries for release...
Jiri, do you think you could add a top-level Makefile so we can do a '$make dist' whenever we want to make a release. This would do a '$make dist-compile' followed by a 'make dist-clean' that would delete all the intermediate .o files, and finished by a '$make dist-tarball' that would make the tarball file whose name would include the release version. This would make further relaeses much easier.
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