Firefly

Firefly offers a set of comprehensive software tools dedicated to bridging the gap between Grasshopper, (a free plug-in for Rhino) the Arduino microcontroller and other input/output devices. It allows near real-time data flow between the digital and physical worlds – enabling the possibility to explore virtual and physical prototypes with unprecedented fluidity.

Load Previous Comments
  • Matthew J Flamm

    Im (probably) re-upping to Rhino 6 over 5 because the display and presentation tools in the new build are plausibly at a level of maturity now that they can be used for scaled drawings and shaded view ports in a professional capacity.  Built-in section tools?!  mind-blown!

    It looks like the last build of Firefly was in 2015 for Rhino5.

    Are there any plans to give this project another pass for Rhino 6 compatibility? 

    The Kinect 2.0 for Windows depth, color and mesh streams were of phenomenal utility!

    I understand that there are multiple routes for obtaining this information like the SDK, and PrimeSense had a branch working on Kinect..

    If this project is on a good long pause, I may try to write a bridge for this information into grasshopper for Rhino 6 using the Kinect 2.0 for Window SDK.  Im just a code-kitty though, so that might be more than is realistic ^_^.

    Is this binary right now? Rhino 5 + all plugins, or Rhino 6 and no promises?

    Miss you Firefly <3

  • Fabio Santarossa

    Hi Everybody, first of all thanks to Andy and Jason for your amazing creation. I'm working on a Gcode generated in grasshopper which I'd like to stream realtime to my Reprap 3D printer. Everything is OK if I save my gcode and send it to the machine in a classic way, but I'm struggling to send it directly through the serial port.

    I open the port, send the code and everything starts, but the movement are completely wrong. Only the G28 homing seems to work fine...Any suggestions? Thanks a lot!

  • Laura Fegely

    For anyone else who might be interested: I recently posted a question (in the wrong place) about correlating the bins output by the Frequency Spectrum component to their actual frequencies.

    I ended up doing a brief characterization of this using a frequency generator app on my phone while recording the bins of the peak point in each spectrum. There was a large amount of outlier removal (which I believe was due to a lack of synchronization between the peak frequency output of the component and my python peak finding component). The trendline equation I ended up with was:

    frequency = 29.095e^(0.0578*x) (with an R-square value of 0.9997 from 120 pts).