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.

In what way are the folder names different. I downloaded the zip file and the file names in the MangoTSTD directory appear to be the same as in the zip file

Bryan

Yes, you can not use the scadaBR database in Mango directly. It doesn't matter if the database is Derby or MySQL you will still not be able to use it in Mango. Your only option is to export the JSON from scadaBR and import your configuration into Mango.

If you are using MySQL to store point values the column is named TS (as in Time Stamp) and the time is stored in Unix Time. If you are using the Enterprise version of Mango then point values are store in a NoSQL database and in a different format.

I seem to have overcome this issue by going to
(start>run>services.msc) and starting the MYSQL instance.

All seems to be going fine now.

I increased the update period, and my controller is using COV but not the other sources.

I'm not sure as I've never used it this way but it probably depends on how you have the point set to log. If you have it set to log on change I would expect you would not get duplicates. You might see duplicates in the cache but only the change should be logged to the database.

@StephenVDK said:

Hello everyone,
When I try and add the multistage point to a graph or indicator in dglux, it says it's null, when it's not. How do I get it to display the proper value?

Thanks.

Generally with a multistate point I would (and this may not necessarily be the best way) use the 'Map' property binding type, then enter the multistate text string and respective text value. For example if you were binding to a gauge with a range of 0 to 100, you could enter the string 'low' as binding to 25, 'medium' to 50, 'high' to 75 etc.

Great thank you!

Thanks, Terry. I was thinking that duplicating the TCPIP data source would be a good start and save a lot of work. Another option is to simply add a UDP checkbox to the TCPIP source, though that may require renaming the source to "IP."

@hanse1pk said:

Managed to get it working.
Had to use 4 byte float swapped

Next item is for me to take in these integers such as in second example and have them be shown and recorded as what they represent.

This doc might be useful to you: http://wiki.infiniteautomation.com/doku.php?id=tipsandtricks:bestpractice

In my experience (having added probably a dozen different types of device to Mango using Modbus) there is always a bit of fluffing around initially to discover the magic transformation to get from the manufacturer's address to the address that Mango expects.

The first thing I usually do is look in the documentation for the modbus registers and find a register that can be easily identified - usually something like a 'hardware model number' or other known value.

Then you can use the 'Modbus Read Data' and 'Point Locator Test' functions on the Data Source page to test out different registers to try to hit the value you want.

In an extreme example, the manufacturer's documentation may say that a holding register is located at 43004, but you might find that the actual register you need to input into Mango is 3003 (43004 - 40001). Software such as 'Modbus poll' or 'CAS Modbus Scanner' also helps in figuring this out.

I may be wrong, but from memory, the chart colours only apply to reports.

The charting stuff looks to have been completely overhauled in the newest beta anyway:
http://infiniteautomation.com/forum/topic/1872/new-features-coming-soon

I have done some more testing and I definitely think there is an issue with the file data source.
Every time I load the CSV I get a different number of data points cached and displayed correctly on the Data points page chart, depending on how full the cache buffer is at the time of the import but only a few points are actually committed to the database.

This screenshot for example shows data logged for 21 April, 04 April, 10 Mar, etc. This is daily data from the 14 Oct to the 21 April. The CSV file is of a constant format. You can see from the graph that daily data is being cached from roughly the 1st April to the 21st April but everything else is in bits. This data is missing from the database data.

cached2.png

Running the import again, this time with display cached data set to 150 I get the complete dataset but nothing more is recorded to the database (see history table).

cached3.png

The datasource is set to log all data so I would assume that if data is being cached correctly, unless there is a double up it should be logged to the database.

datasource.png

Regards,
Matt.

Hi Joel,

It is version 2.5.0.
I have figured it out. I had public-dashboards open with the data points being visualised via the API to a local web page. The data points that were being utilised on the page were the points that were giving me an error when I went to amend them. Simply closing the open web page allowed me to edit the data points without error.

Dominic

The image is created prior to generating the HTML via the FTL template. The images all have preset sizes and are generated at this size when the report is created.

A future feature could be allowing sizes to be set in the report configuration.

However there is a way to generate different size charts via the Chart Servlet. This is the servlet that generates the charts on the Data Point Details page. The help for this can be accessed via the help icon in the System Settings --> Chart API Settings. These charts are different than the report charts but it should be possible to use this chart instead if you can create the URL properly in the template.

Thank you! Solved by removing report usin SQL

That was it. I had completely misinterpreted what the check boxes were for and had them selected. That resolves the issue of clients causing havoc but it would be nice to remove access to all modules except DGLux.
I'm looking forward to the next version. Development seems to be happening in leaps and bounds lately. I especially like the new module upgrade feature.

Matt.

That is a self referencing variable. so my.value would give you the value of the meta data point. This is useful if you want to add a value to it's self or use the current or past values of the meta data point within the calculation. It prevents you from needing to add the meta data point into the script context which ultimately allows you to import self referencing meta data points through the JSON import without getting errors.

Hi Joel
Thanks again for the detailed info. At this point we can shelf the excel requirement as we are just working through the best way to bring a simple production schedule and related data into the database. We have also explored the pop3 data source as an option. Our goal is to be compatible with something simple that clients would already have in their workflow. Any suggestions you have would also be greatly appreciated.

On the topic of XML do you have an example of an import class that we could use as a test which is based on a simple excel document?

Thanks
Michael