Skip to content

Daemon Utility non-communication #116

@Kupaianaha

Description

@Kupaianaha

Hey Team, I wanted some insight on a use case I was thinking about pertaining to the daemons we are making. When it comes to debugging or engineering, it would be good to be able to utilize the daemons without "activating" the communication protocol. This would take out the need to use or be familiar with the lowest level of hardware control while also automatically importing the communication requirements for each device. In a python instance, an example of this would be:

from hispec.util.fw102c import FilterWheelControler
fw = Filter Wheel Controller()
fw.connect(host,port) #You need to remember these for the specific device(6 different filter wheels in HISPEC so you must remember or look back on documentation)
###Then use the lowest level of hardware control

Using the daemon from the upper level would be:

import Atcfwheel
fw = Atcfwheel() #Initializes to the exact device and all parameters needed because all of those params come from the daemon config
fw.connect() #use the standard daemon controls for debugging which would be easy and familiar

Using the daemon without ".serve()", not "starting" the daemon but using all of its functionality while still having access to its lowest level hardware control library via fw.dev.{low level functions}

Let me know your thoughts or comments about this kind of utility. Thank you all!

Metadata

Metadata

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions