Hi
You should use RAB(robot application builder) if you want to migrate your pc app to IRC5.
RAB consist of
FlexPendant SDK - Dev app’s on the flexpendant (FlexPendant Interface needed on the controller)
PC SDK - Dev app’s on a PC (PC Interface needed on the controller)
There is a problem about that… The PalletMaster application is a full system developed in Sweden, so complex, and I have not an open source code of it.
If I use RAB, I would have to start from the begining, and that is not an option now, time factor is critic…
The robot and controller are comming soon, for now I need to figure out what’s going on. So I don’t have contact with the robot to tell you specific details of what I see,
I hope resolve it, but you mean that there is no ethernet communication diferences betwen controllers that I need to worry about? I agree the idea, it shouln’t change, it must be transparent for the user, otherwise it could be a disaster
Interlink has support for both S4 and IRC5 controllers. The alias type will determine which API (RobAPI or RAP) is used to connect to the controller. I can’t think of anything singificant that you can do in RAP that can’t be done on the IRC5.