treczoks

It would be useful if someone with a BT sniffer could observe the Batmobile communication, then. And if one is doing that, I would not mind to learn the answer to question 9 on the hub about the actual power levels associated with the +-10 speeds on the remote. Well, I posted the document on LAN, too, with the explicit idea that the community team forwards it with all the questions to the developers. I would not even mind if they just sent some half-baked notes - we'll figure it out.

Sorry, no, I don't know any such command. But why don't you just send two commands? The communication is quite fast, fast enough that with all the inertia and the tolerances of a LEGO construction you'll probable never notice a difference. Call me old-fashioned, but I really don't like GIT. I prefer a classical linear document or a hypertext system over GIT with its funny document formats at any given time. A Wiki would be a more agreeable and natural place for such a collection of information. But I don't have one, either.

That was actually the thread where I started. But that thread is going into too many directions at the moment, so I started a new one to get a new focus (one of the problems I see with a linear forum like this instead of a tree-like one). This thread here is just about the BTLE communication of the PoweredUp! system, not about hardware tear downs, battery sizes, or prices for the individual parts.

This post is of interest to members of this forum, too. Link to my post about documenting the LEGO PoweredUp! System in the TrainTech forum. If there is a way to simply cross-post here, I have not yet found it, so I thought a link would be the best option. If I erred, do not hesitate to correct me. If you want to comment on the document, please do so in the TrainTech forum post to keep things neat and tidy. Leg bedre, Christian

Hi! A few days ago I joined to find answers on the communication with the elements of the PoweredUp! train control system. Well, I didn't get a reply, and found the solution myself. Yesterday, I made a reverse engineering session and wrote a document listing all the information I could find - hopefully in a concise way. I also added some questions both about the Handset as well as the Smart Hub. Questions I intend to direct at LEGO, too, via the LEGO Ambassador Network. I want to thank Jorge Pereira of the BOOSTreveng project for helpful pointers about the command structure - The old "I could only see that far because I'm standing on the shoulders of giants" definitely applies here. I will continue my work on this document - I'm waiting for the BOOST color sensor to arrive, and want to get my hands on the motor used in the Batmobile - and if someone here has suggestions or additional information, don't hesitate to contact me. PoweredUp! Documentation The next step will be the design of a going-in-between app, which allows me to control my trains with the PUP Handset, but relayed over a computer (maybe a Raspberry Pi) that does things like drive both motors simultaneously, control the lighting, or react to the readings of the color sensor. UPDATE December 16th, 2018: Expanded the documentation with new findings: Battery power readings and conversion factors, blinking and shutdown thresholds. Document is now Version 0.3

One reason: Smaller case. Another one would be the reason Giottist already mentioned.

I really think that LEGO will do a different "insert" and lid one day for the 9V blocks. It not, someone else probably will.

I learned some more about the Train Handheld! When you enable notifications gatttool -b 00:81:f9:e4:b2:0d --char-write-req --handle=0x0c --value=0100 --listen you will be informed about the Green Button on the handheld, too! Press Green Button: Notification handle = 0x000b value: 05 00 08 02 01 Release Green Button: Notification handle = 0x000b value: 05 00 08 02 00 Notification handle = 0x000b value: 04 00 08 03 Press and hold Green Button: Notification handle = 0x000b value: 05 00 08 02 01 Notification handle = 0x000b value: 04 00 02 30 The first message comes when the Green Button is pressed, the second when the handheld switches off after a few seconds

Hi! I'm new here - I actually just joined to participate in this thread - and I'm having some problems with my attempts to connect to the PUP devices. I want to automate our track layout and train controls, so I thought about the following setup: A Raspberry Pi with a BT dongle talks to the trains, the switch motors and the remotes. Some features of the software would be to automatically connect everything automatically by knowing all involved MAC addresses, limit a trains' speed so it will not fly off the track, run two motors from one remote, or, to be more precise, run both trains from the "train remote", while the "switch remotes" run the switches. Now despite following this thread and reading other sources of documentation, I still cannot properly communicate with the remote control. Maybe someone here can tell me which kind of stupid mistake I made... #!/bin/bash gatttool -b 00:81:f9:e4:b2:0d --char-write-req --handle=0x0f --value=0100 gatttool -b 00:81:f9:e4:b2:0d --char-write-req --handle=0x0e --value=0a00400000100000001 --listen I expected this "test balloon" to give me some readings, but I get the message "invalid handle" on both. Nonetheless, the LED on the remote indicates that it is connected until I end the gatttool. I got the strings for "value" from some posts in this thread, but they didn't mention which handle to use - that I copied off BoostRevenge, but obwiously I didn't do it correctly. So which channels would I need to address to be able to read the buttons on the PUB remote controller, or did I do something fundamentally wrong? EDIT: I think I got it... I made two mistakes: a) I had the wrong handles, and b) my value was lacking a digit. After some research I am now here: #!/bin/bash gatttool -b 00:81:f9:e4:b2:0d --char-write-req --handle=0x0c --value=0100 gatttool -b 00:81:f9:e4:b2:0d --char-write-req --handle=0x0b --value=0a004100000100000001 gatttool -b 00:81:f9:e4:b2:0d --char-write-req --handle=0x0b --value=0a004101000100000001 --listen The first gatttool call enables notifications, the second enables the left keys, the third one the right keys. This gives me results like: Notification handle = 0x000b value: 05 00 45 00 ff Notification handle = 0x000b value: 05 00 45 00 00 Notification handle = 0x000b value: 05 00 45 00 7f Notification handle = 0x000b value: 05 00 45 00 00 Notification handle = 0x000b value: 05 00 45 00 01 Notification handle = 0x000b value: 05 00 45 00 00 Notification handle = 0x000b value: 05 00 45 01 01 Notification handle = 0x000b value: 05 00 45 01 00 Notification handle = 0x000b value: 05 00 45 01 7f Notification handle = 0x000b value: 05 00 45 01 00 Notification handle = 0x000b value: 05 00 45 01 ff Notification handle = 0x000b value: 05 00 45 01 7f Notification handle = 0x000b value: 05 00 45 01 00 05 00 45 <PORT> <VALUE> PORT 00 Left keys, PORT 01 Right keys VALUE 00 No Key, VALUE 01 Plus Key, VALUE 7F Red Key, Value FF Minus Key It also gives me a Notification handle = 0x000b value: 0a 00 47 01 00 01 00 00 00 01 which I have not yet understood.

Hi! My name is Christian Treczoks, I'm member and Ambassador of the RLUG "MBFR - LEGO Modelbaufans Rheinland e.V.", and I finally applied for membership here when I found an thread that I have to participate in... I build about everything with plants and landscapes, and I designed the modular train system of our RLUG, which I'm currently expanding to new heights. Some people might know me for my trees and my plant- and tree-building seminars that I held for some years at LEGO Fanwelt in Cologne. Leg bedre, Christian