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.

@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?

@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!

@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.

@cwangv Agreed. I have something scribbled down about the error 'IllegalStateException: Should be in state [INITIALIZING, RUNNING], but is in state TERMINATING' appearing in the log when attempting to delete a point failed. Its almost as though the publisher isn't starting/stopping cleanly. (Only tested with modbus publisher)

@MattFox HI thank you sample it works well Tim

@MaP what does your application do? More than happy to bounce ideas! Alternatively, give me a PM and we can discuss privately if it's sensitive Fox

@cmusselm Thanks for letting me know!

@Rodrigo This issue has been resolved in Mango v4.4.0 with advancedScheduler-4.4.1.

@Rav-Panchalingam Node Red. https://flows.nodered.org/node/node-red-contrib-bacnet https://cookbook.nodered.org/mqtt/publish-to-topic

@mihairosu Thanks for sharing! Fox

Rectified with the use of an angularJS controller and only two ma-point-values lookups Fox

@till There may be an option under system settings -. permissions -> alarms view permissions. Try removing the user permission (every user inherits that by default from 3.7+) Hopefully then, events can only be viewed by the respective users that have the correct permissions to view those datapoints... Mango 4 has more granularity on permissions Fox

@MaP Sorry for the late reply, for some reason I'm not receiving notifications... Yes, thermal shutdown can definitely be a faulty fan. that and how the unit is stored. They are usually the leading causes of the ES units failing (maybe IO as well?) Get yourself a replacement if you can, they're usually around $5 USD mark... A dead give away is the noise of the bearings in the fan itself. Also how is the unit stored? is it in an open air case or is it sealed with an IP rated box that gets really muggy. I do know the ED units are prone to overheating, but they have a guts load more kick than the GT's spineless raspberry pi 3 Fox