Put MQTT in there and you dont even have know/care where devices are or how may devices are doing the same thing all at the same time - being cheeky sorry

Actually I'm in the process of writing MQTT driver for INDI
It will take some time to complete as I'm extremely busy with my profession recently, but anyway worth noting.

Radek -

great minds think alike LOL

At the moment mine isn't for Indi just to use Gphoto2 connected camera from anywhere bu the principle is the same.

IBM wrote a good paper on using MQTT for "serious" Astronomy to share/control data/devices over the world. Biggest plus as I see it is not having to know where the device are. IBM had developed an Ascom wrapper for MQTT but now with Alpaca/Indi maybe it will provide best of all flavours.

Will keep an eye out for your progress !!!!

Good luck

Jasem, maybe you should look at INDIGO XML vs. JSON HTTP/WebSocket mapping before you will try to reinvent the wheel. Among INDIGO web applications it is used also by INDIGO ASCOM drivers for years. Peter

github.com/indigo-astronomy/indigo/blob/master/PROTOCOLS.md

Well tried it out between Up Core Windows 10 and a desktop.

I have to say the terminology doesn't make a lot of sense - remote client , server is fine nothing knew but IMHO the set up is confusing and of course still depends on the user knowing IP addresses etc - plus good old Win10 Firewall sticking its nose in.

Anyhow I got it working but of course Ascom doesn't have a DSLR driver but running APT on the UP Core which was on the mount (my good old SWAZ GoTo) together with Synscan App Pro (no handset) and CDC on a desktop it ran for 2hrs no problem. Slewing here and there no problem. Plus APT PlateSolving worked too.

CDC did initially moan something about "Object Instance error" and loops horribly if the mount get disconnected (does that anyway) - but it worked too.

Response time were fine but I wasn't downloading CCD images between the UP Core and the desktop.

So initial impressions - Impressed it worked so well - wish it had a Ascom DSLR driver - set up not for end users. So just need an Indi interface (especially for DSLR) Ekos and your cooking. Obviously its early days and it was a quick test

As the old Canned Heat record said " Come Come lets work together" LOL

Peter, is there any specific reason you're so sarcastic recently? or is it just bad weather?

Stash,

There is a Ascom dslr driver but I don't know the status: github.com/vtorkalo/ASCOM.DSLR

The error "Object Instance error" is a Ascom exception reported by CdC, no idea why.

I forget to protect CdC again remote disconnection (this is done in CCDciel), I fix it now.
This is something new for the Ascom client because this never arise with the COM driver. You have a checkbox in the server configuration to disable the connect/disconnect capability to prevent to break existing application.

Hi Patrick,

I had tried that DSLR Ascom a while back - didn't work for me with APT

The Disconnection error also occurs when using the Synscan App (windows) with Remote Ascom. Its onl a problem in that it nearly does a deadly embrace and you cannot do anything else.

Love CDC and have been using it for years

Hello Radek,
reading your comment on MQTT driver for INDI, I had to register for this Forum!
I am looking for exactly such a driver!
In times of IoT and home automation, it would totally make sense to have some kind of gateway between INDI and MQTT.
My use case would be (for a starter):
A weather station sends its data via MQTT -> (configurable) INDI Driver makes necessary data available to observatory.

This way, no need to write a specific driver for each and every weather station, just have it send its data via MQTT and the observatory could subscribe to the relevant topics.

Unfortunately, I don't have enough coding experience to write something like this - but definitely willing to test such a driver.

Greetings,
Herwig
astrohd.de

Hi stash,

do you have by chance any more info on this ascom wrapper for MQTT, perhaps even a link?

Thank you,

Herwig
astrohd.de

Hi Herwig, welcome to INDI forum!
There are various use cases for INDI-MQTT. What I assumed in my project so far is that INDI publishes status of devices over MQTT. What you're describing is INDI subscribes to MQTT messages from other devices.
As the matter of fact both are feasible but making it work both ways requires lots of work. If community thinks it is worthwhile, a major project should be defined with several contributors. As for now we can make a small step for INDI but giant leap for mankind. Some day we can get there. In the meantime you can use existing weather drivers, including wunderground - just publish your weather data to wunderground and pull them back with the driver.

All the best!

Hi ,

This is not the orig paper which i cant find. I never found the wrapper just references to it

link is here www.google.co.uk/url?sa=t&rct=j&q=&esrc=...Ap_BkIHh-O3IEgw9Ortk

Google IBM cognative telescope network and ibm telescope commander might throw some info