Skip to content

PJRC Teensy based hardware device to interface a Line 6 FBV3 to a USB-Serial Port to access its functionality through Max for Live or Max/MSP

License

Notifications You must be signed in to change notification settings

JanosGit/FBV3Bridge

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

10 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

FBV3Bridge

PJRC Teensy 3.2 based device to interface a Line 6 FBV3 to a USB-Serial Port to access its functionality through Max for Live or Max/MSP

Inspired by some other projects out there (this one by rasmartins and this one by wrbi), that have successfully interfaced the older FBV-range boards, the goal of this project is to make use of the extended functionality of the FBV3 Board - most of all the RGB-LEDs.

Within this project, I'm responsible of designing the hardware prototype, inlcuding some simple teensy programming and doing a quick proof-of-concept on the PC-Software side. All the following Max-based work and protocol reverse engineering will be done by Soundmanufacture.

The projects consists of a small PCB, interfacing the RS485 over RJ45 connection used by Line 6 to the Teensy's UART ports. Furthermore, it powers the FBV3 with 9V over the USB connection with the help of a step-up-converter.

Hardware top view Hardware bottom view

The software for the Teensy has two modes of operation: If both an amp and an FBV3 Board are plugged in, it logs the communication between the two endpoints and prints it in human-readable form to the USB-Serial output. If no amp is plugged in, it sends the same initialization-sequence an amp would send to the FBV3 board and redirects the in/out data streams byte-transparent to the USB-Serial port afterwards.

This way, the protocol of the FBV3 can be reverse-engineered in the first step and then be used to implement a Max for Live device that will be used to control Ableton Live through the FVB3.

Here you see a screenshot of the serial communication logged

goSerial screenshot

What's known is that the messages alway contain of the start byte 0xF0, followed by a byte specifying the length of the message (excluding the start byte and the length byte). This can be noticed in the log above. Furthermore, I already found the exact sequences to control the red LEDs and the LCD display. With that knowledge, I created a demo Max patcher:

Max screenshot

The rest will be found out by reverse engineering!

About

PJRC Teensy based hardware device to interface a Line 6 FBV3 to a USB-Serial Port to access its functionality through Max for Live or Max/MSP

Resources

License

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published