I'm interested in this idea, myself. There isn't really anything especially magical coming up in the drives to make it impossible to figure this out if it were made to be able to talk to the right elements. So, here's a sketch off the top of my head of what it seems we'd want it to do:
(1) RA positioning drive
(2) RA Clock drive (there are architectures possible where 1 and 2 are separate)
(3) DEC positioning drive
(4) Telescope focus motor
(5) Dew heater
(6) Other motor 1 (e.g. if a guide scope were on a powered stage or camera rotator)
(7) Other motor 2 (e.g. if a guide scope were on a powered stage or camera rotator)
(8) Other motor 3 (Second focusing element)
(9) Dew heater 2
(10) Data output 1 (for pad or computer)
(11) Dome data output GEM (adjusted for as-built mount geometry, and dome data)
(12) Dome data output FORK (adjusted for as-built mount geometry and dome data)
(13) Roll off Roof coordination (e.g. ROR park function).
(1) Bluetooth control- all data.
(2) WiFi hosting and control for all data.
(3) RA motor encoder.
(4) RA position encoder (several possible arrangements)
(5) DEC motor encoder.
(6) DEC position encoder (several possible arrangements)
(7) Focuser motor encoder
(8) Focuser absolute position encoder
(9) Dome position encoder
(10) Dome shutter open/close indicator
(11) System status serial commands
(12) System start control
(13) System normal shut down control
(14) Event-driven system safe/ emergency shut down control
There is going to be a much longer list to get everything. Something I see as an elephant in the room here is "What hardware does this run on?" The need to get the right control system together appears to have a great need for what a mount/ observatory system hub has to be. I personally see great benefit in this being one device. Ideally, it has these parameters:
(A) rock-solid stability- they just don't crash.
(B) remote-friendly capability- it resets itself to the right state if the power goes out.
© Modern data compatibility- I really want to be able to attack the rats' nest of cables.
(D) Mobility capability- it should be able to be really easy to use an built pointing models on the fly- all the good stuff.
(E) Low power requirement- even to the point of being active on a semi-old-school mount with just a clock drive and position encoders.
This doesn't sound at all like a Windows based system to me. I would really like to think something reasonable exists off the shelf which matches this description, though I don't know what that is off the top of my head. I don't know if any of the tablets we have seen up to now could become that device. That's really one for more knowledgeable folks.
Anyway, here's to the start of a thread. My understanding is ASCOM kind of started this way, so it may be possible for a 21st century universal mount and observatory controller to come out of this.
We need an open-source telescope. Probably most of the bits already exist.