Activity for xoscope: digital oscilloscope
-
Brent Baccala committed [d97b9b] on xoscope
get strip chart mode working again by putting back in some of the code to process the old SignalLines
-
allow us to "mute" the first channel and still see Lissajous curves on the second
-
remove code that's been commented out for over 20 years
-
in accumulate mode, limit the number of old traces to ten, and fade out their color
-
don't rescale/reshift the saved signallines; makes it easier, so we don't recompute them anymore
-
a working x-y display
-
my first attempt at a crude x-y display
-
configure changes suggested by "autoupdate"
-
Commit 0107c7 should fix this
-
fix bug #24: use correct argument types and return types when defining a configure test function
-
franta posted a comment on ticket #24
After some search, it seems as a temporary crutch, changing CFLAGS during configure can be used: %configure CFLAGS="%{optflags} -Wno-implicit-int -Wno-int-conversion" (in my case, change is in RPM packager xoscope.spec file)
-
comedi_get_cmd_generic_timed configure test failed
-
Eli Schwartz created ticket #23
Build fails with LTO
-
spelling fix in man page (from Debian; fixed by Graham Inggs; reported by Petter Reinholdtsen)
-
xoscope: digital oscilloscope released /xoscope/2.3/README
-
-
bump xoscope version to 2.3
-
add bootstrap script and remove some auto-installed files
-
Migrated to GTK3
-
Felipe Castro created merge request #1
Migrated to GTK3
-
Fix this by installing the GTK 2 development package: sudo apt install libgtk2.0-dev
-
Paul - Probably your best option is to implement a custom DataSrc (see xoscope.h) and add it to the list near the top of xoscope.c. I don't think the DataSrc interface is too hard, but I think it does expect to poll a file descriptor to find out when more data is available to read. The design was intended for things like sound cards and network pipes that present naturally as file descriptors. The major alternative is to use the COMEDI interface (comedi.org), but I don't see seed listed on their...
-
Paul Bakke created ticket #9
Support for 12-Bit ADC for Raspberry Pi from Seeed
-
rmlazzari modified a comment on discussion Open Discussion
I have the same issue in my notebook running Mint MATE, only 2 options: None and COMEDI. Curiously, my desktop's instalation running Mint Cinnamon offers the Alsa option as device. But the options under Mint MATE's instalation are "None" and "COMEDI". None does nothing. COMEDI says: "/dev/comedi0 No such file or directory". If somebody could help me, I'd be grateful. This is the configuration with issue: System: Host: HP1000 Kernel: 5.4.0-62-generic x86_64 bits: 64 compiler: gcc v: 7.5.0 Desktop:...
-
I have the same issue in my notebook running Mint MATE, only 2 options: None and COMEDI. Curiously, my desktop's instalation running Mint Cinnamon offers the Alsa option as device. But the options under Mint MATE's instalation are "None" and "COMEDI". None does nothing. COMEDI says: "/dev/comedi0 No such file or directory". If somebody could help me, I'd be grateful. P.S.: I'm just a newbie retired hobbyst, so I'd appreciate good will but I don't understand too much tech directions. Thanks anywa...
-
I have the same issue in my notebook running Mint MATE, only 2 options: None and COMEDI. Curiously, my desktop's instalation running Mint Cinnamon offers the Alsa option as device. None does nothing. COMEDI says: "/dev/comedi0 No such file or directory". If somebody could help me, I'd be grateful. P.S.: I'm just a newbie retired hobbyst, so I'd appreciate good will but I don't understand too much tech directions. Thanks anyway.
-
I have the same issue in my notebook running Mint MATE, only 2 options: None and COMEDI. Curiously, my desktop's instalation running Mint Cinnamon offers the Alsa option as device. None does nothing. COMEDI says: "/dev/comedi0 file or folder missing". If somebody could help me, I'd be grateful. P.S.: I'm just a newbie retired hobbyst, so I'd appreciate good will but I don't understand too much tech directions. Thanks anyway.
-
Joe Smith created ticket #22
Does not compile on Ubuntu 18.04 - cannot find GTK
-
Raymundo Cassani posted a comment on discussion Open Discussion
Hi, I tried to build the xoscope2.2 and I got the following error: /usr/bin/ld: display.o:(.bss+0x90): multiple definition of `font'; xoscope_gtk.o:(.bss+0x10): first defined here collect2: error: ld returned 1 exit status make[1]: *** [Makefile:474: xoscope] Error 1 make[1]: Leaving directory '/home/cassani/.cache/yay/xoscope/src/xoscope-2.2' make: *** [Makefile:375: all] Error 2 I'm using gtkdatabox 0.9.3.1 and gtk 2.24.32. To be able to complete the build, I remove the line 38 (shown below) from...
-
Dear John, Why don't you submit it as a patch? I don't anticipate a new xoscope release any time soon, but if it cleanly applies, I'll put it into the git repository myself. agape brent On Thu, Apr 30, 2020 at 1:25 PM John T Nogatch ac6sl@users.sourceforge.net wrote: I have created a new builtin math function "X,Y. 1,2" which plots Channel 1 vs. Channel 2. The attached screenshot shows a 2 kHz sine wave, out of phase. This function is quite small, similar to "Sum 1+2". It requires plot_mode=Point,...
-
John T Nogatch posted a comment on a wiki page
I have created a new builtin math function "X,Y. 1,2" which plots Channel 1 vs. Channel 2. The attached screenshot shows a 2 kHz sine wave, out of phase. This function is quite small, similar to "Sum 1+2". It requires plot_mode=Point, and it cannot display more than 1 point at any X value; note the scarcity of points at the right and left sides of the ellipse. Shall I submit this as a patch ? Or, may I have access to do a "git push" ?
-
gebhard matt posted a comment on discussion Open Discussion
Hi, on ubuntu 19.04 I could sucessfully compile it (thanks to gtkdatabox 0.9.3.1). But device menu gives "none" ? Also starting with padsp xoscope did not help. Any pointers how to tell "xoscope" which alsa-device to use ?
-
Jim Shorney posted a comment on discussion Open Discussion
Fixed. https://sourceforge.net/p/xoscope/discussion/23485/thread/c17ca91b/
-
Remberto Gomez posted a comment on discussion Open Discussion
Ooooh! It works OK! On the xoscope-2.2 directory, running: LD_LIBRARY_PATH=/home/remberto/Descargas/gtkdatabox-0.9.3.1/gtk/.libs ./xoscope Now I only need to do a shortcut on the Desktop. Thanks!
-
I think I see the problem. There should be a space between ".../gtk/.libs" and "./xoscope". It's an obscure syntax. You can set an environment variable for a single command by invoking the command as "ENVNAME=val command" (with a space between them). Without the space, the command just sets a shell variable (a little different from an environment variable, since it doesn't get passed to the command) and does nothing else.
-
On the xoscope-2.2 directory, as root, I ran: GTKDATABOX_LIBS='-L /home/remberto/Descargas/gtkdatabox-0.9.3.1/gtk/.libs -lgtkdatabox' ./configure Then I ran make and make install. Next I ran: LD_LIBRARY_PATH=/home/remberto/Descargas/gtkdatabox-0.9.3.1/gtk/.libs./xoscope It did nothing. Then ran: xoscope and: root@remberto-desktop:/home/remberto/Descargas/xoscope-2.2# xoscope xoscope: error while loading shared libraries: libgtkdatabox-0.9.3.so.1: cannot open shared object file: No such file or d...
-
Sounds like it compiled right, but didn't pick up the shared library when it ran. Please make sure to run it with LD_LIBRARY_PATH=/path/to/gtkdatabox-0.9.3.1/gtk/.libs before xoscope (see my previous post) to make sure it can load the shared library when the program runs.
-
Does not run. Trying to run it from Terminal indicates : root@remberto-desktop:/home/remberto/Descargas/xoscope-2.2# xoscope xoscope: error while loading shared libraries: libgtkdatabox-0.9.3.so.1: cannot open shared object file: No such file or directory
-
To fix the screen color problem, install gtkdatabox-0.9.3.1 from sourceforge: https://sourceforge.net/projects/gtkdatabox/files/latest/download There's no package; I just released this today. You'll probably then need to recompile xoscope, making sure that it uses the new version of gtkdatabox. Probably the easiest way to do this is to install gtkdatabox (run 'make install' as root); it will install in /usr/local by default. Then recompile xoscope. If you can't or won't muck with your /usr/local,...
-
I just reinstalled it from the xoscope-2.2.tar.gz file, and it's working now with the ALSA driver. How can I fix the screen color problem?
-
The screen color problem has been fixed. It was a bug in the gtkdatabox library. The limited device options seem to be a packaging problem. I just configured and built on Ubuntu 18.04.1 LTS and the sound card recognized and worked with the ALSA driver.
-
Esteban posted a comment on discussion Open Discussion
Same thing happening here. Is this bug already fixed?
-
But still the only device options visible on the menu are "None" and "COMEDI". How did you make your Xscope show the signals?
-
Mark Kimball posted a comment on discussion Open Discussion
I had the same problem until I started alsamixer and selected my built-in sound card using F6. Apparently the ALSA default source in 18.04 is NOT the sound card. Computer: Lenovo W530 thinkpad
-
magiblot 1 posted a comment on discussion Open Discussion
It now works fine for me in Arch Linux. Thank you very much. Which reminds me of this: I always get around 17 fps. Is there any way to get more?
-
A Hopkins posted a comment on discussion Open Discussion
OK - just me being inexperienced with Linux / Ubuntu.... it works. Thanks for your help
-
I've installed Ubuntu 18.04 Budgie in a virtual machine and found that the fix worked. Let's see... could you double-check your library paths? Run something like: LD_LIBRARY_PATH=/.../gtk/.libs ldd /usr/bin/xoscope | grep gtkdatabox and ensure that it's pointing to the newly compiled version and not the system version. We'll get to the bottom of this... eventually!
-
Confirming this. Xoscope 2.2 complied from source worked beautifully in Kubuntu 14.04 LTS but has the white screen in Kubuntu 18.04 LTS. I miss mywonderful line monitor.
-
I just upgraded to Ubuntu 18.10 / GNOME 3.30.1 and no change . Still using Budgie
-
Thanks Brent Ubuntu18.04.01 LTS running Budgie Memory 4G Intel Core i5 Graphics Intel Ironlake Mobile GNOME 3.28.2
-
I also got the "failed to load module" message, so I'm not worried about it. Please post your operating system configuration (distribution and version, at least), and I'll try to reproduce the problem.
-
Hello - Didn't work for me. Xoscope loaded, but it still looked the same. Message: 11:21:29.552: Failed to load module "canberra-gtk-module"
-
Hello - Didn't work for me. Xoscope loaded, but it still looked the same. Message: 11:21:29.552: Failed to load module "canberra-gtk-module"
-
I've tracked down the problem to a section of code in the gtkdatabox library, and have committed a work around to the gtkdatabox git repository. I'm waiting to hear back from the GTK+ developers to see if there's a better way to fix the problem. I anticipate a bug fix release for gtkdatabox within the next week or two. In the meantime, you can use the fix by cloning a current snapshot of the GTK2 branch in the gtkdatabox repository and building it. You'll need to make sure that various development...
-
Joe Tular posted a comment on discussion Open Discussion
Hello, Is there any up date on this issue? Thanks
-
It's being actively investigated.
-
Confirming this. Xoscope 2.2 complied from source worked beautifully in Kubuntu 14.04 LTS but has the white screen in Kubuntu 18.10 LTS. I miss mywonderful line monitor.
-
Confirming this. Xoscope 2.2 complied from source worked beautifully in Kubuntu 14.04 LTS but has the white screen in Kubuntu 18.80 LTS. I miss mywonderful line monitor.
-
Hello I have the same issue with the grey background - any updates on a fix? Thanks
-
Martin Tharby Jones posted a comment on discussion Open Discussion
It would be useful if Autotools were mentioned in the README file, I think you need to run the following when building the sources as cloned from git. autoheader aclocal autoconf automake Then the build can continue as described. Martin Jones
-
This is a known bug. I haven't dug deep enough into it to figure it out yet.
-
David Harrison posted a comment on discussion Open Discussion
Hello, I just compiled and installed xoscope with ALSA suppoort on Devuan. So far, so good. My system, unlike a lot of screenshots I've seen, displays the scope background as white. I'd much prefer black as it's easier on the eyes. Is there a fix or setting for this? Thanks, David Harrison
-
Confirmed as a bug.
-
It was working OK on Ubuntu 16.04, now the screen is grey instead of black and the only device options visible on the menu are "None" and "COMEDI"
-
Thanks!
-
OK, I've reproduced this problem. Let me look into it a bit more...
-
The background of the graph becomes grey:
-
The background of the graph becomes grey. See the attachment.
-
Updating gtkdatabox will change the appearance of the program. Does it look reasonably like the screenshot on http://xoscope.sf.net/ ? If not, please attach a screenshot and I'll take a look at it.
-
I'm sorry, I didn't have e-mail notifications enabled. It stopped crashing for me after updating gtkdatabox and recompiling. However, the appearance of the program changed. I think you should try it yourself and check everything continues to work fine.
-
Dominique Michel created ticket #6
ALSA: use the sound card's sampling rates
-
There's an item on the TODO list to "allow user to specify an rc file", but at the moment recompiling from source is the only option you've got, unfortunately. Looks like gtk is trying to move away from rc files towards css, so at some point this part of the code needs to be reworked.
-
I modified that file into the sources and recompiled xoscope. But it would be fine if xoscope could read that file at start up, or if at least the trace colors could be set from inside xoscope or via the command line.
-
I modified that file into the sources and recompiled xoscope. But it would be fine if xoscope could read that file at start up, or if at least the trace colors could be set from inside xoscope ar via the command line.
-
Hi, I have installed xoscope on my gentoo, it seam to run fine, but I don't like some of the default colors. They seam to be defined in xoscope.rc which is into the source code but is not installed. I try to put this file in ~/.xoscope.rc or ~/.xoscope and changed some colors into it, but it doesn't work. Where is the right place for that file, or is it a file which is only used during the compilation, which would imply I must modify it in the sources and recompile xoscope?
-
Sorry I didn't notice this earlier. It looks like I got an email about this in January but I don't remember reading it. Is upgrading gtkdatabox the fix? Is anybody still having problems with a current gtkdatabox?
-
Try updating gtkdatabox to 0.9.3.0 and recompiling xoscope.
-
Discussion going on here as well: https://sourceforge.net/p/xoscope/discussion/23485/thread/2c86f09a/ No reply from the devs at the moment.
-
Bob English modified a comment on discussion Open Discussion
I am not a developer, and signed up just because this concernes me, and it's the only place I found anything on the subject, so sorry if I'm in the wrong place: I have the same problem, and magiblot 1's suggestion to open xoscope with xoscope -i 10000000 works, so thank you, but it's just a workaround and doesn't fix the problem, and now I have to launch it this way untill the error is resolved somehow. I don't usually run GUI programs from a terminal and guess I can add it to the launcher in my...
-
I am not a developer, and signed up just because this concernes me, and it's the only place I found anything on the subject, so sorry if I'm in the wrong place: I have the same problem, and magiblot 1's suggestion to open xoscope with xoscope -i 10000000 works, so thank you, but it's just a workaround and doesn't fix the problem, and now I have to launce it this way untill the error is resolved somehow. I don't usually run GUI programs from a terminal and guess I can add it to the launcher in my...
-
This is the explanation of the segmentation fault, according to gdb: Program received signal SIGSEGV, Segmentation fault. 0x00007ffff75318c4 in gdk_colormap_free_colors () from /usr/lib/libgdk-x11-2.0.so.0
-
For some reason I also get this error: "snd_pcm_hw_params_set_buffer_size_min() failed, Invalid argument"
-
I have the same problem. I compiled from the AUR repository in ArchLinux. You can start the program with xoscope -i 10000000 and quickly set the device to None. The Gdk-CRITICAL messages still appear but the segmentation fault doesn't happen unless xoscope tries to refresh the graph.
-
Koen van Vliet created ticket #21
segmentation fault on archlinux x86_64
-
exe file
-
xoscope is a Linux application. It uses fairly Linux-specific libraries to access data acquisition devices and X windows to display its output, so it's not going to compile or run easily on Microsoft Windows.
-
Gelu Crisan created ticket #2
exe file
-
Dan McManus posted a comment on discussion Help
After trying everything I could find on line, I reloaded pulse audio and ran "padsp xoscope". After slowing down the time scale several steps, the signals were there. This seems linked to the lack of /dev/dsp. I'm just not sure if it was the reload or something else I tried. Things tried: sudo apt-get update sudo apt-get install pulseaudio sudo apt-get install pavucontrol sudo apt-get install osspd sudo apt-get install osspd-alsa osspd xoscope sudo apt-get install alsa-oss then type: aoss xoscope...
-
After trying everything I could find on line, I reloaded pulse audio and ran "padsp xoscope". After slowing down the time scale several steps, the signals were there. This seems linked to the lack of /dev/dsp. I'm just not sure if it was the reload or something else I tried. Things tried: sudo apt-get update sudo apt-get install pulseaudio sudo apt-get install pavucontrol sudo apt-get install osspd sudo apt-get install osspd-alsa osspd xoscope sudo apt-get install alsa-oss then type: aoss xoscope...
-
I posted this in general discussion first by accident so I'll repost here. I have Xoscope loaded with 16.04 on a Gateway NE71B. It loads and seems to recognize the right and left stereo sides of my sound card. It does not recognize a USB sound card I tried. I built a probe adapter and when connected to an approximately 10 hz source, I see nothing on the screen except some random noise. The noise stays when I unplug the adapter. I tried randomly varying the scale, time base and sample rate with no...
-
I have Xoscope loaded with 16.04 on a Gateway NE71B. It loads and seems to recognize the right and left stereo sides of my sound card. It does not recognize a USB sound card I tried. I built a probe adapter and when connected to an approximately 10 hz source, I see nothing on the screen except some random noise. The noise stays when I unplug the adapter. I tried randomly varying the scale, time base and sample rate with no success. I also tried "padsp xoscope". Pulse Audio Volume Control is also...
-
Dominique posted a comment on discussion Open Discussion
Hi Everybody, I have recently dowloaded and installed xoscope 2.2. When I execute xoscope, the main display opens a fraction of second and disappears with the following message: (xoscope:xxxx): Gdk-CRITICAL **: gdk_window_move_resize_internal: assertion 'GDK_IS_WINDOW (window)' failed (xoscope:xxxx): Gdk-CRITICAL **: _gdk_pixmap_new: assertion '(drawable != NULL) || (depth != -1)' failed Erreur de segmentation (core dump) xxxx is for example 9252 but it changes each time I execute xoscope. Does anybody...
-
I'm interested in useg oxoscope to characterize a motorcycle AC CDI ignition system. One output, like the alternator, may be up to 300 VAC. I see DIY hardware plans on line but they seem to be for low voltages only. Are there any plans for higher voltage applications? Or, are there any hardware kits or off the shelf hardware?
-
Graham Harris posted a comment on discussion Help
Hi, I am installing xoscope 2.2 from source on Linux Mint 18.1. ./configure led me to compile first gtkdatabox and fftw3 (in each case, I did ./configure; make; sudo make install). /usr/local/lib/ then contains libgtkdatabox-0.9.3.so.0.0.0 and a symlink libgtkdatabox-0.9.3.so.0 -> libgtkdatabox-0.9.3.so.0.0.0 Those allowed me to build xoscope the same way, and installed it as /usr/local/bin/xoscope When starting /usr/local/bin/xoscope, I get the above error. I solved this by $ export LD_LIBRARY_PATH=/usr/local/lib...
-
Anonymous modified a comment on ticket #17
hmm just an update from paul its not debian but its jlime/OE os on mips
-
Anonymous modified a comment on ticket #17
hmm just an update from paul its not debian but its jlime/OE os on mips
-
Anonymous modified a comment on ticket #17
hmm just an update from paul its not debian but its jlime/OE os on mips
-
Anonymous modified a comment on ticket #17
hmm just an update from paul its not debian but its jlime/OE os on mips
-
Michael Goertz modified a comment on discussion Open Discussion
Looks like I figured out what was going on with the voltage gain steps in #2. I'll...
