But, if the user refresh period is lower than the period with the instrument refresh the signal, this produce more traffic than the necessary one! I will need both possibilities: subscribe and on demand.
Giving back to the bridge design, the Instrumentation class have a new method under the name Instrumentation::getCapture(int channel,double **buffer). This will ask the oscilloscope for the current curve (the double's parameter) that it have. This have no subscrition, this will not do any thing else. If you want another one, ask again.
And what is the goal on this? Now, my tango device server is able to ask to a Tektronix oscilloscope (and only a Tektronix) about the signal that it have in one channel. You can see what the instrument measures, via the distributed system:

Actualization:
The last image was on ATKPanel (written in Java), but also we are working with PyTauico (provisional name):

No comments:
Post a Comment