My post above was a little bit ambiguous. The tool at the website generates the graphs online, just upload the log. It’s not a collection of my scripts.

The idea was to have an easy uncomplicated way from log data to a graph.

-asc

Hi Manfred,

thank you for the feedback. I’m not sure if it’s possible to create a graph with such big width, but I understand the issue. Instead of a fixed 1200×750 resolution I can add a popup menu with some selectable presets. This is easy to implement, we have to test what is feasible.

It may also an option (for the future) to drop the image creation and use a js viewer for the data, where we can zoom in/out and scroll.

OK, the maximum was 19200×750 (256:10), a resolution of 38400×750 create a broken png image. Viewing with firefox was comfortable and much better than expected.

Example with 19200×750 png image.

http://mooshigraph.strcmp.org/?u=868791A9ED30

The x label setting was wrong for higher resolutions (only 10 for the whole graph). It’s now calculated by using the log count and the selected image resolution.

Hi James,
sure, you can write about it in your blog. It’s not closed, I’ll distribute a tarball or put it to github when I have finished the remaining open points (and cleanup the code). But don’t expect to much, it’s just two scripts, but helpful (because you can create a graph with some clicks).

This weekend, I’ve monitored the charging of a agm battery by a small solar charging controller.

http://mooshigraph.strcmp.org/?u=869F3C728135

Hi Manfred,

I’m using GD::Graph for image generation.

http://search.cpan.org/~ruz/GDGraph/Graph.pm

There are other (maybe better) options, but I’m using GD::Graph in two other projects.

Please note, the log parser expects a mooshimeter log file, including the header before the csv part stats. I’ve checked the error log and found some parsing problems caused by log files which are not “compliant” because they are modified.

Since I’ve published the link ~150 graphs were generated, most of them (~100) by myself, for testing and some real measurements.

I’ve the following points at my todo list.

* code cleanup
* notation conversion (scientific or decimal)
* selectable color schemes
* virtual third channel for calculations
* put the whole thing to github

The virtual third channel will open much opportunities. At the moment I’m not sure, how to implement. The easy way is to setup a pull-down menu with predefined operations (electrical Power, etc.). But maybe it’s a better idea to use a text-field where the user can insert a formula (e.g. RPN, which is good to parse). This will cover things like special sensors, shunts, etc. .

It’s also possible to do some final calculation, e.g. determine the real capacity of a battery (when discharging was monitored by the mooshimeter).

Hi James,

the list is not sorted by priority.

Before releasing the code, I must be sure, that there are no potential and obvious vulnerabilities (because it’s running at one of my servers). This is one reason for the code cleanup. I need also to strip private comments and unneeded functions inherited from my other projects. Any kind of documentation is missing.

When I started with it, I was on vacation, want a quick solution, without having in mind to publish it later.