Available source records contain 4 distinct definitions; some records may not include a definition.
Show 4 published definitions
dmsGraphicBitmapTable · unconfirmed
dmsGraphicBitmapTable OBJECT-TYPE
SYNTAX SEQUENCE OF DmsGraphicBitmapEntry
ACCESS not-accessible
STATUS mandatory
DESCRIPTION "<Definition> A table containing the bitmap information for the
graphic entries within the dmsGraphicTable. The values of a columnar object
in this table cannot be changed when the 'dmsGraphicStatus' object of the
corresponding row (row with the same index) in the dmsGraphicTable is any
value other than 'modifying'.
The dmsGraphicBitmapTable permits a complete bitmap to be downloaded to a
sign in pieces small enough to fit within a single SNMP SET request. Each
dmsGraphicBlockSize-sized chunk within the bitmap is represented by a
distinct row of the bitmap data Table; that is, the table is indexed by (1)
the dmsGraphicIndex, and (2) the dmsGraphicBlockNumber of a particular data
block within the graphic's data. Note that this mechanism is purely a
piecewise transfer method layered atop the bitmap data; when all the blocks
of a graphic image are downloaded, they must, as a group, conform to the
format described below. For a particular value of dmsGraphicIndex, the bitmap
defining the graphic image can be constructed in the following manner:
Concatenate the rows of the dmsGraphicBitmapTable with the matching
dmsGraphicIndex, in order of the dmsGraphicBlockNumber value, until the
resultant OCTET STRING is large enough to contain the entire image as defined
by the dmsGraphicHeight and dmsGraphicWidth values for the dmsGraphicIndex in
question.
The format of a complete bitmap is described here:
A complete bitmap image is defined by the rows in dmsGraphicBitmapTable that
share a common dmsGraphicIndex, as defined above. A bitmap image denotes the
color of each pixel within a rectangular region. The size of the rectangular
region is defined by the dmsGraphicHeight and dmsGraphicWidth objects.
If dmsGraphicType is a value of 'monochrome1bit', each bit within the bitmap
data corresponds to a pixel on the DMS display. Starting with the first byte
of the bitmap data, the most significant bit defines the state of the pixel
Page 227 NTCIP 1203 v02.35
in the upper left corner of the rectangular region. Byte 1 through byte N of
the bitmap data corresponds to the rectangular region by rows, left to right,
then top to bottom. If the rectangular region is not divisible by 8, the
remaining bits shall be 0 and contained in the lower bits of the last byte of
the bitmap data. In this case, the total size of the bitmap image in bytes is
given by this formula:
B = ((dmsGraphicWidth * dmsGraphicHeight) + 7)/8
The first term computes the approximate size of the bitmap in bytes, +/- one
byte. The second term computes whether the size of the bitmap in bits is
divisible by 8; if not, an extra byte is required to hold the remaining few
bits.
If dmsGraphicType is a value of 'monochrome8bit', each byte within the bitmap
data corresponds to a pixel on the DMS display. The first byte of the bitmap
data defines the state of the pixel in the upper left corner of the
rectangular region. Byte 1 through byte N of the bitmap data correspond to
the rectangular region by rows, left to right, then top to bottom. Each byte
is one of 255 shades of the monochrome color. In this case, the formula for
the total size of the bitmap in bytes is given by this formula:
B = (dmsGraphicWidth*dmsGraphicHeight)
If dmsGraphicType is a value of 'colorClassic', each byte within the bitmap
data corresponds to a pixel on the DMS display. The first byte of the bitmap
data defines the state of the pixel in the upper left corner of the
rectangular region. Byte 1 through byte N of the bitmap data correspond to
the rectangular region by rows, left to right, then top to bottom. The data
in each byte shall be one of the values indicated by dmsColorScheme under the
colorClassic type. In this case, the formula for the total size of the bitmap
in bytes is given by this formula:
B = (dmsGraphicWidth*dmsGraphicHeight)
If dmsGraphicType is a value of 'color24bit, sets of three bytes within the
bitmap data correspond to a pixel on the DMS display. The first three bytes
of the bitmap data define the state of the pixel in the upper left corner of
the rectangular region. Byte 1 through byte N of the bitmap data corresponds
to the rectangular region by rows, left to right, then top to bottom. The
first byte of the bitmap data shall be the value of blue for the upper left
pixel. The second byte of the bitmap data shall be the value of green for
the upper left pixel. The third byte of the bitmap data shall be the value
of red for the upper left pixel. In this case, the formula for the total size
of the bitmap in bytes is given by this formula:
B = (dmsGraphicWidth*dmsGraphicHeight)*3
All rows of the bitmap data Table must always logically exist (that is, under
no circumstances shall a controller produce a noSuchName error when asked for
a row of the dmsGraphicBitmapTable where
dmsGraphicIndex<=dmsGraphicsMaxEntries and
dmsGraphicBlockNumber<=dmsGraphicMaxSize/dmsGraphicBlockSize). If a GET
request is received for a block for which no corresponding SET request has
been accepted, then the controller shall return a block of length
dmsGraphicBlockSize, each octet of which has the value 0 (zero). Similarly,
when displaying a bitmap, the contents of any block within the bitmap image
that has not been defined by a SET operation shall be assumed to be a
sequence of octets with the value 0 (zero) and length dmsGraphicBlockSize.
--Data Examples
-- 'monochrome1bit' Example 1
--
Page 228 NTCIP 1203 v02.35
-- Example 1 shows a graphic of an arrow as it would be shown on the
-- DMS display.
-- Since the graphic size is 24x7 pixels (which is divisible by 8),
-- the bitwise layout below represents how it will appear on the display.
--
-- 765432107654321076543210
--
-- BYTE1..3 000000000000110000000000
-- BYTE4..6 000000000000011100000000
-- BYTE7..9 000000000000000111100000
-- BYTE10..12 001111111111111111111000
-- BYTE13..15 000000000000000111100000
-- BYTE16..18 000000000000011100000000
-- BYTE19..21 000000000000110000000000
--
-- The following represents the byte stream of the graphic above. The
-- 24 by 7 pixel graphic takes 21 bytes to define.
-- 00 0C 00 00 07 00 00 01 E0 3F FF F8 00 01 E0 00 07 00 00 0C 00
--
--
-- 'monochrome1bit' Example 2
-- The following pattern is what would be displayed. The graphic is
-- 10 pixels wide by 6 pixels high. The general appearance of the
-- sample graphic is an X followed by a 1.
--
-- 1000010010
-- 0100100110
-- 0011000010
-- 0011000010
-- 0100100010
-- 1000010111
--
-- Byte stream of example 2
--
-- Example 2 graphic is 8 bytes in length. Only 60 of the 64 bits
-- make up the graphic. The last 4 bits are buffer
-- 7654321076543210
--
-- BYTE1..2 1000010010010010
-- BYTE3..4 0110001100001000
-- BYTE5..6 1100001001001000
-- BYTE7..8 1010000101110000
--
-- The following represents the byte stream of the graphic above. The
-- 10 by 6 pixel graphic takes 8 bytes to define.
-- 84 92 63 08 C2 48 A1 70
--
--
-- 'color24bit' Example
--
-- Using the same graphic of an multi-colored arrow as the first example,
-- below is how it would
-- appear on the display. A legend is listed below for color reference.
--
-- 0-black, R-red, W-white, B-blue, G-green, P-purple
--
-- 0000RW00000000
Page 229 NTCIP 1203 v02.35
-- 00000RRW000000
-- 0000000RRRW000
-- GGGGGGGPPPPPW0
-- 0000000PPPB000
-- 00000PPB000000
-- 0000PB00000000
--
-- The following represents the byte stream of the graphic above. The
-- 14 by 7 pixel graphic takes 294 bytes to define. The bytes below
-- are and red, green, blue representation of the pixels to be displayed.
-- In hexadecimal each grouping below represents a pixel.
-- BBGGRR where BB represents a byte of blue in hexadecimal
-- and GG represents a byte of green in hexadecimal
-- and RR represents a byte of red in hexadecimal
--
-- 000000 000000 000000 000000 0000FF FFFFFF 000000 000000 000000 000000
-- 000000 000000 000000 000000 000000 000000 000000 000000 000000 0000FF
-- 0000FF FFFFFF 000000 000000 000000 000000 000000 000000 000000 000000
-- 000000 000000 000000 000000 000000 0000FF 0000FF 0000FF FFFFFF 000000
-- 000000 000000 00FF00 00FF00 00FF00 00FF00 00FF00 00FF00 00FF00 FF33CC
-- FF33CC FF33CC FF33CC FF33CC FFFFFF 000000 000000 000000 000000 000000
-- 000000 000000 000000 FF33CC FF33CC FF33CC FF0000 000000 000000 000000
-- 000000 000000 000000 000000 000000 FF33CC FF33CC FF0000 000000 000000
-- 000000 000000 000000 000000 000000 000000 000000 000000 FF33CC FF0000
-- 000000 000000 000000 000000 000000 000000 000000 000000
<Table Type> static
<Object Identifier> 1.3.6.1.4.1.1206.4.2.3.9.10.7"
::= {graphicDefinition 7}dmsGraphicBitmapTable · unconfirmed
dmsGraphicBitmapTable OBJECT-TYPE
SYNTAX SEQUENCE OF DmsGraphicBitmapEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION "<Definition> A table containing the bitmap information for the
graphic entries within the dmsGraphicTable. The values of a columnar object
in this table cannot be changed when the 'dmsGraphicStatus' object of the
corresponding row (row with the same index) in the dmsGraphicTable is any
value other than 'modifying'.
The dmsGraphicBitmapTable permits a complete bitmap to be downloaded to a
sign in pieces small enough to fit within a single SNMP SetRequest. Each
dmsGraphicBlockSize-sized chunk within the bitmap is represented by a
distinct row of the bitmap data Table; that is, the table is indexed by (1)
the dmsGraphicIndex, and (2) the dmsGraphicBlockNumber of a particular data
block within the graphic's data. Note that this mechanism is purely a
piecewise transfer method layered atop the bitmap data; when all the blocks
of a graphic image are downloaded, they must, as a group, conform to the
format described below. For a particular value of dmsGraphicIndex, the bitmap
defining the graphic image can be constructed in the following manner:
Concatenate the rows of the dmsGraphicBitmapTable with the matching
dmsGraphicIndex, in order of the dmsGraphicBlockNumber value, until the
resultant OCTET STRING is large enough to contain the entire image as defined
by the dmsGraphicHeightV4 and dmsGraphicWidth values for the dmsGraphicIndex
in question.
The format of a complete bitmap is described here:
A complete bitmap image is defined by the rows in dmsGraphicBitmapTable that
share a common dmsGraphicIndex, as defined above. A bitmap image denotes the
color of each pixel within a rectangular region. The size of the rectangular
region is defined by the dmsGraphicHeightV4 and dmsGraphicWidth objects.
If dmsGraphicType is a value of 'monochrome1bit', each bit within the bitmap
data corresponds to a pixel on the DMS display. Starting with the first byte
of the bitmap data, the most significant bit defines the state of the pixel
in the upper left corner of the rectangular region. Byte 1 through byte N of
the bitmap data corresponds to the rectangular region by rows, left to right,
then top to bottom. If the rectangular region is not divisible by 8, the
remaining bits shall be 0 and contained in the lower bits of the last byte of
the bitmap data. In this case, the total size of the bitmap image in bytes is
given by this formula:
B = ((dmsGraphicWidth * dmsGraphicHeightV4) + 7)/8
The first term computes the approximate size of the bitmap in bytes, +/- one
byte. The second term computes whether the size of the bitmap in bits is
divisible by 8; if not, an extra byte is required to hold the remaining few
bits.
If the dmsColorScheme is monochrome8bit, colorClassic, or color24bit, and the
graphic is defined with dmsGraphicType monochrome1bit, then pixels are
displayed with the foreground color (bit = 1) or black (bit = 0). Note that
if dmsGraphicTransparentEnabled is set to 1 and dmsGraphicTransparentColor is
set to 0 then a monochrome1bit graphic can be displayed in the same manner as
a font character.
If dmsGraphicType is a value of 'monochrome8bit', each byte within the bitmap
data corresponds to a pixel on the DMS display. The first byte of the bitmap
data defines the state of the pixel in the upper left corner of the
rectangular region. Byte 1 through byte N of the bitmap data correspond to
the rectangular region by rows, left to right, then top to bottom. Each byte
is one of 255 shades of the monochrome color. In this case, the formula for
the total size of the bitmap in bytes is given by this formula:
B = (dmsGraphicWidth*dmsGraphicHeightV4)
If dmsGraphicType is a value of 'colorClassic', each byte within the bitmap
data corresponds to a pixel on the DMS display. The first byte of the bitmap
data defines the state of the pixel in the upper left corner of the
rectangular region. Byte 1 through byte N of the bitmap data correspond to
the rectangular region by rows, left to right, then top to bottom. The data
in each byte shall be one of the values indicated by dmsColorScheme under the
colorClassic type. In this case, the formula for the total size of the bitmap
in bytes is given by this formula:
B = (dmsGraphicWidth*dmsGraphicHeightV4)
If dmsGraphicType is a value of 'color24bit, sets of three bytes within the
bitmap data correspond to a pixel on the DMS display. The first three bytes
of the bitmap data define the state of the pixel in the upper left corner of
the rectangular region. Byte 1 through byte N of the bitmap data corresponds
to the rectangular region by rows, left to right, then top to bottom. The
first byte of the bitmap data shall be the value of blue for the upper left
pixel. The second byte of the bitmap data shall be the value of green for the
upper left pixel. The third byte of the bitmap data shall be the value of red
for the upper left pixel. In this case, the formula for the total size of the
bitmap in bytes is given by this formula:
B = (dmsGraphicWidth*dmsGraphicHeightV4)*3
All rows of the bitmap data Table must always logically exist (that is, under
no circumstances shall a controller produce a SuchInstance value when asked
for a row of the dmsGraphicBitmapTable where
dmsGraphicIndex<=dmsGraphicsMaxEntries and
dmsGraphicBlockNumber<=dmsGraphicMaxSize/dmsGraphicBlockSize). If a GET
request is received for a block for which no corresponding SET request has
been accepted, then the controller shall return a block of length
dmsGraphicBlockSize, each octet of which has the value 0 (zero). Similarly,
when displaying a bitmap, the contents of any block within the bitmap image
that has not been defined by a SET operation shall be assumed to be a
sequence of octets with the value 0 (zero) and length dmsGraphicBlockSize.
--Data Examples
-- 'monochrome1bit' Example 1
--
-- Example 1 shows a graphic of an arrow as it would be shown on the
-- DMS display.
-- Since the graphic size is 24x7 pixels (which is divisible by 8),
-- the bitwise layout below represents how it appears on the display.
--
-- 765432107654321076543210
--
-- BYTE1..3 000000000000110000000000
-- BYTE4..6 000000000000011100000000
-- BYTE7..9 000000000000000111100000
-- BYTE10..12 001111111111111111111000
-- BYTE13..15 000000000000000111100000
-- BYTE16..18 000000000000011100000000
-- BYTE19..21 000000000000110000000000
--
-- The following represents the byte stream of the graphic above. The
-- 24 by 7 pixel graphic takes 21 bytes to define.
-- 00 0C 00 00 07 00 00 01 E0 3F FF F8 00 01 E0 00 07 00 00 0C 00
--
--
-- 'monochrome1bit' Example 2
-- The following pattern is what would be displayed. The graphic is
-- 10 pixels wide by 6 pixels high. The general appearance of the
-- sample graphic is an X followed by a 1.
--
-- 1000010010
-- 0100100110
-- 0011000010
-- 0011000010
-- 0100100010
-- 1000010111
--
-- Byte stream of example 2
--
-- Example 2 graphic is 8 bytes in length. Only 60 of the 64 bits
-- make up the graphic. The last 4 bits are buffer
-- 7654321076543210
--
-- BYTE1..2 1000010010010010
-- BYTE3..4 0110001100001000
-- BYTE5..6 1100001001001000
-- BYTE7..8 1010000101110000
--
-- The following represents the byte stream of the graphic above. The
-- 10 by 6 pixel graphic takes 8 bytes to define.
-- 84 92 63 08 C2 48 A1 70
--
--
-- 'color24bit' Example
--
-- Using the same graphic of an multi-colored arrow as the first example,
-- below is how it would
-- appear on the display. A legend is listed below for color reference.
--
-- 0-black, R-red, W-white, B-blue, G-green, P-purple
--
-- 0000RW00000000
-- 00000RRW000000
-- 0000000RRRW000
-- GGGGGGGPPPPPW0
-- 0000000PPPB000
-- 00000PPB000000
-- 0000PB00000000
--
-- The following represents the byte stream of the graphic above. The
-- 14 by 7 pixel graphic takes 294 bytes to define. The bytes below
-- are and red, green, blue representation of the pixels to be displayed.
-- In hexadecimal each grouping below represents a pixel.
-- BBGGRR where BB represents a byte of blue in hexadecimal
-- and GG represents a byte of green in hexadecimal
-- and RR represents a byte of red in hexadecimal
--
-- 000000 000000 000000 000000 0000FF FFFFFF 000000 000000 000000 000000
-- 000000 000000 000000 000000 000000 000000 000000 000000 000000 0000FF
-- 0000FF FFFFFF 000000 000000 000000 000000 000000 000000 000000 000000
-- 000000 000000 000000 000000 000000 0000FF 0000FF 0000FF FFFFFF 000000
-- 000000 000000 00FF00 00FF00 00FF00 00FF00 00FF00 00FF00 00FF00 FF33CC
-- FF33CC FF33CC FF33CC FF33CC FFFFFF 000000 000000 000000 000000 000000
-- 000000 000000 000000 FF33CC FF33CC FF33CC FF0000 000000 000000 000000
-- 000000 000000 000000 000000 000000 FF33CC FF33CC FF0000 000000 000000
-- 000000 000000 000000 000000 000000 000000 000000 000000 FF33CC FF0000
-- 000000 000000 000000 000000 000000 000000 000000 000000
<Table Type> static
<Object Identifier> 1.3.6.1.4.1.1206.4.2.3.10.7"
::= {graphicDefinition 7}dmsGraphicBitmapTable · mandatory
dmsGraphicBitmapTable OBJECT-TYPE
SYNTAX SEQUENCE OF DmsGraphicBitmapEntry
ACCESS not-accessible
STATUS mandatory
DESCRIPTION "<Definition> A table containing the bitmap information for the graphic entries within the dmsGraphicTable. The values of a columnar object in this table cannot be changed when the 'dmsGraphicStatus' object of the corresponding row (row with the same index) in the dmsGraphicTable is any value other than 'modifying'.
The dmsGraphicBitmapTable permits a complete bitmap to be downloaded to a sign in pieces small enough to fit within a single SNMP SET request. Each dmsGraphicBlockSize-sized chunk within the bitmap is represented by a distinct row of the bitmap data Table; that is, the table is indexed by (1) the dmsGraphicIndex, and (2) the dmsGraphicBlockNumber of a particular data block within the graphic's data. Note that this mechanism is purely a piecewise transfer method layered atop the bitmap data; when all the blocks of a graphic image are downloaded, they must, as a group, conform to the format described below. For a particular value of dmsGraphicIndex, the bitmap defining the graphic image can be constructed in the following manner: Concatenate the rows of the dmsGraphicBitmapTable with the matching dmsGraphicIndex, in order of the dmsGraphicBlockNumber value, until the resultant OCTET STRING is large enough to contain the entire image as defined by the dmsGraphicHeight and dmsGraphicWidth values for the dmsGraphicIndex in question.
The format of a complete bitmap is described here:
A complete bitmap image is defined by the rows in dmsGraphicBitmapTable that share a common dmsGraphicIndex, as defined above. A bitmap image denotes the color of each pixel within a rectangular region. The size of the rectangular region is defined by the dmsGraphicHeight and dmsGraphicWidth objects.
If dmsGraphicType is a value of 'monochrome1bit', each bit within the bitmap data corresponds to a pixel on the DMS display. Starting with the first byte of the bitmap data, the most significant bit defines the state of the pixel in the upper left corner of the rectangular region. Byte 1 through byte N of the bitmap data corresponds to the rectangular region by rows, left to right, then top to bottom. If the rectangular region is not divisible by 8, the remaining bits shall be 0 and contained in the lower bits of the last byte of the bitmap data. In this case, the total size of the bitmap image in bytes is given by this formula:
B = ((dmsGraphicWidth * dmsGraphicHeight) + 7)/8
The first term computes the approximate size of the bitmap in bytes, +/- one byte. The second term computes whether the size of the bitmap in bits is divisible by 8; if not, an extra byte is required to hold the remaining few bits.
If the dmsColorScheme is monochrome8bit, colorClassic, or color24bit, and the graphic is defined with dmsGraphicType monochrome1bit, then pixels are displayed with the foreground color (bit = 1) or black (bit = 0). Note that if dmsGraphicTransparentEnabled is set to 1 and dmsGraphicTransparentColor is set to 0 then a monochrome1bit graphic can be displayed in the same manner as a font character.
If dmsGraphicType is a value of 'monochrome8bit', each byte within the bitmap data corresponds to a pixel on the DMS display. The first byte of the bitmap data defines the state of the pixel in the upper left corner of the rectangular region. Byte 1 through byte N of the bitmap data correspond to the rectangular region by rows, left to right, then top to bottom. Each byte is one of 255 shades of the monochrome color. In this case, the formula for the total size of the bitmap in bytes is given by this formula:
B = (dmsGraphicWidth*dmsGraphicHeight)
If dmsGraphicType is a value of 'colorClassic', each byte within the bitmap data corresponds to a pixel on the DMS display. The first byte of the bitmap data defines the state of the pixel in the upper left corner of the rectangular region. Byte 1 through byte N of the bitmap data correspond to the rectangular region by rows, left to right, then top to bottom. The data in each byte shall be one of the values indicated by dmsColorScheme under the colorClassic type. In this case, the formula for the total size of the bitmap in bytes is given by this formula:
B = (dmsGraphicWidth*dmsGraphicHeight)
If dmsGraphicType is a value of 'color24bit, sets of three bytes within the bitmap data correspond to a pixel on the DMS display. The first three bytes of the bitmap data define the state of the pixel in the upper left corner of the rectangular region. Byte 1 through byte N of the bitmap data corresponds to the rectangular region by rows, left to right, then top to bottom. The first byte of the bitmap data shall be the value of blue for the upper left pixel. The second byte of the bitmap data shall be the value of green for the upper left pixel. The third byte of the bitmap data shall be the value of red for the upper left pixel. In this case, the formula for the total size of the bitmap in bytes is given by this formula:
B = (dmsGraphicWidth*dmsGraphicHeight)*3
All rows of the bitmap data Table must always logically exist (that is, under no circumstances shall a controller produce a noSuchName error when asked for a row of the dmsGraphicBitmapTable where dmsGraphicIndex<=dmsGraphicsMaxEntries and dmsGraphicBlockNumber<=dmsGraphicMaxSize/dmsGraphicBlockSize). If a GET request is received for a block for which no corresponding SET request has been accepted, then the controller shall return a block of length dmsGraphicBlockSize, each octet of which has the value 0 (zero). Similarly, when displaying a bitmap, the contents of any block within the bitmap image that has not been defined by a SET operation shall be assumed to be a sequence of octets with the value 0 (zero) and length dmsGraphicBlockSize.
--Data Examples
-- 'monochrome1bit' Example 1
--
-- Example 1 shows a graphic of an arrow as it would be shown on the
-- DMS display.
-- Since the graphic size is 24x7 pixels (which is divisible by 8),
-- the bitwise layout below represents how it appears on the display.
--
-- 765432107654321076543210
--
-- BYTE1..3 000000000000110000000000
-- BYTE4..6 000000000000011100000000
-- BYTE7..9 000000000000000111100000
-- BYTE10..12 001111111111111111111000
-- BYTE13..15 000000000000000111100000
-- BYTE16..18 000000000000011100000000
-- BYTE19..21 000000000000110000000000
--
-- The following represents the byte stream of the graphic above. The
-- 24 by 7 pixel graphic takes 21 bytes to define.
-- 00 0C 00 00 07 00 00 01 E0 3F FF F8 00 01 E0 00 07 00 00 0C 00
--
--
-- 'monochrome1bit' Example 2
-- The following pattern is what would be displayed. The graphic is
-- 10 pixels wide by 6 pixels high. The general appearance of the
-- sample graphic is an X followed by a 1.
--
-- 1000010010
-- 0100100110
-- 0011000010
-- 0011000010
-- 0100100010
-- 1000010111
--
-- Byte stream of example 2
--
-- Example 2 graphic is 8 bytes in length. Only 60 of the 64 bits
-- make up the graphic. The last 4 bits are buffer
-- 7654321076543210
--
-- BYTE1..2 1000010010010010
-- BYTE3..4 0110001100001000
-- BYTE5..6 1100001001001000
-- BYTE7..8 1010000101110000
--
-- The following represents the byte stream of the graphic above. The
-- 10 by 6 pixel graphic takes 8 bytes to define.
-- 84 92 63 08 C2 48 A1 70
--
--
-- 'color24bit' Example
--
-- Using the same graphic of an multi-colored arrow as the first example,
-- below is how it would
-- appear on the display. A legend is listed below for color reference.
--
-- 0-black, R-red, W-white, B-blue, G-green, P-purple
--
-- 0000RW00000000
-- 00000RRW000000
-- 0000000RRRW000
-- GGGGGGGPPPPPW0
-- 0000000PPPB000
-- 00000PPB000000
-- 0000PB00000000
--
-- The following represents the byte stream of the graphic above. The
-- 14 by 7 pixel graphic takes 294 bytes to define. The bytes below
-- are and red, green, blue representation of the pixels to be displayed.
-- In hexadecimal each grouping below represents a pixel.
-- BBGGRR where BB represents a byte of blue in hexadecimal
-- and GG represents a byte of green in hexadecimal
-- and RR represents a byte of red in hexadecimal
--
-- 000000 000000 000000 000000 0000FF FFFFFF 000000 000000 000000 000000
-- 000000 000000 000000 000000 000000 000000 000000 000000 000000 0000FF
-- 0000FF FFFFFF 000000 000000 000000 000000 000000 000000 000000 000000
-- 000000 000000 000000 000000 000000 0000FF 0000FF 0000FF FFFFFF 000000
-- 000000 000000 00FF00 00FF00 00FF00 00FF00 00FF00 00FF00 00FF00 FF33CC
-- FF33CC FF33CC FF33CC FF33CC FFFFFF 000000 000000 000000 000000 000000
-- 000000 000000 000000 FF33CC FF33CC FF33CC FF0000 000000 000000 000000
-- 000000 000000 000000 000000 000000 FF33CC FF33CC FF0000 000000 000000
-- 000000 000000 000000 000000 000000 000000 000000 000000 FF33CC FF0000
-- 000000 000000 000000 000000 000000 000000 000000 000000
<Table Type> static
<Object Identifier> 1.3.6.1.4.1.1206.4.2.3.10.7"
::= {graphicDefinition 7}dmsGraphicBitmapTable · mandatory
dmsGraphicBitmapTable OBJECT-TYPE
SYNTAX SEQUENCE OF DmsGraphicBitmapEntry
ACCESS not-accessible
STATUS mandatory
DESCRIPTION "<Definition> A table containing the bitmap information for the
graphic entries within the dmsGraphicTable. The values of a columnar object
in this table cannot be changed when the 'dmsGraphicStatus' object of the
corresponding row (row with the same index) in the dmsGraphicTable is any
value other than 'modifying'.
The dmsGraphicBitmapTable permits a complete bitmap to be downloaded to a
sign in pieces small enough to fit within a single SNMP SET request. Each
dmsGraphicBlockSize-sized chunk within the bitmap is represented by a
distinct row of the bitmap data Table; that is, the table is indexed by (1)
the dmsGraphicIndex, and (2) the dmsGraphicBlockNumber of a particular data
block within the graphic's data. Note that this mechanism is purely a
piecewise transfer method layered atop the bitmap data; when all the blocks
of a graphic image are downloaded, they must, as a group, conform to the
format described below. For a particular value of dmsGraphicIndex, the bitmap
defining the graphic image can be constructed in the following manner:
Concatenate the rows of the dmsGraphicBitmapTable with the matching
dmsGraphicIndex, in order of the dmsGraphicBlockNumber value, until the
resultant OCTET STRING is large enough to contain the entire image as defined
by the dmsGraphicHeight and dmsGraphicWidth values for the dmsGraphicIndex in
question.
The format of a complete bitmap is described here:
A complete bitmap image is defined by the rows in dmsGraphicBitmapTable that
share a common dmsGraphicIndex, as defined above. A bitmap image denotes the
color of each pixel within a rectangular region. The size of the rectangular
region is defined by the dmsGraphicHeight and dmsGraphicWidth objects.
If dmsGraphicType is a value of 'monochrome1bit', each bit within the bitmap
data corresponds to a pixel on the DMS display. Starting with the first byte
of the bitmap data, the most significant bit defines the state of the pixel
in the upper left corner of the rectangular region. Byte 1 through byte N of
the bitmap data corresponds to the rectangular region by rows, left to right,
then top to bottom. If the rectangular region is not divisible by 8, the
remaining bits shall be 0 and contained in the lower bits of the last byte of
the bitmap data. In this case, the total size of the bitmap image in bytes is
given by this formula:
B = ((dmsGraphicWidth * dmsGraphicHeight) + 7)/8
The first term computes the approximate size of the bitmap in bytes, +/- one
byte. The second term computes whether the size of the bitmap in bits is
divisible by 8; if not, an extra byte is required to hold the remaining few
bits.
If the dmsColorScheme is monochrome8bit, colorClassic, or color24bit, and the
graphic is defined with dmsGraphicType monochrome1bit, then pixels are
displayed with the foreground color (bit = 1) or black (bit = 0). Note that
if dmsGraphicTransparentEnabled is set to 1 and dmsGraphicTransparentColor is
set to 0 then a monochrome1bit graphic can be displayed in the same manner as
a font character.
If dmsGraphicType is a value of 'monochrome8bit', each byte within the bitmap
data corresponds to a pixel on the DMS display. The first byte of the bitmap
data defines the state of the pixel in the upper left corner of the
rectangular region. Byte 1 through byte N of the bitmap data correspond to
the rectangular region by rows, left to right, then top to bottom. Each byte
is one of 255 shades of the monochrome color. In this case, the formula for
the total size of the bitmap in bytes is given by this formula:
B = (dmsGraphicWidth*dmsGraphicHeight)
If dmsGraphicType is a value of 'colorClassic', each byte within the bitmap
data corresponds to a pixel on the DMS display. The first byte of the bitmap
data defines the state of the pixel in the upper left corner of the
rectangular region. Byte 1 through byte N of the bitmap data correspond to
the rectangular region by rows, left to right, then top to bottom. The data
in each byte shall be one of the values indicated by dmsColorScheme under the
colorClassic type. In this case, the formula for the total size of the bitmap
in bytes is given by this formula:
B = (dmsGraphicWidth*dmsGraphicHeight)
If dmsGraphicType is a value of 'color24bit, sets of three bytes within the
bitmap data correspond to a pixel on the DMS display. The first three bytes
of the bitmap data define the state of the pixel in the upper left corner of
the rectangular region. Byte 1 through byte N of the bitmap data corresponds
to the rectangular region by rows, left to right, then top to bottom. The
first byte of the bitmap data shall be the value of blue for the upper left
pixel. The second byte of the bitmap data shall be the value of green for the
upper left pixel. The third byte of the bitmap data shall be the value of red
for the upper left pixel. In this case, the formula for the total size of the
bitmap in bytes is given by this formula:
B = (dmsGraphicWidth*dmsGraphicHeight)*3
All rows of the bitmap data Table must always logically exist (that is, under
no circumstances shall a controller produce a noSuchName error when asked for
a row of the dmsGraphicBitmapTable where
dmsGraphicIndex<=dmsGraphicsMaxEntries and
dmsGraphicBlockNumber<=dmsGraphicMaxSize/dmsGraphicBlockSize). If a GET
request is received for a block for which no corresponding SET request has
been accepted, then the controller shall return a block of length
dmsGraphicBlockSize, each octet of which has the value 0 (zero). Similarly,
when displaying a bitmap, the contents of any block within the bitmap image
that has not been defined by a SET operation shall be assumed to be a
sequence of octets with the value 0 (zero) and length dmsGraphicBlockSize.
--Data Examples
-- 'monochrome1bit' Example 1
--
-- Example 1 shows a graphic of an arrow as it would be shown on the
-- DMS display.
-- Since the graphic size is 24x7 pixels (which is divisible by 8),
-- the bitwise layout below represents how it appears on the display.
--
-- 765432107654321076543210
--
-- BYTE1..3 000000000000110000000000
-- BYTE4..6 000000000000011100000000
-- BYTE7..9 000000000000000111100000
-- BYTE10..12 001111111111111111111000
-- BYTE13..15 000000000000000111100000
-- BYTE16..18 000000000000011100000000
-- BYTE19..21 000000000000110000000000
--
-- The following represents the byte stream of the graphic above. The
-- 24 by 7 pixel graphic takes 21 bytes to define.
-- 00 0C 00 00 07 00 00 01 E0 3F FF F8 00 01 E0 00 07 00 00 0C 00
--
--
-- 'monochrome1bit' Example 2
-- The following pattern is what would be displayed. The graphic is
-- 10 pixels wide by 6 pixels high. The general appearance of the
-- sample graphic is an X followed by a 1.
--
-- 1000010010
-- 0100100110
-- 0011000010
-- 0011000010
-- 0100100010
-- 1000010111
--
-- Byte stream of example 2
--
-- Example 2 graphic is 8 bytes in length. Only 60 of the 64 bits
-- make up the graphic. The last 4 bits are buffer
-- 7654321076543210
--
-- BYTE1..2 1000010010010010
-- BYTE3..4 0110001100001000
-- BYTE5..6 1100001001001000
-- BYTE7..8 1010000101110000
--
-- The following represents the byte stream of the graphic above. The
-- 10 by 6 pixel graphic takes 8 bytes to define.
-- 84 92 63 08 C2 48 A1 70
--
--
-- 'color24bit' Example
--
-- Using the same graphic of an multi-colored arrow as the first example,
-- below is how it would
-- appear on the display. A legend is listed below for color reference.
--
-- 0-black, R-red, W-white, B-blue, G-green, P-purple
--
-- 0000RW00000000
-- 00000RRW000000
-- 0000000RRRW000
-- GGGGGGGPPPPPW0
-- 0000000PPPB000
-- 00000PPB000000
-- 0000PB00000000
--
-- The following represents the byte stream of the graphic above. The
-- 14 by 7 pixel graphic takes 294 bytes to define. The bytes below
-- are and red, green, blue representation of the pixels to be displayed.
-- In hexadecimal each grouping below represents a pixel.
-- BBGGRR where BB represents a byte of blue in hexadecimal
-- and GG represents a byte of green in hexadecimal
-- and RR represents a byte of red in hexadecimal
--
-- 000000 000000 000000 000000 0000FF FFFFFF 000000 000000 000000 000000
-- 000000 000000 000000 000000 000000 000000 000000 000000 000000 0000FF
-- 0000FF FFFFFF 000000 000000 000000 000000 000000 000000 000000 000000
-- 000000 000000 000000 000000 000000 0000FF 0000FF 0000FF FFFFFF 000000
-- 000000 000000 00FF00 00FF00 00FF00 00FF00 00FF00 00FF00 00FF00 FF33CC
-- FF33CC FF33CC FF33CC FF33CC FFFFFF 000000 000000 000000 000000 000000
-- 000000 000000 000000 FF33CC FF33CC FF33CC FF0000 000000 000000 000000
-- 000000 000000 000000 000000 000000 FF33CC FF33CC FF0000 000000 000000
-- 000000 000000 000000 000000 000000 000000 000000 000000 FF33CC FF0000
-- 000000 000000 000000 000000 000000 000000 000000 000000
<Table Type> static
<Object Identifier> 1.3.6.1.4.1.1206.4.2.3.10.7"
::= {graphicDefinition 7}