Editing Robotic telescope (section)

==Amateur robotic telescopes==
In 2004, most robotic telescopes are in the hands of [[amateur astronomy|amateur astronomers]]. A prerequisite for the explosion of amateur robotic telescopes was the availability of relatively inexpensive CCD cameras, which appeared on the commercial market in the early 1990s. These cameras not only allowed amateur astronomers to make pleasing images of the night sky, but also encouraged more sophisticated amateurs to pursue research projects in cooperation with professional astronomers. The main motive behind the development of amateur robotic telescopes has been the tedium of making research-oriented astronomical observations, such as taking endlessly repetitive images of a variable star.

In 1998, [[Bob Denny]] conceived of a software interface standard for astronomical equipment, based on [[Microsoft]]'s [[Component Object Model]], which he called the [[Astronomy Common Object Model]] (ASCOM). He also wrote and published the first examples of this standard, in the form of commercial telescope control and image analysis programs, and several freeware components. He also convinced Doug George to incorporate ASCOM capability into a commercial camera control software program. Through this technology, a master control system that integrated these applications could easily be written in [[perl]], [[VBScript]], or [[JavaScript]]. A sample script of that nature was provided by Denny.

Following coverage of ASCOM in ''[[Sky & Telescope]]'' magazine several months later, ASCOM [[Systems architect|architect]]s such as Bob Denny, Doug George, [[Tim Long]], and others later influenced ASCOM into becoming a set of codified interface standards for [[freeware]] [[device driver]]s for telescopes, CCD cameras, telescope focusers, and astronomical observatory domes. As a result, amateur robotic telescopes have become increasingly more sophisticated and reliable, while software costs have plunged. ASCOM has also been adopted for some professional robotic telescopes.

Also in 1998, the [[Tenagra Observatories]] site near [[Cottage Grove, Oregon]] was constructed by Michael Schwartz with a robotic {{convert|14|inch|mm|adj=on}} [[Celestron]] Schmidt-Cassegrain telescope {{circa}} 1998.<ref>{{citation|last=Polakis|first=Tom|authorlink=Tom Polakis|title=Robotic Observing: If Robotic-Controlled Telescopes Are the Future of Astronomical Observing, Then Tenagra Observatories Are Leading This Technological Revolution|date=May 2004|journal=[[Astronomy (magazine)|Astronomy]]|volume=32|issue=5<!-- via The Wikipedia Library -->}}</ref>

Meanwhile, ASCOM users designed ever more capable master control systems. Papers presented at the [[Minor Planet Amateur-Professional Workshop]]s (MPAPW) in 1999, 2000, and 2001 and the [[International Amateur-Professional Photoelectric Photometry]] Conferences of 1998, 1999, 2000, 2001, 2002, and 2003 documented increasingly sophisticated master control systems. Some of the capabilities of these systems included automatic selection of observing targets, the ability to interrupt observing or rearrange observing schedules for targets of opportunity, automatic selection of guide stars, and sophisticated error detection and correction algorithms.

Remote telescope system development started in 1999, with first test runs on real telescope hardware in early 2000. RTS2 was primary intended for [[Gamma ray burst]] follow-up observations, so ability to interrupt observation was core part of its design. During development, it became an integrated observatory management suite. Other additions included use of the [[Postgresql]] database for storing targets and observation logs, ability to perform image processing including astrometry and performance of the real-time telescope corrections and a web-based user interface. RTS2 was from the beginning designed as a completely [[open source]] system, without any proprietary components. In order to support growing list of mounts, sensors, CCDs and roof systems, it uses own, text based communication protocol. The RTS2 system is described in papers appearing in 2004 and 2006.<ref>{{Cite web|url=http://rts2.org/index.html|title = RTS2: Open source standard and package for autonomous observatory}}</ref>

The [[Instrument Neutral Distributed Interface]] (INDI) was started in 2003. In comparison to the [[Microsoft Windows]] centric ASCOM standard, INDI is a platform independent protocol developed by Elwood C. Downey of ClearSky Institute to support control, automation, data acquisition, and exchange among hardware devices and software frontends.

=== Smart telescopes ===

A newer introduction to the  consumer market are smart telescopes. They are self contained robotic astronomical imaging devices that combine a small (50mm to 114mm in diameter) telescope and mount with pre-packaged software designed for [[astrophotography]] of [[deep-sky object]]s.<ref>[https://www.techradar.com/features/why-smart-telescopes-are-the-future-of-astrophotography Jamie Carter, Why smart telescopes are the future of astrophotography, techradar.com - September 24, 2022]</ref><ref>[https://ui.adsabs.harvard.edu/abs/2021ASPC..531..411S/abstract Sweitzer, J.,  Star Parties in Deep Space: Smart Telescopes for Education, ASP2020: Embracing the Future: Astronomy Teaching and Public Engagement ASP Conference Series, Vol. 531, proceedings of a virtual conference held 3-December 2020. Edited by Greg Schultz, Jonathan Barnes, Andrew Fraknoi, and Linda Shore. San Francisco: Astronomical Society of the Pacific, 2021, p.411]</ref><ref>[https://www.space.com/vaonis-stellina-observation-station-smart-telescope-review Robin Scagell, Vaonis Stellina Observation Station Smart telescope review, space.com, September 14, 2022]</ref> They use GPS data and automatic star pattern recognition ([[plate solving]]) to find out where they are pointed. They have no optical system that allows the user to directly view astronomical objects and instead send an image captured over time via  [[image stacking]] to a built in digital display (usually shaped like a conventional [[eyepiece]]), or to a [[smartphone]] or [[tablet computer|tablet]]. They come with a database of pre-programmed objects, per-determined imaging routines, and [[Mobile app]] software that allows the end user to begin astrophotography as soon as the telescope is set up. They can be operated remotely and are able to collect a series of images unattended. They can automate various techniques of astrophotography, including "[[lucky imaging]]"  and "[[speckle imaging]]".<ref>{{Cite web |title=Smart Telescope Reviews - Find perfect smart telescope |url=https://smarttelescopereviews.com/ |access-date=2023-12-10 |website=Smart Telescope Reviews |language=en-US}}</ref> The design of the imaging system, combined with relatively small optics, are not optimal for imaging planets or the Moon.<ref>[https://www.techradar.com/features/why-smart-telescopes-are-the-future-of-astrophotography Jamie Carter, Why smart telescopes are the future of astrophotography, techradar.com - September 24, 2022]</ref> Examples include models Seestar and Dwarf, and  from the French companies [[Unistellar]] and Vaonis.<ref>{{Cite web |author1=Robin Scagell |date=2022-08-09 |title=Vaonis Stellina Observation Station Smart telescope review |url=https://www.space.com/vaonis-stellina-observation-station-smart-telescope-review |access-date=2022-09-16 |website=Space.com |language=en}}</ref><ref>{{Cite web |title=Unistellar eVscope eQuinox |url=https://www.skyatnightmagazine.com/reviews/telescopes/unistellar-evscope-equinox/ |access-date=2022-09-25 |website=BBC Sky at Night Magazine |language=en}}</ref>