#Rsi shift exchange how to#
#Rsi shift exchange serial#
#Rsi shift exchange full#

The intention is to use a KRC4 compact controller with most recent software. I'm afraid some it is going a little over my head. Like letting the robot move at full-auto speeds even if it's in T1. RSI also isn't safe - in order to give you that fine-grained control, it bypasses a lot of typical safety features. With RSI, if you order the robot to accelerate too quickly, you'll generate a system fault.

Like acceleration - for a normal program, if you order the robot to accelerate at a bazillion m/s^2, it'll simply do the best it can and soldier on. RSI gives you much more granular control, at the cost of 'working without a net' - you now become responsible for handling many of the low-level functions that the robot would normally handle for you invisibly. but that means you have to create an RSI program that handles all the duties that the KRC would normally. RSI can allow you to remotely control the robot all the way down to the servo level, if you want. Frankly, using FieldBus simplifies things a great deal, and removes all the TCP/UDP complexities from your setup. If you have a PLC, I would strongly advice using whatever FieldBus your robot and PLC support, over trying to do a serial-to-Ethernet conversion. I don't think RSI is emulatable without an actual robot, although that may have changed - and even if it is, you'd have to have OfficeLite or an OfficePC, neither of which is cheap. What controller and KSS version? It matters more than the robot model. Perhaps a lot of questions, but I'd be very grateful if I can get some pointers, even just to confirm I am not barking up the wrong tree.

So are there other simpler ways to control the axes that simply make it a slave without depending on responses?įinally is there any way to emulate an RSI environment without actually running a robot? I'm thinking perhaps some less destructive mode might be necessary to start with, while sorting out the basics. Because I would be going through a converter I'm not sure if I could handle that scenario. I did read that in atleast one mode the sender has to respond to requests from RSI in order to continue responding, so it would need to be a two way communication. Also would an ethernet device have to be configured in any special way? Are certain types of converter going to be better than others?

#Rsi shift exchange how to#

Then if that is possible, is there any information on how to setup an ethernet connection and how to format the data. In other words move it anywhere in it's available xyz space responding to a continuous stream of data.

#Rsi shift exchange full#

I have read that external signals can be used to modify or offset the robot position (within limits such as +- 5deg), but I'm not clear if there is a way to completely control it through the full limits of its movement.

#Rsi shift exchange serial#

I am considering using a serial to ethernet adapter to transmit the data from my program and control the robot, either in cartesian space, either full 6 dof or in palletising mode. My program has a PLC which generates quad signals for directly controlling servo drives as well as an RS232 option which can stream ascii values in realtime.

I am investigating the possibility of controlling a Kuka KR10 via the RSI interface from an external program. I'm new here and perhaps this question is dealt with on other threads, but thought I'd start by asking the specific question.