Update on a really old thread. There was just no option for me to change anything on the PLC side as mentioned before but figured out a workaround.

The problem was that the pump could not be started if the stop bit held the 1 (or stopped if the start bit held the 1) You can visibly see a stuck button if the bit held the 1. The same button could be pressed again to attempt to write a 0 at release.

But instead of explaining that process, I am having the momentary of the start write a 0 to the stop and the stop will write a 0 to the start. This ensures the end user uses the buttons as intended without having to worry about stuck button or held bits. Seems to work fine.

@phildunlap They are Modbus I/P. I don't see anything that happened to that device during that time that it was stuck (2/17 9:33pm.) but there are a lot of events. Most of them are "Exception from modbus master: socket closed, or Bad file descriptor (ioctl FIONREAD failed)

@phildunlap said in Momentary Button Bug?:

Hi sbaik,

What kind of point is it? To me, that sounds like the button release tried to set it back to 0, but there was perhaps a transport exception and so that write didn't make it to the device. If you have the write error events above 'Do not log' for the data source you would be able to find a record of the failure in the events.

@phildunlap Where do I set the write error events? I'm not seeing it in the data source or the points.

Hi,

Here's the markup of the start stop for a pump. They are linked to image of a button. Picture attached. I could not replicate it, so I don't think it was Mango, but I wanted to double check.

<!--pump5 start-->   
    <ma-get-point-value point="point" point-xid="PLC1_e5_start"></ma-get-point-value>
    <ma-switch-img id="76156244-402f-41ee-8327-b17d70fbcb94" style="position: absolute; left: 1349px; top: 535px; width: 80px; height: 80px;" src-false="/rest/v2/file-stores/default/Start.png" src-true="/rest/v2/file-stores/default/Start-depressed.png" ma-momentary="" ma-momentary-start="point.setValue(true)" ma-momentary-end="point.setValue(false)" point-xid="PLC1_e5_start"></ma-switch-img>
<!--pump5 stop-->
    <ma-get-point-value point="point1" point-xid="PLC1_e5_stop"></ma-get-point-value>
    <ma-switch-img id="5260d0ff-65e1-4adb-9fe4-76ecb9b12fda" style="position: absolute; left: 1349px; top: 619px; width: 80px; height: 80px;" src-false="/rest/v2/file-stores/default/Stop.png" src-true="/rest/v2/file-stores/default/Stop-depressed.png" ma-momentary="" ma-momentary-start="point1.setValue(true)" ma-momentary-end="point1.setValue(false)" point-xid="PLC1_e5_stop"></ma-switch-img>

These have momentary button function where the point writes a 1 for the duration of the click, however long, and goes back to 0 when released. This was done with the help of this forum. We fixed bugs like if it was clicked, held, and dragged away and released, it still went back to 0.

Couple of the points shown in the picture of the history, you can see that it was set back to 0 after the momentary 1, then goes back to a 1 without indication that it was set by a user, and stays that way until I was notified and changed it back to a 0 using the detail page.

Any ideas? These are huge pumps (some of them 600hp) and these controls are critical...

I eventually found out what you meant by roll up. Points had default roll up which was none. Now all the trends charts work flawlessly. Just got done with the project and we have happy customers thanks to you guys.

The quick response to all questions and concerns is great.

Re: How to bulk-import event detectors?

Is this possible now?

Just got all the pages done, now need to start text/email alerts. I have done point by point on smaller sites, but this project has hundreds I need to add event detectors to.

Thanks,

Is there a way to sort all points being used in the custom page graphics?

In one of the instances of Mango, they had uploaded hundreds of points from multiple PLC's. I came into the project half way through and almost done with setting up their pages and would like to delete the unused ones.

A lot of them are duplicates such as a numeric value before and after scaling in the PLC of which only the scaled value is used.

@sky_watcher I've done something similar just with permissions.

You can edit the access permission of the custom page so that button will not redirect the users without permission to the target pages.

@phildunlap Roll up as in choose a date and time to look at the value of the point at that time?
End user is wanting to just hover through the chart and observe the values quickly. It appears to be glitchy to them and was brought to our attention. If the resolution is decreased for the hover view and populate the nearest value of all the points at the time whether it'd be every second or 5, that would be great.

