Thanks for the feedback.
It appears to me that the DataPlugIn's are designed to work only when data sets are opened manually through DIAdem navagator. They do not apparently execute when we load data sets through scripts created and executed under DIAdem Scripts (like the gfsmme.dll feature does). Do I understand this correctly?
Thanks and please advise.
Hello,
It sounds as if you are using the MME import based on the DIAdem GPI extension "gfsmme.dll". There is currently a new DataPlugin for ISO-MME on our website that has more functionality. YOu can find this at http://www.ni.com/dataplugins.htm. The older GPI import used variables while the new plugin stores the MME parameters in groups and channel properties. The new DataPlugin will be much more useful to you but you may have to adapt your application to access these MME properties. As to each of your questions:
1. The DataPlugin does not require a fixed order of keywords in the channel files. This was an issue however with the GPI import.
2. The plugin in capable of loading specific channels as well as registering large sets of data.
3. THe channel comment file is optional in the MME format without and format requirements. This plugin does not by default access this file butyou could customize the script to do so.
4. Currently, we still do not have these provisions in the plugin but I will make a product suggestion for it to be included in the future.
Thanks,
Caroline
National Instruments.
04-01-2005 07:19 AM
We are experiencing some difficulties/awkwardness with the DIAdem MME data import function. Please consider the following:
1. The keywords from the channel file are stored in a vector (MME_ChnInfoDesc) and the related values are stored in a matrix (MME_ChnInfo). This scheme assumes the keywords are in the same order in all channel files that comprise the MME set. This is not the case as the ISO specification allows comment keywords to “be used at any line”. In addition, many of the keywords defined in the ISO specification are optional. The insertion of optional keywords will result in channel files with differing keywords and the MME_ChnInfoDesc vector will not represent the keywords properly.
2. Is it possible to have the MME reader only load specific channels in the MME data set, rather than loading the entire MME data set? We have very large MME sets from which only a few channels are required. We do not want to allocate time or memory to handle the excess data.
3. There are no provisions to retrieve the comments for a particular channel from the channel comment file (CHANNEL.TXT).
4. There are no provisions to write MME data channels, sets, or comments.
These issues are forcing us to consider writing a low-level driver to read and write MME data. Does NI have any advise for us on this issue?
Thank you very much.
