Multi-State Blocks (Issues)

[Jim_Okapal]

The Multi-State blocks that I tested were:

1) Supervised Input (Tested all 6 input configurations)

2) Tristate Output

3) MultiState Consumer

4) MultiState Producer

5) MS Value

Common Issues:

1) Of the multi-state blocks that have configurable text choices, the values displayed

on the main wiresheet blocks will still show some version of the original text of State1,

State2,State3...or 1,2,3, etc.   The properties inside the block will display the proper

text.

2) Supervised Inputs (On, Off, Trouble) and Tristate Outputs (Off, On, -On)  have

particular texts that are very valuable to show for diagnostics instead of numbers

on the main wiresheet.  These blocks are showing 1,2,3 on the wiresheet.

3)  When connecting multi-state blocks together, the input priorities appear to be

non-connectable.   The only way to connect them is Value Output to Value Output

4) If using the priority arrays to set a value in a block, they'll still show the original

State1, State2, State3 verbiage as choices.

[Will_Workman · Accepted solution]

This issue has been logged as a defect and should be fixed in a future build.

[ChrisHoward]

@Jim_Okapal ,

I believe all of the multi-state (and state text) issues are now fixed in v29. 

[Jim_Okapal]

Chris,

Pictured below is the issue I'm seeing in all builds, including Build 29

[ChrisHoward]

@Jim_Okapal 

With regards to the State_Text; further testing shows that hitting the 'Refresh' button in the Property Sheet will solve the issue. Can you give this a try?

[Jim_Okapal]

Chris,

Refreshing the property sheet had been working in the past for some items,

similar to when changing text for boolean states from Active/Inactive to On/Off, etc   

The Multi-States have updated in a similar fashiion,  and that part has been working 

from the earlier modules with the exception of the input priorities (as seen in the picture

of the Object Property with Priority 16) The wiresheet on the other hand has been

problematic from the beginning. 

I'll post the full pictures below of the property sheet setup along with the BOG file.

For this module update, i've got all modules in the N4 supervisor as showing version

29, it was a brand new station, the controllers were put back to factory fresh as

un-initialized devices, and the firmware is 3.2.1.  (Usually i've done those steps with

each module update just so i'm dealing with a blank slate and possibly remove one

layer of issues)

To access the BOG file, we'll have to send a private email since i've got our standard

password.   I should have made it different, but i'm a creature of habit.