_Ozzee_

Thank you for taking the time to test the app and write such detailed feedback. I really appreciate it. Your observations are very useful and help me understand which parts of the workflow need improvement. Regarding requiring a real hub connection before motor commands become available - you are absolutely right. It is a very good idea to allow selecting the hub type without requiring an actual connection. I honestly do not know why I did not implement it this way earlier. I will definitely rework this behavior in future releases. About the control logic: in most cases, yes, the logic is event-based, and this is the basic intended workflow. However, this does not mean the programming system is limited only to simple event handling. You can also use looping logic and custom processing blocks to implement much more advanced behavior without relying only on direct events. Regarding multiple events happening at the same time: in a real program, one event will always be processed first depending on the internal event queue and the order in which the operating system delivers the input events. About combining values from multiple inputs - yes, this is absolutely possible. I would recommend using a MyBlock as a custom function and connecting it to multiple events. MyBlocks can also receive arguments, which makes them suitable for implementing custom business logic such as combining trigger values, calculating differences, selecting maximum values, etc. For example, in your trigger scenario: right trigger = forward left trigger = backward both together = calculate the difference This can be implemented using a MyBlock that receives values from both triggers and processes them as needed. The same approach can also be used for combining joystick and trigger throttle input, limiting values, applying curves, selecting maximum values, and other custom logic. I also plan to publish prebuilt profiles for official LEGO sets, including 42114, which should provide good practical examples of how to implement these kinds of advanced control systems. Regarding the ability to set motor speed to values like 1000% or -20%: this behavior is inspired by the original Scratch language and also the LEGO Mindstorms Robot Inventor app. The passed value is interpreted internally and then clamped/cast to the valid range supported by the block. Personally, I did not see this as a problem, but I understand your point and may reconsider improving the UI validation in the future. About exiting a profile without saving changes - unfortunately this is currently not possible. All modifications to programs and dashboards are saved immediately. I understand that this may not be very convenient. Undo/redo support and change history are already on my roadmap, and I am actively working on this functionality because I agree it is an important missing feature. Regarding profile deletion not working: this issue can happen if the device is not connected to the internet. Since profiles are synchronized with the server, profile creation and deletion operations also require synchronization. If you do not want to use cloud synchronization, you can disable it in the account settings. In that case, profiles will be stored locally and deletion should work correctly. About accidental movement of blocks while panning in the profile editor - yes, I completely understand the issue, especially on phones with dense layouts. Currently there is no undo functionality available, but as mentioned earlier, proper undo/redo support and editing history are planned and already in development. Thank you again for the detailed feedback and ideas.

I’d be happy to add support for both SBrick and BuWizz 1.0. The main issue is that these devices are no longer available for purchase, and I currently don’t have access to them. While it might be possible to implement support based solely on documentation, I wouldn’t be able to properly test or verify that everything works correctly without having the hardware on hand. If I manage to get access to these devices in the future, I’ll definitely look into adding support.

In most cases, yes - the app is designed for BLE devices. The only supported hub that uses classic Bluetooth is the LEGO Mindstorms Robot Inventor. Regarding motors: the application does not verify which specific motor or sensor is connected to a port. It simply sends commands to the hub based on the blocks you use. If your motor connected via a PF/9V-to-PUp adapter is detected as a simple train motor, you can try applying all commands intended for that type of motor. So in practice - just give it a try and see how it behaves.

Yes, the community has already grown to more than a couple thousand users, which is great to see. The app was actually released some time ago - I just decided to share it on this forum as well, since it might help more people control their models. As for adding your own profiles, it mostly depends on your familiarity with Scratch-like programming. If you already have some experience, it should be quite straightforward. If not, you can always refer to the documentation for detailed explanations of what each block does. I also strongly recommend exploring the prebuilt profiles for official LEGO sets - they’re a great way to understand how everything works and what options might suit your needs.

Yes, that was one of the main goals of the application - to bring together as many different electric systems into a single, familiar interface for controlling them all. I plan to continue expanding support for additional devices in future releases.

Regarding "One question, if you want to control a car just with an Xbox controller, do you also need to create an interface, or in that case only a program logic?": In case you plan to control your model using only an Xbox controller, you can omit the dashboard controllers entirely. In MOCPilot, creating dashboard controllers is optional and mainly intended for on-screen (touch) control. However, dashboard elements can still be useful if you want to display information such as battery level, motor speed, tilt, or accelerometer data on the device screen. That said, this is not mandatory for basic gamepad-only control. Regarding "Is this a continuation of the ControlZ app?": Long story short, yes - this is an evolution of my previous application, Controlz. For Android devices, MOCPilot is distributed as a separate application. This is because the original Controlz app cannot be updated to MOCPilot due to it being published under a different developer account. On Apple devices, however, MOCPilot is delivered as a direct update and effectively replaces the old Controlz app.

