Cosmik42

Hi guys, I have a question. Have you succesfully connected a WeDo 2.0 Distance Sensor to a Train Hub and managed to receive data? I had no problem connecting a Boost Color/Distance sensor and reading its data thanks to this great article: https://github.com/JorgePe/BOOSTreveng/blob/master/ColorDistanceSensor.md However, this protocol does not activate WeDo 2.0 distance sensor when mounted on a train hub. Help! :D

I do not own this model, but I can confirm these motors have a very smooth progression.

As soon as you turn off the software, your Hub will power off. That said, this is the behavior I see with a standard battery. Not sure how it behaves with a plugged up battery.

Great to read! This limitation will be fixed in the next release.

For now detection is based on the name of the Hub. I have a new version using UUIDs coming up. Make sure your Hubs use one of these 3 factory names: 'HUB NO.4', 'LEGO Move Hub' or 'Smart Hub'. Let me know if this helps!

Absolutely. They are not discovered at all? Did you try to pair them? If so it is best that you remove any pairing.

If this code is ever ported to mobile, 7 I believe is what most Android phones can achieve. On my PC I believe I can connect up to 15 without issues as long as you have a Bluetooth 4.1

Sure! UI is still very rough. If you have any valuable inputs as of how this should look like, I take any feedback!

I will need to buy some. How do you activate them today? I will need the protocol for this to be a reality. Will try to find them in Europe.

@Toastie, thank you for the kind words! This is coming up. Will be in the next version I share, probably around January 5th once I am back home and can test a lot of recent upgrades to the software You can create very complex scenario by programming directly in C#. To do so: - Click 'Add a Program' (bottom right button) - Click 'Add a New Sequence' - Click 'Edit Code' - It comes with some exemples of code. Basically every hub that you will plug to this project will be accessible. You can then call functions on them like SetMotorSpeed, Stop, Wait, etc. - Click 'Test Code' to check if it compiles and run as intended. - Then Close. You can then run that sequence in the future (if you save your project) by clicking 'Start'. Here is an exemple of such code from my own layout: if (!Hub[0].IsInAction && Hub[1].Speed == 0 && Hub[2].Speed == 0) { Hub[0].IsInAction = true; // Activate Switch 1 (Double Cross) To The Right Hub[3].ActivateSwitchToRight("C"); // Start Yellow Train Hub[0].SetMotorSpeed("A", 60); // Then Activate Switch 2 To The Left (To Welcome Yellow Train Back) Hub[4].ActivateSwitchToLeft("C"); // Wait for the train to start and clear the way Hub[0].Wait(2000); // Activate Switch 1 (Double Cross) To The Left (So that red train takes the large route) Hub[3].ActivateSwitchToLeft("C"); // Start Red Train Hub[1].SetMotorSpeed("A", 60); // Release the lock Hub[0].IsInAction = false; } I guess this is possible, but it would require quite some work and I would rather not commit to it just yet. Maybe we can take this discussion to PM as it will require a lot of synchronization. Hope all of this helps!

This is extremely useful and clearly the heart of the issue as the protocol is different on Boost vs Train hub. My method of identification is based on the name of the hub but there are better Technics for that. If I can't automatically detect the right type of hub, I could offer an option to override it manually.

I thought about it. If usage of this really takes off I might take on the endeavor.

You can use it for such purpose too! All you need is using Bluetooth enabled hubs to control them.

@Giottist Thank you so much for the kind words and complete report! I very much appreciate it. This kind of bug report and feedback is what I was hoping for sharing my work here so thank you! I have an idea why your old train isn't working. I will work on it and provide a new build! Let me know once you start digging in the events and procedures! Also I do not own lights so I never tested them. Will buy a pair now and adapt the software to make them compatible with them!

Thanks Toastie and nice to meet you! Oh goodness, this is my bad! Here is a working link: https://www.dropbox.com/sh/ux2r02l545zfyka/AAAbeRZMX5VTOTuQecHJLXewa?dl=1 It is not the latest version, but as I am not home this is the shortest path to giving you a working build! Will provide an updated link soon. Thanks for the kind words. I hope this software is useful to you! Vincent.

Switches are nothing more than another Hub with a motor that automatize your switch. Look at this video for an example: https://www.facebook.com/groups/18854918656/permalink/10156184440253657/ Color sensing works with like this: Distance scenario is as follow: Put a distance sensor next to the track (not on the train) and when a train passes in front of it, it triggers and allows you to do activate something else.

