I would like to be able to generate text tables within my report generated form LabVIEW using the Express vi DIAdem report...currently the only way to do this is create a script. This seems to be an overcomplicated way of doing a relatively benign operation and makes the tool very cumbersome.
Whilst you're at it, labeling the y-axis of a graph also seems to be over complicated from within LabVIEW. Maybe I'm just too used to easy programming with LabVIEW! But programming isn't my main activity...
When editing a Script. The path for the saving files defaults to the last opened file, instead of remembering the path for each file being editted. This causes files to be saved in the directory of the last file opened, which many times results in the wrong saving location. This is especially an issue when have large number of script files in different directories.
I would prefer that each script file that was being edited would keep it path separate and stored so that it always saves the files to the location that it was opened from.
It should be possible to use the code completion functionality for classes one has written, even when the class is in another VBS file and included by “ScriptInclude”. Now that competion feature works only if the class is defined within the same VBS file as one writes the code which uses this class. That would make the developers live much easier, I am sure I am not the only one who writes code which is distributed over several files
I am trying to push DIAdem as an analysis tool. Some of the Engineers use VBOX for DAQ. I downloaded the plug-in to mess with their data.
I was really looking forward to using the GPS to make a map and plot speed, accell etc... I could only load street maps.
Satellite maps would be very usefull. There are no roads where we we are taking GPS data.
Has anyone been able to load custom maps or satellite maps? DIAdem needs more map options in the drop down.
Para los que nos dedicamos a distribuir scripts a clientes creo que se podria estudiar que se pudieran crear ejecutables de un conjunto de macros. Para el usuario final en caso de que estén encriptadas siempre es más facil ejecutar un .exe. También a nivel de desarollo se tienen más posiblidades para proteger un numero de licencias con soluciones como los dongles que se requiere un .exe o programar a partir de la API.
It would be very useful to have the ability to use the X-Channel properties in a chart legend as a default option. In the instance of plotting several stress-strain curves on one chart where the Y-Channel (Stress) is shared across different strain (X) channels, there is no easy way of using the legend to show information from the X-Channel.
There are several ways to get X-Channel data in the legend but these methods only get data from the X-Channel of your first or last curve in the chart and uses that same info in the legend for all curves.
The data reduction on loading could be extended to facilitate partial loading of large data sets:
Currently, it shows 'intervall width' or 'interval number' and 'reduction method (1st value, avg. min, max)'.
I'd love to have an option to define start value and data count, too. Similar to the FFT-timing dialog, where 'start/number/width' can be defined. Today, I always load the full data set, display in view, mark the relevant area and crop via 'mark data' and delete. Works ok, but when I know that I will need maybe the first 5 secs of a 10 minue measurement for one evaluation, it could be done easier, if I only load what I need.
it would be helpful to have the following option in the View:
In case of moving the cursor through the 2D-Graph, I would like to have the table scrolling automatically the same way with highlightning the values of the cursors position.
It would be great to be able to use CurveSnippets taken from a chart on one report sheet and use them on another report sheet. The most obvious use would be when showing chart legend on another sheet. This cannot be done currently and is essential for making legends on different sheets than their charts.
We use scripts extensively to automate many tasks in a consistent manner, so we back these scripts up in a version control system to track changes and revert back to a know version if issues arise.
However, because we also use Diadem dialogs we need to create SUD files to house not only the menus but also the scripts that can be built into them. These SUD files are binary in nature and cannot be compared in the version control system, which is primarily a text based tool, and because the fileformat is unknown any differences at the binary level are not easily understood.
My idea is to have a tool that can parse a SUD file to extract the script associated with each dialog and export that script to a VBS file in a programmatic manner, such that multiple VBS files can be created quickly instead of having to open each SUD file and its many dialogs and then capturing the scripts. The benefit this brings is that there will now be the ability to track script differences in any text diff tool of your choice, it would not address any changes of a graphical nature within the SUD file, but that is not the motivation for this idea.
During script development I'm finding I often want to run little one-off scripts to get some insight into the environment at that particular point in time. Stuff like...
or maybe iterating through a collection to see what it contains.
Currently I have to open a new script window, type up my script, and execute it. This gets to be a headache as I have several temporary script windows open each with a different command I want to use. It would be nice to have a script console tab available in the watch window where I could type in the commands and have them execute immediately. Alternatively, an option to highlight a section of a script and execute only that section would allow me to bunch all my commands into a single temporary window.
1. Currently you can't enlarge the window of DAC-module "Linear scaling"
=> for better overview it is necessary to implement this feature
2. Currently there is no possibilty to export the list of signals (excel)
=> for documentation it is necessary to export
Thank you for your support.
Currently, whenever you open a block diagram in DIAdem DAC, it closes anything that is already open. This is inconvenient if you want to open two separate .DAC files for comparison, copy&paste, prototyping, etc. and especially when you want to reference an example, it tries to close whatever block diagram you have open and may still be working on.
Having multiple tabs like in VIEW, REPORT, and SCRIPT would definitely improve the user experience. Alternatively, we could have it minimized somewhere or have it selectable from the Window menu as long as it allows you to keep multiple block diagrams loaded at the same time.
I know right now you can create a coordinate object in a 2D plot and set the values or create a constant line. Now I would like to create a line that would have the same behavior as the coordinate, just making the input of the initial and final points. I know it is posible to do it creating 2 channels in the data portal but I would like to have the line embedded in the 2D-Plot just like the constant and coordinate objects.
I'd like to have a 64-bit version of DIAdem primarily so the program can utilize more than 2GB of RAM.
I'd expect that this would improve performance and stability for those using a 64-bit OS (eg win 7 64 bit) and working with large data sets.
The DIAdem R&D team is committed to reviewing every idea submitted via the DIAdem Idea Exchange. However, we cannot guarantee the implementation of any DIAdem Idea Exchange submission until further documented.