Experimental Physics and
Industrial Control System

Mark Rivers via Tech-talk <[email protected]> · Thu, 5 Sep 2019 10:53:59 +0000

Hi Amish,

> EPICS_BASE_LIB=/usr/local/epics/base/lib/linux-x86
> EPICS_BASE=/usr/local/epics/base
> EPICS_HOST_ARCH=linux-x86
> EPICS_CA_ADDR_LIST=127.0.0.1
> EPICS_DISPLAY_PATH=/home/pelcon/Apps/epics/modules/areaDetector/ADCore/ADApp/op/adl
> EPICS_BASE_BIN=/usr/local/epics/base/bin/linux-x86
> EPICS_ROOT=/usr/local/epics
> EPICS_CA_AUO_ADDR_LIST=NO

I assume these are all of your EPICS environment variables?  If so, I see 2 problems.
1) You have misspelled EPICS_CA_AUTO_ADDR_LIST, you left out the T in AUTO.
2) You have not set EPICS_CA_MAX_ARRAY_BYTES.  Set that to 20000000 (20 million) to be safe with your cameras.  The NDStdArrays plugin will not work without that being set.  It is documented here: https://areadetector.github.io/master/ADViewers/ad_viewers.html<https://areadetector.github.io/master/ADViewers/ad_viewers.html#epics-ad-viewer-java>

> These are my environment variables, still I have the errors of duplicacy in ImageJ console. [see image3.png]

Those are actually just warnings, and they won't stop things from working correctly, so let's ignore those for now.

> One thing I also noticed is that, when I start acquiring from the camera, a solid green LED showing acquisition is going smoothly is visible but on IOC, I see  "Bad Frame Status: Timeout" (maybe it is due to frame dropping in between??) [see left side of image1.png] at regular intervals when I started the acquisition from MEDM screen [see right side of image1.png]

In order to prevent dropped frames you need to increase some Linux network buffer settings.  I have documented how to do that here.
https://areadetector.github.io/master/ADGenICam/ADGenICam.html#linux-usb-and-gige-system-settings

It can also be helpful to enable Jumbo Frames on your network card. You can do that in your Linux network system settings.

I can see that you have collected many frames OK because the ArrayCounter_RBV on your screen shot is 4816.

> Next, image1.png and image2.png you can also see ImageJ plugins being started and No Display can be seen while the ImageJ log says everything is working fine. Neither the camera goes in acquisition mode (no LED glows up).

Pressing Start in ImageJ only starts the ImageJ display, it does not control the camera at all.  To start the camera you need to press Start on the medm display.  Please send a screen shot of the main medm window after you press Start there. What is the Image rate, i.e. frames/s?

>Have you enabled callbacks on the plugins in question?  NDPluginStdArrays or NDPluginPva for ImageJ, depending on which ImageJ plugin you are using.  NDPluginStats for the histogram plugin.  If you still have problems please send a screen shot of those plugin screens.

You did not send the screen shot I asked for.  Please press the Plugins/All button in medm and send a screen shot of that commonPlugins.adl screen.

> I have epicsV4 installed at ~/epics/epicv4/ but I don't know whether this is sufficient to enable NDPluginStdArrays for ImageJ. Can you please help me on achieving this?

NDPluginStdArrays does not use epicsv4 at all, it only uses standard EPICS Channel Access.

> I am also facing trouble with ADSpinnaker IOC as it does not start from the same template that I am using to start through aravisGigE.

I am not sure what you mean by "template" in this context?  There is an example IOC in ADSpinnaker.

Mark

________________________________
From: Ashish Sharma <[email protected]>
Sent: Thursday, September 5, 2019 4:02 AM
To: Mark Rivers
Cc: Mark S. Engbretson; tech-talk
Subject: Re: Image display on ImageJ not showing up. [AravisGigE, areaDetector, ADViewer]

Hi Mark,

Thanks for your elaborate response.

>You need to set these environment variables

>EPICS_CA_AUTO_ADDR_LIST=NO

>EPICS_CA_ADDR_LIST=xxx.xxx.xxx.xxx

EPICS_BASE_LIB=/usr/local/epics/base/lib/linux-x86
EPICS_BASE=/usr/local/epics/base
EPICS_HOST_ARCH=linux-x86
EPICS_CA_ADDR_LIST=127.0.0.1
EPICS_DISPLAY_PATH=/home/pelcon/Apps/epics/modules/areaDetector/ADCore/ADApp/op/adl
EPICS_BASE_BIN=/usr/local/epics/base/bin/linux-x86
EPICS_ROOT=/usr/local/epics
EPICS_CA_AUO_ADDR_LIST=NO

These are my environment variables, still I have the errors of duplicacy in ImageJ console. [see image3.png]

One thing I also noticed is that, when I start acquiring from the camera, a solid green LED showing acquisition is going smoothly is visible but on IOC, I see  "Bad Frame Status: Timeout" (maybe it is due to frame dropping in between??) [see left side of image1.png] at regular intervals when I started the acquisition from MEDM screen [see right side of image1.png]

Next, image1.png and image2.png you can also see ImageJ plugins being started and No Display can be seen while the ImageJ log says everything is working fine. Neither the camera goes in acquisition mode (no LED glows up).

>Have you enabled callbacks on the plugins in question?  NDPluginStdArrays or NDPluginPva for ImageJ, depending on which ImageJ plugin you are using.  NDPluginStats for the histogram plugin.  If you still have problems please send a screen shot of those plugin screens.

I have epicsV4 installed at ~/epics/epicv4/ but I don't know whether this is sufficient to enable NDPluginStdArrays for ImageJ. Can you please help me on achieving this?

I am also facing trouble with ADSpinnaker IOC as it does not start from the same template that I am using to start through aravisGigE.

Please help me in ADGenICam example ioc creation. If above methods don't work out, I shall try that.

Thanks
-
Ashish

----- Original Message -----
From: "Mark Rivers" <[email protected]>
To: "Mark S. Engbretson" <[email protected]>, "Ashish Sharma" <[email protected]>
Cc: "tech-talk" <[email protected]>
Sent: Wednesday, September 4, 2019 5:25:52 PM
Subject: Re: Image display on ImageJ not showing up. [AravisGigE,       areaDetector,   ADViewer]

Hi Ashish,

> Message: Identical process variable names on multiple servers

These errors a coming because you have more than one network card on your machine, and you are running both the EPICS IOC and the EPICS client (medm) on the same machine.  This is an annoying problem with EPICS, but it is easy to fix.

You need to set these environment variables

EPICS_CA_AUTO_ADDR_LIST=NO

EPICS_CA_ADDR_LIST=xxx.xxx.xxx.xxx