Hi everyone, I want to share MOCPilot — an app for controlling LEGO®-powered creations (MOCs, official sets, robots/mechanisms) from a phone/tablet, and it’s also available on Apple devices including macOS. You can build custom control “profiles” and automate behaviors using a Scratch-like block system. Official site / Documentation Documentation home Quick start What MOCPilot does 1) Profiles (control layouts) Create a custom “profile” per model (your own MOC or a set) Add on-screen controllers (steering, sliders, buttons, etc.) and connect them to motors/ports Monitor hub status + sensor values in real time 2) Gamepad support (full controller driving) You can connect a physical gamepad to your phone/tablet/Mac and drive your model with sticks/triggers/buttons MOCPilot provides dedicated gamepad blocks you can use inside a profile program, so gamepad inputs can directly control motors or trigger custom logic (e.g. gears, lights, sequences, modes) 3) Visual programming (Scratch-like blocks) Drag-and-drop blocks to build anything from simple drive code to automation sequences Use events/logic to react to sensors and hub state Works offline for designing/testing your programs 4) Multi-hub builds A single profile can control multiple hubs at once By default you can add up to 2 hubs per profile; can be extended up to 5 hubs via extra hub slots Supported hubs LEGO® WeDo 2.0 Smart Hub (45301-1) LEGO® Technic™ Hub (880012) LEGO® Technic™ Move Hub (103479c01) LEGO® Move Hub (88006) LEGO® Hub (88009) LEGO® Remote Control (88010) LEGO® Large Hub (88016) (not available on iOS) BuWizz® 2.0 Hub BuWizz® 3.0 Pro Hub Mould King 4.0 (M0006) Mould King 6.0 (M0019) Supported motors Technic™ Large Motor (88013) Technic™ XL Motor (88014) Large Angular Motor (88017) Education Large Angular Motor (45602) Medium Linear Motor (88008) Simple Medium Linear Motor (45303) Train Motor (88011) Medium Angular Motor (88018) Medium Angular Motor (45603) Small Angular Motor (45607) Light (88005) Supported sensors Color & Distance Sensor (88007) Distance Sensor (45604) Color Sensor (45605) WeDo 2.0 Tilt Sensor (45305-1) WeDo 2.0 Motion Sensor (45304-1) Prebuilt profiles (official sets / ready-to-run) MOCPilot includes Prebuilt profiles so you can quickly control supported official sets and also learn from ready-made block programs. Important detail: you can experiment and edit a prebuilt profile, but changes aren’t saved — it resets to the original version next time you open it. Typical use cases Drive & steer Technic vehicles with a clean dashboard UI (on iPhone/iPad/Android tablet, or on a Mac) Use a gamepad for realistic driving feel, plus custom actions mapped to buttons Create realistic sequences (startup, shifting, lights) using blocks Program sensor-based behaviors (distance/color/tilt triggers) Control complex creations by splitting functions across multiple hubs (drive + gearbox + crane + lighting) Download Google Play (Android) Apple App Store (iPhone/iPad) Mac App Store (macOS)

Hello. Yes I know about this problem. I run into her from time to time. I have some ideas why this might be happening, but I can't find a way to permanently repeat this problem. Usually the problem is solved by reconnecting. Now I'm working on reworking the connection system, I think that the problem is in it. As soon as I have news, I will definitely let you know.

The update is quite large, so it's hard to say for sure. Best option at the end of this week, worst next week. I apologize for not responding about the delay. Yes, I have seen this problem mentioned before, I can't reproduce it myself, it sometimes manifests itself, which makes it difficult to solve it. I have some idea why this is happening and reworking some parts of the program should solve it. Anyway I'm following this issue.

Hello, thanks for your feedback. Glad you like the app. At the moment, the servo mode on BuWizz 3 does not work correctly. I figured out the cause and already fix it. This will be in the next update.

Android 2.8.1, iOS 1.4 update available. - fixed a bug that caused a delay between the hub and controls in the profile use mode - redesigned hub management screen in the profile editor - redesigned mechanism for linking hubs to a profile - added new theme "Audio" - small fixes in the market

Hello, you probably have android 12. All users are faced with the problem of finding hubs, because in android 12 the requirements for finding bluetooth devices have changed. The problem has already been identified and fixed. An update will be released soon to fix this issue.

With the release of version 2.7, a bug appeared for some users when loading profiles. This bug was related to the previous version of the program and was fixed in 2.7, but the data in some profiles was already corrupted and the loader from the new version worked with an error. I made changes to the profile loader so that it tries to load what is recoverable and does not crash the program. The update has already been uploaded and is currently being tested. In the next update, I plan to deprecate the current scheme for storing and loading profiles. The next update 2.8 will already use a new profile storage system, which will be much safer than the current one and such cases should not occur. I apologize for the inconvenience to those who encountered the problem.

Controlz downloads the latest firmware versions from the our server. If the versions are received, then the “update” button will appear on the hub management page on the hub, but the application will offer you to use the Lego application for firmware. Since I do not have the ability to flash the hub, and there is also no access to the firmware files. You would help me a lot if you could share your profile backups. I would identify the location that was causing the error and also be able to recover them for you. You can send files to developer@controlz.pro with your forum nickname. I'm currently working on a complete overhaul of profile storage. In future versions, migrating between versions will be absolutely safe. Once again I apologize, it is very difficult to keep track of all the changes in the code.

I am very sorry that this happened. In the previous version, there was a bug when saving profiles, which led to an error in writing data. It appeared quite rarely, but some users encountered this error. It is enough to clear the cache and data of the application for it to start working. I strongly recommend that you save profiles to your device using the share function.