Jump to content

dierkens

Members
  • Content Count

    41
  • Joined

  • Last visited

Community Reputation

2 Neutral

About dierkens

  • Rank
    Advanced Member

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. I’m not sure what you’re trying to do.
  2. Can’t you just read those as individual coils without doing any bit manipulation? Use Modscan to read it as coils and see if you can figure it out from there.
  3. We’ve found the best approach is to just save a data table to a UDT file and then use the converter to toss it into Excel. You can save it to a csv file but you have to thoughtful of how much time it takes to write to the csv file.
  4. Put some jumps around your code to narrow down what may be causing it. Narrow it down from there. You might also load one of the example programs in it and run that for a while. Thats the only way I know to determine if it’s hardware related or not.
  5. Thanks. We’ll probably use this.
  6. Is the date/time correct on your computer?
  7. Perhaps install it to another folder or in another drive. I haven’t tried to run the same version but I’ve done different versions that way in the past.
  8. Yes, however the FTP process is easier and cleaner.
  9. Save the results of the table to a csv file (make sure to watch the file status to make sure that the PLC has enough time to handle the file tasks). You can then setup a triggered task to FTP it to the computer/server or a network share somewhere accessible by the computer. It works well.
  10. The filename can’t have the “/“ character. we build a file name using the substation function and putting a yymmdd format. If your storing a bunch of data in it you have to make sure the file is closed before the next file update takes place. We’re storing 1m data for an entire month in each file. We then use the conversion utility to convert it to an excel file when we need the data on a computer. We FTP the files off the PLC. Hope this helps
  11. For one it's not willy nilly... It does it when it opens the project so that it can keep track of things. Now on to your issue... You can keep track of it in the change control facility directly by creating a text file in your project folder that has the date/time on it. -or- You can create a production library and a development library and keep track of things that way. -or- You can create structure your file name such that the naming convention contains the Save Date in it. Your choice. Okay, last question: What product are you using for Ve
  12. What specifically is the reason it's bad to have this date change? I have some recommendations on how to work around it but I'd like to hear your reasoning first.
  13. On the PLC go to UniApps. Then Network; then VNC; choose your resolution, apply. bingo.
  14. We noticed that too. we could only save about 55,000 records (~ 4 days of 1-minute averages ) before it would time out (> 60 seconds). We ended up changing it to only save the UDTF file. Now it’s been running all month and is about 200,000 records and takes < 10 seconds. If we want /need the data we’ll use the UDTF to Excel utility.
  15. I'm trying to log the duration of the DTI-to-File process and am trying to use the Stopwatch to get the elapsed time. Does anyone have an example of how to trigger and record this process. I'm not set on using the Stopwatch if you've got another idea on how to do this.
×
×
  • Create New...