Jump to content

Recommended Posts

Hi All,

I'm using a VT570 to log some data to SD card.

I realized a single  Trend with 2 curve for 2 sensor. My goal is to log on a monthly basis this data on a file. File name is "MMYY.utr".

Sample rate is 1 data every 5 minutes. When I export data from SD to Excel using the appropriate tool I always have DateTime column rollback in a strange way.

All the datetime are correct till to 25th of month and then they are wrong (even if the logged data continues to be correct).

Here under you can find some screenshots that I hope explain the issue better than my words.

Ladder code is simply and It is essentially a copy of Visilogic example to save Trend on SD Card but I'm not able to understand where is the error.

Any help or advise will be very appreciated.

Regards

Golzione

image.png.54d4ed4ad2107f4c57ab576d069a45ea.pngimage.png.d5987329265beb03907c5de4c6bf3972.pngTrendProperties.PNG.aa0fef28f76083c45e958f60cfd9b60d.PNG

image.png.6b2900e86d31e70d44a4545f0097ef8d.png

XlS.PNG.d9bd42ae21d08274a724a96402c1d295.PNG1617090270_SDCardManager.PNG.af7b80e79c1f1f3be042d569593ed714.PNG

Link to comment
Share on other sites

Hi golzione,

You are going very deep at user level.

please send your project to Unitronics Technical Support for review.

*Add PLC serial number for reference.

*Is the PLC battery voltage OK? What is a SB 8 status?

*Does PLC show right time/date? time

Then we will run it at our desk for simulation and will show result to R&D if we find a problem.

Until now you are the first who comply for such trend behavior.

B. R.

 

Link to comment
Share on other sites

  • MVP 2023

HI golzione, I just noticed this for the first time.  This possibly may have something to do with the way you are handling the data.  To me it looks like you are not clearing your data table each time it needs to restart from Row 1.  What happens then is that the old row gets overwritten with the new information.  In your case you have the data stored on the 7/7 over-written on the 25/8, and the data looks correct because it is simply a continuing record of your process.

I routinely log stuff on a one minute/ 24 hourly basis, and set up my data tables accordingly so that I don't have to clear them.  The next lot of 24 hours records over-writes the current rows right up to the last row of the table, and then the row counter is reset to 1 at midnight and things start again.  At 11:59:10 PM the data table is copied to the SD so that it is permanently logged under that day's date.  The difference here may be that you are writing direct, but the fundamentals of what I am describing may still be occurring.

cheers, Aus

Link to comment
Share on other sites

Hi all,

first of all thank your time.

On 10/3/2019 at 12:11 PM, AlexUT said:

Hi golzione,

You are going very deep at user level.

please send your project to Unitronics Technical Support for review.

*Add PLC serial number for reference.

*Is the PLC battery voltage OK? What is a SB 8 status?

*Does PLC show right time/date? time

Then we will run it at our desk for simulation and will show result to R&D if we find a problem.

Until now you are the first who comply for such trend behavior.

B. R.

 

Is It possible to get PLC serial Number from remote?

Battery Voltage is OK and SB 8 status is always equal to 0

PLC show Date/time correctly.

Which is the email to send my project to Unitronics Technical Support?

 V700_Info.png.d758be3011e29d2126ff2d5c199ab7ce.png

On 10/3/2019 at 11:52 PM, Ausman said:

HI golzione, I just noticed this for the first time.  This possibly may have something to do with the way you are handling the data.  To me it looks like you are not clearing your data table each time it needs to restart from Row 1.  What happens then is that the old row gets overwritten with the new information.  In your case you have the data stored on the 7/7 over-written on the 25/8, and the data looks correct because it is simply a continuing record of your process.

I routinely log stuff on a one minute/ 24 hourly basis, and set up my data tables accordingly so that I don't have to clear them.  The next lot of 24 hours records over-writes the current rows right up to the last row of the table, and then the row counter is reset to 1 at midnight and things start again.  At 11:59:10 PM the data table is copied to the SD so that it is permanently logged under that day's date.  The difference here may be that you are writing direct, but the fundamentals of what I am describing may still be occurring.

cheers, Aus

I got your point but I don't think It is occurring here. The data stored on 25/8 are correct. I mean only timestamp is not not correct. I check the value on 7/7 and they are very different.

I put here only 1 example but this behavior happen every month. Luckily sensors values are correct (there is any discontinuity) so It is simple to fix excel file but in any case It is annoying and I hate where I cannot understand whats going on my sw.

Regards

Golzione

V700_Info.png

XlS.PNG

IssueTrend.PNG

SD Card Manager.PNG

TrendProperties.PNG

Link to comment
Share on other sites

  • 1 month later...

Hi All,

I'm sorry if I'm not update this thread for a long time but I was very very busy.

That MB38 bit rise up on every month change and in this way after the name of the file saved to SD card is changed I stop saving trend on SD and then start again with the new file name when that bit falls down.

Regards

Golzione

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...