Lookout

cancel
Showing results for 
Search instead for 
Did you mean: 

Table object storing all data with same time

The datatable has a lot of Alias datamembers that are configured logging. I tried several datamembers and the logging was fine.

 

Could you tell me a specific datamember which has the logging problem?

 

Ryan Shi
National Instruments
0 Kudos
Message 11 of 25
(3,430 Views)

The paradise drive and judges hill tank heights were definetly two of the points that were not logging.

0 Kudos
Message 12 of 25
(3,424 Views)

I don't have the Aquatrol hardware so I tried different driver, but didn't see the problem.

Could you help to do some more test?

Connect the Aquatrol driver's Alias to a pot.value and log the pot. If this logs well, the problem may be in datatable.

Connect the Aquatrol driver's register to pot directly(instead of Alias), and see the logging.

 

I want to know if the problem is in the datatable or the Aquatrol driver.

Ryan Shi
National Instruments
0 Kudos
Message 13 of 25
(3,420 Views)

Given aquatrol.tanklev and table.tanklev=aquatrol.tanklev, I tried pot.value=table.tanklev and pot.value=aquatrol.tanklev. Is this what you wanted me to test? Both of those showed the same issue (data is stored but with the same timestamp).

0 Kudos
Message 14 of 25
(3,372 Views)

Dear Mr. Ryan Shi;

 

I have been given the project to correct the logging problem that my prior colleague was working on with you.  The problem of all items logged to the data table only logging with a single time stamp appears to be isolated to the data table itself.  When I log points directly from the Aquatrol Driver they do log and display correctly on the Hyper-Trend, but the communications is so discontinuous that we get breaks in the data, and red Xs through the numeric displays.  In order to work around this discontinuity, we thought we would connect the driver points to a data table, log at the data table level and then connect those data table points to the screen displays and trends, however the data table will not work.  It simply repositions the trend line to the latest data point and keeps no historical data.  The thread files are not building.  I hope this gives you more information to help us troubleshoot this problem.

 

Regards,

 

Butch Neylon

 

0 Kudos
Message 15 of 25
(3,217 Views)

I want to take a look at the database. Could you upload the database files to our ftp?

 

And tell me which trace is logged by datatable. I want to check the timsstamp of the data logged by datatable.

 

I don't find problem in the lookout process.

Ryan Shi
National Instruments
0 Kudos
Message 16 of 25
(3,207 Views)

Ryan;

 

I am sorry it took so long to get you this information, but I have attached two files from the database to this email.  If these are not the correct files please let me know what files you need.

 

Thanks,

 

Butch neylon

0 Kudos
Message 17 of 25
(3,124 Views)

Ryan;

 

Could you please give me specific file names of the files you want so I can upload them to you so we can get this problem nailed down.  I have worked on many Lookout systems and I have never had this happen before.  My customer is getting anxious as this is holding up the completion of his project and must be addressed.

 

Thanks,

 

Butch Neylon

0 Kudos
Message 18 of 25
(3,068 Views)

Could you try the Aquatrol driver from lookout 6.5?

We did fix a problem related to the time in a lot of driver objects, but I thought it already took effect in Lookout 6.1. Maybe you can take a try.

Attached is the 6.5 aquatrol.cbx. To use is, copy the current aquatrol.cbx to another folder, and copy the attached on to overwrite the current one. Don't just rename the 6.1 cbx file.

 

I also want to confirm with you about the version of your lookout. Is it Lookout 6.1 or 6.0.1?

Ryan Shi
National Instruments
0 Kudos
Message 19 of 25
(3,047 Views)

Ryan;

 

Tried the Aquatrol 6.5 cbx but it made no difference. 

 

Butch Neylon

0 Kudos
Message 20 of 25
(3,025 Views)