M
Juan Carlos Orozco wrote:
>
> Mario,
>
> About the point 10 - big demo,
>
> I had serious difficulties running LinuxPLC in RedHat 7.0. I could not find
> the console-tools-dev equivalent. I tried the smm-mgr -g and I am getting a
> lot of "Error initializing the plc" messages. For now I gave up trying with
> RedHat 7.0 because debian seemed to work easier.
>
> With the Corel Linux 1.2 (slink debian) things worked better except for the
> vitrine that did not run.
We have to figure out why things are not working in these distributions... I guess this is a good reason to get a binary release out? It doesn't mean we shouldn't figure out what the problems are though...
The console-tools-dev package is only required for the mmi/kbd module. This module allows a user to use the keyboard as push buttons. This is mainly for testing without having to revert
to physical inputs... The rest of the PLC should work without this module. The demos use it, but I think a workaround is still available if this module is not compiled (Jiri, can you confirm this?).
> Since debian seemed to work better I decided to
> get the current stable version of debian (potato). Things worked beautifully
> with this linux, the demos worked very well. Except for the tcl demo that
> has a known bug in potato (I just could not figure out the workaround) when
> compiling /lang/tcl and running ./configure I get a message saying that int
> could not find tcl configuration definitions. Any way I am not planning to
> use tcl for the moment so this is not a problem for now.
I am attaching a file with an email I sent Greg explaining the same difficulties I experienced and how I got around them. Their seems to be a bug in the configure script. How it got there,
I don't know. Maybe people with experience using autoconf can help here?
> I finish installing debian potato yesterday so I am barely starting with the
> demo. I have some documents on the project and want to start trying some
> modifications on the basic demos, I will base my project on the basic_dsp
> demo since my project has some PIDs in it. By the way what is the graph part
> of the vitrine in the basic_dsp demo supposed to do? On my computer it just
> moves a couple of + to the right or to the left as I type 0-9. The two +
> signs move together. Taking a second look to the vitrine.conf I may have
> found the answer myself, it seems there is a typo, in the last line it
> should be out_1 instead of out_f32 for the x_plc_pt and y_plc_pt. One more
> thing, when exiting from the demo my terminal does not make a correct
> carriage return any more which makes it useless. I need to start a new
> terminal after exiting vitrine.
I'm sorry. I have to go now. I'll look into this later on. Anyway, this functionality of the vitrine is not quite finished. I was doing this to test the DSP module. I got stuck doing the
filters of the DSP module, and I have not yet found a book with examples with numbers to help me debug my filters. Anyway, lowpass and highpass seem to be working. Bandpass and bandreject are the problematic ones.
Thanks for your help Juan!
Keep up the good work!
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
>
> Mario,
>
> About the point 10 - big demo,
>
> I had serious difficulties running LinuxPLC in RedHat 7.0. I could not find
> the console-tools-dev equivalent. I tried the smm-mgr -g and I am getting a
> lot of "Error initializing the plc" messages. For now I gave up trying with
> RedHat 7.0 because debian seemed to work easier.
>
> With the Corel Linux 1.2 (slink debian) things worked better except for the
> vitrine that did not run.
We have to figure out why things are not working in these distributions... I guess this is a good reason to get a binary release out? It doesn't mean we shouldn't figure out what the problems are though...
The console-tools-dev package is only required for the mmi/kbd module. This module allows a user to use the keyboard as push buttons. This is mainly for testing without having to revert
to physical inputs... The rest of the PLC should work without this module. The demos use it, but I think a workaround is still available if this module is not compiled (Jiri, can you confirm this?).
> Since debian seemed to work better I decided to
> get the current stable version of debian (potato). Things worked beautifully
> with this linux, the demos worked very well. Except for the tcl demo that
> has a known bug in potato (I just could not figure out the workaround) when
> compiling /lang/tcl and running ./configure I get a message saying that int
> could not find tcl configuration definitions. Any way I am not planning to
> use tcl for the moment so this is not a problem for now.
I am attaching a file with an email I sent Greg explaining the same difficulties I experienced and how I got around them. Their seems to be a bug in the configure script. How it got there,
I don't know. Maybe people with experience using autoconf can help here?
> I finish installing debian potato yesterday so I am barely starting with the
> demo. I have some documents on the project and want to start trying some
> modifications on the basic demos, I will base my project on the basic_dsp
> demo since my project has some PIDs in it. By the way what is the graph part
> of the vitrine in the basic_dsp demo supposed to do? On my computer it just
> moves a couple of + to the right or to the left as I type 0-9. The two +
> signs move together. Taking a second look to the vitrine.conf I may have
> found the answer myself, it seems there is a typo, in the last line it
> should be out_1 instead of out_f32 for the x_plc_pt and y_plc_pt. One more
> thing, when exiting from the demo my terminal does not make a correct
> carriage return any more which makes it useless. I need to start a new
> terminal after exiting vitrine.
I'm sorry. I have to go now. I'll look into this later on. Anyway, this functionality of the vitrine is not quite finished. I was doing this to test the DSP module. I got stuck doing the
filters of the DSP module, and I have not yet found a book with examples with numbers to help me debug my filters. Anyway, lowpass and highpass seem to be working. Bandpass and bandreject are the problematic ones.
Thanks for your help Juan!
Keep up the good work!
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