Search the Community

Showing results for tags 'openscope'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • News
    • New Users Introduction
    • Announcements
  • Digilent Technical Forums
    • FPGA
    • Digilent Microcontroller Boards
    • Non-Digilent Microcontrollers
    • Add-on Boards
    • Scopes & Instruments and the WaveForms software
    • LabVIEW
    • FRC
    • Other
  • General Discussion
    • Project Vault
    • Learn
    • Suggestions & Feedback
    • Buy, Sell, Trade
    • Sales Questions
    • Off Topic
    • Educators
    • Technical Based Off-Topic Discussions

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


AIM


MSN


Website URL


ICQ


Yahoo


Jabber


Skype


Location


Interests

Found 25 results

  1. 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
  2. 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. Should
  3. 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 ev
  4. Hi, after setting up my OpenScope initially, it connected successfully to my home wireless lan and I could access it from the tablet or browser as expected. Then, I disconnected the scope from power and tried to run in on a power bank. The blue light wouldn' stop blinking, so no connection to Wifi anymore. I re-attached to the computer assuming the power bank had not enough power, but also there the scope wouldn't re-connect to Wifi. I checked my Fritz!Box if the channel had changed to something above channel 11, but it is a safe channel 1. Any idea what may have happened h
  5. I need to read some data (a serialnumber to be specific) out of an eeprom. The eeprom I am using supports I2C. in additon to that I'm accessing the openscope mz via json-strings. So I got some questions/problems. Does the openscope mz support i2c? if yes how to I access this with json-commands If it doesn't support i2c I would use an bus-bridge (something like this) to convert it to spi. On the reference website it says the boards supports spi. But I can't find any solution on how to connect to this pins via http. Has anybody some information or recommended websites where I can look
  6. I'm experience a similar problem. In my case I have to use the Digilent Agent to connect and manually setup wifi every time I power up the Open Scope (I get blinking blue light only); some times my network appears in the saved network list and other times it doesn't. I'm on firmware 1.296.
  7. Hi, using the instrumentation protocol I was able to issue a "read command" to the Oscilloscope and receive the following message. 113 {"osc":{"1":[{"command":"read","statusCode":0,"binaryOffset":0,"binaryLength":4876,"acqCount":220,"actualSampleFreq":24381324,"pointOfInterest":2062,"triggerIndex":0,"triggerDelay":84572929674,"actualTriggerDelay":84572929674,"actualVOffset":43,"actualGain":0.25,"wait":0}]}} 130C 66AA8;;68>8>DD>;;;>A;A>;G;>8;;6>6A;6;3DD;;8GAA8;;>>AD;D;8>A;86G;DA3;8>8;>ADA>;GG;AA;8;8>A3A>G68A>>>8>6686>D;;>A;
  8. What is the max input voltage that the Openscope mz can tolerate on the logic analyzer pins. What about the GPIO pins? In the documentation I noted the Oscilloscope has +/-20V measurement range and +/-40V tolerated range (in some forum). But for the logic analyzer I see only a specific mention of 3.3V. I want to be sure before I connect the logic analyzer to either 5V (some Arduino's) devices or 12V devices (e.g. old DSC832 home security board). Reviewing the PIC32 datasheet, and assuming I am correctly interpreting the Openscope reference manual, I can guess that the DIO[0-9] pins are 5V
  9. 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.
  10. Dear Team of Digilent. I am currently working with an MZ OpenScope with the Arduino IDE. I was able to load the Blink program on the shield. But now I am limited, because of the OpenScope.h file I only found some pin declared. // some gpio pins #define PIN_SD_DET PORTD, (1 << 1) // RD1, pin 36 #define PIN_INT_MRF PORTG, (1 << 8) // RG8, pin 59 #define PIN_HIB_MRF LATD, (1 << 13) // RD13, pin 60 #define PIN_RST_MRF LATA, (1 << 4) // RA4, pin 61 #define PIN_WP_MRF LATA, (1 << 14) // RA14, pin 62 #define PIN_LED_1 LATJ, (1 <&l
  11. I recently purchased the OpenScope MZ. I've already reviewed the brief spec sheet but I still have some questions: 1. What are the power requirements of the board? I'm going to be designing a PCB that powers it and I need to know 2. Where can I get a full schematic of the board? 3. Is there a way to get the board to automatically configure itself into a specific wifi network upon startup? I'm trying to get it working on a mobile battery powered system and that functionality would greatly affect my and my company's future use of the product Cheers, Jim
  12. Well, a belated callout for the inclusion of the CyberMonday Openscope-BNC adapter offer. I am about to pay for the OpenScope education version. Can I get the BNC adapter included for free? 😇 BTW, if that doesn’t work, who/where can I contact to purchase/include a BNC adapter with my OpenScope purchase? Thanks! Mike
  13. I'm not able to update firmware from 1.4.0 to 1.296.0. I'm running Waveforms Live Version 1.3.0 on Safari, Chrome, ... macOS 10.13.1 Am I alone ? Any idea ? Jérôme
  14. A few more info about the Learning Edition would be nice. What exactly is everything contained? Is the housing included?
  15. In short, we rely heavily upon the Analog Discovery units in the lab and have grown to rely upon the scripting features that enable triggered signal averaging and custom signal processing. Is there a mechnism or plan to enable a similar set of features with the OpenScopeMZ. As a stand alone, simple scope the system works well but without the ablity to script its potential seems stunted. Ideas? Thoughts? Timeline?
  16. I can see the USB see the device and it mounts it to ttyUSB0 and then when I open digilent-agent it gives me Launch waveform live and exit as actions its willing to give me access too, Active device and version are both greyed out. I even installed the older version of the agent and checked (to get the same outcome) and then upgraded over that and it still does the same. I dont see many topics here about issues in linux so I think I might be an outlier on this. I currently run ParrotOS (debian fork) but I also spun up a Debian 8 and 7 install and both have the same outcome. Any guidance ? And
  17. I finally got around to using my OpenScope for the first time. I've installed the Diligent agent and have gone through updating the firmware and calibrating. I am able to take measurements and everything appears fine. So, I decided to try the Wi-Fi. I configured it for my network and when I power it with a USB wall charger, it appears to connect and gets an IP address on my network. LED #4 (blue) is lit solid. LED #3 (green) is blinking about once a second, and LED #2 (orange) is blinking about once every 5 seconds. When I open a browser and go to that IP address (192.168.0.15), the browser is
  18. Hi there. I was wondering if the STL or say Fusion 3D (for example) files for the OpenScope MZ were posted publicly somewhere. Would love to save time and just print one out if possible.
  19. Will be it able to interface to Sigrok in the near future? https://sigrok.org/wiki/Supported_hardware
  20. Hello! I'm excited to announce that Digilent has our first Kickstarter project for the OpenScope! I won't be able to give the project proper justice in describing the OpenScope and WaveForms Live, so I encourage you to check out the Kickstarter to learn more about the mission of the project. With regards to this sub forum, Digilent would like this to be a place where backers of the Kickstarter are able to ask questions and provide feedback for both the OpenScope and the browser based WaveForms Live. As such, we kindly request that only backers of the project ask questions related to
  21. Hi there, In the Kickstarter campaign it's said that the OpenScope will be "open source". Could someone from Digilent specify the licenses that the various files will be released under? In particular, the licenses for the hardware design files, the device firmware, and the Waveforms Live software? Also, will the hardware design files consist of rendered schematics only or the actual EDA design files? Thanks, Bob
  22. How to hack digital input from 3V3 to 5V? Would voltage divider be enough? Are some of the digital input (used as logic analysizer input) can be used as analog input (but limited to 3v3)? If so, is there any way to utilize "5 dedicated 3.125MHz 12-bit ADCs" for oscilloscope functions? I believe you might be using 2pcs LMV116 as your 2ch analog input and eventually goes to the MCU, how to hack and add 2 more of these op-amp to become 4ch scope in-case if some of the digital input can be used as ADC. I could Add those extrenally. You said two interleaved ADC are used for one cha
  23. I find it both amusing and inspiring how quickly the Kickstarter got funded in just a few hours! Alas, where do you plan on going from here? What sorts of stretch-goals will there be, if any? I would imagine you won't be upgrading the hardware, so as not to cannibalize the market from your other products, but what else is there? Improvements to the software? Nah, those will happen eventually anyway, not a good stretch-goal. Stickers with Digilent-logo or something, like certain companies did with their Kickstarter stretch-goals? Meh, I'd rather like to see something actually useful.
  24. I know that the scope functionality supports two 12bit channels @2 MHz (6.25 MSample/sec) bandwidth, but couldn't find any reference of what's the max input voltage. Nevertheless, great project and I'm happy to back it.