Multistate indicator not binding correctly

Ignition
,
1

Hey, I've got a simple window that's throwing an error in the multistate indicator property binding.

Here's the XML.
window.xml (37.2 KB)

Everything looks correct inside the XML and the only change here from a project that worked should be 'changing the tags the tank binds to and its position'.

2

Is this the same as over here?

If so, don't double post. This is against this forum's rules.

If you don't get an answer on a post within several days, it is appropriate to add a "ping" comment to the original post. If you are in a hurry, open a support ticket.

3

It's slightly different, the old post was incorrect in symptoms and had the wrong XML, so I've flagged a mod to delete it.

If it would have been more appropriate to edit that post instead, I will do so in the future -- I'm used to forums where delete/add is the norm though, my apologies

4

Yes, do. This forum keeps edits visible, so there's no misunderstandings.

5

Will do in the future, and apologies again!
Didn't intend to spam

6

Any ideas on the object level?

7

The expression on the state property doesn't match the tank name. (Cylindical Tank vs Cylindrical Tank 1

1 Like
8

Where are you seeing Cylindrical Tank 1 in the xml?

9

This is what I see when i import your xml into a new window.

image
image1329×396 26.7 KB

1 Like
10

It removed the listener/binding from the multistate because Cylindrical Tank didn't exist.

1 Like
11

Hmmm, ok -- why is the name of the tank changing?

12

Beats me. lol.

Seriously, I tried changing the name to Cylindrical Tank Test in the XML and it imported as Cylindrical Tank Test 1

13

So, offhand, I believe this is a bug on setting items from XML. Can you post an export of the window instead?

14

When I export the window, the expression just comes out as blank

15

Try importing this one. You'll need to update the tank bindings.
Leor_test_2025-02-24_1318.zip (9.2 KB)

1 Like
16

Tried a new setup
deviceconnupdate_2025-02-24_1044.zip (9.6 KB)
Now finding a new odd error involving null prop names?

17

(Your import works, but I'm wondering why my process to generate those bindings isn't working)

18

Here's my new XML: @JordanCClark any ideas?
deviceconnupdate_2025-02-24_1137.zip (9.6 KB)

19

I've run through a bunch of improvements to now end up with the following XML:
nwindow.xml (25.5 KB)
It should just have the expression bindings for tank value and capacity changed (according to my internal differ,

Changes in o:

  • Removed: capacity expression binding to 10000
  • Added: capacity expression binding to {[default]Local_Tags/A1}+{[default]Local_Tags/A2}
  • Removed: value expression binding to {[default]1_A1-1_A10/1_A1}*{[default]1_A1-1_A10/1_A2}
  • Added: value tag binding to [default]Local_Tags/A1)

But I'm now seeing a deserialization error.

@pturmel @JordanCClark any ideas?

20
  • I would make this into a template
  • Properties within the template components should point to tags using indirect addresing.
  • Top level parameters of the template hold just enough info to drive the indirect tags.
1 Like