Lawo / ember-plus

Ember+ control protocol - Slick and free for all!

Home Page:https://github.com/Lawo/ember-plus/wiki

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Ember+ 1.4: Templates - do you have a sample code how to use it

yboujraf opened this issue · comments

Dear @KimonHoffmann @mkeuck

Do you have any sample of Template, StreamDescription, StreamFormat, StringIntegerCollection

We implemented the Ember+ library Producer and client supporting your latest specifications.

And we are looking some ber file where we could tests our library.

This is the list

TAG number

image

We supporting till TAG-17 but the new one are not supported at this time. Is there any new Tag used in the Lawo products like MC², NOVA, UHDCORE,A_MIC, ......

If yes, again , do you have any ber file to test it?

Template

I have implemented the Template in my own library but don't have any sample code to test it.

If yes, again , do you have any ber file to test it?

StringIntegerCollection

Type Tag: Application – 8
Type: Sequence
Members: Entries of type StringIntegerPair

The StringIntegerCollection is a sequence that contains StringIntegerPairs. This
structure is used by the enumeration map.

If yes, again , do you have any ber file to test it?

StreamDescriptor

StreamDescriptor
Tag: Context – 16
Type: StreamDescription
A StreamDescriptor is required when a single stream entry contains more than one
value and is provided as octet string. The descriptor then provides the internal data
offset and the stream value format. The formats available can be found in the DTD at the
end of the document.
The descriptor is used additionally to the StreamIdentifier and provides a way to transmit
values in a raw array of bytes. This array may contain an arbitrary number of streamvalues, for each parameter that has the same StreamIdentifier. The descriptor specifies
where the data for a parameter is located within the buffer and how to decode it.
The value type of the descriptor must match the Type or the Value property.
Note
The streaming mechanism is typically used to transmit several values within a small
interval. Therefore, there should be as less overhead as possible.

If yes, again , do you have any ber file to test it?

StreamDescription

StreamDescription ::=
 [APPLICATION 12] IMPLICIT
 SEQUENCE {
 format [0] StreamFormat,
 offset [1] Integer32 -- byte offset of the value in the streamed blob.
 }
-- type: 0=uint, 1=int, 2=float
-- size: 0=1byte, 1=2byte, 2=4byte, 3=8byte
-- endianness: 0=big, 1=little
StreamFormat ::=
 INTEGER {
 unsignedInt8 ( 0), -- 00000 00 0
 unsignedInt16BigEndian ( 2), -- 00000 01 0
 unsignedInt16LittleEndian ( 3), -- 00000 01 1
 unsignedInt32BigEndian ( 4), -- 00000 10 0
 unsignedInt32LittleEndian ( 5), -- 00000 10 1
 unsignedInt64BigEndian ( 6), -- 00000 11 0
 unsignedInt64LittleEndian ( 7), -- 00000 11 1
 signedInt8 ( 8), -- 00001 00 0
 signedInt16BigEndian (10), -- 00001 01 0
 signedInt16LittleEndian (11), -- 00001 01 1
 signedInt32BigEndian (12), -- 00001 10 0
 signedInt32LittleEndian (13), -- 00001 10 1
Ember+ protocol specification Lawo GmbH
87
 signedInt64BigEndian (14), -- 00001 11 0
 signedInt64LittleEndian (15), -- 00001 11 1
 ieeeFloat32BigEndian (20), -- 00010 10 0
 ieeeFloat32LittleEndian (21), -- 00010 10 1
 ieeeFloat64BigEndian (22), -- 00010 11 0
 ieeeFloat64LittleEndian (23) -- 00010 11 1
 }

If yes, again , do you have any ber file to test it?

Best Regards
Youssef