• Content Count

  • Joined

  • Last visited

About Kristoff

  • Rank
    Prolific Poster

Profile Information

  • Gender
  • Location
    Seattle, WA

Recent Profile Visitors

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

  1. Hey, As you mentioned the analog input range of OpenLogger is +/-10V and the ADC is 16-bits and your math is correct that theoretically that would result in ~0.3mV as the smallest voltage difference we can measure. In reality every non-ideal system component starts to chip away at that precision. For OpenLogger our tests show that we can consistently measure to about 3mV (effectively 12 bits of resolution for our ±10V range) and assuming the OpenLogger is appropriately calibrated our accuracy is typically within about 10mV due to noise and distortion. We can improve these values by
  2. Adding this to the FAQ here under When will all of the v1.0 features be available? We'll add more details and updates there.
  3. Hey Bevets, We plan to evaluate better Linux and Mac support after we get the main feature set complete in the OpenLogger firmware and WaveForms Live. Our goal is to have Wifi released by the end of March. Once we support Wifi, Mac and Linux will be a viable option via wifi, but you'll still need a Windows machine to connect via USB and update the device firmware. We're working on logging to the SD card now and should have a release ready in the next couple weeks. The first release will probably not include logging on boot, but that should be released shortly after logging t
  4. Hey MRE, Sorry to hear that you got off to a rocky start with OpenLogger. I'll add some links here so others can benefit from your feedback. All of our OpenLogger documentation is linked from the OpenLogger resource center and I suggest all new users follow the instructions in the OpenLogger Getting Started Guide for initial setup. You can find the pinout diagram on the OpenLogger resource center as well (top left side). The pinout diagram is also available once you're connected to the device in WaveForms Live (see image below). I wish we could have labeled the pins on the
  5. Wifi support will be added in one of the next updates. I expect it should be released by mid March. -Kristoff
  6. Hey, The getActiveDevice has not been implemented. I added a note to the documentation to call that out. During initial development we started by defining the specification and then found some commands were not required for OpenScope/OpenLogger to function with WaveForms Live. Logging to RAM is a bit different than logging to a file on a non-volatile storage device (SD in the case of OpenScope / OpenLogger). When logging to RAM it doesn't actually create 'files' in RAM, it just logs to a buffer and the buffer will be overwritten when you stop logging and start a new log. Let
  7. Hey Adithya, Any commands sent to the agent's root endpoint http://localhost:42135 will be passed through to the active device (if there is an active device). Since there is no active device in your case you get the error you noted. You can send commands to configure the agent to the 'config' endpoint http://localhost:42135/config The Agent code that handles these commands is here for your reference. Let us know if that works for you or if you have any more questions. Thanks! -Kristoff
  8. Hey arnz, lo is the loopback adapter. It's a virtual network adapter that just 'loops back' any network traffic sent to it. You can ignore it for what you're doing. It sounds like when you use LabVIEW to configure the network adapter it somehow saved the old (DHCP) IP as the static IP. I don't have the software in front of me, but off the top of my head I can't think of a good explination of how this would happen. Can you post a screenshot of the selection(s) you made in the network config menu? It's good practice to not manually assign IP addresses that are in the range tha
  9. That's right. The trigger pins are hardware capable but the current version of the firmware has not yet implemented support for them. -Kristoff
  10. Hey Marty, Thanks for the feedback. I created an issue for this on GitHub. For now I recommend you just make the change locally to get the correct data to pass through. -Kristoff
  11. Hey Marty, The Max32 + Ethernet Shield is a supported combination with LINX. You can see all the LINX supported devices here. Let us know if you have any questions about this. Thanks! -Kristoff
  12. Can you provide more details on what hardware and software you're using, what exactly you would like to accomplish and what parts you're having trouble with? The more details you provide the easier it will be for us to help you. Thanks! -Kristoff
  13. Fair enough :D. Glad to hear LabVIEW + WF32 is working well for you. I had a lot of fun creating that and still have my original demo with a WF32 with WS2812 light strip controlled by LabVIEW mounted on my porch ceiling. -Kristoff
  14. Hey, LabVIEW support doesn't depend on Jessie, but it was developed and tested on Jessie and has not been updated for Stretch. The LabVIEW runtime should still work just fine, but there may be changes in the newer OS that require some manual setup / modification. For example SSH is not enabled by default anymore, so you'll have to enable that before following the standard setup procedure. RPI has been pretty good about not breaking backward compatibility for the I/O, but I haven't tested it so I can't say for sure that all the I/O will work without modification. -Kristoff