TimvH

Maybe check: - The library manager, are you maybe missing some libraries - Tools - CODESYS installer: update the CODESYS Visualization and Visualization support - Project - Project environment: maybe you need to update the visualization profile

Maybe it is better to use Interfaces to access the objects instead of pointers. But besides that, is "read_obj_ptr" a method? If yes, you need to call it, so add brackets behind the method call: read_obj_ptr();

Did you test this with the latest version of the CODESYS Visualization add-on? Something that you might want to test is if it works better when you disable the "Support client animation and overlay of native elements". Double-click on the VisualizationManager in your project to find this setting.

Yes, this will work.

Maybe the ModbusFB library is a good option for you. See: https://forge.codesys.com/prj/codesys-example/modbus/home/Home/

It is a known issue. It only happens with CODESYS and Wago controllers and the Persistent Variables. It seems related to using 64 bit variables in the PV list (e.g. LREAL). Internally in the PLC everything works okay. It is just a monitoring issue.

It seems like a bug in FBD. Work-around: If you click on the small line between the box and the output variable and delete this, the variable is removed. When you then assign a variable again (Ctrl-A), then you will see that the line will be a bit longer. If you then select the previous variable, you will see that it works.

have you tried: VisuElems.VisuStructClientData ?