other ways of getting csv files out of eWON
Hello, I have an eWON flexy 201 on site and want to log ca 30 tags at a frequency of 1Hz. As this generates a lot of datapoints, the eWON does not succeed in sending out the files, even if I limit it to a time frame of let's say 2h, which should be possible according to my calculations. Additionally sending the csv file in attachment of an email is no longer interesting if you have to send a mail every 2h or more frequently. Is there another option to get the csv files out of the eWON on a more regular basis, let's say every hour, so the files are not that big? Thanks for your input on this.
-
Hello Marjan,
You can use our REST API to retrieve the .csv files as well.
Two question I have from this though:
- Which files does the Ewon fail to send, and how does it not succeed?
- What exactly do you want to do with the csv data, perhaps you can use the BASIC script to achieve your goal.
Regards,
Bas Dieben0 -
Hello Bas
About the csv-files:
Visualization of the data goes already via the Datamanagement and the Visualization package, so that's already setup. But at all times we want to be able to retrieve the raw data for calculation and problem solving purposes. This doesn't mean we always need it, but we want to retrieve it when we need it.
Until now, we solve this by sending out the CSV-files via email. But in a 'new' type of installation, our logging frequency is quite high (ideally 1s) and for up to 30 tags, the CSV-files get too big for being sent out (message by eWON). I already chop it up in smaller pieces with lower logging frequency, but sending 3x a csv file that covers 8h isn't very workable anymore and is already less than we actually want. So looking for an easier way.
I already tried with the BASIC script to change logging frequency of a certain group depending on a certain condition because we had a lot of downtime of the installation so at that point, we didn't need logging. Still if all is going 'normal' the required data is too much to send via CSV-files.
About your suggestion:
- Can I found documentation on the REST API somewhere?
- is it possible to do it myself, so to create a 'Talk2M developer ID' for myself and set it up myself?
Thanks for your input!
Best regards,
Marjan
0 -
Hello Marjan,
Sorry for the slow reply!
I do wonder after your exact setup, as logging every second for only 30 tags should not be an issue. I'd buffer it on the Ewon and maybe send it every minute or so. Can be done with BASIC, but if you want to do that it might be better to make a ticket on our portal.But yes, you can definitely create a T2M developer ID yourself.
Then, to use the API, you can check out the Postman collection. I would just open the json in a text editor where you can see all options and how they are built up.-Bas
0 -
Hello Bas
Sending out the csv files every minute is indeed not a problem but handling the csv files is: every minute an email with this attachment is not handy, or do I misunderstand what you're writing?
In the meantime I put in a request for a T2M developer ID myself, but I didn't get any response on that. Can you tell me where I can see what the status is there?
Thanks!
Marjan
0 -
Hello Bas
Sending out the csv files every minute is indeed not a problem but handling the csv files is: every minute an email with this attachment is not handy, or do I misunderstand what you're writing?
In the meantime I put in a request for a T2M developer ID myself, but I didn't get any response on that. Can you tell me where I can see what the status is there?
Thanks!
Marjan
0 -
Hello Marjan,
Oh sorry, I just meant you could easily log that data directly to a system with the API.
We had some issues indeed with developer IDs not being sent. I will check what the status on that is and get back to you.
-Bas
0 -
You should have had the developer ID mailed to you yesterday, let me know if that is not the case.
0 -
Hey Bas
I didn't receive any email related to a developer ID so if you can double check?
0 -
Marjan,
I've created a ticket for you on this, I will ask them to send the dev ID there.-Bas
0
Bitte melden Sie sich an, um einen Kommentar zu hinterlassen.
Kommentare
9 Kommentare