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.

This has been narrowed down to a Derby problem. It will be fixed in the next release. In the meantime, if you set a "home url" for the user, the problem should go away.

Only settable points can be listed there. If you have no settable points, your list will be empty.

We currently have a customer logging around 500 samples every 2 seconds, so i think you'll likely be ok. I recommend you separate your database server from your M2M2 server and scale the hardware as necessary.

The easy answer is to have 10 M2M2 instances. But to answer the question you asked, at the moment there are no mechanisms for this, but there is no corporate philosophy preventing them from being added.

Hi daniel,

Thanks for reporting this. The problem will be fixed in the next version.

Yes. All Mango documentation is online. Click on the "?" icons.

Hi,

In point properties (edit datapoint)
Text renderer options:
Type = Analog
Format = 0.0

In this way you get one decimal.

Br, Conny Larsson

There's a bug in the anonymous code. A fix will be available soon.

No. It's possible it was already discovered and fixed in dev.

OK, Thanks, I loaded the compatible module's and all is well, Thank You for your timely reply.

Hi, Matthew

It's working now, the "&" solved it.
Added modules and licenscefile and restarted.
Now the fun starts :D

Thank you

Yes, it is.

This will be released soon. We just needed to work out how ScadaBR wanted to have it done.

Please keep the great work moving forward, I'm sure the users will support you.

Thanks
Mo

Source code will be provided for some modules, but it hasn't yet been decided which. Stay tuned...

This is a bug. The 0.9.1 version of the module will fix this problem.

You must register you instance first.
Make sure you have the correct address in env.properties file and click on the link "Update License" in "Modules" page.

BR

great - works now - prehaps the instructions could be a little clearer

Ok, it works!