
PS2000A Datasheet
Doc. Number:
TECINHD001
Version 1.0
3/1/2002
P&S DataCom Corporation
35
11 Generating and Loading the Device Property Table
11.1
Generating the Device Property Table
For the PS2000A, a key step is that the device property table is generated correctly and
written in the PS2000A successfully. With the help of P&S DataCom’s device property
table generating and downloading tool, the device property table can be generated
through the MCU application system, and the table can be loaded into the PS2000A
remotely or locally. For the detailed use of P&S DataCom’s device property table
generating and loading tool, refer to the WebChip
TM
Device Property Table Generating
Tool User’s Manual.
11.1.1
Device Property Table
Any device object based on a MCU can be defined with the following five types of
objects: Constant, Variable, Event, Function, and File. For detailed descriptions of these
five types, refer to the MCUnet 1.0 Protocol.
The Device Property Table (DEVICE_PROP_TABLE) sets up the object-oriented
controlling relationship between the MCU and the network server and is a complete
description of a device. The network server accesses the device through its
DEVICE_PROP_TABLE.
For the detailed description of the Device Property Table, please refer to the MCUnet
1.0 Protocol.
In the PS2000A, the bit definition of the Device Property Description word
(DEVICE_PROP_DESP) is shown in Table 26.
Table 26
D15
D14
D13
D12~D10
D9
D8
D7
D6~D0
1
0
0
Reserved (always 0)
0
0
0
Number of device objects (Obj_Num)
In the PS2000A, the object name character string supports ASCII code only. Address
length is 16 bits. The expression of word (or double word) is from high to low in
sequence.
The number of objects in the device supported by the PS2000A should be less then 128.
In the MCUnet
TM
1.0 protocol, there are 12 user-defined memory types in the item
“Storage Type” of the Device Property Table. The user-defined memory may be any
memory type (Internal RAM, External RAM, NVS and PROM of MCU). It is available
for the user to easily distinguish the different memory types when being accessed.
For instance, in the MCS-51 application system shown in Figure 25, the microcontroller
connects to two X25C02s using its I/O ports.