Data Logger Graph Software |BEST| Download
Drema Elleman
Download version 7.7 of our EasyLog USB software, compatible with Windows 10 and 11. The latest build of the software includes support for the EL-USB-5+ Event and State data logger as well as improvements to the graphing module.
Watch this video for a detailed guide on how to stop and download data stored on your USB data logger and how to make the most out of the analysis features included in Lascar's EasyLog graphing software.
Data is downloaded in EasyLog software in graphical format. Run your cursor over the graph to see time and date stamped logs. Export all data to Excel for further analysis or view average statistics over a period of time using the EasyLog Summary Report.
Datalogger Graph is developed by Company and is used by 3 users of Software Informer. The most popular versions of this product among our users are: 2.0 and 2.1. The names of program executable files are DataLogger.exe, Graph.exe. The product will soon be reviewed by our informers.
I have a DRV8301-69M-KIT, and I am trying to work through the InstaSPIN Projects and Labs. I am new to CCS and this hardware. I am having two problems with the data logging feature in Lab 1b. The first is that the signals from the data logger are not being properly displayed in the graph windows, as can be seen in the following plot of the angle gen signal (it jumps all around and does not consistently look like this):
It seems to be a display or buffering issue rather than an issue with the actual signals. They look as expected (mostly) when I probe them with my scope. I read on one of the E2E forum questions that one-shot capture was recommended, and I have tried setting datalog.Flag_EnableLogOneShot = true in proj_lab01b.c, but I have not been successful in getting that to work.
The second issue I am having is that the DAC gains and offsets I set in hal.c do not seem to have any effect on the DAC output signals, neither those displayed in the graphs from the data logger nor those I probe with my scope. As far as I can tell, that code is executing, and the offsets and gains appear to be getting set, but I have no control over the actual offset of the signals, and the angle generator signal is always saturating high when I look at it on my scope.
1. I imported the appropriate .graphProp files from C:\ti\motorware\motorware_1_01_00_18\sw\solutions\instaspin_foc\src to set up the graph properties. That all worked just fine, and I am not having an issue with graph settings.
2. I have set datalog.Flag_EnableLogOneShot to "1", and I do get it to display a single shot of buffered data, but it is very close to a flat line in all cases. It looks nothing like it is supposed to. I have tried modifying the buffer and display data sizes, which does change what is displayed, but for no values am I able to get a waveform that looks as it should.
1. I am modifying these gain and offset values in hal.c. My problem is that the gains and offsets have no effect on the either the DAC outputs (as measured on my scope) or the data log signals. For example, the angle_gen signal, when viewed on my scope, is saturating high, regardless of the
2. I am probing the DACPWM pins with my scope. That is how I know that the graphs is not accurately displaying the DAC data. It is also how I have confirmed that the DAC gain and offset settings are not having any effect on the DAC signals.
After adjusting the reference speed and the buffer size, I now have the one-shot data logging working. But, still no luck getting the DAC offset and gain values to have any effect. I change the values in hal.c, but the DACPWM signals probed at J6 never change - the angle_gen signal always has a positive offset and is clipping high.
Going to the above page, we see that we are presented with a very basic list of the data files that can be selected from. Clicking any of them will cause the graph for that datafile to be loaded (much more quickly than the Arduino can manage).
Before we get started, we need to make sure our SD card is good to go. It should be formatted as a FAT16 or FAT32 filesystem, the details of which are available on the official Arduino website. Once that is done, we need to ensure two things are present in the root directory of the card: the HC.htm file, and a data/ directory for our datafiles. The data directory is easily made with the same computer that was used to format the card provided one has an SD card reader of some sort. The HC.htm simply consists of the following code:
I currently have my code set up to make a measurement every 10 minutes, and to create a new data file every week. You are welcome to change those parameters, just be aware that the current data file management names files using a dd-mm-yy.csv date format, so the new file interval should be at least 24 hours. Another concern, is that the shorter the measurement interval and the longer the new data file interval is, the larger the files will be. Because the Arduino is not especially powerful, this will have consequences for the loading times of each chart.
is #46 on/off and 47 power or 29 Dev.
I use it with the drive edge made by Taustin and I remember that he had created it so that the data was updated every minute, but I have no idea what the Shelly 3EM can give in order as time between measurements
The data logger will measure in a continuous streaming mode, until it is stopped by the user. While measuring, each time new samples are taken, they will be transferred directly to the computer where they will be processed and displayed and when required stored to disk. Any change in the input signal(s) will be immediately visible. The measurement duration is not limited by the amount of internal memory in the instrument, allowing for very long uninterrupted measurements.
The main difference with the oscilloscope is that the oscilloscope measures a predefined amount of time and stores all measured data internally in the instrument. When all data is measured, all data will be transferred to the computer and then be processed and displayed. After that, a new measurement will be started. This limits the total measuring length to the the size of the available memory inside the instrument. And there will always be a gap between two successive measurements.
The measuring mode of the data logger / transient recorder makes it the ideal instrument for measuring slowly changing signals like e.g. the temperature change in a room. While capturing the whole process, any change on the input signal(s) is immediately visible.
Another application for the data logger is to measure long non-repetitive signals like e.g. a serial communication signal, that would last too long to be captured in the internal memory of the hardware.
The data logger can have one or more graphs, each displaying one or more signals, where each graph can display different parts of a signal. Graphs can display the signal(s) in Yt mode or in XY mode, with or without interpolation. Colors of all items in a graph can be set to any required value. Graph dimensions can be adjusted to any required size, graphs can be located in one single window or in separate windows, which can be located anywhere on the desktop.
Controlling the data logger is done through customizable instrument and channel toolbars, through instrument and channel settings windows and popup menus and by hotkeys. A quick function toolbar is available for often used functions.
This website can also use non-functional cookies, for analytic purposes. When placing non-functional cookies, traceable data is processed. When you click the "Accept" button you will allow placing non-functional cookies.
I am looking to graph temperature data from an SD card onto a 3.2 TFT LCD. I would like to know what I should be researching/studying to make this happen?
All my searches lead me to Processing and graphing to a computer via Serial port, but that's not exactly what I want.
shows graph drawing using the Henning Karlsen library, which has excellent documentation, even though I had a lot of grief getting my display to work with it, and the data draw is staightforward enough. Here, the data is from sensors, but handling it from myfile reads would be much the same.
I'm using the SimpleEventLogger smartapp, currently dumping temperature data data into GoogleSheets (as I've been too lazy to set up a local DBMS until now). It dumps raw sensor data into a sheet and it looks like this
Note: When setting up Simple Eventlogger, under Other options there's "Include additional columns for short date and hour?" Be sure to turn that option ON as we'll need it. (that's column G in the screenshot above) To preserve space set "Delete Extra Columns?" ON as well and set archive type to Out of space. Once your sheet runs full, SimpleEventlogger will rename the sheet and start a new fresh sheet every blue moon, depending on your number of sensors and logging frequency.
Third step is to split all the sensor data out into columns for each sensor and create an average datapoint for each sensor per hour. That's where column F above is important, as that's the hour. We need to average as some sensors might be spitting out temperatures every few minutes, so even if I configure your SmartApp only to scan every 30 minutes, it'll pick up all those past sensor readings (haven't quite figured out how to get around thaT)
I wanted the graph to show an hour marker for the current hour as the graph does a cyclic update left to right, i.e. it's helpful to see where current time of day is on the graph. Next to the pivotal tables, I inserted the following formula in all cells G1-G24: =if($H2=hour(now()),$A$8,$A$10)
Once you got the graph running, all you need to do is publish it. Be sure to use the Image option under the Embed menu, as nothing else will work with AT. Copy the full URL from https:// to include format=image, but get rid of the iframe around the url.
Create a new media URL in AT and paste it in. Set the update interval to your preference, I'm running mine at 1800 seconds (half hour) update intervals.
That's pretty much all I've done, yet full disclosure it's not completely working as it's supposed to. Sometimes the graphs re-arrange themselves without prior consent from me. Some sensors just seem to drop off the graph even though there's still data for them. No idea why this happens yet, So there's still a few kinks to be worked out, yet I hope this is useful to some of you.