These seem to be Modbus protocol-specific questions.
Modbus does not have an auto-discovery like BACnet. You can make your own by polling each slave and see if there is any response.
Modbus can only have one master on a network.
Slaves cannot initiate a message they can only respond to a master.
Hi Sean
1.On your original point you must make then event detector with your 2 minute duration.
2. Then create a new binary virtual point.
3. go to event handler page and make a event handler like the picture. use the meta point that you created.
4. Now use <ma-get-point-value> on the new meta point and use that for your dashboard logic.
@pedro said in Script error: TypeError: Cannot read property "get" from undefined multistate:
var bulk = 1;
var stagePastDay = stage.past(DAY);
var bulkHours = stagePastDay.data.get(bulk).runtime / (10006060);
return bulkHours;
The example on the help documents for the .get() is
return b.past(MONTH, 2).get(false).proportion;
try remove the .data on your .get call. 
Hi @joeselbiyoyo
Firstly your data source is set to update at 5-minute intervals. You could reduce this to 5-10 seconds.
your data points are logging the average at 1-minute intervals. There will only be one value to average out. So there will be 5 values that are the same in a 5 min period.
you are then reporting the 1-hour average of these values smoothing them out even further.
I would try the following:
1.change the data source to 5-second poll rate.
2.change data point logging to instant
It would be great if it was possible to scale a data point in the data point Properties eg: have a section by the text rendering properties where a device span and engineering span could be put in.
device span : min= 0, max = 4095
engineering span: min= 0 , max= 100
unit = %
This would convert a 12 bit analog signal to a 0 to 100%
currently I am solving the problem by making a meta data source and a data point for each unit I need to scale. I think adding it to the original data point properties will make it a lot easier when doing bulk configurations in excel.
I have a page with 5 watch lists and haven't had issues. My code looks like this :
<ma-watch-list-get ng-model="designer.KNZ" parameters="designer.KNZ.parameters" on-points-change="designer.KNZ.points = $points" id="KNZ_ID" watch-list-xid="KNZQueryWL" ></ma-watch-list-get>
<ma-watch-list-get ng-model="designer.MAT" parameters="designer.MAT.parameters" on-points-change="designer.MAT.points = $points" id="MAT_ID" watch-list-xid="MATQueryWL" ></ma-watch-list-get>
<ma-watch-list-get ng-model="designer.WR" parameters="designer.WR.parameters" on-points-change="designer.WR.points = $points" id="WR_ID" watch-list-xid="WRQueryWL" ></ma-watch-list-get>
<ma-watch-list-get ng-model="designer.FM" parameters="designer.FM.parameters" on-points-change="designer.FM.points = $points" id="FM_ID" watch-list-xid="flowQueryWL" ></ma-watch-list-get>
<ma-watch-list-get ng-model="designer.KAR" parameters="designer.KAR.parameters" on-points-change="designer.KAR.points = $points" id="KAR_ID" watch-list-xid="KARQueryWL" ></ma-watch-list-get>```Hi Richard
I believe, you do not need your query string function as there is already a component for this. You will need to register you page with the URL of ?page
<ma-state-params on-change="PageStart = $stateParams.page; stateParams = $stateParams" update-
params="updateParams"></ma-state-params>
Here is a help document that explains how to use it with a watchlist:
https://help.infiniteautomation.com/linking-to-dynamic-pages
Hi @bullitbd
The following functions are available in the scripting enviroment. So you could use a meta point to watch if your process is running and then enable the relevant data source. then disable it when the process is not running. Data sources do take some time to start so you might need to look at how you could get a signal before the process starts.
isDataSourceEnabled(xid)
xid - Xid for a data source return true if enabled false if not or DNE
enableDataSource(xid)
xid - Xid for a data source, return status
disableDataSource(xid)
xid - Xid for a data source, return status
isDataPointEnabled(xid)
xid - Xid for a data point return true if enabled false if not or DNE or User does not have permissions
I looked into this and I am able to get delays longer than 5 seconds but the max delay possible is the update interval of the context point. If you go to the administration --> system status --> work items you will see only one work item is created for each meta point XID: Meta delay for DP_b2fc2661-2f8a-4054-9d62-8e7224fef067. If the delay period is longer than the update interval then the old work item gets cancelled and a new one is created and scheduled for update time + delay.
Hi @iperry
Do you plan on dynamically editing the SVG to add more elements or dynamically adding SVG's to the page.
Not sure how you have structured your SVG and if new sensors have a relation to the existing sensors ie: connecting pipes or lines ect.
You could do a ng-repeat and dynamically add smaller SVG's for each sensors data that comes from the pages query.
@ddukaric you will need to configure the proxy to allow websocket upgrades.
The reports module is not supported in v4. How did you load the module?
This is a feature that will be in 4.0. you will be able to configure which tags should appear on menus. For 3.7 you will need to work around it as @MattFox pointed out.
@brownbucks11 The only issue I can see from the pic is that you have not. selected which point should trigger the script to update. At least one of the update check boxes should be checked.
Please add your ma.log file to the post
@cmusselm Mango will not be able to bind to port 80 unless the root user starts it. This is a Linux permissions issue. You will need to use IP tables to route port 80 to port 8080
You should see an error like this in the ma.log
ERROR 2021-06-02T21:15:48,714 (com.serotonin.m2m2.Main.main:162) - Error during initialization
java.io.IOException: Failed to bind to /0.0.0.0:80
Hi Ricardo
It looks like your core did not update, I would expect this to happen if you did not change the production release to development. To fix the issue you will need to down load beta 12 from here: https://maven.mangoautomation.net/repository/ias-release/com/infiniteautomation/mango/mango-bundle/4.0.0-beta.12/mango-bundle-4.0.0-beta.12.zip
Delete all the modules in your faulty installation and replace them with all the module zip files from the beta 12 down load.
if you want to then upgrade to beta 14 you will need to change the production release at administration-->system settings--> system information to development. Then go to the modules page and check for upgrades. Make sure that you are upgrading the core aswell
Hi Ricardo
Can you paste the whole log file here. I wonder if the core did not get upgraded? There is also an issue where if you have the twilio module installed mango will not start.
@tecova I have responded to your support ticket. We will handle it from the support portal.
It is the exact same concept.:
<ma-state-params on-change="designer.parameters.dn = $stateParams.dn" update-params="designer.updateParams"></ma-state-params>
this component takes the URL parameters and puts them into a object called designer.updateParams. That object can be used anywhere now in the pages scope.