How josue-silva-t/control-telescope works
Main components
a. Motor-Control MCU (Moteres/MtP folder: MtP.ino, x.ino)
b. Camera-Control MCU (Camara.ino)
c. Embedded HTTP Server (app_httpd.cpp, camera_index.h, camera_pins.h, index.html) running on the Camera MCU or on a network-enabled board
d. Desktop Control Application (ControlT solution: Windows Forms – Form1.cs, Form2.cs, Program.cs)
e. End-User Interfaces
• Web UI (served by the Embedded HTTP Server via index.html)
• Desktop UI (ControlT Windows Forms)
Relationships and data flows
• The Desktop App (ControlT) communicates over USB/Serial with both MCUs to send control commands (azimuth, elevation, shutter) and receive status feedback.
• The Embedded HTTP Server interfaces directly with the Camera MCU’s GPIO (camera_pins.h) to trigger the shutter and stream any telemetry; it serves index.html to any web browser on the same network.
• End users can either run the Windows Forms desktop client or open the web UI in a browser to control the telescope.
Architectural patterns and technologies
• Embedded Firmware – Arduino-style sketches for motion control (Moteres/MtP) and camera control (Camara.ino).
• Custom HTTP daemon (app_httpd.cpp) implements a minimal web server on the Camera MCU.
• Rich Client – .NET Windows Forms (C#) for advanced local control and configuration.
• HTML/JavaScript static UI served by the MCU.