Where is documentation on building applications for Cyberbrick?

MakerWorld CyberBrick
1

I have looked through this page several times, and I can’t find how to actually build and flash an application:
https://makerworld.com/en/cyberbrick/api-doc/cyberbrick_core/start/index.html

There’s how to install the tools, how to use REPL, and a bunch of material on libraries. But nothing about building in VS Code or flashing an application (can you debug from VS Code or have to flash from Cyberbrick application?). Am I missing something obvious?

1 Like
2

This may not be what you’re looking for, but my understanding is that you can only paste your code snippets into the field in CyberBrick PC app the so that it will be included when applying your configuration.

1 Like
3

(post deleted by author)

4

I don’t think that is correct. Application code would be called by rc_main.py, which is called by boot.py. Messing with boot.py would be risky unless you KNOW what you’re doing.

5

Based on what are you saying it? Can You link us new to this to any kind of documentation? I understand, that it’s still early days and we’re just out of kickstarter, but having a basic “make LED blink” step-by-step tutorial would be one of the first things to focus on, don’t you think?

6

I think their primary focus is getting people making simple things using the GUI editor for PC/Mac. From there you can achieve “LED blink” by playing around with the (imo) fairly intuitive interface. It’s drag-and-drop for the transmitter and receive with limited but fairly obvious options.

7

For many actions, using the GUI will be the most straightforward approach. If you’d like to add some custom code snippets, you can do so following this process:

  1. In the CyberBrick desktop app, after pairing your devices, select “Code” under your receiver.
  2. Click “Add” to add a new code snipped.
  3. Write and save your code. If you use an external editor, there’s an issue on some platforms with pasting code into this field. If that happens, you may be able to drag the text and drop it into this field.
  4. Under the Receiver, select the component that will be used to trigger your code snippet.
  5. Click “Add”’ to add an event.
  6. Change the Module to “Code” and the change the value to your code snippet.

After doing this, you can save and send your config to test on the device or click the “Test” button next to the event.

AddCodeSnippet

This example just makes the onboard LED blink.

1 Like
8

I think he’s asking how to upload a complete program, not use the RC skeleton to run actions based on button presses.

9

From what I can see in the available documentation, this doesn’t appear to be officially supported.

10

Given the kinds of failures that have been reported (motors turning without ‘cause’, peripherals not responding to changes in controls, failed attempts to connect, etc) it seems to me that some simple guidance on how to:

  1. enable the logging that’s already included in the code,
  2. how and where to retrieve the resulting logs,
  3. a means to print both the raw and parsed data values received.

This little bit of info would go a long way toward debugging these failures. These SHOULD be within the capabilities of the code, but sorely lacking in any ‘how to’ do it. Where are the developers? Where are the support people?

And to pre-answer those who say it’s still early in their development cycle, I firmly disagree. This is a product that claims to be usable by anyone with a 3D printer. That COULD be true IFF there was some modicum of support.

11

Here are the documents on MicroPython, but please do not use third-party tools for firmware upgrade operations, as this will cause device security verification to fail and cannot be recovered :https://makerhub-dev.bambulab.net/en/cyberbrick/api-doc/

1 Like
12

This is what I get with that link:
Blocked

If I can use Thonny to edit the python code and monitor the serial port, then this SHOULD enable simple debugging.

13

trent, the link does not work

14

Try This
Overview — MicroPython for CyberBrick V01.00.00.02 documentation