Bit #	Definition
15	0=link LED off; 1= Link LED on
14	0=Application LED off; 1= Application LED on
13	0=twisted pair; 1=fiber
12	0=10Mbit; 1=100Mbit
11... 8	Reserved
7... 4	Module Type
3	Reserved
2	0=half duplex; 1=full duplex
1	0=not configured; 1=configured
0	0=PLC not running; 1=PLC/NOE running

Table 1: Get local statistics Word3 board status

NOTE: Bit 0 is a low bit counting from right side, so that means: PLC Running = 0x0001, Application LED = 0x4000, LED connection = 0x8000.

140NOE77111/01 V3.5 & 140NOE77100/10 V1.02, V2.0 has the same order as the table below:

Bit #	Definition
15...12	Module Type
11	Reserved
10	0=half duplex; 1=full duplex
9	0=not configured; 1=configured
8	0=PLC not running; 1=PLC/NOE running
7	0=link LED off; 1= Link LED on
6	0=Application LED off; 1= Application LED on
5	0=twisted pair; 1=fiber
4	0=10Mbit; 1=100Mbit
3...0	Reserved

Table 2: Get local statistics Word3 board status

NOTE: Bit 0 is a low bit counting from right side, so that means: PLC Running = 0x0100, Application LED = 0x0040 , LED connection = 0x0080.


2. Documentation Mismatch:
· Unity V2.2 and Concept V2.2, V2.6 help file uses the same byte order as table 1.

· Modicon Quantum with Unity Ethernet Network Modules User Manual (6/2006) and Transparent Ready User Guide (10/2005) use the same byte order as table 2.
Considering majority users have been using the order same as the current version V3.6 for NOE77111/01 and V3.4 for NOE77100/10, we decide to remain the current MSTR board status byte order (shown in table 1) for NOE module and will make sure the consistency in our future release.
Schneider will correct the corresponding documentation to reflect the change.