• T
    Turbo

    Greetings, all:

    I'm running Mango 3.7 right now:

    I'm wondering why my Mango Persistent TCP Tunnels don't seem to show alarms. I've got the "Event Alarm Levels" set for Urgent and Urgent for both Data Source Exception and Decryption Failed. We have one of our persistent tunnels offline due to perhaps a cell modem failure, and none of those alarms show in the "current alarms" panel on the Persistent publisher screen.

    What am I missing here? I'd like to get an event created when the Tunnel fails, so I can go start fixing the problem.

    posted in User help read more
  • T
    Turbo

    Thanks for the response--

    That seems unfortunate.. I know mango has a USER-CREATE-REPORTS type role for this kind of thing for report creation-- I don't think it's unreasonable to have a similar permission role for my users to be able to configure their own alarms.

    I suppose for now, that's where we are, but that means I need to hand out lots of superadmin to people, which is definitely not ideal.

    posted in User help read more
  • T
    Turbo

    Heya:

    I ran into similar issues with memory usage-- Notably, whenever one of our users ran one of their Big Excel Reports, the Available Memory would go to Zero, and the wheels would come off of Mango. We set our JAVAOPTS to be 10G, and those problems seem to go away.

    Mango uses Monster Amounts of Memory under certain conditions-- I'd say that you 1600Meg is too small. I've got site machines running with 2 gigs of RAM, and we use the JAVAOPTS small for that. Those sites only use the Modbus datasource, a handful of metapoints, and the persistent publisher. Even that seems to use all the available memory at times, and once Java takes RAM it never give sit back..

    Right now, our main machine is set up with 16 gigs of RAM, with only 174 megs free. The rest of that is JAVA, which is using 14.785 GB of RAM according to TOP.

    This peaks whenever a report is ran, but then Java never gives RAM back to the OS after it's taken. Right now, our JVM free memory is about 5 gigs, but that will go to < 2 gigs if one of these big reports gets ran.

    Cheers,
    -Greg

    posted in User help read more
  • T
    Turbo

    The problem here is that--- Well, something is ALWAYS broken, and always will be. I've got so far about two-dozen different sites, about half of them are running different types of machine, each with Serial Numbers started with 100 or less, which are constantly breaking in random / different ways.

    Here's how this works:
    I notice something like the watt/kw/whatever problem I described originally- Clearly, this is Broken, and isn't working right. Great. Now I know. It happens just often enough to Annoy Me, but not often enough that the people who make the equipment care. So, the People who Make The Equipment tell me things like "Well, you know you can only poll our equipment every 10 minutes on obverse full moon, or else it isn't going to work". So, fine, okay, I start polling every 10 minutes on obverse full moon cycles, and some other Dumb Thing pops up with that, so round around it goes again. Eventually I inevitably get the "we haven't seen this before", and then it ends, and it just stays Broken until I roll out metapoints or some other random workaround to get it working.

    No matter what, it seems to work for about 143 hours, and then they remote-update the firmware, and some other Damn Thing breaks, since everyone designs everything nowadays to basically require field firmware upgrades every 48 hours, which of course they DO, and then the wheels fall off some different point. "Oh yeah, we forgot to tell you that the current register is now expressed in mA instead of Amps, and the volts have been converted to ergs-per-unit area, because someone thought that was a good idea-- Also, if you don't read it every 10 seconds, the Inverter shuts down the Modbus and won't respond to polls again unless you power cycle the inverter and poll it within 30 seconds. That last thing ACTUALLY IS TRUE.. That was a Huge Pain to work out.

    While in principle I completely agree- I do need to know if Something is Broken. But I'm talking largely to Solar Inverters, in quantities of dozens at a time. The sales life of these machines is maybe 2-4 year, and then the manufacturers really don't seem to care about fixing Broken. So it falls on Me and Mango to report data the best I can, so that we can tell our customers when their machines are broken, and if so offer help in fixing them. I've had hours-long with most major domestic inverter manufacturers, and comms is like 80 on their list of things to fix. Or, they say "Well, you have to work with our Integration Partner, and pay them $12,000 for their Magic Box, which converters Modbus/IP to Modbus IP for some reason, and has their own firmware update cycle, and blah blah blah" Once the Next New Machine comes out, the tech support for previous machines instantly dries up, so no one cares about fixing these things any more.

    While I appreciate the Meta-pointedness gusto of doing such a thing in a metapoint, I already sink hours and hours into fixing and mapping broken and ill-defined modbus maps on a daily basis, and this includes doing metapoints for some of the most egregious examples of this. It's this use case that made me think that this would be a Feature that might make this a bit less ridiculous.
    By the same logic of that argument, why bother with the Discard Extreme Values, or prevent extreme sets options? Both of those could indicate malfunction, and be implemented quite easily as a metapoint as well.

    I guess I've kinda given up on "needing proof" that a communications interface / whatever is Broken. It almost always is. I'm trying to get Good Solid Data as best I can to run reports and analysis of the system as a whole, not to fight with disinterested inverter manufacturers about how to fix their kw registers.

    Cheers,
    -Greg

    posted in Mango feedback read more
  • T
    Turbo

    Greetings, all:

    I'm dealing with some Angry Devices that behave in annoying ways. An example of this behavior is a power register- It merrily reports 45.5 45.7, 48, 90.2, 46.1, 44.2... Or something similar. That 90.2 is NOT a real reading. Big Extremes I can toss out with the "Discard Extreme Values"- This is very useful when some of these machines end up writing Full Scale INT to their registers at the end of the day. However, for these random within-range random excursions, there's no reasonable way to filter this out.

    It's not possible for some of these data points to change from 45.7 to 90.2 (for example) in the space of a single poll cycle, so that data is clearly errant. But it's still in the reasonable range of data points values that would be expecting for that data point, so Mango merrily logs it.

    Such a setting maybe to "Discard values where delta is greater than X" for each point. Then, for that device, I could stick like "10" in there that would prevent those errant writes from getting into the database.

    I see this on some temperature channels as well, where suddenly the temperature will go from 45C to -0.1C in a single 5-second poll. Unless Elsa released her Freeze Powers on that particular sensor, that's not a real measurement. It's an annoying problem right now, since these things sort of pollute the database with hard to post-process trash.

    Cheers,
    -Greg Linder

    posted in Mango feedback read more
  • T
    Turbo

    Greetings, all:

    I've set up several Persistent TCP connections, and noticed that the Old UI lets you save a publisher with a Minimum Overlap of 0, and flags no error. The New UI forces you to enter in an Overlap of greater than 0.

    Dunno if this is a bug, but it is a difference in how this stuff behaves.

    -Greg

    posted in Mango feedback read more
  • T
    Turbo

    I agree with this-- This is an issue I see as well.

    Would nice to have another format for this thing.

    Cheers,
    -Greg

    posted in Wishlist read more
  • T
    Turbo

    Greetings:

    I gave up on using the built in Units in Mango. They seem to be.. Sort of broken and generally annoying, since there never seems to be the right M/k/u/m type for whatever I'm doing-- Megawatts, kilowatts, whatever. The Best Practice seems to be to just use the Text Renderer Properties, and set the Suffix to Whatever unit you want.

    I tried using the built-in units a number of ways, but I got tired of dealing with the little "dot" for multiplied units which really aren't. I don't remember which unit, but it was something like kwh showing as kw<dot>h.. It's not kilowatt TIMES hours.. Anyways. I've run into trouble with import/export also using built-in units, where m^2 doesn't import right under some conditions (for example). Don't have these troubles using the "text renderer properties" Suffix box

    Yeah. The general practice seems to be "use the text renderer properties"... Makes your life easier.

    posted in Mango feedback read more
  • T
    Turbo

    Greetings, all:

    We have a bunch of event handlers create in the old Mango UI. I have users I created that are able to modify and create those events, but when they try and use the new UI to create new event handlers, I get an error that says the user doesn't have the proper role.

    Which role do I need to assign to my users so they can create and modify event handlers?

    Cheers,
    -Greg

    posted in User help read more
  • T
    Turbo

    Excellent.

    This would be a Very Useful Thing to have..

    Cheers,
    -Greg

    posted in User help read more