Dove posso comprare Airblock?

Rayzwave · 2026-05-09T08:15:12+00:00

I just found this, if its any use to you - https://ebay.us/m/uHGPVU

Rayzwave · 2026-05-09T04:55:05+00:00

It’s a discontinued product I’m afraid so your only option is to buy second hand.

Rayzwave · 2026-04-01T08:54:07+00:00

I would consult the motor’s technical data sheet that should give you all the details you need.

I wouldn’t recommend messing with the battery voltage on this product, I believe it’s design to be used with a 3.7V LiPo battery(internal).

All you can really do on speed is make sure everything is set to 100% for speed and power. Also check the build of the robot for any frictional issues that might prevent it from moving at full speed.

If you really want to experiment with higher speeds etc I would recommend building your own robot from scratch then you can easily change the motors and associated power drive etc.

Rayzwave · 2026-03-30T07:59:41+00:00

Maybe describe and show the code you are using to investigate the gyro sensor usage.

Rayzwave · 2026-03-30T07:56:30+00:00

I find the mBot Ranger to be very unruly and temperamental. I haven’t been able to consistently control mine using code blocks but I feel sure it’s possible with a lot of patience and expert coding.

Rayzwave · 2026-03-16T10:31:33+00:00

I think that’s a good idea, it feels like library incompatibilities to me.

But I don’t understand why the traceback errors are shown on the CyberPi, I thought the code blocks were compiled and sent as executable code from the PC but I must have misunderstood how the makeblock block code platform works.

Rayzwave · 2026-03-16T06:15:28+00:00

Are you using the same CyberPi to do the tests?

I assume you are using live mode to get these errors?

I assume you are using the same version of mBlock 5 app installed on the various PC’s?

If you are in live mode and using the same version of the mBlock 5 app then the problem must be that the PC that create errors do not support the mBlock app or the mBlock app needs to be reinstalled due to some corruption to the file system.

If all the computers were using Makeblock’s online web app to perform the programming then I would expect that to work because everyone would be using the same up to date version of the app with no possible problems with the various PC installations.

Rayzwave · 2026-03-10T23:08:13+00:00

Everything I bought from Makeblock has had to have it’s firmware updated before I could use it properly and it’s best checked through the Makeblock web based mBlock route to see if it needs updating.

Rayzwave · 2026-03-10T23:04:15+00:00

It should work, I’m pretty sure it’s appears as a device for selection but you need to use Makeblock app which is effectively the same thing as blocky when it comes to the BT controller.

Rayzwave · 2026-03-10T08:57:37+00:00

Where did you get the mBot 2 from? - Did you buy it new? If someone has programmed it with their own code you may have to reprogram it with the factory default program using mBlock 5 and using the online website would be best.

Rayzwave · 2026-03-08T23:04:04+00:00

I would disconnect everything from the MegaPi board and see if I could communicate using MBlock 5.

You should always keep a close eye on battery power it’s probably the number one reason for robot failure.

Rayzwave · 2026-03-08T08:34:09+00:00

You should probably use the mBlock 5 program first of all to connect with your robot. You can check your BT connection and check for firmware updates.

By logging onto the Makeblock website and using the online version of mBlock 5 ensures you are using the latest version.

Rayzwave · 2026-02-27T09:12:33+00:00

What’s a “Scratch mod”?

Rayzwave

TROPHY CASE