imurvai

Eurobricks Citizen
  • Content Count

    416
  • Joined

  • Last visited

Everything posted by imurvai

  1. BrickController2 is an Android and iOS application that allows you to control your Lego models using a compatible gamepad. It supports the following devices: - SBrick - BuWizz 1-2 - BuWizz 3 (basic support) - Lego Powered-Up devices: Boost, PUP HUB and Technic HUB (or Control+) - PF infrared (on Android devices having infrared emitter). Features: - Multiple profiles for a single creation - Multiple motor (or output) assignment to a single controller event - Different types of devices can be used at the same time - The same motor (or output) can be assigned to multiple controller events - Different joystick characteristic settings - Different button modes: normal button, simple toggle, ping-pong toggle, carousel toggle, ... - Train mode on joysticks - Normal and servo mode for the new Control+ motors - Sequences (like for flashing light) BrickController 2 on the Google Play Store: BrickController2 android BrickController 2 is also available on the Apple App Store. BrickController2 iOS Video tutorial created by @kbalage (many thanks for this): And another great video by @kbalage: Older versions: BrickController Android application. It lets you to control Lego creations via Lego infra-red, SBrick and BuWizz V1 and V2 using any Android compatible game controller: Current version: BrickController 0.6 User guide: BrickController User Guide Minimum system requirement: Android 4.4 and bluetooth low energy support on the phone (or tablet) Video on the older SBrickController application:
  2. I tried that but didn't help. Do I need to leave it disconnected for some time?
  3. Hi, yes, unfortunately the servo calibration is only working on Android yet - my ios dev environment went down and I haven't had time to fix it :(. Also my Buwizz 3 has stopped working (I left it in my drawer for a couple of months and now I can't charge it up), so not sure when I can fix it.
  4. Hi, the stepper hasn't been implemented properly for BW3. I need some more time to figure out how it's working. Sorry for the inconvenience.
  5. Yes, it's a known issue. For some BW2s the ports are swapped. If I have time I'll add a config setting for it.
  6. Hi, actually something similar is implemented in BC2, maybe not that accurate than your implementation. I see. It is up to the PID parameters set for the servo. Currently it is hardcoded and I tried to find a general setting. I'm planning to make it adjustable through the UI.
  7. Thanks for the videos. Yes, the PU hub servo is a harder issue as the PID should have been done in the app itself, but for the BW3 it is handled by the device so it's more accurate and faster. Ah, I saw your message on github but completly forgot about that. Sorry for that. I'll look into how I can add those buttons.
  8. TBH I've never tried the speed servo mode, but you made me curious :) So I'll investigate it.
  9. TBH no idea. I have no control over the current used by the motors (at least I'm not aware of any command that can control it). Normal mode uses the PWM control. Thanks for the testing ;)
  10. I'm not sure how BW3 works internally (PWM I think?). And what do you mean by the power comes in waves? Can you make a video on it?
  11. Thanks for the feedback. I try to set better PID values, or alternatively I'll consider adding a setting page for customizing the PID parameters.
  12. Hi, Please be informed that BrickController2 version 3.3 has been released for Android containing the servo support for BuWizz 3. The iOS version will come later as my dev environment went down and need to be fixed. Please let me know if you find any issues. Happy playing! :)
  13. Yes, there will be option for manual calibration as well. The same way as for the Technic hub. It's almost done, there is only one edge case I need to resolve.
  14. Hi, PFx Brick is not supported unfortunately as I don't have that device.
  15. I think it's possible by setting up a toggle button with the servo, but I have to check it...
  16. Currently I'm working on the proper servo handling for BW3 including the auto-calibration too. I'll let you know when it's done.
  17. Hi, Just got a BW3 for testing/fixing issues. I'll look into that... In the Android's developer options the bluetooth trafic logging can be turned on. But it logs every BT communication so it's better to turn every BT device off but your phone and the Lego receiver you want to log. Then do some activity with the receiver and copy the logfile to PC (I can't remember its exact location and can vary phone by phone). On the PC I'm using Wireshark to analyze the BT log. Unfortunately I don't have any MK device so I can't do the reverse engineering for that.
  18. Hi, yes both BW3 and PU hub supports normal and servo modes, stepper works somehow but not perfect. Sorry, what is the question exactly? BC2 has both auto and manual calibration for servo mode if you asked for that.
  19. Hi, actually the problem with working in background is relating to the controller input, not the bluetooth. The controller events are dispatched only to the application in focus unfortunately. This is why I implemented the dark mode, to save some battery on amoled devices, but a fake display off is also a good idea. I'll try to implement it.
  20. As I can see version 3.2 is already out in the PlayStore. Please let me know if the fix is working.
  21. Yes, I removed this permission request from v3.1 and it worked on my old phone that way (don't really understand why as Android used to require that permission before). I just added back the location permission request but bluetooth scan still doesn't work on Android 12. So I keep investigating it...
  22. Hi, Just got my new phone running Android 12 and I'm facing the same issue. I'm on it and push the fix as soon as possible.
  23. Yes, the zero point can be set to any position, but found that it is safer to restrict the automatic calibration to set the zero position 90 degrees aligned. Simply it was the most stable solution. If your model requires the zero point to be set elsewhere, then you can use the manual calibration.
  24. Hi, I need to check how I implemented it (it was quite some months ago :) ), but as far as I remember the auto calibration tries to find the nearest 90 degree position to the center. Most probably in your model it's not the exact center position. The reason is that the endpoints can't be measured precisely, therefore the exact center can't be calculated. What you can do is to manually calibrate your servo. Also: Good news, version 3.1 has been released for Android too (for iOS it has been out for a couple of weeks). It contains the BuWizz 3 servo support which has been added by Vit Nemecky. Many thanks for that.