test2K2K
New pieces of information are added here, but the info below is still valid and OK!
1. How to use :
This program allows to operate
camera in interactive way. It is possible to set paramters, make image and
save to disk. The program allows to communicate with camera via
USB ( default ) or Ethernet interface ( -eth option ). In order to use camera via USB no
special options are needed, to use it via Ethernet option
-eth=IP_ADDRESS_OF_CAMERA is required ( see below for details ).
It is allso possible to use more advanced option, in order to make advanced
options available add options ( -medium ( same as -advanced ) or -all ( same as -expert ) - see below for details )
Program can be run in the following way :
test2K2K CAMERA OPTIONS
PARAMTERES DESCRIPTION :
CAMERA - specifies
which camera will be used it can be specified as number 0 or 1 ,
but also namely as k2a
or k2b or k1
NOTE : in case camera has unknown
ID or ID=0 then the following command shoud work :
test2K2K k1
OPTIONS - the
following options are available :
-safe
- safe mode only several safe commands are available this is the DEFAULT
-medium ( same as -advanced )- some more options are available ( like moving motors,
changing gain etc ... )
-all ( same as -expert ) - all options are
available ONLY
FOR EXPERTS - inluding uploading of firmware to
CYPRESS and ALTER etc ...
-eth=100.100.100.96 - ip of
ethernet camera
-local_ip - to force ip of
local machine ( it should be detected automatically, but sometimes due
to bad configuration is not
see here when it is possible
to have such problems )
-local_port - to force port of
local machine ( default is 23100 ) ,
NOTE : this option is sometimes
required to run when due to different reasons function gethostbyname
returns localhost.localdomain
and due to this IP = 127.0.0.1 for which camera does not want to
connect to.
that's why for many cases it is required to add for example :
-local_ip=192.168.0.103
-set_eth=100.100.100.96 - this
option allows to connect to ethernet camera by USB interface , it will
use USB driver
instead of ethernet connection
-cool_until_possible=300 - in case temeparture is set to very low which cannot be reached
( for example in cam_test.sh ) in order to permanently cool camera, it allows to stop waiting for this temperature
when no temperature changes are detected after specified amount of time ( 300 sec in the example here )
-outdir=shutter10temp10 - output
directory where fits will be saved
-batch - option for
running program in batch mode and executing given command, by default
command 1 ( status ) is used
otherwise pass command with option -batch :
-batch=2
to turn on coolingof the camera
It is possible to run list of commands also with paramters , for
example :
test2K2K k2a -eth=193.0.84.112 -init_params -batch=8,-10 -batch=7,-10
-batch=42 -batch=34,2
This command will set shutter time to -10 sec, set temperature -10 ,
wait for this temperature and make 2 images
CONFIGURATION FILES :
In order to get confgiuration files use script getcfgfiles! with options :
- double_side - for double side readout camera
- single_side - for single side readout camera
After program is lunched , for example by command :
test2K2K k2a
There is set of available options which can be executed and in order to
exit choose 0.
More info on development on piwiki
2. FITS file naming
After checking the code of test2K2K/main.cpp and Device2K2K.cpp
and DeviceBase.cpp , I see that naming of fits file ( prefix ) should
work in the following way :
- jak sie nie poda zadnej nazwy kamery tylko uzywa sie po
numerku pliki powinny sie zaczynac od camID , gdzie ID to id kamery
czyli np :
cam8_070507_00001.fit
- jak sie wola test2K2K jako :
test2K2K k16
to pliki powinny sie nazywac :
k16_070507_00001.fit
- ostatecznie mozna tez wymusic ten prefix , opcja : -camname=k17 i
wtedy to nadpisuje wszystkie poprzednie warunki , pliki nazywaja sie :
k17_070507_00001.fit
3. Changes :
- 20070621 - 46 command for sleep N seconds , to keep camera alive
for whole day without watchdog reset