Technical Forum Moderator
  • Content Count

  • Joined

  • Last visited

Everything posted by AndrewHolzer

  1. The summary isn't quite correct. A change in Chrome security policies is preventing the browser from communicating with the Agent when accessing the live version of the site. Using the locally hosted version of the website skirts around these updated security policies, but required updating the static assets served by the local server to a version that supports OpenLogger. Using a different browser (such as Firefox) will allow use of the live version of the site, provided it isn't using the same browser engine as Chrome. AndrewHolzer
  2. Hi Martin, It looks like some changes have occurred in the Chrome browser and others based on it that is breaking some things. You can correct it by going to the chrome://flags page, and setting the 'Block insecure private network requests' to Disabled. This flag is preventing requests made to localhost from sites available on an external IP address, ie Continuing to visit the http://localhost:42135 address will also work and has the same functionality of, if setting a configuration flag in your browser isn't something you want to do. I have noticed that
  3. Hi @MA00, I dug out my OpenLogger and had a look myself but found that everything was working fine. Can you enable logging in WFL and open the browser developer tools, then try to connect. There should be some output that appears in the console, and I would appreciate it if you could share a screenshot or text dump if it with me. You might also try running the agent as an administrator and see if that provides any results. Regards, AndrewHolzer
  4. Hi @Anatha Vidhya, I am sorry to say that we don't have that information for the JTAG-SMT2, and have no plans to procure it. Regards, AndrewHolzer
  5. Hello @ailee, According to this application note, the two can be used interchangeably. The note also details any differences between the two devices and their datasheets. Regards, AndrewHolzer
  6. Hello @rappysaha, You will need to have licenses for the HDMI TX Subsystem, HDMI RX Subsystem and the VPHY controller. You may request an evaluation license or purchase one here. Regards, AndrewHolzer
  7. Hey David, The Digital Discovery doesn't Slave mode, meaning it won't be able to send the ACK bit. Regards, AndrewHolzer
  8. Hey @reddish, This is really cool and I know a few people who would love to see this! Thank you for sharing this demo with us!
  9. Hello @mikew, The 240-021-6 will work as a replacement for 240-035. It is only missing the right-angle header. Regards, AndrewHolzer
  10. Hi @Tylor, As far as my understanding goes there isn't a 2019.4 version. Xilinx transitioned to releasing 2 versions per year in 2019 and the last 2019 version released was 2019.2. Regards, AndrewHolzer
  11. Hello @Gumesh, I looked into it a bit to see what I could come up with, but since we haven't used the ov9821 in our products this is as much support we can provide. The ov9821 supports different image resolution, color support, and active array sizes, among other differences in specifications vs the ov5640. As such, both the drivers and the IP iself would need to be adjusted to account for these different specifications and any changes in register sizes on the ov9821. Hopefully one of our amazing community members has some experience with that product and can help you out.
  12. Hello @CurtisNotestine, What version of Vivado are you using? Xilinx no longer includes, and has no plans for replacing the Ethernet PHY MII to Reduced MII (MII2RMII) in versions 2019.2 or later. The current work around is to obtain a copy of the IP provided in Vivado 2019.1 or earlier. You can include it in 2019.2 onwards by including it like you would a regular IP repository. This thread has all that information. Best regards, AndrewHolzer
  13. Hi @DavidLee1997, I am letting you know that I've seen your question and I am working on finding you an answer. Keep an eye out for a response! Thank you for your patience, AndrewHolzer
  14. Hello @tkuraku, I'm taking a look at getting you some kind of directionality so you can recreate that magic. I'll let you know what steps to take as soon as I have them myself. Thank you for your patience, AndrewHolzer
  15. Hi @rappysaha, I just wanted to let you know that I am looking at what our support plans are for the Genesys 5EV, and that I am waiting for some questions I had to get answered. I'll relay that information to you as soon as I get it myself. Thank you, AndrewHolzer
  16. For those coming to this thread at a later date, looking for a solution to the "busy" Trigger state: In short the "busy" state is a catchall for any Trigger state that isn't Idle, Stopped, Triggered, Running or Armed. In the case of the Trigger, it is usually busy due to being in a Waiting state but can be other states as defined in the OPEN_SCOPE_STATES enumeration in OpenScope.h of the firmware source (starting at line 476). The solution here is to wait for the Trigger to leave that "busy" state by continuing to send the Trigger getCurrentState commands. I suggest that an easement algor
  17. Hi @Raghunathan, I took a look into the WPA/WPA2 issue you've been having. In short, the WINC1500 driver doesn't distinguish between WPA & WPA2 from the perspective of the software, in happens internally on the chip. The OpenLogger reports back to WaveForms Live what the WINC1500 is telling it during a WiFi AP scan, which is that a WPA/WPA2 network is just a WPA network. I'm glad to hear that switching to WPA got you to the saving stage, but I urge you to go back to WPA2 instead. You are increasing the vulnerability of your local network. Instead, can you please send a capture of
  18. Hi @orquesea, There are a few things going on that I will try to explain to you, that I hope will help you get things working properly and perhaps impart some info on how WaveForms Live is working. WaveForms-Live calculates the expected acquisition time based off the buffer size and the sampling frequency. After clicking Start, WaveForms-Live waits for this period of time to pass before querying the OpenScope for available data. WaveForms-Live also calculates the sampling frequency from the time per division value in order to fit the entire acquired signal on the chart by default. If we
  19. Hi @Raghunathan, Is it possible for you to send a capture of the browser console log when you are trying to log to the SD card and get the "Error Starting or Running" message? There should be some more technical information in there that should help in debugging your issues.
  20. You will have to redo the calibration every time you program the OpenScope with the Arduino tools. It isn't preserved through the process. You can possibly re-implement the firmware upgrade flow in WFL, which will allow you to preserve the calibration settings that have been saved in flash. Otherwise you can save to an SD card as well. We intended that user calibration exist on the SD card and manufacturing calibration be kept in flash, but both can be overwritten by the user, anyways.
  21. Hi @Ravi Kumar, Thank you for supplying these log outputs as they've proved helpful in finding a solution that should work for you. I took a look through the source code and found that the OpenScope will attempt to save the calibration configuration to the SD card when using the terminal UI, which fails if you don't supply an SD card . I confirmed that I received the save error as you have demonstrated and after a small change that I'll describe to you I saw the error disappear. If you look at line 811 inside IO.cpp, you will see a call being made to CFGSaveCalibration . You can configu
  22. Hi @Ravi Kumar, I am going to need some more information from you. What version of the Digilent Agent are you running? Can you connect from your PC to the OpenScope using a terminal application (puTTY, TeraTerm, etc.) and see what the output is booting your compiled firmware, and share the results? How recent was the last time that you synced your copy of the firmware source with the Digilent repo (in case you've had it a while)? Can you enable the console logs, and see the output in your browser's developer tools when you try to calibrate your device? I am curious to see what error code yo
  23. Hi @Ravi Kumar, I am going to need more information from you in order to proceed with this issue. I haven't been able to replicate your issue unfortunately; I've made a few additions to the OpenScope source, built and flashed the device and can trigger the scope instrument. Can you tell me what Arduino version you are running? Have you made any changes to the OpenScope source code? After uploading your custom firmware, have you calibrated your OpenScope? Your answers to these questions should form a foundation from which we can build an understanding of the issue you are experiencing.
  24. Hi @frokostfredag, That's some odd behavior that you're describing there. There is one thing I'd like you to try to debug this, and that's to enable the console output in WaveForms Live before trying to connect to the device. I'm hoping that this lets us see what command is causing the OpenScope to choke. You can do this by going into the Settings page, opening the Advanced section and clicking on Change Console Log. Set this to Console, then open the developer tools for your browser. For Chrome and Firefox this is Ctrl+Shft+i. The commands and their responses, plus some other additional in