Replying to myself... As a m2m2 noob I somehow managed to overlook the "edit data point" icon on the "Data points" page so it's now clear how to have a different logging interval than the polling one. Sorry.
That solves the resource issue for the DB - however, the question of having a different data source polling interval when viewing graphics still holds...
(I've been looking through a few related posts in m2m's forum as well as m2m2's config options but couldn't find an answer; sorry if I've overlooked)
I'm wondering how the following setup can be done:
It seems it's possible as an old post [1] shows, but I can't figure what config/module is needed.
Otherwise, is there for instance a way to initiate a data "refresh" at fixed intervals in a jsp script ? (might be dangerous if there's no global "limit" mechanism, as there will be a potential for DDoS if many views are open).
On a slightly related topic, I fail to understand how "Discard data delay (ms)" relate to the update period in the modbus module; any pointer ?
Thanks !
(I've been looking through a few related posts in m2m's forum as well as m2m2's config options but couldn't find an answer; sorry if I've overlooked)
I'm wondering how the following setup can be done:
It seems it's possible as an old post [1] shows, but I can't figure what config/module is needed.
Otherwise, is there for instance a way to initiate a data "refresh" at fixed intervals in a jsp script ? (might be dangerous if there's no global "limit" mechanism, as there will be a potential for DDoS if many views are open).
On a slightly related topic, I fail to understand how "Discard data delay (ms)" relate to the update period in the modbus module; any pointer ?
Thanks !
it seems it fixed it, no new alarm for 10 minutes.
I thought about that option when reading the changelog of 1.2.0rc, but 1.1.0 had the same problem so I dismissed it.
thanks - I will continue testing... ; feel free to ask if you want me to test that setup again with in case you patch something.
thanks for the quick reply...
here's the export (with the data source as well).
this m2m2 instance is only for tests and this specific data source + 2 points, so no problem if you want me to do some tests / brake things.
forgot to mention that to iron out a problem with the modbus device itself (Delta electronics/IFD9506) I tried reading the coils with libmodbus (on linux) as well as Delta's own software and everything is OK.
Edit:
1/ results of the read data test / coil / 2050 + 10:
2050 ==> false
2051 ==> true
2052 ==> false
2053 ==> false
2054 ==> true
2055 ==> false
2056 ==> false
2057 ==> true
2058 ==> true
2059 ==> false
2/ results of point locator for coil 2059
Result: false
Attachment: download link
hi there !
I'm playing with m2m2 + modbus (so no license for core/modbus) and I don't manage to use more than one modbus point.
I'm doing the following:
everything seems to work ; but then, if I add a 2nd point (name: m11), I get "illegal data value" alarms for that point, while the 1st one (y11) is working OK.
it's not a problem with the point config itself since if I first define m11 then y11, the illegal data value is now for y11 while m11 is working.
tried with 1.1.0 as well as 1.2.0rc.
is that a limitation of the trial mode ?
hi there !
I'm playing with m2m2 + modbus (so no license for core/modbus) and I don't manage to use more than one modbus point.
I'm doing the following:
everything seems to work ; but then, if I add a 2nd point (name: m11), I get "illegal data value" alarms for that point, while the 1st one (y11) is working OK.
it's not a problem with the point config itself since if I first define m11 then y11, the illegal data value is now for y11 while m11 is working.
tried with 1.1.0 as well as 1.2.0rc.
is that a limitation of the trial mode ?