Hi everyone, I am new here and loved reading many of your posts! About a month ago, I decided to try to connect to my newly acquired Powered Up train via bluetooth on my own computer. The goal was to be able to control all of my train at once, and better, program complex behaviors. The forum was a huge source of inspiration, but if you are not a programer, just technical chat. What I set myself to achieve is to create a program that would be user-friendly and capable of connecting to any number of Powered Up & SBrick devices! 1 month later, I am happy to report that I have built a complete custom solution to achieve just that with "The Lego Train Project". Here is a video that shows you an example of how the software works: With it you can: - Control as many hubs as you own at the same time, creating a centralize solution for your trains, switches and other sensors/motors. - Read color from color sensor mounted on each trains - Create (color or distance) sensor related events that can activate actions on any other hubs of the network - Create C# sequences that compile and run dynamicly! I am building a fairly complex train automation project with it for my own layout, but would love if other would be interested to test it Edit - Source Code is out - June 27th 2020! The project has now been renamed "BAP" short for Brick Automation Project. The source code is now freely available here: https://github.com/Cosmik42/BAP Edit - V0.3.1 is out - 01/08/19 Minor update includes: - Code editor improvement - Fix Hub not showing up on certain configurations - Add 'State' variable to each hubs Edit - V0.4 is out - 01/14/19 Major update includes: - SBrick support - Global code editor Edit - V0.5 is out - 01/14/19 Major update includes: - Full support of SBrick Plus and PF Sensors. - Introducting an Anti-Collision system that works with simple distance detectors - Bug fix: Code was executed twice on sensor event - Bug fix: Better handling of faulty device connection V0.6 is out - 01/20/19 - Self-Driving Trains! - New UI - More Robust Hub Detection - Add Port Selection for Sensor Events - Bug Fixes V0.7 is out - 01/27/19 - Programming: * Plenty of new properties are now available * You can name sequences * You can customize distance/color trigger cooldown - Self-Driving module: * You can now customize clearing time and 'stop needed ahead' speed * Add capacity to wait for the next 2 sections to clear * Allow to run code when next section releases * Speed Coefficient, to slow or accelerate trains based on battery level. Edit - V7.0.1 (Hot Fix) - Programming: * Fix a bug preventing the access of custom code with events. - Self-Driving module: * Fix a bug preventing the deletion of Paths. * Fix a bug with 'Clear 2 Sections' in the Self-Driving Module V0.8 is out - 02/02/19 - Remote Control Support - LED Color Configuration - Allow to start and stop Bluetooth Scanning - Allow to disconnect single devices - Programming: * Support for Custom Trigger Events * Change the color of LEDs programmatically - Self-Driving module: * Implement Green/Red lights based on Section occupation. * Fix a bug with looped Paths V0.9 is out - 02/03/19 - WeDo 2.0 Full Support! - Fix SBrick+ Sensor Calibration - Fix Saving of Project using PUP Remotes V1.0 is officially released! - New Name: The Brick Automation Project - EV3 Support! - Fix of SBrick port (port B and C were inverted) - Add 'Released' event for PUP Remotes - Fix Battery Level Not Showing up for PUP Hubs - Introduce official terms of service V1.0.1 is out - Hot Fix - 02/11/19 ---------------------------- - Bug Fix: Remove hard-coded COM5 for EV3 connection and properly uses the COM input by the user - Improvement: Stretch the length of the Hub names to allow Battery % to show up V1.1 is out - 02/19/19 ---------------------------- - New Feature: PFx support! - Improvement: Better Section Reservation for Self-Driving System. - Bug Fix: Show proper battery level of remote controls - Bug Fix: Motor Slider now properly show negative speed. - Bug Fix: EV3 Motors properly activate on their ports. - Bug Fix: Train not stopping immediately in Self-Driving module V1.2 is out - 03/17/19 ---------------------------- - BuWizz - Implementation - Play Sound (WAV) from the Event section V1.3 is out - 05/04/19 ---------------------------- - Mandatory update to fix malfuntion of motors with the latest PUP Firmware V1.4 is out - 08/18/19 ---------------------------- - Includes a way to limit the devices capable of connecting (Devices from a project or from a global list) - Fix a bug affecting the latest Boost Hub firmware update. Port id are properly assigned base on firmware version. - Self-Driving Tutorial images have been fixed. V1.5 is out - 08/21/19----------------------------- Control+ Hub - Implementation complete, including new L + XL Technic motors- Fix a bug with EV3 preventing the use of more than one sensor at a time- Fix a UI bug related to the Section part of the Self-Driving Module. That section now properly redraws after window resize.You can download the V1.5 build here: https://www.dropbox.com/sh/o3i9653vwx755ps/AABfxfpL_4SeoBS4HyCVZLT_a?dl=1 Below is a demonstration of the self-driving module! Note: The app works only under Windows 10 and requires a Bluetooth 4.0 Connection! Sorry for the current limitation!