Technical Forum Moderator
  • Content Count

  • Joined

  • Last visited

  • Days Won


AndrewHolzer last won the day on November 30 2019

AndrewHolzer had the most liked content!


About AndrewHolzer

  • Rank
    Prolific Poster

Profile Information

  • Gender

Recent Profile Visitors

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

  1. You're welcome @snes369, anytime! Do not hesitate to post again on the forums if you need any help. We are happy do to so. AndrewHolzer
  2. Hi @snes369, Thank you for reaching out to us about your problem. I am going to ask you to do a few things so that we can try and establish what the real issue is here. First, have you tried a different USB cable, and what sort of USB port are you plugging it into on the PC? Best get this out of the way off the bat. If the cable is sound, has the device appeared in Ports section of the Device Manager? You can easily find this by right clicking the Windows Start menu and selecting 'Device Manager' from the new menu. Unplug the OpenLogger before you open the Manager, then once you've expanded the Ports section, plug the OpenLogger in and see if a new COM device is reported. If we can see the OpenLogger in the Manager, are we able to get some output from a serial terminal? You can use whichever one, I use PuTTY and others here use Tera Term. If you specify a baud rate of 1250000 (1.25 MBaud), the terminal can establish a connection. Once the terminal has connected, press the reset button of the OpenLogger. It should output some information on the terminal after startup, such as calibration state and wifi state among others. Let me know what results you find. Together we'll find the problem and its solution. AndrewHolzer
  3. Hi @twistedsymphony WaveForms Live doesn't support concurrent use of multiple OpenLoggers. The best that you can do is to configure and run one device, re-associate the agent with the second, then configure and run that one. Unfortunately there won't be any sort of synchronization between the devices, and you'll have to re-associate the agent if you want to view the chart for each OpenLogger. You may possibly configure both device to Log on Boot and stream to the SD card. Still, there won't be any synchronization between the OpenLoggers, but you will be able to gather data across your 12 or more channels.
  4. Thank you for pointing out that nowhere does the store page say that the OpenLogger is only supported by Windows. We make statements on the wiki to that effect, but the store page needs to state that as well. I will get the store page updated promptly to state that. To start the returns process, please contact our sales department and we will refund you your purchase.
  5. Hi @mossygreen, The OpenLogger is only supported by Windows and is incompatible with versions of the agent older than 1.2.0. Windows is the only OS that supports changes made to the agent after 1.2.0 hence why the OpenLogger is only supported by it. You could dual boot Windows on your Mac and get it working that way. If this is too tall an order to ask of you, then we will proceed with the returns process and give you a refund.
  6. You need to be using older attributes to set the column sizes. This article has the appropriate attributes to use. I don't think you can specify any sort of width and thus have to stick to the ones specified which is why the previous width-30 & width-70 didn't work.
  7. Hi @sgrobler, I think it's entirely possible to include a timestamp in a log header when starting a session from a connected host. I'll put this on my list of additions & fixes, put some thought into a proper solution and get to work on it. I'll personally message you once I've made the changes (and you'll probably see a blog post about them as well). Regards, AndrewHolzer
  8. Hi @sgrobler, Thank you for posting about the issues you are having with WaveForms Live. I am currently doing some further work on the OpenLogger and WaveForms Live and will gladly fit investigating them into task list. I'll also take a look at the single character scaling issue you posted about. Keep an eye on this thread for an update. AndrewHolzer
  9. Hi @Jentson, I did a sort of back of the envelope calculation to figure this out. At 3 MS/s, the 32640 buffer will be filled in about 10.77 ms. The OpenScope has a 12-bit resolution per channel, which means we are looking at 391680 bits. To keep the buffer from overflowing you'll need to send all those bits over serial within 10.77 ms. The baud rate necessary to do so comes out to about 2.21 MBaud. The OpenScope runs at 1.25 MBaud with no way to change the baud rate, so you will run into issues. You will be unable to run the data over WiFi as well. There are few factors that play into the limited speed, but we measured a sustained speed of 200 kB/s over WiFi. I am sorry to say but the OpenScope won't cut it for the intended application you have in mind for it. AndrewHolzer
  10. @DomDV, Glad to hear you found a solution. If you indeed need to report back, I'll be keeping an eye out for you.
  11. Hi @DomDV, Have you changed anything about your setup between when it used to work and now? Can you also enable console logging in the Settings page underneath the Advanced section, open your browser's developer tools and then include a copy of the console output in your reply of you trying to connect to the OpenScope? What is the IP address you mentioned? AndrewHolzer
  12. Yes, that's what I measured. I've included an image that has the dimensions labelled. If it is hard to see, each side measures 72mm.
  13. Only the files that are opened will be corrupted. I don't know what the OpenLogger is doing with the files as it logs to the SD but can figure out if you require further information. I just had issues with the PCB dimensions file and had trouble myself. I am going to see if that can be fixed, but in the meantime I measured each side of the PCB to be 2 & 13/16 inches,
  14. Hi @TKMoon, The error code you have there signifies no networks found. This error alone shouldn't cause the device to never finish booting however. To solve the AutoConnect error you must either bring the network back up or have the device forget the network configuration information. Can you tell me how long you've had the device and anything that may have happened leading up to the device failing to boot? Regards, AndrewHolzer
  15. Alright, just heard back. The operational temperature range is 0C to 70C. The DDR is the limiting factor of the design.