CLONWiki - User contributions [en]

July 1, 2009 online meeting minutes

2009-07-01T02:52:44Z

98.166.91.3:

present:

1.СLAS12 trigger: following equipment needed for the CLAS12 trigger system:
* dd
* jj

CLON meeting July 1, 2009

2009-07-01T02:51:13Z

98.166.91.3:

Clas On-line Meeting, Wednesday, July 1 at 11am in Room A110
------------------------------------------------------------------

1. CLAS12 trigger

2. Others

CLON Group Meetings

2009-07-01T02:46:40Z

98.166.91.3: /* 2009 */

[[CLON meeting December 13, 2006]] >>>>> [[December 13, 2006 online meeting minutes]]

== 2007 ==

[[CLON meeting September 5, 2007]] >>>>> [[September 5, 2007 online meeting minutes]]

[[CLON meeting September 12, 2007]] >>>>> [[September 12, 2007 online meeting minutes]]

[[CLON meeting September 19, 2007]] >>>>> [[September 19, 2007 online meeting minutes]]

[[CLON meeting September 26, 2007]] >>>>> [[September 26, 2007 online meeting minutes]]

[[CLON meeting October 3, 2007]] >>>>> [[October 3, 2007 online meeting minutes]]

[[CLON meeting October 10, 2007]] >>>>> [[October 10, 2007 online meeting minutes]]

[[CLON meeting October 17, 2007]] >>>>> [[October 17, 2007 online meeting minutes]]

[[CLON meeting October 24, 2007]] >>>>> [[October 24, 2007 online meeting minutes]]

[[CLON meeting October 31, 2007]] >>>>> [[October 31, 2007 online meeting minutes]]

[[CLON meeting November 7, 2007]] >>>>> [[November 7, 2007 online meeting minutes]]

[[CLON meeting November 14, 2007]] >>>>> [[November 14, 2007 online meeting minutes]]

[[CLON meeting November 28, 2007]] >>>>> [[November 28, 2007 online meeting minutes]]

[[CLON meeting December 12, 2007]] >>>>> [[December 12, 2007 online meeting minutes]]

== 2008 ==

[[CLON meeting January 16, 2008]] >>>>> [[January 16, 2008 online meeting minutes]]

[[CLON meeting January 23, 2008]] >>>>> [[January 23, 2008 online meeting minutes]]

[[CLON meeting January 30, 2008]] >>>>> [[January 30, 2008 online meeting minutes]]

[[CLON meeting February 13, 2008]] >>>>> [[February 13, 2008 online meeting minutes]]

[[CLON meeting March 5, 2008]] >>>>> [[March 5, 2008 online meeting minutes]]

[[CLON meeting March 12, 2008]] >>>>> [[March 12, 2008 online meeting minutes]]

[[CLON meeting March 26, 2008]] >>>>> [[March 26, 2008 online meeting minutes]]

[[CLON meeting April 16, 2008]] >>>>> [[April 16, 2008 online meeting minutes]]

[[CLON meeting April 23, 2008]] >>>>> [[April 23, 2008 online meeting minutes]]

[[CLON meeting May 21, 2008]] >>>>> [[May 21, 2008 online meeting minutes]]

[[CLON meeting June 4, 2008]] >>>>> [[June 4, 2008 online meeting minutes]]

[[CLON meeting June 18, 2008]] >>>>> [[June 18, 2008 online meeting minutes]]

[[CLON meeting July 2, 2008]] >>>>> [[July 2, 2008 online meeting minutes]]

[[CLON meeting July 16, 2008]] >>>>> [[July 16, 2008 online meeting minutes]]

[[CLON meeting September 10, 2008]] >>>>> [[September 10, 2008 online meeting minutes]]

[[CLON meeting September 17, 2008]] >>>>> [[September 17, 2008 online meeting minutes]]

[[CLON meeting September 24, 2008]] >>>>> [[September 24, 2008 online meeting minutes]]

[[CLON meeting October 1, 2008]] >>>>> [[October 1, 2008 online meeting minutes]]

[[CLON meeting October 15, 2008]] >>>>> [[October 15, 2008 online meeting minutes]]

[[CLON meeting November 12, 2008]] >>>>> [[November 12, 2008 online meeting minutes]]

== 2009 ==

[[CLON meeting January 21, 2009]] >>>>> [[January 21, 2009 online meeting minutes]]

[[CLON meeting January 28, 2009]] >>>>> [[January 28, 2009 online meeting minutes]]

[[CLON meeting February 4, 2009]] >>>>> [[February 4, 2009 online meeting minutes]]

[[CLON meeting February 18, 2009]] >>>>> [[February 18, 2009 online meeting minutes]]

[[CLON meeting February 25, 2009]] >>>>> [[February 25, 2009 online meeting minutes]]

[[CLON meeting March 25, 2009]] >>>>> [[March 25, 2009 online meeting minutes]]

[[CLON meeting April 8, 2009]] >>>>> [[April 8, 2009 online meeting minutes]]

[[CLON meeting April 22, 2009]] >>>>> [[April 22, 2009 online meeting minutes]]

[[CLON meeting May 6, 2009]] >>>>> [[May 6, 2009 online meeting minutes]]

[[CLON meeting May 20, 2009]] >>>>> [[May 20, 2009 online meeting minutes]]

[[CLON meeting June 3, 2009]] >>>>> [[June 3, 2009 online meeting minutes]]

[[CLON meeting June 10, 2009]] >>>>> [[June 10, 2009 online meeting minutes]]

[[CLON meeting June 17, 2009]] >>>>> [[June 17, 2009 online meeting minutes]]

[[CLON meeting July 1, 2009]] >>>>> [[July 1, 2009 online meeting minutes]]

Scratch

2009-04-29T03:31:12Z

98.166.91.3:

Nerses:

Home number is +374 10 425049

Cell phone +374 91 206 217

-----------

clon02:/etc> ifconfig -a
lo0: flags=2001000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4,VIRTUAL> mtu 8232 index 1
inet 131.225.70.20 netmask ff000000
age0: flags=1000842<BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 2
inet 131.225.70.20 netmask fffffc00 broadcast 131.225.255.255
ether 0:a0:80:0:52:e5
eri0: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 3
inet 129.57.167.2 netmask ffffff00 broadcast 129.57.167.255
ether 0:3:ba:1d:9b:c0
clon02:/etc>

-------

SUNW-MSG-ID: ZFS-8000-HC, TYPE: Error, VER: 1, SEVERITY: Major
EVENT-TIME: Thu Mar 5 17:41:00 EST 2009
PLATFORM: SUNW,Netra-240, CSN: -, HOSTNAME: clon10
SOURCE: zfs-diagnosis, REV: 1.0
EVENT-ID: 2f3d5430-2bbb-c8aa-87d5-f79b44f89edf
DESC: The ZFS pool has experienced currently unrecoverable I/O failures. Refer to http://sun.com/msg/ZFS-8000-HC for more information.
AUTO-RESPONSE: No automated response will be taken.
IMPACT: Read and write I/Os cannot be serviced.
REC-ACTION:

