Jump to content

imurvai

Eurobricks Citizen
  • Posts

    422
  • Joined

  • Last visited

Everything posted by imurvai

  1. If the phone recognizes it as an infrared device then in theory it could work, but I haven't tried such an adapter.
  2. Exactly, it has been added to avoid the overshot. Using full speed even for small turnings made the servo behave kind of hectic.
  3. Yeah, it could be something like that. The current implementation uses the last joy position to calculate the speed the servo should turn with. Most probably the joy reports the 0 target position twice (or more) therefore the app calculates the minimum speed for the servo (which is 5 currently). I also tried using the current position reported by the motor to calculate the turning speed but the notification from the motor wasn't fast enough. Anyway I'll try to tweak the algorithm. The worst case scenario would be turning the adaptive servo speed completely off and always use some reasonable fixed speed.
  4. Hmm, it's a wierd behavior indeed. I'll try to reproduce and fix it...
  5. So neither BrickController2 nor the official SBrick app can see your SBrick? Is that correct? Just made a short video on the new automatic and manual calibration feature and how to use it:
  6. Hmm, ok I try to add it to the app... BC2 version 1.8 is now available for Android too. Changes are the same as for the iOS version:- Automatic and manual calibration for PoweredUp servo motors.- Fixed output issues for Powered up hubs.- Fixed connection issues. Feedbacks are still welcome! Happy playing! :)
  7. Hi, BC2 version 1.8 is now available for iOS in the AppStore - surprisingly the review process was faster now compared to the Android Play Store. Changes: - Automatic and manual calibration for PoweredUp servo motors. - Fixed output issues for Powered up hubs. - Fixed connection issues. The Android version is still under review, I'll let you know when it has been approved.
  8. It's already being reviewed in the stores so I expect it to be live in 1-2 days at most.
  9. BrickController2 version 1.7 has an unfortunate limitation that the motors connected to port A and B should be identical. It'll be fixed in version 1.8.
  10. Hi @Philo, I managed to obtain the absolute positions from the new L and XL motors, so that I can calibrate the servos. This is the setup sequence for a given port to get notications on the absolute and relative positions: 05, 00, 42, portId, 02 -> lock the port for setup 0a, 00, 41, portId, 03, 02, 00, 00, 00, 01 -> requesting notification for abs position 0a, 00, 41, portId, 02, 02, 00, 00, 00, 01 -> requesting notification for rel position 08, 00, 42, portId, 01, 00, 30, 20 -> setting mode and data set 05, 00, 42, portId, 03 -> unlock the port and enable notifications After this sequence the hub starts sending notifications about the abs and rel position. It can be done for as many ports as needed. I tested it with one L and two XL motors at the same time and works OK. The notification format: messageLength, 00, 46, portId, 03, absPos0, absPos1, relPos0, relPos1, relPos2, relPos3 Positions are in two's complement in little endian format, abs is 16bits, rel is 32bits.
  11. Actually this is how the official C+ app calibrates the servo. What I don't like about it is that the servo stresses the plastic when it measures the operating range. Yesterday I tried to regulate the turning angle using a simple black pin and the servo bent it a bit and I could even hear a cracking sound. And also if you build a moc using a push rod steering mechanism instead of using the steering rack it could be possible that the mid point of the measured range is not the straigh direction. So I'd like to add some adjustment setting.
  12. Yesterday I played a little bit with the technic hub and its motors and found the followings: - If only one XL motor is connected it doesn't move (most probably the virtual port is not working in this case), the connected L motor is still functioning - Connecting one XL and one L motor to the PUP hub (batmobile, train) the motors don't move, most probably another virtual port issue (motors should be identical???) - Servo motor works better if the stop state is HOLD instead of BRAKE (current implementation in BC2) - There are still open question regarding the calibration process but it gets clearer. At least I managed to figure out what the control+ app does. I'd like to come up with a more general solution... - I need to improve the virtual port setup 'cause I've been reported not functioning PUP and train hubs.
  13. Just got my technic hub and managed to reproduce this issue. Trying to fix it...
  14. That's wierd. The technic hub should work with any combination of motors. WeDo is not supported in BC2 but Boost and Train should work. I know it's not an explanation to your problem, I'm just saying what is working for me and for most of the users. Does Boost and the Train hub connects in the device section? Or it connects but the sliders don't move the motors? And can the SBrick, Move hub and technic hub be controlled using the gamepad or they only work in the device screen?
  15. Hi, hmm, no idea why it happens. I'll check if there was a firmware update for buwizz and lego... Is it buwizz 1 or 2 BTW? Thanks for the explanation. One idea is to add an extra option to set the servo speed. Maybe the overshot will be eliminated by using lower speed. I was also thinking about the PID option but reading the current position and setting the speed accordingly could add a significant delay for the servo operation which I would like to avoid.
  16. Hi, In my phone there is an option for this: Language & Input -> Physical keyboard -> Show virtual keyboard. By turning it on the virtual keyboard is always shown even if there is a physical one (like a gamepad) is connected.
  17. Just found a cool video by @functionalTechnic about utilizing a pneumatic valve by a new L motor using BC2:
  18. First, I'm surprised that DS4 now works on iOS. I'm gonna test it :) Second, thanks for your detailed analysis and you're right BC2 moves the motors in servo mode in full speed regardless of the angle interval. I'll try to find a better way, maybe simply reducing the speed to 50-60% would solve the overshot issue.
  19. What motor did you try with? I'm experiencing the same using the Boost external motor in servo mode and it's kind of normal unfortunately. Apparently this motor can't handle the fast changes BC2 sends to it. I was reported that the new L motor works OK in servo mode. I haven't had the chance to test it myself though as I don't have the new 42099 set yet.
  20. Got it. Thanks for the explanation.
  21. What is the point behind sending a disconnect command? If you just disconnect from the HUB it will turn itself off after a couple of seconds.
  22. Version 1.7 is now available in the Apple App Store: - Technic HUB support (Control+) - Train control - Trigger fix
  23. There is no limitation in the code. Have you tried to discover the other SBricks separately?
×
×
  • Create New...