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.

@bhansen Modbus does not support discovery, so you need to know the slave address, register address, type and format to be able to map data points.

This reference on the Mango site may help : http://docs-v4.mango-os.com/modbus-point-list-requirements

This one: https://forum.mango-os.com/topic/3551/data-sources-does-not-appear/13?_=1629414527624

@till That is correct. The value will be held in the cache. You can even set the data point to hold x number of values in the cache so there is some history there.

@hazel I am pretty confident one of your registers is being read as:

NaN

by Mango.

I have opened a ticket to make this more robust but the current version of Mango does not have a simple way to determine what data point is causing this. You will need to start looking into what registers you are reading for numeric values that have out of range data.

@terrypacker thanks a lot, an example code is more than enough. I will look into the library in detail and see how to use it in the upcoming days.

Thanks once again!

@mert sorry for the delay. Another option would be to use the Service that is injected into the context like this:

const dataSourceService = services.dataSourceService; const ip = dataSourceService.get('xid');

Also here is a collection of example scripts for the new environment and a few for the legacy one:

https://github.com/infiniteautomation/script-examples

Is there any plan to give permission to Global Scripts? Because user can view Global Scripts page and scripting permissions can be defined on system permissions.

@joelhaggar said in Config Import:

To set a PTCP data point it will send the set command down to the originating data point.

Ah! That's very good to know, thanks for that note. I wasn't aware the PTCP points are working in both directions like that.

@cwangv
Yes, thanks. Seems like there is no harm in just importing it over the existing one that I receive through the Persistent TCP data source.

I think there is a component similar to what you are asking about in this demo https://github.com/infiniteautomation/mango-demo

The demo is for Mango v4 and is a bit outdated but might give you some ideas on how to get it done.

@jared-wiltshire Yes, my bad. Oh i see, well thx for the help again.

@tungthanh500
yes, there are buttons on the top right hand corner of the page that you can use to create folders and files.

1.Administration-Dashboard designer
2.enable componenet list
3. in component list click on
Basic component-Link
link button appears on page
4. in property editor open Element specific list
5.open link-to-state list
6.find page to link and set

@till

Found it!

Generate History
When creating a new Meta Point sometimes it is helpful to backfill values for it. This can be done by the generate history link in the Data Points table.

The most recent saved value for all Context Points is found and that date is used for the Starting date for the simulation. (If any context point has no saved values the Generation will fail here)
The oldest saved value for the Meta Point is found and that is used as the Ending date for the simulation. (If no values exist the current time is used)
The simulation is run from Starting to Ending times and a values are created and saved according to the Meta Point settings.
This means that a history can only be generated for times before the earliest Meta Point value.
Calls to set() tell the database to save this value regardless of logging type and do not send it out through the data source

var pointValues = myContextPoint.getPointValuesBetween(fromTimestampInMilliseconds,toTimestampInMilliseconds); print(pointValues);

Fox

Hi Joel, I am able to confirm the function is working in v4.0.0 Beta.14. Many thanks for your reply.