search

HALRobotics / Beta

HAL Robotics Framework beta release and associated documentation.
17 stars 3 forks source link

"PCSDK not started" error message in Controller Configurator #116

Closed CQuinonez01 closed 2 years ago

CQuinonez01 commented 2 years ago

Prerequisites

Description

[Description of the issue] HAL Issue I don't understand why this happened. I uninstalled everything and added all the extensions that I did the first time and it happened again.

sebandraos commented 2 years ago

Hi @CQuinonez01 , the ABB PCSDK must not be installed on your PC. This is either installed with RobotStudio or as part of our installation process. However, both of these require admin rights to install. Assuming your ABB robot has RobotWare 6.0 or newer, I would recommend switching all of the subsystems (dropdowns on the left) currently using PCSDK to RobotWebServices and deactivating all of those which can't be switched.

Out of interest, did you intentionally not install the PCSDK during the ABB extension installation or did you not get that option?

Thanks.

CQuinonez01 commented 2 years ago

I installed HAL with ABB and when I go to open my files on Grasshopper that issue appears. I uninstalled everything dealing with HAL and ABB and redownloaded it and it happened again. Also I didn't have this issue before and it just happened today

sebandraos commented 2 years ago

If you had previously been using the PCSDK without issue then we'll need to think about what else might have caused the change in functionality. Before the issue started:

  1. Did you update the HAL Robotics Framework?
  2. Did you update Windows?
  3. Did you install any other software? e.g. RobotStudio?
  4. Did you change PC?
  5. Are you using a personal PC or something provided by an organisation that might have been modified by your IT department?
CQuinonez01 commented 2 years ago
  1. Not sure how to do that
  2. Not Recently
  3. RobotStudio was already installed when I downloaded HAL the first time
  4. NO
  5. My own laptop
sebandraos commented 2 years ago

In which case, this looks like a duplicate of this issue: https://github.com/HALRobotics/Beta/issues/107 I would recommend using the workaround I described in my first message then because if our software hasn't changed and RobotStudio hasn't changed then it sounds like a local machine configuration issue that's going to be very complicated to get to the bottom of. RobotWebServices is designed to avoid this kind of issue so I would head down that route.