<azonenberg>
whitequark: can you spin up your scope port forward again? i'm refactoring the SCPI transport code and will want to test in 15 mins or so
<whitequark>
uhhh okay
<whitequark>
azonenberg: should be up i think
<_whitenotifier-3>
[scopehal] azonenberg opened issue #68: Refactor LeCroy scope driver to use SCPITransport - https://git.io/fjElE
<_whitenotifier-3>
[scopehal] azonenberg labeled issue #68: Refactor LeCroy scope driver to use SCPITransport - https://git.io/fjElE
<_whitenotifier-3>
[scopehal] azonenberg opened issue #69: Refactor HMC804x driver to use SCPITransport - https://git.io/fjElu
<_whitenotifier-3>
[scopehal] azonenberg labeled issue #69: Refactor HMC804x driver to use SCPITransport - https://git.io/fjElu
<_whitenotifier-3>
[scopehal] azonenberg opened issue #70: Refactor HMC801x driver to use SCPITransport - https://git.io/fjEl2
<_whitenotifier-3>
[scopehal] azonenberg labeled issue #70: Refactor HMC801x driver to use SCPITransport - https://git.io/fjEl2
<azonenberg>
whitequark: 5556? no reply
<azonenberg>
it appears to connect but drops when i send any traffic
<whitequark>
oh sec
<whitequark>
azonenberg: again
<whitequark>
er, hang on
<whitequark>
again
<azonenberg>
lain/error_404: fyi i'm creating a new SCPITransport / SCPISocketTransport class to split all of the transport layer stuff from driver code
<lain>
:o
<azonenberg>
so you can write a driver once then move it over rs232, usb, ethernet, etc
<azonenberg>
you of course have to have written the transport classes and right now TCP sockets are the only one i have
<azonenberg>
but you could add say a USBTMC one
<lain>
cool
<azonenberg>
Now 99% of oscilloscopes can just derive from SCPIOscilloscope and take a SCPITransport* in the constructor
<azonenberg>
and it does the rest for you
<azonenberg>
however this isn't forced on you, and you can use custom binary protocols or external APIs etc if needed
<azonenberg>
whitequark: do you have external trigger set on your scope right now?
<azonenberg>
if not, what channel is currently selected as the trigger?
<whitequark>
azonenberg: uh, let me see
<whitequark>
azonenberg: ch1 negedge
<whitequark>
and ch1 has a square wave
<azonenberg>
oh so bonus of this refactoring
<azonenberg>
you get scpi command logging for free
<azonenberg>
just add --trace SCPISocketTransport
<_whitenotifier-3>
[scopehal] azonenberg pushed 1 commit to master [+6/-2/±4] https://git.io/fjEl9
<_whitenotifier-3>
[scopehal] azonenberg a3b46a7 - Created SCPITransport/SCPISocketTransport classes, refactored Rigol driver to use it
<_whitenotifier-3>
[scopehal-apps] azonenberg pushed 2 commits to master [+0/-0/±2] https://git.io/fjEl7
<_whitenotifier-3>
[scopehal-apps] azonenberg cedc1b2 - Updated freqresp example
<_whitenotifier-3>
[scopehal-apps] azonenberg 88bb365 - Now using SCPITransport for Rigol driver
<_whitenotifier-3>
[scopehal-cmake] azonenberg pushed 1 commit to master [+0/-0/±3] https://git.io/fjEl5
<_whitenotifier-3>
[scopehal-cmake] azonenberg 8d90c01 - Updated to latest submodules, added freqresp example
<azonenberg>
So, i guess next order of business is to try banging up that R&S driver using the new api
<azonenberg>
i'll worry about backporting it to the older drivers later
<azonenberg>
but all new drivers should use this
<azonenberg>
since it means multi-transport scopes are now drop-in without any changes to the driver class
<_whitenotifier-3>
[scopehal] azonenberg pushed 1 commit to master [+0/-0/±4] https://git.io/fjE8C
<_whitenotifier-3>
[scopehal] azonenberg a2da179 - Moved *IDN parsing to SCPIOscilloscope
<_whitenotifier-3>
[scopehal-apps] azonenberg pushed 2 commits to master [+0/-0/±3] https://git.io/fjE8w
<_whitenotifier-3>
[scopehal-apps] azonenberg 2626343 - fgtest/curvetrace: now using SCPITransport
<_whitenotifier-3>
[scopehal-apps] azonenberg c077b8d - Added support for creating RohdeSchwarzOscilloscope instruments
<_whitenotifier-3>
[scopehal] azonenberg pushed 6 commits to master [+4/-0/±12] https://git.io/fjE8r
<_whitenotifier-3>
[scopehal] azonenberg 9487366 - HMC8012: now using SCPITransport. Fixes #70.
<_whitenotifier-3>
[scopehal] azonenberg bb31766 - HMC804x: now using SCPITransport
<_whitenotifier-3>
[scopehal] azonenberg e1e7f75 - Added error return value to SCPITransport
<_whitenotifier-3>
[scopehal] ... and 3 more commits.
<_whitenotifier-3>
[scopehal] azonenberg closed issue #70: Refactor HMC801x driver to use SCPITransport - https://git.io/fjEl2
<_whitenotifier-3>
[scopehal] azonenberg commented on issue #69: Refactor HMC804x driver to use SCPITransport - https://git.io/fjE8o
<_whitenotifier-3>
[scopehal] azonenberg closed issue #69: Refactor HMC804x driver to use SCPITransport - https://git.io/fjElu
<_whitenotifier-3>
[scopehal] azonenberg opened issue #71: Refactor Siglent driver to use SCPITransport - https://git.io/fjE8i
<_whitenotifier-3>
[scopehal] azonenberg labeled issue #71: Refactor Siglent driver to use SCPITransport - https://git.io/fjE8i
<_whitenotifier-3>
[scopehal] azonenberg opened issue #72: Create VICP SCPITransport class - https://git.io/fjE8X