Please Note This forum exists for community support for the Mango product family and the Radix IoT Platform. Although Radix IoT employees participate in this forum from time to time, there is no guarantee of a response to anything posted here, nor can Radix IoT, LLC guarantee the accuracy of any information expressed or conveyed. Specific project questions from customers with active support contracts are asked to send requests to support@radixiot.com.

@cmusselm that setting may help depending on what you are doing. That setting will effectively send a short value to a register if it is 2 bytes according to the point locator's modbus data type. If it is > 2 bytes then no matter what it will send an array to the slave and likely will write > 1 register.

Ahh! That make sense. Thanks @MattFox !

Appreciate it @mattfox !

@mattfox thanks,I tested it your way and got some ideas

Use maStats (the statistics directive) and get the max value over your monthly time period.

Fox

02e1fb21-f4ca-4a17-874b-aec38f17d8eb-image.png

File store is on system running mango under the /opt/mango/filestore
You'd require those files as well as the SQL database.

Fox

Thanks for your reply and adding the noSQL licence, @CraigWeb!

Regarding the other error: I wanted to migrate existing H2 data into noSQL and was mislead by the documentation:

The NoSQL migration can take several hours to complete but it will happen in the background.

My bad -- I thought it was a one-click solution given, that Mango knows which DB it is using and what the credentials are. Will report back when I had access to the client's server again. Thanks again for your help!

@cwangv
Actually, Mango logs audit events for edit, delete, create user actions.

You are correct. Set each user in their respective timezones. Mango system will continue to use system timezone unless explicitly specified in the env.properties file.
I half wonder if your mango system should run GMT then all offsets are based from a zero offset per user rather than an offset of an offset..

Fox

This.. Is a Spicey MeatBall Solution..

So:
(1) The 3.7.7 release has a broken Excel importer, since it's on its way out, anyways.
(2) The only way to modify existing points is to use the REST API as an admin and delete point values using XIDs?
(3) I really don't want to delete.. I want to export, filter, and re-import. I suppose I could do the filtering on a Meta, and "generate history", but there's no way to move that back into the Active polled point, which is used elsewhere in our system for doing other math-related things.

I really think there needs to be some way to do this sort of bulk "export / filter / re-import" way native to Mango..

This, and the benefits of Copy and Paste at the data source level, are two things that have been vanished from the Legacy interface that cause me no small amount of consternation.. I mean, the legacy UI could copy'n'paste data sources, which was a really easy way to roll things out. Now I'm exporting JSON, finding and replacing XIDs, and re-importing, which takes at least a billion times as longer than "copy, paste, rename".

Now I have to go whip up another external tool to Mango to do this export / filter / import thing? I mean.. I guess I can write a custom Excel importer using the "data import" thing, and pipe that back into the system... But the "remove" type of excel interface made this so it was a feature we were trying to sell as a benefit to fix this kind of data catastrophe, which happens more often than not.

Anytime

@craigweb Hi! Sorry about late answer. The root cause of the problem was finally tracked to our outstation which was using wrong DNP3 profile and since that we got only integer values through DNP3.

I appreciate your help on this:

I've been gradually rolling out Option (1), and it seems to work out ok. Seems to be it would be a Handy and Useful Feature to have an alarm point that would fail within the Persistent publisher itself when the link fails (for any reason). Maybe some people do persistent links that come up and down randomly through the day, but it seems that the persistent link feature is generally intended to be used.. Well, persistently.

Anyways, the not changed event detector option for the persistent metrics seems to do the job.

Thanks!

-Greg

copy the /opt/mango/web/modules/mangoUI/web/index.html
to /opt/mango/overrides/web/modules/mangoUI/web/index.html
and add your stylesheet link.
If you are able to pull all of the font files and the font-family stylesheet,
put them in here - Just downloading the stylesheet file won't work.

/opt/mango/overrides/web/modules/mangoUI/web/fonts/montserrat/style.css

the link in the index.html file will look like this:

<link rel="stylesheet" href="/modules/mangoUI/web/fonts/montserrat/style.css"/>

Fox