DIAdem Idea Exchange

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

I was using an “assignment” channel as the “ChnEventTrueChn” for “ChnEventCreateFilteredTrueChn” and was really hoping the result channel would also be an assignment channel, but no, it’s not.  

 

My original assignment channel is matched up nicely with some text values, so it would be really helpful to have those values “carry” if I execute a function or calculation on the numeric channel.

 

FYI, Brad Turpin provided a workaround until this is implemented that works just fine for me:

Clone your assignment channel and use the clone for the ResultChannel channel in the “ChnEventCreateFilteredTrueChn”  function.

 

Set OldGroup = Data.Root.ChannelGroups(1)

Set NewGroup = Data.Root.ChannelGroups(2)

Set OldAssignChannel = OldGroup.Channels(1)

Set NewAssignChannel = NewGroup.Channels.AddChannel(OldAssignChannel)

Call ChnEventCreateFilteredTrueChn(NewAssignChannel, ChnEventList, OldAssignChannel, ChnEventFalseValue)

 

 

Most dialog editors I've used have a "timer" function of sorts, and I would like the DIAdem SUD dialog editor to have a "timer" function.  This would allow an event to happen at a specified interval (example 1 second) 

 

The simplest case would be to simply display the current date/time on a user dialog, and this is not possible right now without using worker objects, and I feel silly using a worker object just as a time-keeper! I would use this function often.

 

 

When I right-click on a REPORT sheet, I have the option to "manage..." sheets.  There is a similar but less functional dialog available in VIEW.  I would like all of the functionality of REPORT "manage..." sheets in VIEW.

In some cases, the visual interface becomes very confusing and mixed up. Is it possible to develop a function to form layers like in the dialog editor? 

It would simplify the work in complex dac plans very much.

Add the ability to decode relative paths for video files within View and TDV files AND make it the default setting.  Adding an option box to the "Select Video File" dialog to allow absolute or relative path decode.  Also have the system recognize a relative path (i.e. ".\video.avi").  This may require a new TDV-Path variable.  This allows moving large video/data views to networked based folders allowing other engineers/customers to review/manipulate the data.

 

 

When you have loads of pages in VIEW and would like to print a specific one, there is

 

1. no option in the print menu to print "selected page", and

2. no way to find out which page number you are currently on, except for counting manually or per script.

 

Even in the "manage" menu you get no information about it. So any ID link would be great.

We've suggested this in person, but thought I'd finally post it to the site.

Despite it being called the Data Portal, we'd like to have the capability of docking DIAlogs of any purpose into the data portal as new tabs alongside 'Structure' and 'List' views.

 

Non Modal DIAlogs tend to cover some portion of the active window, so tend to get in the way and end up being closed and re-opened by the user despite our resizing and overlapping of the Data Portal.  Allowing docking into the Data Portal would allow for convenient sizing (REPORT/VIEW tabs are already re-sized around the data portal) and movement with the application from one screen to another.

 

The primary example of functionality advancement for us would be our 'Page Browser', which is much like the View/Report 'manage' function, but works for both, allows filtering on both, allows for convenient rearranging of sheets to any other position, and can remain up at all times so users can simply jump to or flip to sheets without re-opening the 'manage' function or slowly tabbing/scanning through all sheets.

 

Obviously, it's up to you to decide the implementation...having some sort of tab manager at the very top or bottom that switches the 'Data Portal' out entirely for a 'Sheet Portal' and other custom DIAlog options & names could also work, or some other implementation entirely, but as the other tab manager already exists (but only ever contains 2 tabs), I feel would likely be less of a massive UI overhaul.

 

-Josh

What about an extended grouping feature like the recently implemented collapsing/expanding possibility for subs or functions? I would like to see it extended to loops, case structures or just arbitrary chunks of script to make longer scripts clearer and easier accessible.

