In this series:
Mitsubishi Movemaster Joint Tracking: Part 1 – Concept

Mitsubishi Movemaster Joint Tracking: Part 2 – Communication

Mitsubishi Movemaster Joint Tracking: Part 3 – Joint Tracking with Matlab

The first step in this project is to communicate with the robot arm. According to the manual the drive unit is capable of RS232 – but it uses the old 36 pin serial port. I spent quite a bit of time making a cable with the correct wiring (it got weird) to connect it to the single serial port on my work computer. This worked, and I made a post about it. The problem was that if I wanted to communicate with both arms at the same time, I needed another RS232 port. There are quite a few ways to do this – a USB to serial adapter, but I tried one of those and the pinout wasn’t right and it just refused to work with the drive unit. Long story short, I decided that the Parallel port on the drive unit was the easiest way forward. Don’t know what that is? Well brace yourself for the easiest-to-understand digital communication protocol ever!

Source: Wikipedia


So the parallel port has 8 data pins, each corresponding to a single bit. It also has a STROBE pin, that when the host (computer) pulls the STROBE pin low, the device reads the 8 data pins. There is also a BUSY and an ACK pin, but I’m not here to write about the parallel interface for a full page. Anyways, you load up the byte you want to send on the data pins, cycle the STROBE pin and boom, byte sent. The best part? These pins operate from 0-5V, not +-12V like RS232, so it is directly Arduino compatible.

I went ahead and connected the cable to a Teensy with an Arduino form breakout board:


I then made a quick program to copy whatever is in the serial monitor to the parallel interface. Check it out:

Here’s the code I used


Mitsubishi Movemaster Joint Tracking: Part 2 – Communication
Tagged on:                 

Leave a Reply