RobotStudio event

PCSDK: Exception when using MainComputer


Hi All,

when I try and access the contollers MainComputerServiceInfo I get the above exception, with the message "The URL used to initialize the helper does not resolve to a valid object."

Obviously I'm doing something wrong. 

What I do is (I've shortened it):

var scanner = new NetworkScanner();
NetworkScanner.AddRemoteController(ipAddress);
scanner.Scan();
ControllerInfo[] controllerInfos = scanner.GetControllers();
robotController = ControllerFactory.CreateFrom(controllerInfos[0]);
robotController.Logon(UserInfo.DefaultUser);


Now I have a connection to my robotController, testing it with the following code creates a perfect backup, so the controller works.

var backupManager = new BackupManager(robotController );
backupManager.LocalName = systemName + ".lzo";
backupManager.Backup();



When I call 

MainComputerServiceInfo infCPU = robotController .MainComputerServiceInfo; 

OR 

string str = robotController .MainComputerServiceInfo.CpuInfo;

Gives me the above error.

Does anybody knows whats going wrong? A piece of sample code perhaps?



Exception details:

ABB.Robotics.GenericControllerException was unhandled
  Message= The URL used to initialize the helper does not resolve to a valid object.
  Source=ABB.Robotics.Adapters.IRC5
  ExtendedErrorInformation=""
  StackTrace:
       at Adapters.Data.Get()
       at ABB.Robotics.Controllers.Internal.DAL.DataAccessObject.GetStringValue(String instance, String attribute)
       at ABB.Robotics.Controllers.Internal.DAL.MainComputerDevice.GetCpuTemperature()
       at ABB.Robotics.Controllers.Internal.Controller.GetMainComputerServiceInfo()
       at ABB.Robotics.Controllers.Controller.get_MainComputerServiceInfo()
       at AWL.RobotController.AbbController.GetCpuInfo() in c:UserssboDocumentsVisual Studio 2012ProjectsRobotStudioAddin1AbbControllerAbbController.cs:line 57
       at WindowsFormsApplication2.Form1.button1_Click(Object sender, EventArgs e) in c:UserssboDocumentsVisual Studio 2012ProjectsRobotStudioAddin1WindowsFormsApplication2Form1.cs:line 26
       at System.Windows.Forms.Control.OnClick(EventArgs e)
       at System.Windows.Forms.Button.OnClick(EventArgs e)
       at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)
       at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
       at System.Windows.Forms.Control.WndProc(Message& m)
       at System.Windows.Forms.ButtonBase.WndProc(Message& m)
       at System.Windows.Forms.Button.WndProc(Message& m)
       at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
       at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
       at System.Windows.Forms.NativeWindow.DebuggableCallback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
       at System.Windows.Forms.UnsafeNativeMethods.DispatchMessageW(MSG& msg)
       at System.Windows.Forms.Application.ComponentManager.System.Windows.Forms.UnsafeNativeMethods.IMsoComponentManager.FPushMessageLoop(Int32 dwComponentID, Int32 reason, Int32 pvLoopData)
       at System.Windows.Forms.Application.ThreadContext.RunMessageLoopInner(Int32 reason, ApplicationContext context)
       at System.Windows.Forms.Application.ThreadContext.RunMessageLoop(Int32 reason, ApplicationContext context)
       at System.Windows.Forms.Application.Run(Form mainForm)
       at WindowsFormsApplication2.Program.Main() in c:UserssboDocumentsVisual Studio 2012ProjectsRobotStudioAddin1WindowsFormsApplication2Program.cs:line 18
       at System.AppDomain._nExecuteAssembly(Assembly assembly, String[] args)
       at System.AppDomain.ExecuteAssembly(String assemblyFile, Evidence assemblySecurity, String[] args)
       at Microsoft.VisualStudio.HostingProcess.HostProc.RunUsersAssembly()
       at System.Threading.ThreadHelper.ThreadStart_Context(Object state)
       at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
       at System.Threading.ThreadHelper.ThreadStart()
  InnerException: 




John Wiberg2013-02-22 15:53:00

Comments