DIAdem Idea Exchange

It might require too much computation time but I was wondering if the DataFinder could calculate and store such characteristic values as channel min/max during it's index. I would find this really helpful.

If it is not practical to do on the fly, how about an extra option on the context menu in Navigator - in addition to 'Re-Index File' etc there would be 'Calculate Characteristic Values' which would then calculate and save the valeus back to the files for the file/folder/drive selected. 

Rather than a channel that has a "fixed" value (numeric or string), this new "calculation channel" type would be a function of other channels.  Currently, if Channel3 = Channel1 + Channel2, and then I change the values for either Channel1 or Channel2, I have to re-execute the calculation

ChnCalculate("Ch(""Channel3"") = Ch(""Channel1"") + Ch(""Channel2"")")

Now, if there was a "calculation channel" where I could define Channel 3 as "Channel1 + Channel2", I wouldn't need to perform this re-execution! 

Another way to explain is to have a channel that works like Excel calculation cells.  The cell calculation stays the same, and when the input cells change, the result cell is automatically updated. 

I'm not sure if I explained this well, please ask for clarification if necessary. 

Having network directories available in the DataFinder is a great tool. However, if a network directory is added as a default search locations AND the network cable is unplugged, DIAdem will hang for a very long period of time. Windows commands are used to query for network locations. If not connected to the network, the timeout for these commands is quite large. 

While this is technically expected behavior, it is not ideal software functionality to hang if a network cable is unplugged.

Luke W

I've noticed that the easiest way to relate a channel calculation back to the original channel is to append to the channel name:

iH_EngSpeed_rpm

iH_EngSpeed_rpm_RegX

iH_EngSpeed_rpm_RegY

iH_EngSpeed_rpm_1

iH_EngSpeed_rpm_2

iH_EngSpeed_rpm_Filtered

Filtering for *engspeed, or *engspeed_rpm will return all of the above channels, but in my experience I rarely want to see all the additional channels...With enough channels, it can effectively obscure the channel you're looking for!

The simplest way I can think of to obscure these with the current functionality would be to have a stop character ("\"?) to prevent the filter from grabbing anything beyond that point:

*EngSpeed_rpm\ would return anything ending in *EngSpeed_rpm

Another way would be to get rid of the assumed * at the end of the filter, forcing people to put one on themselves when necessary (but that would be changing the current functionality and would likely confuse users at first):

*Engspeed_rpm would return anything ending in *EngSpeed_rpm

*EngSpeed_rpm* would return everything with EngSpeed_rpm inside it

This would also be nice for looking for channels that end in something, like anything ending in *nm\ rather than anything with nm in the name...

Simplify how to create a DataPlugin. I should be able to define a binary layout like a telemetry stream and directly assign channels.

For example, A new GUI would be created. I define the telemetry stream which has three floating point numbers then an integer, repeat. Assign channel names Volts, Amps, Power Out, and Setting. Perhaps set the built-in properties. Press a button the plug in is automatically created.

Create SQL interface for the datafinder.