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.

@ThomasEinasto You need to set a name on the JSON store item. I'll update the example to set a name.

Thanks again Phillip. Both examples are very helpful.

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>

Hi Mark,

The Modbus read data tool in Mango displays the register result in hexadecimal, so 0x37 is 55. Might the value have changed between the readings? You can use the point locator test tool if you want to decode the register by describing the type of data in the register. Another part of the mystery is that Mango begins its addressing at 0, where associating the values in 1025 and 1026 may suggest modscan uses a base address of 1.

Edit: Also, I find it strange you say Modbus RTU when the screenshot from Mango is of an IP data source.

Hi Phillip,

There's not a simple mechanism I'm aware of for this. The status outputs for the data source and publisher both output packet counts, which don't reflect actual transmitted bytes in all situations (some packets may have fewer values, some packets may have more effective compression, etc). I think if I needed to form a first order approximation of that, I would compare something like ifconfig output from one day to the next via an SSH data source or write that to a file via cron and use the ASCII source. Then the number would at least reflect actually transmitted byte counts instead of uncompressed byte counts.

Perhaps you are looking for https://material.angularjs.org/1.1.18/api/service/$mdThemingProvider#mdthemingprovider-disabletheming-isdisabled

Hi Ramhuzani

I see how that message can be misleading. You will need to look in your ma.log file to see what error you are getting.
If you go to system settings --> email settings you can confirm your SMTP server setting and test it from there. Then have a look at your ma.log file to see if it is an authentication failure or host failer etc.
Note that it will send a test email to the email address of the user logged in. So you will need to make sure your user has an email address.

Thanks for having an eye to posterity!

Hi Dream, welcome to the forum!

Have you seen this post? https://forum.infiniteautomation.com/topic/3316/script-to-restart-mango/3

It shows how to restart Mango from within Mango, which can be done in a scripting data source. It also describes how to use the startup scripts restart mechanism.

Edit: I changed Ubutu to Ubuntu in my edits

Hi Phillip,

Is it an IP that you're polling? Did the network schema change such that it resolves that host to be somewhere else on the network? For instance, AWS instances can communicate more effectively using the intra-availability zone IP addresses, but that is not accessible outside of that zone and you would see this message.

If it's a domain name, you could see what DNS servers are being used. But, I wouldn't think that it would be, since generally there're redundant routes around the internet.

Thanks Jared I will create a new metapoint. :)

It works! Thank you for your help.

Hi Ian,

The lack of the template id element would lead me to believe that the property template is not required.

Correct.

The data history will be the same as the point to which it is linked; the logging type of "All Data" will ensure this.

It's not that simple. If the publisher is sending realtime values with update / change as its update event, the data source is saving real time values, but the point on the publisher is logging on an interval then the updates within an interval would have been published and saved, while on the publisher side only the interval logging would be recorded longer term.

So the settings that go into it are:

