Research Note 01
FANUC integration — early KAREL-based model
An early plug-in structure wrapping AIVE TCP communication in FANUC KAREL. It became the basis of today's AimFactoryCore FANUC integration.
- FANUC KAREL
- Call AIVEReady()
- Call AIVEManual(mm,hz,sec)
- 9-step install
- Integrated into AimFactoryCore
On FANUC, the TCP/IP communication logic was implemented in the KAREL language rather than a TP program. As with Epson's RC+ SPEL+ and KUKA's KRL, the AIVE protocol strings are wrapped as Call AIVEReady, Call AIVELight(1/0), Call AIVEMotion(1/2), Call AIVEManual(mm,hz,sec).
Installation is nine steps — more complex than other brands. Loading the KAREL file on the controller and setting the communication port follow FANUC's particular procedure. Even so, once done, it can be called as simply as Call AIVEREADY from a TP program.
This plug-in was also distributed free to FANUC and AIVE users. The plug-ins for Epson, KUKA, Stäubli, UR, and FANUC all came from the shared goal of letting engineers control AIVE without handling TCP/IP socket communication directly.
The KAREL-based communication structure and AIVE protocol handling verified here became the basis of AimFactoryCore's direct FANUC integration today.
This technology is inside our products today
The structures validated in research notes are now part of AimFactoryCore and Robot Suite.