Christoph Buchner

Thanks, appreciate the offer and the link to your implementation, that is quite useful. Oh, the APT implementation is quite large! :-o In any case, I think we need to...

#621 add instruments (TC038 and TC038D) with a command_word-target_register-length kind of syntax, so this fits into this frame-based communication scope.

I see you point I think, although I'm wondering if the [problem in #559](https://github.com/pymeasure/pymeasure/pull/559#discussion_r780658782) (i.e., the need to copy the `values()` implementation) could have been avoided by encapsulating the device-specific...

> In my understanding, looking at the code, I see the following: Agreed on all points > What is the recommended paradigm to implement instrument using a binary interface (as...

> custom wrapper-class could be proposed to do the interfaceing between the properties in the instrument definition and the backend (adpter-class and lower HW IF) Yes, this is one thing...

> I was thinking about event based communication in pyVISA in combination with the extended status reporting defined in SCPI99 page 50 Thanks!

AFAIK, USB and LAN can be handled by PyVISA, too. > I agree, but then I don't understand the code here https://github.com/pymeasure/pymeasure/blob/9f265683a2bd28e8a87139e8d01cad37baaafc27/pymeasure/instruments/toptica/adapters.py, where a custom adapter includes instrument specific settings...

Re supporting Prologix: Might be worth it to ping the pyvisa maintainer in that issue, he [seems open to merging a PR](https://github.com/pyvisa/pyvisa/issues/112#issuecomment-422954079) (and there is some draft code below that...

Yeah, Mixins could be a nice solution to this problem, as we typically only have to override a couple of classes. There are a couple of rules/guidelines to observe (order...

> My gut feeling is that last draft proposal from @bilderbuchi is preferred. Sorry for not numbering my alternatives. I'm assuming you mean this approach "put the mixin on the...