Jump to content

Alejandro_i

Members
  • Posts

    6
  • Joined

  • Last visited

Posts posted by Alejandro_i

  1. Thank for all, because I didn't know how works thir forum... sorry about this comment.

    Our problem is not Labview DSC power, we want to make easier and faster all the variable definition , it's like Alejandro_i explains... He says something about a new tool, XDSC, what's that? how it works...

    Does anyone know anything about XDSC?

    Alejandro_i, where can we see the features of this toolkit? we haven't found in any web page...

    Hi 'shared brain'.

    ¡I found a video demo named XDSC_Demo.avi!. This video explains how do you use this component. It seems Xnode-Based Technology...

    Does anyone have additional information about this component (XDSC)?

    Thanks

  2. Hi,

    We are starting a DSC project up to 1500 variables. Anyone knows any tools to make faster data binding and manipulate variables properties?

    Thanks

    Hi, 'shared brain'. I think this is a very big project !!. Based on my experience, shared variable engine (tagger) is enough powerful to develop a application with this number of variables (break your library process between other lesser libraries).

    You have a limited set of tools shipped with LabVIEW DSC to configure links between front panel controls and indicators, and shared variables.

    1) Front panel binding, available on ‘Tab’ control properties: Data Binding (use PSP option). This option involves long time to implement connections. Imagine 1000 controls on front panel … !.

    2) Mass front panel databinding. You should make some .csv file to configure controls and indicators

    The two methods exposed have limitations to keep sustainability and scalability. You should think about others application aspects:

    - Control maximum, minimum and increment values. User interface should act as input values filter. When you operate a machine or process is very important to prevent you can’t input dangerous values

    - Normally, the communication between PC and PLC’s is made by OPC Servers software layer, so you should verify input values are correctly transmitted. It is necessary to control this communication, waiting until input values are written to PLC

    - Messages to user to confirm Boolean operations (Run/Stop,…)

    - Application scalability. If you have a monitoring system where two or more machines have a similar process variable mapping, you should re-use the code with minimum changes (I think process name is the unique difference between machines)

    - …

    As you have seen, the tools shipped with LabVIEW DSC are limited, and you should think about a toolkit/scripting tool to resolve these problems.

    I have heard exists a component/toolkit named XDSC, developed for a engineering that can you help, because resolve enough problems, and the most important, you can to save a lot of development time.

    I will post information soon…

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.