computer name: PCATLIBLUPG09
IP in CERN network changes every now and then (you can check its IP by ping PCATLIBLUPG09.cern.ch )
reachable within the CERN network by connecting via a VNC client by connecting to PCATLIBLUPG09.cern.ch
root pwd is taped to the bottom right edge of the device (needed for changing software etc.)
username: telescope (pwd: t3stb3am!) “HV-PC”:
TROUBLE SHOOTING NETWORK CONNECTIONS; The PCATLIBLUPG09.cern.ch hostname seems to only work when the PC is connected to the CERNn wifi network; try checking that if you're having issues (right click on the internet icon on the top right of the desktop, check the wireless connection is CERNn, instead of CERN or (god forbid) eduroam). If that doesn't work, try disconnecting from the CERNn network and then reconnecting. If that still doesn't work try crying or pinging the IP 192.168.1.1 from a machine connected to the local network (i.e. with an ethernet cable running to the switch in the beam area.) if that works you can connect to the pc using the IP address, either via ssh or a vnc client that lets you use an IP instead of a hostname. Contact me at ndann at cern.ch if you're stumped.
computer name: PCSPATHA
LAN IP: 192.168.1.210
connecting from DAQ-PC:
rdesktop -g 80% 192.168.1.210 & 80% is just the geometry; with higher percentage navigation becomes difficult
username: LocalAccount (pwd: testbeam)
Windows 7
used for ISEG HV remote control
HV remote control
To avoid tripping, set the Itrip limit for the used range in the ISEG Monitor to 0. Then do the ramping WHILE OBSERVING THE CURRENT. After ramping has finished, set the trip current back to it's initial value.
the Basic network check has to finish with “OK” for RCE 12 and RCE 13
the Rebooting has to finish with “OK” for RCE 12 and RCE 13
then, I observed that often “Uploading module” is not working, the error is “terminate called after throwing an instance of 'RCENet::Error' Abort (core dumped)”. However, Uploading module has to finish with “OK” for both RCE's. Solution: power cycle RCE, then execute startDAQsys.csh again (only executing startDAQsys.csh will not change anything). This you might have to do a lot of times. Sometimes one RCE is ok, then the other isn't and so on. If the HSIO is in a funny state (by not showing “L” and some number on the LED display), then also reset the HSIO. Only start cosmicGui when both RCE's are ok, i.e. when the startDAQ script executed fine.
Then just execute calibGui or cosmicGui
I | Attachment | History | Action | Size | Date | Who | Comment |
---|---|---|---|---|---|---|---|
![]() |
SBM02-Documentation.pdf | r2 r1 | manage | 145.9 K | 2015-07-29 - 16:27 | FranciscaJavielaMunozSanchez |