• MattFox

    @phildunlap said in Google Cloud Big Query module for accessing/storing data:

    Always a good plan. Although, one could argue it's overkill if you're automating someone's home greenhouse, for instance

    Without going into too much detail of the company model, let's just say we're in the agricultural sector in multiple areas.

    @phildunlap said in Google Cloud Big Query module for accessing/storing data:

    The API can enable you to get the values out. Querying the API is lighter than using the UI (since the UI is built on top of the API + registering for websockets).

    This could be quite beneficial for me, I'd just have to work out what language/framework to use to provide what our customers need,..

    @phildunlap said in Google Cloud Big Query module for accessing/storing data:

    The NoSQL database has a sustained performance of wicked fast. What data tools would users be accessing from?

    Good to know, just that since that users access their data direct from a web browser desktop/mobile it would be good to provide read access with minimal overhead. I am finding that there are issues with connecting to mangoUI via a rural internet connection. Trying to load the now condensed down mangoservice and mangoUI files generally throttles the connection and stalls it...

    @phildunlap said in Google Cloud Big Query module for accessing/storing data:

    We have quite a few systems with a lot of points (more than 3000). If you tune the overlap window in the persistent publisher it's pretty dang efficient, and I wouldn't worry too much about it unless your system is already bogging down sometimes.

    Where can I read or can you email me a guide? Sometimes what's in the mango help and on the help.inifiniteautomation.com site varies a little. Would be good to get as much as I can out of my system. (Currently two cores with 15GB of memory)

    @phildunlap said in Google Cloud Big Query module for accessing/storing data:

    It sounds like you're talking about three Mangoes to me. Two on site, with one being a redundancy if you're updating or the primary goes down, and one in the cloud. Then the one in the cloud needs to be able to serve data to your clients the way they want to consume it. So, what way would they want to consume it?

    Technically, one on site for the customers that want/need it. A server in google cloud and another based here.
    I'm doing my darnedest to automated and streamline as much as I can as I'm a one man band. Hence my arguable over-concern for redundancy.

    @phildunlap said in Google Cloud Big Query module for accessing/storing data:

    Rereading the title, I think I may have been missing something in my previous posts. I am familiarizing myself with Big Query a little better.

    Thanks, hugely appreciate you taking me seriously.

    posted in Wishlist read more
  • MattFox

    Sure Phil happy to!

    1. The idea is that only one mango unit will be writing at any one time, i'll likely have some form of redundant network configured in order to switch between the two systems when I take one down.
    2. I want to focus on using the mango as more as a control/data collection system and having the means for my customers to be able to access their data from a different server.
    3. However I cannot do this if it's being stored in a nosql system that only mango can access. I have considered using cloudSQL as it would mean I could have two live systems reading the data but it does not scale well long term and I can envision my data tripling within the next four to six months.
    4. By doing this, it takes the overhead away from mango for retrieving datasets and will allow me to segment my system a little better.
    5. I've considered using a publisher but I already have a fair few going. That and I'm not sure how well it will work if I'm pushing the updates of nearly 3000 points...

    posted in Wishlist read more
  • MattFox

    Looks like a load of missing menu items to me.
    If you can edit the JSON, Amend it to this:

    {
    	"menuItems": [{
    			"name": "ui.dataPointDetails",
    			"permission": "superadmin"
    		},
            {
                "name": "ui.events",
                "permission": "edit-ui-pages"
            },
            {
                "name": "ui.watchList",
                "permission": "edit-ui-pages"
            },
            {
                "name": "ui.settings",
                "permission": "superadmin"
            },
            {
                "name": "ui.help",
                "permission": "superadmin"
            },
            {
                "name": "ui.docs",
                "menuHidden": false,
                "permission": "superadmin"
            },
     {
    			"name": "ui.plantaDeTratamiento",
    			"url": "/planta-de-tratamiento",
    			"linkToPage": true,
    			"permission": "user",
    			"menuText": "Planta de Tratamiento",
    			"pageXid": "cd3b879e-125a-4544-9df4-7b7479b6c017",
    			"menuHidden": false,
    			"weight": 1000,
    			"abstract": false,
    			"menuTr": "Planta Tratamiento"
    		}, {
    			"name": "ui.estacionbomb.acueducto",
    			"url": "/acueducto",
    			"linkToPage": true,
    			"permission": "user",
    			"menuText": "Estacion Bombeo",
    			"menuTr": "",
    			"pageXid": "3efbd854-5e20-4fc7-8e78-a7a1d4ce15f1",
    			"menuHidden": false,
    			"weight": 1000,
    			"menuIcon": "E",
    			"abstract": true
    		}, {
    			"name": "ui.estacionbomb.acueducto.estacionbomb",
    			"url": "/estacionbomb",
    			"linkToPage": true,
    			"permission": "user",
    			"menuText": "Estacion de Bombeo",
    			"pageXid": "3efbd854-5e20-4fc7-8e78-a7a1d4ce15f1",
    			"menuHidden": false,
    			"weight": 1000,
    			"abstract": true,
    			"menuIcon": "E"
    		}
    	]
    }
    
    

    posted in User help read more
  • MattFox

    Focusing on the big picture and wanting to have redundancy in mango system to ensure I can guarantee 100% uptime for 6 crucial months of the year, it would be good to be able to run two mango instances that can talk to the same data set and update values. Ideal when I'm running code updates or upgrading mango/Linux.
    I'd be keen to know other people's thoughts.
    Fox

    posted in Wishlist read more
  • MattFox

    Nicely identified Phil, glad I could be of assistance,

    posted in Mango feedback read more
  • MattFox

    Well I toggled it to inactive, but my info logs still kept notifying me of it firing/finishing (i set up both to confirm if I could use it like a flip flop during different parts of the day). maybe it's not actually setting it to inactive outright?

    EDIT: Strange, I implemented it the same way again to see if I would have the same outcome but can no longer replicate it....
    I'll watch closely, but in the meantime, that fix you mentioned will definitely help.

    posted in Mango feedback read more
  • MattFox

    ^ What he said! (hahaha)

    posted in User help read more
  • MattFox

    Anytime, always here to assist.

    posted in User help read more
  • MattFox

    Hey @phildunlap, could you do me a favour and check the advanced scheduler code as well?
    I may be using 3.4.1 and thus you may have fixed it. But when I had a schedule set to inactive, the events still kept firing also.

    Thanks
    Fox

    posted in Mango feedback read more
  • MattFox

    @sbaik said in Drop Down Navigation:

    SS and HTML following some tutorial and it results in a list with offset bullets.

    If you're going to go down that route, ensure your css has:

    <style>
    li
    {
    list-style:none;
    }
    </style>
    

    The beauty of having ng-click events mapped to menu over items is because then you can make your screen compatible with touch devices. ie open menu, close menu.

    This is a bit of a hack but keep things simple and utilise the tools already provided:

     <!-- Trigger element is a md-button  -->
     <md-menu>
     <ma-button ng-click="$mdMenu.open($event)" class="md-icon-button"label="FLUORIDE" aria-label=FLUORIDE">
     </ma-button>
     <md-menu-content md-menu-align-target="bottom">
       <md-menu-item>
       <ma-button style="background-color: rgb(0, 128, 255, 0.9);" ui-sref="flourideWest" label="West Fluoride"></ma-button></md-menu-item>
    <md-menu-item><ma-button style="background-color: rgb(0, 128, 255, 0.9);" ui-sref="flourideEast" label="East Fluoride"></ma-button></md-menu-item>
     </md-menu-content>
    </md-menu>
    </div>
    <style>
        .md-open-menu-container.md-active{
      margin-top: 45px !important;
    }
    </style>
    

    it's a click to open, simple click off or on the menu button itself to close it.

    posted in User help read more