The pool has experienced I/O failures. Since the ZFS pool property 'failmode'
is set to 'wait', all I/Os (reads and writes) are blocked. See the zpool(1M)
manpage for more information on the 'failmode' property. Manual intervention
is required for I/Os to be serviced. You can see which devices are
affected by running 'zpool status -x':

# zpool status -x
pool: test
state: FAULTED
status: There are I/O failures.
action: Make sure the affected devices are connected, then run 'zpool clear'.
see: http://www.sun.com/msg/ZFS-8000-HC
scrub: none requested
config:

NAME STATE READ WRITE CKSUM
test FAULTED 0 13 0 insufficient replicas
c0t0d0 FAULTED 0 7 0 experienced I/O failures
c0t1d0 ONLINE 0 0 0

errors: 1 data errors, use '-v' for a list

After you have made sure the affected devices are connected, run 'zpool clear'
to allow I/O to the pool again:

# zpool clear test

If I/O failures continue to happen, then applications and commands for the
pool may hang. At this point, a reboot may be necessary to allow I/O to the
pool again.

----

mgetty

Sergey --- does this help you ? Today marked the 3rd week since this
case was opened....

Paul

-------- Original Message --------
Subject: CASE 66172087
Date: Wed, 28 Jan 2009 12:39:51 -0500
From: Roland 'butch' Morrissette - Sun Microsystems
<Roland.Morrissette@sun.com>
To: letta@jlab.org

Paul

Received this from engineering. Hopefully this is of some helpfull.

xdm is creating $HOME/.Xauthority file, xauth only reads it. In
$HOME/.Xdefaults file try adding the following entry as an alternate
location to see if it works.
*

DisplayManager.DISPLAY.userAuthDir

*/DISPLAY should be the actual display, like

/DisplayManager.host1:0.0.userAuthDir: /path/to/alternate/file

*
*(If this does not work and still $HOME/.Xauthority file gets written
try changing the permissions on $HOME/.Xauthority file to readonly)

Regards,

--

Roland 'Butch' Morrissette
Sun Service OS Support
Sun Microsystems, Inc.