Thanks,

@phildunlap Is there a way to decrease the resolution so that couple of millisecond misalignment does not cause this?

What makes the value tag pop up while hovering the cursor over the trends on a watchlist? It doesn't populate on every point/line in the watchlist and not on the same time x-axis value so it pretty much just sporadically blinks as you hover left to right.

The points being trended are on the same source with the same update rate.

@phildunlap I guess the thought was to have the function built in within Mango to not rely on the browser. In the case that the user needs to switch browser, clear cookies, or something to that aspect. But I did not consider the vulnerability of network information. Will talk it over with our tech director some more.

I know there is the auto login function now that stores credentials in the browser cookies, but would it be possible to add a built in function of auto login looking for a static IP or MAC address machine?

We are wanting the users to only have writable access at 2 specific machines inside the control room without knowing the credentials of the login. We provided a read only user to monitor using handheld devices.

@jared-wiltshire

Thank you for the quick response. That worked beautifully.

@jared-wiltshire said in Custom range date picker buttons:

See the ng-init? Set it to ng-init="dateBar.preset = 'LAST_1_DAYS'"

I thought this had worked but apparently not. I'm not sure if it has to do with the fact that the custom pages are a root page to hide the side and top bar, or something else.

It does populate the point name with the colored squares at the bottom of the chart but it does not populate the graph itself until one of the date buttons is clicked.

<div class="ma-designer-root" id="6bdb9bd5-45a2-4d17-a299-086cb5416f5e" style="width: 1920px; height: 980px; position: relative; background-color: rgb(0, 130, 125); font-size: 30px;" ma-center="true" ma-scale-to="ma-ui-page-view" ng-init="dateBar.preset = 'LAST_1_DAYS'">

<!--Trends-->
<ma-now ng-if="!dateBar.preset" update-interval="5 seconds" output="now" on-change="dateBar.from = ($value | maMoment:'subtract':numDays:'days'); dateBar.to = $value"></ma-now>
<ma-button id="9cc2c144-4df9-41de-bb79-523016daa8b1" raised="true" style="position: absolute; left: 1017px; top: 729px; font-weight: bolder;" label="Last 1 day" ng-click="dateBar.preset = null; numDays = 1;" hue="hue-2" palette="warn"></ma-button>
<ma-now ng-if="!dateBar.preset" update-interval="5 seconds" output="now" on-change="dateBar.from = ($value | maMoment:'subtract':numDays:'days'); dateBar.to = $value"></ma-now>
<ma-button id="9cc2c144-4df9-41de-bb53-523016daa8b1" raised="true" style="position: absolute; left: 1017px; top: 780px; font-weight: bolder;" label="Last 2 days" ng-click="dateBar.preset = null; numDays = 2;" hue="hue-2" palette="warn"></ma-button>
<ma-now ng-if="!dateBar.preset" update-interval="5 seconds" output="now" on-change="dateBar.from = ($value | maMoment:'subtract':numDays:'days'); dateBar.to = $value"></ma-now>
<ma-button id="1209dae7-9cf8-43fb-8f26-e9650eeae913" raised="true" style="position: absolute; left: 1017px; top: 831px; width: 104px; height: 48px; font-weight: bolder;" label="Last 3 days" ng-click="dateBar.preset = null; numDays = 3;" hue="hue-2" palette="warn"></ma-button>
<ma-now ng-if="!dateBar.preset" update-interval="5 minutes" output="now" on-change="dateBar.from = ($value | maMoment:'subtract':numDays:'days'); dateBar.to = $value"></ma-now>
<ma-button id="1209dae7-9cf8-43fb-8f26-e9650ehrw913" raised="true" style="position: absolute; left: 1017px; top: 882px; font-weight: bolder;" label="Last 1 week" ng-click="dateBar.preset = null; numDays = 7;" hue="hue-2" palette="warn"></ma-button>
  
