<d1b2>
<azonenberg> Oh. yeah none of the currently implemented bridge scopes have more than one stream on a channel so that would make sense
<d1b2>
<azonenberg> you'll have to override those methods and extend the protocol for your scope
<d1b2>
<azonenberg> or well,. not even extend the protocol since all of the range stuff is done clientside
<d1b2>
<azonenberg> but if there's instrument config to do too that will need a protocol extension
<d1b2>
<azonenberg> the remote bridge protocol now is basically the common features of the Digilent, ThunderScope, and PicoScope drivers
<d1b2>
<rapzak_> yearh i have overwritten the functions an seems to work... i may consider skip the remotebridge...
<d1b2>
<azonenberg> yeah there's absolutely no requirement to use that class it's just a convenience helper for network-attached custom scopes since we used so much of the same features in each driver
<d1b2>
<azonenberg> if your instrument is significantly different in feature set it may not buy you much
<d1b2>
<rapzak_> i gave me a lot learning
<d1b2>
<rapzak_> together with the tiny vna driver for stream
<d1b2>
<azonenberg> (in fact i think we started with separate drivers for pico and digilent then i combined the copy-pasted code and refactored into a base class)