Publisher update event. All publishers have this setting, and it determines when you send a value from a point (or update the publishers' data image in the case of the Modbus or BACnet publisher). The logging type of the data point being sent. For a data point logging all data, for instance, the 'update' and 'logged' events are synonymous. If the publisher transmits real time data. If not, then only historical syncs will bring about data on the receiver. If the data source saves real time data. If not, then the points will appear to update in time, but their histories will only be filled in once a history sync is run.

Hi Phil,
Thanks for the quick reply.

I now have the Mango login screen displaying on the cloud server. I resolved this by creating a firewall rule to allow traffic through to port 8080 (so effectively port forward). I may need to change to port 80 to lose the port from the URL in the future- thanks for that tip! The echo $JAVA_HOME. I did log out of ssh session so I think it should work. I need to look into this further but the issue right now may be my lack of linux use. I may need to add JAVA_HOME to the profile file instead. The java.net.UnknownHostException message at the stack trace- I got this message prior to creating the firewall rule so I need to check for this message when I restart Mango (I can only do this next week so I will keep you posted)
Great software and great support- much appreciated
Paul

Hello Jarrod,
Thank you, I will enter it manually.

Cheers

Brian

Hi fishfacs,

Its also worth noting that I can add the Amps from multiple motors on different series, so I'm guessing it is a conflict with the units of Hz and A being on the same Y axis.

I wouldn't think so, series with different units can share an axis.

It could be:

The chart is displaying with no height. I saw this using your code snippet, but solved it by putting all those directives into a <div style="height: 300px"></div> One of the series is much more dense than the other and you've hit the limit of point values on a chart (5001 by default) and the less dense series isn't getting to return much data before that limit gets hit. Perhaps try a rollup like "Start" ?

Have you tried clicking on the series in the chart legend to see if you can see the other series simply by disabling the display of one of them?

Also, while I'm on the topic, I've noticed that when I mess up the syntax in any way, the preview in the page editor just shows up blank. Is there any log or debugger I can use to determine what is causing it not to render?

You can open your browser's developer tools. Sometimes you'll see a related error for certain sorts of mistakes in the markup, but not always.

Did all points stop or only the COV points?

Disregard. It started working as intended following a server reboot.

Thanks.

DEBUG 2019-03-26T10:52:40,708 (com.infiniteautomation.mango.io.serial.JsscSerialPortInputStream.:62) - Creating Jssc Serial Port Input Stream for: /dev/ttyUSB11 INFO 2019-03-26T10:52:40,714 (com.serotonin.m2m2.rt.RuntimeManagerImpl.initializeDataSourceStartup:380) - Data source 'Keepalive Connection' initialized INFO 2019-03-26T10:52:40,716 (com.serotonin.m2m2.rt.RuntimeManagerImpl.initializeDataSourceStartup:385) - Data source 'Keepalive Connection' took 24.55144ms to start INFO 2019-03-26T10:54:30,269 (com.serotonin.m2m2.rt.RuntimeManagerImpl.initializeDataSourceStartup:380) - Data source 'Keepalive Message' initialized INFO 2019-03-26T10:54:30,270 (com.serotonin.m2m2.rt.RuntimeManagerImpl.initializeDataSourceStartup:385) - Data source 'Keepalive Message' took 80.276995ms to start INFO 2019-03-26T10:57:34,036 (com.serotonin.m2m2.rt.RuntimeManagerImpl.stopDataSourceShutdown:423) - Data source 'Keepalive Connection' stopped DEBUG 2019-03-26T10:58:39,274 (com.infiniteautomation.mango.io.serial.JsscSerialPortInputStream.:62) - Creating Jssc Serial Port Input Stream for: /dev/ttyUSB11 INFO 2019-03-26T10:58:39,280 (com.serotonin.m2m2.rt.RuntimeManagerImpl.initializeDataSourceStartup:380) - Data source 'Keepalive Connection' initialized INFO 2019-03-26T10:58:39,281 (com.serotonin.m2m2.rt.RuntimeManagerImpl.initializeDataSourceStartup:385) - Data source 'Keepalive Connection' took 13.000694ms to start INFO 2019-03-26T10:59:36,361 (com.serotonin.m2m2.rt.RuntimeManagerImpl.stopDataSourceShutdown:423) - Data source 'Keepalive Connection' stopped DEBUG 2019-03-26T10:59:36,929 (com.infiniteautomation.mango.io.serial.JsscSerialPortInputStream.:62) - Creating Jssc Serial Port Input Stream for: /dev/ttyUSB11 INFO 2019-03-26T10:59:36,934 (com.serotonin.m2m2.rt.RuntimeManagerImpl.initializeDataSourceStartup:380) - Data source 'Keepalive Connection' initialized INFO 2019-03-26T10:59:36,936 (com.serotonin.m2m2.rt.RuntimeManagerImpl.initializeDataSourceStartup:385) - Data source 'Keepalive Connection' took 12.735079ms to start DEBUG 2019-03-26T11:14:00,003 (com.infiniteautomation.mango.io.serial.JsscSerialPortInputStream.serialEvent:121) - Serial Receive Event fired. DEBUG 2019-03-26T11:14:00,003 (com.infiniteautomation.mango.io.serial.JsscSerialPortInputStream.serialEvent:130) - Recieved: ERROR 2019-03-26T11:14:00,005 (com.infiniteautomation.serial.rt.SerialDataSourceRT.serialEvent:476) - null java.lang.NullPointerException: null DEBUG 2019-03-26T11:16:00,003 (com.infiniteautomation.mango.io.serial.JsscSerialPortInputStream.serialEvent:121) - Serial Receive Event fired. DEBUG 2019-03-26T11:16:00,004 (com.infiniteautomation.mango.io.serial.JsscSerialPortInputStream.serialEvent:130) - Recieved: ERROR 2019-03-26T11:16:00,005 (com.infiniteautomation.serial.rt.SerialDataSourceRT.serialEvent:476) - null java.lang.NullPointerException: null DEBUG 2019-03-26T11:17:00,003 (com.infiniteautomation.mango.io.serial.JsscSerialPortInputStream.serialEvent:121) - Serial Receive Event fired. DEBUG 2019-03-26T11:17:00,003 (com.infiniteautomation.mango.io.serial.JsscSerialPortInputStream.serialEvent:130) - Recieved: ERROR 2019-03-26T11:17:00,005 (com.infiniteautomation.serial.rt.SerialDataSourceRT.serialEvent:476) - null java.lang.NullPointerException: null DEBUG 2019-03-26T11:18:00,003 (com.infiniteautomation.mango.io.serial.JsscSerialPortInputStream.serialEvent:121) - Serial Receive Event fired. DEBUG 2019-03-26T11:18:00,004 (com.infiniteautomation.mango.io.serial.JsscSerialPortInputStream.serialEvent:130) - Recieved: ERROR 2019-03-26T11:18:00,005 (com.infiniteautomation.serial.rt.SerialDataSourceRT.serialEvent:476) - null java.lang.NullPointerException: null DEBUG 2019-03-26T11:21:00,003 (com.infiniteautomation.mango.io.serial.JsscSerialPortInputStream.serialEvent:121) - Serial Receive Event fired. DEBUG 2019-03-26T11:21:00,004 (com.infiniteautomation.mango.io.serial.JsscSerialPortInputStream.serialEvent:130) - Recieved: ERROR 2019-03-26T11:21:00,005 (com.infiniteautomation.serial.rt.SerialDataSourceRT.serialEvent:476) - null java.lang.NullPointerException: null DEBUG 2019-03-26T11:24:00,004 (com.infiniteautomation.mango.io.serial.JsscSerialPortInputStream.serialEvent:121) - Serial Receive Event fired. DEBUG 2019-03-26T11:24:00,004 (com.infiniteautomation.mango.io.serial.JsscSerialPortInputStream.serialEvent:130) - Recieved: fe DEBUG 2019-03-26T11:25:00,004 (com.infiniteautomation.mango.io.serial.JsscSerialPortInputStream.serialEvent:121) - Serial Receive Event fired. DEBUG 2019-03-26T11:25:00,005 (com.infiniteautomation.mango.io.serial.JsscSerialPortInputStream.serialEvent:130) - Recieved: ff

I'll have to monitor...