Compile error

[xevrebyc]

'Timer' does not name a type
src/beam.h:79:5

Here is line 79 under private:
Timer* _syncTimer;

[ScruffR]

What system version are you targeting on your Particle board?
Software Timers are only supported from 0.4.7 onwards.
Also Particle.h (or its predecesor application.h) need to be included.

Can you try this repo (till the respective PR may get merged)
https://github.com/ScruffR/beam_particle

[xevrebyc]

I really appreciate the quick reply. I am using a Particle Photon with 0.6.2. By timer I mean I am just running a loop that counts 0-60 with a delay(1000) on each iteration. With a single Beam it take a 173 seconds to complete. It I add a send Beam it take ~250 seconds to run the same loop. Here is what I am running. I have all the includes from the example. I just removed everything and added my small loop. void loop { b.print(string(i)); b.display(); i++; if(i>60){i=0;} } My end application will be a radar speed device which will display the speed on the Beam. At the current display speed the go-cart will have already passed before the speed is displayed. Even on the examples provided on github the delay between scrolling text and displaying the frames is quite long. Sent from the iPhone of: Jay Wright Erroneous words are a feature, not a typo.

…

On Jun 27, 2017, at 8:47 AM, ScruffR ***@***.***> wrote: What system version are you targeting on your Particle board. Software Timers are only supported from 0.4.7 onwards. Also Particle.h (or its predecesor application.h) need to be included. Can you try this repo — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or mute the thread.

[ScruffR]

I see, but the error message does relate to the lack of definition for Timer without the needed include statement.
This is an easy fix tho' (as said).

Your timing issue on the other hand is beyond my scope, since I'm answering here as a Particle forum mod but I haven't got enough insight into the inner workings of the HoverLabs Beams hardware to understand whether the extensive delays featured in the library are required or what they are for.

I'd leave that to HoverLabs to answer, but I also noticed this lack of responsiveness of the Beams for something I'd (admittedly w/o clue) consider a trivial task given the possible I2C speed of 400kHz allowing several KB/s to be transferred.