Bad data, it happens to us all. Doing some testing or a sensor fails and goes out of range - but not far enough to be discarded.

This can completely mess up the trending display, as it is doing to me right now. Even when rejecting extreme values, sometimes a glitch can return a value that is not extreme enough to be discarded, but well out of the normal operation of the process resulting in the scale being thrown off every time you try to view historical data.

I have done the export/reimport CSV thing before but this is honestly a very clumsy and slow way of editing the history, and the interface has changed somewhat to the point where I had to hand-edit my CSV last time I did it.

Is there an easier way to do this with an SQL query? I have tried modifying the pointvalues table, where the bad data point seems to be easily found with SELECT * FROM pointvalues WHERE pointvalue = $baddata;

However UPDATEing this value does not seem to result in anything changing on the charts? Is it cached somewhere or stored in another location?

Thanks

Thanks! I won't bother messing around with it then. The best way to implement it would probably be so that the administrator can configure it from the "Event audio files" section on a per-level basis, i.e. warning could be set to only be played once, but life safety would repeat indefinitely. This would save the operators from the annoyance of low level alarms repeating.

Oops, the default setting for both the admin user and newly created users is "Muted". Missed that. Yes, the new UI will sound audible alerts (once) once I un-muted the users.

Looking at activeEventsIcon.js and eventAudio.js it looks like it would make more sense to modify eventAudio.js seeing how it is sitting on the toolbar beside activeEventsIcon. It's already set up with features like isCurrentAudioPlayer() so that it doesn't play in every tab. And if I unmute the users and modify activeEventsIcon then I'm going to end up running two instances of audio.play() on the first run, which will clash with each other for a nasty sound.

Before I start trying to break my copy of eventAudio.js though, I'll wait and see if you guys are planning to add an option for a repeating alert. Makes more sense than me making an internal change that could be broken every time an update comes out. Thanks for your help!

This almost works. It does cause the audio to repeat until acknowledged. If you acknowledge the event from another tab, it works as expected.

However, if you click the events icon on the page that is playing the audio, it appears that the interval() persists but the rest of the script passes out of scope (I do not know JS at all by the way, I usually do embedded not web development) Now, when the event is acknowledged, that ACKNOWLEDGED is not detected. The audio will continue to repeat until the tab is closed. So, I was wondering if there are some simple alarm flags as well, or is there only this subscription based interface?

It seems a bit odd to me that the Mango new UI has no audible alerts built in. They are present in the old UI, work from every page and will continue to sound until acknowledged or silenced. To me this is the expected behaviour from an audible alert, and is necessary especially if a safety alarm is raised and the operator is not immediately present. Was this a design decision in the new UI?

I've installed the user module that was supplied here: https://forum.infiniteautomation.com/topic/2986/events-table-refreshing/4

It works, but it only will chime once, when the alert is first thrown. This appears to be how it is supposed to work.

I don't know what internals of Mango this script hooks into, but is there a way to change the script such that the audio sample will continually retrigger (every x seconds let's say) until the event is acknowledged?

The URL parameters method is exactly what I was looking for and it's working perfectly. Thanks for your help!

The online documentation you linked appears to contain some information that isn't included in the local help files. I'm going to have to read through it as I just learned how Rollups actually work and why I would use them.

Hi, I'm new to Mango but seem to be getting the hang of the system pretty well.

Right now I'm trying to set up a remote dumb display that hangs on a wall and displays the fill level of several tanks. I want it to be completely hands-off, boot on power-up, no keyboard or mouse intervention required. Just a basic display so that the guys can see the tanks at a glance.

Right now I'm trying it out with Porteus Kiosk on a laptop. Porteus Kiosk boots off a read-only filesystem, starts a browser and opens a page that is burnt into the filesystem. As such, there's no way to log in to Mango and no way to persistently store the autologin cookie.

I thought there was a way to make a view accessible to anonymous users but it is not obvious. Is there a simple way to do this?