My beta version of the Speakercraft - Commanfusion interface is in
test phase. The unit converts the hex and resends the strings as
ASCII. (Each Speakercraft MZC has a state machine created that
interrogates the connected devices and builds a real time
representation)
Question1 - I have terminated each string with CR LF - this is then
entered into System Manager as the EOM. Is there a Start of String
marker I can use to define the text string more clearly for processing
by CF.
Question2 - The device has the option of multiple protocols - I am
designing a CommandFusion protocol to allow direct interface for CF
without the need for Regex strings to extract the ASCII data. The info
is available as Joins. When the join value changes state, it will send
the updated join data. Do you recommend I keep a data life cycle
counter for each join and transmit the join after the life span has
expired ?
Question3 - Can you point me to resources regarding implementation of
your protocol other than the existing developers manual.
Thanks
--
You received this message because you are subscribed to the Google Groups "CommandFusion" group.
To post to this group, send email to commandfusion@googlegroups.com.
To unsubscribe from this group, send email to commandfusion+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/commandfusion?hl=en.


Comments
0 comments to "Speakercraft - ASCII"
Post a Comment