DMD2.7.4 PID Viewer Data Logging

[stgislander]

I had originally posed this question in the Automation-Direct forum.
https://community.automationdirect.com/s/profile/0053u000004OGvOAAW

I'm having the same issue again.  DMD will not remember the changes to the logging time interval.  I have Current View, All Open Views, and New Views checked.  I change the logging interval from 100ms to 50ms.  After I press OK I go back in and check my values.  All have reverted back to the originals.

What is different this time is that DMD is running on a laptop on the west coast, and I am remotely logged into the laptop from the east coast.

Could remote access be the issue?

[franji1]

I tried it and it worked for me. ***EDIT*** in Designer 2.9.4

Here's the steps I took.

I had a PID View up from the PID1.dmd sample and it was configured to archive every 1.000 seconds.  I turned on logging by hitting the REC button for about 10 seconds. See the data in the attached SimPID1.TXT (I had to change the extension from .csv to .txt).  The rows' time/stamps are approximately 1 second apart.

With the PID View still up, I then went to the PID View Options for All Views and changed the Export/Logging Method log interval to 100ms.  I made sure All Open Views was checked (in addition to New and Current).  I turned on logging by hitting the REC button for about 10 seconds again.    See the data in the attached SimPID2.TXT.  The rows' time stamps are approximately 100ms apart, as I configured in the PID View Options dialog.

I then closed and re-opened the project and logged the data a third time, keeping the interval at the previous 100ms, and that's what it logged (see attached SimPID3.TXT).

Please describe what steps you took and what you are actually seeing.   If you are in the middle of recording a log, I don't think that new interval will be applied until you stop that recording then start a new recording (is that what you are seeing?)

[stgislander]

I followed your steps.  My setup initialized at 100ms so my first record was at that rate.  I generated a 10 second record.  When I opened my .txt file, I had 9-10 sample points per second.

For my second record, I decreased the interval to 1s and made a 10 second record.  In my .txt.file I had 10 sample points for the entire record.

For my third record, I increased  the interval back to 100ms and made a 10 second record.  In my .txt.file I had 9-10 sample points per second.

For my fourth record, I increased  the interval to 50ms and made a 10 second record.  In my .txt.file I still had 9-10 sample points per second.

Could it be that a 50ms interval is too high?

[franji1]

I tried to set the Trend View option to be less than 100ms and it warned me that Designer UI may not be able to keep up.  I did not see that message with the PID View option, however (but the same limitation is there).

I did not see any code "gating" that, but it appears you don't want to go faster than 100ms.  Your Designer UI (especially if you are remoting in) can get sluggish.

[franji1]

Turn ALL STATUS OFF except for your one specific PID view - that will help keep the comm flowing and logger logging.

[stgislander]

Okay.  You did not see a warning either.  Good to know.  Thanks for the assist.