where xxx.xxx.xxx.xxx is the broadcast address of the network you want to use for EPICS Channel Access.  It is typically the public network interface of your machine, rather than one of the private network interfaces.  On my machine I might have private network address of 192.168.0.1 and a public network address of 164.54.160.202.  I set EPICS_CA_ADDR_LIST=164.54.160.255 because the netmask of the public interface is 255.255.255.0.

> I have both ADGenICam and ADSpinnaker built in my system but I tried first wiith AravisGigE after reading T. Cobb's
> comment that it should work with GigEVision camera. Am I mistaken here?
> I found setting up ADSpinnaker setup a bit difficult in comparison to aravisGigE. Can you please help here?

You actually have 4 choices of drivers to use with that camera.

- aravisGigE.  This is based on the aravis package.  It runs on most any version of Linux, and it should work fine.

- ADAravis.  This is also based on aravis, but uses the new ADGenICam base class.  It also runs on most any version of Linux, and it should work.  It queries camera properties more frequently than aravisGigE and so has performance problems with some cameras because aravis does not currently properly cache camera registers.  The aravis developer is working on this problem.

- ADSpinnaker.  This uses the new Spinnaker SDK from FLIR.  It runs on Windows and Linux.  The SDK is built with very recent version of gcc so they only claim it works on Ubuntu 18.  In fact it may work on Ubuntu 16, and it has been tested on RHEL8.

- ADPointGrey.  This uses the older FlyCap2 SDK from FLIR/Point Grey.  It runs on Linux and Windows.  The version of the FlyCap2 SDK included in ADPointGrey runs on RHEL7, although the more recent versions of the SDK require Ubuntu (16 or 18?).

> Still I am unable to see the ImageJ display and NX, NY, NZ still being blank with 0.0 Frames/s. [ Duplicate issue of PV in ImageJ is still there even after EPICS_CA_ADDR_LIST setup].

Are there any errors in the ImageJ log window?

> Also the medm screens does not show any histogram etc. plots however, it seem to acquire from camera. [I have enable SCIPLOT in medm installation and commented out Xrtgraph]

Have you enabled callbacks on the plugins in question?  NDPluginStdArrays or NDPluginPva for ImageJ, depending on which ImageJ plugin you are using.  NDPluginStats for the histogram plugin.  If you still have problems please send a screen shot of those plugin screens.

Mark

________________________________
From: [email protected] <[email protected]> on behalf of Ashish Sharma via Tech-talk <[email protected]>
Sent: Wednesday, September 4, 2019 6:04 AM
To: Engbretson, Mark S.
Cc: tech-talk
Subject: Re: Image display on ImageJ not showing up. [AravisGigE, areaDetector, ADViewer]

Hi Mark,

Thanks for your response.
EPICS_DISPLAY_PATH setup could recognize the missing .adl files and that error has gone but the follwing long list is still appearing as soon as I am opening my camera link in medm,

Wed Sep 04 14:44:02 IST 2019
medmCAExceptionHandlerCb: Channel Access Exception:
  Channel Name: Unavailable
  Native Type: Unavailable
  Native Count: 0
  Access: Unavailable
  Host: Unavailable
  Message: Identical process variable names on multiple servers
  Context: Channel: "13ARV1:cam1:Gain", Connecting to: 169.254.0.2:5064, Ignored: 10.1.15.37:5064
  Requested Type: TYPENOTCONN
  Requested Count: 0
  Source File: ../cac.cpp
  Line number: 1308

Wed Sep 04 14:44:02 IST 2019
medmCAExceptionHandlerCb: Channel Access Exception:
  Channel Name: Unavailable
  Native Type: Unavailable
  Native Count: 0
  Access: Unavailable
  Host: Unavailable
  Message: Identical process variable names on multiple servers
  Context: Channel: "13ARV1:cam1:DataType_RBV", Connecting to: llrf-Control.local:5064, Ignored: 10.1.15.37:5064
  Requested Type: TYPENOTCONN
  Requested Count: 0
  Source File: ../cac.cpp
  Line number: 1308
.............

I have both ADGenICam and ADSpinnaker built in my system but I tried first wiith AravisGigE after reading T. Cobb's comment that it should work with GigEVision camera. Am I mistaken here?
I found setting up ADSpinnaker setup a bit difficult in comparison to aravisGigE. Can you please help here?

Still I am unable to see the ImageJ display and NX, NY, NZ still being blank with 0.0 Frames/s. [ Duplicate issue of PV in ImageJ is still there even after EPICS_CA_ADDR_LIST setup]

Also the medm screens does not show any histogram etc. plots however, it seem to acquire from camera. [I have enable SCIPLOT in medm installation and commented out Xrtgraph]

Please help.

Thanks.

-
Ashish

________________________________
From: "Engbretson, Mark S." <[email protected]>
To: "Ashish Sharma" <[email protected]>
Cc: "tech-talk" <[email protected]>
Sent: Wednesday, September 4, 2019 3:32:41 PM
Subject: Re: Image display on ImageJ not showing up. [AravisGigE, areaDetector,        ADViewer]

First of all, you do not have the EPICS_DISPLAY_PATH variable set that points to the location of the adl files in ADCore.

If you are using a FLIR camera, you should probably be using just the GenICam and ADSpinnaker directories, not the Aravis ones.

The duplicate PV's are caused my most OS's these days having more than 1 ethercard, or virtual ethernet cards. You normally solve this by setting the EPICS_CA_ADDR_LIST to a single ip # ( or even to 127.0.0.1) and setting EPICS_AUTO_ADDR_LIST to NO

On Sep 4, 2019, at 04:26, Ashish Sharma via Tech-talk <[email protected]<mailto:[email protected]>> wrote:

Dear all,

I am trying to configure and use FLIR BFS-PGE-16S2C-CS camera for beam viewing application. This camera has GigEVision interface.
My system has Ubuntu 16.04, 32-bit version.
Successfully tested Acquisition app of Spinnaker SDK to capture 10 images.
I have installed AreaDetector module successfully and also configured the aravisGigE module of areaDetector. arv-tool-0.6 successfully recognized my camera and using the following link I was able to generate the .template file, .edl, -feature.edl, and .adl files successfully.

http://controls.diamond.ac.uk/downloads/support/aravisGigE/0-1-9/documentation/doxygen/index.html

I then added the following to my st.cmd file in aravisGigE/iocs/aravisGigEIOC/iocBoot/iocAravisGigE

aravisCameraConfig("$(PORT)", "FLIR-19308820")
dbLoadRecords("$(ARAVISGIGE)/db/FLIR-19308820.template","P=$(PREFIX),R=cam1:,PORT=$(PORT),ADDR=0,TIMEOUT=1")

This is corresponding to my Camera ID.
then upon running ./start_epics it loads the db from template (~ 1202 PVs).

Next I installed the MEDM package successfully and ran

