It appears the Dynamic DEMUX object in R2 - LonWorks jar - Conversions folder is not setting the output bits incorrectly for some SNVT_State values?

Issue

It appears the Dynamic DEMUX object in R2 - LonWorks jar - Conversions folder is not setting the output bits incorrectly for some SNVT_State values?

Product Line

TAC I/A Series

Environment

R2, all versions

Cause

Third party definition of the SNVT_State bits.

Resolution

The dynamicDEMUX object takes a "SNVT_State" value in and breaks it into representative output bits 0 to 15.  This object assigns the bits from bit0 to bit15 with bit0 on the left and counting left to right. 

For example a SNVT_State value of 1000 hex is 1000000000000000 in binary, therefore the DEMUX object would show bit0 on.  Some third party manufacturers define their SNVT_State bits starting with bit15 on the left and counting down left to right ,so in this example their documentation would indicate bit15 should be on .  Once this is understood the DEMUX output bits can be interpreted correctly.