# Automated Read/Write Access to ARSim Hardware I/O from External Tools **URL:** \ **Category:** B&R Software & Runtime\ **Tags:** arsim\ **Created:** [March 6, 2026, 7:52pm UTC](https://community.br-automation.com/t/automated-read-write-access-to-arsim-hardware-i-o-from-external-tools/10409 "2026-03-06T19:52:25Z")\ **Posts on this page:** 1\ **Showing post:** 5
**Author:** ![christoph.hilchenbac](https://dub1.discourse-cdn.com/brcommunity/user_avatar/community.br-automation.com/christoph.hilchenbac/32/423_2.png) [@christoph.hilchenbac](https://community.br-automation.com/u/christoph.hilchenbac)\ **Post date:** [March 9, 2026, 7:43am UTC](https://community.br-automation.com/t/automated-read-write-access-to-arsim-hardware-i-o-from-external-tools/10409/5 "2026-03-09T07:43:02Z")
Hi, my approach is similar to Marcus’s. Call [AsIOEnableForcing()](https://help.br-automation.com/#/en/6/libraries/asio/fbks/asioenableforcing.html) in \_INIT when CPU is in Simulation mode ([DiagCpuIsARsim ()](https://help.br-automation.com/#/en/6/libraries%2Fasiodiag%2Ffbks%2Fdiagcpuisarsim.html)=TRUE). 1.) If you need real time simulation data (every cycle matters) write to the variable connected to the forced IO- datapoint by \_CYCLIC application code. Automation Studio uses plain text files for source code, which can also be created using external tools and filled with simulation files (e.g. fill an array). 2.) if real time is not important one can use PVI’s LinkNodes to write to the IO- datapoints from outside. We had a similar discussion a few days ago: [Is it possible to activate variable forcing (ForceActivated / ForceActivated Value) programmatically via PVI? - Ask Questions / Programming - B&R Community](https://community.br-automation.com/t/is-it-possible-to-activate-variable-forcing-forceactivated-forceactivated-value-programmatically-via-pvi/10377/4) --- _[View the full topic](https://community.br-automation.com/t/automated-read-write-access-to-arsim-hardware-i-o-from-external-tools/10409)._