Cosmik42

Count me in if you do make more! Yes, that would explain why one of my ideas didn't work.  Actually, the next version will allow you to set this timer to the value of your choice. On another subject, @Lok24, can you check if your sensor works in this new version?

I have the same problem. Which dongle do you use? Can I use more than one dongle at a time? I bought this one: https://www.amazon.de/dp/B007MKMJGO/ref=pe_3044161_185740101_TE_item I can connect to 12 hubs with it.

Did you custom build this hardware or is it something I can buy? If I can find it, I could add support for it. And my architecture is based on the very clean one of @Mr Hobbles. So adding new hardware is quite simple which is why I am proposing to add BuWizz, WeDo 2.0, but also 4D Brix and maybe yours!

It's a fair question - Battery Level on my phone and all consumer devices are in % - so I kept that norm. But I agree that I cannot guess the type of battery plugged to it, so showing volt makes more sense. You need to pass the object inside your function. So you function will look like this static void MyGlobalFunction(Hub train) { train.Stop("A"); } And then inside your script you can call it like this MyGlobalFunction(Hub[0]);

Definitely. I like the logic you have implemented for your project and will do something similar! As a matter of fact, sensors via SBrick start to act funny as soon as the battery is 3/4 empty. Weird, out of bound values.

That should satisfy some of your requests. Coming in the next version.

Oh that makes total sense as I am running into similar issue on my 'self-driving module' where speed are hard-coded per section, and low battery trains kinda suffer there :)

Do you have an usage scenario for the tilt? As mentionned earlier, I don't own one, but can't seem to justify buying one. What scenario for these properties too? I can easily exposed them anyway. Otherwise it's a pretty solid list. Will see what I can do. Yes, indeed. The best here would be for me to expose the distance, so that you trigger no matter what the distance, then use the actual distance value to do what you want on your motor speed for example. Will look into it.

I can add more color, but at least with my sensor, these color were not reliably detected. Meaning that for exemple a dark grey is detected as blue, sometime. The colors I picked were the one I could 100% of the time correctly identify. But I can add these other colors. It's a good point and a definitive => must do! This is a very good question. I trigger only when the color is found AND the distance to the sensor is very close. The reason again is reliabilty. When nothing is very close to the sensor, it picks up almost random colors from its camera. Finally, there is a 1.5s cool-down before another color event can trigger, to avoid too many shot of the same event at once.

I wish there was polling option in this forum. Many of them support this feature but I can't seem to find it here. Here is the menu to vote for: * Interactive map (14 votes so far) * Android version (13 votes so far) * iOS version (5 votes so far) * Mac/Linux version (4 votes so far) * WeDo 2.0 support (4 votes so far) * 4DBrix support (2 votes so far) * BuWizz support (1 vote so far) Also, don't hesitate to mention if you have other ideas!

Hi everyone, I am running a poll on our FB page to vote for the next major feature to be developped. Come join and vote! https://www.facebook.com/groups/2311775879052281/permalink/2331147483781787/

So I kinda just discovered the official protocol from Lego! And I found what I was looking for there: more than a disconnect, a power off: [0x03 0x00 0x02 0x01] Adding that 0x01 specify a clean power off. So no chance to reconnect again if you are still listening.

Sounds amazing, but without such hardware myself, there is no way I can integrate such a dream hardware :)

Sincere apology if it came out that way! Actually reading @Kalahari134, I realize that he is talking about a physical controller, which I missed when I replied. Here is my plan: create some kind of manual controller screen dedicated to manually interact with all the pre-prepared scenarios. Would it achieve what you are asking @Kalahari134?

I believe LTP can do this already. The idea is to define train paths for specific scenario, for each of your trains. At the end, you are still playing manually with them, but in small scenarios. For exemple => Bring red train from section 0, via section 4, to section 2. Then stop. => That bit is a button you click that will make sure your trains goes where you want it to go. But that's it. To get there, the software make sure there won't be any crash and switches will be aligned to accomplish that path. But you remain in control. You can put the layout in full autonomy, but what's really fun is to trigger all your scenarios on your trains independantly, when you wish so. And you can do just that.

Thanks! Nathan shared that earlier too and it works great indeed!

Not yet, but I have it in my short list! For now I support 'Bluetooth' enabled devices like PUP, SBrick and soon BuWizz. I am talking with 4DBrix to support their USB swiches. So it is totally thinkable to do support more USB devices! It's in the same bucket as 'Mac OS' port. There is an initiative that helps support cross-platform c# code. I will investigate soon!

Hi Sandra! It sounds like you are working on some great automation project too. I don't own any Arduino, so I can't help you there, but my own implementation was inspired by the work of Nathan who shared node.js library. Very clean and readable implementation that should help you get the protocol right!

This post is getting pretty long so I create a separate one that act as an 'How-To' for the Self-Driving System.

Hi everyone, I just released the V0.6 of The Lego Train Project which delivers the ultimate goal I set to myself: build a fully automated driving system for lego trains. First you can watch this 3 minutes video to understand the high-level concept and see it in action: Download V0.6 here: https://www.eurobricks.com/forum/index.php?/forums/topic/169318-automation-control-all-your-powered-up-power-function-sbrick-devices-with-a-single-software/&page=1 #1 Map out your section The first thing that you need to do is to define your Sections. Typically you need to define a new section everytime you have a Switch. Here is what I did on this simplified version of my layout: #2 Report your sections to the software. Note this is a one time setup! Note about Switches: - I use a very simple system with a motor like this one to motorize my switches You need to define that a Motor is a Switch for it to show up in the Switch drop-downs. Note about Sensors: - In this scenario I only use WeDo 2.0 distance detectors. They are easy to buy and cheaper than the Boost Color-Distance detector. Note: WeDo 2.0 & Boost Sensor should show up automatically. SBrick Sensor have to be defined manually. # 3 Define Train's Paths Once your network is setup, you need to create the different scenarios your trains will take! #4 Some Important Verifications Before Starting: - Make sure each Train is attached to the section it is physically at. This is the only way for us to know constantly where is a train. A wrong section on start will break the automation. - Select a path which contains the section where this train is. Otherwise the automation won't start. #5 Enjoy! And that's all Folks! Hope you enjoy it. It was an incredible challenge to put it together and I hope it will be used beyond my own layout :) Cheers! Vincent.

V0.6 is out! * Self-Driving Trains! * New UI * More Robust Hub Detection * Add Port Selection for Sensor Events * Bug Fixes You can download this version here: https://www.dropbox.com/sh/185eb598dldqodm/AADXVEz2u5nPTAlJLYD_18_Ka?dl=1

Thank you so much Thorsten! Totally agree on the manual play part. This is why I put some extra love in adding visual and icons to the top tier which is 100% meant to play manually. It's also at the top because I want it to be the most obvious and immediate thing to do. Slide a speed dial or press a switch button. I want to thank you as well for your continued support on this project. Have a great weekend!

Thank you! Hopefully will be able to share a build today. The self-driving system has a lot of edge cases that I am squeezing one by one.

Sneak peek to what is coming up! Fresh UI, robust device detection and ... self-driving lego trains!

Just to clarify => Do you see any distance output in the console on the faulty Hub? Because if so - then it's my software that has an issue.