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.

The bug was in the Meta module. I didn't put it in the store yet, nor did I backport to the 2.8 Meta module.

This worked for me. Thank you!

BTW we had rest.customDateOutputFormat already specified in our env. properties file, it was just the wrong format. So the hard coded defaults are probably fine.

Hi Terry,
Thank you for the quick response. I have just tried this on another PC and I don't get the error so it must be something cached.

Thank you for your help!
Matt.

OK. In any case the current JSON retriever works fine in 3.2.

I find this tool to be very helpful to quickly get the correct slashes for the pointers:

www.jsonpointer.com

Hi Frank, welcome to the forum!

The module doesn't support this currently, and it wouldn't be trivial to achieve through the scripting options.

It looks like the protocol implementation library, DNP34J, does support setting time out to a device, but not synchronizing (it does identify these as distinct, but doesn't implement synchronizing). It didn't look like it would be too much work to wire this up. I've sent you an email with a few modifications to have a button to send the time out and some questions and whatnot. Let's communicate there and see if we can get this feature added.

Oh! @phildunlap I didn't realise thats what that button was for.. haha!

Thanks again, and thanks very much for the script too!

Cheers!
-Shaun

Yeah you will definitely find some things that don't render properly in Edge, I would recommend using Chrome or as a second preference Firefox.

@phildunlap Many thanks, at least we all know now and if anyone hits this snag they'll find it here.

Matt

Glad to hear it! Thanks for bringing this to our attention.

@silvia thanks fixed for next release. I think we will also have to try and compile each element individually and catch the errors in the future so this sort of scenario doesn't repeat itself.

Thanks. That makes sense.

pjc

Hi Phil,

Sorry but I have already finished with my project and set it up for my client after I noticed the upgrade.

I will try it on my next upcoming project.

I guess if you have fixed it then its okay, I was just bringing it out as I noticed it was behaving strangely.

Thomas

Ok i understand.
I thought that the Publisher send one requet per point but it send a lot a point on one request. We have change the php script to catch all values and now it's ok. Thanks !

A couple of things you could check would be the logging setting on each data point. Your Compressor Call (Binary) should be set to "log on change" And your KW will probably be on a 1 minute average or something like that.

The other thing that would be good to do would be to export the data for that same chart as Excel so the time stamps can be verified independently of the chart to see if the data is just being displayed incorrectly on the chart but actually saved in the database correctly.

Hi FlexBob,

Do you have any data type exception errors in the log for the data source? The event message text contains "Script data type error setting point". What is Baro_Pres_DAQ's data type?

Any response? Yes/No/Maybe?

PS: I know that this might be troublesome for the Mango Startup / Shutdown notifications.