Bliss

Well, thanks to you to make the suggestion. I did not even know the existance of the Lego ToyPad before you mentionned it ! It really makes a great addition to this project as we can now mix a bunch of very different lego devices all in one Graphical Programming IDE... In the latest version of Lego Blockly, I added more ToyPad Led blocks. In addition to "Set Led color" block, I added Flash Led and Fade Led blocks. For each "Set Color", "Flash" and "Fade", you have a block that uses a Color Sliders Picker or R, G, B Values. (For the Set Led Color block, there are 2 color picker types but I really prefer the Sliders and will probably remove the other color picker) Have fun!

@Toastie and all, I finally found a Lego Dimensions Starter Pack (Batman) for Wii. So I added a first draft of the Lego ToyPad support in Lego Blockly. (Version: 2026-06-24-1431) I will add more blocks (specially for the Leds control) eventually. For now you have one block to get the Tag Id of a particular region. The tag id is an Hexadecimal String unique to the tag I guess. And you have one block to control the LED Color (R, G, B. 0,0,0 = off). EDIT 29-06-2026: I added blocks for LED Flashing and LED Fading too. If you want to make a logic that fires according to a certain tag, you can print tag hex value in the status window using the Print block in the Control toolbox. You place the tags on the regions and press RUN in blockly. You can then copy paste the Hex string in variables... In the following example, I Run a motor on Interface B when any tags is on the Left Pad and stop the motor when the Tag is removed from the Left Pad Also the Left Pad goes green with a tag and red without a tag: (I used a one-shot rising to avoid sending LED command every loop scan since I did not yet cache the led command... I will implement Cache soon. Int.B output commands are cache already except for the reverse command...) EDIT: I added Cache to every ToyPad commands so it will not send identical consecutive commands to the ToyPad. I Removed the one-shot rising block in the previous example and everything appears to work flawlessly. Let me know if it works for you. I only tested with a Wii ToyPad. I read that it shoud work the same for PS3 PS4 version but CoPilot tells me it might be different. So please let me know if you have a PS3 PS4 ToyPad and if it works. Thank you.

Well, I just learned something today again... It appears indeed that the default firmware can be changed and PyBricks can make these hubs autonomous which is really great. But, out of the box, these hubs are not autonomous and the LPF2 protocol is available and we can use them in Lego Blockly as is. Thanks again for pointing this out.

This is not 100% accurate. Yes RCX, CM are independant microcontroller and I would call them Smart Brick. But PF, WeDo1, WeDo2, LPF2 (Lego Power Function 2 = Boost, Technic Hub, Lego Hub, Lego Control Hub (Remote controlled car like the porsche with head and tail lights)) are not smart bricks. They are brainless bricks. So the brain, the program, must run on a PC, Phone, Tablet... @Toastie, other than that, your description of Lego Blockly is quite good and complete. The idea behind lego blockly is really to be able to program in one simple interface a mix of older and newer Lego Brainless Electronic Bricks (RCX/CM are exceptions). in addition, I wanted to make an App that does not need any install and would work in many OS (OS X, Linux, Windows). It is a Web App (Chromium) but can run standalone too. In addition to all protocol listed by @Toastie, it also support VLL (Visual Light Link) for Micro Scout and Code Pilot bricks. It is One-Way so it is not to control the Spybotics... Since it is a Web app, the code behind Lego Blockly is in JavaScript. The app is always evolving... Next lego device to be supported will probably be the Lego Dimentions Toy pads and tags somehow... I also have other feateures to add for LPF2 (Technic Hub internal LED, Control Hub lights, etc)

You mean "powered up"? ;-) I'm still looking on marketplace for this at a good price... There are quite a few lego dimensions for sale on marketplace but once I eliminate the xbox dimensions ads, and toy pads only ads, tags only ads, over priced ads etc, not much remaining... There is one though, that is a bit far but not out of reach... So yes it is in the plan and will work on this as soon as I put my hands on a set...

I noticed that and it is indeed counter intuitive... Hitting "ENTER" should be the same as OK... Not cancel... When I tried to create a variable at first I did the same mistake, i.e. just hit enter and no variable created... I did not make a fuss about it but now, since you point this out, I realize it is the kind of small issue that affects the quality of the experience... I think we lost the correct behaviour after I added some code to correct other problems... Often, while correcting a bug, we generate a couple others... I'll try to see if it is fixable somehow... Thanks for reporting... EDIT: This is now fixed in version : Version: 2026-06-13-1234 Now, pressing enter will default to OK.

