Again, I know this should be a simple question, but where do I find how the network connections are configured on the KRC4, if I'm trying to use RSI to control the robot? I know that there is supposed to be a virtual network for KLI (virtual 5?), and I've read that RSI should come up somewhere as virtual 6, but when I do 'ipconfig' at the command prompt, all I see is the '192.168.0.1' on network 3. Thanks for the help!
KRC4 Network Connections
-
gtrobot -
December 12, 2013 at 5:40 AM -
Thread is marked as Resolved.
-
-
Make sure you are in Expert mode then Start-up > Network configuration
-
When I log into Network Configuration in Expert mode, all I see is the 172.31.1.147 connection. Shouldn't I see the KLI virtual 5 network? Am I doing something wrong? Thanks!
-
The HMI is running on VxWorks. To see Virtual 5 and 6, you need to show connections from inside VxWorks.
An easier way is to open the RSI-Network program from Start --> All Programs --> RSI-Networks
-
Since the HMI is running on VxWorks, wouldn't it be able to show the VxWorks connections? Is there an option for this in the Network Configuration menu?
I will check what comes up in the RSI-Network program again, but I don't remember seeing the virtual5 network there.
What does it mean that I can't see the virtual 5 connection in Network Configuration? Could this indicate that the KLI connection is not properly installed/configured? Is there an easy way to check that it has been (or to configure the KLI connection)? It used to be quite easy to check through telnet on the KRC2's, but I'm not sure if this is still possible with the KRC4.
Any help would be greatly appreciated. Thanks!
-
While you are on the network page there is an option, 'networks' I think, which will show you the virtual networks.
Sent using Tapatalk 4
-
Is this network page the best (or only?) interface/method for determining the network configuration (IP address, etc.) for the KLI and RSI?
I'm trying to diagnose a network issue (can ping external PC from KRC4 command line, but not KRC4 from external PC). I've read that KLI and RSI need to be on different subnets, but I have to be able to identify KLI first.
Again, any help is greatly appreciated. Thanks!
-
Hi,the KRC runs dual operating systems (Windows for visualization and VxWorks for Realtime robot control). These two "brains" have to communicate with each other. In your case most probably the VxWorks side did not boot correct. Hence the Windows side still waits for the connection. For a more specified diagnose why VxWorks does not start you could use
C:\Windows\System32\PuTTYtel.exe -vio -noflush
inside a windows cmd-shell openeing a putty-Shell of the VxWorks-side and post the content. Otherwise you could look at C:\KRC\ROBOTER\LOG\System\<LogFileName_Timestamp.csv> containing a somewhat reduced version of what is shown in the putty. If all of the above requires to much expert knowledge you could generate a KRCDiag using the "green Start KRC" button in the taskbar and send the KRCDiag to KUKA for analysis.
Fubini
I thought the above post might be useful since you can ping from inside VxWorks using Putty.
Also make sure you firewall is disabled to allow incoming connection from KRC4.
-
Is this network page the best (or only?) interface/method for determining the network configuration (IP address, etc.) for the KLI and RSI?I'm trying to diagnose a network issue (can ping external PC from KRC4 command line, but not KRC4 from external PC). I've read that KLI and RSI need to be on different subnets, but I have to be able to identify KLI first.
Again, any help is greatly appreciated. Thanks!
KLI is virtual network 5, by default. And 172.31.1.147 is its factory default IP address.
You're using RSI v 3.1? Section 5.2 of the manual covers how to set up the RSI-specific virtual interface.
-
SkyeFire This is good information to know, thank you.
So, with KLI set to 172.31.1.147, I set the remote PC to 172.31.1.148, and I am able to ping from both the KRC and the remote PC. Success!
However, when I set the RSI connect to 172.31.2.XX (as per suggestion in the 'KRC4 RSI Ethernet' thread), after a cold boot the teach pendant indicated it could to talk to the KRC4. Is this a common error, or is there something I missed setting the RSI IP?
Thanks for the help!
-
What subnet mask are you using, if it's 255.255.255.0 then you won't be able to connect, try 255.255.0.0.
(If you wish to restrict the subnet, 255.255.252.0 should work.)Sent using Tapatalk 4
-
My KRC4s seem to have a real problem re-connecting to the SmartPad after cold boots. Often it requires 2-3 reboots before the two will work together again. This has nothing to do with RSI -- it seems to just be a KRC4 issue.
-
^^^^ agreed, and its really annoying....
-
Well, I remember when the KRC1s were at the same stage of development -- Blue-Screen of Death on the KCP all the time. Of course, back then VxWorks and Windows were so isolated that the robot would keep running perfectly well, unless you needed to use the user interface. Those problems got resolved as the controller matured, and I'm sure the KRC4 will follow a similar trajectory. But I imagine it'll be a PITA for the next 2-3 years, though. Ah, well, that's the price we pay for technological progress, I guess.