[MAT-devel] Oven demo in its final stages...

J

Thread Starter

Juan Carlos Orozco

Hi all,

I uploaded to the mat cvs the first release candidate of the oven demo using vitrine. By the way thanks Mario for the change in the point definitions, this was a time saver.

I will upload the gui version of this demo shortly.

By the way I want to make a suggestion to change the names for the directories of the demos that use the graphical interface hmi_gtk:

basic_gtk to basic_gui?
basic_dsp_gtk to basic_dsp_gui?

Therefore the name for the oven gui will be:
oven_gui

Another option is to have a gui subdirectory inside the demo directory. In any case a README file inside the demo directory or in the documentation, listing the demo directories and a short description could be of great help for a new user.

I am not a cvs expert so I rather not do this changes myself.

If this is not possible or someone is against this, no problem. In this case I may add oven_gtk for consistency.

Any suggestions about this?

Regards,

Juan Carlos Orozco

ACElab Industrial Automation
[email protected]
www.ace-lab.com

_______________________________________________
LinuxPLC mailing list
[email protected]
http://linuxplc.org/mailman/listinfo/linuxplc
 
Juan:
> I am not a cvs expert so I rather not do this changes myself.

It's not really possible to re-name directories in CVS. There are ways of doing it, but they're all clumsy and have various drawbacks.

Generally it's better to leave them as they are.

BTW, you're right that there should be a guide through the demo directory in the documentation (in the manual, I think).


Jiri
--
Jiri Baum <[email protected]>
http://www.csse.monash.edu.au/~jiribvisit the MAT LinuxPLC project at http://mat.sf.net

_______________________________________________
LinuxPLC mailing list
[email protected]
http://linuxplc.org/mailman/listinfo/linuxplc
 
J

Juan Carlos Orozco

>> I am not a cvs expert so I rather not do this changes myself.
>
> It's not really possible to re-name directories in CVS. There are ways of
> doing it, but they're all clumsy and have various drawbacks.
>
> Generally it's better to leave them as they are.

Ohh, I may have added directories without proper care. This is good to know, I guess one must think twice before naming a directory in a cvs. I
must be spoiled by PC file systems.

For consistency the oven directory for the gui interface should be oven_gtk then.

Also, please notice that pushbuttons are now implemented. I updated the hmi_gtk module its README file and also the basic_gtk demo. In the
basic_gtk demo aditional window I leaved the toggle buttons, just to have the two options available, besides toggle buttons reflect the
current state of the bit so its nice to see them change while one presses the corresponding push button.

Regards,

Juan Carlos Orozco

ACElab Industrial Automation
[email protected]
www.ace-lab.com

_______________________________________________
LinuxPLC mailing list
[email protected]
http://linuxplc.org/mailman/listinfo/linuxplc
 
J

Juan Carlos Orozco

Hi,

Now the basic_gtk bug (no pushbuttons) and the hmi_gtk feature request (graphical representations of on/off) are solved and the changes reflected in the files of the hmi_gtk and basic_gtk directories. Please let me know what do you think about them Jiri.

Also I need to place some images for the oven_gtk demo, this images can be of use to other graphical hmi's. I propose to place them in a directory called images (go figure) that will be placed under the hmi_gtk directory. If anyone is against this location please let me know.

Regards,

Juan Carlos Orozco

ACElab Industrial Automation
[email protected]
www.ace-lab.com

_______________________________________________
LinuxPLC mailing list
[email protected]
http://linuxplc.org/mailman/listinfo/linuxplc
 
M

Mario de Sousa

> I uploaded to the mat cvs the first release candidate of the oven demo using
> vitrine.


Hi Juan,

Looking good!

BTW, can you please check whether it is working as intended. It seems that the HEATER loop is brocken. The HeaterHeat is always 0, even with
the PID output at 100%. It didn't work that way before.

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
 
M

Mario de Sousa

Arggghhh... Forget it!

It seems that we now have to start the machine first... ;-)

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
 
J

Juan Carlos Orozco

Because this is a more complete demo, now the start machine and stop machine actually work. You need to press the corresponding key to start the machine. Maybe this is what is happening. There are two indicators on the upper part of the demo that show the state of the flame and of the pump, this should turn to on when the machine is running. Another change between the machine being on and off is the belt speed feedback. By the way the speed of the belt is used to simulate the heating of the product. I found this interesting because the temperature of the product that is being heated is normally not available, but in this case it is simulated so there is no need
to sense this value to have an idea of how the product is being processed.

Regards,

Juan Carlos Orozco

ACElab Industrial Automation
[email protected]
www.ace-lab.com

_______________________________________________
LinuxPLC mailing list
[email protected]
http://linuxplc.org/mailman/listinfo/linuxplc
 
Juan:
> Now the basic_gtk bug (no pushbuttons) and the hmi_gtk feature request
> (graphical representations of on/off) are solved and the changes
> reflected in the files of the hmi_gtk and basic_gtk directories.

Sounds good - don't forget to close them in the bug tracker; you should be able to get to them through http://sf.net/my (sorry if you knew that).

> Please let me know what do you think about them Jiri.

I'll have a look at them.

> Also I need to place some images for the oven_gtk demo, this images can
> be of use to other graphical hmi's. I propose to place them in a
> directory called images (go figure) that will be placed under the hmi_gtk
> directory. If anyone is against this location please let me know.

Don't forget the -kb option when you're adding them, if they're binary. (Most image formats are binary, I think the only exception is .xpm)

BTW, was I going to get you the LED images or not? I lost track... I have a red LED, and I was going to make all eight colours of it, but didn't get around to it yet. (I seem to be running short of round toits these days.)

Jiri
--
Jiri Baum <[email protected]>
http://www.csse.monash.edu.au/~jiribvisit the MAT LinuxPLC project at http://mat.sf.net

_______________________________________________
LinuxPLC mailing list
[email protected]
http://linuxplc.org/mailman/listinfo/linuxplc

 
Top