Jump to content

Julien

Members
  • Posts

    10
  • Joined

  • Last visited

Julien's Achievements

Member

Member (2/4)

0

Reputation

  1. Hi, I've mixed up all my USB cables and am wondering which one came with the Analog Discovery 2. Could you confirm if this is the one that has the following markings on it: "USB shielded high speed cable 2.0 revision E343712 9J AWM 2725 28AWG/1PR and 24AWG/2C 80ÂșC 30V VW-1 DHE". Thank you, Julien
  2. Hi, I've noticed that there is no "Trigger" label in the scope UI next to the "None/Auto/Normal" dropdown box (see screenshot). Is that intentional? I'm new to this software and was a bit confused at first as I wasn't sure what that box was for. I figured it out after reading the documentation, but having a label next to it would have been much more intuitive. Or maybe am I missing something? Thanks, Julien
  3. An update: I managed to get it to work by using the settings in the attached screenshot.
  4. It's possible that I might have failed to connect to ground, I'm not sure. I'll report back if I run into the issue again. Thanks.
  5. FWIW, the protocol analyzer seems to work in Spy mode (see attached screenshot below). It'd be great to figure out the right settings to get the same thing in the logic analyzer. Let me know if you have some tips on how to achieve that. Thanks!
  6. Thanks @attila for your response. What would be the appropriate way to increase the sampling? I've selected the "Record" mode and added a I2C trigger on Start. It looks like that increased the sampling to 100kHz. However, I've still mostly seeing Start and Error events (see screenshot). I'm new to logic analyzers in general, so I'm most certainly not using it properly :) Any tips would be helpful.
  7. Hi, I'm getting started with the logic analyzer. I've got a circuit that uses I2C and is controlled by a Pico microcontroller programmed in Python. The circuit itself works well but the logic analyzer returns almost exclusively "error", "start", "ack", and "h00" events. I cannot seem to see in the logic analyzer any of the actual data sent over the I2C bus. I've tried reducing the frequency to 100kHz or 50kHz in the microcontroller's program, but the info returned in the logic analyzer still seem like garbage (unless I'm reading it wrong...). Do you have some tips on how I could troubleshoot this? Thanks! Julien
  8. Another update: I just tried the fly wires again and the curve is now sharp and clean as well like in the second post. I can't seem to reproduce the issue I saw in the original post. So I'm a bit puzzled. If you have some clues on what might have gone wrong in that first post/screenshot, let me know.
  9. Actually, I just tried with the BNC adapter and BNC probe, and the curve is now much more precise. See attached new screenshot. In my original post I was using the fly wires. Is that to kind of amplitude of measurements to be expected with fly wires?
  10. Hi, I'm new to the Analog Discovery 2 and new to oscilloscopes in general as well. I'm going through this tutorial, which shows a capacitor charging up to 9V then slowly discharging down to 0V: https://www.instructables.com/Using-the-Oscilloscope-With-the-Analog-Discovery-2/ When I run the scope scan, I see that the voltage oscillates between roughly 8.5V-10.8V when the circuit is turned on (see attached screenshot). That seems like a pretty wide amplitude and instead I would have expected the curve to be much closer to 9V. The power supply is set at 9V, and my DMM measures exactly 9V while the circuit is closed. Am I missing something? Thank you, Julien
×
×
  • Create New...