diff --git a/state/NOTES.md b/state/NOTES.md index 5d83f64..37fc86d 100644 --- a/state/NOTES.md +++ b/state/NOTES.md @@ -10,3 +10,28 @@ - Sensors are 16-bit ADC unless noted (T20's ASI2400C is 14-bit). - Free scopes (30 min/day): T68 (Utah), T33 (Siding Spring). - Minimum elevation limits come from the support article, not the sheet. + +## Automation recon (2026-07-18, all verified live) + +Credentials live OUTSIDE this repo (local claudetemp, never commit them). + +- go.itelescope.net is ASP.NET WebForms. Login: GET /login.aspx, POST + UsernameTextBox/PasswordTextBox plus __VIEWSTATE, __VIEWSTATEGENERATOR, + __EVENTVALIDATION, LoginButton=Login; session cookie then works everywhere. +- JSON service at /DataService.svc (session-cookie auth): GetAccountStatus + (balance, plan, renewal), GetMyAvailablePlans (per-plan, per-scope + AccessDiscount), ApplyPromoCode (POST). More methods likely; enumerate from + inline $.ajax calls on each page (Scripts/Common.js has none). +- Home page /default.aspx carries live network status text (per-scope + offline/online reasons) plus points balance: cheap to poll. +- Reservation/Overview.aspx links every telescope's own control server: + https://tNN.itelescope.online/ or http://tNN.itelescope.net:80NN/. These are + ACP web servers behind HTTP auth accepting the same iTelescope credentials + (verified read-only on T33: index.asp is a TiddlyWiki info page, min elevation + 20 degrees, 900 s max exposure). Session control and plan submission happen + here; ACP endpoint mapping is the next step. +- Reservation/Planner.aspx now redirects to https://lookup.itelescope.online + (new planning tool, not yet explored). +- Weather per site: Weather/Weather.aspx?site=UDRO|SSO|DSC|SRO|AC|EYE. +- Account: Plan-40 (GBP 32.00 per 28 days), renewal 12 Aug 2026, subscribed + since Apr 2019, balance 2,638 points at recon time. diff --git a/state/TODO.md b/state/TODO.md index e699da8..ffc7f9c 100644 --- a/state/TODO.md +++ b/state/TODO.md @@ -19,6 +19,15 @@ ## Pending +- Automation: map the ACP web endpoints on a per-scope server (start with free + T33) for plan submission and status; explore lookup.itelescope.online (the new + planner); enumerate more /DataService.svc methods. Recon notes in NOTES.md. +- Campaign impact (status seen 2026-07-18): T71 and T73 are offline + (development/mount testing), as are T2, T17, T18, T20, T25, T30, T72, T74, + T75, T80. T8, T33, T32, T59 at Siding Spring are operational. Re-plan the + July-August campaign around T33 free time and Siding Spring scopes until the + Chile rebuild finishes; re-check status before any booking. + - Fill in T74 when iTelescope publishes its specs. - Reconcile the retired scopes (T9, T19, T31, T69): the support article still lists them but the maintained sheet does not; confirm status and note it.