alexhw has quit [Remote host closed the connection]
alexhw has joined #scopehal
m4ssi has quit [Quit: Leaving]
bvernoux has joined #scopehal
m4ssi has joined #scopehal
m4ssi has quit [Remote host closed the connection]
andres has joined #scopehal
andres is now known as Guest33892
<Guest33892>
Hello there
<Guest33892>
Can anyone give me a small intro to scopehal? (I would like to connect to my Rigol osc)
<azonenberg>
o/ Guest33892
<azonenberg>
Which rigol do you have?
<azonenberg>
and what interface are you trying to connect via?
<azonenberg>
right now i believe only ethernet is supported, and only tested on the DS1000Z series although other rigols may use the same command set and work
<azonenberg>
As of now i think the driver is also read-only and doesn't support changing of trigger settings or volts/div etc (i.e. you have to configure the scope via the front panel and then use scopehal only to analyze the data coming off)
<azonenberg>
Would not be hard to do the rest of it, I've just been busy and nobody's bugged me about it :)
<Guest33892>
Hey, sorry I was afk. It is actually a DS1104Z
<azonenberg>
Perfect. I haven't touched that code in a bit as i don't own a DS1000Z myself but i haven't done anything that should have broken it so it should work fine
<azonenberg>
(whitequark loaned me one over the internet to do initial driver dev with)
<azonenberg>
To start, go grab azonenberg/scopehal-cmake from github, make sure you get all of the submodules too
<azonenberg>
and compile everything
<Guest33892>
Done ! :)
<azonenberg>
ok, so the main client application you'll use is "glscopeclient". Right now due to an open issue, it has to be launched from src/glscopeclient as the working directory
<azonenberg>
There's currently no GUI connection dialog, so you have to specify the target instrument as a command line argument
<azonenberg>
so for example glscopeclient myscope:rigol_lan:192.168.1.2:5555
<azonenberg>
adjust the ip and port as needed, "myscope" is a nickname that helps you tell apart instruments if you have more than one connected
<azonenberg>
you can pass multiple connection strings to talk to several scopes at once, although the integration between them isn't as clean as i'd like yet
<azonenberg>
glscopeclient also takes standard logtools arguments to increase debugging verbosity, --verbose or --debug are probably good to add to get extra details if you have any trouble
<Guest33892>
Ok, so rigol_lan is the software brick used to connect to the scope ?
<Guest33892>
I'm hooking up the scope as we speak
maartenBE has quit [Ping timeout: 265 seconds]
<Guest33892>
So I hear my scope glitching as I try to connect
<Guest33892>
Question: A shaders error is a missing dependency ?
<Guest33892>
Oh I see what you meant now. Copy the binary and execute it from the $(REPO)/src/glscopeclient folder
maartenBE has joined #scopehal
<azonenberg>
Copy, or just chdir to that directory
<azonenberg>
and run ../../blah/glscopeclient
<Guest33892>
So if the only debug message that I see is "Connecting to SCPI ..." it means there is something wrong with my link
<azonenberg>
sec...
<azonenberg>
What's the title of the main application window?
<azonenberg>
Does it show the full scope model name and serial number? if so, you connected
<Guest33892>
I have a border with no fill actually
<Guest33892>
Literally just the window border, it looks like a graphics problem
<azonenberg>
Hmmm. Either that or it's hanging trying to connect
<azonenberg>
close glscopeclient and try to connect to your scope IP/port via telnet/netcat
<azonenberg>
send "*IDN?" (no quotes
<azonenberg>
do you get an id string back?
<Guest33892>
Yes I have the data
<Guest33892>
That's a relief at least for the LAN art
<Guest33892>
part*
<Guest33892>
I tested a couple of commands and it responds. When I open the client it resets the channels back on, so I'd say it's responding
_whitelogger_ has joined #scopehal
_whitelogger has quit [*.net *.split]
_whitenotifier-e has quit [*.net *.split]
<azonenberg>
Back
<azonenberg>
But you're still getting no UI updates? Can you send a screenshot>?
<azonenberg>
Guest33892:
<Guest33892>
Exactly, I see the serial number in the title as you said, but the UI is just non existant
<Guest33892>
Sorry, I don't really know how to send a screenshot :/ I'm (re)learning irc
<azonenberg>
save a screenshot then upload somewhere (say, imagebin.ca) and send the link here
<bvernoux>
Guest33892, are you using a VM or a native GNU/Linux ?
<bvernoux>
as it seems like an OpenGL bug ...
<Guest33892>
Native (Arch Linux)
<bvernoux>
what is your GFX card ?
<bvernoux>
maybe it does not support OpenGL ...
<azonenberg>
bvernoux: also possible the app is hanging without rendering anything
<azonenberg>
Guest33892: can you pastebin the output of glxinfo?
<azonenberg>
also, try to attach a debugger and see if you can figure out if it's hanging somewhere
<bvernoux>
azonenberg, yes but when I have tested glscopeclient on my VM I had same issue because I have not used the right emulation with OpenGL support
<Guest33892>
The gfx card is an onboard intel (nvidia deactivated) but I don't think that's the issue
<azonenberg>
yeah it supports gl 4.5, i don't think i use any features past 3.0 or so
<azonenberg>
It's possible the app is hanging early on during initialization somehow
<azonenberg>
attach gdb and see if it looks to be frozen?
<azonenberg>
also try wireshark on the connection from you to the scope and see if there's constant traffic or if it stops
<Guest33892>
I will in a couple of minutes, have to go now. But will post the updates later. Thank you very much! Will do the GDB debugging
<Guest33892>
Well, startup after system update seems to work
<Guest33892>
I will test with the scope and report back !
<azonenberg>
it works after you updated?
<Guest33892>
Yes
<azonenberg>
maybe you had some kind of driver misconfiguration then
<azonenberg>
Awesome. Let me know if you can't figure out how to do something, there's not much in the way of end user facing documentation yet
<Guest33892>
I'll give it a try yes
<azonenberg>
and like i said, changing of settings is mostly not going to be functional with the rigol driver yet
<Guest33892>
Thank you again, and I hope to contribute someway
<azonenberg>
If you want to try to work on improving that yourself, i can walk you through things
<azonenberg>
lib/scopehal/RigolOscilloscope.cpp is the relevant file for the scope driver
<Guest33892>
Great
<azonenberg>
SetTriggerVoltage(), SetTriggerType(), SetChannelOffset(), SetChannelVoltageRange(), SetChannelBandwidthLimit(), SetChannelAttenuation() are the main missing functions right now for basic functionality
<azonenberg>
a bit of googling should find the remote control manual for your scope
<Guest33892>
I downloaded the command guide of Rigol
<azonenberg>
excellent :)
<Guest33892>
Awesome, I'll try to play with it later
<azonenberg>
There's still some more advanced work left to do, for example the DS1000Z series scopes have variable sample rates depending on what channels are enabled
<azonenberg>
But i haven't implemented the UI for changing sample rates yet anyway
<azonenberg>
so that's a non-issue for now :)
<Guest33892>
haha well, there is a lot of work already done
<azonenberg>
Yeah of course. Just FYI, I'm basically the sole active developer right now and I run a 100% LeCroy shop
<azonenberg>
So one of the biggest obstacles to support for more scopes is people who have said scopes and are willing to put some work into drivers
<azonenberg>
i cant afford to buy every scope people want support for