Search the Community

Showing results for tags 'openlogger'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • News
    • New Users Introduction
    • Announcements
  • Digilent Technical Forums
    • FPGA
    • Digilent Microcontroller Boards
    • Non-Digilent Microcontrollers
    • Add-on Boards
    • Scopes & Instruments
    • LabVIEW
    • FRC
    • Other
  • General Discussion
    • Project Vault
    • Learn
    • Suggestions & Feedback
    • Buy, Sell, Trade
    • Sales Questions
    • Off Topic
    • Educators
    • Technical Based Off-Topic Discussions

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


AIM


MSN


Website URL


ICQ


Yahoo


Jabber


Skype


Location


Interests

Found 20 results

  1. Here's an OpenScope and OpenLogger log file utility that can export to CSV (TODO: JSON). It's written in Python, but the important part (the log file parsing) is portable across about a dozen other languages. https://github.com/bdlow/dlog-utils-portable I've used a combination of the data structure definitions in the Digilent dlog-utils project, some information posted in this forum on the OpenScope data format, and the application of educated guesswork. IMHO this is an improvement over the current version of dlog-utils, which has various log file parameters hard-coded within even though these parameters are specified within the log file header. It's also more portable (Python 3), smaller and of course handles both log types. This work was made possible through the use of the awesome Kaitai Struct project to define the log file structure and automatically generate a Python parsing library from that. Kaitai handles all the details of the log formatting including endianness and data types, and presents the log via a very easy to use Python class. The web IDE makes it very easy to poke around the binary log file. Want to use something other than Python? All you need's the `.ksy` file and you're almost there for any of the languages that Kaitai supports: C++/STL, C#, Go, Java, JavaScript, Lua, Perl, PHP, Python and Ruby. I've a JSON exporting version almost ready, though I probably ought to add some tests first. @Digilent: can you expand on what the channel map is meant to represent? I had presumed it was the channel number to sample index mapping, e.g. if I recorded channels 2, 3 and 7 in the OpenLogger then I'd have expected the data to have three channels in each sample; and the channel map to look like [2, 3, 7, 0, ...]. However my OpenLogger generates log files with a channel map [1, 2, 3]. Bug?
  2. I've been able to use Waveforms live and connect to my OpenLogger through my phone's wifi hotspot in the past. However since I've upgraded firmware to 1.3.0 I have not been able to to this. I now get a message "firmware update required" even though I'm on the latest openlogger firmware. (see screenshot). The blue light is on solid, indicating that I'm connected to wifi. I've also tried connecting through my home wifi network with waveformslive on my computer, and get the same message. Can anyone at Digilent or elsewhere check to see if you can connect via phone hotspot with firmware version 1.3.0? (I also cannot connect via wifi from my PC - I can ping the openlogger, but cannot connect to it...) many thanks - Steve
  3. Now that there is a means of exporting log files to csv, I have been trying out my device (with firmware 1.3.0). There are some issues that I think still need to be resolved. 1. Advanced tab - "profile": if I store a profile and then restore it later, the settings for the DC power supply are not re-loaded. I am using the DC power supply to power a sensor, so it would be nice for the power setting to be reloaded when I load the saved profile. It also does not load any scaling applied to the analogue channels. 2. Advanced tab - "Log On Boot": This option lets the logger automatically start logging when it reboots. The issue I have is related to the one above - I am powering a sensor with the DC supply, so on reboot, the DC power setting should get restored, but it does not, so the sensor is not powered-up on re-boot. Can we make the power be re-applied on reboot also? 3. Advanced tab - loading profiles. I've saved two profiles. However only one appears in the profile drop-down list menu. I know both are saved because if I go to the "file explorer" button, I can see them stored under the "flash" folder. At one time I could see them both but now I only see one - even after re-booting the openlogger and re-connecting. 4. Scaling: I am scaling my sensor signal by a factor of 50 to convert from Volts to m. I have my sensor connected to Channel 5. The graph always displays "Ch 1" and gives units in "mV" despite the scaling and units I've entered. It should display my channel number correctly and the correct units, but it does not. I can see my signal in the top buffer display, but not on the main chart. 5. Waveform display: Attached is a screenshot showing streaming of channel 5 (without any scaling). Display shows Ch1 (even though channel 1 is not even active). The graph y-scaling seems to be 5mV/div even though for channel 5 it is set to 500mV/div. The true waveform signal is around 723mV, yet the graph axis indicates its about 7mV. Is anyone else seeing the same issues? Could these please be addressed in future firmware releases?
  4. Hi I've updated my openlogger with latest firmware (1.3.0). A problem that I noticed with previous firmware and which is still present, is that the scaling option will only let you enter one character for your units. There are many units that need more than 1 character, eg mm, Pa, dB, dBA etc so it would be nice to be able to enter more than one character. Once you hit enter you get an "invalid units" message. Is there a trick that I am missing?
  5. Two questions: 1. Supposing I want to use my logger somewhere without a wireless network - is there a way I can have a direct wi-fi connection between my phone and the openlogger? 2. At the moment I can connect to my openlogger through the usb or through wifi, from Waveforms live on my desktop computer. I seem to be able to connect to it from my mobile phone, but I can't launch the instrument panel from teh mobile phone - a "connecting to device" message flashes up on the phone and then nothing happens. Any idea why?
  6. Hi everyone, I found an easy way to read .log file by MATLAB. MATLAB has functions to read binary file but the difficulty is that we are not sure about the header and format of the log data. I am not familiar with Python so the other way that posted by benl using Python is such a pain to me. Here are a few lines that can easily decode .log file with two channels of data: %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% %% Read Data from OpenLogger file close all;clear;clc logfilename = '20190723_9_0.log'; finfo = dir(['F:\' logfilename]); channelNum = 2; %number of channels sampleNum = finfo.bytes/2/channelNum; fileID = fopen(logfilename); logdata = fread(fileID,[channelNum sampleNum],'int16=>int16'); fclose(fileID); headerNum=257; plot(logdata(1,headerNum+1:end),'-'),hold on %channel 1 plot(logdata(2,headerNum+1:end),'-'),hold off %channel 2 %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% WaveForms Live read in Matlab Note: I don't care about the header info so I just get rid of it. I use random input pulses for ch2; The two plots are not from the same time. peggy
  7. Hi, I am trying to continuously log data. I have logged data to the SD card for more than 20 hours. The experiment result is pretty good: 1. the OpenLogger can continuously work; 2. it can split files automatically 3. the maximum size of a single file is about 3.7GB However, the time of each data file is wrong. Does the OpenLogger have any timing module? I have made it connected to the internet. Is it possible for it to adjust time according to the internet? thanks!
  8. Hi, I use OpenLogger to log data to the SD card. The saved data file is in the format of *.log. I tried to read it out by Matlab but failed. Could you give me some help? For example, what's the format of these data? Does it both include time and voltage? What's the header like? ... Thanks, Peggy
  9. Hi, Since I am just an end-user of the OpenLogger. Hence, I am having a hard time to read a log file to a CSV file based on the instruction of the digilentinc' s instruction. Has anyone succeeded in converting the log file? If so, is there any advice or suggestion that you could give? Could you post a video of converting to CSV on youtube Digilentinc as it is very ridiculous for the OpenLogger to produce a file which can not be read in Matlab?
  10. Hi, 1. What are the power requirements of the board? I am designing a system that requires the OpenLogger to be mobile (not powered by USB micro B via laptop) 2. Where can I get a full schematic of the board?
  11. Further to my struggles here https://forum.digilentinc.com/topic/17957-open-logger-some-basic-doubts/?tab=comments#comment-46282 I must say today was a lucky day ... Yes the OpenLoggerMZ worked as it should with another laptop running WINDOWS 8.1. Using this opp i even upgraded the firmware to 0.1719.0 and all well. Could feed the Wavegen output to CH1 and could see the plot. Atleast the board is still not bricked ... whew !! Then try the same with WINDOWS 10 which is my own laptop. Nothing works . Board connects only in offline mode and even then reports OpenScopeMZ ( see the mess in the reporting .. OSMZ and bottom line reads OpenLoggerMZ) and of course nothing more happens. So its confirmed that this board is not working with WIN10. I even tried to invoke compatibility mode with WIN8.1. No luck
  12. Hi, I am trying to generate a pulse wave instead of a continuous wave which is the default of Waveform Live. Is there a way to do this? I am also having a problem using the math function which is located in the bottom right of the browser, It freezes the site when it is selected.
  13. Thanks for updating the new function of logging data to the SD card! Unfortunately, I still can not find the button for logging data to the SD card in the WaveForms Live. Only 'chart' is available. My firmware is already the newest version 0.1719.0.
  14. We have both of these and would like to use either of them to measure dc voltages. The problem is we are using robotics to move our sensors so we also need the x,y,z coordinates as well as the voltage read at those coordinates. Is there any way to ask the hardware to report what it is reading? Our software basically positions the sensor in one of 900 possible grid locations and we then measure 2 voltages and compute the current from the voltage drop across a know resistor as well as reading magnetic field strength. If we could put the coordinates into the log perhaps using the digital i/o. We just need a way to indicate the position where we took the readings in the log file somehow. Thanks.
  15. Have just started playing with the OpenLogger that just arrived. Did a firmware update and calibration via a Windows 10 VM on a macOS machine, and connected the OpenLogger to wifi, all went fine. Is wifi meant to be working? If so, consider the following as a bug report. If not, then what's the ETA looking like? OL firmware version: whatever the latest is (how can I determine this from a running device? the UI should have some method of viewing the connected device's firmware version (e.g. in device manager?)) env: Chrome Version 73.0.3683.103 (Official Build) (64-bit); macOS 10.14.4 (18E226) However when connected to the OpenLogger via wifi I see frequent errors, including - "Error Occurred Starting Or Running Acquisition" when interacting with the timebase and amplitude (i.e. mouse zooming/scrolling) - "Could not set AWG parameters" when interacting with the AWG controls, changing modes There doesn't seem to be anything in the browser dev tools console when these occur. (the console does show a bunch of warnings re. 't' plugin and a CORS policy error just on loading the waveformslive.com page, but there's nothing additional when the acquisition error occurs). Repro: 0. OpenLogger connected to wifi 1. go to http://waveformslive.com/ 2. start streaming 3. interact with the UI - scroll back and forth, zoom in/out 4. in very short order one of the above error messages pops up; at this point the UI becomes unresponsive and a page reload / device reconnect is required Occasionally the device will get itself so confused it won't connect at all (WFL reports "No response received"), and a OL board reset is required. PS: there needs to be some sort of error log mechanism, it's a real pain to try and capture the errors via toasts....
  16. As you can tell from, my spate of messages, I'm playing with my OpenLogger - discovered this problem today: I wanted to use one of the two DC power supplies. I set DCOUT1 to 1V and measured on the board with a multimeter. Nothing. Turned it off and set DCOUT2 to 1V and measured. Nothing. Left DCOUT2 set to 1V and measured on DCOUT1 and yes, 1V is there, but it shouldn't be So, DCOUT1 on the interface is not working at all. DCOUT2 on the interface incorrectly directs output to DCOUT1 on the hardware.
  17. Hi to all !! Got my OpenLogger and installed Digilent Agent on my Windows 10 notebook. No errors. 1. Then followed line by line the Getting Started instructions. Have come stuck at the Device Identification via Agent. I just get a message " Error connecting to device " . What could be wrong ?? 2. Am I supposed to power up the board or only the USB cable is enough ? When exactly one use the DC power socket for power up? The manual is sadly silent on this ... 3. Instead of the Web based Waveforms Live how to host it locally on my PC ? When I try to enter http://localhost:42315 into Chrome browser I get a 404 response. I even tried to run the Agent in WIN8 compatibility mode. No use... SO what else do I need to check
  18. I got my Open logger on Monday and till date I have struggled enough but yet to see a single plot on screen. So have been wanting to get some tips in this thread...https://forum.digilentinc.com/topic/17957-open-logger-some-basic-doubts/ With no possibility of updating the firmware past the version 0.1691.0 and the WaveForms Live throwing up only errors its really frustrating.
  19. Greeting, I am interest to purchase the OpenLogger board. But have a question. Hope you can help to clarify. I want to use the device to collect data for analog K Thermocouple sensors Would it support analog input such as K type of thermocouple sensors? What are some of the K type thermocouple sensors it support? If the OpenLogger doesn't support is there a similar options? Thank you. Yoom
  20. I've noticed some problems with openlogger and waveforms live: 1. If I try to enter a equation into the analogue channel scaling popup, I cannot enter "mV" for the units. It looks like entry is restricted to a single letter only. That is a bit limiting. Furthermore any scaling equations I enter there don't seem to be saved, so I can't reload them next time I start waveforms live 2. Under the Advanced section, if I save the profile its not there the next time I run waveforms live. Where is it saved to, and how do I retrieve a stored profile?