This example shows the transfer of dynograph data to Oracle using vector
transfer. It also shows the use of indirect addressing in the cross
ref table. Here we use it get the name of where the `X' and `Y' data
is located. In this example the attribute ".last x name" may
contain the string ".dyno card(0:114,X34)", and the attribute
".last y name" may contain the string ".dyno
card(0:114,Y34)".
| Point Name - Dynographs
Alias - DYNOGRAPHS Residence = Ram Categories = 00000000000000000000000000000001 CE Indicator = Enabled CE Order = Natural |
||
|---|---|---|
| Attribute Name | DE Type | Value |
| device poll types | rtBYTES4 | (0x)00000004 |
| device PRBX types | rtBYTES4 | |
| scan input control | rtLOGICAL | 1 |
| scan input status | rtUINT8 | |
| failure threshold | rtUINT8 | 3 |
| scan input | (see below) | |
| scan output control | rtLOGICAL | 0 |
| scan output status | rtUINT8 | |
| scan output | (not used) | |
| dev fail threshold | rtUINT8 | 3 |
| oracle table name | rtBYTES48 | "DYNOGRAPHS" |
| transfer direction | rtUINT8 | 4 |
| cross ref table | (see below) | |
| debug level | rtUINT8 | 0 |
| sql filename | rtBYTES32 | "" |
| device stats | rtUINT32 | |
| point control | poll type mask | st buffer size | # of elements | RTAP DE type | deadband type | deadband | rtap alias name |
|---|---|---|---|---|---|---|---|
| 1 | (0x)00000004 | 0 | 1 | 1 | 0 | 0 | "11-20 DYNOGRAPHS" |
| 1 | (0x)00000004 | 0 | 1 | 1 | 0 | 0 | "10-07 DYNOGRAPHS" |
| 1 | (0x)00000004 | 0 | 1 | 1 | 0 | 0 | "14-07 DYNOGRAPHS" |
| 1 | (0x)00000004 | 0 | 1 | 1 | 0 | 0 | "10-12 DYNOGRAPHS" |
| oracle field | rtap attribute | conv rtap de type |
|---|---|---|
| TAGNAME | [alias] | 0 |
| TIMESTAMP | [time] | 0 |
| X | {.last x name} | 0 |
| Y | {.last y name} | 0 |
| VALIDATION_STATUS | [v]\\\\"nck\\\\" | 16 |
| SUBSTITUTION_STATUS | [v]\\\\"nck\\\\" | 16 |
| ORIGIN | [v]\\\\"FDC\\\\" | 16 |