Jump to content
THIS IS THE TEST SITE OF EUROBRICKS!
THIS IS THE TEST SITE OF EUROBRICKS!

Toshi

Eurobricks Vassals
  • Joined

  • Last visited

  1. After building the Greyhound, Rocky and the Hot Trot, I would love to get building instructions for this one also! …I would likely try to come up with an alternative power source, since I think BW3 is way too expensive, but this model would be a good motivation to finally getting around to doing that! Any chance you will make instructions in some form and a possible timeframe for it to happen?
  2. Die Anleitung kann man auf Rebrickable kaufen: https://rebrickable.com/mocs/MOC-19517/Didumos/4wd-rc-buggy/#details
  3. I figured it out in the end, so it works as intended now! My problem was that the definition of the center position and the definition of the max steering angle are not on the same "page" in the configuration. That prevented me from making the connection at first, I guess... Manual configuration was a bit "trial & error", because I needed to set a value, then start the profile in order to test it and repeat this until everything was the way I wanted it to be. It would be very cool if this was either more interactive (changing both values while the profile is running), or if you could see the current values during configuration or at least the result of the automatic configuration! (maybe something to keep in mind in case you feel bored some day )
  4. Okay, thank you for looking it up! I still have not figured out how to configure the Servo manually though… :(
  5. Hi, would be cool to understand how it is implemented! :) What do you mean when you say that measuring the endpoints is not precise? Using the nearest 90 degree position sounds somewhat situational. I guess this means I was lucky with the other two models, where it is working correctly?! If I remember correctly, both 42109 and 42099 use an L-Motor for steering and XL-Motor(s) for driving. (I only built 42109 once and in 421099 there was no possibility for a mixup of motors) If Lego usually ships the motors in "90-degree-alignment" and the L-Motor was never used for driving, this might explain it for my other models. Since "Hot Trot" uses 42129 as a base and has 3 L-Motors, it is certainly possible I used one of the L-Motors used for driving before as a servo now... So it is certainly possible the angle in this motor was not a multiple of 90 when I put the gear rack in place... ;) I do not have the model & remote with me right now, but I will check how to do the manual calibration later on!
  6. @imurvai: first of all thanks a lot for your app - really appreciate it! :) I currently have a problem with a PU motor used as a servo that maybe someone can help me with... If I use auto-calibration, the servo moves to both "endpoints" but afterwards it does not stop in the middle, but clearly off-center! At first I thought that I might have overlooked something while building the model (i.e. needing to align the motor / gear rack in a certain way upon assembly), but since the rotation encoder should have a resolution of 1 degree, I no longer think that this is the case. I also tricked the PU App to calibrate the servo (had to switch ports & connect another motor to do that) and the LEGO App calibrates correctly - pretty much dead center. Is there a know issue with auto-calibration? Maybe something to do with crossing the 0/360 rotation encoding at a bad spot? Is there a way to see the values chose by auto-calibration and modify / correct them somehow? Can the servo be calibrated manually? I did not have time to really investigate, but so far I have not been able to find a manual option. (I would also need the plain values for all extreme positions in order to do that, I guess...) Edit: I forgot to mention that I have two other models where auto-calibration works fine! (a stock 42109 & "Rocky" by @Didumos69 - I am currently building "Hot Trot", also be @Didumos69)
  7. I guess 42125 makes those available now! :) (not that I am a purist anymore... ;))
  8. Same here! Makes little sense to have L and XL motors if they only differ in size and not in other characteristics!?
  9. I have no other specifics about release dates and features, but the videos on YouTube about motorising the Sian (42115) do not make me hopeful they will be able to power more than one RC motor on the BuWizz. :( Maybe the RC motors they are using in the project are prototypes and maybe the BuWizz 3.0 is not ready yet either, but using 8 BuWizzs to power 8 RC motors is kind of a let down for me! :(
  10. I would also be very interested in details about RC motors released by BuWizz! I actually think they are facing quite a challenge here... :( As far as I know, it is not possible to drive 2 Lego RC motors with one BuWizz 2.0 in ludicrous mode - even fast mode does not work reliably all the time afaik (look at the Ripsaw thread by @Marxpek). This might depend on the weight of the model of course, but in case of the Ripsaw with 8 RC motors, I doubt there is more than 500g of weight for each single motor to move... If they release their own RC motors, I would expect it to be possible to run at least 2 (best would be 4) of them with one BuWizz in ludicrous mode - everything else would be strange in my opinion. So they either need to find a very efficient internal motor to power their RC motor, which might make it expensive to manufacture (?), or they need to release an improved BuWizz 3.0 (which would be a let down for all BuWizz and BuWizz 2.0 owners, I guess). Maybe it is also possible to improve the old BuWizzs via firmware update, Idk?! At the same time I am not certain the market for a new RC motor is the same it was a few months back, because Mould King released their Black Furious L-Motor, which also has 1200 rpm and therefore already is a competitor to a new RC motor - and with a better form factor too! (the L-motor is easier to integrate than the RC motor in my opinion) The price is also very reasonable, which makes it harder to justify a price tag that is much higher than what Mould King charges - unless there really is a big difference in quality or features... It will be very interesting to see, what they come up with and what the price tag of the final product will be! My hope is that they will improve the old BuWizz (at least the 2.0 version) via firmware update in order to allow a higher load before shutting down... :)
  11. Buying plastic bricks can be way too addictive! Therefore I think it makes sense that there is some sort of (constructive) control over our hobby spending habits - we don't want it to get out of hands after all! ;)
  12. Guess I should have checked the output in the app before posting, I suppose! :) Can't do it right now, because I do not have the controller with me - will do that next week... If the joystick really does behave different than I expect and does not return 1/1 in the top-right-corner, will doing the same setup, but assigning x and y to different joysticks also work? Will the app still mix it right, even if the same motors are assigned twice to different joysticks??
  13. I always assumed that the joystick will somehow „adapt“ to its physical limitation!? It should be equivalent to a „+“-Controller (no idea what they are called), right? And „top-right“ would be 100% for both axis on one of those controllers, correct? After all, you do not want to slow down while steering, right!? ;)
  14. Hi imurvai, let me start by saying that I love your app and really appreciate the work you are investing in it! :) I am also trying to control a tracked vehicle like this and while it does work in principle, I find it rather hard to maintain precise control over a fast tracked vehicle I am currently building (4 buggy motors, 2 per side). I have also tried to play with the settings for the x-axis, using exponential or logarithmic scale instead of linear in order to have more control, but so far I am failing! :( Maybe I am doing something wrong, or my controller is not working correctly?!? How exactly does the app mix the inputs to the left and right side (track) when you configure it like you describe? At y=1, x=0, I would expect 100% to both tracks. At y=1, x=0.1, I would expect 100% to the left track and 80% to the right track. And at y=1, x=1, I would expect 100% to the left track and -100% to the right track. Thanks a lot in advance! :)
Sponsored Links