medm -x aravisTop.adl

It starts the top menu and when I select my camera from drop-down, (infact any of the listed cameras), it gives following console output simultaneously opening the control page for camera with features listed as well:

MEDM Version 3.1.14: Loading aliased fonts.................

compositeFileParse: Cannot open file
  filename: ADSetup.adl

compositeFileParse: Cannot open file
  filename: ADPlugins.adl

compositeFileParse: Cannot open file
  filename: ADShutter.adl

compositeFileParse: Cannot open file
  filename: ADAttrFile.adl

compositeFileParse: Cannot open file
  filename: ADBuffers.adl

Wed Sep 04 14:44:02 IST 2019
medmCAExceptionHandlerCb: Channel Access Exception:
  Channel Name: Unavailable
  Native Type: Unavailable
  Native Count: 0
  Access: Unavailable
  Host: Unavailable
  Message: Identical process variable names on multiple servers
  Context: Channel: "13ARV1:cam1:Gain", Connecting to: 169.254.0.2:5064, Ignored: 10.1.15.37:5064
  Requested Type: TYPENOTCONN
  Requested Count: 0
  Source File: ../cac.cpp
  Line number: 1308

Wed Sep 04 14:44:02 IST 2019
medmCAExceptionHandlerCb: Channel Access Exception:
  Channel Name: Unavailable
  Native Type: Unavailable
  Native Count: 0
  Access: Unavailable
  Host: Unavailable
  Message: Identical process variable names on multiple servers
  Context: Channel: "13ARV1:cam1:DataType_RBV", Connecting to: llrf-Control.local:5064, Ignored: 10.1.15.37:5064
  Requested Type: TYPENOTCONN
  Requested Count: 0
  Source File: ../cac.cpp
  Line number: 1308

Wed Sep 04 14:44:02 IST 2019
medmCAExceptionHandlerCb: Channel Access Exception:
  Channel Name: Unavailable
  Native Type: Unavailable
  Native Count: 0
  Access: Unavailable
  Host: Unavailable
  Message: Identical process variable names on multiple servers
  Context: Channel: "13ARV1:cam1:ArraySizeX_RBV", Connecting to: llrf-Control.local:5064, Ignored: 10.1.15.37:5064
  Requested Type: TYPENOTCONN
  Requested Count: 0
  Source File: ../cac.cpp
  Line number: 1308

Wed Sep 04 14:44:02 IST 2019
medmCAExceptionHandlerCb: Channel Access Exception:
  Channel Name: Unavailable
  Native Type: Unavailable
  Native Count: 0
  Access: Unavailable
  Host: Unavailable
  Message: Identical process variable names on multiple servers
  Context: Channel: "13ARV1:cam1:ArraySizeY_RBV", Connecting to: llrf-Control.local:5064, Ignored: 10.1.15.37:5064
  Requested Type: TYPENOTCONN
  Requested Count: 0
  Source File: ../cac.cpp
  Line number: 1308

Wed Sep 04 14:44:02 IST 2019
medmCAExceptionHandlerCb: Channel Access Exception:
  Channel Name: Unavailable
  Native Type: Unavailable
  Native Count: 0
  Access: Unavailable
  Host: Unavailable
  Message: Identical process variable names on multiple servers
  Context: Channel: "13ARV1:cam1:ColorMode", Connecting to: llrf-Control.local:5064, Ignored: 10.1.15.37:5064
  Requested Type: TYPENOTCONN
  Requested Count: 0
  Source File: ../cac.cpp
  Line number: 1308

Wed Sep 04 14:44:02 IST 2019
medmCAExceptionHandlerCb: Channel Access Exception:
  Channel Name: Unavailable
  Native Type: Unavailable
  Native Count: 0
  Access: Unavailable
  Host: Unavailable
  Message: Identical process variable names on multiple servers
  Context: Channel: "13ARV1:cam1:ColorMode_RBV", Connecting to: llrf-Control.local:5064, Ignored: 10.1.15.37:5064
  Requested Type: TYPENOTCONN
  Requested Count: 0
  Source File: ../cac.cpp
  Line number: 1308

Wed Sep 04 14:44:02 IST 2019
medmCAExceptionHandlerCb: Channel Access Exception:
  Channel Name: Unavailable
  Native Type: Unavailable
  Native Count: 0
  Access: Unavailable
  Host: Unavailable
  Message: Identical process variable names on multiple servers
  Context: Channel: "13ARV1:cam1:AcquireTime", Connecting to: llrf-Control.local:5064, Ignored: 10.1.15.37:5064
  Requested Type: TYPENOTCONN
  Requested Count: 0
  Source File: ../cac.cpp
  Line number: 1308

Wed Sep 04 14:44:02 IST 2019
medmCAExceptionHandlerCb: Channel Access Exception:
  Channel Name: Unavailable
  Native Type: Unavailable
  Native Count: 0
  Access: Unavailable
  Host: Unavailable
  Message: Identical process variable names on multiple servers
  Context: Channel: "13ARV1:cam1:AcquireTime_RBV", Connecting to: llrf-Control.local:5064, Ignored: 10.1.15.37:5064
  Requested Type: TYPENOTCONN
  Requested Count: 0
  Source File: ../cac.cpp
  Line number: 1308

Wed Sep 04 14:44:02 IST 2019
medmCAExceptionHandlerCb: Channel Access Exception:
  Channel Name: Unavailable
  Native Type: Unavailable
  Native Count: 0
  Access: Unavailable
  Host: Unavailable
  Message: Identical process variable names on multiple servers
  Context: Channel: "13ARV1:cam1:AcquirePeriod", Connecting to: llrf-Control.local:5064, Ignored: 10.1.15.37:5064
  Requested Type: TYPENOTCONN
  Requested Count: 0
  Source File: ../cac.cpp
  Line number: 1308

Wed Sep 04 14:44:02 IST 2019
medmCAExceptionHandlerCb: Channel Access Exception:
  Channel Name: Unavailable
  Native Type: Unavailable
  Native Count: 0
  Access: Unavailable
  Host: Unavailable
  Message: Identical process variable names on multiple servers
  Context: Channel: "13ARV1:cam1:AcquirePeriod_RBV", Connecting to: llrf-Control.local:5064, Ignored: 10.1.15.37:5064
  Requested Type: TYPENOTCONN
  Requested Count: 0
  Source File: ../cac.cpp
  Line number: 1308

Wed Sep 04 14:44:02 IST 2019
medmCAExceptionHandlerCb: Channel Access Exception:
  Channel Name: Unavailable
  Native Type: Unavailable
  Native Count: 0
  Access: Unavailable
  Host: Unavailable
  Message: Identical process variable names on multiple servers
  Context: Channel: "13ARV1:cam1:NumImages", Connecting to: llrf-Control.local:5064, Ignored: 10.1.15.37:5064
  Requested Type: TYPENOTCONN
  Requested Count: 0
  Source File: ../cac.cpp
  Line number: 1308

