• hussam

    sorry,have resolved ,it is browser compatibility problem

    posted in Announcements read more
  • hussam

    I download the new version 3.0 to test,but is not be started right,it stoped on
    INFO 2017-05-08T10:17:38,942 (org.springframework.web.servlet.handler.AbstractUrlHandlerMapping.registerHandler:362) - Mapped URL path [/sqlConsole.shtm] onto handler of type [class com.serotonin.m2m2.web.mvc.UrlHandlerController]
    INFO 2017-05-08T10:17:38,942 (org.springframework.web.servlet.handler.AbstractUrlHandlerMapping.registerHandler:362) - Mapped URL path [/globalScripts.shtm] onto handler of type [class com.serotonin.m2m2.web.mvc.UrlHandlerController]

    have anyone else found this?

    posted in Announcements read more
  • hussam

    you just want to read data from Redis,or you want store and read on redis;if you want store,you need to solve the key-Unique issue,redis is key-value struct,if you just want to read,it 's simple,you can see the redis official demo.

    posted in How-To read more
  • hussam

    quality field means in pointvalues database table direct indicate one point is good or bad in a exact timestamt.
    in ALL loggingType, if one timestamt no value,this can indicate it communication error.
    in on_change type,we can use use "No Change" or "No Update" event detectors to indicate it communication error.

    but when query pointvalue in api,chart,report ,just query data from pointvalue table,we don't join the event detectors to indicate one point is bad or good in a exact timestamt.

    posted in Mango Automation general Discussion read more
  • hussam

    In on_change loggingType , we can't differentiate one datapoint is communication error or is really have value just because value not change,this will impact datapointvalue query in chart, report and other place,especially in chart,if one point communication error on a peroid time then recovered, the chart line display straight line.

    if add one quality field,it would avoid this issue.

    posted in Mango Automation general Discussion read more
  • hussam

    update rate must be >timeout*(retries+1),and max read bit count=16*register. just fyi

    posted in User help read more
  • hussam

    Mango have already provided the datasource event to watchdog itself, you can use the datasource events.

    posted in Mango Automation general Discussion read more
  • hussam

    1:stop the mango.
    2:update you database use SQL.
    3:start again.

    posted in How-To read more
  • hussam

    It seems like, datapoint value's timestamp change every datasoure poll even if it's value don't change,so the last point update's time = datasource last poll time.

    posted in How-To read more
  • hussam

    I have more than 50 modbus datasource at one server,"updatePeriodType":"MINUTES", "updatePeriods":5, so, at the * */5 * * * ?, cpu utilization 100% instantaneous.

    so,if you have many datasource,avoid trigger them at same time point(same updatePeriodType and same updatePeriods),you can balance them to different time point.

    posted in Mango Automation general Discussion read more