Re: [foxboro] ATS dropping out - Followup
- From: Terry Doucet <doucet427@xxxxxxxxxxx>
- To: <foxboro@xxxxxxxxxxxxx>
- Date: Fri, 16 Sep 2011 06:20:38 -0400
To turn on the variable at boot up, it is easy to edit fvcmds or dmcmds file
and change "disable monitor" to "enable monitor" then restart FV or DM.
We built a display with all AW's and WP's WPIDLE parameter and had the service
people look at that display after something was changed. A few times we saw
the WPIDLE time go to zero, and stay there so we knew that something was not
right. We wanted to see this number mostly in the 90's. If you were doing some
a-periodic task (eg checkpoint on host) you could expect to see it dip while
the task was happening. A format of a floppy drive (remember them) would drop
WPIDLE to zero for the duration of the format. If you put an extremely busy
display on a WP (500 variables or so) then that WP's WPIDLE could dip to the
70's while the display was on the screen.
Terry
> From: Alex.Johnson@xxxxxxxxxxxx
> To: foxboro@xxxxxxxxxxxxx
> Date: Fri, 16 Sep 2011 04:07:40 -0500
> Subject: Re: [foxboro] ATS dropping out - Followup
>
> From B0193MQ:
>
> Accessing WP51/AW51 CPU Idle Time and RAL for DMs
> You can access the CPU idle time for a workstation and RAL for DMs by reading
> the following shared variables:
>
> WPIDLE<stationlbug> An Object Manager shared variable of type float
> containing the current CPU idle time for the station.
>
> DMLEVEL<dmname> A long integer Object Manager shared variable containing
> the current RAL for each DM. This variable may be trended
> or used on a user-built display.
>
> To conserve CPU cycles, by default the above variables are not set by
> FoxViews/DMs and are initialized to -1.
>
> To turn on the setting of these variables by FoxViews/DMs, run the following
> command for each FoxView/DM:
> pref -dmname dmcmd "enable monitor"
>
> To turn off the setting of the above shared variables, run the following
> command:
> pref -dmname dmcmd "disable monitor"
>
>
> You can use 'pref' to turn this on or off, but I suspect you could also add
> the monitor command to user.init to make it happen at boot-up for all DMs. I
> don't know the loading impact of that though I doubt is it large on newer
> machines.
>
>
> Regards,
>
> Alex Johnson
_______________________________________________________________________
This mailing list is neither sponsored nor endorsed by Invensys Process
Systems (formerly The Foxboro Company). Use the info you obtain here at
your own risks. Read http://www.thecassandraproject.org/disclaimer.html
foxboro mailing list: //www.freelists.org/list/foxboro
to subscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=join
to unsubscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave
Other related posts:
