Technical Forum Moderator
  • Content Count

  • Joined

  • Last visited

  • Days Won


Everything posted by AndrewHolzer

  1. Apologies for the delay @Raghunathan. Can you please take a look at the task manager and check to see if there are multiple versions of the Agent running? Even if you don't, I suggest that you use the task manager to kill any running Agent processes, then make sure that you start the latest version only, then try connecting. As another test to see if your browser can hit the agent, if you visit http://localhost:42135/debug in your browser, with airplane mode off, you should see a page that says "Debug Controller Page...". If you get the chance to hit a WIN8.1 machine from your WIN10 machine, I'd like to see the results of that test as well, but no worries if this can't be done. AndrewHolzer
  2. Hi @benl, At the moment you can't use WFL to view the logged data. There are some challenges that surround this and we are working on finding a solution that best solves these problems. The dlog utility has yet to be updated to parse the OpenLogger .log files, as they have a different binary format from the OpenScope. If you are eager and have the capabilities to do so, we can provide you the .log header struct so that you can make your own parser. Otherwise, we'll be working on updating the dlog utility, and will let you know as soon as that has been done. Regards, AndrewHolzer
  3. @Raghunathan, Let's try a few more things here. First, can you remove the OpenLogger you have added there, and try adding it again while still on the network? What I'd like you to do differently is replace localhost with when you are at the step where WFL requests the URL for the Agent. Are you running any anti-virus software on your machine? I don't expect it to be causing you any issue (and see no reason why turning on Airplane mode would affect it) but it's still a possibility. If you are running anti-virus, turn it off for a moment and try adding the device again. Another thing to try is to connect the OpenLogger to your WIN8.1 machine and run the Agent there, but use WFL on your WIN10 machine. When you go to add the Agent, replace localhost with the IP address of your WIN8.1 machine. Even if this works its still not an ideal setup. I'm asking you to try this so that I can get a better feel as to what the real issue is here. If you try all that and it still doesn't work, then I'd like you to try a new build of the Agent. You can download that here. Let me know what your results are. I will continue to research this issue and get to the bottom of it all. I personally appreciate your patience as we work through this issue, AndrewHolzer
  4. Hey @Raghunathan, Thank you for the screenshot here. What I am gathering from this image and your previous posts is that you are possibly running into a network priority issue. There are several things we can do here to see if this is truly the case. A network priority issue may arise when you are connected to multiple networks, say over ethernet and WiFi, or when you are running VPN software. When your machine sends data over the network, it needs to decide which interface it uses first, and this priority is usually established within the OS. So, first: Is your WIN10 machine connected to multiple networks and/or is it running any VPN software? If this is the case, then you may need to reorder the priority within Windows to fix the issue. This guide shows you how to change the interface metric which will affect the interface priority level. If you've tried the above solution to no avail, or it doesn't apply to you then we'll try something else. WFL normally uses the localhost address on port 42135 to communicate with the agent, and I'd like you to try and see if we can use localhost at all. So, secondly, I want you to open your CMD prompt, and enter ping localhost. You should see some output saying 'Pinging <machine-name> with 32 bytes of data' followed by several replies. If you don't see any of those replies then something is blocking you from localhost. If you are blocked from localhost, when connecting to the agent you can replace where it says localhost with This is the IPv4 address of localhost, and WFL should work as if you had localhost and if your problem doesn't persist. If these steps don't fix your issue then there is something else that is giving you trouble. In that case, we'll continue to dig further and see what we can come up with. Let me know if you are running any VPN software or are connected to multiple networks, as well as whether the ping localhost works for you or if using works as well. Regards, AndrewHolzer
  5. I'm glad to hear that you've made some progress, Raghunathan, and I greatly appreciate your patience. Nothing about your system tells me it would be interfering with the agent, so I need you to do some more digging for me. I'd like to see what the console output is when you try to add your OpenLogger. Before doing anything, visit the Settings page, and click Advanced. Click the Change Console Log button, and choose Console. Once you've done so, press Ctrl+Shift+i to open the Chrome Developer Tools, and make sure the Console tab is active. Run through adding the device until it fails again. You should see a bit more detailed information as to why it is failing in the Chrome Developer console. If you can share that with me as a screenshot or some other way, I would appreciate it. About the profile: You shouldn't have to select the last saved profile when launching WaveForms Live. Ideally WaveForms Live recognizes what profile your device has assigned to it and will load it up, but that doesn't seem to be working. If you could also give me the console output after entering the logger page (when WFL checks the device profile) and share that, we should get to the bottom of this issue as well. Thank you for your cooperation and patience, AndrewHolzer
  6. Hi @Raghunathan, Can you share information in regards to your WIN10 machine, such as hardware spec, OS patch versions, etc? I run WIN10 myself and have been successful in working with the OpenLogger and WaveForms Live in this environment. There's another factor at play that is causing the malfunction you are seeing, and I'd like us to get to the bottom of the issue. Can you also check to see what the version your local copy of WaveForms Live is? If you visit the settings panel, in the bottom left of the page you'll see WaveForms Live <version #>. It is possible that your local copy is an older version of WaveForms Live that doesn't support the OpenLogger. If it is an older version, you can visit the WaveForms Live wiki and download the offline build (this link will download the latest build). Then, once you've got that downloaded, you need to extract that zip to where the Agent will serve the files from, located at C:\Users\<username>\AppData\Local\Digilent\Digilent Agent\www. If you visit the address, check the version again. If it looks like the page hasn't updated, you should do a hard refresh, as your browser probably cached the old files. This can be done with a Ctrl+Shift+R. Let me know how that works out, and what your WIN10 machine info are. AndrewHolzer
  7. Hi @Raghunathan, Here is a link to the 0.1719.0 hex file. I've also gone ahead and updated that link on resource page. I missed that last time I posted new firmware, and I apologize for the inconveniences that that has caused you. AndrewHolzer
  8. Hi @mltma, At this moment SD card logging is not supported. You can expect an update that supports it within the week. We are working hard bring this feature to you all, and we greatly appreciate your patience while we work. I can message you here once we've posted the update if you prefer. As for the SD card, it needs to be formatted to a FAT32 file system. If your SD card is formatted correctly, great! You don't need to do anything more. Otherwise you can use your system's tools to properly format the SD card, and once SD logging is supported in WFL you'll be good to go! Regards, AndrewHolzer
  9. Hi @sgrobler, 1. Can you tell me what you are trying to accomplish here? I don't think I understand what you'd like to happen, but I'll try to explain why it is the way it is: We have the concept of units of measurement and prefix, units being things such as voltage, pascal, ampere, etc and prefixes as milli, micro, Mega, etc. The OpenLogger only measures voltages and passes these voltage samples back to WFL which draws the data on the chart. The sensor that your OpenLogger is sampling takes real life analog signals and converts them to a voltage, but you and I would think of that voltage as representing those signals, ie pascals if you're measuring pressure. The scaling popover takes care of translating the voltage output of the OpenLogger to whatever unit of measurement makes sense for the signal you are measuring. The scaling of the unit value happens based on what you want to see in the chart, which can be changed by shift+scrolling in the chart or setting the Volts/ input. 2. Profiles are saved within the flash storage of the OpenLogger. When WFL connects to the device it will query it for any profiles it may have. If you check the file explorer in the logger page, you can expand the Flash section and see each profile saved to your device. Saved scaling equations on the other hand are saved to localstorage in your browser. What browser are you using? I will also mention that in order for these settings to be applied and saved you must click their respective save buttons. If you are doing that but nothing is being saved then there is a bigger issue that I can help you debug. Regards, AndrewHolzer
  10. I am very glad to hear that you got things working John! I hope that you enjoy your new OpenLogger! Feel free to start another post on the forums or shoot me a personal message if you encounter any further issues. I'd be more than happy to help you out. Regards, Andrew
  11. @Scooby, It doesn't seem like your board is bricked and can still be recovered. I want you to try the recovery process one more time. Before you do, exit the Agent in the task bar and check to Task Manager to be sure the process has exited. Once it has, spin up a new instance of the Digilent Agent before proceeding. If you are able, try running through the process on a different computer, so that we can be sure that the real issue isn't with what you're currently using. At this point, check the Device Manager, and underneath Ports you should see which COM port the OpenLogger is on. When you get to step 6, select this COM port instead of the Digilent OpenLogger MZ entry. I also ran through the recovery sequence myself once more, and found that clicking Open while the OpenLogger is in bootloader mode will show the 'Unable to Communicate with Device' popup message, but you can proceed to the next step and click Load Firmware. When you do so, the selected device will be Other, and you'll need to upload the firmware hex yourself. If you visit this link you'll download the latest OpenLogger firmware. Click Browse, navigate to where the hex file was downloaded and select it. Status should say 'Ready to upload "OpenLoggerMZ-0.1619.0.hex". File size is 1892510 bytes". Once you are good and ready, click Flash Selected Firmware and the flashing process should begin. Let me know if this works for you. I also want to thank you for your patience while we work through this issue together. I certainly appreciate it. AndrewHolzer
  12. @Scooby, Did you see LD6 flashing as you typed into the terminal?
  13. Hi @victagayun, When your OpenScope starts initializing the WiFi state, it is reporting a WiFiNoNetworksFound error. Even though you've asked it to save the credentials, the auto connect may happen to fail for several reasons. When a connection attempt fails, the OpenScope only knows that it's disassociated based on the response it gets back from the radio and doesn't retry. One cause of failure may be due to the signal. On a network with many connected devices the routers are increasingly busy and can't service all the traffic. If the OpenScope were on such a network, it may fail to connect to the access point. If possible, try connecting to a network with less traffic, or a stronger signal. Another possibility is that the credentials you've entered are wrong. Because the OpenScope only knows it is disassociated when it fails to connect, it cannot recognize that a connection attempt failed because of incorrect credentials and not because the network is busy. If you double (triple) check the passphrase you used, you should first delete the connection entry from the OpenScope, then proceed to entering the credentials anew.
  14. @Scooby, When you say boot mode I take it you mean bootloader mode? You won't see any output over the serial terminal when you enter bootloader mode. You should connect your open logger up to your computer and establish a terminal session. The first image I've included has the settings I use in PuTTY. Once you've established a session, press just the reset button (P32 RST). After the OpenLogger powers on and initializes itself, you should see some text similar to whats in the second image I've attached. If you don't see any output, try mashing some keys and observe LD6 on the OpenLogger. It should be flashing as you type. Let me know how this turns out.
  15. Hi @dklann, At this moment the OpenLogger is only supported on Windows. Some effort needs to be put into getting the Agent working on Mac & Linux. @Scooby, Is it possible for you to capture the serial output of your OpenLogger during boot? If you use something like TeraTerm or PuTTY, you can see the OpenLogger's serial port output as it boots which can provide some troubleshooting information. When setting up the session, you'll want to specify a speed of 1.25 MBaud. Once the session has established, hit P32 RST near the radio module and observe the output in the terminal. If you can include a screenshot or textual representation of the output in your response we can proceed troubleshooting your issue. AndrewHolzer
  16. Hi @Scooby, It sounds like the .hex file may have been corrupted when it downloaded due to a network issue, or when transfering the file via USB. If you are using a USB hub, we require that you use a USB 2.0 high-speed hub. While updating firmware will usually work with a full-speed hub, we have encountered issues when using full-speed. You will need to run through the Corrupt Firmware Recovery flow to fix the issue. You may want to downloaded the firmware .hex from the resource page, underneath Firmware on the right. If you decide to download the hex from the resource page, when you get to selecting the version of firmware you'd like to flash, select Other and then Browser to select the .hex you downloaded earlier and continue following the guide. Let us know whether you were successful or whether we need to work with you further on troubleshooting this issue.
  17. Hey @BecauseIHaveto, First, I must apologize for my delayed response. I'm still scratching my head on this. Ideally, before reading the oscilloscope you would issue a getCurrentState command and check to see whether the trigger has fired and data has been made available, then perform the read. With how you've got things configured, the 3 second delay before reading would allow enough time for data to be made available to you. I suggest that you try a getCurrentState before the read, looping on that while there is no data and once there is, then performing the read to fetch it. I also suggest that you make sure that you are looping the output of the WaveGen back into channel 1 of the oscilloscope. It is a simple solution, but its easy to overlook because of its simplicity. I'll be looking forward to your update. AndrewHolzer
  18. Hi @BecauseIHaveto, What it sounds like to me is that the oscilloscope hasn't acquired any data yet because the trigger conditions haven't occurred. When the trigger is armed, the instrument will wait for the specified trigger conditions to occur, and when that happens some amount of data is acquired and is then made available for the subsequent oscilloscope read command.The error you are seeing makes sense in this case. However, I also see that you are setting of the wavegen instrument and I am assuming that you are feeding this signal back into the OpenScope via oscilloscope channel 1, so we should see some acquired data. I do not see a run command for the awg being sent in the code snippet you sent above, and this right here looks to be the cause of the issue. If you drop in a awg run command after the awg setRegularWaveform, your osc read should (hopefully) come back with some data. Let me know if that works out for you, or whether there is another issue that needs to be fixed. Regards, AndrewHolzer
  19. @Fa-b, It is possible that your browser could be caching the results of the firmware version list operation. You might try a force refresh on the page to see if that fixes the issue. If that doesn't work, I'd like you to try a different browser to see if you can see version 1.301.0 there. If you can, then please go back to your regular browser, and visit the WaveForms Live settings page. Expand the Advanced portion and click the Change Console Log button, and choose Console to enable logging to the browser's console. Open the console (usually with Ctrl + Shift + i), and then visit the Update Firmware page. Capture the console output, and send it to me through a PM. You could also try clearing the browser cookies and cache, however this would mean WaveForms Live would forget your devices, so I only advise you do this if you are okay with this happening. Regards, Andrew
  20. Hi @banban & @Fa-b, I've pushed the most recent firmware version onto GitHub. I don't have a changelog for the changes from 1.296.0 to 1.301.0, but moving forward each release of the firmware will be posted to the repository along with a changelog for the update. I hope that this will help with bug fixes in the future. I also spoke to Keith about the LA trigger where he and I both confirmed that it is working on the latest firmware. We tested this using WaveForms Live and connecting LA channel 1 up to a source producing a square wave at a fixed frequency. Can either of you please clarify how you came to find the LA trigger isn't working as expected? As you, banban, are trying to make a Python interface, it is possible that you aren't configuring the trigger properly. WFL issues a trigger.setParameters command when the user clicks Run. This command sets the source instrument you want to trigger on and the rising & falling bitmask for the trigger conditions. I'll be looking for your updates regarding the LA trigger issue, Andrew
  21. Hi @Ictinike, Have you resolved your issue, or found anything new? You mentioned this issue began when you updated the firmware; have you tried rolling back to a previous version and seeing if things work properly? If you are still having issues, I can help you troubleshoot and find the real issue at cause here. Regards, AndrewHolzer
  22. Hi @chuerta, In WaveForms Live you can configure an oscilloscope channel's sampling rate and the number of samples taken in the instrument panel. The sampling rate is based on the time base by default, but toggling the lock to the right of the setting will allow you to manually set it. You can tweak these values to hone in your FFT resolution. AndrewHolzer
  23. Hey Banban, Trigger In functionality hasn't been implemented in the firmware. We reserved those pins for future implementation but as you've noticed we haven't done so yet. I'll speak to Keith about getting the latest/all the firmware version(s) onto GitHub. He's out until next week, so I ask for your patience until we can get you the updated firmware. Can you please elaborate on how you were using the LA trigger to accomplish your goal? I'll see how I can help you here but I need some more information to do so. Thank you, Andrew
  24. Hello Fabian, I'm the other engineer JColvin mentioned. I'll begin with your question about how WFL handles forceTrigger: If you a look at the WFL source, specifically the trigger component, you should notice that the component wraps trigger.forceTrigger, and this component method is bound to the on tap event of a button. If the user clicks this button when acquisition isn't running or the trigger is set to off, then the status code you were seeing is reported and the user is told of the error. When setting the trigger to off, the command sent to the OpenScope when told to run has the trigger source instrument set to 'force'. I assume the OpenScope then readies a buffer whether or not a trigger condition is met since we told it to not care about that. Once the instruments are running and the multiCommand that was issued completes, WFL calls setTimeout with a delay that's calculated from the buffer size and sampling frequency, which attempts to read the OpenScope buffers when completed. If we aren't doing a single run acquisition then this timeout is repeatedly set until an error occurs or the user stops acquisition. After going over all this I believe the trigger type should really be called auto instead of off. The acqCount parameter requires some explanation, which hopefully clarifies your data row-up question. Both the OpenScope and WFL keep a running count of acquired buffers which is this acqCount value. When querying the OpenScope for a buffer, WFL doesn't ask for the most recent buffer in most cases, and instead asks for the previous acqCount plus one. If the OpenScope hasn't buffered the data yet, it reports back as such, at which point WFL will periodically queries the OpenScope for the buffer until it gets it. This method ensures that there is no overlapping data that is coming back from the OpenScope. Depending on the triggering conditions you set there may be some lost data between buffer packets. To specifically answer your question, the OpenScope keeps the most recent full buffer of data while it fills a new buffer up, which becomes the most recent full buffer when it is full. It sounds like you want a similar approach to what is happening when the trigger is set to off: begin acquisition, poll the OpenScope for available an available buffer until you get it, process the buffer and then ask the OpenScope for more until you are satisfied. If you have further questions or need further clarification on something, I'll do my best to help you. It might take me some time for me to reply as I find you your answers but I'll be digging as deep as I need to to find them. Regards, Andrew
  25. @D@n, You're welcome! Glad to do what I can. Andrew