Bob,

Took a look, but your suggestion is far more work to get it going on the RPi2 than the link I provided in my original post, which is specifically already for the RPi and Rpi2. I am trying to avoid re-inventing the wheel, which I do not have time for. Not only that, the proposed solution (in my link) is hokey and not 100% documented, due to changes since it was posted.

The Wolfram language already has several functions for dealing with various interfaces

http://reference.wolfram.com/language/guide/UsingConnectedDevices.html

Device Types

• "Serial" — generic RS-232/RS-422 serial protocol;
• "GPIO" — general-purpose digital I/O directly from pins;
• "Arduino" — Arduino analog and digital I/O and autonomous code execution;
• "Camera", "RaspiCam", ... — cameras for capturing images;

This is one of the main purposes of the Wolfram Connected Devices Project. Clearly missing from the list is "GPIB" --- Since GPIB is one of the longest standing and standard interfaces, this project falls squarely under their charter ( Launching the Wolfram Connected Devices Project ) and they should be undertaking it ASAP. GPIB as it name suggests, is a GENERAL PURPOSE INTERFACE BUS and not specific to any one device, therefore it is much more important than a whole bunch of different drivers for all kinds of different devices (here today and gone tomorrow) shown on the connected devices home page. There are MANY GPIB instruments of all kinds (the connected devices project even has a bunch of them for specific instruments already), and although there are more modern and better interfaces, GPIB is still widely used, just as RS 232/422 is.

This project needs to get the attention of stephen wolfram if someone else employed by wolfram doesn't take it on!