Wed Sep 04 14:44:02 IST 2019
medmCAExceptionHandlerCb: Channel Access Exception:
  Channel Name: Unavailable
  Native Type: Unavailable
  Native Count: 0
  Access: Unavailable
  Host: Unavailable
  Message: Identical process variable names on multiple servers
  Context: Channel: "13ARV1:cam1:NumImages_RBV", Connecting to: llrf-Control.local:5064, Ignored: 10.1.15.37:5064
  Requested Type: TYPENOTCONN
  Requested Count: 0
  Source File: ../cac.cpp
  Line number: 1308

Wed Sep 04 14:44:02 IST 2019
medmCAExceptionHandlerCb: Channel Access Exception:
  Channel Name: Unavailable
  Native Type: Unavailable
  Native Count: 0
  Access: Unavailable
  Host: Unavailable
  Message: Identical process variable names on multiple servers
  Context: Channel: "13ARV1:cam1:NumImagesCounter_RBV", Connecting to: llrf-Control.local:5064, Ignored: 10.1.15.37:5064
  Requested Type: TYPENOTCONN
  Requested Count: 0
  Source File: ../cac.cpp
  Line number: 1308

Wed Sep 04 14:44:02 IST 2019
medmCAExceptionHandlerCb: Channel Access Exception:
  Channel Name: Unavailable
  Native Type: Unavailable
  Native Count: 0
  Access: Unavailable
  Host: Unavailable
  Message: Identical process variable names on multiple servers
  Context: Channel: "13ARV1:cam1:ImageMode", Connecting to: llrf-Control.local:5064, Ignored: 10.1.15.37:5064
  Requested Type: TYPENOTCONN
  Requested Count: 0
  Source File: ../cac.cpp
  Line number: 1308

Wed Sep 04 14:44:02 IST 2019
medmCAExceptionHandlerCb: Channel Access Exception:
  Channel Name: Unavailable
  Native Type: Unavailable
  Native Count: 0
  Access: Unavailable
  Host: Unavailable
  Message: Identical process variable names on multiple servers
  Context: Channel: "13ARV1:cam1:ImageMode_RBV", Connecting to: llrf-Control.local:5064, Ignored: 10.1.15.37:5064
  Requested Type: TYPENOTCONN
  Requested Count: 0
  Source File: ../cac.cpp
  Line number: 1308

Wed Sep 04 14:44:02 IST 2019
medmCAExceptionHandlerCb: Channel Access Exception:
  Channel Name: Unavailable
  Native Type: Unavailable
  Native Count: 0
  Access: Unavailable
  Host: Unavailable
  Message: Identical process variable names on multiple servers
  Context: Channel: "13ARV1:cam1:TriggerMode", Connecting to: llrf-Control.local:5064, Ignored: 10.1.15.37:5064
  Requested Type: TYPENOTCONN
  Requested Count: 0
  Source File: ../cac.cpp
  Line number: 1308

Wed Sep 04 14:44:02 IST 2019
medmCAExceptionHandlerCb: Channel Access Exception:
  Channel Name: Unavailable
  Native Type: Unavailable
  Native Count: 0
  Access: Unavailable
  Host: Unavailable
  Message: Identical process variable names on multiple servers
  Context: Channel: "13ARV1:cam1:TriggerMode_RBV", Connecting to: llrf-Control.local:5064, Ignored: 10.1.15.37:5064
  Requested Type: TYPENOTCONN
  Requested Count: 0
  Source File: ../cac.cpp
  Line number: 1308

Wed Sep 04 14:44:02 IST 2019
medmCAExceptionHandlerCb: Channel Access Exception:
  Channel Name: Unavailable
  Native Type: Unavailable
  Native Count: 0
  Access: Unavailable
  Host: Unavailable
  Message: Identical process variable names on multiple servers
  Context: Channel: "13ARV1:cam1:TriggerSoftware", Connecting to: llrf-Control.local:5064, Ignored: 10.1.15.37:5064
  Requested Type: TYPENOTCONN
  Requested Count: 0
  Source File: ../cac.cpp
  Line number: 1308

Wed Sep 04 14:44:02 IST 2019
medmCAExceptionHandlerCb: Channel Access Exception:
  Channel Name: Unavailable
  Native Type: Unavailable
  Native Count: 0
  Access: Unavailable
  Host: Unavailable
  Message: Identical process variable names on multiple servers
  Context: Channel: "13ARV1:cam1:Acquire", Connecting to: llrf-Control.local:5064, Ignored: 10.1.15.37:5064
  Requested Type: TYPENOTCONN
  Requested Count: 0
  Source File: ../cac.cpp
  Line number: 1308

Wed Sep 04 14:44:02 IST 2019
medmCAExceptionHandlerCb: Channel Access Exception:
  Channel Name: Unavailable
  Native Type: Unavailable
  Native Count: 0
  Access: Unavailable
  Host: Unavailable
  Message: Identical process variable names on multiple servers
  Context: Channel: "13ARV1:cam1:BinX", Connecting to: 169.254.0.2:5064, Ignored: 10.1.15.37:5064
  Requested Type: TYPENOTCONN
  Requested Count: 0
  Source File: ../cac.cpp
  Line number: 1308

Wed Sep 04 14:44:02 IST 2019
medmCAExceptionHandlerCb: Channel Access Exception:
  Channel Name: Unavailable
  Native Type: Unavailable
  Native Count: 0
  Access: Unavailable
  Host: Unavailable
  Message: Identical process variable names on multiple servers
  Context: Channel: "13ARV1:cam1:Acquire", Connecting to: llrf-Control.local:5064, Ignored: 10.1.15.37:5064
  Requested Type: TYPENOTCONN
  Requested Count: 0
  Source File: ../cac.cpp
  Line number: 1308

Wed Sep 04 14:44:02 IST 2019
medmCAExceptionHandlerCb: Channel Access Exception:
  Channel Name: Unavailable
  Native Type: Unavailable
  Native Count: 0
  Access: Unavailable
  Host: Unavailable
  Message: Identical process variable names on multiple servers
  Context: Channel: "13ARV1:cam1:Acquire", Connecting to: llrf-Control.local:5064, Ignored: 10.1.15.37:5064
  Requested Type: TYPENOTCONN
  Requested Count: 0
  Source File: ../cac.cpp
  Line number: 1308

