Search the Community

Hi, i just received my OpenScope today from element14. Once setup and installed Waveforms Live Agent on my Windows 10 laptop and I can't add my device. I went through the forum and non of the recommendations worked. Please advise.

First of all, background of my firmware re-installation: I was using my MacBook to power up my OpenScope MZ when I got the error message saying "USB devices disabled, unplug the device using to much power to re-enable USB devices." And then when I reconnect my openscope to the laptop, there appeared a data transfer issue on WaveFormsLive, where openscope data was flat even with the direct connection from FGEN to OSC1, and there also popped up an error message saying something about data loss during transfer (didn't screenshot that). So I thought there might have been a firmware corruption and decided to follow the guide here and here to reinstall it. I strictly follow the process, and everything was working well until the last step: when uploading OpenScope.ino I got the error message saying fork/exec /Users/siyu/Library/Arduino15/packages/Digilent/tools/xc32-tools/xc32-1.43/bin/xc32-g++: no such file or directory Error compiling for board Digilent OpenScope. anyone ever got the same problem before?

My son is doing an NPN transistor type diff gain circuit/CMRR breadboard for his class. He's using the +3V and -3V supplies and the AWG from the openscope MZ board. Seems to me he needs to ground the scope 1- and 2- leads to the black GND, otherwise floating, hence wacky results. He has in fact been floating these "-" leads and indeed got some weird results. Since he is using positive and negative supplies, the breadboard has no GND connection explicitly. So the path to ground is maybe thru the supplies, or some weird high impedance AC path thru the scope "+" leads. Shouldn't he simply build a ground plane on his breadboard where he shorts scope "-" leads to the AWG and DC supply GNDs?

Here's an OpenScope and OpenLogger log file utility that can export to CSV (TODO: JSON). It's written in Python, but the important part (the log file parsing) is portable across about a dozen other languages. https://github.com/bdlow/dlog-utils-portable I've used a combination of the data structure definitions in the Digilent dlog-utils project, some information posted in this forum on the OpenScope data format, and the application of educated guesswork. IMHO this is an improvement over the current version of dlog-utils, which has various log file parameters hard-coded within even though these parameters are specified within the log file header. It's also more portable (Python 3), smaller and of course handles both log types. This work was made possible through the use of the awesome Kaitai Struct project to define the log file structure and automatically generate a Python parsing library from that. Kaitai handles all the details of the log formatting including endianness and data types, and presents the log via a very easy to use Python class. The web IDE makes it very easy to poke around the binary log file. Want to use something other than Python? All you need's the `.ksy` file and you're almost there for any of the languages that Kaitai supports: C++/STL, C#, Go, Java, JavaScript, Lua, Perl, PHP, Python and Ruby. I've a JSON exporting version almost ready, though I probably ought to add some tests first. @Digilent: can you expand on what the channel map is meant to represent? I had presumed it was the channel number to sample index mapping, e.g. if I recorded channels 2, 3 and 7 in the OpenLogger then I'd have expected the data to have three channels in each sample; and the channel map to look like [2, 3, 7, 0, ...]. However my OpenLogger generates log files with a channel map [1, 2, 3]. Bug?