[ottorino]

@ray wrote:

Hope this makes sense.

This make a lot o sense. At least to me.
I know this topic is about saving memory, but …wouldn’t be possible to log such a potentially very dangerous event ?
Or is it already logged as partial watering time ?

[ottorino]

@ray wrote:

Another question: since ‘seconds’ is not very common, do people care about the accuracy of 1 second, or would 5 seconds suffice?

Consider the use of a station for watering small pots or nurseries: overwatering behind the corner.
Or a clayey soil ( = slow infiltration rates) with slopes (= fast rill/surface erosion): the slopes will be underwatered; the end of the slopes overwatered, even in reduced state (= too much water = no oxygen).

I think that 5 seconds is a sufficient granularity. A greater value could be too much..
I went crazy in adjusting drippers with an old programmer whose granularity was 1 minute.
Consider also the existent humidity of soil which can alter the infiltration rate as the irrigation proceed.
I think that a fine granularity is mandatory; and on the plus side of this project.

A second thought.
Five seconds would still allow the use of a 1-2 sec delay in master/pump, but then the granularity would be reduced to 4 o 3 seconds.
Practically, I cannot see any diffrence between the actual granularity of 1 or the new one of 5 seconds.
Would people need longer delays in pump/master ?

[ottorino]

Now it works again here.
Thanks for your prompt help.

[ottorino]

Ciao Rjalex !!
Thanks for the correct translation !! Mine was poorly “handmade”.

[ottorino]

Hi all,
I think this is the proper topic to talk about a weird behavior on scheduling ’round midnight.

From time to time I find the from/to values of some of my programs changed to
from = 00:00
to = 00:00

This morning it happened again, and I noticed that it was a program which started at 00:01 and stopped at 08:00.
I’m not totally sure, but I suspect that the reset may be due to the 00:01 value.

I do not know if this behavior is reproducible. I will keep an eye on it.

Any other on this forum has noticed this ?

[ottorino]

Similar problem here, on debian jessie and Iceweasel.

TypeError: body is undefined home.js:8
Non è stata dichiarata la codifica caratteri del documento HTML. Il documento verrà visualizzato con del testo incomprensibile in alcune configurazioni del browser nel caso in cui contenga dei caratteri al di fuori dell’intervallo US-ASCII. La codifica caratteri di una pagina deve essere dichiarata nel documento o nel protocollo di trasferimento.

HTML charset have not been declared. The document will be shown with unintelligible characters in some browser’ configurations, when the document itself contains non US-ASCII characters. Page charset must be declared in the document or in the transfer protocol

Also from android: all I can see is a blank screen.

[ottorino]

Thanks Samer, it was easier than I expected.

Now I have another question: the data format of the logs.

They looks like;

1,1,40,1408579221],[2,2,180,1408579403], [5,0,45,1408582846], … , [3,3,120,1409088721],[99,0,21,1409090274],[99,0,65533,1409090289],[99,1,60,1409301780],[99,4,60,1409301871],[99,3,60,1409302036

I would like to import them into “R”, but this is not a familiar format to me.

I can guess that ( between the inner [ ], from the last figure );

A) the long final figure is the date (which format ? seconds from which date ?);

B) the number before are the seconds during which the station was on
(the “65533” is the mistery I would like to solve; it has been happened twice during this month);

C) the number before is the program which activate the station, being 0 a manual start.

D) the first number should be the station, but I suppose that the “99” have a special meaning, which I’m missing.

Are my guesses correct ??

[ottorino]

Sure I will.
I already noticed that the web interface has no issues in rounding

[ottorino]

@ottorino wrote:

Apparently I have also some other problems (better call them perplexities), but I will report on them when I will have a true keyboard and a more reliable connection.

On the mobile app: on entering the log page, appears a graphic, with lines, no areas. If you modify the time window, or the grouping, the graph doubles and appears as seen trough a prism. Almost unreadable

On the web program: none of the above; and the lines appears not as areas, but as lines.

I can say areas because for some reason I’ve got a unreal 1091 seconds on a station, dropping to zero in 20 minutes, linearly.

It was due to some misfunctioning: that station entered in a strange loop; it was running over and over again, but the valves did not open at all.

To reboot was not sufficient: I had to turn the controller off and wait some minutes to recover.

This is the main reason for which I would like to see the logs.

Before you ask, Samer: the logs are not mailable, either if the weird run is included or not.

I also noticed that on table, only minutes are reported. I have a heavy clayey soil with some slope here and there, i.e. its infiltration rate is very low and dictates very short (about 40 sec) and long-distant-in-time watering periods.

Are the emailed logs rounded to the nearest minute as well ?

[ottorino]

@salbahra wrote:

If you reset the config, does the export work? I am wondering if this is some sort of data encoding issue in station names?

Thanks!

No. Still the same behaviour.

On restoring the configuration I’ve found ten programms instead than 5.
I have to check them, but at first inspection it seems that they are my actual ones plus some old ones.
Is that doubling of programs an expected behaviour?

UPDATE: they are doubled; two identical copies of 5 programs.
1=6, 2=7, …., 5=10.

No. I can’t even find any export on both side panels: may be I did not understand well where to search for it.

In the meanwhile, I upgraded to version 1.1.7 the web interface.

UPDATE: from the web interface (ethernet wire connected to my router, iceweasel on Debian wheezy) I cannot export the log at all. On pressing “export” the e-mali client (Evolution) do not even opens up. I will check Iceweasel settings.
Should I move to 2.0.8 firmware ??

[ottorino]

I will try this as soon I will get back home.
I’m waiting for a TP link to permanently connect the controller.

I am wondering if this is some sort of data encoding issue in station names?

As far I can remember, I have no particular “weird” characters in it; accented ones I mean. Only ASCII ones, spaces and capitals included.

[ottorino]

I’ve placed all the details in my signature. Should it not to be exhaustive, I can add details: just tell me which ones.

Yes: on pressing the button ‘export’, the e-mail client opens up with an empty message. Only the subject field is filled with text.
Apparently I have also some other problems (better call them perplexities), but I will report on them when I will have a true keyboard and a more reliable connection.

PS
No need to be sorry, Samer. I’m only reporting, hoping to help to improve the whole system

[ottorino]

I’ve tried this feature, but I’ve only received an empty e-mail without any attachment.
What am I missing here?

PS
Firmware 2.0.7 on OS, with 16gb SD card FAT32 formatted.
I can see the logs in the app both graphically and as tables.

[ottorino]

http://www.fao.org/docrep/x0490e/x0490e04.htm

Hope this helps

[ottorino]

… Or simply a bad battery!! Thanks for the suggestion. A new cell solved the problem. The old one measured only about 0.2 V

[ottorino]

Hi all, here is Ottorino from Florence, Italy.

Here on Debian Jessie Linux I was not able to update the firmware no matter how compulsively measure the two seconds, no matter if the usb cable was inserted before or later in the computer !!

I finally succeded to update the firmware to 2.0.7.
Apparently the problem was the 3.0 USB plugs (the blue ones) on my fujistu.
Performing the upgrade procedure with standard usb, I encountered no problems at all.

[Author]

Posts