Experimental Physics and
Industrial Control System

"Mark Rivers" <[email protected]> · Tue, 3 Jul 2007 13:49:40 -0500

Justin,

I had a lot of trouble getting the Canberra working with Windows.  I know I did succeed at one point, but I forget what combination of cygwin vs native Windows, what libraries, etc.  It works very well with Linux.  Is there a reason it must run under Windows?  Remember the IOC can run on a different computer from the user-interface application.

I did not see libnet in your list of libraries.  Is that included in Winpcap?

Are  you sure the in-use light came on when you ran the IOC on Windows?  Is it possible that there is also a Linux IOC running, and that it owns the module?  If so, only one IOC at a time can talk to the Canberra MCA, and that could be why you are getting the "could not buy module" error.

What happens when you type nmc_show_modules and icb_show_modules at the IOC prompt?

Mark

________________________________

From: [email protected] on behalf of Justin Coleman
Sent: Tue 7/3/2007 1:18 PM
To: [email protected]
Subject: building EPICS for Canberra MCA on Windows XP

Has anyone successfully built a working EPICS system on Windows XP SP2
that can talk to a Canberra MCA? I've been trying for days with little
success.

I've used current Cygwin (win32-x86-cygwin and cygwin-x86) to build,
and the build process completes but the application is unable to talk
to the MCA. Error messages include "could not set SO_REUSEADDR" and
"could not buy module". The "in use" light on the MCA comes on but
none of the module "ready" lights do. This makes me suspect something
in the network libraries, but I have no idea where to start looking.
As an aside, I tried this under Win98 as well, but couldn't figure out
how to get the NIC's service name to put in the st.cmd script.

I've also tried Borland's free command line toolkit
(win32-x86-borland) as suggested on the EPICS web site, and VC++2005
Express Edition (win32-x86; the VC2003 Tookit is no longer available
from MS), and in both cases the applications crash. Specifically
seq-2.0.11, snc.exe crashes which stops me from completing the seq
build.

I'm using the following releases:
Base 3.14.9 (and 3.14.8.2)
Seq 2.0.11
Asyn 4.8 (and 4.6)
Autosave 4.2.1
Gensub 1.6
Sscan 2.5.3
Calc 2.6.3
Std 2.5.4
MCA 6.9
Winpcap 4.0b3

This identical hardware setup works fine under Linux. If anyone does
have a native WinXP/Canberra interface, I'd love to hear what
releases/versions you're using, so I can get at least one step closer
to having this finished.

Thanks,

-Justin Coleman

Experimental Physics and Industrial Control System

Experimental Physics and
Industrial Control System