• Sign In
  • Sign Up
    Loading ...
View All Updates Mark All Read
  • Home
  • Videos
  • Albums
  • Groups
  • Forum
  • Events
  • About
  • Store

Member Info

  • Profile Type: Regular Member
  • Profile Views: 5,773 views
  • Friends: 34 friends
  • Last Update: Wed at 3:31 PM
  • Joined: June 19, 2014
  • Updates
  • Info
  • Friends(34)
  • Albums(1)
  • Recently Edited Pages(6)
  • Links(4)
    • Forum Posts (169)
    • Videos (4)
    More +

Updates

The post was not added to the feed. Please check your privacy settings.
  • Tamás Fábián
    Tamás Fábián replied to a topic in the forum Support:
    Hello Hambone,
    we managed to reproduce the problem and working on a fix.
    Cheers,
    Tamas
    • Wed at 3:31 PM
  • Tamás Fábián
    Tamás Fábián replied to a topic in the forum Support:
    Hello everyone,
    a couple of you complained that no SBricks could be seen after upgrading the SBrick app and/or Simple Control.
    One of our collegues had the same issue, and we successfully reproduced the problem.
    The issue were finally resolved by...  more
    Hello everyone,
    a couple of you complained that no SBricks could be seen after upgrading the SBrick app and/or Simple Control.
    One of our collegues had the same issue, and we successfully reproduced the problem.
    The issue were finally resolved by changing certain settings on the phone.
    The SBrick apps need permission to access the device's location, and the location services must be enabled. This is a limitation of the Android OS and this is so to protect your privacy.
    Since the list of Bluetooth devices correlates with the physical location of the device, all application need to have permission to access location services.
    So, If you suddenly unable to see your SBrick on your device, please follow these steps (the name of the menu items and settings might be different on different devices):
    1. Go to "Settings" and then "Apps & notifications". Choose "SBrick" and/or "SBrick Simple Control". Open "Permissions", and make sure that "Location" is enabled.
    2. Got to "Settings" and then "Security &...    less
    • Nov 20
  • Tamás Fábián
    Tamás Fábián replied to a topic in the forum Support:
    Hello Hypershadow,
    could you take a video of your problem? It would help a lot in finding the issue.
    Thank you.
    • Apr 5
  • Tamás Fábián
    Tamás Fábián replied to a topic in the forum Support:
    Hello,
    yes, the input is analog. The SBrick's C1 and C2 pins on each port can be used to measure voltage. By default, these are tied to the battery voltage (Vcc) / 2 with a resistive divider.
    You can apply any voltage on these pins between 0V and Vcc.
    To...  more
    Hello,
    yes, the input is analog. The SBrick's C1 and C2 pins on each port can be used to measure voltage. By default, these are tied to the battery voltage (Vcc) / 2 with a resistive divider.
    You can apply any voltage on these pins between 0V and Vcc.
    To take measurements, use commands "2C Set up periodic voltage measurement", and "2E Set up periodic voltage notifications" or "0F Query ADC".
    https://social.sbrick.com/wiki/view/pageId/11/slug/the-sbrick-ble-protocol
    The input voltage is dropped through a 1:10 voltage divider. The reference voltage is 1.24V, and the resolution is 12 bits, but you'll get a 16 bit number back.
    Basically, you have to take the number you get from the SBrick, multiply it by 1.24 (the reference voltage), and again with 11 (because of the voltage divider), and divide the the result with 2^15 (12 bit resolution, stored in MSB, first bit is essentially a sign), to get a voltage value.
       less
    • Mar 29
  • Tamás Fábián
    Tamás Fábián replied to a topic in the forum Support:
    Hello Ray,
    the absolute maximum value is 11.8 Volts. This comes from the datasheet of the integrated circuit we use for driving the outputs (DRV8833). The safe operating limit is 10.8 for the same IC.
    Having said that, we managed to overvolt SBricks up...  more
    Hello Ray,
    the absolute maximum value is 11.8 Volts. This comes from the datasheet of the integrated circuit we use for driving the outputs (DRV8833). The safe operating limit is 10.8 for the same IC.
    Having said that, we managed to overvolt SBricks up to 14 volts and never damaged a single one. However, do not take this as a recommendation. It's a bit like overclocking / overvolting CPUs and memory modules in a PC. Be aware that overvolting your SBrick beyond the absolute maximum voids your warranty.
    What you can do is:

    Play safe, and don't run the SBrick over 10.8V
    Accept some extra heating and reduced safety margin, and go near the absolute maximum limit of 11.8V
    Accept the chance of immediately and permanently damage or severely reduce the lifespan of your SBrick, and run it over the absolute maximum of 11.8V.
    Use a 3-cell Lithium Iron Phospate (LiFePo4) battery. With a maximum cell voltage of 3.65V it just barely goes over the recommended operating limit of 10.8V, and stays well...    less
    • Mar 18
  • Tamás Fábián
    Tamás Fábián Hello everyone, we've updated the SBrick BLE Protocol page. From now on the protocol description is available in PDF format.
    The SBrick BLE protocol - Wikis Profile - SBrick Community
    This is Wikis Profile page. Social network site built around SBrick, the smartphone remote control device for LEGO® creations
    • Mar 18
  • Tamás Fábián
    Tamás Fábián replied to a topic in the forum Suggestions:
    Yes, by default the SBrick apps lock the motors in neutral position. We're considering including this as an optional feature to allow free wheeling.
    Timber Brick said:
    I have similar observations about neutral sensitivity.  We fight battle bots with...  more
    Yes, by default the SBrick apps lock the motors in neutral position. We're considering including this as an optional feature to allow free wheeling.
    Timber Brick said:
    I have similar observations about neutral sensitivity.  We fight battle bots with skid steer control.  Recently, we've been adding two speed transmissions.  At high speeds, control skid steering is difficult.  Two reasons.  1.  When the SBRICK is in the neutral off position, it locks the motor.  The result is an out of control sliding spin.  I believe there is a way for the h-bridge motor controller to allow it to coast instead.  That mode would be most helpful.  2. The neutral range is tight and linear.  As the previous poster just suggested, an exponential modulation would be very helpful, allowing a wider neutral range.

       less
    • Mar 7
  • Tamás Fábián
    Tamás Fábián replied to a topic in the forum Suggestions:
    Hey Ray, good idea, thank you. We're going to investigate the possibility of including this feature in the apps & profile designer.
    Ray Simon said:
    Feature Request: Reduce steering servo control sensitivity.
    I fly RC airplanes and a feature that is very...  more
    Hey Ray, good idea, thank you. We're going to investigate the possibility of including this feature in the apps & profile designer.
    Ray Simon said:
    Feature Request: Reduce steering servo control sensitivity.
    I fly RC airplanes and a feature that is very helpful is called "Exponential". The most obvious use here would be steering of an RC vehicle. The benefit of Expo is that the steering is less sensitive around the neutral point of the control stick which gives great control for making fine adjustments left or right of neutral. Then the sensitivity is higher as you get closer to the end points to allow you to jam around corners.
    I use a Nimbus gamepad controller paired to an iPhone. I find that when using steering with the PF servo that a tiny bump on the control stick gives a big change in steering direction. Essentially my servo which has the capability of 7 positions in either direction is really acting as a 3 position turning servo (neutral, approx 50% turn, full turn). Fine adjustments in...    less
    • Mar 7
  • Tamás Fábián
    Tamás Fábián replied to a topic in the forum Support:
    Hello Heiko,
    there's a bug in the code that handles voltage measurement setup readback. As a workaround, try "2d00" instead of "2d" (This will stop working once we fixed this bug).
    To measure the voltage, use channel "01", that's the "C2" lead on port...  more
    Hello Heiko,
    there's a bug in the code that handles voltage measurement setup readback. As a workaround, try "2d00" instead of "2d" (This will stop working once we fixed this bug).
    To measure the voltage, use channel "01", that's the "C2" lead on port "A".
    Cheers,
    Tamas  
    • Jan 24
  • Tamás Fábián
    Tamás Fábián replied to a topic in the forum Support:
    Hi Michel,
    no, unfortunately the BLED112 dongle does not support A2DP, and also doesn't work well as a generic purpose Bluetooth dongle.
    The thing you should watch out for is "Bluetooth Smart" or "Bluetooth Low Energy" support. To meet your needs, the...  more
    Hi Michel,
    no, unfortunately the BLED112 dongle does not support A2DP, and also doesn't work well as a generic purpose Bluetooth dongle.
    The thing you should watch out for is "Bluetooth Smart" or "Bluetooth Low Energy" support. To meet your needs, the dongle should also support "BR/EDR" (basic rate / enhanced data rate). These dongles are often called "dual mode".
    One such dongle would be Laird BR851 ( https://hu.mouser.com/new/laird/laird-bt851-bluetooth-adapter/ )
    An other one is LM Technologies LM506 ( https://www.lm-technologies.com/product/bluetooth-usb-adapter-4-0-dual-mode-class-2-lm506/ )
    Cheers,
     
    Tamas  less
    • Jan 24
  • Tamás Fábián
    Tamás Fábián replied to a topic in the forum Support:
    Hello Grzegorz,
    what do you mean by "frame format"? Could you please re-phrase the question?
    Grzegorz Bladocha said:
    When connecting with another bluetooth + arduino module to enable channel A which frame formatsend?

     
    • Jan 24
  • Tamás Fábián
    Tamás Fábián replied to a topic in the forum Support:
    Hi,
    the LEGO M motors are notoriously hard to drive. Try them with LEGO's own V2 IR receivers, and you'll likely get the same results.
    The problem with M motors is they have a large capacitor in parallel with the actual brushed DC motor in...  more
    Hi,
    the LEGO M motors are notoriously hard to drive. Try them with LEGO's own V2 IR receivers, and you'll likely get the same results.
    The problem with M motors is they have a large capacitor in parallel with the actual brushed DC motor in them. 
    When the DRV8833 motor driver chip in the SBrick Plus tries to charge this capacitor, it may go into overcurrent protection mode, and cut the PWM signal.
    This problem is not always present, most M motors and most SBricks work together just fine. If you can, please try other M motors and SBricks.
    The problem gets worse as the M motors need to supply more torque. If nothing seem to work, try using a thin silicon lubricant on the moving parts of your creation to reduce friction. You may try to apply lubrincant onto the planetary reduction gear inside the M motor, but you'd need to take it apart.
    (If nothing helps, and you _are_ willing to take the M motor apart, you can remove the capacitor, but this obviously isn't a real solution for most customers...    less
    • November 23, 2018
  • Tamás Fábián
    Tamás Fábián replied to a topic in the forum Support:
    Hello everyone,
    I'm sorry to hear your SBrick failing.
    We already have an idea about the cause of this problem. We need to take a look at the faulty pieces as they arrive.
    If the findings confirm our theory, we'll need to issue a firmware upgrade...  more
    Hello everyone,
    I'm sorry to hear your SBrick failing.
    We already have an idea about the cause of this problem. We need to take a look at the faulty pieces as they arrive.
    If the findings confirm our theory, we'll need to issue a firmware upgrade and change what the SBrick's doing right after it's powered on.
    Until then please do not leave your creations powered on if there's a possibility of the battery losing all charge during operation. If you see a battery pack failing, turn your creation off immediately. You sould run SBrick with fresh / fully charged batteries.
    Your SBricks are probably permanently damaged, please contact info@sbrick.com and ask for a replacement if you didn't already do.
       less
    • November 23, 2018
  • Tamás Fábián
    Tamás Fábián replied to a topic in the forum Support:
    Hi Derek,
    unfortunately you can't combine the current on the different pins. You can feed at most 3 amps into SBrick, othervise you risk melting the plastic around the metal contacts.
    It is _technically_ possible to drive SBrick with a LiPo pack, but...  more
    Hi Derek,
    unfortunately you can't combine the current on the different pins. You can feed at most 3 amps into SBrick, othervise you risk melting the plastic around the metal contacts.
    It is _technically_ possible to drive SBrick with a LiPo pack, but please only do this if you know what you're doing. There is no fuse in SBrick, and a short circuit with a LiPo pack can drive dozens of amps through it potentially causing fire or even an explosion.
    LEGO battery packs come with proper current limiting, LiPo packs usually don't.  less
    • November 23, 2018
  • Tamás Fábián
    Tamás Fábián replied to a topic in the forum Support:
    Hello!
    The protocol over BLE is described here: https://social.sbrick.com/wiki/view/pageId/11
    You can use the gatttool command to write characteristics, and so to use the DRIVE command, or to use the Quick Drive method.
    One caveat is the...  more
    Hello!
    The protocol over BLE is described here: https://social.sbrick.com/wiki/view/pageId/11
    You can use the gatttool command to write characteristics, and so to use the DRIVE command, or to use the Quick Drive method.
    One caveat is the watchdog.
    The purpose of the watchdog is to prevent a model running away is your phone (or other devices) is frozen, so there is a connection (the so the model won't stop), but the application stops sending commands.
    The watchdog is a timer that starts whenever there is a channel that's DRIVE-ing or BRAKE-ing. In these cases, the application MUST send a command in every second, or the connection will be terminated. Sending a "DRIVE 0" to all channels disables the watchdog.  less
    • September 4, 2017
  • Tamás Fábián
    Tamás Fábián replied to a topic in the forum Support:
    Hello Andrew,
    this is probably SBrick's overcurrent protection in action. It's a sign of trying to use SBrick near it's current limit.
    Don't use SBrick near it's current limit for too long, it will overheat, and the thermal protection will disable the...  more
    Hello Andrew,
    this is probably SBrick's overcurrent protection in action. It's a sign of trying to use SBrick near it's current limit.
    Don't use SBrick near it's current limit for too long, it will overheat, and the thermal protection will disable the motors for several seconds / minutes. Doing this often will adversely affect the SBrick's lifetime.
    I suggest using more motors instead of a single big one. I know this could be a hassle and/or more expensive, but you'll get reliable operation and happy, cool SBrick ;)
    Cheers,
    Tamas  less
    • April 4, 2017
  • Tamás Fábián
    Tamás Fábián replied to a topic in the forum Support:
    Hello Kees,
    The 5th channel is indeed the the "LED identification on-off" channel.
    It's usage with quick drive is undocumented, since it's rather convoluted. Use the DRIVE command to turn it off (0) or on (any other value).
    You could use the LED...  more
    Hello Kees,
    The 5th channel is indeed the the "LED identification on-off" channel.
    It's usage with quick drive is undocumented, since it's rather convoluted. Use the DRIVE command to turn it off (0) or on (any other value).
    You could use the LED identification function via quick drive by sending a value 2 to turn it off (!) and 3,4, or greater to turn it on.  
    • March 29, 2017
  • Tamás Fábián
    Tamás Fábián replied to a topic in the forum Support:
    Dear Kees,
    old firmwares don't have the manufacturer specific data record in neither the advertisement, nor the scan response data packet.
    You can recognize these old bricks (beside updating the firmware, obviously :) ) by looking for devices with the...  more
    Dear Kees,
    old firmwares don't have the manufacturer specific data record in neither the advertisement, nor the scan response data packet.
    You can recognize these old bricks (beside updating the firmware, obviously :) ) by looking for devices with the name "SBrick". There are very old pre-production prototypes with the name "SmartBrick".
    To support these, you need to match for names of "SBRICK" or "SMARTBRICK" case insensitive (so "SBrick", "sbrick" and "sbRIck" all match). Since you cannot prevent anyone to name a BLE device "SBrick", you might end up listing and connecting to non-SBrick devices. To prevent confusion and strange errors, check for the remote control service in the GATT database.
    Cheers,
    Tamas  less
    • March 1, 2017
  • Tamás Fábián
    Tamás Fábián replied to a topic in the forum Support:
    Hello Owen,
    you need to subscribe to notifications on the "quick drive" characteristic (489a6ae0-c1ab-4c9c-bdb2-11d373c1b7fb).
    Let me know wether this solves your problem or not.
    Cheers,
    Tamas
    • January 25, 2017
  • Tamás Fábián
    Tamás Fábián replied to a topic in the forum Support:
    Hello Francesco,
    the documentation had an error, the ADC channel numbering changed after version 14.
    The battery reading is on channel 8, the temperature is on 9.
    The full list of channels can be read in the updated documentation:...  more
    Hello Francesco,
    the documentation had an error, the ADC channel numbering changed after version 14.
    The battery reading is on channel 8, the temperature is on 9.
    The full list of channels can be read in the updated documentation: https://social.sbrick.com/wiki/view/pageId/11/slug/the-sbrick-ble-protocol . See section "SBrick Data Records", record 06 "Voltage measurement".  
    • December 8, 2016
  • Tamás Fábián
    Tamás Fábián replied to a topic in the forum Support:
    aaaaaaaaand that is correct. Thank you, the wiki will be updated soon. ;)
    • February 8, 2016
  • István Murvai
    István Murvai is now friends with Tamás Fábián.
    • February 3, 2016
  • Tamás Fábián
    Tamás Fábián replied to a topic in the forum Support:
    (if I do make more sense, I'm gonna update the wiki)
    • February 1, 2016
  • Tamás Fábián
    Tamás Fábián replied to a topic in the forum Support:
    Okay:

    Bit 0 is always the direction bit.
    Braking occures, when the drive value is zero, regardless of direction. 0x00 and 0x01 are both braking...  more
    Okay:

    Bit 0 is always the direction bit.
    Braking occures, when the drive value is zero, regardless of direction. 0x00 and 0x01 are both braking commands.
    Freewheeling occures when the drive value is the least non-zero value regardless of the direction. 0x02 and 0x03 are both free wheeling.
    If all non-direction bits are ones, then apply full drive. 0xFF and 0xFE are all full-drive commands in reverse and forward respectively.
    All other values are equal with a drive command with power X & 0xFE where X is a value written to the quick drive characteristic, and "&" is a bitwise AND operation.

    do I make any sense now? :)
       less
    • February 1, 2016
  • Tamás Fábián
    Tamás Fábián replied to a topic in the forum Support:
    Hello everyone,
    thank you all for the reports.
    We're working on the issues and improvements, and going to release a new version this...  more
    Hello everyone,
    thank you all for the reports.
    We're working on the issues and improvements, and going to release a new version this week.
     
    We're going to buy a couple of new devices for testing including many of the problematic ones to be able to hunt those bugs down.
     
    Thank you for your attention :)  
    • January 26, 2016
  • Tamás Fábián
    Tamás Fábián replied to a topic in the forum Support:
    ...the wiki page was also updated. Check it out!
    • January 19, 2016
  • Tamás Fábián
    Tamás Fábián replied to a topic in the forum Support:
    Hello Peter,
    Convert LE bytes to integer (C/JAVA): int adc = (((int)low) & 0xff) + ((((int)hi) & 0xff) * 256) Where "low" is the byte at the lower memory address, and hi is the byte at the higher memory address.
     
    Voltage is calculated as:...  more
    Hello Peter,
    Convert LE bytes to integer (C/JAVA): int adc = (((int)low) & 0xff) + ((((int)hi) & 0xff) * 256) Where "low" is the byte at the lower memory address, and hi is the byte at the higher memory address.
     
    Voltage is calculated as: (double)adc / 16.0 * 1.22 / 2047.0 * 11.0;
     
    Temperature is calculated as: (double)adc / 145.0067 * 1.22 - 160.0;  
    • January 19, 2016
  • Tamás Fábián
    Tamás Fábián replied to a topic in the forum Support:
    Hello,yes, bit 0 is the direction. A "0" means braking, 1 means freewheeling. Bits 1-7 can be set to control the drive level in each driection, and yes, there are 127 values from 1-127. (Value "0" either brakes or just "doesn't go" depending on the...  moreHello,yes, bit 0 is the direction. A "0" means braking, 1 means freewheeling. Bits 1-7 can be set to control the drive level in each driection, and yes, there are 127 values from 1-127. (Value "0" either brakes or just "doesn't go" depending on the direction bit). Value 127 on the bits 0-7 means "full drive" in each direction (uninterrupted DC voltage on the channel).  
    • January 13, 2016
  • Tamás Fábián
    Tamás Fábián replied to a topic in the forum Support:
    Thank you Klaus for the info.
    It means your hardware and OS is complatible with SBrick, and the problem is somewhere in the app.
    Now try "SBrick Simple Control" from Google Play. Does that scan your SBrick OK?
    • December 12, 2015
View More
Loading ...

Info

Personal Information

  • First Name Tamás
  • Last Name Fábián
  • Gender Male
  • Birthday November 17, 1983

Personal Details

  • About Me Hardware & firmware developer @sbrick.com

Friends

  • Lénárd Pásztor Did you know, that the SBrick app supports hardware gamepads? Check out the porfile/port settings section and tap the gamepad icon.
  • Andras Barath
  • Nandor Ladi
  • Aron Kurucz Guess what's in the making. http://gfycat.com/TintedAllItalianbrownbear
  • Zsolt Szrapkó Profile Designer 1.4.96 is out now, with new addition to the Output values: - Auto Brake: Now you can set the control's behaviour for the release. - Output Curve: Set the sensibility of the slider and the joystick.
Previous
Next

Albums

  • Wall Photo­s 1 photo

Previous
Next

Recently Edited Pages

  • User guide for SBrick

    Create by Lénárd Pásztor | January 9, 2015 | Last updated by Zsolt Szrapkó November 18, 2015 (view change)

    » User guide for SBrick

    Notes There is a LED on the SBrick which has been programmed to light up briefly when the SBrick is powered up. Unfortunately the Quick Setup Guide in the packaging states that the LED should light up continuously. This was a typo on our part, so please ignore it.   Requiements To power you...

  • Android "SBrick stops working after OTA" workaround

    Create by Tamás Fábián | August 13, 2015 | Last updated by Tamás Fábián August 17, 2015 (view change)

    » Support » Android "SBrick stops working after OTA" workaround

    After an OTA firmware upgrade, most devices won't work with the SBrick. Some devices can connect, but the controls don't work, some devices don't even connect.This is because Android won't refresh the list of services offered by the SBrick, and new firmwares tend to change that list. Using the old ...

  • The SBrick BLE protocol

    Create by Tamás Fábián | January 9, 2015 | Last updated by Tamás Fábián April 7, 2015 (view change)

    » Developers area » The SBrick BLE protocol

    Download the latest verstion of the SBrick Protocol's documentation here.

  • Software development roadmap for the SBrick application

    Create by Lénárd Pásztor | January 9, 2015 | Last updated by David Haja May 8, 2015 (view change)

    » Developers area » Software development roadmap for the SBrick application

    iOS wizard auto profile update new control schema that supports gyro, speed-o-meters, linked sliders, break pedal, etc... social functions security kids mode apple watch integration (Push) notifications: new firmware, new profile, brick shared with the user Share brick with friends (share...

  • Hardware and firmware versions

    Create by Tamás Fábián | January 9, 2015 | Last updated by Tamás Fábián January 9, 2015 (view change)

    » Developers area » Hardware and firmware versions

    Both hardware and software versions are described using a major and a minor version number separated by a point. The first commercial hardware version of SBrick is 4.0: 4 is the major, 0 is the minor version. This SBrick comes with a factory firmware version 4.0 too. A firmware image only compatib...

  • Developers area

    Create by Lénárd Pásztor | January 9, 2015 | Last updated by Lénárd Pásztor January 9, 2015 (view change)

    » Developers area

    Our goal is to bring as much out of the SBrick as possible. We have deliberately made the SBrick hackable: the communication protocol is open and has been created to allow the firmware to updated from our application. We will help you to create custom firmware and upload it with our application in ...

View All »

Links

  • The SBrick BLE protocol - Wikis Profile - SBrick Community
    This is Wikis Profile page. Social network site built around SBrick, the smartphone remote control device for LEGO® creations
  • SBrick - Smart way to control all your LEGO® Creations by Mark Bollobas — Kickstarter
    Mark Bollobas is raising funds for SBrick - Smart way to control all your LEGO® Creations on Kickstarter! SmartBrick is the next level in remote controlling your LEGO®. Build more, play more like never before.
  • https://social.sbrick.com/public/app/android/SBrick_0.0.9.4.apk
    https://social.sbrick.com/public/app/android/SBrick_0.0.9.4.apk
  • SBrick Community - Design ideas
    Social network site built around SBrick, the smartphone remote control device for LEGO® creations Dear Community, we designed SBrick as carefully as one could be to match your needs, but as more and more people getting know SBrick we receive more and mor
Previous
Next

Forum Posts

  • December 4, 2019 3:31 PM CET
    in the topic Multiple Motion Sensors per Sbrick in the forum Support
    Hello Hambone, we managed to reproduce the problem and working on a fix. Cheers, Tamas
  • November 20, 2019 4:52 PM CET
    in the topic SBrick Android App in the forum Support
    Hello everyone, a couple of you complained that no SBricks could be seen after upgrading the SBrick app and/or Simple Control. One of our collegues had the same issue, and we successfully reproduced the problem. The issue were finally resolved by changing certain settings on the phone. The SBrick apps need permission to access the device's location, and the location services must be enabled. This is a limitation of the Android OS and this is so to protect your privacy. Since the list of Bluetooth devices correlates with the physical location of the device, all application need to have permission to access location services. So, If you suddenly unable to see your SBrick on your device, please follow these steps (the name of the menu items and settings might be different on different devices): 1. Go to "Settings" and then "Apps & notifications". Choose "SBrick" and/or "SBrick Simple Control". Open "Permissions", and make sure that "Location" is enabled. 2. Got to "Settings" and then "Security & lock screen". Choose "Location" and make sure "Use location" is on. So again, you have to give the application permission to access location AND make sure that location services is actually enabled. Feel free to give to give us feedback on this. Cheers, Tamas
  • April 5, 2019 3:20 PM CEST
    in the topic Problem with power consumption in the forum Support
    Hello Hypershadow, could you take a video of your problem? It would help a lot in finding the issue. Thank you.
  • March 29, 2019 2:32 PM CET
    in the topic SBrick+ input characteristics in the forum Support
    Hello, yes, the input is analog. The SBrick's C1 and C2 pins on each port can be used to measure voltage. By default, these are tied to the battery voltage (Vcc) / 2 with a resistive divider. You can apply any voltage on these pins between 0V and Vcc. To take measurements, use commands "2C Set up periodic voltage measurement", and "2E Set up periodic voltage notifications" or "0F Query ADC". https://social.sbrick.com/wiki/view/pageId/11/slug/the-sbrick-ble-protocol The input voltage is dropped through a 1:10 voltage divider. The reference voltage is 1.24V, and the resolution is 12 bits, but you'll get a 16 bit number back. Basically, you have to take the number you get from the SBrick, multiply it by 1.24 (the reference voltage), and again with 11 (because of the voltage divider), and divide the the result with 2^15 (12 bit resolution, stored in MSB, first bit is essentially a sign), to get a voltage value.  
  • March 18, 2019 3:06 PM CET
    in the topic Max current rating in the forum Support
    Hello Ray, the absolute maximum value is 11.8 Volts. This comes from the datasheet of the integrated circuit we use for driving the outputs (DRV8833). The safe operating limit is 10.8 for the same IC. Having said that, we managed to overvolt SBricks up to 14 volts and never damaged a single one. However, do not take this as a recommendation. It's a bit like overclocking / overvolting CPUs and memory modules in a PC. Be aware that overvolting your SBrick beyond the absolute maximum voids your warranty. What you can do is: Play safe, and don't run the SBrick over 10.8V Accept some extra heating and reduced safety margin, and go near the absolute maximum limit of 11.8V Accept the chance of immediately and permanently damage or severely reduce the lifespan of your SBrick, and run it over the absolute maximum of 11.8V. Use a 3-cell Lithium Iron Phospate (LiFePo4) battery. With a maximum cell voltage of 3.65V it just barely goes over the recommended operating limit of 10.8V, and stays well below the absolute maximum. Ray Simon said: Thanks Lenard! I have a follow up question: Is it safe to connect a fully charged three-cell LiPo directly to the SBRICK Plus? I'm sure when the battery levels off to nominal voltage of 11.1V it is safe. The question is if the initial voltage of 12.6V will harm the SBRICK. I would like to use my hobby-grade 3S LiPo batteries with the SBRICK Plus. These are standard three-cell LiPo used for RC cars, airplanes, helicopters, etc. The behavior of these batteries is that at full charge, the voltage is 12.6V without load. After load is applied and some current draw, the voltage drops and levels off to "operating" or "nominal" voltage which is 11.1V. I have been researching other options to use my 3S LiPo batteries and you can get a DC-to-DC mini voltage regulator, but generally the output must be at least 1.5V below the input voltage, which means it would need to be set to about 9V to be safe to handle the LiPo as the voltage drops while it is discharged. This is possible but requires more complexity and equipment. It would be much simpler if we can connect the LiPo directly to the SBRICK. Thanks for your support!   This post was edited by Tamás Fábián at March 18, 2019 3:06 PM CET
Previous
Next

Videos

  • 1:46
    LEGO® Technic 42030 Volvo on Trial track - controlled by SBrick
    By Tamás Fábián
    920 views
  • 0:09:44
    SBrick, Bluetooth controller for your LEGO creations, final version: Unboxing and Review
    By Tamás Fábián
    942 views
  • 0:06:22
    Sbrick in Windows Phone (Short app review)
    By Tamás Fábián
    867 views
  • 0:21
    Star Wars - "The Imperial March" by LEGO® motor and SBrick
    By Tamás Fábián
    1587 views
Previous
Next
Copyright ©2019  -  Privacy  -  Terms of Service  -  Contact  - 

 

SmartBrick is carried by Vengit Ltd. LEGO®, the LEGO® logo, the Minifigure®, DUPLO®, the DUPLO® logo, BIONICLE®, the BIONICLE® logo, LEGENDS OF CHIMA®, the LEGENDS OF CHIMA® logo, DIMENSIONS®, the DIMENSIONS® logo, the FRIENDS® logo, the MINIFIGURES® logo, MINDSTORMS®, the MINDSTORMS EV3® logo, MIXELS®, the MIXELS® logo, NINJAGO®, the NINJAGO® logo, NEXO KNIGHTS®, and the NEXO KNIGHTS® logo are trademarks and/or copyrights of the LEGO Group, which does not sponsor, authorize or endorse this web site. ©2018 The LEGO Group. All rights reserved.

Share