David's Astronomy Pages
Notes - Session 607 (2017-12-13)

   
Bullet Session Aims & Highlights
   
Bullet Operational Issues
  - Critical Issues (1),  Major Issues (0),  Minor Issues (4),  Small Defects (0),  Continuous Improvement (0)
Bullet Communication Ports
Bullet Images from 2017-12-13 >>
   

Session Aims & Highlights (S607)

Main Aims

  1. CCDApp2. Conduct a live test of VS2017 version of CCDapp2 Observatory Control Program
  2. Targets. Acquire images from a selection of deep sky objects.
  3. Dual Camera Ops. Continue testing of dual camera operations using both PHD2 and SharpCap 3.0, including updated routines for autoguiding communications and a new routine for taking & plate solving a SharpCap image.

Equipment & Software

Highlights

Back to Top


Operational Issues (2017-12-13, S607)

[ Prev | Next ]

Critical Issues

Major Issues

Minor Issues

Small Defects

Continuous Improvement

[ Prev | Next ]

Fig 1

Back to Top


Communication Ports

A start-up issue when trying to start by SharpCap Server Script with Aurora Cloud Sensor Software already open showed that I need to have tighter control over the Ports used for software/computer communications.

Port    Software Use
4000   Aurora Cloud Sensor Broadcast of Aurora Cloud data to Local Network
4001   Weather Station Repeater Broadcast of Weather Station data to Local Network
4002   SharpCap Server  Control of SharpCap
4400   PHD2 Control of  PHD2 (Guiding)

Notes: Port 4000 used by Aurora Cloud Sensor Software is the default port number when first installed. It can be changed by editing the 'NetworkPort' setting in ".\Program Files\Aurora Eurotech\CloudSensor.cfg"

Ports 4001, 4002 are hard-coded into my own software.   Port used by SharpCap Server Script was changed to 4002 after discovering the conflict with Aurora Cloud Sensor Software.

Port 4400 is fixed by PHD2 software and can't be changed.

Back to Top