Jump to content

Lok24

Eurobricks Counts
  • Posts

    1,240
  • Joined

  • Last visited

Everything posted by Lok24

  1. Hi, I think the four loops " wiederhole fortlaufend " should be removed completely. Just: - If slider is moved - call subroutine "Getriebeschalten" - start motor E with ....
  2. It's the same with iOS, only later I never faced such problemes, App (android), RaspPi, ESP32. I'll test later what happens here....
  3. Hi, could you please send a pic of the program? Perhaps this gives a hint....
  4. The "yard loop" is only for shunting purposes, so it has to be separeted (signals, allowed speed, rules for driving are quite different), you cannot use a a shunting track for "normal trains" (here in Germany) These sections are usualley separeted, so that shunting does not affect paasenger trains. It is very useful if you motorize the switches. For the locos and/or automation you need metallic tracks and modify all(!) locos on the layout.
  5. Hi @zephyr1934, It's no loop, but the turnout track I assume. And therefore it should not have any connection to the other loop. It can be reached from all shunting tracks in the lower section and is absolutely required. I'm very happy with that idea.
  6. You always argue from the LEGO point of view and disregard all the rest. We're talking about a raspberry product. Imagine you come from the microcontroller community and have already a PI and now want to connect motors ...... and here is a way to get drivers, libraries, motors, sensors and so on to move something. It ist not a LEGO product. And I am surprised that the ideas of @CheungsLegoCreation are interesting to you - I mentioned in my first reply already the idea of using a camera or others. In summary:a raspberry offers much more connectivity than a LEGU HUB. And much more different software. And is very much cheaper than a RI set ! And does things very different from the technic Hub. But for me EOD, as it has nothing to do with with the woderful robot of @CheungsLegoCreation
  7. If you just want to understand robotics/programming (i.e. in an educational context) it might not be useful to start at zero. Yes, you're missing, that it offers the chance co connect the two worlds (microcontroller and PU). And therefore much more possiblites using the GPIOS to expand PU concerning communication and control. What's wrong with that? I can imagine lots of applications, and there is nothing similar on the market.
  8. As mentioned: the HAT has quite different properties: you can connect a camera to the PI, or other electronical stuff, inluding audio, set up a webserver to control your model etc. The intention of the HAT is not to replace the technic hub, but to connect powered up devices to a rapsberry Pi.
  9. The syntax is wrong. Yes, sure What is the Idea, if you cant' run it? What is the question?
  10. the set 31313 never contained any software, it was always free for download from the LEGO site. You don't need any code. But software might now look different from that your kids used. Today it is based on Scratch, formerly it was based on LabVIEW. But the features shold be the same.
  11. No, never heard that. What software do you use, can you send a screenshot where license code is required?
  12. The pybricks is found under https://beta.pybricks.com/ For parallel working look here:
  13. As I understand (and know for the PU-Devices) you have to download the pybricks-FW, which is still in beta, to use RI Aren't there options in motor control command whether command has to be finished or programm continues immidiately?
  14. thanks @joeh There is no problem to connect EV3 motors with their full functionally to any hub if you use some kind of adapter. But as a L-PU-motor is available for app 16 € it would be really useful, I fear. The only difference might be the precision of measurement.
  15. You could set maxSpeed ..... With tacho motors instead of the train motors you can really archieve low speed: https://youtu.be/UaNMkoPSUSA
  16. Sure, I have no Spike prime, that's all. Don't know, but it does.
  17. It's not a matter of absolut positioning, but of rotation feedback in general. That could be useful, but nor for me.
  18. Profile is switched as indicated in line 39 SWITCH = "CENTER" where "CENTER" is a reserved word in pybricks which means the green button, you can also use SWITCH = "B+" i.e. And it does't necessarily change the speed, but intended to have a different acceleration. Color of remote indicates the mode as set in lines 50/51 LED_A = Color.GREEN*0.3 # Remote Profil_A, color * brightness LED_B = Color.RED*0.5 # Remote Profil_B, color * brightness so it should turn from green to red. You can set the speed-buttons in 36-38 to "B", if you like
  19. Hi, if I remember correctly that's is an issue not fixed in pybricks, 10 is the maximum. Edit: yes, here it is: https://github.com/pybricks/support/issues/485 Thats correct, the Hub starts, but not the program. To start the program you have to press the Hub Button when flashing blue, LED turning to RED. And then press remote green button. Pressing the Hub button when program is running stops program, returning to flashing blue. And so on
  20. @Toxic43, I have no idea what went wrong, sorry. When you open the program in beta.pybricks.code you have two lines that handle the behaviour of the remote: remoteTimeout =10 # hub waits x seconds for remote connect after starting hub remoteName = "" # connect this remote only You only have 10 seconds after starting the hub to connect, and there should be no "remoteName" entered to connect any remote Did you really run https://beta.pybricks.com/ ? Did you turn on "include current program" in the settings? Way sould be : Program starts with a red light, which turns off after 10 secs, unless you press green button on the remote within the 10 seconds. What color does Hub show when starting the program? Edited Aug 22: It's now available with code.pysbricks.com
  21. Hi @CheungsLegoCreation One of the main problems to me: varibale names! As far as I know following is announced: - support for other device-IDs (what should solve the sonic problem) - new Icon-design - documentation(!) The method to load programs into the hub (via VM ware) I would not expect for this year.
  22. I think it's not supported, there is no tile/icon for it. Same with force sensor, I fear.
  23. @JaBaCaDaBra yes, nice idea you than just have to take care, that no other access is in progress (i.e. aksing the roration of a motor on a HAT momentarily "disconnected". But that all can be solved, I'm sure.
  24. There are some points: you have to use beta.pybricks.com instead of code.pybricks.com, version should be 3.1 then, only this supports the remote one remote can only communicate with one hub no communication between hubs
×
×
  • Create New...