I am using the latest e-book version "Update: 11. Nov. 2022 Ver. 1.13"

Some examples:

1) In 2.2.5, step 4 states "In the Condition field, place the block in the operators category to create the expression when the button is not pressed". Where is the "Condition field"? I am guessing it should say to drag the "Not" block from the Operators category?

2) In 2.3.1 - it says "..we will turn off the RGB LED of Picobricks, if not, we will turn off the LED". I believe it should say "if not, we will turn ON the LED".

3) In project 2.2.5, why aren't "When Started" and "Forever" blocks required? Using only two "When" blocks seems to keep the code running forever. Confusing... In a later example it did mention that "When" blocks run all the time. It would be helpful to mention this earlier to avoid confusion...

Suggestions:

1) Using Micro Blocks program on my iMac, I do not see any way to quickly clear the work area of all code blocks. One can right-click on individual code block objects and choose Delete. BUT how do we quickly delete all code to start with a blank workspace? I'm guessing Micro Blocks is provided by a third party?

2) It would be really helpful if references to code block names were italicized (or bold). e.g. "When Started" could simply show as When Started...

LOVE the product so far!! Nice work!

-Mike

I've reviewed the sketch and I think I have it correct. The screen does show "The game begins" but nothing happens.

V170 firmware and v1.1.89 MicroBlocks.

I published my models for those trays at: https://www.printables.com/model/310823-pico-bricks

Enjoy!

If you run the program using Arduino/C++ the time display has display errors in both the minutes and seconds when either one goes from 2 digits to 1. The starting time is inaccurate because it uses millis which is the amount of time since the program started running, so will be off b amount of time it took ou to set the time and push the button. It also has a time resetting problem and will not correctly see the end of time so starts showing a negative time.

It might be nice to have a separate section for documentation corrections and maybe a procedure for submitting pull requests. Now it is not clear how to best report documentation problems. The formatting of the Arduino code leaves a lot to be desired. I would prefer a change to a monospaced font to differentiate it more from the main text.

BTW I received my picobricks yesterday in western US. It was a relief to have the package released from UPS hold. I am enjoying the setup. It is nice and clean that the main board works out of the box without having to setup any cabling. This is by far the easiest way I have been introduced to a microcontroller. After having used MicroPython and JavaScript for a couple of projects, I had completely forgotten what a pain Arduino C++. (It is really C++ and not C, because the libraries are imported as objects and use the dot notation.)

My normal sensor range is 4 or 5 to about 90. stays fairly consistent (wtihin5%) and so set code to 70 rather than 90 to ensure it wasnt the sensor moving to cause the flicker.

I have changed the wiring so it is not the external cables. (I separated the components already).

stopped and started the microblocks program.

any more ideas?

I keep getting some errors, for instance:

--------------

 File "<stdin>", line 15, in <module>

TypeError: unexpected keyword argument 'pin_num'

When running alarm_clock

---------------

Traceback (most recent call last):

 File "<stdin>", line 25, in <module>

AttributeError: 'WS2812' object has no attribute 'pixels_fill'

when running autonomous_lightnint_01

etc... etc...

There are some real first impression issues with the setup:

1. The shipping. My box was DEMOLISHED to the point of holes with bags of equipment sticking out.
2. NO PACKING SLIP? I had to dig through kickstarter and hope I got everything I paid for.
3. Temp and Humidity don't work on the SHIPPING DEMO. I see it's an issue with microblocks from the forums, but how do you ship an example that doesn't work? Did no one even power it on to check on at least a single board? what about the person who wrote the example? Testing is the difference between a good first impression and a box going to the garbage with kids.
4. The eBook doesn't work on mobile. It never loads. It looks like a paid service, but a request for a fix would need to come from Robotistan.

I am a newbie on the SOC / IOT🙂

Than you very much for the hard work!

Thank you for all your hard work and congratulations Robotistan.