ganzziani / xscopes-qt Goto Github PK

If the zero position of channel 1 and 2 is reduced by the bitmap pixel offset of 9, then the ch1 and ch2 position sliders are at the precise mid point to place the graph at the precise mid point of the display. They also line up with the grid. This also makes the cursor voltage readings more reasonable. The cursors track the signal better. The positive offset observed in many situations is gone.

Cons:
The zeroposition pointer is low.

Scope repeatedly crashes to BSOD (BAD_POOL_HEADER) when started in Win7 64 bit.
Version 1.1.0.0

First, I am not very familiar with Qt. After updating Qt and pulling the latest version I run into a link issue with libusbdevice. The files for libusb seem to be all in the build folders. Any advice hwo to fix this?

OS is Windows 8.1

Thanks,
Tom

1. As soon as i press the play button and select the file generated by save wave, an error window appears that closes the program.
2. As soon as I press record button, it doesnot record anything and when I press the stop button, the program stucks.

I am using windows 8.1 64bit.

Any help or patch in this regard ?

The bit numbers on the protocol sniffer page in xscope are supposed to be numbered 4 to 7

link to forum post

Application seems to run but gains are set at 0 v/div and can't be changed. No traces appear. The hardware and software both work fine on MacBook Air with OSX 10.8

See the discussion at the end of #30

I compiled the code in ArchLinux, but the screen is too big to fit my display size. Is there a way to resize/add a scroll bar/zoom out the window?

This is how the UI looks like on a 3200 x 1800 Pixels Display with scaled Fonts:

Also, the size of the right part with controls cant be changed.

I corrected this by installing the Microsoft distribution from http://www.microsoft.com/en-us/download/details.aspx?id=8328 although some better method is probably in order.

1. When channel invert is selected:
   • The trigger mark has to be inverted as well
   • The channel label has to change from “CHn” to “-CHn”
2. If the channel math is enabled, then the channel label has to change to the operation performed, taking into account if the channel is inverted.

1. The position of the trigger mark is not read correctly at startup (or when restoring the settings), it seems to have an offset. Try this:
   a. Start the application, set the trigger mark on a particular spot. Then close the program
   b. Start the application again, now the trigger mark is not at the same place.

The windows display just not working, the channel 2 to AWG display will look correct till I make a few tab changes to do setup. After a few minutes during a tab change the trace will be gone. the markers and voltage readings jitter or change value so fast you can not read it.

Trying to start the app only brings up the splash screen telling me that the software quit unexpectedly. Nothing I do does anything different.

Hi! Thanks for good product!

I use arch-linux + xfce4.

For qt apps i use qt5ct theme (QT_QPA_PLATFORMTHEME=qt5ct, QtCurve theme, darker color-scheme).

In the application, the background color and the text color is light. Labels are not visible.

I remove all background colors from *.qss files and that solve problem for me.

The IQ FFT display on the PC is not properly centered around 0Hz.
It is centered on the device's screen.

The screen is refreshed as fast as possible, instead of waiting for data to be available from the usb. In the constructor of the Main Window, we have:
dataTimer.start(0);

Instead of doing this, there should be a signal generated from the usb library, connected to a slot on the graph drawing.

Hi

I wanted to use xscopes to mesure a condenser discharge time, so I set up a trigger to single mode and wanted to record the result onto a file and use another program for fine mesurements.
But when the oscilloscope is paused, saveWavetoFile() is never triggered; and I didn't managed to call it manualy (it does saves, but empty files. There's something with buffers that I don't get).

If the Decay is set when switching to the XY mode, old waveforms remain on the screen

Vertical lines appears instead of the display getting completely filled.
Also, changing oscilloscope settings need to reset the display.

Hi,
I'm seeing an issue with XScope 1.0.0.2 on OSX.
When the issue occurs the oscilloscope (left) section of the UI freezes up. The physical oscilloscope still works and when I make changes (like turning on and off a channel) then the changes are reflected on the physical device but not in the oscilloscope graph section.

While experiencing the issue the app refuses to be terminated through the use of "quick" and must be terminated using "force quit".

The meter reads zero for both channels in the linux version. The windows version shows voltages in the meter correctly.

Hi,

It recompiles in itself and runs stand-alone, but whenever USB connection is tried, it crashes instantly
I have followed the previous recipe before on Sierra, but now, on my new machine, it does not result in a working version...

Anyone has any idea how to make this work again?

Potential issues with Xcode/SDK versions
use xcode-select to set path to older versions if needed
0) sudo  xcode-select -s /Applications/Xcode92.app/Contents/Developer
1) get homebrew http://brew.sh/ and Apple's developer tools (homebrew should give you instructions if you don't have them)
1b) brew update
1c) brew upgrade
2) install qt and libusb: brew install qt libusb
3) get xscopes' sources: git clone https://github.com/ganzziani/xscopes-qt.git
4) change into the cloned dir: cd xscopes-qt
5) export PATH="/usr/local/opt/qt/bin:$PATH"
6) compile: qmake && make
7) now you should have a newly created 'xscope.app' in your directory. Note that it links to brew's qt and libusb, so it will only work on your computer. To make it really 'standalone', there's more fiddling required to get the libraries into the app itself.

Hello, I have compiled the app on linux, but when I try to connect the device via USB the app sees the cable but when I press connect, I get 2/3 seconds of grey app and then nothing, no device found. I have executed the USBfix.sh but no luck, any idea?

I also have the bluetooth addon and tried the download precompiled app for both windows and linux from the main page but no luck. The device (XMEGA Xprotolab) does work on a old windows app that I found and it's missing a few options, so there is no problem with the device.

Thank you,
Constantin

using xscope, I expected the use of the normal mode instead of the single mode to result in a reset of the buffer. However, this does not happen, not in circular mode and not in linear mode.

Normal mode: Continuous operation, when the buffer is filled, all pages are erased, the index goes back to page 1

I use an xprotolab with firmware 2.40

Is this a xprotolab bug or a xscope bug?

In the udev rules file (extra/linux/64-xscope.rules#L1) it should be GROUP="plugdev" and not GROUP=="plugdev", since that is supposed to be an assignment and not a comparison.

The Qt5Network headers and libraries need to be made available in the CMakeLists.txt to successfully build the project.

When the two vertical tracers are placed on the screen, the delta-T measurement in the top right appears to be correct, but the frequency (1/delta-T) is off by a factor of 1000. I'm currently measuring a period of 0.5s, and it tells me the frequency is 2kHz.