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.

Mango is on the same LAN with the Modbus IP devices.

I was using TCP, and have switched to TCP with keepalive to see if that helps.

@craigweb You are right! Thanks!

Thank you..

The new data source UI doesn't seem to have the bug.

Thanks!

I do not believe it is possible. I think that may be somewhat under the scope of this git issue: https://github.com/infiniteautomation/ma-core-public/issues/1352

Hi Ava,

This is almost certainly caused by the name of the H2 database file changing to include the version of H2 in the filename. This was in the course of upgrading H2 from 196 to 199 which required doing a dump and restore. The advantage of using the newer version is that the LOB expansion that caused countless Mango users to shrink their H2 databases manually and in some cases regularly has been fixed.

Currently the version is 199, so the filename is mah2-199.h2.db now. This means the connection URL needs to be modified to:

jdbc:h2:/opt/mango/databases/mah2.199

I think given this it would probably be in the module's interest to add a way to say it's this Mango's database, to avoid this issue if we update H2 again / it requires an actual upgrade path like 196 to 199 did.

Thanks for bringing this to our attention!

Oh yes, now I see that the problem happens only in the legacy UI, in the new datasource page UI, the feature is working properly!

@jared-wiltshire said in Questions about point-values endpoint:

/rest/v2/point-values/time-period/

Ok, thank you!!! I had not take a look to this endpoint before. It is good to know this variant of the request.

I switched back to java se. I was able to get version 1.8.0 212-b10 installed. Hopefully this will be the fix.

Maybe I've to create a chron script that daily rsync backup directory on a remote server.

Yes, that's a good way to do it.

Ok, good idea.
Thank you!!!

Hi etantonio,

The logs you've shown span eight seconds and show that your publisher was running with debug logging on. I do not know what you're asking about as far as speeding things up, or the normality of it. All the log shows are a few packets being sent every second.

If those messages are in the ma.log file, you can decrease the log settings in your Mango/classes/log4j2.xml or Mango/overrides/classes/log4j2.xml file that pertain to the package (which would lead me to believe you may have switched to the debug-log4j2.xml since these messages aren't in the default configuration).

Otherwise, I suspect this is from the publisher log, and then your publisher is set to log debug messages in its publisher settings.

@petermcs There is a component in Mango 3.6 to display heat maps like this (they rendered as a SVG in Mango)
It is also customizable (color scale, legend position, number of weeks etc)

0_1558457599645_fc072d45-9965-4454-9a8b-99d9df3b4c82-image.png

Thanks, naturally you're right!

Hi Antonio,

Have you restarted Mango since copying it to Mango/overrides/properties? If not, the issue may involve the group ownership of 'root' for that file.

It would be the same as any other polling data source with long running polls: polls that occur while previous polls are running will increment the aborted polls count and not poll.

Thanks Phil.
the part regarding the script is ok, thanks.
Concerning file upload the client side maybe I can use something like this
https://www.folio3.com/blog/angularjs-file-upload-example-tutorial/
instead for the server side maybe I can use the service pointed by the
JSON File importer just adding a { character at beginning of file.
Thanks

@phildunlap problem solved, I used event handler to make a schedule instead. Thank a lot for your help!

You can modify the FTL that generates that report. Take a peak in Mango/web/modules/reports/web/ftl and place any versions you write into Mango/overrides/web/modules/reports/web/ftl/ (may take restarting Mango if that directory is new).

@craigweb I think this protocol is important. And many hardware supports this protocol. Does Mango have a timetable to support this?

Or is there a way to indirectly support the hardware of this protocol?

Or is there a manual support method? Now I have passed c# to Read and Write my hardware.