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.
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.
I've noticed that the easiest way to relate a channel calculation back to the original channel is to append to the channel name:
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...
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.
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.
When developing scripts, I frequently add channel groups for analysis results, using
However, when re-running the scripts, successive groups "analysis1", "analysis2" etc. are created. This is a handy feature that I should not want to miss at some times, BUT
at other times I want to skip the creation of new channel groups. As a work-around I litter my code with 'exist'-statements such as
If not call data.root.channelgroups.exists("analysis") then
Set oResGrp = data.root.channelgroups("analysis")
Now, my suggestion is to add a command such as "AddOrReplace" or "Use", which would use the existing group if it exists and creates a new group if not. Pretty much the same behaviour as with the calculator, where
CH("NewChannel")= CH("oldChannel") will create a new channel or overwrite an existing one.
would work as we know it and
would create a new object or use the existing one.
Alternatively one could supply an optional paramter to the .Add-method like
as default using the well-known behaviour whereas
would change to create or replace.
Obviously the same would come in handy for channels or other objects that use an .add-method.
I would like to export the table from the Navigator search pane into Excel or a CSV file so we can use that in a report (Word) as an overview of performed measurements.
We can quite good configure that table so let's make use of that.
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.