Hi Robin,
I’ve been using this “home automation for the lab” strategy for a few years now. What I’ve found is there’s no silver bullet. Lab equipment manufacturers often make up their own protocols or half-implement something before going their own way, which means that you usually need to get your hands dirty with custom communication interfaces.
Our solution is to 1. write a python driver for each brand of (serial) equipment, 2. use raspberry pis to expose async HTTP APIs, and 3. tie ipywidgets to HTTP requests. Accomplishing 1 required some up-front work, but 2+3 are easy and I’ve found we don’t bring in many new brands of equipment.
You can see sample drivers here, a blog post here, and I’d be happy to talk further. We’re constantly talking through how to make this process simpler, and I could share much more detail on how we do it today.
Hope this helps,
Pat
--
You received this message because you are subscribed to the Google Groups "Project Jupyter" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jupyter+u...@googlegroups.com.
To post to this group, send email to jup...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jupyter/c73db86b-ddc7-40a2-a78c-71aba2608d93%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.