Jump to content

AVCampos

LEGO Ambassadors
  • Posts

    1,479
  • Joined

  • Last visited

Everything posted by AVCampos

  1. You shouldn't need to previously pair the SBricks. However, at least for the initial search in BC2 I need to turn location on (it's a thing with Android, go figure). In other news, the newest Android version has been approved at the Play Store!
  2. I would like that to happen, but I'm not keeping my hopes up: I'm still burned with the 42039, the 42069 and the 8527.
  3. Do you mean the "Devices" test screen? I tested PF IR, SBrick, train, and Technic, and the sliders always work to change the motors' speeds.
  4. That depends on the phone brand and Android version, but some of them let you choose to have the virtual keyboard pop up even when you have a physical input controller (in this case a gamepad) connected. If an icon appears on the status bar whenever you have the gamepad connected, maybe you can activate the relevant setting from there.
  5. For a given gamepad to work with BC2, it needs to be recognised as such by the generic gamepad test apps. Since your gamepad appears to control volume, it appears to be in a different mode than "game". Check its user manual to know how to change modes: usually it's a switch on the device, or pressing "home" or "start" together with one of the other buttons.
  6. The WeDo 2.0 hub doesn't recognise the PUp app. For that it would need a firmware update, but, unlike the other PUp hubs (Boost, trains, Control+, and possibly SPIKE), its firmware can't be changed.
  7. I'd bet the Control+ app implements a PID controller to move the motor to the desired angle as quickly as possible without overshoot and jitter.
  8. Agreed. Another such possibility would be animals. Grohl's single-set MOCs show that Technic animals are feasible.
  9. Would a mobile crane with the size and weight to be in scale with Unimog tyres work well with the limitations of plastic LEGO elements? We know, for example, that the 42055 and the 42082 are at the limit of what can be done.
  10. I can't identify that part; can you take a photo of it detached from the hub?
  11. Most likely that means the colour. The sellers didn't specify what the motors' colours are. So far, the Control+ hub (I'm assuming that's the one you're referring to, since you wrote it has four ports) can only be controlled by the Control+ app, which, like @Lok24 wrote, only works with the motor configuration of the 42099. However, if you have a phone-compatible gamepad (that connects via USB or Bluetooth), you can use BrickController 2 with any hubs and motors connected in any way you want:
  12. When I reviewed the set, the conclusion I reached was that it's a good set for MOCers (apart from the lack of "proper" tread sprockets) but a bad set for players.
  13. I never had problems with that, I just use one of the battery covers as a crowbar. The PUp hub (the one in the trains and the Batmobile), on the other hand...
  14. Not yet. Both are studded. The difference is that the Simple doesn't have an encoder. There are a lot of differences, in built-in motors, integrated gyro/accelerometer, type of batteries, and number of outputs.
  15. If you want compatibility with the PF M motor, the PUp simple M motor (from WeDo 2.0 and the Batmobile) has the same dimensions and almost the same attachment points.
  16. Wow, that's a big oversight! Even worse is that, unlike the PF servo, it's not enough to connect it directly to a power source to make it recentre itself before building it into the model. I think I'll recentre my motors via app (when that becomes possible) and then, with a sharpie, mark the zero positions on their outputs.
  17. I've just checked, and can confirm that you can set it to up to 360º. @imurvai Would it be possible, for outputs set to servo mode, to automatically turn them to 0º when a profile initialises? Of course, this would only be possible for motors with absolute position encoding, like the PF servo and the SPIKE motors. I don't know yet if PUp motors have only relative position encoding like the NXT/EV3 motors.
  18. That has also been my feeling. Not that I'm complaining, the 42095 has a great price for what it brings.
  19. It takes up more space than a direct connection, but you can use linkages to reduce the motor's +-90º to the valve's +-45º, like was done in the 42030. It also has the advantage of increasing torque.
  20. I tried BrickController 2 yesterday with the Control+ hub and its motors, and found that if you set the channel type to "ServoMotor" it has a similar behaviour to that of the Control+ app, with the advantage of being able to set the maximum angle.
  21. Sariel X-rayed them for his review, so there isn't much need for that.
  22. And, in the meanwhile, BrickController 2 and BuWizz appear to already work with the Control+ hub, so there's no excuse for AFOLs to MOC to their hearts' content.
  23. When (not if) I get one, I'll build it with the transmission gears swapped right off the bat, so that the motors get geared down instead of up. Off-road capability is more important to me than speed. That could invert some of the results in the video.
×
×
  • Create New...