administrators

Ok got it, here's a simple example, it doesn't handle day light savings or have any scales but its a start. We might be able to add this as a component.

<div class="ma-designer-root" id="bee6bb2e-5cc4-4204-b710-5355b319c849" style="width: 1600px; height: 800px; position: relative;">
    <ma-now output="date.now" update-interval="1 days" on-change="date.to = ($value | maMoment:'startOf':'day'); date.from = (date.to | maMoment:'subtract':10:'weeks'); "></ma-now>
    <ma-point-values from="date.from" to="date.to" rollup="AVERAGE" rollup-interval="30 minutes" point-xid="temperature" values="pointValues"></ma-point-values>

    <ma-fn fn="toColor" expression="'hsl(' + Math.floor(240 - arg0 * 240) +',100%,50%)'"></ma-fn>

    <div id="3c622df6-d9cb-4cf5-ba95-3b08cabd0368" style="position: absolute; left: 0px; top: 0px; width: 1400px; height: 480px;" layout="column" layout-wrap="">
        <div ng-repeat="pv in pointValues track by pv.timestamp" style="width: calc(100% / 70); height: calc(100% / 48)" ng-style="{'background-color': toColor(pv.value / 100)}"></div>
    </div>
    
    <div id="0393e351-a6b5-42e4-8f3a-a3c96c4db0ae" style="position: absolute; left: 1494px; top: 124px; width: 20px; height: 220px;" layout="column">
        <div ng-repeat="v in [1, 0.9, 0.8, 0.7, 0.6, 0.5, 0.4, 0.3, 0.2, 0.1, 0] track by $index" style="height: calc(100% / 11); width: 100%" ng-style="{'background-color': toColor(v)}"></div>
    </div>
</div>

The data point I used is not very interesting but here's a screen shot, you can see an hour is missing due to DST

One problem with that is that you've apparently defined JAVA_HOME in the User variables instead of the system variables.

Now I changed back to
wrapper.java.command = %JAVA_HOME%/bin/java

I don't know what you mean, "changed back to" as the zip you'd have gotten from our instructions on the setup had,

wrapper.java.command = java

So please check the Path variable for the system user. I am not sure if you could use JAVA_HOME as you have tried, but you would certainly have to define it as a variable for the system user to do so.

@Christophe Use the "Bulk data point editor" under the administration menu. Select hierarchy folders using the left panel then apply a tag to them using the right panel.

• Click this icon
• Enter a tag name
• Type the tag value in the column header
• Select all the data points in the table by clicking the top checkbox
• Click "Start bulk edit"

Note this process will change a little in the upcoming 3.6 release.

The exposure is a question of networks and ports, and there is no authentication in Modbus (unless there is some device specific thing like writing a password to some register(s)). Therefore, there is insufficient information to assess the exposure and the problem, which isn't really a Mango question anyway.

Were you on the current version, or simply used a second publisher as you suggest, the issue wouldn't exist. So... why not do that?

What are you actually trying to do?

https://forum.infiniteautomation.com/topic/3936/retrieving-historical-values/2
https://forum.infiniteautomation.com/topic/4024/filter-for-point-values/7

When 3.6 is released there will be a bookend="false" option on <ma-point-values>

@richard-mortimer its not valid to put text directly inside a <tr> as in your first example. That's probably why you were seeing strange behavior. Its also possible that the browser doesn't like custom elements (<ma-*>) there either. See https://developer.mozilla.org/en-US/docs/Web/HTML/Element/tr under "Permitted content"

Setting display-type="converted" will make it display the raw numeric value as you discovered. You want to use the rendered value which is controlled by the data point's text renderer. When you have the analog text renderer selected and "Use unit symbol as suffix" is set it inserts a space between the number and the unit symbol. If you want to get rid of this space, uncheck "Use unit symbol as suffix" and set the suffix manually.

@petermcs If you give us a clearer description of what you are after we might be able to give you better guidance. Please link to an example image or website that is similar to what you are looking for.

@Christophe It wont work with the "Point hierarchy" parameter type. I suggest using a tag instead. Also I think the parameter names are case sensitive, so DN != dn

You certainly would want to point the device at /httpds to use the HTTP receiver, as you have seen.

I would advise using that HTTP receiver point to update the context in a scripting data source, where I would split the value on the command and then process the different fields. The HTTP Receiver does not supply a means to parse within a parameter's value, and that whole value is the IMEI parameter in the HTTP message.