-
Notifications
You must be signed in to change notification settings - Fork 250
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Problem while assigning KONI port to WINDOWS #59
Comments
StartKRC manages some kind of virtual network that enables the remote connection. Connect a monitor, mouse and keyboard to the cabinet, reboot, and try the steps again directly from the embedded Windows interface. |
@mbanerj 👍 Thanks a lot, it works ! I never realised Windows stayed alive after stopping KRC, although it makes sense now. |
Yeah, there's a lot of complexity going on inside the workings of the cabinet... glad you got it working! |
Hello!
I have troubles following the procedure detailed in cabinet_setup. I'm trying to setup your solution on KUKA Sunrise.OS 1.7.1.12.
During Step 2:
The green icon you describe seems to be the StartKRC Icon. Right-clicking on it displays "KRCDiag" or "Stop KRC". However, "Stop KRC" just shuts down the robot computer and disables the remote connexion as well, which prevents from doing any further action.
Hence, my solution was to go in the task manager and end StartKRC.exe.
Running this command led to the following output in the KUKA Hardware Manager :
any attempts at killing more processes (KUKAHardwareService.exe, KukaPMService.exe KUKAHardwareManager) before step 3 didn't improve the last WARN message...
After hoping against hope that I was supposed to get this output, I tried the forth step. However, no reference to a KONI port seems to have added to the list of my Device Manager..
I believe I couldn't shutdown KRC properly (step 2) which prevented me from going any further. Would you have any solution to my problem please?
The text was updated successfully, but these errors were encountered: