Cosmik42

In the spur of an evening I managed to fully support WeDo 2.0! Coming up in V0.9

Oh I found it by downloading the WeDo 2.0 Official SDK. They have a dedicated Characteristic just for disconnecting: private const string WEDO2_DISCONNECT = "0000152B-1212-efde-1523-785feabcd123"; // "152B" The call looks like this: WriteMessage(new byte[0], CharacteristicDisconnect);

Ah good, glad you found something! I am still trawling through that document and adding support for various features to my library. :) I do wish it was more detailed into the various commands that can be sent to the various attached devices. While it does a pretty good job of detailing the protocol, it mentions very little about sensor modes and message parsing, special motor control modes (ie. swing mode), etc. Any idea how to do this but for WeDo 2.0 Hub? I am finally implementing it and can't seem to find the 'Shutdown' call.

Has anyone in this forum connected to a SBrick+ programmatically to read sensor data? To my surprise, the data is raw voltage from the sensor, making it sensible to battery level, and I can't figure out a relationship between battery level and the data I am getting from the sensors making impossible to properly calibrate it when battery is not fully charged. Help! :D

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 Download here => https://www.dropbox.com/sh/8dtjo22d4ddjcj0/AAAHCxMamxemVQ67vIoyPcb6a?dl=1

And .... it's almost ready! Will release this update tomorrow.

Close to complete 2 requests at once: - Provide parameters for event triggers - Support the Remote

Ok, the current documentation from Lego doesn't help here. Have anyone of you managed to subscribe to the left (+ / -) and right (+ / -) buttons of a PUP Remote? EDIT: Found it. It was under 'Sensor Message'.

Connection issue being solved, I implemented LED colors yesterday nights! Available in the next version.

Awesome! :D

Sent you a build in PM to test if it fixes your issue which very strange.

That's a great idea. Alright, thank to your help I just ordered that tilt sensor! Will make sure to implement it! Actually, this is a great idea! Will make sure to do it too.

Actually, as is, it will search for more. Easy to do! Added to the list!

Great!

I don't get that. Can you share a project where you have that behavior?

Here is a hot fix: V7.0.1 - 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 Link: https://www.dropbox.com/sh/axyjdb1gaebdcfi/AADJwkedu3jbu7gQYCqwY9Goa?dl=1 Ok, so wait, I can arrange this quickly and put in V0.7.1 Done. This version now reverts to multi-windows.

Actually that was made on purpose, to avoid having more than one opened at a time. But I can revert to what we used to have. I don't have this error here. Can you send me your project file or copy paste the full error? Scratch this - found the bug. Sorry about this!

Looking forward to it!

V0.7 is out! - 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. Download it here: https://www.dropbox.com/sh/c4wi20c540zncsr/AADdfH97vKmAWdL-KJgPypSda?dl=1

Thank you so much! I am in touch with them and I am trying to get a sample from them. If it doesn't work out, I will gladely accept your offer!

this sounds great. It would be awsome to have a property to set the value for the cooldown programmatically. Running fast --> short cooldown, running slow --> bigger cooldown Hub[0].setCooldown("A",2000); Every illegal number should cause an outputmessage and set it to default. That took me 1 minute :D Final form is this one: Hub[0].SetSensorCooldown("A", 2000); Will be available in the next version, hopefuly today!

@treczoks, I just added these parameters, so that you can tune this cooldown the way you want. @mawe, this will also help you with what you want to achieve

Actually, now is a pretty good time! But maybe I can buy it in Europe? They seem to be located in Canada?

Such an original concept! Congrats!

Awesome. Thanks for checking!