How to force a deactivated block to scan again

If you request memory addresses from a device that are NOT valid on the device, in many TOP Server drivers, by default, the driver will mark the block of memory that is was reading as invalid, because the device typically will continue to fail that entire read transaction, and marking the block as "Deactivated" prevents the driver from wasting time on failed read transactions.

By simply adding another tag with the same address as one of those in the deactivated block, and then using OPC Quick Client to attempt to read that tag again, the block would be put back on scan and if successful, keep scanning from then onward.

Afterwards, the extra tag can be deleted.

Basically anything you do that would modify the contents of what is requested to be read in a block, even if it is asking for the same point again from the block, will cause that block to be reevaluated and scan attempted again