Messages

1

Support Questions / Re: Basic Data Logger 2 Stops Logging After 2 or 3 Days

« on: February 19, 2019, 09:28:46 AM »

It is version 399x.

The issue may be our own internal issue! I am told that there were network issues at some point over the weekend. I have restarted the Advanced HMI application and will see if it stops again.

Thank you.

2

Support Questions / Basic Data Logger 2 Stops Logging After 2 or 3 Days

« on: February 19, 2019, 06:47:14 AM »

I have the Basic Data Logger 2 set up to save to a text file, on data change, and change to a new file daily. It seems to run fine for 2 to 3 days and then it stops logging. Any ideas?

I am using Version 399.

Thanks.

Lee.

3

Support Questions / Re: Advanced HMI and Simatic 505 PLC

« on: February 01, 2019, 06:39:13 AM »

Thank you.

4

Support Questions / Advanced HMI and Simatic 505 PLC

« on: January 31, 2019, 03:01:48 PM »

Will the AdvancedHMI application work with a Simatic 505 PLC. If so, what driver do I need to use to communicate. Our PLC only has RS232 communication available.

Thanks.

5

Support Questions / Re: BasicDataLogger2 sql database

« on: January 29, 2019, 02:35:01 PM »

I really want to capture the machine running bit and the downtime reason. The Machine ID does not change since I read each machine separately into their own files. I think I will leave the code as is and get the programmer to figure out something on his end,

Thanks.

6

Support Questions / Re: BasicDataLogger2 sql database

« on: January 29, 2019, 01:11:34 PM »

Yes, ideally that is what I would like. But would all of the values have to change, or can some of them remain unchanged. And example would be:

When the Machine Running bit goes TRUE, then the downtime reason value should go to zero. When the Machine Running bit goes FALSE, the downtime reason may remain a zero, depending on whether or not the logic in the PLC has enough coding to recognize all stops. If it doesn't then the downtime reason would remain a zero. Will this mess up the Advanced HMI coding? Perhaps I should just leave well enough alone and let the programmer on the other end of this project sort out the various lines in the .log file.

7

Support Questions / Re: BasicDataLogger2 sql database

« on: January 29, 2019, 12:58:48 PM »

Ideally yes, I would like to capture everything once they have all changed. Only other issue is the downtime reason may stay a zero, depending on how the logic captures the event. So it may not really matter that there are multiple lines. We may be able to code around that on the other end of what we are trying to do.

8

Support Questions / Re: BasicDataLogger2 sql database

« on: January 29, 2019, 12:46:47 PM »

Multiple lines. Each line has a different value for the comma separated values and a different time stamp.

Jan-29-19 12:45:48:175,,44,72
Jan-29-19 12:45:48:284,False,44,72

In the first line the first comma separated value was not read, then in the second line it was. I am reading three separate points in a PLC. The False indicates that the machine is not running, the 44 is the Machine ID number and the 72 is the downtime reason.

9

Support Questions / Re: BasicDataLogger2 sql database

« on: January 29, 2019, 12:38:11 PM »

That is what I am currently doing. I am also using the script that I found on here that makes a new file for each day. The issue is I get multiple entries in the .log file each time one of the datapoints I am monitoring changes state. I am guessing that it is due to their location in the PLC and the scan time of the PLC. They do not all update at once.

10

Support Questions / Re: BasicDataLogger2 sql database

« on: January 29, 2019, 12:08:03 PM »

I would like to save it to a text file (.log). Do you still have to create a Data Source?

11

Support Questions / Re: BasicDataLogger2 sql database

« on: January 29, 2019, 10:45:25 AM »

That is what I was thinking I would have to do, but I am lost when it comes to that!

12

Support Questions / Re: BasicDataLogger2 sql database

« on: January 29, 2019, 07:46:31 AM »

I know this is an old post, but I am trying to use it so that I get all of the data at once from the DataLogger2 rather than as each piece of information is fired. However I don't understand where this code needs to be set up as it fails when I build the application:

Using t As New sasDataSet.nwpresslogDataTable, ta As New sasDataSetTableAdapters.nwpresslogTableAdapter

All of the other code I can modify (it seems to build OK, except for this section). I am not really a VB programmer, ladder logic is my forte!

Thanks

13

Support Questions / Re: Routing Path for CLX PLC

« on: January 25, 2019, 06:08:43 AM »

I hang my head in shame! It was the tag name, I had written it down wrong. Too much going on yesterday wasn't looking with clear eyes until this morning.

I appreciate all of your help. I may have more questions later as I am trying to use Advanced HMI as a data capture method to automate a downtime collection system that we use in plant.

Thank you again.

14

Support Questions / Re: Routing Path for CLX PLC

« on: January 24, 2019, 06:05:24 PM »

Yes, that tag is in the controller scope.

15

Support Questions / Re: Routing Path for CLX PLC

« on: January 24, 2019, 02:15:57 PM »

I tried that in the beginning and it shows "Path Segment Error (Invalid Tag Name).

I am positive that I have the correct tag name.

I also take it that the IP Address you put in was a typo? My address is 10.20.110.39 and you had down 10.20 110 139

Thanks.