# Bug RobotStudio IO config (24.4.11080.0)

**URL:** <https://tech-community.robotics.abb.com/t/bug-robotstudio-io-config-24-4-11080-0/11777>\
**Category:** UpFeed\
**Created:** [February 4, 2025, 10:38am UTC](https://tech-community.robotics.abb.com/t/bug-robotstudio-io-config-24-4-11080-0/11777 "2025-02-04T10:38:46Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Newman](https://dub1.discourse-cdn.com/flex005/user_avatar/tech-community.robotics.abb.com/newman/32/2900_2.png) [@Newman](https://tech-community.robotics.abb.com/u/Newman)\
**Post date:** [February 4, 2025, 10:38am UTC](https://tech-community.robotics.abb.com/t/bug-robotstudio-io-config-24-4-11080-0/11777/1 "2025-02-04T10:38:46Z")

</div>

Hi  
The device map disappears when I remove io device for a signal.  
This was possible on last RS version.  
/David

---

<div class="post-metadata">

**Author:** ![Newman](https://dub1.discourse-cdn.com/flex005/user_avatar/tech-community.robotics.abb.com/newman/32/2900_2.png) [@Newman](https://tech-community.robotics.abb.com/u/Newman)\
**Post date:** [February 13, 2025, 9:48am UTC](https://tech-community.robotics.abb.com/t/bug-robotstudio-io-config-24-4-11080-0/11777/2 "2025-02-13T09:48:33Z")

</div>

I’ve made a bug report to my local ABB support.

---

<div class="post-metadata">

**Author:** ![Newman](https://dub1.discourse-cdn.com/flex005/user_avatar/tech-community.robotics.abb.com/newman/32/2900_2.png) [@Newman](https://tech-community.robotics.abb.com/u/Newman)\
**Post date:** [February 13, 2025, 12:28pm UTC](https://tech-community.robotics.abb.com/t/bug-robotstudio-io-config-24-4-11080-0/11777/3 "2025-02-13T12:28:48Z")

</div>

In a way, it may seem normal that the mapping disappears when you remove the device, but at the same time it has been a nice feature.  
Thus, early in the simulation phase of a project, you can prepare e.g. machine signals and make them virtual (remove the device for all signal with multi select) but the mapping remains. Then you avoid alarms that the device is missing and you can also manipulate inputs with RobotStudio for testing.  
Then, when you do the commissioning at the customer site, you set the real device for all signals by multiselecting in RS. A simple 1 minute job even if you have hundreds of signals.

---

<div class="post-metadata">

**Author:** ![Newman](https://dub1.discourse-cdn.com/flex005/user_avatar/tech-community.robotics.abb.com/newman/32/2900_2.png) [@Newman](https://tech-community.robotics.abb.com/u/Newman)\
**Post date:** [March 11, 2025, 11:09am UTC](https://tech-community.robotics.abb.com/t/bug-robotstudio-io-config-24-4-11080-0/11777/4 "2025-03-11T11:09:21Z")

</div>

My local support don’t see this as a problem.  
@Maxim : Do you know if this “feature” I have been using for 10 years in reality has been a bug that now has been “fixed”?

Back in the RW5 days we used to create a virtual “FAKE\_BOARD” for devicenet signals, but since RW6 this has not been needed.

---

<div class="post-metadata">

**Author:** ![Maxim](https://dub1.discourse-cdn.com/flex005/user_avatar/tech-community.robotics.abb.com/maxim/32/4429_2.png) [@Maxim](https://tech-community.robotics.abb.com/u/Maxim)\
**Post date:** [March 11, 2025, 11:52am UTC](https://tech-community.robotics.abb.com/t/bug-robotstudio-io-config-24-4-11080-0/11777/5 "2025-03-11T11:52:12Z")

</div>

Hej David,

Can you send me more details in PM, regarding what info your local ABB provided to you?

Thanks!