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.

@tangyiping your CSV needs to be in the exact same format as provided in the samples including the time stamps. Make sure to click the "?" icon on the page to see the examples and the formats. There is no option to import point values from JSON with this tool. Thanks.

Will do, Thanks

@craigweb said in CSV with Nested structure:

Is there any way to import data points as CSV that includes nested structures.

The answer is kind of for data points only, but it wont import event detectors. You can export CSV from the data sources page. Then import the CSV on the configuration import/export page.

We are currently working on better solution for importing and exporting data points via CSV. It will get tied into the new bulk data point edit page.

For the time being your approach of using a script to generate JSON for import via the configuration import/export page is a good one.

Thanks. The charts are working after I deleted those files and restarted.

Hi Nikos,

Yes, you could use a meta point like,

var dayStartTime = new Date(); dayStartTime.setHours(0); dayStartTime.setMinutes(0); dayStartTime.setSeconds(0); dayStartTime.setMilliseconds(1); //Get the value before the first millisecond of the day // (00:00:00.000, or the last value from yesterday if it didn't change) var subtracter = variableContextPoint.pointValueBefore(dayStartTime.getTime()) var subtrahend = energyContextPoint.value; if(subtracter == null) return -subtrahend; return subtracter.doubleValue - subtrahend;

@MattFox See the post here -
https://forum.infiniteautomation.com/topic/3238/failed-to-create-authentication-token-bad-request/2

Thanks!

Yes, it is fully realized (with few special exceptions in the system settings: you cannot import database schema version numbers). It is unlikely that data sources or points would change in such a way as to invalidate previous JSON. If there were a change, it would most likely be the addition of a property that would have a class default, so it could be foregone in old JSON without issue. We try to stay conscious of this so that people's backups do not get invalidated.

Ah! Thanks for sharing what the cause and solution were. I went back and edited that post so that Dan's suggestion (this issue) was /opt/mango/bin/ma.pid in the original post

Glad you got it working!

Glad to hear it! But, I think you may wish to get rid of the LOG.debug portion. print() doesn't return anything so you're logging undefined. My script looks like this:

LOG.debug(print("test"));

which produces the output:

test
DEBUG 2017-12-21 09:39:40,795 - undefined

Hi Thirawad,

Can you be more specific about which part you're having trouble with?

The help in the SSH data source explains how to get SSH connectivity in a common Linux situation. You simply need to generate the keys, install the public key on the target machine, have the private key to gain SSH access on the Mango machine, and point the data source at this file.

Data points run commands and then take the response as their value. So, maybe you're grep'ing values from files into a numeric point. Maybe you're cat'ing a file into an alphanumeric point so that you can run a script over it.

Got it, but i had to disable the datasource's regex for it to work. Datapoint regex works fine.
for some reason datasource just wouldn't work with (.* )=(.* )\r
Strange as it works with normal serial data datasources just fine....
disabled datasource regex, set timeout to 30 seconds, changed point regex to
test=(.*)(?:|\r|\n) with identifier being test and bang, in goes my values....

Oops, yes I meant to say Modbus TCP/IP from Click PLCs, haha.

Nice, good to know! Thanks for sharing!

@phildunlap Thanks for the note and confirming what we'd found. I was hoping for something a bit easier. I'll put something in the feature request board.

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.