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.

Hi Nikospps, I'm not certain. Are you getting any events or log messages? If I had to guess, there is an illegal address exception in your logs, and the actual modbus requests span your existing point and your new point, but in between in those addresses is one the device doesn't grant permission to read. So, to fix, use the "Contiguous batches only" setting, or decrease your maximum register / bit request size until it stops happening.

Hi thirawad, :D Thank you for documenting the solution so clearly. Image points will appear in the publisher's table in 3.3, but this will be helpful until that is released, for sure!

Nice! Glad you got it working!

Actually, you can make it a lot easier than that. You could just set the onclick attribute of your button for this use case. e.g. <ma-button raised="true" label="Print" onclick="window.print()"></ma-button> You can add some custom CSS to hide the top bar when printing - @media print { .ma-ui-main-toolbar { display: none !important; } }

Thanks, that's a good idea. I created and saved a new view. The point still renders as a grey Lego block with a yellow triangle to its left. A mouseover of the yellow triangle still displays "The point for this component is missing or invalid" as it did in my other view described above. When I mouseover the grey block, I see the valid point rendered as text, displaying the expected Multistate text string, time stamp, set dialog, and table history.

Did you look at your Mango/logs/ma.log file when the issue occurred to see if there was more information?

Hi Nikospps, welcome to the forum! The Modbus scan tool is only to make identifying slave IDs somewhat easier or assessing which slave IDs are currently up. The tool simply attempts to read Holding Register 0, and if it succeeds it reports that slave ID as existing on the network. You do not need to purchase Mango in your use case. You need to create data points that correspond to the data mapping in your external device. If it's a standard sensor / component / PLC it may have a modbus map in the manual for a device that explains register range, data type, register offset and possibly scale factors that you can use to create points. Try using the "Point locator test" tool on the same page as the scan and using that to create a data point. If your device has hundreds of registers preconfigured in that modbus map, know the free license is limited to 300 points and non-commercial use so you may need to be choosy about which points you are collecting data on. [image: P6nm6pS.png]

@aoliver said in How to automatically start Mango in a systemd based Linux OS: PIDFile=/opt/ambilogger/bin/ma.pid although, this PIDFile=/opt/ambilogger/bin/ma.pid should be /opt/mango/bin ;-)

Certainly, I hope it's useful!

@jared-wiltshire said in Increase the 5001 limit on values in the new dashboards UI?: /ui/administration/ui-settings Thank-you :-)

I looked into it pretty deeply and didn't expect issue. Do what you feel.

Hi phildunlap, is there a way to pass the timestamp from UI to scripting data point? Currently it seems to me that at least 2 meta data points will be required to key in the value and timestamp then referred from scripting datapoint to call .set(value,timestamp) - resulting in a total of 3 datapoints.

Hi MaP, Is the key "prices" unique in the JSON? If so, you could use a regex like.... "prices": (.*?\}\\]) I think, value index 1. That'll capture the list, which can then be parsed in a script... if( scriptRuntime.time < httpPoint.time ) { var pricesList = JSON.parse( httpPoint.value ); for( var k = 0; k < pricesList.length; k+=1 ) { var time = Date.parse( pricesList[k].starts ); if( isNaN(time) ) continue; //Consider error handling? outputPoint.set( priceList[k].spotEnergyPriceDollarsPerMWh, time ); } scriptRuntime.set( scriptRuntime.value + 1 ); } Where output point is either a numeric scripting point or a settable virtual point, and scriptRuntime is a multistate scripting point I am setting to see if newer data has arrived. You may wish to turn that point to not log. You could also do something in the loop like if( time <= outputPoint.time ) continue; to prevent extra work. The script would be on a cron similar to the polling rate of the http data source. Edit: In Mango 3.2 (which should be released next week) we've added the ability for scripting points to trigger the script, which would eliminate the need for the scriptRuntime point. We've also added the ability for meta points or point links to call the set() function.

@phildunlap Thanks, I'll try that. I tried and works very well.

Certainly!

That looks right, you probably just havent linked to the file from the UI settings page. It should look like this [image: xYR2LFb.png] Be sure to hit save at the top of the page.

@phildunlap Thanks Philip, much appreciated.

Thanks