Jump to content

imurvai

Eurobricks Citizen
  • Posts

    422
  • Joined

  • Last visited

Everything posted by imurvai

  1. Hi, With SBrick and BuWizz fast changes are possible because all the outputs can be controller by issuing a single command on the characteristic. Fortunately it is also possible on the PowerUp HUB and and on the Boost HUBs internal motors only. It works quite well in my BrickController2 app. The source can be found here
  2. Hi, Posting too many commands to a characterestic could flood the server resulting unexpected behavior (depending on the server device), so I think it is safer to "write" the characteristic and wait for the response meaning that the server is ready to receive a new command.
  3. For those who are interested in programming the BuWizz 1-2 devices I created the BuWizz protocol description Be aware that it's not official! (but working)
  4. Hi, Just found a topic mentioning lags between android and gamepads: https://forums.androidcentral.com/samsung-galaxy-tab4-10-1/528898-ps4-ds4-dual-shock-4-controller-delayed-bluetooth-input-lag-latency-android-samsung-galaxy-there-anyway-i-can-fix.html In this topic a guy suggests installing the Bluetooth Auto Connect app which might solve the lag issue. This kind of problem is most probably phone and/or gamepad dependent. Could you try and let me know if it helps? Ahh yes, it's a good idea. I was also thinking about adding it :)
  5. Hi @Philo, Thanks for your feedbacks. - For connecting to 2xSBricks: on certain devices it could be problematic connecting to multiple devices at the same time, I'll try to figure out a more stable method... - Powered-Up issue: to be honest my best guess is that your device has a different firmware version. I'll look into if any update has happened... - Boost issue: no idea for the connection issue at the moment. Do you experience lag on the internal or the external outputs or both? My experience is that utilizing the internal outputs only is faster than using both the internal and external motors at the same time due to the current protocol restrictions. I hope it'll be changed in the future. - No WeDo support at the moment. I'll try to get a WeDo 2 device and then I can add support for it. BTW thanks for the Power function documentation, I used the one you shared on your page :)
  6. Hi, I'm affraid it's not possible. You can connect any iOS compatible controllers (MFi), but unfortunately the XBox gamepad is not MFi :( I'm using one like this: Mad Catz
  7. Thanks, actually with developing BC2 I connected two of my hobbies (programming and lego). The source is open and placed on github so anyone can see or fork it :) At the moment I'm building only for 64bit ios devices, that is why it's not working on iphone5. In the next release I'll try to turn on the 32bit building as well.
  8. BC2 has been released in both Android Play Store and Apple AppStore (not beta anymore): BrickController 2 on the Google Play Store: BrickController2 androidBrickController 2 is also available on the Apple App Store. BrickController2 iOS Happy playing!
  9. Cool that it's working, however now others reported output swapping, so it really seems that there are two subversions of BuWizz 2. I'm on fixing it...
  10. Hi, thanks for your feedback. I'll try to get a BuWizz 2 to sort out this kind of issues once and for all... BTW after a system upgrade my phone also started not connecting smoothly to my BuWizz 1, however my old phone still works ok.
  11. Hi, BrickController 2 version 1.0 has been released for both Android and iOS. New features: - Added support for Lego Boost - Hungarian and German localization (besides the original English) - Improved Lego Powered-Up handling Known issues: - Swapped output on some BuWizz 2 devices - Notable lag on some BuWizz 2 devices - One user reported connection issue with BuWizz 2 Links: - Android: Google Play Store - iOS: Apple TestFlight Happy playing! and please let me know if you face any other issues.
  12. @PF Remote your app is very cool :) I was thinking of creating such an app but in this case I don't need to :) Anyway I also did some research on using the jack-to-IR thing but I have given it up. First I created my own blaster using simply two IR diodes and basically it was working ok (even with Lego) but the operating distance was very low (max 10-20cm), then I ordered another one having an amplifier (from here) but I didn't manage to make it work with Lego. Most probably the amplifier added too much distortion or it could not handle the 38kHz signal. I'm looking forward to your experiences with jack-to-IR. Maybe you'll have better luck :) Merry XMAS to everyone!
  13. @Mr Hobbles thanks for sharing your project. With that I managed to utilize the two motors of the Batmobile with one single command.
  14. Hi, I checked the released documentation but I found it kind of preliminary. Eg. the virtual port setup is not working (it is mentioned in the doc though) and also I'm using subcommand 0x60 to operate the motors, but it's not even mentioned. This subcommand was reverse engineered by someone else. So it seems that the doc is still in progress and and also the PUP hub (and most probably the Boost hub) will need firmware update to take advantage of what is written. BTW I have a working application that utilizes the PUP hub (Boost support is coming): https://github.com/imurvai/brickcontroller2 If I have some free time I'll try to sniff the BT communication and see what the official app is doing...
  15. Hi, the led as 3rd output is a good idea. I'll think about how I can do it. For the feedbacks: it doesn't really matter for me, it's ok either here in the topic or you can PM me and the Play Store is also OK.
  16. Yes, this is what I'm doing but it's not fully sufficient eg. for the batmobile.
  17. Hi @treczoks! Thanks for the doc you made. I've already created an Android and iOS app that can utilize the PUP hub but it has a little limitation: I can't operate the two outputs with a single characteristic write. Do you know if there is a way to send commands on both the outputs with one single command?
  18. Hi, According to this guide it should work with Android devices with a little trick, but personally I don't have any experience with this controller.
  19. Thanks! Did you experience the output swapping between channel 1-2 and 3-4? Cool crawler what you created! And great video!
  20. Version 0.9 has been published: - BrickController2 0.9 on Google Play Store - BrickController2 0.9 on Apple App Store Happy playing!
  21. In the meantime I found a tiny little difference how SBrickController and BrickController identify the SBrick, so I'll try to fix the SBrick connection issue in the next release...
  22. No it is for SBrick as well. Others have also reported that their SBricks can't be found during scanning. I'm looking into the issue...
×
×
  • Create New...