Benedikt Burger

> However, isn't this already possible right now, if you pass Yes. My solution (in comparison to dkriegners) keeps that mechanics as is, but makes it more simple to create...

The original request of this issue was, to put some parameters globally and others specifically, due to the requirements of a specific converter. I propose to follow the documentation: define...

@dkriegner your two examples are mutually exclusive unless the adapter_kwargs contains the baud_rate (maybe in `asrl={'baud_rate': 2400}`) as well. If we have that single point of information, it should contain...

User defined adapters ignore the connection settings in the instrument, therefore it does not matter, whether it is defined as single connection or multi connection.

I don't understand you. If you have ~~~ adapter = SomeAdapter(...) Inst = MyInst(adapter...) ~~~ The adapter does not get anything defined in "MyInst.__init__".

Good point. "Genérica" or "pymeasure" would be a manufacturer and would be better than to put a generic spectrum analyzer in the root path (where only the "building blocks" (instrument,...

Auto correction at its best...

> I'd put a generic spectrum analyzer into `instruments/generic_types.py`? And aren't the generic types "building blocks" (for the manufacturer-specific instruments)? Mhmm. They are builiding blocks, but could also be used...

What version of pymeasure do you use? I think such an issue got already addressed, but I do not know, whether it is already released.

Sorry for the late response. I checked the code, funnily enough, the line numbers of your error message do not match the code of the tag 0.12.0. Nevertheless, you use...