M2D-Laser-Scanner with Ethernet-Interface
Manual
HB-M2D-Ethernet-E
Page 16 of 39
www.MElsensor.com
S
S
t
t
a
a
t
t
u
u
s
s
i
i
n
n
f
f
o
o
r
r
m
m
a
a
t
t
i
i
o
o
n
n
r
r
e
e
a
a
d
d
o
o
u
u
t
t
u
u
s
s
i
i
n
n
g
g
c
c
o
o
m
m
m
m
a
a
n
n
d
d
0
0
x
x
2
2
1
1
:
:
1. Firmware version up to 1.10.0
when the scanner receives the command 0x21, a special
status info-telegram block
is sent out. To verify, if you
have got this special info-telegram block, check if a packet is received with version 0x10. The Header defines,
where the version information is located. The version is normally 1, 2 or 3. Version 0x10 marks a status packet.
The Status Packet contains 64 Byte Status, but no scan profile data.
Then the Ethernet-Version sends the Firmware Revision as string, end with 0x00, 0xFF.
2. Firmware Version 1.11.0 and higher
In addition to version 1.10 , at the end of the info-telegram block 31 Byte status register were sent, then 3 Bytes
FiFO-status.
Protocol 0x10 response to command 0x21 does not include scan profile data. Packet size is 2048 Byte.
Byte-Nr.
Register
Function
Length | Type
Ending
Firmware
00 …51
Header
-
52 … 59
Synchronisation
8 x 0x00
-
60 Protocol
version
-
61
Scanner Status 1
-
62 Image
number
-
63
Scanner Status 2
-
Hea
der
64 … 65
Reserved
-
66 … 97
0 … 31
Status Register
32 Byte
-
98 … 129
32 …63
Eprom-Data
32 Byte
-
130 … x
Firmware-Version
* String
0x00
1.10
X +1 …x+32
0 … 30
Functions Register
31 Byte
0xFF
X+33 …x+35
123...125
FiFO status
3 Byte
0xFF
appended
Fill bytes
0xFF
-
1.11+
* the length of the Firmware string is defined by the ending 0x00, 0xFF. The total length varies with the Firmware
version! The FiFO status (filling level) is given also with every scan profile packet of the length 2048 bytes.
Status registers are the registers marked in yellow on page 15. Status registers can be queried using register
0x11. Function registers are marked in light blue on page 15. These function registers can be read using register
0x21 command.
E
E
n
n
c
c
o
o
d
d
e
e
r
r
d
d
a
a
t
t
a
a
Encoder data is available in the profile data transmission protocol version 3.
This is
different from the special
status info-telegram which is received after sending command 0x21
.
Details for the info-telegram were given in
the following chapter, the description for the scan data block follows on the next page 18.
The profile information block ends with 8 Bytes 0x00. Then protocol revision number is given as 1 Byte, followed
by the 4 Bytes of encoder data. The end of the transmission block is all 0xFF’s, but the last 3 Bytes contain the
FiFO fill level data. (FiFO = first in first out buffer memory).
Note: the protocol version number is also given in the header, byte 60.
D
D
a
a
t
t
a
a
f
f
o
o
r
r
m
m
a
a
t
t
f
f
o
o
r
r
r
r
e
e
g
g
i
i
s
s
t
t
e
e
r
r
a
a
d
d
d
d
r
r
e
e
s
s
s
s
,
,
c
c
o
o
m
m
m
m
a
a
n
n
d
d
a
a
n
n
d
d
d
d
a
a
t
t
a
a
MSB = „0“ = command or register number
MSB = „1“ = register content
To change a value first send the register number and then the value. The register number remains set until a new
register number or command is transferred. Register can not be read out except status registers. These can be
read out using the special function register 0x18.
For dual registers, the value is active when writing the higher register.
Order of Bits
Register
Data
Register
Data
Lo-Byte
Lo-Byte
Hi-byte
Hi-byte
76543210 76543210 76543210 76543210
0xxxxxxx
1xxxxxxx 0xxxxxxx 1xxxxxxx
