Flyfish FF32 Gets GUI

[CWroos] has written an impressive GUI for the Flyfish FF32. The Flyfish is a port expander of sorts, allowing the user access to a large array of I/O , analog inputs, SPI, I2C and a few other connectivity options over a USB connection. There is no driver as it uses a native HID driver in the operating system of the device it’s attached to. It’s not just tethered to a PC either. It works with Raspberry Pi, Beaglebone and several other SBCs.

program window

[CWroos]’s GUI makes it easier than ever to interact with the FF32. It has a script editor allowing you to run and edit scripts on the fly (pun intended). It appears he’s actually written his own basic like language for the scripting, which he goes into great detail on his site. There’s a blinky script example, and few more complex examples that will show you how to read temperature and control a servo.

There is also the ability to control the hardware directly allowing you to set pins, read firmware version, set the USB address and several other options. If you have an FF32 lying around, be sure to check out [CWroos]’s program and let us know how it works for you.

8 thoughts on “Flyfish FF32 Gets GUI

  1. Does anyone know about this FF32 chip? Looking at the page it just looks like it may be a re-labeled PIC with USB support… or is this an acuall chip made by some small company in dip format, seems odd? Looked through data sheet real quick I didnt see anything about it being a micro, or if it does High speed USB which is what I am interested in.

    1. Almost certainly yes, it’s a programmed micro and has been done before. It remembers me about the IO-Warrior and similar devices of a few years ago, this one though is more powerful and very nicely priced, which makes it more interesting. The only problem with all these devices is that technology moves on, so that when the company stops writing firmwares for the new chips you have to reenginer everything for a different platform that does the same thing.

      Device like this one should come with a one line signed contract from whoever writes the firmware: “when we go belly up or development is stopped (insert most appropriate legalese definition here), code is released as open source within 1-3 years”. The 1-3 years would let them to monetize from IP without screwing customers.

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.