<ma-watch-list-get ng-model="watchList2" on-points-change="watchList2Points = $points" watch-list-xid="LocalTankLevel"></ma-watch-list-get>
<ma-watch-list-chart id="tank1" watch-list="watchList2" points="watchList2Points" from="dateBar.from" to="dateBar.to" rollup-type="dateBar.rollupType" rollup-intervals="dateBar.rollupIntervals" rollup-interval-period="dateBar.rollupIntervalPeriod" simplify-tolerance="dateBar.simplifyTolerance" style="position: absolute; width: 750px; height: 400px; left: 1141px; top: 129px; background-color: rgb(36, 36, 36); z-index: 0;" ng-init="dateBar.preset = 'LAST_1_DAYS'"></ma-watch-list-chart>
<ma-watch-list-get ng-model="watchList3" on-points-change="watchList3Points = $points" watch-list-xid="43PSPressure"></ma-watch-list-get>
<ma-watch-list-chart id="tank2" watch-list="watchList3" points="watchList3Points" from="dateBar.from" to="dateBar.to" rollup-type="dateBar.rollupType" rollup-intervals="dateBar.rollupIntervals" rollup-interval-period="dateBar.rollupIntervalPeriod" simplify-tolerance="dateBar.simplifyTolerance" style="position: absolute; width: 750px; height: 400px; left: 1141px; top: 552px; background-color: rgb(36, 36, 36); z-index: 0;"></ma-watch-list-chart>
<div id="5d6fde5a-5bc4-4bcc-9cce-5ee6481813fd" style="position: absolute; left: 1398px; top: 552px; color: rgb(255, 254, 254); font-size: 25px; font-weight: bold; width: 250px; height: 24.1406px; text-align: center; z-index: 2;">PRESSURE</div>
<div id="40b6ab15-6a7f-41f5-8c30-d50f8c196d38" style="position: absolute; left: 1398px; top: 129px; color: rgb(255, 254, 254); font-size: 25px; font-weight: bold; width: 250px; height: 24.1406px; text-align: center; z-index: 2;">TANK LEVEL</div>    
</div>

What it should look like, or what it looks like after pressing button

I had missed setting the permission for the JSON store UI pages and UI menus as you suggested.

Thanks Phil.

Created a permissions profile named readonly.
All the points has view permission set to user and readonly and the set permission to user.
All the pages I have has view permission set to user and readonly.

I created an account with the permissions readonly and the Home URL to point to a page called Overview.

When I login with said account, it populates a "Page not found"
If I delete everything after .com, it will go to the Overview page and everything functions as it should as "readyonly"

Now if I set the user account permission to user, the Home URL works fine.

Is there another layer of permission I need to add this new readonly profile to use the Home URL function?

Thanks,

Mango V3.4.5 works just fine on any browser. the 3.2.2 does not with with Chrome while it does with Firefox.

This is what I'm seeing on the console whenever I am trying to load edit data source or data points with Chrome. Mango version 3.2.2
element.style {
}
html, body, td, th {
font-family: Tahoma;
}
user agent stylesheet
html {
display: block;
}
display:
block
;
font-family:
Tahoma
;
height:
251.426px
;
width:
1013.75px
;

dojo.js?v=1514858302:324 [Deprecation] Synchronous XMLHttpRequest on the main thread is deprecated because of its detrimental effects to the end user's experience. For more help, check https://xhr.spec.whatwg.org/.
audio/information.mp3:1 Failed to load resource: the server responded with a status of 404 (Not Found)
2
VM54622:1 Uncaught ReferenceError: normal is not defined
at eval (eval at g (/resources/xstyle/css.js:NaN), <anonymous>:1:1)
at g (css.js.uncompressed.js:1)
at HTMLLinkElement.a.onload (load-css.js.uncompressed.js:185)
header.js?v=1514858302:193 Level1 Sound Failed to load
dojo.js?v=1514858302:1879 Error: timeout
at makeError (dojo.js?v=1514858302:106)
at dojo.js?v=1514858302:1641
dojo.js?v=1514858302:1882 src: dojoLoader
dojo.js?v=1514858302:1882 info:
Object
dojo.js?v=1514858302:1884 .

​

@mattfox Thank you for taking your time for that!