FireFly Open Port

Hello,

I'm very new to FireFly, and have a basic setup question.

1. I'm running the Arduino/FireFly board off of COM3.

2. The FireFly Firmata loaded successfully, and I closed the IDE (so the port should not be open).

3. All releases of Rhino 5, Arduino, GH, and FF are the latest as of May 21st.

I Boolean toggled the port open, but I can't seem to get any output to display from the UnoRead component. I was hoping to see values from any of the analog inputs (APin5 depicted) connected as info gets sent back and forth between the Arduino and my comp. I'm getting simultaneous "Hooray" and "Whoops" messages, and I can't pinpoint why. See attached JPG.

Does it have to do with the fact that I have a list of COM ports? Even though I know COM 3 is the correct one as defined in the IDE, do I need to re-declare it in Grasshopper as well? Does the {0} shown impact this output?

Any direction is appreciated.

Thanks - JFig

Attachments:

GH_Arduino Exercise 2.jpg, 258 KB

Replies to This Discussion

Permalink Reply by Andy Payne on May 23, 2013 at 6:49am

Sorry to hear you're having trouble. As you suspected, I believe the issue you're having is because you're feeding the Open Port component (and the Uno Read) a List of COM ports... rather than specifying specifically the one port you want to talk to. My guess is that you're Arduino is actually connected to Port 3 (not 1 or 2). Since the Ports Available is returning a list (this would also be the case inside the Arduino IDE BTW)... there are a couple of options you can try. You could use a List Item and retrieve the specific COM port number you're looking for (item 2 in this case). Or you could simply type the number 3 in a text panel and connect that to the Open Port component. You could also right-click on the Port input and set the integer manually that way as well. Any of these will work. But, its important that you're only opening up a single port and not a list of ports. Make sure you also specify the same port on the Uno Read component as well. This should fix your problem (although please let me know if you encounter other issues).

HTH,

Andy

Permalink Reply by JFig on May 23, 2013 at 9:06am