treczoks

Eurobricks Vassals
  • Content count

    25
  • Joined

  • Last visited

About treczoks

Spam Prevention

  • What is favorite LEGO theme? (we need this info to prevent spam)
    Creator
  • Which LEGO set did you recently purchase or build?
    60179

Profile Information

  • Gender
    Male
  • Location
    Königswinter
  • Interests
    LEGO, Electronics

Extra

  • Country
    Germany

Recent Profile Visitors

60 profile views
  1. treczoks

    Powered Up - A tear down...

    That is my problem at the moment, too. Train front: First motor and white lights. Train rear: Second motor and red lights. And the sensor?
  2. treczoks

    Powered UP to Power Functions adapter

    Now all we need is an affordable source for the PoweredUp! Cable/Connector...
  3. treczoks

    Powered Up - A tear down...

    Well, just move the smart part elsewhere. I'm currently working on a project where I use the new PoweredUp! train parts, and I intend to put the brain in a RaspberryPi. The remote talks to the RPi, which in turn talks to the SmartHubs on the train. Problem solved.
  4. treczoks

    Documenting the LEGO PoweredUp! System

    I know that, I was talking about a logic analyzer for work, not for home. Maybe I'll get one of the smaller Saleae for home one day, though. I'm not sure if they will take us in. They seem to do open source things, but it looks like they are more aimed at sociological/political work. But thanks for the link, I'll investigate further. The other way would be to get a professionally hosted wiki, and my web hoster seem to offer such things for ~€5-10 per month, which I would be willing to invest. Bt if I get a good free solution, why not. One of the key issues, though, would be what wikia version and which add-ons they offer.
  5. treczoks

    Documenting the LEGO PoweredUp! System

    Of course. From that start point I would have used an oscilloscope, too, just to get an idea what is happening. The logic analyzer is still stuck in the budget pipe... And we can easily get everything under one hood, hardware tear downs, wired communication, wireless communication, even frameworks and libraries and their documentation. I know one can start a wiki-based project on sites like wikia, but I have not yet investigated how this all works. What I'm not going to do is host a server and run my own wiki engine there - I've had a wiki in my home network for test purposes, and it was a pain to keep up with the target system, well, at least back then. So I'll have to look for a turnkey solution, somehow. I'm not sure about the costs involved, either. No, that is not my intention. I use SVN at work for the software and documentation I write, but my documentation project uses the odt file only as a temporary measure. It is basically my digital lab book. With all the different sources, and different areas of interest and expertise, we'll probably need a wiki. I'll add this to a list of questions I'll have to deal with for t his project. At the moment (as in until and including next Tuesday) I'm busy workwise. But I hope I then get a bit of breathing room until January so I can deal with the color sensor, maybe even the Batmobile motors, document all this, and maybe, just maybe, even building something again...
  6. treczoks

    Documenting the LEGO PoweredUp! System

    At the moment, the document is in an intermediate stage: I'm still researching the whole issue, and the whole research results are collected in one .odt file. This is neither a perfect, nor a permanent solution. But it has become clear to me that we need to bring this documentation thing to a whole new level on the long run, in a way that allows for cooperation. One solution would be a wiki, maybe with limited write access for a certain group of people only. I've done some wiki writing, so it would be no problem to turn my findings into a wiki. But then we need other people to contribute what they found on devices they have (and I don't). And it has to be checked and double checked - basically peer reviewed like proper scientific research.
  7. treczoks

    Documenting the LEGO PoweredUp! System

    That would be something I wanted to do in the future, but with a different approach: Here I would just have taken a SoC, maybe an arduino, and have him take care of this. If it is "just" a serial, then programming a signal analyzer might be a bit much. And yet another github repository... I think it is time to find something better than github for documenting all this. There now is a bunch of githubs, all different, caring about one product family, with varying degrees of accuracy and being current (or not...)
  8. That question is still open. There is a node.js thing for all those devices by Mr Hobbles that looks good, but I'm not really into these typescript things. I thought about using python for this, but I'm still looking for the right protocol stack. If all else fails, fallback is always c/c++... I originally thought about getting the four best discernible colors, and let them each represent two bits, so, with a starter code (a fifth color) thrown in for good measure. With this, I could e.g. easily do 14 bits over one piece of track. Well, I'd be happy with 6 or 8 bits, though. Which should be more than enough for encoding all the track blocks for a layout. One big question is if the sensor is fast enough for a train at a reasonable speed.
  9. treczoks

    Documenting the LEGO PoweredUp! System

    Not necessarily. I still prefer SVN.
  10. Ah, OK. When they use IR to measure distance, and 10 is the maximum, then reading of 0a for black makes sense. Do I understand this correctly that the LEDs cycles through R/G/B and the sensor only measures brightness/reflection? If the LEDs cycle through several different colors, does the reflected light ... well ... reflect the average value? Looks like I really have to start working on a program instead of dealing with the gatttool shell to provide a bit of filtering. At the moment I'm not sure if the best way to encode a certain amount of information on the rails is using a set of multicolored tiles and let the LED color-cycle, or use a barcode-like system with only two colors (or maybe a third to indicate a start/attention signal).
  11. The Boost color- and distance sensor arrived, and was immediately put to test. According to Jorges document, I activated the sensor with [90:84:2B:05:B1:C6][LE]> char-write-req 0e 0a004101080000000001 So with sensor mode 08 (The 0a004101080000000001), I should get messages like 08 00 45 <PORT> <COLORCODE> <HIGHDISTANCE> ff <LOWDISTANCE>. and it spewed a lot of messages like Notification handle = 0x000e value: 08 00 45 01 05 01 ff 02 Notification handle = 0x000e value: 08 00 45 01 03 01 ff 02 Notification handle = 0x000e value: 08 00 45 01 05 01 ff 02 Notification handle = 0x000e value: 08 00 45 01 03 01 ff 02 Notification handle = 0x000e value: 08 00 45 01 05 01 ff 02 Notification handle = 0x000e value: 08 00 45 01 05 01 ff 02 Notification handle = 0x000e value: 08 00 45 01 03 01 ff 02 Looks good, but some things are really off here. According to the BOOSTreveng docu, the distance should be something like "Inch" and "Partial Inch" for the <HIGHDISTANCE> and <LOWDISTANCE> readings. But I get values that don't really match this... My setup: I have installed the sensor in a dummy train engine, pointing down. My "color tags" are tiles 2x2 on the sleepers, and the distance between the front of the sensor and the sensor and the tile is one plate. Other readings would be a dark bluish grey sleeper with no tiles on it at 2 plates distance, and the floor (light wood) at three plates distance. Between the sleepers, I get a reading (last four bytes) of 0a 01 ff [08..09] - White (which is OK for the light floor), but one inch and something distance? On a sleeper, I get 03 04 ff [02..03] - Blue, but four inches? And sometimes I get even color 07, yellow. On the red tile, I get 09 00 ff 07, on the yellow tile 07 00 ff [09..0a], on the blue tile 03 00 ff [01..02], on the green tile [05|00] 01 ff 02, on the black tile 00 0a ff [01..02], and on the white tile 0a 00 ff 09. So the colors are good, except for the green, which is a bit shaky, but the supposed distance values make absolutely no sense. I also tried mounting the sensor a bit higher, but the results are similarly off. Could this be due to the short distance? At the moment, my project idea does not look that good - I need not only see one color, but read a "string" of different tiles encoding a number, but it seems to be impossible to get a decent reading. Or the values in the notifications mean something entirely different... Could anybody who has worked with the sensor enlighten me?
  12. treczoks

    Switches

    What I've seen of 3d-printed parts looks way too bad with regards to the surface structure, IMHO.
  13. treczoks

    Documenting the LEGO PoweredUp! System

    OK, I just asked - I can take the department's good power supply home for the weekend. I can then feed the Handset and the Smart Hub with whatever voltage I like, and get good readings on voltage and current. I'll make a measured series for both devices, especially to get them into low power conditions, and see what happens. So either I'll find a good formula over the weekend, or I will just drop the list of readings on the net for the world to figure it out.
  14. treczoks

    Documenting the LEGO PoweredUp! System

    That may be the key - the Boost motor has its own processor, and communicates via serial with the Smart Hub. I would not be surprised if the Smart Hub only had one UART to spare, and gets into a badly handled scheduling conflict.
  15. treczoks

    Documenting the LEGO PoweredUp! System

    I definitely am. And I already found some oddities. You claim in your source that the "power level" delivered from port 3b on the Handset and port 3c on the Smart Hub is (n/4096*100)% This does not really relate to what I measured: Handset reading from port 3B: 0X0b50=2896 => According to your formula ~70%. While my voltmeter might not be the best, I'd still say that 5.98V (of 6V) is a bit better than 70% Smart Hub reading from port 3C: 0x0d50=3408 => According to your formula ~83%. Measured voltage: 8.58V (of 9V). A bit closer, but no cigar. So either the formula or the readings are off. I don't know which, but at the moment I would not bet important body parts on the (n/4096*100)% formula. :-) And no, I don't have a solution for those readings, either. I suspect that the truth is a bit more complex, but for that I would need some more readings. Where did you get this information about the supposed voltage level and the current readings on port 3C of the Handset? Another interesting information I got from your source is the virtual port 57, but that seems only be available with two identical motors attached to the Smart Hub. Looks like I have to pillage another motor to test this - it it even works with two train motors. Well, at least I now know how typescript looks like. And I'm amazed by the amount of information you must have had about the hardware to write all this.