Process Analyst View Issue ,,, Trends Issue

Hi Mohammed,

That seems strange that it only displays when clicking. All "clicking" on the background/pen does in the PA is activate the pen and "select" it - put that ghost border around the line. No additional retrieval is triggered.

Retrieval occurs naturally if you have auto-scroll on (which you do) and during manual scrolling far enough in the view.

My first thought is that you have 20 pens in this display which will all be requesting data from the trend server at the same time and it is coincidence that it is coming back near when you click/scroll. Your view will be attempting to retrieve 6000 samples 20 x 300 and I see it is a 10 minute span, but I do not know what your sample periods are. If they are too small (lots of samples to process) perhaps this is contributing to slow retrieval.

Some questions for you:

1. Is this view loaded from a PAV file, created via cicode, or pre-configured within a page itself?
2. I notice every pen is "in error", have you diagnosed that? (Check trend server logs)
3. Is the trend server busy

To try, create a PAV file with just this one pen(trend) in it and load it, does it display instantly?

Also, can you turn sample markers on. You may as well add trend cursor as well.

Hi Mohammed,

That seems strange that it only displays when clicking. All "clicking" on the background/pen does in the PA is activate the pen and "select" it - put that ghost border around the line. No additional retrieval is triggered.

Retrieval occurs naturally if you have auto-scroll on (which you do) and during manual scrolling far enough in the view.

My first thought is that you have 20 pens in this display which will all be requesting data from the trend server at the same time and it is coincidence that it is coming back near when you click/scroll. Your view will be attempting to retrieve 6000 samples 20 x 300 and I see it is a 10 minute span, but I do not know what your sample periods are. If they are too small (lots of samples to process) perhaps this is contributing to slow retrieval.

Some questions for you:

1. Is this view loaded from a PAV file, created via cicode, or pre-configured within a page itself?
2. I notice every pen is "in error", have you diagnosed that? (Check trend server logs)
3. Is the trend server busy

To try, create a PAV file with just this one pen(trend) in it and load it, does it display instantly?

Also, can you turn sample markers on. You may as well add trend cursor as well.

Firstly, Thanks for your reply.

I believe it is not a data request issue because once I click on the view all the trends in the equipment will show the trend and everything will be normal.

1- This view is the default view of the process analyst, its working principle is that you select an equipment from the tree on the left side and it adds all configured trends in that equipment type to your pane under the trend view.

2- this error is because i am not connected to the actual network and there is no real reading, but I am sure it happens also if I am connected to the network that contains those tags values.

3- the trend server is not busy.

Note : This is simulation for values to make sure the Unit Error is not the issue.

and as you see this equipment only have one pen and it behaves the same as if any other equipment is selected.

Bradley  

ok, that is certainly interesting. I can see it has retrieved the pen info, and certainly no data is coming through.

I think we need to see what the cicode is doing and what events are being handled from the PA. This maybe too much for a forum post and will require submitting your project via support so we can repro and debug.

In the meantime, I would approach looking at your project as follows:

1. On the Process Analyst object, go to the Main property page and:
   1. Can you confirm the DisplayRefresh, DataRequest, InfoRequest rates please?
   2. Can you confirm the Max number of samples
2. Do you have any calls to BlockRepaint in your process analyst cicode
3. Are you handling the PenCreated or PenSelectionChanged events in cicode and running any special code that may be responsible for the behaviour observed