An Object is a data item such as a temperature, a switch value or actuator state. Objects can be thought of as point parameters.
There are two categories of Objects that the Bacnet Spyder supports. They are:
The following is a list of fixed objects supported by Spyder.
|
Object Name |
Object Type |
|
DebugIndex0 |
Analog-value |
|
DebugIndex1 |
Analog-value |
|
DebugIndex2 |
Analog-value |
|
DebugIndex3 |
Analog-value |
|
DebugIndex4 |
Analog-value |
|
DebugIndex5 |
Analog-value |
|
DebugIndex6 |
Analog-value |
|
DebugIndex7 |
Analog-value |
|
DebugIndex8 |
Analog-value |
|
DebugIndex9 |
Analog-value |
|
DebugIndex10 |
Analog-value |
|
DebugIndex11 |
Analog-value |
|
DebugIndex12 |
Analog-value |
|
DebugIndex13 |
Analog-value |
|
Debug0 |
Analog-value |
|
Debug1 |
Analog-value |
|
Debug2 |
Analog-value |
|
Debug3 |
Analog-value |
|
Debug4 |
Analog-value |
|
Debug5 |
Analog-value |
|
Debug6 |
Analog-value |
|
Debug7 |
Analog-value |
|
Debug8 |
Analog-value |
|
Debug9 |
Analog-value |
|
Debug10 |
Analog-value |
|
Debug11 |
Analog-value |
|
Debug12 |
Analog-value |
|
Debug13 |
Analog-value |
The following is a list of mandatory objects supported by Spyder.
|
Object Name |
Object Type |
Object Instance |
|
HardwareID |
Analog-value |
0 |
|
BrandModel |
Analog-value |
1 |
|
VersionReflash |
Analog-value |
2 |
|
VersionMajor |
Analog-value |
3 |
|
VersionMinor |
Analog-value |
4 |
|
InUse |
Analog-value |
5 |
|
Error0 |
Analog-value |
6 |
|
Error1 |
Analog-value |
7 |
|
Error2 |
Analog-value |
8 |
|
Error3 |
Analog-value |
9 |
|
Error4 |
Analog-value |
10 |
|
Error5 |
Analog-value |
11 |
|
Error6 |
Analog-value |
12 |
|
Error7 |
Analog-value |
13 |
|
Error8 |
Analog-value |
14 |
|
Error9 |
Analog-value |
15 |
|
Error10 |
Analog-value |
16 |
|
Error11 |
Analog-value |
17 |
|
Error12 |
Analog-value |
18 |
|
Error13 |
Analog-value |
19 |
|
Error14 |
Analog-value |
20 |
|
Error15 |
Analog-value |
21 |
|
AlrmStatus |
Analog-value |
22 |
|
AlarmH |
Analog-value |
23 |
|
ConfigErrorID |
Analog-value |
24 |
|
ConfigErrorNature |
Analog-value |
25 |
|
ConfigErrorRecord |
Analog-value |
26 |
|
WMCommErrorDeviceAddr |
Analog-value |
27 |
|
WMCommErrorFileID |
Analog-value |
28 |
|
UniqueID0 |
Analog-value |
29 |
|
UniqueID1 |
Analog-value |
30 |
|
UniqueID2 |
Analog-value |
31 |
|
UniqueID3 |
Analog-value |
32 |
|
UniqueID4 |
Analog-value |
33 |
|
UniqueID5 |
Analog-value |
34 |
Note: The Bacnet Spyder supports the following object types.
AVI - Analog Value Input
AVO - Analog Value Output
AV Setpoint - Analog Value Setpoint
BVI - Binary Value Input
BVO - Binary Value Output
BV Setpoint - BinaryValue Setpoint
MVI - Multi-state Value Input
MVO - Multi-state Value Output
MV Setpoint - Multi-state Value Setpoint
The configured objects are mapped to the Function Block memory space to be used by any Function Block. Each Object is configured with a name.
The table has the following columns:
The table has the following columns:
Note:
In a Fixed_Dropable Object, only Internal Data Type can be modified.
Custom Object is the user defined Object. A Custom Object can be edited or deleted.
Fixed Objects marked as Fixed_Dropable can be exposed on the wiresheet. Other fixed objects cannot be exposed as points.
When a user changes the device model, if the name of a custom object clashes with a fixed object name in the target model, Honeywell Spyder generates a new unique name for the custom object and creates the new fixed object.