Tools I built for
FANUC work, given away.
Backup utilities, a better TP dialect, a KAREL unit test framework, parsers, log analyzers and editor support. Most of it started as something I needed on a Friday night in a plant and kept using afterward.
BackupTool
A free command-line utility for pulling backups from many FANUC robots at once. Point it at a list of IPs, walk away, come back to a full set of ASCII and image backups.
Fexcel
Label FANUC robot I/O, registers and position registers straight from a spreadsheet. Keep the plant's naming in Excel where everyone can edit it, then push it to the controllers.
KUnit
A small unit testing framework for FANUC KAREL. Write assertions against your routines and run them on the controller instead of finding the bug with a robot in motion.
tp.js
A TP parser, interpreter and runtime in JavaScript — enough to step through a program in a browser tab and watch registers change without a controller nearby.
vqlog.js
Reads FANUC line tracking VQLOG files and turns the raw dump into something you can actually reason about when a tracking cell is drifting.
vim-tp
Syntax highlighting for FANUC TP in Vim, so an .ls file stops looking like a wall of undifferentiated text.
vim-karel
The same treatment for KAREL: keywords, builtins, strings and comments all where your eye expects them.
TP+
An improved dialect of FANUC's TP language. No longer maintained by ONE Robotics — the project has a new home with active development.
Using one of these?
Bug reports, patches and "it broke on R-30iB Plus" notes are all welcome. Issues on GitHub get read.
github.com/onerobotics →Need something built for you?
The open source work is the free half. When you need a tool, plugin or integration that fits your plant exactly, that's the paid half.
See consulting →