Wed Sep 04 14:44:02 IST 2019
medmCAExceptionHandlerCb: Channel Access Exception:
  Channel Name: Unavailable
  Native Type: Unavailable
  Native Count: 0
  Access: Unavailable
  Host: Unavailable
  Message: Identical process variable names on multiple servers
  Context: Channel: "13ARV1:cam1:TimeRemaining_RBV", Connecting to: llrf-Control.local:5064, Ignored: 10.1.15.37:5064
  Requested Type: TYPENOTCONN
  Requested Count: 0
  Source File: ../cac.cpp
  Line number: 1308

Wed Sep 04 14:44:02 IST 2019
medmCAExceptionHandlerCb: Channel Access Exception:
  Channel Name: Unavailable
  Native Type: Unavailable
  Native Count: 0
  Access: Unavailable
  Host: Unavailable
  Message: Identical process variable names on multiple servers
  Context: Channel: "13ARV1:cam1:DetectorState_RBV", Connecting to: llrf-Control.local:5064, Ignored: 10.1.15.37:5064
  Requested Type: TYPENOTCONN
  Requested Count: 0
  Source File: ../cac.cpp
  Line number: 1308

Wed Sep 04 14:44:02 IST 2019
medmCAExceptionHandlerCb: Channel Access Exception:
  Channel Name: Unavailable
  Native Type: Unavailable
  Native Count: 0
  Access: Unavailable
  Host: Unavailable
  Message: Identical process variable names on multiple servers
  Context: Channel: "13ARV1:cam1:ArrayCounter", Connecting to: llrf-Control.local:5064, Ignored: 10.1.15.37:5064
  Requested Type: TYPENOTCONN
  Requested Count: 0
  Source File: ../cac.cpp
  Line number: 1308

Wed Sep 04 14:44:02 IST 2019
medmCAExceptionHandlerCb: Channel Access Exception:
  Channel Name: Unavailable
  Native Type: Unavailable
  Native Count: 0
  Access: Unavailable
  Host: Unavailable
  Message: Identical process variable names on multiple servers
  Context: Channel: "13ARV1:cam1:ArrayCounter_RBV", Connecting to: llrf-Control.local:5064, Ignored: 10.1.15.37:5064
  Requested Type: TYPENOTCONN
  Requested Count: 0
  Source File: ../cac.cpp
  Line number: 1308

Wed Sep 04 14:44:02 IST 2019
medmCAExceptionHandlerCb: Channel Access Exception:
Too many exceptions [25]
No more will be handled
Please fix the problem and restart MEDM

Upon Pressing "Acquire" button, the camera link LED is constant ON and I think it starts acquiring as well.
After that I installed ImageJ and Java on my PC and subsequently added and complied/run the EPICS_areaDetector Plugins (i.e. EPICS AD Controller, EPICS AD Viewer, EPICS NTNDA Viewer).
When I started EPICS AD Viewer and added my PV prefix as 13ARV1:image1: (it is shown in green highlight) and status is 4/9/2019 14:49:51.869: Connected to EPICS PVs OK

But on pressing Start nothing happens, 4/9/2019 14:51:23.206: Image display started message is displayed but no display is actually started and NX, NY, NZ and Frames/s boxes are still empty.
However, the console of ImageJ shows the following issues:

Sep 04, 2019 2:02:30 PM com.cosylab.epics.caj.CAJContext searchResponse
INFO: More than one PVs with name '13ARV1:Over1:1:PositionX' detected, additional response from: /169.254.0.2:5064
Sep 04, 2019 2:02:30 PM com.cosylab.epics.caj.CAJContext searchResponse
INFO: More than one PVs with name '13ARV1:Over1:1:PositionY' detected, additional response from: /169.254.0.2:5064
Sep 04, 2019 2:02:30 PM com.cosylab.epics.caj.CAJContext searchResponse
INFO: More than one PVs with name '13ARV1:Over1:1:SizeX' detected, additional response from: /169.254.0.2:5064
Sep 04, 2019 2:02:30 PM com.cosylab.epics.caj.CAJContext searchResponse
INFO: More than one PVs with name '13ARV1:Over1:1:SizeY' detected, additional response from: /169.254.0.2:5064
Sep 04, 2019 2:02:32 PM com.cosylab.epics.caj.CAJContext searchResponse
INFO: More than one PVs with name '13ARV1:ROI1:MinX' detected, additional response from: /169.254.0.2:5064
Sep 04, 2019 2:02:32 PM com.cosylab.epics.caj.CAJContext searchResponse
INFO: More than one PVs with name '13ARV1:ROI1:MinY' detected, additional response from: /169.254.0.2:5064
Sep 04, 2019 2:02:32 PM com.cosylab.epics.caj.CAJContext searchResponse
INFO: More than one PVs with name '13ARV1:ROI1:MinX_RBV' detected, additional response from: /169.254.0.2:5064
Sep 04, 2019 2:02:32 PM com.cosylab.epics.caj.CAJContext searchResponse
INFO: More than one PVs with name '13ARV1:ROI1:MinY_RBV' detected, additional response from: /169.254.0.2:5064
Sep 04, 2019 2:02:32 PM com.cosylab.epics.caj.CAJContext searchResponse
INFO: More than one PVs with name '13ARV1:ROI1:BinX' detected, additional response from: /169.254.0.2:5064
Sep 04, 2019 2:02:32 PM com.cosylab.epics.caj.CAJContext searchResponse
INFO: More than one PVs with name '13ARV1:ROI1:BinY' detected, additional response from: /169.254.0.2:5064
Sep 04, 2019 2:02:32 PM com.cosylab.epics.caj.CAJContext searchResponse
INFO: More than one PVs with name '13ARV1:ROI1:ReverseX_RBV' detected, additional response from: /169.254.0.2:5064
Sep 04, 2019 2:02:32 PM com.cosylab.epics.caj.CAJContext searchResponse
INFO: More than one PVs with name '13ARV1:ROI1:ReverseY_RBV' detected, additional response from: /169.254.0.2:5064
Sep 04, 2019 2:02:32 PM com.cosylab.epics.caj.CAJContext searchResponse
INFO: More than one PVs with name '13ARV1:ROI1:SizeX' detected, additional response from: /169.254.0.2:5064
Sep 04, 2019 2:02:32 PM com.cosylab.epics.caj.CAJContext searchResponse
INFO: More than one PVs with name '13ARV1:ROI1:SizeY' detected, additional response from: /169.254.0.2:5064
Sep 04, 2019 2:02:32 PM com.cosylab.epics.caj.CAJContext searchResponse
INFO: More than one PVs with name '13ARV1:ROI1:ArraySizeX_RBV' detected, additional response from: /169.254.0.2:5064
Sep 04, 2019 2:02:32 PM com.cosylab.epics.caj.CAJContext searchResponse
INFO: More than one PVs with name '13ARV1:ROI1:ArraySizeY_RBV' detected, additional response from: /169.254.0.2:5064
Sep 04, 2019 2:02:34 PM com.cosylab.epics.caj.CAJContext searchResponse
INFO: More than one PVs with name '13ARV1:Trans1:Type' detected, additional response from: /169.254.0.2:5064
Sep 04, 2019 2:02:34 PM com.cosylab.epics.caj.CAJContext searchResponse
INFO: More than one PVs with name '13ARV1:Trans1:ArraySizeX_RBV' detected, additional response from: /169.254.0.2:5064
Sep 04, 2019 2:02:34 PM com.cosylab.epics.caj.CAJContext searchResponse
INFO: More than one PVs with name '13ARV1:Trans1:ArraySizeY_RBV' detected, additional response from: /169.254.0.2:5064
Sep 04, 2019 2:02:36 PM com.cosylab.epics.caj.CAJContext searchResponse
INFO: More than one PVs with name '13ARV1:cam1:MinX' detected, additional response from: /169.254.0.2:5064
Sep 04, 2019 2:02:36 PM com.cosylab.epics.caj.CAJContext searchResponse
INFO: More than one PVs with name '13ARV1:cam1:MinY' detected, additional response from: /169.254.0.2:5064
Sep 04, 2019 2:02:36 PM com.cosylab.epics.caj.CAJContext searchResponse
INFO: More than one PVs with name '13ARV1:cam1:MinX_RBV' detected, additional response from: /169.254.0.2:5064
Sep 04, 2019 2:02:36 PM com.cosylab.epics.caj.CAJContext searchResponse
INFO: More than one PVs with name '13ARV1:cam1:MinY_RBV' detected, additional response from: /169.254.0.2:5064
Sep 04, 2019 2:02:36 PM com.cosylab.epics.caj.CAJContext searchResponse
INFO: More than one PVs with name '13ARV1:cam1:SizeX' detected, additional response from: /169.254.0.2:5064
Sep 04, 2019 2:02:36 PM com.cosylab.epics.caj.CAJContext searchResponse
INFO: More than one PVs with name '13ARV1:cam1:SizeY' detected, additional response from: /169.254.0.2:5064
Sep 04, 2019 2:02:36 PM com.cosylab.epics.caj.CAJContext searchResponse
INFO: More than one PVs with name '13ARV1:cam1:ArraySizeX_RBV' detected, additional response from: /169.254.0.2:5064
Sep 04, 2019 2:02:36 PM com.cosylab.epics.caj.CAJContext searchResponse
INFO: More than one PVs with name '13ARV1:cam1:ArraySizeY_RBV' detected, additional response from: /169.254.0.2:5064
Sep 04, 2019 2:02:36 PM com.cosylab.epics.caj.CAJContext searchResponse
INFO: More than one PVs with name '13ARV1:cam1:MaxSizeX_RBV' detected, additional response from: /169.254.0.2:5064
Sep 04, 2019 2:02:36 PM com.cosylab.epics.caj.CAJContext searchResponse
INFO: More than one PVs with name '13ARV1:cam1:MaxSizeY_RBV' detected, additional response from: /169.254.0.2:5064
Sep 04, 2019 2:02:36 PM com.cosylab.epics.caj.CAJContext searchResponse
INFO: More than one PVs with name '13ARV1:cam1:BinX_RBV' detected, additional response from: /169.254.0.2:5064
Sep 04, 2019 2:02:37 PM com.cosylab.epics.caj.CAJContext searchResponse
INFO: More than one PVs with name '13ARV1:cam1:BinY_RBV' detected, additional response from: /169.254.0.2:5064
Sep 04, 2019 2:02:37 PM com.cosylab.epics.caj.CAJContext searchResponse
INFO: More than one PVs with name '13ARV1:cam1:ReverseX_RBV' detected, additional response from: /169.254.0.2:5064
Sep 04, 2019 2:02:37 PM com.cosylab.epics.caj.CAJContext searchResponse
INFO: More than one PVs with name '13ARV1:cam1:ReverseY_RBV' detected, additional response from: /169.254.0.2:5064
Sep 04, 2019 2:04:19 PM com.cosylab.epics.caj.CAJContext searchResponse
INFO: More than one PVs with name '13ARV1:image1:ArraySize0_RBV' detected, additional response from: /169.254.0.2:5064
Sep 04, 2019 2:04:19 PM com.cosylab.epics.caj.CAJContext searchResponse
INFO: More than one PVs with name '13ARV1:image1:ArraySize1_RBV' detected, additional response from: /169.254.0.2:5064
Sep 04, 2019 2:04:19 PM com.cosylab.epics.caj.CAJContext searchResponse
INFO: More than one PVs with name '13ARV1:image1:ArraySize2_RBV' detected, additional response from: /169.254.0.2:5064
Sep 04, 2019 2:04:19 PM com.cosylab.epics.caj.CAJContext searchResponse
INFO: More than one PVs with name '13ARV1:image1:ColorMode_RBV' detected, additional response from: /169.254.0.2:5064
Sep 04, 2019 2:04:19 PM com.cosylab.epics.caj.CAJContext searchResponse
INFO: More than one PVs with name '13ARV1:image1:DataType_RBV' detected, additional response from: /169.254.0.2:5064
Sep 04, 2019 2:04:19 PM com.cosylab.epics.caj.CAJContext searchResponse
INFO: More than one PVs with name '13ARV1:image1:ArrayData' detected, additional response from: /169.254.0.2:5064
Sep 04, 2019 2:04:19 PM com.cosylab.epics.caj.CAJContext searchResponse
INFO: More than one PVs with name '13ARV1:image1:ArrayCounter_RBV' detected, additional response from: /169.254.0.2:5064
Sep 04, 2019 2:14:59 PM com.cosylab.epics.caj.CAJContext searchResponse
INFO: More than one PVs with name '13ARV1:image1:ArraySize0_RBV' detected, additional response from: /169.254.0.2:5064
Sep 04, 2019 2:14:59 PM com.cosylab.epics.caj.CAJContext searchResponse
INFO: More than one PVs with name '13ARV1:image1:ArraySize1_RBV' detected, additional response from: /169.254.0.2:5064
Sep 04, 2019 2:14:59 PM com.cosylab.epics.caj.CAJContext searchResponse
INFO: More than one PVs with name '13ARV1:image1:ArraySize2_RBV' detected, additional response from: /169.254.0.2:5064
Sep 04, 2019 2:14:59 PM com.cosylab.epics.caj.CAJContext searchResponse
INFO: More than one PVs with name '13ARV1:image1:ColorMode_RBV' detected, additional response from: /169.254.0.2:5064
Sep 04, 2019 2:14:59 PM com.cosylab.epics.caj.CAJContext searchResponse
INFO: More than one PVs with name '13ARV1:image1:DataType_RBV' detected, additional response from: /169.254.0.2:5064
Sep 04, 2019 2:14:59 PM com.cosylab.epics.caj.CAJContext searchResponse
INFO: More than one PVs with name '13ARV1:image1:ArrayData' detected, additional response from: /169.254.0.2:5064
Sep 04, 2019 2:14:59 PM com.cosylab.epics.caj.CAJContext searchResponse
INFO: More than one PVs with name '13ARV1:image1:ArrayCounter_RBV' detected, additional response from: /169.254.0.2:5064
Sep 04, 2019 2:19:08 PM com.cosylab.epics.caj.CAJContext searchResponse
INFO: More than one PVs with name '13ARV1:image1:ArraySize0_RBV' detected, additional response from: /169.254.0.2:5064
Sep 04, 2019 2:19:08 PM com.cosylab.epics.caj.CAJContext searchResponse
INFO: More than one PVs with name '13ARV1:image1:ArraySize1_RBV' detected, additional response from: /169.254.0.2:5064
Sep 04, 2019 2:19:08 PM com.cosylab.epics.caj.CAJContext searchResponse
INFO: More than one PVs with name '13ARV1:image1:ArraySize2_RBV' detected, additional response from: /169.254.0.2:5064
Sep 04, 2019 2:19:08 PM com.cosylab.epics.caj.CAJContext searchResponse
INFO: More than one PVs with name '13ARV1:image1:ColorMode_RBV' detected, additional response from: /169.254.0.2:5064
Sep 04, 2019 2:19:08 PM com.cosylab.epics.caj.CAJContext searchResponse
INFO: More than one PVs with name '13ARV1:image1:DataType_RBV' detected, additional response from: /169.254.0.2:5064
Sep 04, 2019 2:19:08 PM com.cosylab.epics.caj.CAJContext searchResponse
INFO: More than one PVs with name '13ARV1:image1:ArrayData' detected, additional response from: /169.254.0.2:5064
Sep 04, 2019 2:19:08 PM com.cosylab.epics.caj.CAJContext searchResponse
INFO: More than one PVs with name '13ARV1:image1:ArrayCounter_RBV' detected, additional response from: /169.254.0.2:5064
Sep 04, 2019 2:23:53 PM com.cosylab.epics.caj.CAJContext searchResponse
INFO: More than one PVs with name '13ARV1:cam1:MinX' detected, additional response from: /169.254.0.2:5064
Sep 04, 2019 2:23:53 PM com.cosylab.epics.caj.CAJContext searchResponse
INFO: More than one PVs with name '13ARV1:cam1:MinY' detected, additional response from: /169.254.0.2:5064
Sep 04, 2019 2:23:53 PM com.cosylab.epics.caj.CAJContext searchResponse
INFO: More than one PVs with name '13ARV1:cam1:MinX_RBV' detected, additional response from: /169.254.0.2:5064
Sep 04, 2019 2:23:53 PM com.cosylab.epics.caj.CAJContext searchResponse
INFO: More than one PVs with name '13ARV1:cam1:MinY_RBV' detected, additional response from: /169.254.0.2:5064
Sep 04, 2019 2:23:53 PM com.cosylab.epics.caj.CAJContext searchResponse
INFO: More than one PVs with name '13ARV1:cam1:SizeX' detected, additional response from: /169.254.0.2:5064
Sep 04, 2019 2:23:53 PM com.cosylab.epics.caj.CAJContext searchResponse
INFO: More than one PVs with name '13ARV1:cam1:SizeY' detected, additional response from: /169.254.0.2:5064
Sep 04, 2019 2:23:53 PM com.cosylab.epics.caj.CAJContext searchResponse
INFO: More than one PVs with name '13ARV1:cam1:ArraySizeX_RBV' detected, additional response from: /169.254.0.2:5064
Sep 04, 2019 2:23:53 PM com.cosylab.epics.caj.CAJContext searchResponse
INFO: More than one PVs with name '13ARV1:cam1:ArraySizeY_RBV' detected, additional response from: /169.254.0.2:5064
Sep 04, 2019 2:23:53 PM com.cosylab.epics.caj.CAJContext searchResponse
INFO: More than one PVs with name '13ARV1:cam1:MaxSizeX_RBV' detected, additional response from: /169.254.0.2:5064
Sep 04, 2019 2:23:53 PM com.cosylab.epics.caj.CAJContext searchResponse
INFO: More than one PVs with name '13ARV1:cam1:MaxSizeY_RBV' detected, additional response from: /169.254.0.2:5064
Sep 04, 2019 2:23:53 PM com.cosylab.epics.caj.CAJContext searchResponse
INFO: More than one PVs with name '13ARV1:cam1:BinX_RBV' detected, additional response from: /169.254.0.2:5064
Sep 04, 2019 2:23:53 PM com.cosylab.epics.caj.CAJContext searchResponse
INFO: More than one PVs with name '13ARV1:cam1:BinY_RBV' detected, additional response from: /169.254.0.2:5064
Sep 04, 2019 2:23:53 PM com.cosylab.epics.caj.CAJContext searchResponse
INFO: More than one PVs with name '13ARV1:cam1:ReverseX_RBV' detected, additional response from: /169.254.0.2:5064
Sep 04, 2019 2:23:53 PM com.cosylab.epics.caj.CAJContext searchResponse
INFO: More than one PVs with name '13ARV1:cam1:ReverseY_RBV' detected, additional response from: /169.254.0.2:5064
Sep 04, 2019 2:23:53 PM com.cosylab.epics.caj.CAJContext searchResponse
INFO: More than one PVs with name '13ARV1:ROI1:MinX' detected, additional response from: /169.254.0.2:5064
Sep 04, 2019 2:23:53 PM com.cosylab.epics.caj.CAJContext searchResponse
INFO: More than one PVs with name '13ARV1:ROI1:MinY' detected, additional response from: /169.254.0.2:5064
Sep 04, 2019 2:23:53 PM com.cosylab.epics.caj.CAJContext searchResponse
INFO: More than one PVs with name '13ARV1:ROI1:MinX_RBV' detected, additional response from: /169.254.0.2:5064
Sep 04, 2019 2:23:53 PM com.cosylab.epics.caj.CAJContext searchResponse
INFO: More than one PVs with name '13ARV1:ROI1:MinY_RBV' detected, additional response from: /169.254.0.2:5064
Sep 04, 2019 2:23:53 PM com.cosylab.epics.caj.CAJContext searchResponse
INFO: More than one PVs with name '13ARV1:ROI1:BinX' detected, additional response from: /169.254.0.2:5064
Sep 04, 2019 2:23:53 PM com.cosylab.epics.caj.CAJContext searchResponse
INFO: More than one PVs with name '13ARV1:ROI1:BinY' detected, additional response from: /169.254.0.2:5064
Sep 04, 2019 2:23:53 PM com.cosylab.epics.caj.CAJContext searchResponse
INFO: More than one PVs with name '13ARV1:ROI1:ReverseX_RBV' detected, additional response from: /169.254.0.2:5064
Sep 04, 2019 2:23:53 PM com.cosylab.epics.caj.CAJContext searchResponse
INFO: More than one PVs with name '13ARV1:ROI1:ReverseY_RBV' detected, additional response from: /169.254.0.2:5064
Sep 04, 2019 2:23:53 PM com.cosylab.epics.caj.CAJContext searchResponse
INFO: More than one PVs with name '13ARV1:ROI1:SizeX' detected, additional response from: /169.254.0.2:5064
Sep 04, 2019 2:23:53 PM com.cosylab.epics.caj.CAJContext searchResponse
INFO: More than one PVs with name '13ARV1:ROI1:SizeY' detected, additional response from: /169.254.0.2:5064
Sep 04, 2019 2:23:53 PM com.cosylab.epics.caj.CAJContext searchResponse
INFO: More than one PVs with name '13ARV1:ROI1:ArraySizeX_RBV' detected, additional response from: /169.254.0.2:5064
Sep 04, 2019 2:23:53 PM com.cosylab.epics.caj.CAJContext searchResponse
INFO: More than one PVs with name '13ARV1:ROI1:ArraySizeY_RBV' detected, additional response from: /169.254.0.2:5064
Sep 04, 2019 2:23:53 PM com.cosylab.epics.caj.CAJContext searchResponse
INFO: More than one PVs with name '13ARV1:Trans1:Type' detected, additional response from: /169.254.0.2:5064
Sep 04, 2019 2:23:53 PM com.cosylab.epics.caj.CAJContext searchResponse
INFO: More than one PVs with name '13ARV1:Trans1:ArraySizeX_RBV' detected, additional response from: /169.254.0.2:5064
Sep 04, 2019 2:23:54 PM com.cosylab.epics.caj.CAJContext searchResponse
INFO: More than one PVs with name '13ARV1:Trans1:ArraySizeY_RBV' detected, additional response from: /169.254.0.2:5064
Sep 04, 2019 2:23:54 PM com.cosylab.epics.caj.CAJContext searchResponse
INFO: More than one PVs with name '13ARV1:Over1:1:PositionX' detected, additional response from: /169.254.0.2:5064
Sep 04, 2019 2:23:54 PM com.cosylab.epics.caj.CAJContext searchResponse
INFO: More than one PVs with name '13ARV1:Over1:1:PositionY' detected, additional response from: /169.254.0.2:5064
Sep 04, 2019 2:23:54 PM com.cosylab.epics.caj.CAJContext searchResponse
INFO: More than one PVs with name '13ARV1:Over1:1:SizeX' detected, additional response from: /169.254.0.2:5064
Sep 04, 2019 2:23:54 PM com.cosylab.epics.caj.CAJContext searchResponse
INFO: More than one PVs with name '13ARV1:Over1:1:SizeY' detected, additional response from: /169.254.0.2:5064
Sep 04, 2019 2:48:13 PM com.cosylab.epics.caj.CAJContext searchResponse
INFO: More than one PVs with name '13ARV1:image1:ArraySize0_RBV' detected, additional response from: /169.254.0.2:5064
Sep 04, 2019 2:48:13 PM com.cosylab.epics.caj.CAJContext searchResponse
INFO: More than one PVs with name '13ARV1:image1:ArraySize1_RBV' detected, additional response from: /169.254.0.2:5064
Sep 04, 2019 2:48:14 PM com.cosylab.epics.caj.CAJContext searchResponse
INFO: More than one PVs with name '13ARV1:image1:ArraySize2_RBV' detected, additional response from: /169.254.0.2:5064
Sep 04, 2019 2:48:14 PM com.cosylab.epics.caj.CAJContext searchResponse
INFO: More than one PVs with name '13ARV1:image1:ColorMode_RBV' detected, additional response from: /169.254.0.2:5064
Sep 04, 2019 2:48:14 PM com.cosylab.epics.caj.CAJContext searchResponse
INFO: More than one PVs with name '13ARV1:image1:DataType_RBV' detected, additional response from: /169.254.0.2:5064
Sep 04, 2019 2:48:14 PM com.cosylab.epics.caj.CAJContext searchResponse
INFO: More than one PVs with name '13ARV1:image1:ArrayData' detected, additional response from: /169.254.0.2:5064
Sep 04, 2019 2:48:14 PM com.cosylab.epics.caj.CAJContext searchResponse
INFO: More than one PVs with name '13ARV1:image1:ArrayCounter_RBV' detected, additional response from: /169.254.0.2:5064
Sep 04, 2019 2:49:51 PM com.cosylab.epics.caj.CAJContext searchResponse
INFO: More than one PVs with name '13ARV1:image1:ArraySize0_RBV' detected, additional response from: /169.254.0.2:5064
Sep 04, 2019 2:49:51 PM com.cosylab.epics.caj.CAJContext searchResponse
INFO: More than one PVs with name '13ARV1:image1:ArraySize1_RBV' detected, additional response from: /169.254.0.2:5064
Sep 04, 2019 2:49:51 PM com.cosylab.epics.caj.CAJContext searchResponse
INFO: More than one PVs with name '13ARV1:image1:ArraySize2_RBV' detected, additional response from: /169.254.0.2:5064
Sep 04, 2019 2:49:51 PM com.cosylab.epics.caj.CAJContext searchResponse
INFO: More than one PVs with name '13ARV1:image1:ColorMode_RBV' detected, additional response from: /169.254.0.2:5064
Sep 04, 2019 2:49:51 PM com.cosylab.epics.caj.CAJContext searchResponse
INFO: More than one PVs with name '13ARV1:image1:DataType_RBV' detected, additional response from: /169.254.0.2:5064
Sep 04, 2019 2:49:51 PM com.cosylab.epics.caj.CAJContext searchResponse
INFO: More than one PVs with name '13ARV1:image1:ArrayData' detected, additional response from: /169.254.0.2:5064
Sep 04, 2019 2:49:51 PM com.cosylab.epics.caj.CAJContext searchResponse
INFO: More than one PVs with name '13ARV1:image1:ArrayCounter_RBV' detected, additional response from: /169.254.0.2:5064

Since, I am an EPICS user (not developer) and a beginner, I am unable to comprehend this situation to view the Image Display. Please help of in resolving this issue.

Please let me know if anything else needs to be done from my side.

Thanks and regards
--
--
Ashish Sharma
Engineer 'C'
Inter-University Accelerator Centre,
Aruna Asaf Ali Marg, New Delhi - 110067, India

Experimental Physics and Industrial Control System

Experimental Physics and
Industrial Control System