Configurazioni

INDI

Non ci sono stati problemi durante l’installazione.

La connessione con la mia EQ6R avviene tramite un adattatore Seriale-USB Prolific PL-2303RA:

che Linux riconosce tranquillamente:

[ 4566.184116] usb 3-1: new full-speed USB device number 2 using uhci_hcd

[ 4566.354347] usb 3-1: New USB device found, idVendor=067b, idProduct=2303

[ 4566.354362] usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0

[ 4566.354371] usb 3-1: Product: USB-Serial Controller D

[ 4566.354379] usb 3-1: Manufacturer: Prolific Technology Inc.

[ 4566.758666] usbcore: registered new interface driver usbserial

[ 4566.758746] usbcore: registered new interface driver usbserial_generic

[ 4566.758817] usbserial: USB Serial support registered for generic

[ 4566.785496] usbcore: registered new interface driver pl2303

[ 4566.785576] usbserial: USB Serial support registered for pl2303

[ 4566.785664] pl2303 3-1:1.0: pl2303 converter detected

[ 4566.802022] usb 3-1: pl2303 converter now attached to ttyUSB0

Il driver da utilizzare è Celestron NexStar:

Cartes Du Ciel

Nessuna configurazione o problemi in particolare. Si connette senza problemi al server INDI (che deve essere stato preventivamente avviato).

GPhoto2

La Nikon D5100 viene identificata in automatico, quando collegata:

astronetbook kernel: [ 1073.316344] usb 1-3: new high-speed USB device number 4 using ehci-pci

astronetbook kernel: [ 1073.479231] usb 1-3: New USB device found, idVendor=04b0, idProduct=0429

astronetbook kernel: [ 1073.479244] usb 1-3: New USB device strings: Mfr=1, Product=2, SerialNumber=3

astronetbook kernel: [ 1073.479253] usb 1-3: Product: NIKON DSC D5100

astronetbook kernel: [ 1073.479261] usb 1-3: Manufacturer: NIKON

astronetbook kernel: [ 1073.479269] usb 1-3: SerialNumber: 000006877305

astronetbook mtp-probe: checking bus 1, device 4: "/sys/devices/pci0000:00/0000:00:1d.7/usb1/1-3"

astronetbook mtp-probe: bus: 1, device: 4 was not an MTP device

INDI va configurato per utilzzare Gphoto2, aggiungdo al server il device corretto:

Anche il client va configurato:

CCDciel

Vanno fatte alcune configurazioni importanti:

1. cartella dove salvare i file:

1. luogo:

1. formato della matrice di Bayer della fotocamera:

1. astrometria:

1. I dati di default sono quasi corretti, quelli indicati in Other options identificano l'attuale FOV del mio setup (dedotti seguendo questo tutorial).
2. I tempi di plate solving sono ottimi:

Entangle

Non serve nessuna configurazione: la mia Nikon viene identificata in autormatico.

Astrometry.net

Caricando una immagine su http://nova.astrometry.net si identificano i file di indici da scaricare:

Found tag-along columns from field: FLUX BACKGROUND Field 1: solved with index index-205.fits. Field 1: tried 102180 quads, matched 356035 codes. Spent 95.1 s user, 1.62 s system, 96.72 s total, 98.1823 s wall time.

RedShift

E’ necessario configurare la temperatura dello schermo, oltre che le coordinate geografiche di dove abito (si crea il file redshift.conf in .config/).

; Global settings for redshift

[redshift]

; Set the day and night screen temperatures

temp-day=5700

temp-night=1000

; Enable/Disable a smooth transition between day and night

; 0 will cause a direct change from day to night screen temperature.

; 1 will gradually increase or decrease the screen temperature.

transition=1

; Set the screen brightness. Default is 1.0.

;brightness=0.9

; It is also possible to use different settings for day and night

; since version 1.8.

;brightness-day=0.7

brightness-night=0.6

; Set the screen gamma (for all colors, or each color channel

; individually)

gamma=0.8

;gamma=0.8:0.7:0.8

; This can also be set individually for day and night since

; version 1.10.

;gamma-day=0.8:0.7:0.8

gamma-night=0.7

; Set the location-provider: 'geoclue', 'geoclue2', 'manual'

; type 'redshift -l list' to see possible values.

; The location provider settings are in a different section.

location-provider=manual

; Set the adjustment-method: 'randr', 'vidmode'

; type 'redshift -m list' to see all possible values.

; 'randr' is the preferred method, 'vidmode' is an older API.

; but works in some cases when 'randr' does not.

; The adjustment method settings are in a different section.

adjustment-method=randr

; Configuration of the location-provider:

; type 'redshift -l PROVIDER:help' to see the settings.

; ex: 'redshift -l manual:help'

; Keep in mind that longitudes west of Greenwich (e.g. the Americas)

; are negative numbers.

[manual]

lat=45.47

lon=8.63

; Configuration of the adjustment-method

; type 'redshift -m METHOD:help' to see the settings.

; ex: 'redshift -m randr:help'

; In this example, randr is configured to adjust screen 1.

; Note that the numbering starts from 0, so this is actually the

; second screen. If this option is not specified, Redshift will try

; to adjust _all_ screens.

[randr]

;-screen=1