Bob,
If you change the configuration routine and constructor from
int prosilicaConfig(char *portName,
int uniqueId,
int maxBuffers, size_t maxMemory,
int priority, int stackSize)
to
int prosilicaConfig(char *portName,
const char* address,
int maxBuffers, size_t maxMemory,
int priority, int stackSize)
Then you can test "address" to see if it is an integer. If so, it is a UniqueID, if not it is an IP address or IP name. Then call the appropriate PvCameraOpen function. The nice thing about making this change is that it is backwards compatible with existing startup scripts, since the iocsh can pass a unique ID as an integer or a string without requiring quotes.
I'm on travel or I would try it myself.
Mark
________________________________
From: Bob Gunion [mailto:[email protected]]
Sent: Wed 6/15/2011 5:06 PM
To: Mark Rivers; Robert Petkus
Cc: [email protected]
Subject: Re: AreaDetector: Prosilica camera on different subnet?
I think it's not a difficult change: call PvCameraOpenByAddr if given an IP address, or PvCameraOpen if a unique ID - but with that I've exhausted my knowledge of the Prosilica API. Perhaps I'll give it a try and see if there are problems (functionality/performance limitations?).
Bob
On Jun 15, 2011, at 12:32 PM, Mark Rivers wrote:
>
>
>
> Actually the Prosilica areaDetector driver cannot currently do this. The reason is that the camera is found by its Unique ID rather than its IP address. This is convenient because cameras can use DHCP and do not need a fixed IP address. But it won't work across subnets because it requires a broadcast to find the cameras by Unique ID. We could modify the driver to add logic to allow IP address or IP name in place of Unique ID.
>
> Mark
>
>
>
>
>
> ________________________________
>
> From: [email protected] on behalf of Robert Petkus
> Sent: Wed 6/15/2011 12:10 PM
> To: Bob Gunion
> Cc: [email protected]
> Subject: Re: AreaDetector: Prosilica camera on different subnet?
>
>
>
> If the both the IOC and camera allow a default gateway to be configured,
> you can keep them on separate subnets and simply use a router. The
> router can be either a server or a multi-layer switch with an interface
> on each of the subnets. The router interface addresses will be the
> gateway addresses configured on the IOC and camera. From there one
> could create policies to allow only traffic from the (2) devices to span
> subnets if there are security concerns.
>
> --
> Robert Petkus
> Bldg. 902-B, 17 Cornell Avenue
> National Synchrotron Light Source II
> Brookhaven National Laboratory
> Upton, New York 11973
> Tel. : +1 (631) 344 3258
> Fax. : +1 (631) 344 8085
> http://www.bnl.gov/nsls2
>
>
> On 6/15/11 12:59 PM, Bob Gunion wrote:
>> I have a Prosilica GigE camera (model GC1380H) which is on a different subnet from the desired location of my ioc. Does the prosilica driver for areaDetector support this? If not, would this be a worthwhile contribution, or is it advisable to keep both on the same subnet?
>>
>> Thanks,
>> Bob Gunion
>>
>>
>
>
- Replies:
- Re: AreaDetector: Prosilica camera on different subnet? Bob Gunion
- References:
- AreaDetector: Prosilica camera on different subnet? Bob Gunion
- Re: AreaDetector: Prosilica camera on different subnet? Robert Petkus
- RE: AreaDetector: Prosilica camera on different subnet? Mark Rivers
- Re: AreaDetector: Prosilica camera on different subnet? Bob Gunion
- Navigate by Date:
- Prev:
Re: radiation damage to electronics inside accelerator tunnel? Benjamin Franksen
- Next:
Re: radiation damage to electronics inside accelerator tunnel? Elder Matias
- Index:
1994
1995
1996
1997
1998
1999
2000
2001
2002
2003
2004
2005
2006
2007
2008
2009
2010
<2011>
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
- Navigate by Thread:
- Prev:
Re: AreaDetector: Prosilica camera on different subnet? Bob Gunion
- Next:
Re: AreaDetector: Prosilica camera on different subnet? Bob Gunion
- Index:
1994
1995
1996
1997
1998
1999
2000
2001
2002
2003
2004
2005
2006
2007
2008
2009
2010
<2011>
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
|