labview for batch processing

[mom]

dear sir,

 i am using labview7.0 for scada application  using dsc module. In this application we are aquiring data from instrument. Now i want to develope scada software using labview dsc module for batch processing. But i donot have any idea about batch processing. Please help me to know more about batch processing. And how can i develope the scada software for that

thanking you

falgandha

[MattP]

Hello,

Batch processing typically involves raw materials that are combined to mix or react in a certain sequence over a period of time to produce the completed output. Often, different recipes are used to combine the materials in different ways and with different sequences to change the outcome. Automation is used in batch processing to precisely control quantities, times and sequences (description found with a Google search of 'batch processing'), and you can use LabVIEW DSC to control your system.  This is accomplished by using data items called tags bound to your hardware.  To send a command to your hardware, you would write a new value to a tag bound to that hardware.  Hardware could include PLC's, Fieldpoint controllers, RTU's, Modbus devices, etc.  Most commonly, you will connect the tags to your hardware via an OPC server.  OPC servers are available from NI, the PLC manufacturer, and several 3rd-party vendors such as Kepware.

Providing you with more detailed information will be difficult without a more specific question I can help you with  The DSC Module help and shipping examples will get you started with creating your application, so I'd recommend giving those a look.  If you have a more specifc question about how to do something in LabVIEW, let us know and we'll be glad to help!

[mom]

dear sir

thanks a lot.

if you have develpoed any application  for batch processing please give me any idea or details regarding to screen designing

falgandha

[MattP]

Hello,

The design of your screens in DSC will depend heavily on what exactly you want each screen to do.  I would recommend first defining exactly what you need the system to do before you start trying to build the interface for the system.  For example:

• What process/action you want the software to control
• Inputs required from the operator at each stage of the process
  
• What information needs to be displayed to the operator at each stage of the process

Armed with this knowledge, it will be much easier to properly design the screens to interact with your application.  Beyond just the view into the system, you should also spend some time considering how to model and control your system.

For the model:

• What do you want to control?
• How can you represent this system in terms of I/O?
  
• What data items must be created?

For the controller:

• What stages exist in your process?
• How will you transition between states?
• What events (alarms) do you want the system to be able to respond to?
• Under what conditions do you take each action?

Considerations like these will help you decide how best to architect your system.  In the end, I can only provide suggestions - it will be up to you to decide what is best for your application.