sorry,have resolved ,it is browser compatibility problem
Latest posts made by hussam
RE: Mango Automation 3.0 Released
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?
RE: Developing a module to read data from Redis in-memory data structure store
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.
RE: dataPointvalue quality to indicate datapoint is good or bad
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.
dataPointvalue quality to indicate datapoint is good or bad
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.
RE: Polling issue with high register number with Arduino via Modbus
update rate must be >timeout*(retries+1),and max read bit count=16*register. just fyi
many datasource trigger at same time cause high cpu utilization instantaneous
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.