PC SDK networkscanner doesn't find robostudio virtual controller and real contr. (service port)

RobotStudio
1

Hi All,
I am a beginner and I started to develop the first simple c# application that performs the scanning of the network in order to find controllers that is reported in the application manual of PC SDK. I tried to run the application looking if it could scan the virtual controller on robot studio (installed on the same computer of visual studio), but it doesn’t work. I tried to run again connecting real controller through service port, but it doesn’t work again. Someone can help me? Thank you so much!!!

Perla

2

hmm,

Have you got your references right on VS ?

How about configuring your ports ? you might have Dynamic IP address. Make it static.

I have written some code that is highly simplified ( for beginners ) using IronPython.

If you run this it should work without config and upload a sample rapid file onto your virtual robot. Make sure to have Roboware 5.15 installed !

3

ohh i forgot to add ! you need to pass in a third argument in the cmd line , something like “0,0,0” or “0,0,10” if you want the robot to move by 10 mm in the z direction

4

I am still working on the project. but in a while I would have exposed a very simple API for anyone to use basic functionality of the robot without hassle : ) I just need help from other ppl like yourself to push it forward.

What exactly do you wish to do with the robot ? just general linear motion or rotation and stuff like that ?

5

Hi
Check that you have the PC Interface option on the controller. Need when working with the PC SDK

6

Its the PC interface option enabled by default ? where can I go to make it default if its not default ?

This reminds me of a problem - I have PC interface enable but I am unable to use Sockets :frowning:

Any idea what might be the problem there ?

7

For a virtual controller you check the option when building your system. For a real controller it’s enabled if you have a key that includes the option.
When communicating with the controller over ethernet you should use the factory network port and not the service port (real controller).