RTS2 Wiki

User Tools

Site Tools

Trace:
howto:bootes:bootes_1

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
Last revisionBoth sides next revision
howto:bootes:bootes_1 [2008/12/10 23:25] – pkubanekhowto:bootes:bootes_1 [2009/01/10 17:59] – Added note on webcam IP pkubanek
Line 16: Line 16:
 Our installations include five imaging systems in total: BOOTES-1A, BOOTES-1B, BOOTES-1ASM, External webcam and internal webcam watching BOOTES-1B. We have two domes, first, older and recently reconstructed covers B-1A and B-1ASM. The newer and larger dome hosts BOOTES-1B and it's webcam.  Our installations include five imaging systems in total: BOOTES-1A, BOOTES-1B, BOOTES-1ASM, External webcam and internal webcam watching BOOTES-1B. We have two domes, first, older and recently reconstructed covers B-1A and B-1ASM. The newer and larger dome hosts BOOTES-1B and it's webcam. 
  
-===== Bootes-1B =====+====== Bootes-1B ======
  
 The 30cm Meade has a declared focal length of 3072mm, i (mates) do not remember measuring it so I do not have the real value. Current configuration with the Meade 1:6.3 focal reducer gives the focal length of 1684mm with a 16um pixel scale of 1.96"/pixel (effective focal ratio of 1:5.5, field of view 16.7arcmin). The 30cm Meade has a declared focal length of 3072mm, i (mates) do not remember measuring it so I do not have the real value. Current configuration with the Meade 1:6.3 focal reducer gives the focal length of 1684mm with a 16um pixel scale of 1.96"/pixel (effective focal ratio of 1:5.5, field of view 16.7arcmin).
Line 27: Line 27:
 **NOTE:** The switch is commom with the Bootes-1A Alta CCD, which will be also power cycled if you do this. Therefore, you should also consider stopping the alta driver before and restarting it after the former action. **NOTE:** The switch is commom with the Bootes-1A Alta CCD, which will be also power cycled if you do this. Therefore, you should also consider stopping the alta driver before and restarting it after the former action.
  
-===== Bootes-1A =====+====== Bootes-1A ======
  
 The camera driver has a bug, which causes it to hang when exposure is ended prematurely. The following sequence should bring it back. The camera driver has a bug, which causes it to hang when exposure is ended prematurely. The following sequence should bring it back.
Line 42: Line 42:
  
 **NOTE:** as this switch is common with Bootes-1B mount, you should check the mount as well. If observing, consider paring the mount in advance to avoid possible problems while the mount is being reset. **NOTE:** as this switch is common with Bootes-1B mount, you should check the mount as well. If observing, consider paring the mount in advance to avoid possible problems while the mount is being reset.
-===== Weather & dome control =====+ 
 +====== Weather & dome control ======
  
 These devices are generally common to all involved systems, they are all connected to a single PC (//iam1a//), which replaced the former //DCM//, via serial ports (RS232).  These devices are generally common to all involved systems, they are all connected to a single PC (//iam1a//), which replaced the former //DCM//, via serial ports (RS232). 
  
-** // FORDOSTROJ // **+===== Fordostroj =====
  
 The PC-to-dome interfaces are two (for each dome separate) serial boards designed for us by Martin Nekola in Ondrejov. They are both connected to //iam1a//. The board controlling (older, reconstructed, western) Bootes1A dome, is connected to ''/dev/ttyS0'', while the Bootes1B board is on ''/dev/ttyS4''. There is a set of scripts allowing simple actions be taken on the boards in ''iam1a:/home/standa/fordostroj/'' (**Read them before trying. You are indeed opening & closing the dome, it may rain!**). Under normal circumstances, //RTS2// has two separate custom drivers ''rts2-dome-bootes1a'' an ''rts2-dome-bootes1b'' to be watching on them. They run on //iam1a// computer. The PC-to-dome interfaces are two (for each dome separate) serial boards designed for us by Martin Nekola in Ondrejov. They are both connected to //iam1a//. The board controlling (older, reconstructed, western) Bootes1A dome, is connected to ''/dev/ttyS0'', while the Bootes1B board is on ''/dev/ttyS4''. There is a set of scripts allowing simple actions be taken on the boards in ''iam1a:/home/standa/fordostroj/'' (**Read them before trying. You are indeed opening & closing the dome, it may rain!**). Under normal circumstances, //RTS2// has two separate custom drivers ''rts2-dome-bootes1a'' an ''rts2-dome-bootes1b'' to be watching on them. They run on //iam1a// computer.
  
-** RAIN SENSORS **+===== Rain sensors =====
  
 There are two Eigenbrodt IRSS 88 precipitation detectors, connected separately to the dome control inlets (//fordostoj//). The northern detector is connected only to Bootes-1B inlet (no. 5, ''0x10''), while the southern one is connected to both units in parallel (at B-1A it is inlet no.1, i.e. ''0x01'', at B-1B it is no.6, i.e. ''0x20''). [one of them was removed faulty on Nov/9/2008 and brought to Gr for repair] There are two Eigenbrodt IRSS 88 precipitation detectors, connected separately to the dome control inlets (//fordostoj//). The northern detector is connected only to Bootes-1B inlet (no. 5, ''0x10''), while the southern one is connected to both units in parallel (at B-1A it is inlet no.1, i.e. ''0x01'', at B-1B it is no.6, i.e. ''0x20''). [one of them was removed faulty on Nov/9/2008 and brought to Gr for repair]
Line 58: Line 59:
 The northern (nearer to the domes) sensor seems to have a malfunctioning DEU (drop evaluation unit), although the drops (well, screwdriver strikes) get detected well at the frame, the DEU does not react. The unit should be revised soon.  The northern (nearer to the domes) sensor seems to have a malfunctioning DEU (drop evaluation unit), although the drops (well, screwdriver strikes) get detected well at the frame, the DEU does not react. The unit should be revised soon. 
  
-** CLOUDMETER **+===== Cloudmeter =====
  
 Provides sky transparency measures through by providing the radiative temperature of the sky. It is connected to ''iam1a:/dev/ttyS6''. It is integrated to //RTS2// and trigger bad weather if average cloud value drops bellow predefined value. Provides sky transparency measures through by providing the radiative temperature of the sky. It is connected to ''iam1a:/dev/ttyS6''. It is integrated to //RTS2// and trigger bad weather if average cloud value drops bellow predefined value.
  
-** DAVIS WEATHER STATION **+===== Davis weather station =====
  
 Wireless weather station capable of providing precipitation sums in mm/m2, wind speed, temperature and humidity.  Wireless weather station capable of providing precipitation sums in mm/m2, wind speed, temperature and humidity. 
 Connected to ''iam1a:/dev/ttyS1''. Wind speed sensor is not working, so a modified [[http://meteo.othello.ch|Othello]] package must be installed. Connected to ''iam1a:/dev/ttyS1''. Wind speed sensor is not working, so a modified [[http://meteo.othello.ch|Othello]] package must be installed.
  
-** WEBCAM **+===== Webcam =====
  
-The webcam may be considered another weather measuring instrument. It is not being used that way, but running astrometry upon the received image does not seem that problematic. In any case, the archive of images taken every second is in ''iam1a:/home/axis/''. +The webcam may be considered another weather measuring instrument. It is not being used that way, but running astrometry upon the received image does not seem that problematic. In any case, the archive of images taken every second is in ''iam1a:/home/axis/''.  The webcams are pingable from iam1a as //wc1// and //wc2// (see entry in ///etc/hosts//). You can access webcam over http port, so either run HTTP browser (mozilla) on iam1a and point to wc1, or using -L option to ssh forward to your host (//ssh -L 8080:wc2:80 iam1a//). 
  
-** PiXY **+===== Pixy =====
  
 The discharge detector PIXY is supposed to provide additional security against lightnings, it's output is being logged, but currently is not actively used. It is connected to ''iam1a:/dev/ttyS5''. Currently its performance is evaluated. The discharge detector PIXY is supposed to provide additional security against lightnings, it's output is being logged, but currently is not actively used. It is connected to ''iam1a:/dev/ttyS5''. Currently its performance is evaluated.
  
-===== Data storage =====+====== Data storage ======
  
 We have several storage facilities at BOOTES-1, here they are described with their primary purpose, by size. In **bold** are fault tolerant devices. We have several storage facilities at BOOTES-1, here they are described with their primary purpose, by size. In **bold** are fault tolerant devices.
howto/bootes/bootes_1.txt · Last modified: 2009/01/10 00:00 (external edit)