DIAdem Idea Exchange

Community Browser
cancel
Showing results for 
Search instead for 
Did you mean: 
Post an idea

Use Case: We frequently use the 'Report' panel of DIAdem, where the 'Transfer-To-View' function is essential. Typically, we include 4-5 graphs on a single 2D axes system.

MMargaryan_2-1743604003475.png

 

 

After transferring the page to the 'View' panel, we receive the correct image but with multiple areas worksheet

MMargaryan_1-1743603799549.png

Problem Statement: When zooming the x-axis, each area zooms independently, which is inconvenient when analyzing data from multiple graphs simultaneously.

Proposed Feature:

  1. Combined Area Zoom: Create a feature that combines multiple areas (e.g., 4 areas) into a single area. This would enable synchronized zooming of all areas while preserving individual graph characteristics.

  2. Synchronized Zoom Across Multiple Areas: An alternative would be to implement a zoom synchronization function for the x-axis that works across all individual areas without merging them into one. 

 

with a channel calculation via the pocket calculator, the basic property “Description” is overwritten !?

please allow individual sections (e.g. script and view) of diadem to be operated on separate monitors.

 

In the report area of a 2d axis system, it is possible to select a common x-axis for all channels.
Please also enable this function of a common x-axis in the view area for a 2d axis system

 

In the current DIAdem version (2024), when the display format of the LabVIEW graph axis is configured to "SI Notation", the data will be interpreted wrongly when export them to DIAdem report. For example, the x-axis of the following graph is set to "SI Notation": 

hongcc1_0-1733152719082.png

 

When exporting to DIAdem, the graph is plotted incorrectly: 

hongcc1_3-1733153843066.png

 

hongcc1_1-1733152789642.png

 

If look at the raw data (compare to Export Data to Excel feature):

hongcc1_2-1733152914340.png

 

Because DIAdem ignores the pico and nano scale, the first 12 points in pico scaling are appeared larger than the rest of points in nano scale. 

 

This feature should be very important because there will be more Instrument Studio measurement plugins UI are developed in LabVIEW. "Export Data to DIAdem" is a good use case of connecting workflow from Instrument Studio to DIAdem. 

Analyze the timing and transition of single or multiple pulses like LabVIEW express VI: 

 

hongcc1_1-1733149290329.png

Or quick analysis to calculate the rise and fall time for 10% to 90% and vice versa from the peak: 

hongcc1_2-1733150037868.png

Or the step response analysis like Matlab stepinfo to get more information about the rising step such as settling time, peak time, overshoot, undershoot, etc. 

 

This will be very handy for quick understanding of signal when acquired waveform from other LabVIEW+ software such as Flexlogger and Instruments Studio.



After thoroughly reviewing the DIAdem help documentation, it seems there isn't a built-in command, like schememeasstop(), to programmatically stop measurements.

The objective is to automate at least two consecutive DAC measurements in NI DIAdem. While the first DAC measurement can be started and stopped using digital inputs, the current process still requires manual intervention. Specifically, the operator must press the "Stop Measurement" button on the DIAdem toolbar to end the first measurement before the second can be started.

In der Anzeige View können die anzuzeigenden Eigenschaften der Legende eingestellt werden, wie z.B. CursorX und CursorY. Die angepassten Einstellungen werden aber immer nur für den ausgewählten Bereich gespeichert. Jeder weitere Bereich muss erneut angepasst werden. Ebenso nach Neustart von Diadem. Die angepassten Einstellungen werden nicht gespeichert.

Many of my metadata properties are very long and do not display well in the DataFinder search results view.  I would love for an option to be available to "word wrap" the titles (similar as is available in the DIAdem VIEW legend settings).  

 

In my attached image, I can not see the title of my properties with the default length, and if I make the length long enough, I cannot see very many properties per page!

JuliaDawkins_0-1714144203688.png

 

When dealing with large TTL data log files (approximately 25 Gb or more) in DIAdem using BUS CAN converter, users have reported encountering freezing issues during the conversion process. 

