What's a Table ORD?
A Table ORD is resolved into a table. The standard ORD schemes that resolve into a table are for BQL, SQL and History. Values from a table can then be updated into a point.
The best way to help figure out your ORD, is to open a copy of Workbench and try opening the ORD. If it works, you should be presented with a table of information.
What examples are there of a Table ORDs?
station:|slot:/Drivers/RdbmsNetwork/SqlServerDatabase|sql:select * from dbo.TESTHISTORY_NUMERICWRITABLE: This ORD makes a query in a SQL Server database.
station:|slot:/|bql:select name, facets, out.value from control:NumericPoint: This ORD performs a BQL query.
history:/tableTest/NumericWritable: This ORD performs a history query.
history:/tableTest/NumericWritable|bql:historyFunc:HistoryRollup.rollup(baja:RelTime '1800000'): This ORD performs a history roll up query. This is particularly powerful since the max, min and average of a history can now be placed into a point!
I don't under the Properties on the proxy extension. What do they mean?
Please refer to the documentation for the proxy extension.
The points don't seem to updating? They're stale!
If you have an invalid table ORD, the points will go into fault. If the points appear to be stale this is most probably due to the high refresh times set in the drivers poll scheduler. By default, all points refresh every minute. This is because high amount of processing power needed to resolve certain ORD schemes. The 'force refresh' Action on the TableDevice will manually perform the update the points if needed. Otherwise, adjust either the poll frequency on the TableDevice or the times on the poll scheduler itself (located under the TableNetwork).
Copyright © 2000-2016 Tridium Inc. All rights reserved.