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.

@rob987 Hi, have you find solution for you JSON timestamp?

@kyle-Hughes its kind of hard for me to follow your configuration and identify what the actual problem is. Maybe you could do a diagram on how each Mango assets links together ?

@carnecro Not a problem, I would recommend upgrading to 4.5 there are 2 changes on the Bacnet module.

@MattFox yes we are aware of the email problem and are working on it.

@cbyrne I'd build an overridden mangoUI with development mode enabled, then you can do whatever you want, could likely also do a hack with the userModule, but the overriding would be giving you more freedom Fox

edit: nevermind just had to clear all browsing data.

@Turbo The behavior you described that causes the script to execute continuously; Is this by design? If so, can you explain how that works? The data source can either execute on an interval defined by the polling period or a context update from either an external point or an internal point. Both external points and internal points can be configured to trigger the script by checking the update context box. but if an internal point is configured to update the context and that point itself is updated by the script then there will be a cyclical situation. So the solution is to make sure that any point that the script affects does not have the "updates context" check box checked. Kind of difficult for me to follow and understand your 6 chained scripts, to be honest, but the first step is to make sure that you don't have a situation as I mentioned above.

@CraigWeb Hi, Craig Good to see you back on here. I will definitely submit this for my project since I have an existing Mango system running. Should I just get in contact with technical support?

@MattFox Fair enough- @nino-kurtalj said "Let's assume I have values in the W.".. Which I understood to mean he was using "watts" and it looks like he was trying to integrate watts over seconds in the metapoint he posted, using the now-last values as a sort of way to integrate watts into kwh. Also; @nino-kurtalj if you are integrating watts over time to get kwh, realize that you're accumulating errors as you go. It's much much better to use the raw kwh (or wh, or energy point) out of your metering device. This is because even integrated watts to kwh in mango, you're still limited by polling rate of your device. I run 1000's of points of energy and power in my system, and we can see the errors building up over time: Particularly when the power signal changes rapidly. The internal power meter kwh points (the "kwh" register you read out of your electrical meter) integrates at "electrical speed", so they catch those wiggles in real time: They basically sum every update of some high-speed V*A calculation. If you're reading watts and integrating that into wh youself, you can only get those values every time you ask the meter for it, so you'll miss the little wiggles that happen in between polls. If you're polling every second, this will probably be a fairly small error, but it grows over time, so if you go true up your integrated watt -> kwh point by comparing it to like the power company's billing meter, you'll always be off by a few percent. The slower the watt polling interval, the larger that energy error is at the end of the month. I run into this (and deal with this) all the time in the business I'm in, since some people insist on taking (for example) 15-minute average kilowatt, summing them up, calling it kwh, and then complaining to me that my energy points are wrong- They aren't. They're just integrating a low-frequency discrete time signal and comparing it with an integral at real time as the signal changes: They will not be the same. That error can cause lots of confusion, if you're (for example) trying to calculate your AC line losses over time- The error in going from 15-minute average power into kwh is generally larger than the actual losses in the cable you're trying to measure. We do use "integrated watts" from Mango for certain applications, but it's in places where that error is easy to deal with (such as by hourly comparisons, where you don't have time for that error to accumulate over months before comparing).

@CraigWeb Sure: This is running the latest Mango V4.5. I'm using the Raw TCP data source to chat with a TCP <-> GPIB Adapter, but this bug (also) appears in the serial data source as well. It mentions it in the documentaiton somehwere, too, that you should be able to put \r\n in the "delimiter" and have it sense that as the end of message. This does not work. To make it work, you have to download the JSON file and manually put in "\r\n" and then re-import it, at which point the datasource "delimiter" blank shows up blank. Here's the screen grab of our (working) data source: [image: 13QWC1x.png] Notice: Nothing in the "Delimiter" field. If I download the JSON for that data source, however, I see this: "updatePeriodType":"SECONDS", "delimiter":"\r\n", "hex":false, which shows the proper delimiter. This works (btw) so mango is processing the delimiter properly internally, it just doesn't display right in the UI. "acceptance criteria" would be "The actual delimiter value should be visible in the Delimiter blank, somehow, even of it consists of nonprintable characters" In the datasource help, attached below as a screen grab, with my highlighting shown, it says " Delimiters are unescaped before sending, so "\r" translates to carrriage return.": [image: uuM7yRY.png] If you put "\n" in that blank, you get this in the JSON: "updatePeriodType":"MINUTES", "delimiter":"\"\\n\"", "hex":false, If you put \n (no quotes) you get this: "updatePeriodType":"MINUTES", "delimiter":"\\n", "hex":false, Which seems to mean that the parser expects \\n (not a \n) The only way I was able to get the TCP data source to store the data using \r\n was to edit the JSON file as above, which seems to work properly. But then the \r\n doesn't show up properly in the "delimiter" blank

@CraigWeb Uh oh, that's a mistake on my part. Thanks for catching that!

@Gordoe Yes all cloud connect clients use the same port. I do not see why this would be more secure. To access the clients you have to be authenticated with the server. THe cloud connect server acts as a reverse proxy so to communicate with the clients you connect through the server.

@tungthanh500 Uou might want to email the sales channel instead of support. This is a license issue.

@tungthanh500 It should accept any characters. Do you have this problem if you export a file and directly import it without editing it? can you share a snippet of a JSON file that has bad chars so I can test? If you are editing the file your text editor could be adding a BOM to the start of the file. Please check for that and if it is there remove it.

@tomatopi point="water" This code is assigning the point-value object to a variable in the local scope called water. Since we are working in javascript, variables must be valid javascript variables.

@nino-kurtalj New link is here: https://docs-v4.radixiot.com/script-examples