Furthermore, if you check the Task Manager, it may show that DIAdem is not responding, which typically implies that the software has crashed. This lack of feedback makes it challenging to determine whether DIAdem is functioning correctly.

However, despite the apparent freeze, the conversion process eventually completes successfully after approximately 30 minutes.

 

To improve the user experience, it would be beneficial for DIAdem to provide clearer feedback during large file conversions, such as a progress indicator or status updates. This would help users understand that the software is indeed working and prevent unnecessary concern about crashes.

 

Thanks in advance!

In the report area you can select a common x channel.

This option would also be very helpful in the view area.

 

 

 

 
 

Some Python plotting modules have an HTML output for Python graphs (Bokeh and Plotly, for example), and Plotly specifically has some really cool interactive HTML plots.  It would be great to have a simple HTML Display Type in VIEW to be able to view these plot outputs!

EuroNCAP has introduced a new injury criterion for the THOR dummy, which would be very handy to have as a function native to Diadem through the Crash Analysis Toolkit

 

https://cdn.euroncap.com/media/67886/tb-035-brain-injury-calculation-v10.pdf

Other IDE programs (like PyCharm or Visual Studio Code) have an "autosave" feature which is very useful! After a certain amount of time, the script you are working on is auto-saved (if it has been saved).  

I understand that DIAdem is not a console application, but a GUI-application.  Therefore, a python command like

 

val = input("Enter value: ")

 

will not work because sys.StdIn and sys.StdOut are not available.  However, this isn't well-documented and the error given isn't very helpful. 

 

There are other more complicated outputs that I have seen in the console area of my regular Python IDE (I usually use PyCharm) that fail with very unrecognizable errors in DIAdem Python, usually a string of errors in many scripts that looks very intimidating!  

 

It seems that DIAdem is just grabbing the simple "print" statements from Python scripts, and nothing else works.  This would be ok if these errors could be bypassed somehow?

The VIEW "Layout Parameters" setting "Word wrap" value is not persistent and does not seem to be saved to the DIAdem desktop "Desktop.DDD" file.  I think it should either be persistent or added to the saved parameters for the Desktop.DDD file. So if I change it, and close/reopen DIAdem, the setting is always changed back to deselected.  

 

The workaround is adding "View.Settings.UseMultilineLegend = 1" to some startup script which is fine, but I'd prefer it to be persistent upon changing it.

 

Please implement dark mode in Diadem. 

All my other softwares are setted up to dark mode, when I exchange to Diadem is like going out of a dark tunnel in sunny days.

 

I'm a student in my last year of studies and I'm not that good working with scripts.

I work with Diadem to analyze my real-time data,  and when i import the excel files ( One year of data gathered in excel files separately ) into Diadem my columns change automatically to text format So i guess the solution in to write a script to convert my channels into Numeric format?

  Capture.PNG

I would like a feature where you can add extra paths in DIAdem's Python implementation for user-specific Python library directories.

 

In Visual Studio Code you can edit the settings.json to add paths to:

  • python.analysis.extraPaths (for importing)
  • python.autoComplete.extraPaths (for autocompletion)

JoshRew_0-1642107684799.png

 

So stuff imported from "C:\Repositories\Python\MyLibraryOther\__init__.py" is directly visible on import alongside stuff in SitePackages:

JoshRew_1-1642107684803.png

 

I've been able to add further locations to the active DIAdem Python Path via to use programmatically:

import site
site.addsitedir('C:/Repositories/Python/')

 

With that, I can "use" the script contents from both "Other" and "Site-Packages" items:

JoshRew_2-1642107685010.png

 

But currently I can only "see" items located within the Site-Packages folder:

JoshRew_4-1642107684831.png

 

-Josh Rewerts

Having Python as a scripting language is great, however, Python is not (yet) supported to develop user dialogs. Dialogs must be developed using VBS. While a Python script file can be run from a dialog using VBS, this leads to many Python files containing snippets of code. Updating the approach for GUI (SUD) development would be a welcome improvement.