UDT Not scaling float when passing in parameters

I am working on a large project converting 5 Wonderware applications to Ignition. I have created a UDT for analog signals and set up parameters for things like Description, Max_EU and Max_Raw values. I have bound these parameters into the scaling information for some Float OPC tags. I set up the initial OPC address as "[{Device}]HR" and just manually overrode that with the actual address (i.e.HR16). I populate each UDT instance parameter accordingly (Max_EU = 22 & Max_Raw = 10000). No errors on the tag, but the values for everything are reporting the RawValue, even though I have liner scaling set up. Here are images of the UDT and one of the tags.

If I again manually override the {Max_EU} binding, without changing anything, it starts scaling. Wondering if anyone has seen this.

One additional issue is regarding coil reads. Have a tag set up with address C1027. Ignition is reporting it as being on. Wonderware reads that register as off. Most Coils are reading correctly, but have a handful reading wrong value. Any thoughts?

Thanks in advance for any suggestions.

Removed: Misread and posted Siemens driver info instead of Modbus.

This is modbus, based on the use of HR item paths. C is for coils in modbus.

Whoops, must've been a long week and some brain fog on a Friday, I swear I read siemens driver in the post which is why I posted that.

You might want to expand a specific tag in the tag browser and review the effective value of each property.

Might want to post a screenshot of that here as well.

could be off by one register, double check the Zero-based Addressing setting on your device connection to make sure it matches with your device map

My first question here is, why are we scaling these in Ignition and not in the PLC?

Edit: Are Max_EU and Max_Raw UDT parameters? Yes, I see they are. If not, they won't work. Tag properties' binding are not full-featured like expression tags--they cannot reference tags. (With certain partial exceptions for alarm props.)

Never mind.

The defaults for those parameters should definitely not be zero, though.

Because the original project was done 20 years ago.

Yes @pturmel , Max_EU and Max_Raw are parameters of the UDT.

It looks like the UDT definition does not have a value for max EU. Try putting a default value in there (100) - also make max raw be non-0. See if that changes anything. I've had issues with strings where if you make the parameter and don't do anything with it it comes in null. Even just making the string a " " and then deleting the " " fixes it.