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.

Hi sbaik,

Have you seen this thread about using the JsonEmport tool in scripts? https://forum.infiniteautomation.com/topic/3708/a-script-jsonemport-example

@sbaik said in filter points being used in graphics:

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

There's no easy way unfortunately. The only suggestion I could give you would be to open your dev tools and look at the network requests your dashboards are making. You will see requests to /rest/v2/point-values/time-period/{xid} for example when its fetching point values for a particular point. You can also find the websocket for live point value updates and see what XIDs it is listening to -

0_1542409809862_e6672f1a-3cc9-4f2e-b834-e2cae9bd6803-image.png

Glad to hear it!

@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 had missed setting the permission for the JSON store UI pages and UI menus as you suggested.

Thanks Phil.

Hi sbalk,

You're looking for this thread:
https://forum.infiniteautomation.com/topic/3551/data-sources-does-not-appear

TLDR known issue, fixed by updating the xstyle library in the web directory, can be done on 2.8 instances or instances that aren't otherwise staying up to date manually with Jared's suggestion at the end of the thread.

Anytime, always here to assist.

@Jared-Wiltshire how to change the time? It should not use "now" - instead a fix time like 06:00 a.m.

Thanks!

A multi-state meta data point would probably be your easiest option.

Add the 4 binary data points as context points. The script would look something like this -

var a = contextA.value << 0; var b = contextB.value << 1; var c = contextC.value << 2; var d = contextD.value << 3; return a | b | c | d;

If you set it too high you'll be more likely to crash a browser.

@sbaik said in Button graphic layover:

@jared-wiltshire said in Button graphic layover:

@sbaik It doesn't have to be used in conjunction with a <ma-button> you can use it on any element/component. Try it out.

I must have tried to use it on other components before it was added as a directive. It works perfectly now. Thanks

No problems.

@jared-wiltshire said in Dashboard Designer Choose page to edit unresponsive:

@sbaik I've released dashboard designer v3.4.2, can you try that version for me please.

Both switching between pages to edit and going from markup back to page does not create any error and functions fine.

Thanks Jared!

@sbaik said in Custom Page disappeared:

I believe it was on an earlier version than 3.2. Perhaps it was deleted before I updated to 3.4 last week and just noticed it after.

Ah OK, that's probably it then. I feel confident we fixed the issue, let me know if you see anything odd again.

@mattfox Thank you for sharing that code.
As of this project, I don't think it would be cost effective for me to learn and redo all the pages just for the drag to zoom function on a chart.

@jared-wiltshire

Thank you, that is exactly what I was missing. I tried ma-get-point-value, but did not know to put "point.setValue(true)" in the ma-button markup.

@MattFox I double checked the menu item permissions and it was correct @phildunlap This was exactly it. I overlook the JSON every time. Thank you!

No problem, I'm glad you came right!

Brought them out of root level and now everything is great. Have some buttons assigned to specific date ranges on the page itself. Now if there's a way to hide the top blue bar, it will be perfect.

That makes more sense than it being a timeout. A timeout would have produced a ModbusTransportException with timeout as its message, not an operating system message about a file descriptor having issues.