AndrewHolzer

Technical Forum Moderator
  • Content Count

    126
  • Joined

  • Last visited

  • Days Won

    4

AndrewHolzer last won the day on February 1 2017

AndrewHolzer had the most liked content!

2 Followers

About AndrewHolzer

  • Rank
    Prolific Poster

Profile Information

  • Gender
    Male

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Hi @HeroGian, I've replicated your issue with my own setup and am getting an idea for a solution. I've got a few questions that I'd like to ask to help me get closer. First, what version of Petalinux are you using? What file are device tree file are you editing? In the device tree fragment you provided, I noticed that there are a few parameters left empty, such as interrupt-parent, interrupts, etc. Have these been intentionally left blank? Lastly, I'm unfamiliar with any of the XIrq_gen function calls that you are making within your application code. Is that part of the source generated for your HLS IP? Looking forward to helping you reach a working solution, AndrewHolzer
  2. Hi @Raghunathan, I've had a chance to try replicating your issue on several WIN10 machines, but haven't been successful. This leads me to believe that there is something about your machine that is causing the issue. Without troubleshooting your system, all I can say is use a WIN8.1 machine. Regards, AndrewHolzer
  3. 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
  4. 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
  5. @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 127.0.0.1 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
  6. 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 127.0.0.1. 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 127.0.0.1 works as well. Regards, AndrewHolzer
  7. 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
  8. 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 http://127.0.0.1:42135/ 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
  9. 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
  10. 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
  11. 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
  12. 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
  13. @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
  14. @Scooby, Did you see LD6 flashing as you typed into the terminal?
  15. 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.