I'm creating a projet and I need to use the Pico and some picobricks components outside, without USB powering then. I tested with the default battery compartment (3v) but it doesn't seem to work. However, powering with a phone powerbank via a USB cable work, but it's too big and heavy.

I'm wondering if there are any other solutions, and how to apply them.

Thx for reading,

t0qen

PS: here is a photo of my project

PS 2: I'm french, be friendly about my writing, please

I am experiencing an issue with the MQTT library on an ESP32 board. The connection to the broker (Adafruit IO) and the topic subscription (MQTT sub) both complete successfully. This is confirmed by debug messages and the ability to reliably publish data (MQTT pub). However, the when MQTT event block never triggers when a message is published to the subscribed topic. I have tested this with a minimal script that only displays the payload, but it still does not work. This suggests a bug in how incoming messages are handled, as they are not triggering the event block.

Also, for a more direct support of MicroBlocks related issues with these boards, you can check out our Discord Forum at: https://discord.com/channels/1000653853491998760/1321772362479173673

My emails to you folks have yet to get a response, so I figured I would open a discussion here.

Issues listed below:

• If the motors are engaged at >10%, then the USB communication frequently drops out. More than 25-30% motor drive causes coms to drop out immediately. In my experience, this behavior is characteristic of a severe voltage regulation, or decoupling problem on the main board. Recovery typically requires a hardware reset, and a re-connect. I added a 47uF cap to the 3.3v header on the board, sadly no change in performance. Without a schematic, I have no plans to dig any deeper.
• If the motors are set to < 20%, then the wheels do not have enough torque to spin. They make noise, but that is all. This is disappointing, but not fatal. Clearly if there were wheel velocity sensors, and some simple PID control code, this would remedy this issue, but I understand that this would be outside of the scope of this introductory robotic toy.
• Although correctly wired, the tires spin incorrectly.  For now, Right causes Forward, Left causes Backward, Forward causes pivot Right, Backward causes pivot Left.  I edited the forward, backward, left, & right methods in the TB6612 module of the berrybot.py library. I'll need to edit other TB6612 methods in way as well, but this preliminary edit solved the problem for the method that I am currently using.
• Issuing a Stop from the IDE is most often ineffective, as with most of the above actions, using the motors appears to cause USB communication failures. Even without the use of the motors, the Stop from the IDE still appears slow and problematic.  
• Using Thonny, any of the code that employs motor control is at present is a waste of time, as USB communication is so frequently corrupted. Thonny throws exceptions similar to: PROBLEM IN THONNY'S BACK-END: Exception while handling 'Run' (ConnectionError: EOF). 

If the comm drop out issue is specific only to my board, then I will need a replacement assembly.

If this is an epidemic defect of the this first run of BerryBot devices, then this problem is magnified by the quantity of devices shipped.

What can we do to resolve these issues?  Thanks in advance for a prompt reply.

I have also set the below code up as a test and getting nothing whatsoever on the screen after the intial tick on turning it on.

Any assistance appreciated...

To test your IR sensor with the remote you get with your Zero to Hero kit, you can use this script.

The broadcast block sends out the message content specified into the program context. All when received message blocks with the same message content will receive the message and act on it.

I added when received for the first 4 buttons only. But I guess you get the message how it works.

Have fun.

and when uploading the code v4 and even v5 the serial monitor stays at

DMP ready! Waiting for first interrupt...

And wont do more.

When I detach it off the board, it doesn't respond. The light does work.

Same code in each case. So it must be hardware.

Is the project dead? Can I get either the kit or the money back ?

Have fun.

I am developing a STEM class focusing on the virtual environments as deployed in Bookworm.

I was struck, I should be able to target a Pico and, in turn, your whole landscape.

I’m wondering if I had something running in the virtual environment and deployable to a Pico as a service.

·       Can I interact with your environment?

·       Can I run something like a full version of Python inside the environment or would I be limited to the reduced instruction set?

In my reading it looks possible

The basic concept is that I would add devices (i2c) running within a given environment and deployed as a service. In my environment I then stream the data to a db.

Can I function in your environment where I would basically be an enhancement of your access to i2c .

Can my objects (virtual environments) be enveloped into your Microbricks?

BTW is there a plug I can tap the I2c connectors directly? (I realize it can be accessed via the breadboard.)

Anyway, I bought one for my grandson, I’m hoping to show him some of what I am doing, so I’ll be playing with it. 

Anybody want to offer an opinion, suggest some libraries etc.

I'm all ears.

Problem was seen on both firmware version 1.18 and 1.19.

Other codes tried that does not have the picobricks module are OK.

Can you please advise on what to do with the setup? Thanks!

Project Codes

Project Videos

GitHub: https://github.com/selimgayretli/PB_wifi_gamepad

Project Details:

• Enter your Wi-Fi ID and password inside the MicroPython code.

• Log in by typing the IP address on the serial port into Google search or Safari search (Phone/Computer).

• You can control PicoBricks Robot tank or robot arm from the “PicoBricks Gamepad”.

Version 1.0, Peter Mathijssen

This project could be the basis for a school project. 

In healthcare, there are patients who have problems verbally expressing their pain. 

Sometimes being only able to use a single finger. With this project, you could develop a system where patients could alert someone when their pain goes beyond a certain level.

It uses a PicoBricks button, an OLED screen, and a buzzer.

In this sample, the blocks for the buzzer are added but not used. As a nurse, you could "talk" to your patient and decide together when help is needed and whether the buzzer should make a noise or the message should get sent. 

Think about adding a bigger button, a bigger OLED screen, a WIFI module, or a Bluetooth module so you can send an alert to a nurse. There is no casing for this project so you could also think about that.

The images used in this project were made with the help of this tutorial: 

https://wiki.microblocks.fun/snap/snap2mb_img_code

The zip-file contains the MicroBlocks ubp file.

Remark: It should be allowed on this community to upload a ubp file without having to put it in a zip-file.

When I nuked my Pico with the UF2 file from RPi for the Pico the system reset and now I do not know how to get that UF2 file back, or where to get it or if I can create it myself. It would seem that MS Maker is an option but what is the best way to go about this, would like to delve into the Start from The Start.

Or am I overthinking this whole gig? :-)

how can I fix the distance sensor on the plate? Is there only a 3d-Print file available who's link doesn't work.

Do I have to have a 3d-printer????

Thanks in advance

Wolfgang

Thanks for the awesome board and projects!

Mind+: Home - Mind+ - (mindplus.cc)

microBlock IDE: microBlock IDE

Mixly 2.0: Mixly2.0 RC3发布 - Let's Mixly!

BlocklyDuino Editor F2: 吉哥的分享 - 如何安裝吉哥自製積木 (google.com)

BIPES: Desarrollo (bipes.net.br)

Todos ellos son de uso gratuito y en algunos las bibliotecas de componentes son muy extensas.