Jump to content

Philo

Eurobricks Counts
  • Posts

    1,015
  • Joined

  • Last visited

Everything posted by Philo

  1. Can't say better... I was expecting to find many textured parts in Studio library to test but I found few of them (128).
  2. Using 4 ports Technic hubs for the switches might help a bit...
  3. 60216 - Downtown Fire Brigade (City / Fire) Download MPD (OMR compliant) Known errors: Missing stickers Done with LDCad 1.6c Rendered with Studio 2
  4. This year, a regular 28t gear was also introduced: https://brickset.com/parts/design-46372
  5. Indeed, to make it clear: No lag with BC2 in device test mode, sliders respond immediately. No lag with BC2 in controller test mode Control+, PoweredUp and ControlZ apps work perfectly. BC2 with the same controller and hubs work fine on my Asus tablet.
  6. Stupid me - thanks @Jetro. But that doesn't solve the problem, still experience variable lags (from 0 to 5 seconds or so!!!). I was so happy when it worked. What did changed to make it work? What whanged back to break it again???
  7. Mmmhhh... can't get that. If I push the green button for a long time the Pup hub just shuts down. No purple light.
  8. What do you mean with reset, just remove batteries or something more radical?
  9. Unfortunately this victory was short lived :( I tried again with Batmobile, and the huge lags are back. Kind of strange, since this morning I was able to connect several times flawlessly, including with 42099. I tried to unpair the controller, reboot my phone and make the same sequence of actions I did this morning (pair the controller, lauch BC2, connect to Batmobile) but to no avail.
  10. Did you make something to improve the lag with some devices? Anyway, 2.6 works perfectly now on my G5+!!! Tested on Batmobile/PoweredUp and 42099 / Control+ For sure
  11. FYI the needed range for Liebherr long actuators is about 26000°
  12. @Didumos69 You intend to make bulding instructions, don't you?
  13. Makes sense... thanks! Yes, but if you build your own controller you can used a much more capable motor driver... then physical limits of the connector are important to know ;)
  14. I love your self-translating videos ;) ...your mechanisms too!
  15. @Bartosz There is a spreadsheet summarizing Michael Harris findings available in Facebook Powered Up group: https://www.facebook.com/groups/PoweredUp/permalink/2234377586863700/
  16. Do you have an example where Studio UV mapping is significantly different from cylindrical (or even front/back planar) projections? I couldn't find one (and I think that Part Designer uses plain planar anyway) Why take a hammer to crush a fly? Anyway patterns are mostly acquired by photo/scan so are (essentially) planar projections...
  17. Hi @imurvai, Actually I wanted to do that in software, but not get too deep in low level code... that's why I tried BC2. Since it seems that getting rotation encoder encoder is not yet available in BC2, I used external sensors on a PUP hub to have a minimum feedback about the position of the arm. But now that Technic hub is supported in Powered up app, I'll use that to make what I want (even though this app does have some stupid shortcomings, such as limited range in input/output fields!)
  18. We could derive max wire current from its gauge (this is probably the highest rating of all the things that could limit current), but as plugs and sockets are custom, it's impossible to get manufacturer data... and I don't know how to "safely" measure that :(
  19. Problem is that it appears partially outside of my screen... Disconnect button on device screen? Otherwise, found a little glitch: I seem to be unable to discover a Technic hub that I renamed using powered up app. After changing back to default "Technic Hub" name, worked fine.
  20. Works great! (tested with @Didumos69 Rocky 42099 B-model). Two things nonetheless: I can't seem to be able to move "steering wheel" control on my device (Moto G5+). I can move other control types. Is there a way to disconnect other than kill the app (or power off the hub)?
  21. Yes they are, but only for "dumb" motors (M-motor, train motor, LEDs). Control+ or Boost motors are identified through serial link protocol. See https://philohome.com/wedo2reverse/connect.htm and https://philohome.com/wedo2reverse/protocol.htm
  22. Thanks @pennyforge! Worked perfectly...
  23. Any tips for a Python noob to run this on Windows? Requirements?
×
×
  • Create New...