Replies: 3 comments 2 replies
-
|
There exists no function called |
Beta Was this translation helpful? Give feedback.
-
MicroPython imports don't work quite the same as regular Python. The only thing you could do right now is: from pybricks.experimental import hello_worldThere isn't anything else in the experimental module currently. To be able to use exp = __import__("pybricks.experimental")
print(dir(exp)) |
Beta Was this translation helpful? Give feedback.
-
|
Hi @laurensvalk and @dlech, What is the current recommended/official method in Pybricks to create a custom BLE service that can receive data from a PC? |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hello Pybricks Team and Community,
I'm encountering a persistent issue with my LEGO MINDSTORMS Robot Inventor Hub (51515) where pybricks.experimental appears to be missing or inaccessible. My goal is to use pybricks.experimental.pb_ble_uart for BLE communication with a PC.
After flashing pybricks-primehub-v3.6.1.zip (downloaded from the official v3.6.1 GitHub release) using pybricksdev, the Hub's REPL reports itself as Pybricks MicroPython ci-release-86-v3.6.1 on 2025-03-11. When I try to import pybricks.experimental (which seems to pass without an ImportError initially) and then access any attribute like dir(pybricks.experimental) or use from pybricks.experimental import pb_ble_uart in a script, I get AttributeError: 'module' object has no attribute 'experimental'.
The "About Pybricks Code" dialog in my Pybricks Code web IDE (v2.6.0) also references "v3.6.1".
Steps Taken:
1.Tried the web flasher on code.pybricks.com (using Pybricks Code v2.6.0) multiple times with different browsers (Chrome, Edge, incognito mode). This did not resolve the issue.
2.Downloaded pybricks-primehub-v3.6.1.zip directly from the Pybricks v3.6.1 GitHub release assets page.
Used pybricksdev to flash this file. The flash process reported success (erase and download completed 100%).
pybricksdev Flash Log:
REPL Output After Local Flash:
The REPL output after a successful pybricksdev flash and connecting to the Hub via Pybricks Code is as follows:
The REPL string Pybricks MicroPython ci-release-86-v3.6.1 on 2025-03-11 is particularly concerning. While the version tag is v3.6.1, the build date of 2025-03-11 seems anomalous for a firmware that was officially released around March 2024. Could this indicate an issue with the specific build artifact for pybricks-primehub-v3.6.1.zip in that release, or that I'm somehow getting a development/mislabeled build?
1.Is pybricks-primehub-v3.6.1.zip from the v3.6.1 release the correct and latest stable firmware for the LEGO MINDSTORMS Robot Inventor Hub (51515)?
2.Should pybricks.experimental (and specifically pb_ble_uart within it) be present and accessible in this official v3.6.1 firmware for this hub?
3.Is the 2025-03-11 build date reported by the Hub's REPL expected for the official pybricks-primehub-v3.6.1.zip firmware, or does this suggest a potential issue with the build/artifact?
4.Given the successful pybricksdev flash log, why might pybricks.experimental still be inaccessible? Are there any known issues or alternative steps for the Robot Inventor Hub?
I've been very careful with the flashing process and seem to have hit a roadblock. Any insights or guidance would be greatly appreciated!
Thank you,
KeltosGG
Beta Was this translation helpful? Give feedback.
All reactions