 |
 |
 |
 |
 |
 |
 |
| Mac OS | Ubuntu / Debian |
Fedora / RPM |
Windows | WinUSB Driver | Code | Forums |
This software is used to interface to Gabotronics' line of oscilloscopes (Xprotolab / Xminilab). The PC interface has been rewritten in the Qt framefork so it can be multiplatform. This is the FIRST RELEASE of the software, meaning that it may have many bugs. Please report bugs in GitHub.
This application is open source, so everyone is encouraged to improve it.
For Windows, you will need to install the WinUSB drivers using the ZADIG tool.
For USB connectivity, you will need:
- USB capable device, such as the Xminilab HW 2.0, or Xprotolab HW 1.7.
- Update the the device with the latest firmware.
- Connect the USB device and install the USB Driver. I currently don't have a digital signature from a certificate authority, so you will get a big red warning when installing the driver. Trust me, the driver is just WINUSB with my own .inf file.
This application is open source, so that anyone can port it to another OS, or perhaps just use the source for a similar project.
Thanks to Murray Lindeblom for his contribution on the WINUSB drivers.
Thanks to Scott McCain for his contribution for a modern UI remake of the .NET application.
Comments
http://www.microsoft.com/net/download.aspx
Works on my XP after getting over some initial strangeness probably due to changing too many controls too fast. Updates surprising fast, 1 per second for dual channel display. I connected through my own level shifters to serial COM1, don't have a UART USB cable.
I didn't realize that I was still using old firmware without USB support. So I had to upgrade the firmware.
According to "http://www.stderr.nl/?-tags=" I had to manually install version 6.1 of avrdude (previous versions) (including some dev libraries) and upgraded the firmware :
/usr/local/src/avrdude-6.1/avrdude -c flip2 -p x32a4u -U application:w:xminilab.hex:i
/usr/local/src/avrdude-6.1/avrdude -c flip2 -p x32a4u -U eep:w:xminilab.eep:i
I am having trouble connecting it to my computer. I downloaded the latest Windows Net 4 program. The PC user interface works as well. However, when I use a microusb to connect the protolab to the computer and press "connect" on the PC user interface, it doesn't seem to connect and gives "error" in the firmware box below. Do you have any suggestions? I really want this to work because of how good of a device this is!
Amazing unit ! could you please let us know when the next version of pc software is going to be availible? really got a big project and need the logic analizer to interface with my PC
http://www.jayconsystems.com/usb-otg-cable-female-a-to-micro-a-5.html
Any news on on the pc interface software update?
Best Regards
Jody
Could you give us an update on the PC Software update?
Best Regards
Jody
Updated xmega xprotolab to v2.25 firmware via usb AVR flip program. Installed (i think correctly via zadig software) the usb driver to connect via microusb to win7 64 machine. Xprotolab shows in device manager under universal serial bus devices as XScope, it does not seem to have an associated COM port listed in properties.
Load the compiled .net interface, clicked options tab and couldn't connect as no com port associated with XScope. I suspect I haven't installed the correct driver. Any recommendations?
Thanks,
Ed
I cannot find a download link on this page.
extract compressed download
navigate to extracted folder
double-click the appropriate .deb file to install
type command line $sudo sh usbfix.sh (followed by your user name)
it works, it works it works! YAAAAAAAAAAAAAAAAAAAA!
Cheers
Kevin
If anyone wants to compile it themselves, here's what I did:
1) get homebrew http://brew.sh/ and Apple's developer tools (homebrew should give you instructions if you don't have them)
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) fix linking info: edit 'XprotolabInterface.pro', find the line which looks like "unix:!macx:!symbian: LIBS += -lusb-1.0" (near the end) and delete ":!macx", so that it looks like "unix:!symbian: LIBS += -lusb-1.0"
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.
Cheers!
@ganzziani: Thanks for including the app on top! Feel free to let me know if you'd get some issues with that reported, and also if you'd want me to compile newer versions.
Noticed one small problem with the UI - in Oscilliscope mode, under "Vertical" the tabs for "FFT" and "REF" are clipped on my machine (Macbook Pro 13" Retina 2014)
Screenshot: https://drive.google.com/file/d/0B_oayye0KbyZSkdzMFZBVXVmZ0k/edit?usp=sharing" rel="nofollow" target="_blank">https://drive.google.com/file/d/0B_oayye0KbyZSkdzMFZBVXVmZ0k/edit?usp=sharing
Thanks again!
I have successfully been using my Xminilab with your interface on a laptop running Windows 8.1 - it really works extremely well, thanks! However, I am now trying to install the interface on a second laptop running Windows 7. I have used the Zadig tool to install the driver and this appears to work but it shows up in Device Manager as "Xscope" under USB devices. The problem is that the interface is looking to connect to a COM port which is different. I did not have this problem on my other machine and I am now at a loss as to how to proceed. Any advice would be very much appreciated.
Just realised the query above should have been posted on the appropriate forum. I will repost there.
the same issue as mrh on W7 64bit, shows Xscope under device manager and no additional COM port.
I put Xmega/Xprotolab in a box, soldering standard switches to the micros on the PCB, making some circuital extensions and, at the end, it all works on the mini Oled. I wasºtrying to connect to the windows application. Firmware is 2.25, app is the last Qt one, I tried with all drivers you put on your site and with the last version of Zadig. The tests were made on a seven 64 bit and on a XP 32 bit computer... always the same result: unknown device. And obviously Qt app remains waiting for a com port in the option tab without being able to connect. Is it possible that I exchanged data wires on the usb connection? Indeed I soldered also this one to make possible the boxing and, as long as I know, data wires are not ordered wires. Are they? Am I wrong? I need the scope to work on I2C buses and also as a sniffer but using the Oled it's impossible. May you help me? Could it be a problem of wire??
Thx in advance for your patient and I excuse myself if these question had to be posted in the forum area... sincerely I don't know.
Gracias por todo!
Another option, if you have time, perhaps you could install Qt and compile the code on your computer.
Thanks
James
* The USB driver linked from the gabotronics site (v2.0.1.162) wouldn't install under Win 8.1. I had to go to zadig.akeo.ie to get the vista-and-later driver (v2.1.2), then run the installer twice -- once to install the WCID driver, then again to install the "driver". Until both were done, it didn't show up as an xscopes USB device.
* XScopes application installed just fine, but said MSVCP100.dll was missing when run. That's from the MS Visual C++ 2010 redistributable package, so a quick trip to microsoft.com to get and install that allowed xscopes to run.
Success :D
Just received my XProtolab Plain yesterday and I've been using it successfully in Linux Mint 18.1. Everything in the software works great. I do have one question:
How do you determine the frequency of the peaks in FFT display?
Thanks!
Just received my XProtolab Plain yesterday and I've been using it successfully in Linux Mint 18.1. Everything in the software works great. I do have one question:
How do you determine the frequency of the peaks in FFT display?
Thanks!