Substantially beef up the ability to pipe data from labview into diadem.

 

 

  • Importing text arrays/tables
  • importing graphs, with annotations
  • greater control over text values : make them easily reordered and renamed, perhaps make them polymorphic to allow cluster usage, that way order isn't important and changes to the layout won't change the location of the variable in the array/cluster
-Regards
JW

 

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

 

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. 

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).  

Currently, ONE python engine is started with each instance of DIAdem.  This behavior is not well-documented and comes with limitations. 

 

For example, if I have an imported function ".py" script called "MyHelperFunctions.py" and import this into another script, the function is only loaded once.  If I make edits to this function, and save the file, the edits will not be available until I close/reopen DIAdem!

 

I suggest having multiple embedded python engines at the same time.  And this would enable DIAdem to always be ready for a python call but still retire a python engine that was bloated.

 

At the least, having a script command to spin up a new python engine would be very helpful for me!

I use n Systems Y-axis viewing a lot, often with groups of channels defined into common axes with Curve Related Scaling.  The only way to save this is in a TDV file, which locks it into that specific layout.  I cannot share a scaling definition with another View area or sheet in the same layout - I have to manuall enter all the details again every time.  

Would it be posisble to allow Curve-related Scaling settings to be sharable in some way, so they can be more easily re-used both within a single session, and across sessions, independently of the complete TDV layout?

I would like a tool that would help identify noise spikes in my data, so that they may be set to NO VALUE or carefully interpolated.  In the attached example, I have two torque spikes in my data that are significantly higher than the mean.  If I were only looking at one file, I would simply "Set Flags" in VIEW, then "Flags: Remove Data Points". However, I am reviewing dozens of files with several channels of interest.  

 

Peak data points are the most damaging to the components under test, so it is important that we keep the real events and reject the noise.  

 

Concerns with other peak / spike removal options:

  • Manual Set Flags -> Flags:  Remove Data Points; time required
  • ANALYSIS -> Event Search -> Event = Window -> Upper Limit:  In other data files, I have real events with values higher than the noise in this data file.  
  • ANALYSIS -> Digital Filters or Smoothing:  This will change all of the data - it will likely narrow the peak-to-peak of my other data and interpolate my noise spikes, adding damage that is not actually real.  I only want to remove a few data points in the channel data. 

nCode Glyphworks has a nice Spike Detection Tool that uses 6 available algorithms to detect spikes.  Once it identifies them, it allows the user to see them, prior to performing any actions - this is important, because it allows the user to identify if they are real or noise, prior to taking action.  

Download All

In REPORT, you have the option of using a "Joint x-channel", which allows REPORT to use the x-channel of the first curve as the x-channel for all other curves in a 2D axis system.

 

I would like this exact same functionality in VIEW.

I really love all of the Event search functions and commands, but I wonder if perhaps you could make a class out of this so we'd have intellisense available.  Also, many of the commands are very similar and difficult to find.

 

event.png

Is it possible to add some image processing (offline) to video recordings (without programming)?

Maybe to jump to the time where something changed?

Or an OCR functionality when filming alphanumerical displays?

I've been struggling with setting up contour plots in the report the way that I would like to and it is mainly due to the limited ability to customize the color legend and isolines. I've posted about this in the normal forums and no one has found a way to set up the plots the way I would like. Relevant post can be found here: https://forums.ni.com/t5/DIAdem/Contour-Color-Legend-Modification/td-p/3719857

 

I would like to see the following options for the contour plots in reports:

  • Option for color legend to display first, last, and every nth symbol. 
  • Option to have two contour tables; one for the colors/legend, one for isolines. 
  • Ability to adjust where the symbol text is displayed relative to the color legend
  • Option in the dialog box to select how many colors are in the palette (i.e. 16, 32 or 64), this can be done via script but not through a dialog.

Add a tool in DIAdem that works seamlessly with the NI created databases made using NI TestStand  and its Generic Record Set Schemas.

 

Yes, I know you can use SQL for this, but who really wants to use SQL when it could be done all within the NI ecosystem?