RE: ezca

["Siddons, David" <siddons@bnl.gov>]

Hi Mark, Till,
   Changing the arrays to the correct type and updating my EZCA library to the one on Github fixed the problem.
Thanks for your help, guys.
Pete.

________________________________________
From: Mark Rivers [rivers@cars.uchicago.edu]
Sent: Saturday, January 20, 2018 9:35 PM
To: Till Straumann
Cc: Siddons, David; tech-talk@aps.anl.gov
Subject: Re: ezca

Hi Till,

The version on Github had your enhancements merged into it in 2011. There have been several fixes to it since then.

Mark


Sent from my iPhone

> On Jan 20, 2018, at 7:35 PM, Till Straumann <strauman@slac.stanford.edu> wrote:
>
> A long time ago I created a thread-safe fork of ezca for the labCA matlab/scilab CA interface
> (http://www.slac.stanford.edu/~strauman/labca/) This definitely works on 64-bit systems (linux + windows).
> I don't know if we are using it already with 3.15 but we definitely will and I don't anticipate
> serious problems.
>
> - Till
>
>
>> On 01/20/2018 04:22 PM, Mark Rivers wrote:
>> Hi Pete,
>>
>>
>>> I'm having some trouble with EZCA. Does anyone else still use this?
>>
>> Yes, we use it because it is part of the IDL EPICS interface.  It is also part of the matlab EPICS interface, which I don't use but I know that others do.
>>
>>
>>> Do we know if there are 64-bit issues with it?
>>
>> I have been using it with 64-bit IDL for many years and have never seen any problems.
>>
>>
>>> Does it work with 3.15.5?
>>
>> Yes.  Here is the output of ldd on my IDL shareable library for EPICS.
>>
>> corvette:extensions/lib/linux-x86_64>ldd /usr/local/idl_user/epics/libezcaIDL.so_linux_x86_64
>>         linux-vdso.so.1 =>  (0x00007ffcaa342000)
>>         libezca.so => /usr/local/epics/extensions/lib/linux-x86_64/libezca.so (0x00007f077cbd5000)
>>         libEzcaScan.so => /usr/local/epics/extensions/lib/linux-x86_64/libEzcaScan.so (0x00007f077c9c9000)
>>         libca.so.3.15.5 => /usr/local/epics/base-3.15.5/lib/linux-x86_64/libca.so.3.15.5 (0x00007f077c75f000)
>>         libCom.so.3.15.5 => /usr/local/epics/base-3.15.5/lib/linux-x86_64/libCom.so.3.15.5 (0x00007f077c4ec000)
>>         libpthread.so.0 => /lib64/libpthread.so.0 (0x00007f077c2b9000)
>>         libreadline.so.6 => /lib64/libreadline.so.6 (0x00007f077c073000)
>>         librt.so.1 => /lib64/librt.so.1 (0x00007f077be6b000)
>>         libdl.so.2 => /lib64/libdl.so.2 (0x00007f077bc66000)
>>         libstdc++.so.6 => /lib64/libstdc++.so.6 (0x00007f077b95e000)
>>         libm.so.6 => /lib64/libm.so.6 (0x00007f077b65c000)
>>         libgcc_s.so.1 => /lib64/libgcc_s.so.1 (0x00007f077b445000)
>>         libc.so.6 => /lib64/libc.so.6 (0x00007f077b082000)
>>         /lib64/ld-linux-x86-64.so.2 (0x000055fd08911000)
>>         libtinfo.so.5 => /lib64/libtinfo.so.5 (0x00007f077ae57000)
>>
>> So it is using the 3.15.5 versions of libCom and libca.
>>
>>
>>> I see wrong values from an ezcaGet of an array of long ints. The caget shell command gets the right values.
>>
>> What version of ezca are you using?  The latest (though still over 4 years old) is on Github:
>>
>> https://github.com/epics-extensions/ezca
>>
>>
>> You are referring to the function ezcaGet in the ezca library?  So you are calling this from an application you have written?
>>
>>
>> Can you send the source code for that application, and the incorrect output you are getting?
>>
>>
>> Cheers,
>>
>> Mark
>>
>>
>>
>>
>> ________________________________
>> From: tech-talk-bounces@aps.anl.gov <tech-talk-bounces@aps.anl.gov> on behalf of Siddons, David <siddons@bnl.gov>
>> Sent: Saturday, January 20, 2018 3:16 PM
>> To: techtalk ‎[tech-talk@aps.anl.gov]‎
>> Subject: ezca
>>
>> Hi Tech-talk,
>> I'm having some trouble with EZCA. Does anyone else still use this? Do we know if there are 64-bit issues with it? Does it work with 3.15.5? I see wrong values from an ezcaGet of an array of long ints. The caget shell command gets the right values.
>> Pete.
>>
>