phone: (781) 442-7112
email: roland.morrissette@sun.com
(800)USA-4SUN (Reference your Case Id #)

My Working Hours : 8am-4pm ET, Monday thru Friday
My Manager's Email: dawn.ball@sun.com

5126
303-6644

CLAS12 DC (Mac 14-nov-2007): 2 stereo, +-6 degrees, good resolution (1% dp/p, 1 mrad angle), six 6-layer superlayers, 112 wires per layer; reconstruction improvements: use double hits, use segment angle in road dictionary, early l-r ambig. resolution (now it resolved locally and then corrected after track reconstructed ?), find tracks with no TOF hit and cut off accidental tracks (using residials ?), derive off-diagonal terms in error matrix

SVT readout:

SVX4 - old chip
132ns clock, 40pipeline cells ->5.2us trigger latency; can select readout window like pipeline TDCs (position defined +-132us, window size 132ns fixed)
initial part stored upto 4 events, they are rotating internally
32 bits per hit, 128 channels per chip, ... -> 3.2us per chip to get data from the chip to the buffer of 512 full events
L2 pipeline 16us
L1 latency from Amrit is 3us, Amrit will try to make it 4us
Use the same clock as entire CLAS12 trigger system (256MHz)

FSSR 125ns instead of 132ns (built for BTev, never used)
self-triggering, do not need L1ACCEPT, L2 pipe 16us can be implemented

SVX4 goes to review !!!

Generic DAQ drawing will be sent to Amrit in April

Scratch

2009-04-29T03:30:26Z

98.166.91.3:

Nerses:
Home number is +374 10 425049
Cell phone +374 91 206 217

-----------

clon02:/etc> ifconfig -a
lo0: flags=2001000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4,VIRTUAL> mtu 8232 index 1
inet 131.225.70.20 netmask ff000000
age0: flags=1000842<BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 2
inet 131.225.70.20 netmask fffffc00 broadcast 131.225.255.255
ether 0:a0:80:0:52:e5
eri0: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 3
inet 129.57.167.2 netmask ffffff00 broadcast 129.57.167.255
ether 0:3:ba:1d:9b:c0
clon02:/etc>

-------

SUNW-MSG-ID: ZFS-8000-HC, TYPE: Error, VER: 1, SEVERITY: Major
EVENT-TIME: Thu Mar 5 17:41:00 EST 2009
PLATFORM: SUNW,Netra-240, CSN: -, HOSTNAME: clon10
SOURCE: zfs-diagnosis, REV: 1.0
EVENT-ID: 2f3d5430-2bbb-c8aa-87d5-f79b44f89edf
DESC: The ZFS pool has experienced currently unrecoverable I/O failures. Refer to http://sun.com/msg/ZFS-8000-HC for more information.
AUTO-RESPONSE: No automated response will be taken.
IMPACT: Read and write I/Os cannot be serviced.
REC-ACTION:

The pool has experienced I/O failures. Since the ZFS pool property 'failmode'
is set to 'wait', all I/Os (reads and writes) are blocked. See the zpool(1M)
manpage for more information on the 'failmode' property. Manual intervention
is required for I/Os to be serviced. You can see which devices are
affected by running 'zpool status -x':

# zpool status -x
pool: test
state: FAULTED
status: There are I/O failures.
action: Make sure the affected devices are connected, then run 'zpool clear'.
see: http://www.sun.com/msg/ZFS-8000-HC
scrub: none requested
config:

NAME STATE READ WRITE CKSUM
test FAULTED 0 13 0 insufficient replicas
c0t0d0 FAULTED 0 7 0 experienced I/O failures
c0t1d0 ONLINE 0 0 0

errors: 1 data errors, use '-v' for a list

After you have made sure the affected devices are connected, run 'zpool clear'
to allow I/O to the pool again:

# zpool clear test

If I/O failures continue to happen, then applications and commands for the
pool may hang. At this point, a reboot may be necessary to allow I/O to the
pool again.

----

mgetty

Sergey --- does this help you ? Today marked the 3rd week since this
case was opened....

Paul

-------- Original Message --------
Subject: CASE 66172087
Date: Wed, 28 Jan 2009 12:39:51 -0500
From: Roland 'butch' Morrissette - Sun Microsystems
<Roland.Morrissette@sun.com>
To: letta@jlab.org

Paul

Received this from engineering. Hopefully this is of some helpfull.

xdm is creating $HOME/.Xauthority file, xauth only reads it. In
$HOME/.Xdefaults file try adding the following entry as an alternate
location to see if it works.
*

DisplayManager.DISPLAY.userAuthDir

*/DISPLAY should be the actual display, like

/DisplayManager.host1:0.0.userAuthDir: /path/to/alternate/file

*
*(If this does not work and still $HOME/.Xauthority file gets written
try changing the permissions on $HOME/.Xauthority file to readonly)

Regards,

--

Roland 'Butch' Morrissette
Sun Service OS Support
Sun Microsystems, Inc.

phone: (781) 442-7112
email: roland.morrissette@sun.com
(800)USA-4SUN (Reference your Case Id #)

My Working Hours : 8am-4pm ET, Monday thru Friday
My Manager's Email: dawn.ball@sun.com

5126
303-6644

CLAS12 DC (Mac 14-nov-2007): 2 stereo, +-6 degrees, good resolution (1% dp/p, 1 mrad angle), six 6-layer superlayers, 112 wires per layer; reconstruction improvements: use double hits, use segment angle in road dictionary, early l-r ambig. resolution (now it resolved locally and then corrected after track reconstructed ?), find tracks with no TOF hit and cut off accidental tracks (using residials ?), derive off-diagonal terms in error matrix

SVT readout:

SVX4 - old chip
132ns clock, 40pipeline cells ->5.2us trigger latency; can select readout window like pipeline TDCs (position defined +-132us, window size 132ns fixed)
initial part stored upto 4 events, they are rotating internally
32 bits per hit, 128 channels per chip, ... -> 3.2us per chip to get data from the chip to the buffer of 512 full events
L2 pipeline 16us
L1 latency from Amrit is 3us, Amrit will try to make it 4us
Use the same clock as entire CLAS12 trigger system (256MHz)

FSSR 125ns instead of 132ns (built for BTev, never used)
self-triggering, do not need L1ACCEPT, L2 pipe 16us can be implemented

SVX4 goes to review !!!

Generic DAQ drawing will be sent to Amrit in April

Clasweb

2009-02-14T20:41:14Z

98.166.91.3:

'''clasweb''' (it is alias, canonic name is '''claspc28''') is official CLAS web server accessable from outside of JLAB. Several online-related services are running there, including logbook and online database interface for ''clasprod'' database on ''clondb1'' machine. Greg Riccardi is author and custodian for those two projects. Marty Wise from Computer Center is responsible for that machine, but Sergey Boyarinov has limited access to it as well. In particular he can restart ''apache'' and ''tomcat'' services using following commands:

ssh boiarino@claspc28
/apps/bin/sudo /etc/init.d/tomcat stop
/apps/bin/sudo /etc/init.d/httpd stop
/apps/bin/sudo /etc/init.d/httpd start
/apps/bin/sudo /etc/init.d/tomcat start

Restarting ''tomcat'' usually required in case if logbook is not working, and normally it is not necessary to restart ''httpd''.

'''Slow control history''' software is located in ''/group/clas/www/clasweb/htbin/epics_history'' directory on claspc28. In particular script ''epics/pl'' displays main control GUI for the history graphs, and ''add_to_list.pl'' controls adding and deleting of items from the list. To work properly following attributes must be used (described in ''db_parms.pm'', which must be included into any scripts accessing database):

$hostname = 'clondb1.jlab.org';
$user = 'clasweb';
$password = '';
$database = 'epics';

See 'clasweb' user privileges for 'claspc28' on 'clondb1' database server.

Clondaq2

2008-12-31T19:34:05Z

98.166.91.3:

Clondaq2 is X4200 server running Solaris, s/n: 0626AM2523, f/n: F46985. It is second DAQ server serving mostly to run Event Recorder and handle SILO traffic.

Network ports:

clondaq2 - e1000g0
clondaq2-daq1 - e1000g1
clondaq2-daq2 - e1000g2

After Solaris installation:

1. Add following SILO-related lines to the ''/etc/auto_direct'' file:

/usr/local/mss -rw,bg clonfs2:/vol/vol0/local/mss
/ssa -rw,bg clonfs2:/vol/vol0/ssa

Restart autofs:

svcadm restart system/filesystem/autofs

2. Make ''/raid/stage_in'' link:

cd /
ln -s /ssa/active raid

3. Make ''/mss'' link:

cd /
ln -s /w/mss mss

4. Adjust [[Sudo]] config file.

5. Make sure [[ZFS]] RAID partitions are mounted.

Clondaq1

2008-12-31T19:32:19Z

98.166.91.3:

Serial 'ser mgr' port login: root/changeme

This server is being used as *DAQ Event Builder*
SUN Fire V40z, 4x1.8GHz i86, 8GB RAM, s/n: XG043571186, f/n: F418263.

[[http://www.sun.com/servers/entry/v40z/specs.jsp Specifications]]
[[http://sunsolve.sun.com/handbook_pub/Systems/SunFireV40z/SunFireV40z.html System Hand Book]]

Network ports:

clondaq1 - e1000g0
clondaq1-daq1 - bge0
clondaq1-daq2 - e1000g1

After Solaris installation:

1. Add following SILO-related lines to the /etc/auto_direct file:

/usr/local/mss -rw,bg clonfs2:/vol/vol0/local/mss
/ssa -rw,bg clonfs2:/vol/vol0/ssa

Restart autofs:

svcadm restart system/filesystem/autofs

2. Make /raid/stage_in link:

cd /
ln -s /ssa/active raid

Clondaq1

2008-12-31T19:31:37Z

98.166.91.3:

Serial 'ser mgr' port login: root/changeme

This server is being used as *DAQ Event Builder*
SUN Fire V40z, 4x1.8GHz i86, 8GB RAM, s/n: XG043571186, f/n: F418263.

[[http://www.sun.com/servers/entry/v40z/specs.jsp][Specifications]]
[[http://sunsolve.sun.com/handbook_pub/Systems/SunFireV40z/SunFireV40z.html][System Hand Book]]

Network ports:

clondaq1 - e1000g0
clondaq1-daq1 - bge0
clondaq1-daq2 - e1000g1

After Solaris installation:

1. Add following SILO-related lines to the /etc/auto_direct file:

/usr/local/mss -rw,bg clonfs2:/vol/vol0/local/mss
/ssa -rw,bg clonfs2:/vol/vol0/ssa

Restart autofs:

svcadm restart system/filesystem/autofs

2. Make /raid/stage_in link:

cd /
ln -s /ssa/active raid

SmartSockets

2008-12-19T04:17:08Z

98.166.91.3:

SmartSockets is the communication package used by many CLON programs. We have license with TIBCO, it must be renewed every year, normally in September.

'''Startup procedure'''

Following command must be executed on clondb1 after reboot (until startup script is ready):

rtserver -server_names clondb1 >& /dev/null &

TIBCO download site: http://download.tibco.com/. To login use ''boiarino@jlab.org'' as user name and usual password.

Sergey Boyarinov is an authorized user for the following account: SURAJE-13612-13612.

'''NOTES from TIBCO'''

If any of your product entitlements require license keys/tickets, they will be forwarded to you in a
separate message. In some cases, you may be required to provide additional information. Please take a
moment to review the instructions and respond accordingly.

Refer to the online Help for assistance, if you experience any problems while accessing your account.

For more information about getting started with TIBCO, please access the Customer Care Center at
http://www.tibco.com/services/customercare.jsp

The TIBCO Customer Care Center is a single point of contact for our customers. TIBCO Customer Care
Center can:

- Connect customers with the right individual or group within TIBCO to expedite answers or resolutions
in a timely manner.

- Respond to administrative issues such as sales inquiries, contract questions, maintenance renewals,
product information, marketing, locating an account executive, order status and partnership programs.

- Provide information about support, consulting, and training/educational services and programs.

- Help customers get started with TIBCO.

DATEL DVME-628

2008-12-12T04:41:48Z

98.166.91.3:

Discontinued product !

Company site: http://www.datel.com/

Manual [https://clonwiki.jlab.org/wiki/clondocs/man/VME/dvme628.pdf (pdf)]

DATEL DVME-628

2008-12-12T04:40:33Z

98.166.91.3:

Discontinued product !

Company site: http://www.datel.com/

Manual [ (pdf)]

DATEL DVME-628

2008-12-12T04:40:21Z

98.166.91.3:

Discontinued product !
Company site: http://www.datel.com/
Manual [ (pdf)]

CAEN V288

2008-12-12T04:36:35Z

98.166.91.3:

Manual [https://clonwiki.jlab.org/wiki/clondocs/man/VME/v288_rev0.pdf (pdf)]

Electronics Documentation

2008-12-12T04:35:28Z

98.166.91.3:

[https://clonwiki.jlab.org/wiki/clondocs/Docs/2917.pdf 2917 VME-CAMAC Interface (pdf)]

[https://clonwiki.jlab.org/wiki/clondocs/Docs/JLAB_NIM_LVL1FWDCarriage.pdf JLAB NIM ADC Gate Electronics (pdf)]

[https://clonwiki.jlab.org/wiki/clondocs/Docs/JLAB_VME_FIFO_board.pdf JLAB VME FIFO Board (pdf)]

[https://clonwiki.jlab.org/wiki/clondocs/Docs/JLAB_VME_Latch_driver.pdf JLAB VME Latch Driver Board (pdf)]

[https://clonwiki.jlab.org/wiki/clondocs/Docs/JLAB_VME_MLU_board.pdf JLAB VME MLU Board (pdf)]

[https://clonwiki.jlab.org/wiki/clondocs/Docs/JLAB_VME_OR_board.pdf JLAB VME OR Board (pdf)]

[https://clonwiki.jlab.org/wiki/clondocs/Docs/JLAB_VME_ts2_board.pdf JLAB VME TS2 Board (pdf)]

[https://clonwiki.jlab.org/wiki/clondocs/Docs/JLAB_VME_f1TDC_User_Manual_V1.1.pdf JLAB VME F1TDC Board User Manual (pdf)]

[https://clonwiki.jlab.org/wiki/clondocs/Docs/JLAB_VME_DiscrManual2002.pdf JLAB VME Discriminator (2002) (pdf)]

[https://clonwiki.jlab.org/wiki/clondocs/Docs/caen_SY527.pdf CAEN SY527 HV Mainframe (pdf)]

[https://clonwiki.jlab.org/wiki/clondocs/man/VME/v288_rev0.pdf CAEN V288 VME Interface to SY527 HV Mainframe (pdf)]

[https://clonwiki.jlab.org/wiki/clondocs/Docs/v895_rev2.pdf CAEN V895 VME Discriminator (pdf)]

[https://clonwiki.jlab.org/wiki/clondocs/Docs/TS140_Manual.pdf TS140 Cyclades Terminal Server Manual (pdf)]

[https://clonwiki.jlab.org/wiki/clondocs/man/VME/VMIC_VMIVME_6016_Manual.pdf VMIC VMIVME6016 Manual (pdf)]

[https://clonwiki.jlab.org/wiki/clondocs/Docs/VIPC616_C2_UM_6.pdf VIPC VME 616 Manual (pdf)]

[https://clonwiki.jlab.org/wiki/clondocs/man/VME/VMIC_VME_3122A_Manual.pdf VMIC VME3122A Manual (pdf)]

[https://clonwiki.jlab.org/wiki/clondocs/man/VME/VMIC_VMIVME_2232_Manual.pdf VMIC VMIVME2232 Manual (pdf)]

[https://clonwiki.jlab.org/wiki/clondocs/man/VME/VMIVME_1129_Manual.pdf VMIC VMIVME1129 Manual (pdf)]

[https://clonwiki.jlab.org/wiki/clondocs/man/VME/VMIVME_2120_Manual.pdf VMIVME2120 Manual (pdf)]

[https://clonwiki.jlab.org/wiki/clondocs/Docs/DVCSChillerControlManual.pdf DVCS Chiller Control Manual (pdf)]

Compcontrol CC121

2008-12-12T04:33:54Z

98.166.91.3:

Company site: http://www.compcontrol.com/.

Manual [https://clonwiki.jlab.org/wiki/clondocs/man/VME/cc121.pdf (pdf)]

Compcontrol CC121

2008-12-12T04:30:00Z

98.166.91.3:

Company site: http://www.compcontrol.com/.

Manual:

EPICS: vxWorks IOC

2008-12-12T04:25:24Z

98.166.91.3:

VxWorks IOCs are normally running in VME crate controllers.

== Hardware List ==

Following boards are used in CLAS VME vxWorks IOC crates:

{| border="1" cellpadding="2"
!width="200"|Brand/Model
!width="250"|IOC List
!width="150"|Driver subdirectory (in $BASEB/src/)
|-
|[[Xycom DIO XVME-240]] ||classc1, classc3, classc8 ||...
|-
|[[Xycom XVME-564]] ||classc3 ||...
|-
|[[Xycom XVME-560]] ||classc3, classc8 ||...
|-
|[[Struck SIS3801]] ||classc1, classc6, classc4, classc2 ||...
|-
|[[Joerger VSC16]] ||classc1, classc8 ||...
|-
|[[DATEL DVME-628]] ||classc1, classc4 ||...
|-
|[[OMS VME44]] ||classc1, classc8 ||...
|-
|[[Compcontrol CC121]] ||classc5, classc12 ||...
|-
|[[CAEN V775]] ||classc7 ||...
|-
|[[SYSTRAN VMESC5]] ||classc12 ||...
|-
|[[SBS VIPC616]] ||classc6, iocptarg ||...
|-
|[[OMS VS4]] ||classc2 ||...
|-
|[[CAEN V288]] ||camac2, dccntrl ||...
|-
|[[VMIC VMIVME-3122]] ||iochlb ||...
|-
|[[VMIC VMIVME-2120]] ||iochlb ||...
|-
|[[VMIC VMIVME-1129]] ||iochlb ||...
|-
|Machine Protection System I/O ???? ||iochlb ||...
|-
|Beam Viewer / SLM Control Board ???? ||iochlb ||...
|-
|[[HYTEC VSD2992]] ||iochlb ||...
|-
|[[VMIC VMIVME-2232]] ||iocptarg ||camacApp
|-
|[[JLAB FLEXIO]] ||iocptarg ||...
|-
|[[VMIC VMIVME-6016]] ||sc-laser1, camac1 ||...
|}

== Standard Installation ==

cd $EPICS_BASE
./bin/solaris-sparc/makeBaseApp.pl -b $EPICS_BASE -t ioc iocsy527
./bin/solaris-sparc/makeBaseApp.pl -b $EPICS_BASE -i -t ioc iocsy527
The following target architectures are available in base:
solaris-sparc
vxWorks-ppc604_long
solaris-x86
linux-x86
What architecture do you want to use? vxWorks-ppc604_long
The following applications are available:
caclient
caserver
ioc
ioccamac
iocCore1
iocCore
iochv
iocsy527
ioctest
support
What application should the IOC(s) boot?
The default uses the IOC's name, even if not listed above.
Application name? iocsy527

It creates directories ''iocsy527App'' and ''iocBoot/iocsy527''.

cd iocsy527App
gmake

It compiles both unix and vxWorks versions.

cd ../iocBoot/iocsy527
gmake

It creates useful ''cdCommands'' file. File ''st.cmd' in the same directory contains an example of startup script. Uncommect followibg line

cd "/usr/local/clas/devel/R3.14.8.2/base-3.14.8.2/iocBoot/iocsy527"

and boot. Everything looks good.

== Makefile, source files ==

Original Makefile in ''/usr/local/clas/devel/R3.14.8.2/base-3.14.8.2/iocsy527App/src'':

TOP=../..
include $(TOP)/configure/CONFIG
#----------------------------------------
# ADD MACRO DEFINITIONS AFTER THIS LINE
#=============================
#=============================
# build an ioc application
PROD_IOC = iocsy527
DBD += iocsy527.dbd
# iocsy527.dbd will be made up from these files:
iocsy527_DBD += base.dbd
#include definitions for any other support applications needed
#iocsy527_DBD += xxx.dbd
# <name>_registerRecordDeviceDriver.cpp will be created from <name>.dbd
iocsy527_SRCS += iocsy527_registerRecordDeviceDriver.cpp
iocsy527_SRCS_DEFAULT += iocsy527Main.cpp
iocsy527_SRCS_vxWorks += -nil-
#The following adds support from base/src/vxWorks
iocsy527_OBJS_vxWorks += $(EPICS_BASE_BIN)/vxComLibrary
#add a definition for each support application used by this application
#iocsy527_LIBS += xxx
#NOTES:
# 1)It is not possible to build sncExample both as a component of iocsy527
# and standalone. You must choose only one.
# 2)To build sncExample SNCSEQ must be defined in <top>/configure/RELEASE
#The following builds sncExample as a component of iocsy527
#iocsy527_SRCS += sncExample.stt
#iocsy527_LIBS += seq pv
iocsy527_LIBS += $(EPICS_BASE_IOC_LIBS)
#The following builds sncExample as a standalone application
#PROD_HOST += sncExample
#sncExample_SNCFLAGS += +m
#sncExample_SRCS += sncExample.stt
#sncExample_LIBS += seq pv
#sncExample_LIBS += $(EPICS_BASE_HOST_LIBS)
#===========================
include $(TOP)/configure/RULES
#----------------------------------------
# ADD RULES AFTER THIS LINE

Copy following files from 'DriverOld':

sy527.h
sy527epics1.h
v288.h
sy527.c
sy527_test.c
sy527epics1.c
v288.c

Add following to Makefile:

iocsy527_SRCS += v288
iocsy527_SRCS += sy527
iocsy527_SRCS += sy527epics1

Type ''gmake'' - everything compiles and linked with new source files.

Copy following files from 'IocshellOld':

command.h
sub.c
bigsub.c
devCAEN.c

Add them to the Makefile the same way, and type 'gmake'. It complains for UNIX on linking, but command

gmake vxWorks-ppc604_long

works fine. Reboot IOC - no undefined symbols.

Add our HV database and 'src' directories into ''cdCommands'':

db = "/usr/local/clas/devel/R3.14.8.2/EPICS/app/hvca/db"
src = "/usr/local/clas/devel/R3.14.8.2/base-3.14.8.2/iocsy527App/src"

Add following two lnes to startup script after iocInit() (before - complains):

cd src
dbLoadDatabase("support.dbd")
cd db
dbLoadRecords("caen_04.db")

Reboot ioc again, type 'dbl' - all records printed.

Try to caget one of them - vxWorks printed error: we got through but corresponding function support is missing.

Do following on vxWorks prompt:

registryFunctionAdd("InitChannel",InitChannel)
registryFunctionAdd("ScanChannel",ScanChannel)

does not help. Run driver commands in the very end of startup script - does not help:

sy527Init()
sy527Start(0,"sy527_0x100000_9")
sy527GetMap(0)

== trying same, but use type 'example' instead of 'ioc' ==

cd $EPICS_BASE
./bin/solaris-sparc/makeBaseApp.pl -b $EPICS_BASE -t example iocsy527
./bin/solaris-sparc/makeBaseApp.pl -b $EPICS_BASE -i -t ioc iocsy527

Everything compiles and boots, 'caget' works.

Now, lets customize it for sy517:

* copy following v288- and sy527-related *.h and *.c files to ''$EPICS_BASE/iocsy527/src'' directory:

v288.c
v288.h
sy527.c
sy527.h
sy527_test.c
sy527epics.c
sy527epics.h

(sy527epics1 was renamed to sy527epics in a process). Add follwoing lines to the Makefile:

iocsy527_SRCS += v288.c
iocsy527_SRCS += sy527.c
iocsy527_SRCS += sy527epics.c
iocsy527_SRCS += sy527_test.c

Compile, reboot - looks good.

* '''NOTES:''' our CAEN HV software structure

1. Everything starts from ''$APP/hvca/db/caen_04.dat'' or similar file generated from ''caen.dat''
2. Statements ''field(INAM,InitChannel)'' and ''field(SNAM,ScanChannel)'' requires functions ''InitChannel'' and ''ScanChannel'';
those functions are in ''bigsub.c''
2.1 ''bigsub.c'' calls one function ''CAEN_GetChannel'', that function is in ''sy527epics.c''
2.2 ''sy527epics.c'' contains following functions:
CAEN_HVinit
CAEN_HVstart
CAEN_HVstop
CAEN_HVload
CAEN_GetHv
CAEN_GetAlarm
CAEN_GetValidity
CAEN_SetHV
CAEN_GetProperty
CAEN_GetChannel
3. Statement ''field(DTYP,"CAEN_HV")'' requires ...
3.1 file ''support.dbd'' contains following statements:
device(ao,VME_IO,devAoCAEN,"CAEN_HV")
device(bo,VME_IO,devBoCAEN,"CAEN_HV")
device(bi,VME_IO,devBiCAEN,"CAEN_HV")
3.2 file ''devCAEN.c'' contains following statements:
epicsExportAddress(dset,devAoCAEN)
epicsExportAddress(dset,devBoCAEN)
epicsExportAddress(dset,devBiCAEN)
3.3 structure ''devAoCAEN'' contains for example field ''init_record'' containing function ''init_ao''

Continue customization. Copy ''devCAEN.c'', ''command.h'' and ''support.dbd'' as ''CAENSupport.dbd'' to ''src'' directory. Modify Makefile changing devXxxSoft to devCAEN and xxxSupport to CAENSupport everywhere (I decided not to just add new names, but eliminate old ones, because
for example 'xxxSupport_SRCS += xxxRecord.c' referes to xxxSupport library, and I want to build only one library CAENSupport). Also:

mv xxxSupport.dbd xxxSupport.dbd_obsolete
mv devXxxSoft.c devXxxSoft.c_obsolete

From directory ''iocsy527App'' type 'gmake vxWorks-ppc604_long clean' and 'gmake vxWorks-ppc604_long', compiles fine. Reboot, have error:

## Load record instances
dbLoadRecords("db/dbExample1.db","user=boiarino")
Error Last token ")"
input line: record(xxx, "boiarino:xxxExample")
in: file db/dbExample1.db line 39
db_parse returned -1
value = -1 = 0xffffffff
filename="../dbLexRoutines.c" line number=910
Record Type does not exist dbFindRecordType

This is probably a result of eliminating xxxSupport.dbd and devXxxSoft.c. (INTERESTING: in Makefile there is following code:

# xxxRecord.h will be created from xxxRecord.dbd
DBDINC += xxxRecord

and devXxxSoft.c has

#include "xxxRecord.h"

- just good to know).

In Makefile comment out lines

########DBDINC += xxxRecord
########CAENSupport_SRCS += xxxRecord.c

and in startup script

#####dbLoadRecords("db/dbExample1.db","user=boiarino")

because it does not work anyway. Rename unused files:

mv xxxRecord.c xxxRecord.c_obsolete
mv xxxRecord.dbd xxxRecord.dbd_obsolete

Recompile, reboot. Looks good.

Copy bigsub.c (our init and scan functions for the 'bigsubRecord'). Add following to the Makefile:

iocsy527_SRCS += bigsub.c

Recompile, reboot. Looks good.

Now interesting part. Add following to the startup script:

db = "/usr/local/clas/devel/R3.14.8.2/EPICS/app/hvca/db"

CLON Index

2008-12-12T04:24:59Z

98.166.91.3:

[[Apache]]

[[Bootp]]

[[CAEN SY527 Mainframe]]

[[CAEN V288]]

[[CAEN V775]] TDC Board

[[Capfast]]

[[Cisco Switches]]

[[Clasweb]]

[[Clon00]]

[[Clon01]]

[[Clon02]]

[[Clon03]]

[[Clon04]]

[[Clon05]]

[[Clon06]]

[[Clon10]]

[[Clon20]]

[[Clondaq1]]

[[Clondaq2]]

[[Clondb1]]

[[Clonfs]] Main RAID System

[[Clonfs2]]

[[Clonmon]]

[[Clonmon1]]

[[Clonpc2]]

[[Clonweb]]

[[Clonwiki]]

[[clonhp]]

[[clonhp2]]

[[Compcontrol CC121]]

[[CycladesTS1000]]

[[DATEL DVME-628]]

[[DNS server]]

[[Electronics Documentation]]

[[EtherLite32]]

[[EPICS Base Installation]]

[[EPICS: Software IOC]]

[[EPICS: vxWorks IOC]]

[[EPICS: Software IOC for CAEN HV]]

[[EPICS: generation of DBs and GUIs for HV]]

[[EPICS: CVS usage examples]]

[[EPICS: Gamma Profiler]]

[[Event Monitor]]

[[Fiber Channel Switches]]

[[Foundry BigIron 15000 Switch]]

[[Foundry Switches]]

[[JAVA installation]]

[[JLAB Discriminators]]

[[Joerger VSC16]]

[[HYTEC VSD2992]]

[[Labeling Machines]]

[[Linux Installation Procedure]]

[[Linux Customization on CLON Cluster]]

[[Lnf cluster]]

[[Mac OS X Installation Procedure]]

[[MRTG]]

[[mSQL]]

[[MySQL Installation]]

[[MySQL Usage]]

[[Nagios]]

[[Nagios Plugins]]

[[NFS]]

[[NIS server]]

[[Nrpe]]

[[Ntp]]

[[OMS VME44]]

[[OMS VS4]]

[[OpenSSL]]

[[PERL]]

[[Procmail]]

[[raidold]]

[[Routing]]

[[Rrdtool]]

[[SBS VIPC616]]

[[Serial Connections from Computer Ports]]

[[Slow Controls Time History]]

[[SmartSockets]]

[[SNMP]]

[[Software Documentation]]

[[Solaris Installation Procedure]]

[[Solaris Customization on CLON Cluster]]

[[Struck SIS3801]]

[[Sudo]]

[[SUN Microsystems]]

[[SYSTRAN VMESC5]]

[[Tcl/Tk]]

[[Tftp]]

[[JLAB FLEXIO]]

[[Troubleshooting printing]]

[[UNIX Automount on CLON Cluster]]

[[UPS (Uninterruptible Power Supplies)]]

[[UPS CHB1]]

[[UPS CHB2]]

[[UPS Troubleshooting]]

[[VI editor]]

[[VMIC VMIVME-3122]]

[[VMIC VMIVME-2120]]

[[VMIC VMIVME-1129]]

[[VMIC VMIVME-2232]]

[[VMIC VMIVME-6016]]

[[VNC]]

[[WIENER]]

[[Wiki]]

[[Wiring]]

[[X server]]

[[Xycom DIO XVME-240]]

[[Xycom XVME-564]]

[[Xycom XVME-560]]

[[ZFS]]

CLON Index

2008-12-12T04:18:26Z

98.166.91.3:

[[Apache]]

[[Bootp]]

[[CAEN SY527 Mainframe]]

[[CAEN V775]] TDC Board

[[Capfast]]

[[Cisco Switches]]

[[Clasweb]]

[[Clon00]]

[[Clon01]]

[[Clon02]]

[[Clon03]]

[[Clon04]]

[[Clon05]]

[[Clon06]]

[[Clon10]]

[[Clon20]]

[[Clondaq1]]

[[Clondaq2]]

[[Clondb1]]

[[Clonfs]] Main RAID System

[[Clonfs2]]

[[Clonmon]]

[[Clonmon1]]

[[Clonpc2]]

[[Clonweb]]

[[Clonwiki]]

[[clonhp]]

[[clonhp2]]

[[CycladesTS1000]]

[[DNS server]]

[[Electronics Documentation]]

[[EtherLite32]]

[[EPICS Base Installation]]

[[EPICS: Software IOC]]

[[EPICS: vxWorks IOC]]

[[EPICS: Software IOC for CAEN HV]]

[[EPICS: generation of DBs and GUIs for HV]]

[[EPICS: CVS usage examples]]

[[EPICS: Gamma Profiler]]

[[Event Monitor]]

[[Fiber Channel Switches]]

[[Foundry BigIron 15000 Switch]]

[[Foundry Switches]]

[[JAVA installation]]

[[JLAB Discriminators]]

[[Labeling Machines]]

[[Linux Installation Procedure]]

[[Linux Customization on CLON Cluster]]

[[Lnf cluster]]

[[Mac OS X Installation Procedure]]

[[MRTG]]

[[mSQL]]

[[MySQL Installation]]

[[MySQL Usage]]

[[Nagios]]

[[Nagios Plugins]]

[[NFS]]

[[NIS server]]

[[Nrpe]]

[[Ntp]]

[[OpenSSL]]

[[PERL]]

[[Procmail]]

[[raidold]]

[[Routing]]

[[Rrdtool]]

[[Serial Connections from Computer Ports]]

[[Slow Controls Time History]]

[[SmartSockets]]

[[SNMP]]

[[Software Documentation]]

[[Solaris Installation Procedure]]

[[Solaris Customization on CLON Cluster]]

[[Sudo]]

[[SUN Microsystems]]

[[Tcl/Tk]]

[[Tftp]]

[[Troubleshooting printing]]

[[UNIX Automount on CLON Cluster]]

[[UPS (Uninterruptible Power Supplies)]]

[[UPS CHB1]]

[[UPS CHB2]]

[[UPS Troubleshooting]]

[[VI editor]]

[[VMIC VMIVME-3122]]

[[VMIC VMIVME-2120]]

[[VMIC VMIVME-1129]]

[[VMIC VMIVME-2232]]

[[VMIC VMIVME-6016]]

[[VNC]]

[[WIENER]]

[[Wiki]]

[[Wiring]]

[[X server]]

[[Xycom DIO XVME-240]]

[[Xycom XVME-564]]

[[Xycom XVME-560]]

[[ZFS]]

Electronics Documentation

2008-12-11T01:04:07Z

98.166.91.3:

[https://clonwiki.jlab.org/wiki/clondocs/Docs/2917.pdf 2917 VME-CAMAC Interface (pdf)]

[https://clonwiki.jlab.org/wiki/clondocs/Docs/JLAB_NIM_LVL1FWDCarriage.pdf JLAB NIM ADC Gate Electronics (pdf)]

[https://clonwiki.jlab.org/wiki/clondocs/Docs/JLAB_VME_FIFO_board.pdf JLAB VME FIFO Board (pdf)]

[https://clonwiki.jlab.org/wiki/clondocs/Docs/JLAB_VME_Latch_driver.pdf JLAB VME Latch Driver Board (pdf)]

[https://clonwiki.jlab.org/wiki/clondocs/Docs/JLAB_VME_MLU_board.pdf JLAB VME MLU Board (pdf)]

[https://clonwiki.jlab.org/wiki/clondocs/Docs/JLAB_VME_OR_board.pdf JLAB VME OR Board (pdf)]

[https://clonwiki.jlab.org/wiki/clondocs/Docs/JLAB_VME_ts2_board.pdf JLAB VME TS2 Board (pdf)]

[https://clonwiki.jlab.org/wiki/clondocs/Docs/JLAB_VME_f1TDC_User_Manual_V1.1.pdf JLAB VME F1TDC Board User Manual (pdf)]

[https://clonwiki.jlab.org/wiki/clondocs/Docs/JLAB_VME_DiscrManual2002.pdf JLAB VME Discriminator (2002) (pdf)]

[https://clonwiki.jlab.org/wiki/clondocs/Docs/caen_SY527.pdf CAEN SY527 HV Mainframe (pdf)]

[https://clonwiki.jlab.org/wiki/clondocs/Docs/v288_rev0.pdf CAEN V288 VME Interface to SY527 HV Mainframe (pdf)]

[https://clonwiki.jlab.org/wiki/clondocs/Docs/v895_rev2.pdf CAEN V895 VME Discriminator (pdf)]

[https://clonwiki.jlab.org/wiki/clondocs/Docs/TS140_Manual.pdf TS140 Cyclades Terminal Server Manual (pdf)]

[https://clonwiki.jlab.org/wiki/clondocs/Docs/VMIC_VMIVME_6016_Manual.pdf VMIC VMIVME6016 Manual (pdf)]

[https://clonwiki.jlab.org/wiki/clondocs/Docs/VIPC616_C2_UM_6.pdf VIPC VME 616 Manual (pdf)]

[https://clonwiki.jlab.org/wiki/clondocs/Docs/VMIC_VME_3122A_Manual.pdf VMIC VME3122A Manual (pdf)]

[https://clonwiki.jlab.org/wiki/clondocs/Docs/VMIC_VMIVME_2232_Manual.pdf VMIC VMIVME2232 Manual (pdf)]

[https://clonwiki.jlab.org/wiki/clondocs/Docs/VMIVME_1129_Manual.pdf VMIC VMIVME1129 Manual (pdf)]

[https://clonwiki.jlab.org/wiki/clondocs/Docs/VMIVME_2120_Manual.pdf VMIVME2120 Manual (pdf)]

[https://clonwiki.jlab.org/wiki/clondocs/Docs/DVCSChillerControlManual.pdf DVCS Chiller Control Manual (pdf)]

Electronics Documentation

2008-12-01T20:27:43Z

98.166.91.3:

[https://clonwiki.jlab.org/wiki/clondocs/Docs/2917.pdf 2917 VME-CAMAC Interface (pdf)]

[https://clonwiki.jlab.org/wiki/clondocs/Docs/JLAB_NIM_LVL1FWDCarriage.pdf JLAB NIM ADC Gate Electronics (pdf)]

[https://clonwiki.jlab.org/wiki/clondocs/Docs/JLAB_VME_FIFO_board.pdf JLAB VME FIFO Board (pdf)]

[https://clonwiki.jlab.org/wiki/clondocs/Docs/JLAB_VME_Latch_driver.pdf JLAB VME Latch Driver Board (pdf)]

[https://clonwiki.jlab.org/wiki/clondocs/Docs/JLAB_VME_MLU_board.pdf JLAB VME MLU Board (pdf)]

[https://clonwiki.jlab.org/wiki/clondocs/Docs/JLAB_VME_OR_board.pdf JLAB VME OR Board (pdf)]

[https://clonwiki.jlab.org/wiki/clondocs/Docs/JLAB_VME_ts2_board.pdf JLAB VME TS2 Board (pdf)]

[https://clonwiki.jlab.org/wiki/clondocs/Docs/JLAB_VME_f1TDC_User_Manual_V1.1.pdf JLAB VME F1TDC Board User Manual (pdf)]

[https://clonwiki.jlab.org/wiki/clondocs/Docs/JLAB_VME_DiscrManual2002.pdf JLAB VME Discriminator (2002) (pdf)]

[https://clonwiki.jlab.org/wiki/clondocs/Docs/caen_SY527.pdf CAEN SY527 HV Mainframe (pdf)]

[https://clonwiki.jlab.org/wiki/clondocs/Docs/v288_rev0.pdf CAEN V288 VME Interface to SY527 HV Mainframe (pdf)]

[https://clonwiki.jlab.org/wiki/clondocs/Docs/v895_rev2.pdf CAEN V895 VME Discriminator (pdf)]

[https://clonwiki.jlab.org/wiki/clondocs/Docs/TS140_Manual.pdf TS140 Cyclades Terminal Server Manual (pdf)]

[https://clonwiki.jlab.org/wiki/clondocs/Docs/VMIC_VMIVME_6016_Manual.pdf VMIC VMIVME6016 Manual (pdf)]

[https://clonwiki.jlab.org/wiki/clondocs/Docs/DVCSChillerControlManual.pdf DVCS Chiller Control Manual (pdf)]

Wiring

2008-12-01T20:23:54Z

98.166.91.3:

'''Connectors'''

RJ45 Jack and Plug [http://clonweb/wiki/clondocs/Docs/rj45pinout.gif Pinout].

Cable connector's [http://yost.com/computers/RJ45-serial/rj45-plug.gif picture].

'''Ethernet Cabling'''

The TIA/EIA-568-A specifies two wiring standards for a 8-position modular connector such as RJ45. The two wiring standards, T568A and T568B vary only in the arrangement of the colored pairs. We are using T568B.

Straight-Through Cable Pinout (T568B):

RJ45 Pin # Wire Color 10Base-T Signal 1000Base-T Signal
(T568B) 100Base-TX Signal
1 White/Orange Transmit+ BI_DA+
2 Orange Transmit- BI_DA-
3 White/Green Receive+ BI_DB+
4 Blue Unused BI_DC+
5 White/Blue Unused BI_DC-
6 Green Receive- BI_DB-
7 White/Brown Unused BI_DD+
8 Brown Unused BI_DD-

Cross Over Cable Pinout (T568B):

RJ45 Pin # Wire Color RJ45 Pin # Wire Color
(END 1) (END 2)
1 White/Orange 1 White/Green
2 Orange 2 Green
3 White/Green 3 White/Orange
4 Blue 4 White/Brown
5 White/Blue 5 Brown
6 Green 6 Orange
7 White/Brown 7 Blue
8 Brown 8 White/Blue

NOTE: The cross over cable layout is suitable for 1000Base-T operation, all 4 pairs are crossed.

The following diagram shows the Normal use of Crossed and Straight cables:

straight--HUB,SWITCH--crossed--HUB,SWITCH--straight--PC

PC--crossed--PC

NOTE': To avoid the need for Crossed cables many vendors provide UPLINK ports on Hubs or Switches - these are specially designed to allow the use of a STRAIGHT cable when connecting back-to-back Hubs or Switches. Read the manufacturers documentation carefully.

'''RS-232 Cabling'''

From web, need check:

RS-232 Name/Function DB-25 DB-9 RJ-45 RJ-45
Signal (Input/Output) (Standard) (Standard) (Cyclades) (Netra/Cisco)
Chassis Safety Ground 1 Shell Shell Shell
Gnd Signal Ground 7 5 4 4(and 5?)
TxD Transmit Data (O) 2 3 3 3
RxD Receive Data (I) 3 2 6 6
DTR Data Terminal Ready (O) 20 4 2 2
DSR Data Set Ready (I) 6 6 8 7
DCD Data Carrier Detect (I) 8 1 7 -
RTS Request To Send (O) 4 7 1 1
CTS Clear To Send (I) 5 8 5 8

continue:

RS-232 Name/Function RJ-45 mvme6100 RJ12(6pin)
Signal (Input/Output) (EtherLite32) etc (VME6016)
Chassis Safety Ground
Gnd Signal Ground 6 3,6 2
TxD Transmit Data (O) 5 4 4
RxD Receive Data (I) 4 5 3
DTR Data Terminal Ready (O) 7 8 -
DSR Data Set Ready (I) 2 - -
DCD Data Carrier Detect (I) 3 1 5
RTS Request To Send (O) 1 2 6
CTS Clear To Send (I) 8 7 1

From vvsap (RxD and TxD are wired, cross or straight; not sure if GND is wired properly; not sure accually which one is EtherLite32 and which one is ROC, and numbering order, seems does not matter ...):

mvme6100 ---------> EtherLite32 --------> RESET
1 Orange Brown Brown
2 White/Orange Blue White/Green
3 Blue White/Brown White/Brown
4 White/Blue White/Blue Green <--- in use (RxD/TxD)
5 Green Green White/Blue <--- in use (RxD/TxD)
6 White/Green White/Green Blue <--- ?? in use (GND)
7 Brown Orange Orange
8 White/Brown White/Orange White/Orange

Sergey (check !):

EtherLite32 -----------> CISCO
8 Orange White/Brown
7 White/Orange White/Orange
6 Blue White/Blue
5 White/Blue Brown
4 Green Blue
3 White/Green Green
2 Brown White/Green
1 White/Brown Orange

October 15, 2008 online meeting minutes

2008-10-17T02:22:19Z

98.166.91.3:

present: Sergey Boyarinov, Valery Kubarovsky, Ben Raydo, Chris Cuevas, Puneet Khetarpal, Sergey Pozdnyakov, Pawel Nadel-Turonsky

* DVCS-CLAS trigger

third rack was installed to make cabeling easy; all racks connected to the clean power, one more power strip was ordered
to use second 20A circuit

cabling between splitters and discriminators has been started in according to the Ben's map

forward carreage is in position and DVCS-CLASTRIG cable was can to the nominal length, signal is in gate about 30ns from
the beginning of the gate pulse, gate cables is in production, hope to get another 20ns; we will make gate-signal coincidence curve with DVCS laser with DAQ

EPICS readout for scalers in both CLASTRIG2 and DVCSTRIG is working, scaler histograms and corresponding MEDM GUIs to be checked; normally all scalers will be reported in Hz; all quadrons counts equally

Ben developed pattern test for the CLASTRIG2, extra v1495 board was installed in clastrig2 and connected to the main v1495, test was started from Windows GUI and passed successfully including loading by scripts; DVCSTRIG test to be conducted - VERY IMPORTANT ! also will look at polarity of the optput cables

trigger downloading scripts were adjusted, downloading/uploading works fine, uploading LUT still not implemented

L2 to be tested

TO DO: DVCSTRIG test, gate cable, scope gate test, DAQ gate test, DVCS pedestal run; all-concidence-delay curve will be done with beam, need to write delays from script

'makelut' will be installed into $CODA area, README file exist; it will write logic formula from C code into LUT file as a comment

NEED TO COLLECT ALL DRAWINGS/DOCUMENTATIONS BEFORE RUN STARTS !!!