Kristoff

Administrators
  • Content count

    109
  • Joined

  • Last visited

  • Days Won

    1

Kristoff last won the day on February 9

Kristoff had the most liked content!

1 Follower

About Kristoff

  • Rank
    Prolific Poster

Profile Information

  • Gender
    Male
  • Location
    Seattle, WA
  1. Just to be clear jpeyron's suggestion is for educational purposes. Digilent does not recommended or supported modifying the board in this way. Any modification to Digilent hardware will void the warranty and make the board ineligible for RMA. -Kristoff
  2. Hey, tsenneville was nice enough to do a remote debugging session with us over the weekend and we think we've narrowed down the issue. When WaveForms Live first connects to the Digilent Agent it sends an 'enumerateDevices' command. The Digilent Agent responds with a list of devices attached to the system (COM Ports). WaveForms Live waits for up to 5 seconds for a response. If WaveForms Live does not hear back from the Agent within 5 seconds WFL assumes the Agent is either not present or malfunctioning and alerts the user that it was not able to connect to the Digilent Agent. In tsenneville's case it looks like it was taking just over 5 seconds for the Digilent Agent to enumerate the device and build the response. arkuk, what make/model is your computer (or what CPU and how much RAM do you have)? We're going to build a new version of WaveForms Live that increases this timeout (and others) to see if this resolves the issue. We'll continue to post updates in this thread. -Kristoff
  3. For anyone that is interested here is Keith's analysis of the RMA'd board: ---------- Hi, I reviewed the returned OpenScope and there is indeed a hardware failure. On the DC output 2 opamp, the voltage at pin 5 on the MCP6H82 was measured at zero volts instead of the VREF1V5 1.5v. On the reference side of R100 there is indeed 1.5v, on the opamp side it is 0v. So either the input pin of the opamp internally shorted out due to a failure (most likely case), or the cap at C68 shorted to ground. I did not unload the cap to determine which as the circuit is clearly failing; but the opamp is providing a constant -1.0v no matter what the PWM signal is, so it is my very strong suspension that the opamp failed. During calibration to determine the coefficients of the DC circuit, the PWM circuit is run to generate an output of +3 to -3 volts and the difference measured. Since the output is putting out a constant -1v (actually -0.96v), the difference will be zero, and the coefficient for the PWM term will also be zero. Later, when the 2nd OSC channel is calibrated we use the calibrated DC output to set the input stimulus to the OSC channel (channel 2). To determine the appropriate PWM value to generate the requested voltage we need to divide by the DC output coefficient. Dividing by zero causes a coprocessor instruction fault and causes the MCU to reset itself; and thus why it looked like the processor browned out, it really didn’t but the effect is the same, the processor reset itself. This is an infant death condition on the opamp. This clearly passed during the manufacturing test as we calibrated and the calibration would have fail if this had occurred at the factory. Clearly the opamp failed shortly after it was released from manufacturing. The opamp itself has both good ESD and short circuit protection. It is unlikely the customer did anything to cause the failure. My conclusion is, nothing is at fault other than we got a bad opamp that failed shortly after manufacturing. I am please we replaced the board, and am confident this will not be an ongoing problem in production. Thanks KeithV
  4. Hey, I emailed some instructions. -Kristoff
  5. I talked to our manufacturing team and they said we may have shipped a few boards with 1.4.0 on them already. I was surprised to hear that. I agree that this should have 'just worked' and it does on most systems so I'm very curious to get to the bottom of this. Would you be willing to do a skype/google hangouts call with Dharsan and me so we can all walk through it together. Based on all the troubleshooting you've done so far it looks like everything is working. I'm not out of ideas yet, but seeing it in action would be most helpful at this point. Otherwise I can list some other things to try. Thanks! -Kristoff
  6. Hey, In the first log WaveForms Live is successfully connecting to the Agent and getting data from the OpenScope MZ. On line 156 we can see the enumeration response that indicates the firmware version is 1.4.0. How did you update the firmware to 1.4.0? -Kristoff
  7. Glad to hear that you got it to work on 1.6.9. When I built it it took around a minute on my Windows desktop (high end i7). Since we haven't tested in 1.8.3 those errors in don't surprise me. This is why we recommend 1.6.9. -Kristoff
  8. You shouldn't need to move any files. I just downloaded the repo as a .zip, extracted it to a folder called OpenScope, opened the OpenScope.ino inside and built it with no issues. Did you install the Digilent core from Arduino 1.6.9 or 1.8.3? You should do everything from 1.6.9. -Kristoff
  9. The OpenScope MZ is not supported in WaveForms 2015 and won't show up in the devices list. I created a debug build of the Digilent Agent. Download the debug build of the Digilent Agent here. Extract it to your desktop. Start a command prompt. Navigate to the folder on your desktop containing the debug digilent-agent.exe Run the following command to start the digilent agent: digilent-agent.exe > logfile.txt 2>&1 If prompted to allow network access, check both boxes and click allow. Launch WaveForms Live. Attempt to add the Digilent Agent. Return to the command prompt and press Ctrl+c to kill the agent. The folder containing digilent-agent.exe should now have a logfile.txt. Please post that file here. Let us know if you have any questions. Thanks! -Kristoff
  10. I posted an updated mac build here. -Kristoff
  11. Glad to hear that worked. Let us know if you have any other questions as you get started. Thanks! -Kristoff
  12. Hey Jasper, Glad to hear that the new board is working, and thanks for sending the old one back. We're eager to see what went wrong on the first board. Let us know if you have any questions as you get started. Thanks! -Kristoff
  13. Hey, We've been going back and forth with Apple on getting this release of the Digilent Agent in the App store but it's starting to look like that may not work for this release. Stay tuned. -Kristoff
  14. Ok good. That shows that WFL is communicating with the Digilent Agent and we got the expected status code back. My best guess at this point is that the Agent is not able to access the COM ports (maybe due to lack of permissions?) I'll need to build a debug version of the Digilent Agent for you on Monday, but until then can you close the digilent agent and then right click the Digilent Agent exe and choose Run as Administrator. Then try adding the Agent to WaveForms live and see if it still times out. Thanks! -Kristoff
  15. Hey, You can use the BNC Adapter for Analog Discovery with OpenScope MZ to use BNC Probes. Since OpenScope MZ only has one WaveGen the second WaveGen connector will not be connected. WaveForms Live does not currently support multipliers or probe calibration but it is something we could add in the future if enough people find it useful. -Kristoff