Hello, Can you give more details how and where you are defining these variables? Because I can create a lot more than 4 variables using the Variables menu in the blockly toolbox. (Using "Create Variable"). And name them as I wish. Also, using the "Count" block from the Loop menu in the toolbox, this creates automatically variables i, j, k, m, n, o (I added 6 count block in blockly). So I wonder in what circumstances and how you create your variables? Maybe you could send your saved code (json file)? Thanks!

Very nice box! Could you add another LED ? An IR Emitter LED on Pin D2 ? :-) In the Int.A V2 toolbox, I added a new PF IR section... I thought at first to make a driver for PF IR on a separate arduino with a new serial protocol etc... But since we already have a driver with a custom serial protocol for Interface A, I thought it could be easier to just merge the PF IR protocol code in the Int. A arduino code... However, it is not that intuitive because someone that just want to play with PF IR in blockly (No Int.A) will have to choose Int.A V2 in the device drop box. So I changed the text in the dropbox for Int.A V2+PF IR... Also, this was not that simple to merge with Int.A V2 arduino code because the PF IR arduino code found on the internet is a "Blocking code", and it takes around 100-150 ms to send an IR sequence... It was affecting Int.A Commands response time... So Copilot gave me an alternative code using Interrupt timers which is quite complex but it works great... There are two new blocks really. The PF Single Output block: This block will start or stop one motor (RED port or BLUE port). There is no timeout. and the PF Combo PWM block: This block will start or stop TWO motors at the same time at the specified power. This combo command has internal timeout (about 1.4 sec I think) So to keep the command executing, you must repeat it somehow. Example to keep a combo command that runs 2 motors forward, power 4, for 5 seconds: Remember that an IR command takes time to send (100-200 ms). But I implemented a small queue (8 commands) in the Arduino code for PF IR commands. So you can have 2 consecutive single outputs block for Red and Blue port. Example: This will start "RED" motor first then it will start the "BLUE" motor. the delay between both motor starts will be as fast as the arduino can send the IR sequence for each one. I might eventually add a Status PF Ready that will tell the IR engine is ready to accept another command. We'll see. More tests are needed first... In my github, I added the new Lego9750_V2PF sketch. https://github.com/BlissCA/lego-blockly/tree/main/SketchArduino I used an IR LED I retrieved from OLD TV/VCR etc Electronics. Not All IR Led are the same. With mine, I had to use a 100 ohm resistor to get a 1 meter range... The IR Led must be wired to D2 Pin. I hope some people here will be able to test this... Let me know how it works for you guys...

https://github.com/maehw/BrickLines from @maehw is a solution already but at the moment it talks to interface A through an arduino. (Which I find already very simple and cheap). I guess it could be adapted to this new interface when its protocol becomes avail...

Very cool little board indeed. I cannot find any references to Interface A into your BlockLogo: https://github.com/openbrickproject/BrickLogo/tree/main In your video I see v0.11.2 which correspond to the release... Did you release or make the Interface A driver public yet?

In version: Version: 2026-05-20-0052 New WeDo 2.0 hub support: The following example will change the color of the WeDo2 LED randomly every time you press on the WeDo green button (short press) Another example for the Distance and Tilt Sensors: It only supports the WeDo 2.0 Sensors and simple motor that came with the set. There is a piezo inside the WeDo 2.0 hub but I find it almost inaudible (at least for me), so I did not implement it. I can add it if someone realy want it in blockly...

In version: 2026-05-17-2324 I improved the tilt block that works for BOOST and Technic hub internal tilt sensors (Choose port "TILT") (Boost does not have axis Z). I will add soon the Accel and Gyro and Gesture blocks (Technic Hubs)... I'm not too sure about the values they give. Accelerometer give mG (milli-G) that gives a number that could be used for the tilt but I prefer the Tilt block as it give Degree of tilt... Gyro gives DPS (Degree Per Second) so I think it must detect moving or accelerating, not sure yet... From what I can find about it, they use BLE (BLE use 2.4 ghz). They did not make their protocol public but there might be people that have done some reverse engineering etc... I'm glad to know there are other alternatives but I will put this in the very bottom of my todo list for the moment.

Thank you very much for all this information and link to your work. I just found out today about the existence of Lego Dimensions... And I saw some toy pads not too expensive on marketplace around my location. I will certainly try to add support for this in Lego Blockly. Thanks also to @Toastie to bring this up...

I finally got a Techinc control+ hub with one XL and one L motors. It seems to work with Lego Blockly out of the box with all the motor blocks. But technic hub has new internal sensors to handle that I have to take care off... Stay tune for more...

I had to search for what is CaDA... If I understand well, it is non lego bricks company... I had no idea who they are... For the moment, I have enough only with Lego devices :-) Wow, I never heard of this... And after some search, I see that LEGO Dimensions pad are for Game console like WII, XBOX, PS4 etc... So they have different protocol (and cable ?) I would guess according to which console you have?