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.

Hi Ian, Quite strange. You could try launching it at the command line. Sometimes, especially in older versions, there were some errors that would make it to stderr and avoid the log file.

@phildunlap said in How do Excel reports handle no datapoints: g the value Thanks guys, my curiosity has been satisfied.

Yes but only one ES is publishing to this server with one connection so why is it showing 4 connections from the one server? If I stop and restart it it goes back to one connection and then over the next hour it grows to multiple connections. [image: JaapzMB.png]

Whenever a publisher or data source is saved, it is stopped and then started. You must save your changes for them to be in effect.

You are correct! Only IP networks use BBMDs A local device can currently only register as a foreign device with one BBMD. You could try creating more LocalDevices and experimenting with using other port numbers. This has come up a few times fairly recently and we're likely to do some work making it easier in the future. See this thread: https://forum.infiniteautomation.com/topic/3798/support-multiple-bbmd-routers-networks-over-1-nic

@jleblancmango It sounds like the contents of your main div are overflowing or something like that. Post your markup / screenshot.

Has anything changed with Persistent TCP being bi-directional now in 3.5?? Yes. As Fox mentioned there is a setting on the publisher that permits it to accept sets. If, the "Allow data source to set values back" is enabled on the publisher the original published point is settable it is set as settable in the point created on the receiver and the user has set permission to the point on the receiver then you can set to the received point. It will behave as though it were set on the publishing device, such that the value is only recorded as it is echoed back in the normal course of publishing.

https://forum.infiniteautomation.com/topic/3991/release-notes-for-scripting-3-5-1

@chio said in Stop data logging on date source exception: when faulted it stops responding to Mango queries via Modbus TCP How did you verify this?

@iperry It actually is possible, you just need to enable HSTS in the env.properties - # Configure HSTS (HTTP Strict Transport Security) # Enabled by default when ssl.on=true # Sets the Strict-Transport-Security header, web browsers will always connect using HTTPS when they # see this header and they will cache the result for max-age seconds ssl.hsts.enabled=true ssl.hsts.maxAge=31536000 ssl.hsts.includeSubDomains=false This will only affect browsers, as @Puckfist says HTTP is actually still enabled and you can make REST requests over HTTP using a script for example. Just bear in mind that the browser will remember the HSTS setting and refuse to connect to HTTP for the specified amount of time after you configure this.

Glad to hear it!

Sorry I should have qualified that question. I meant if they were run exactly on the hour would they be equivalent?

Hi Psysak, It's possible the devices are indeed dead. We'd prefer to address this over email if possible. Can you send in a link to this thread and the serial numbers for the MangoES units in question to support@infiniteautomation.com ? Thanks.

@phildunlap said in Implementing project tracking sheet: Not yet. It would take something like a script shuffling it into a data point to make it available to an excel report, currently. Would it be better, and feasible, to implement the same thing using alpha points?

Yes I have seen it before in my case Mango was not running on the server. What you are seeing is from your browser cache. Try doing a hard refresh and see what errors you get in your browsers console.

Hi Ian, You could do this by modifying the Mango/web/modules/mangoUI/web/mangoUi.js file. The string Mango v3 only appears in the relevant place (you'll need to address the use of titleSuffix elsewhere in the file, probably). The <title> element is in Mango/web/modules/mangoUI/web/ui/index.html Modifying those will not persist through an upgrade. While you could put them into Mango/overrides/web/modules/mangoUI/web[/ui] I would not advise it, since that could break other things in the UI upon update. Edit: See this thread for a better way to do it: https://forum.infiniteautomation.com/topic/4457/cutomizing-the-tab-name

Hi Phil, Ohh good, thought we might be going crazy. heh Thanks Ian

Thanks Craig.