Cosmik42

Really fun idea!!!

Sadly I did not. So I would love to take you up on your offer in order to integrate this hardware.

Sorry, I meant sound effects :) And I got my answer from the other thread :P

I love you really use every bit of possibility from this. Well done!

This is awesome! What do you use to trigger the SFX?

Wow!! That was soooo cool! Never though of using strings!

That sounds amazing!

No point making a hard-coded case for Black. Let's offer the option to all colors. It was fixed the same night. You were just too fast to download it :p Thanks for the feedback though.

Then the only way to solve your problem is to let the black color trigger with a lower partial value. I will cook you up something.

It is totally possible to integrate NXT as well via Bluetooth. Issue is I don't own one. Will see how easy to find one.

BTW, I confirm EV3 is the next device being integrated! Started tonight and I am half way through!

Yes, but you see this partial 0, 1, 2 or 3? It means that the program thinks this black is way further away than it probably is. It's why I offer you that you can change the current hard-coded value of a Partial 5 to trigger a color, to the partial of your liking.

I think Black is the most confusing color for the detector. Because it is hard to estimate distance when the surface is black. If it never triggers its because it never believe it is close to the color itself. I had a more in-depth look and I believe I can support EV3 in a just a couple days of coding.

Sounds amazing! Do you plan to sell these? Any chance to make them compatible with PF or PF2 plugs? Would love to integrate these to "The Lego Train Project" if you make them available.

Given you want to double down on the color route, let me know if you want me to expose this 'partial' trigger? Yes! Forgot to add it to the helper list. It is SetLEDColor(Colors color) where Colors is an enum with the following options: public enum Colors { BLACK = 0, PINK = 1, PURPLE = 2, BLUE = 3, LBLUE = 4, CYAN = 5, GREEN = 6, YELLOW = 7, ORANGE = 8, RED = 9, WHITE = 10 } Mostly yes. There's a lot more but most of it is internal stuff. I had no idea EV3 was Bluetooth enabled! I just found a great open-source library to connect to it. Sounds like an amazing idea! I will definitely explore this!

@Toastie, great link! Taken from it, I think this is the best answer matching both your experience and the one of @Mr Hobbles : "[The number of BLE device you can connect to] depends on the amount of RAM you have available on the master device. For a stand-alone Bluetooth dongle where the stack runs on the dongle itself, this is anywhere from 6 - 8. A lot of dongles I have seen support 7. That said, if the dongle is using the Bluetooth stack that’s built into the operating system (or if you use the built-in Bluetooth adapter on the phone/tablet), then you are not RAM-limited (you have gigabytes available rather than a few hundred kilobytes), so the limit is a lot higher."

Ah crap. Maybe .co.uk or .fr?

Used to have the issue too. Bought this dongle and can connect up to 14 hubs with it: https://www.amazon.de/dp/B007MKMJGO/ref=pe_3044161_185740101_TE_item

After what was a productive weekend - V0.9 is out! - WeDo 2.0 Full Support! - Fix SBrick+ Sensor Calibration - Fix Saving of Project using PUP Remotes Download it here: https://www.dropbox.com/sh/b5x0kca3u0nlkpa/AABBE3gzieJP66A29QI5UXgOa?dl=1

Actually not. The cool down is here to avoid too many repeated positive detection. In the case of a train going fast and the color on the track being short, the train might miss entirely the color. So no color detected, no cool down.

This is also why I moved away from color detection to do sensor detection. It is a little more expensive as you need more sensors, but they are 100% reliable where sometime color detection is not when trains are going to fast.

Well now you understand why I never exposed them before. The color detector constantly 'think' he has found a color but often he is just plain wrong. The 'partial' value correspond to how close you are from the detector. I trigger only if a color is triggered close enough to the detector so that we are 100% certain it is in fact this color. I could probably let you adjust the 'partial' level if you want to. But right now it is set to 5 minimum (1/5 of an inch).

Great to read and really sorry for this. #Beta :p

This is an early V0.9 with WeDo 2.0 support. I added a fix for the saving issue. Give it a shot! https://www.dropbox.com/sh/b5x0kca3u0nlkpa/AABBE3gzieJP66A29QI5UXgOa?dl=1

Ooopss! I know exactly what it is. Fix on the way!