Kristoff

Administrators
  • Content count

    127
  • Joined

  • Last visited

  • Days Won

    1

Kristoff last won the day on February 9

Kristoff had the most liked content!

1 Follower

About Kristoff

Profile Information

  • Gender
    Male
  • Location
    Seattle, WA
  1. Hey Joor and Bob, At the end of the day we want OpenScope MZ to be a great tool for teaching and learning. We felt that posting the schematics, communication protocol, firmware source code and app software source code provided the vast majority of the benefit of being open to our customers. Posting gerbers or design files seemed like it would not be very useful to most OpenScope MZ users and slightly increases the risk of straight up clones that add no value on top of the original design. We have the 'what is open source' discussion regularly at Digilent and I welcome any feedback you all have on this topic. -Kristoff
  2. Hey DwayneR, You will need to setup a Wifi network for the OpenScope MZ to connect to. Depending on your phone you may be able to enable a wifi hotspot on the phone and have the OpenScope MZ connect to that network. If your phone does not support that you may need to add a wifi router to provide the network. Let us know if you have any questions about this. Thanks! -Kristoff
  3. PCB Update Changes

    Hey faultylee, The changes were all 'nice-to-have' improvements and we do not recommend trying to modify your Rev F. I created a change log on our wiki here. Let us know if you have any questions about any of this. Thanks! -Kristoff
  4. Hey Joor, We posted the schematics as PDFs here, but we have not published eagle files. -Kristoff
  5. Agent dosent recognize Scope

    Hey HorreC, 'Version' will always be grayed out since it is just designed to indicate the version number, not be interactive. 'Active Device' should be grayed out until a device has been selected in WaveForms Live. You should be able to follow the instructions here to use WaveForms Live to select the OpenScope MZ as the active device and get data. Let us know if you have any questions about this. Thanks! -Kristoff
  6. Retry Enumeration

    Can you confirm that COM3 is assigned to the OpenScope MZ. The easiest way to do that is: Unplug the OpenScope MZ. Open Windows Device Manager Expand the Ports Section. Make note of the ports listed. Attach the OpenScope MZ. Make note of the new port added. Let us know what you find in device manager. Can you also share the state of the LEDS when the OpenScope MZ is plugged in. Are any solid on? Are any blinking? Thanks! -Kristoff
  7. Retry Enumeration

    It looks like the Digilent Agent is able to open the COM port but when WaveForms Live tries to enumerate the device that is failing. Is this OpenScope MZ new out of the box or have you used it before? Thanks! -Kristoff
  8. Retry Enumeration

    Hey, It sounds like you were able to add the Digilent Agent to WaveForms live, it detected your OpenScope MZ as COM 3 and your device shows up on the WaveForms Live device manager (the main page) like the image below. Is that correct? Does the error show up when you click the device card shown below? Thanks! -Kristoff
  9. Licenses

    Hey Bob, We feel like the schematics are the most useful part for the majority of users so the plan is to release schematics but not the design files. -Kristoff
  10. Open Scope Inquiries

    Hey Victagayun, I suggest using a level shifter if you need to go form 5v to 3.3v. For example the PmodLVLSHFT would work. The digital inputs cannot be used as Analog Inputs. The ADC channels are interleaved to get better resolution on the Osc channels. There is no simple way to extend the device to 4 Osc channels. Our default firmware uses virtually all of the hardware resources on the MZ to achieve the shipping features set. In addition to the pin availability you have consider things like timers, ISRs, peripheral mapping, DMAs, etc. The Logic Analyzer pins can be used as GPIO. You could modify the firmware and bitbang some protocols on these pins but it would likely get interrupt by or interfere with the default device operation. Let us know if you have more questions. Thanks! -Kristoff
  11. Licenses

    Hey Bob, All of the software will use the MIT license except the Digilent Agent which is built using Qt and requires a GPL license. I'll have to confirm but I think the plan is to release hardware schematics (probably not design files) under MIT license as well. -Kristoff
  12. Hey Beleg, OpenScope uses the ADCs on the PIC32MZ which can be oversampled to provide increased resolution. Right now we're trying to stay focused on the 'general instrumentation' use case and our idea of logging will be pretty simple to start (just grab some point on demand and log them to a file, db, or similar). That being said we're already kicking around ideas for ways to get more channels at higher resolutions and we'd love to see some community firmware modifications that head in this direction. Feedback like this will help us determine what exactly we mean by 'more channels' and 'higher resolution' . Thanks! -Kristoff
  13. The sample rate and number of samples acquired is determined by the time/div settings. For example if your time/div is set to 1 ms then your 'view' is 10 ms wide. We acquire for time equal to twice your 'view' so we'd acquire for 20ms. The sample rate is set to acquire about 1 point per pixel on your screen. This means we don't have to decimate the data in the browser and as you zoom in you sample faster. The OpenScope is designed for fast buffer acquisitions, not streaming. The best way to log data over a long period of time would be to use the host (PC) side library (we will provide a TypeScript library) to acquire data and log it to a file / database / etc. You could also create custom firmware to do this. The tutorial mode is very much a work in progress at this point. There are some difference between the simulated device and a real device here. On the simulated device the trigger is always centered in the buffer. This is not the case on a real OpenScope. When you pan left / right in your 'view' you are setting a trigger delay. The end result is that you can pan off to one side, sample again and your 'view' will be centered at the same point relative to the trigger. There is an auto scale button on the right side of the chart that will center and scale the buffer to fit in your 'view' We plan to add support for AD2. If it works well and there is enough interest we'll consider EE as well. For DIO you can configure them as Input, Output, or Analyzer. Analyzer channels will be graphed, output you can click to toggle high/low, input will display their values when you click refresh. We'll have a tutorial mode for this eventually. Can you elaborate on why you want the math menu left open? If you have the math menu open (or any other 'pop-over' menu) the first click outside the menu will close the menu and will not activate the button. The second click would actually refresh the value in that case, not the first. The last 5 mins do not have shorthand names at the moment. We generally refer to them by their funciton or 26, 27, 28, 29 and 30. We have a lot of internal debugging code that we turn off by default to improve performance. The console log button lets you choose to re-enable this and decide where the output should be routed. This will enable users to send us their debug logs so we can help track down bugs. This will be more obvious in the release version. -Kristoff
  14. Scope max. input voltage

    That's correct, the Scope inputs function to ± 20v and are protected to ± 40v. Let us know if you have any more questions. Thanks! -Kristoff
  15. Hey, It sounds like you are likely missing NI VISA (the Serial driver for LabVIEW). You can download and install NI-VISA from this page. Let us know if that helps or if you have any more questions. Thanks! -Kristoff