Collecting min/max peaks in dasylab? Can this be done?

[TomRizzo]

In that case you can try to use the signal adaptation and sync it with the other channels.  The MinMax module blocks the flow on the output untill the next values comes.

WHat we usually do, we create a 4 channels file for the minimum and maximum each.  Then we choose to eiter reset the min and max with an action list or set the block size accordinly.

The file will be, of course as big as the sample rate on the oputput.

You might need to rethink a litle the process on how to save this values

[KraM8]

This is how I set it up now, and it seems to be working.  But you might have mentioned this in your previous post but I am way to many values.   I set it up with the 4 channels, LVDT 1 is set to min, the other to max, and same on LVDT 2.  But its sampling rate is huge and I can't cut it down because I am afraid I will miss some important points.

So the min/max module can't be adapted for my use?   Or is the signal adaption used with the min max module?  I am not sure if I can set that up.

[KraM8]

Not to mention my min/max will be constantly varying.  Thats why I though the min/max might work the best.

[CJ_Butler__DASYLab_Pro]

Here's a way that should work... remember, the actual time stamp for the max/min will be force to be the same. You'll get the data values for both LVDTS, but the time stamp will be for the first LVDT. 

This also assumes that both sensors are doing about the same thing... the same number of min/max in about the time period. If one is running  a lot faster than the other, then you need to store them into different files. 

Right after the Min/Max, put a Signal Adapt (Special Module Group) and configure it to ADAPT TIME.

Then connect to the Write module.

The List Display is a DISPLAY module, and has the same restrictions as the Write Data Save to ASCII module, so it allows you to verify what will work or not, and to see what rows are being written. 

[KraM8]

I set it up as you showed, and it does work. I don't have any running problems with.  However, the 2nd LVDT number gradually increases (I have it set to 6 decimals places, and for our job, 4 is typically what we need).  Both of the sensors will be doing about the same thing.  I am not sure I understand the idea of a timestamp.  Are you saying that the time it records for  LVDT 1 will also be the time it records for LVDT #2?   So is it taking the ACTUAL peak of LVDT 2 and just putting it like it happened at the same time LVDT 1 peaked?  Also why the gradual increase of LVDT 2?

What happens if I hooked up a min/max module to its OWN LVDT; and then had 2 write files. One for each incoming data stream instead of bringing 2 LVDTs into one min/max module.

What you just showed me works pretty good though.

[CJ_Butler__DASYLab_Pro]

Only the time stamp for the second LVDT is affected. Not the data value. The Adapt module is forcing both inputs to the same time stamp, and uses the first input as the reference channel time stamp. The Data is not affected when you use the ADAPT TIME setting.