# 3.2 Controller Initialization

**URL:** <https://tech-community.robotics.abb.com/t/3-2-controller-initialization/815>\
**Category:** Robot Controller\
**Created:** [August 21, 2006, 5:31pm UTC](https://tech-community.robotics.abb.com/t/3-2-controller-initialization/815 "2006-08-21T17:31:27Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![jwinne](https://avatars.discourse-cdn.com/v4/letter/j/3e96dc/32.png) [@jwinne](https://tech-community.robotics.abb.com/u/jwinne)\
**Post date:** [August 21, 2006, 5:31pm UTC](https://tech-community.robotics.abb.com/t/3-2-controller-initialization/815/1 "2006-08-21T17:31:27Z")

</div>

Having troubles with the controller intializing. Using IRB440L30-2000.  
When I switch to a 3.2 controller I have no problems. I have had this in  
the past. When I swtiched to 3.2 the fix helped, but now I am back to  
square 1. Any thoughts? I was told in the past that the Tuesday updates  
by Microsoft may have something to do with it. In fact, I was fine on  
Monday and Tuesday was not. :rage:

---

<div class="post-metadata">

**Author:** ![Anders\_S](https://avatars.discourse-cdn.com/v4/letter/a/ce7236/32.png) [@Anders\_S](https://tech-community.robotics.abb.com/u/Anders_S)\
**Post date:** [August 22, 2006, 3:53pm UTC](https://tech-community.robotics.abb.com/t/3-2-controller-initialization/815/2 "2006-08-22T15:53:28Z")

</div>

If it’s only the IRB4400L30-2000 controller you have problem with, perform a coldstart and try again. If that doesn’t help create a new controller for that mechanism.

If you have problem with all your V4.0 controllers it could depend on that you are missing the mediapool for the controllers. The default controllers in RobotStudio 3.2 are using the mediapool: 3HAC6811-2.13. Make sure that you have that mediapool (a folder with that name) in the following folder: C:Program FilesCommon FilesABB AutomationMediaPool

---

<div class="post-metadata">

**Author:** ![jwinne](https://avatars.discourse-cdn.com/v4/letter/j/3e96dc/32.png) [@jwinne](https://tech-community.robotics.abb.com/u/jwinne)\
**Post date:** [August 22, 2006, 6:11pm UTC](https://tech-community.robotics.abb.com/t/3-2-controller-initialization/815/3 "2006-08-22T18:11:47Z")

</div>

We had created a “backup” controller some time ago. When we set that to  
the active robot the problem was fixed. Looks like I have a problem with  
the default controller.

Any thoughts on how to fix the default?

Cold starts did not work.

I have yet to create a new controller, is that an easy task? :worried:

Are these problems typical for version 3.2 of RS?

---

<div class="post-metadata">

**Author:** ![Anders\_S](https://avatars.discourse-cdn.com/v4/letter/a/ce7236/32.png) [@Anders\_S](https://tech-community.robotics.abb.com/u/Anders_S)\
**Post date:** [August 23, 2006, 9:51am UTC](https://tech-community.robotics.abb.com/t/3-2-controller-initialization/815/4 "2006-08-23T09:51:49Z")

</div>

If a cold start doesn’t help you have to create a new controller.

How to create a copy of an existing controller is explained in the RobotStudio Online help.

These problems are not typical for RS 3.2. Normally will a cold start solve the problem.