Add support for instrument with channels. about pyvisa-sim HOT 8 CLOSED

Agreed. Maybe the way is to add a channels entry in the property dict and require that getters and setters are written with named placeholders such as {channel:d} and {value:.3f}

I will release version 0.1 later this week and start with this afterwards.

from pyvisa-sim.

It might be better to keep track of the channels at the instrument level rather that at the property level, as often instruments have many (a dozen) property which apply to channel. Could you do some hierarchical declaration in the YAML like this:

device PNA:
    properties : 
         # instrument wide properties
    channel :
         properties:
              # channel specific declaration.

Otherwise I fine with the use of '{channel}' or '{ch_id}' (may make sense to use the same we may use in lantz, whatever it ends to be).

from pyvisa-sim.

I think the latter implementation is only manageable if issue #16 is resolved first, otherwise for channels that share a lot of the same properties, it could get a bit tedious to define them.

from pyvisa-sim.

I might start working on this during this week. @hgrecco can you give any pointer where to look at first ?

from pyvisa-sim.

Most of the work will be in devices.py where you'll have to modify getters and setters inside of the Device class. Some work may be necessary in parser.py to accomodate the new yaml tags.

from pyvisa-sim.

Indeed most changes will be in devices.py @MatthieuDartiailh If you proceed to implement your hierarchy, it would be a good idea to have a way to specify the valid values fo r the channel.

from pyvisa-sim.

It is my intention indeed. But the ideal would be to specify in the resource which channel are active. But I will let that for another PR.

from pyvisa-sim.

close as of #27

from pyvisa-sim.