Some thoughts/issues after getting my pair of Flutters

[awd]

My Flutter package came a or two ago, and I just found the time to finally dig in.

I started out with the RangeTest light example code, which seems a bit off to me. Since the lights were flashing at seizure inducing speeds and I couldn't tell if they were actually synching up, I turned the delay between color changes from 40 milliseconds up to 400. They were changing color in time, but the colors were off, i.e. Transmitter would go red->green->blue->..., meanwhile receiver would go green->blue->red->... It looks like the issue was that in line 85 the transmitter's color was being shifted back by one tick. Removing the " -1" made the LEDs synch up. Was this intentional? If not I can send a PR on github

I noticed that there's a lot of places where debug stuff is being sent out over the serial port, but when I try to open the serial monitor it says it can't find any connected Arduinos. Is the serial monitor in the app supposed to work? I'm on OSX, if that makes a difference.

Also, I know the documentation is still a work in progress, but I was wondering if there was anywhere that describes the structure of a bare-bones sketch for flutter. I noticed all the sample sketches have the same set of functions in them (tickInterrupt(), radioInterrupt(), softInt(), systemReset(), and interrupts for the two buttons). Do I need to define these in my own code if I want it to work?

Thanks

[taylor]

Hello!

Thanks for your comment. A few notes:

Interesting about the Range Test example. It wasn't intended to be synchronized so I'm not surprised there's an off by one error. I intend to provide a more canonical example soon.

The serial port as configured uses hardware pins D2 and D3, and can be read with an FTDI USB adapter. The USB Serial port is a big known issue and we are working on resolving it as quickly as possible. I am getting multiple reports a week of progress from a dev working on it, so I think it won't be long now. Big feature to have missing I know, but I didn't want to hold up hardware shipments on it.

Also, there shouldn't be any places in the library that print debug code unless you enable debugging in Flutter.h by uncommenting out the line that defines the DEBUG symbol. Are you seeing output printed from the library without the DEBUG symbol defined? I hope I didn't commit ther code with debugging enabled.

A bare bones sketch example is a very good idea, thank you. I have started one now and will post it when complete. I apologize for being MIA, I've had a lot of meetings since MakerCon but I expect that to calm down soon.

As far as your own code, yes those functions need to be defined. I'd like to move them to the library but I haven't sorted that out yet. I am told however that one of our backers is working on it. I should put that into the Issues page on github I suppose...

Please let me know if you have any other questions/issues.