M2i-LAN Laser-Scanner manual
HB-M2-iLAN-UDP-E.doc
page 16 of 44
MEL Mikroelektronik GmbH, Breslauer Str. 2, 85386 Eching / Germany
www.MELSensor.de
0
0
x
x
2
2
1
1
:
:
i
i
n
n
f
f
o
o
t
t
e
e
l
l
e
e
g
g
r
r
a
a
m
m
:
:
s
s
c
c
a
a
n
n
n
n
e
e
r
r
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
The command 0x21 reads out the status information in
one
complete packet from the scanner. When you
have sent the command 0x21 to the scanner and watch out for a packet with the protocol version 0x10. This
protocol revision number is in the byte 60 of the header. When you found 0x10 in Byte 60, you have
identified the info telegram packet. Protocol version 0x11 is the message that something with profile scan
data status is wrong.
At the end of the packet, additionally 31 bytes of function register status is sent, then the FiFO fill status
information. The table on the next page shows the details.
When the command 0x21 is received by the scanner, a packet with 2048 Bytes is sent from the scanner to
the PC. The packet contains all information of the registers 0 … 63, but no scan profile data. From Byte 130
on, the firmware version is sent as a string. The end of the string is 0x00.
I
I
n
n
f
f
o
o
T
T
e
e
l
l
e
e
g
g
r
r
a
a
m
m
(
(
t
t
h
h
e
e
s
s
c
c
a
a
n
n
n
n
e
e
r
r
s
s
a
a
n
n
s
s
w
w
e
e
r
r
t
t
o
o
t
t
h
h
e
e
c
c
o
o
m
m
m
m
a
a
n
n
d
d
0
0
x
x
2
2
1
1
)
)
Byte
Nr.
Register
Nr.
Function
Length|type
Ending
Firmware
00 ... 51
Header
52 Byte
52 … 59
Synchronization
8 x 0x00
60 … 60
Protocol version
1 Byte
61 … 61
Scanner Status 1
1 Byte
62 … 62
Image number
1 Byte
63 … 63
Scanner Status 2
1 Byte
Hea
der
64 … 65
Reserve
2 Byte
66 … 97
0 ... 31
Status-Register
32 Byte
-
98 … 129
32 ...63
Eprom Data
32 Byte
-
130 … x
-
Firmware-Version
* String
0x00, 0xFF
X+1 ... x+32
0 ... 30
Functions-Register
31 Byte
0xFF
...1.10.0
X+33 ... x+35
123...125
FiFO fill status
3 Byte
0xFF
... 2047
Fill bytes
0xFF
1.
11.0+
...
* the length of the firmware string is defined by the ending 0x00. the length of the firmware string varies with
each version! Between the register data and the FiFO-Bytes 0xFF may appear! The position of the FiFO-
Bytes is after the function registers. Always a block of 2048 Bytes is sent, at the end of the block “old” data
(trash) may exist.
command: 0x21, read out register-dump –Scanners action upon 0x21:
o
64 EEPROM Registers are read out
o
the protocol version is set to 0x10
o
the sync raster is written 8-Null Bytes
o
from Byte 130 of the data section the firmware-Version number is sent
o
no Scan-Data were transferred
Data format of the Packet valid from
Firmware Version 1.11.0 and higher.
D
D
a
a
t
t
a
a
f
f
o
o
r
r
m
m
a
a
t
t
:
:
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
e
e
s
s
,
,
C
C
o
o
m
m
m
m
a
a
n
n
d
d
s
s
o
o
r
r
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 active, unless a different register number is sent.
Tipp:
double registers were made active only when the higher register is transferred.
Order
of
bits
Register Data
Register Data
Lo-Byte
Lo-Byte
Hi-byte
Hi-byte
76543210 76543210 76543210 76543210
0xxxxxxx 1xxxxxxx
0xxxxxxx 1xxxxxxx
Tipp:
if not otherwise stated: for registers Bit 7 is not used and always 0.
for data, Bit 7 is always high.
