Jump to content
View in the app

A better way to browse. Learn more.

Tinkerunity

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

luzik

Members
  • Benutzer seit

  • Letzter Besuch

Posts erstellt von luzik

  1. Geschrieben

    Callbacks are registered only from main process. There are no Callbacks registered from PTC or DC modules. I will try to disable them anyway.

    In main thread I created tf class where I init all TF hardware, then I use tf.ptc as argument for multiprocessing.Process() fork function. Is it ok ? Maybe i should init ptc from within forked process ?

    tf.ssr (SolidStateRelay) work fine in this way.

  2. Geschrieben

    When i run PTC.get_temperature() on my software init stage ..everything works fine! after initing more bricklets, and running some threads PTC.get_temperature throws TIMEOUT error (other bricklets works just fine).

    In same software i use DC brick. Motor run till some points where it is mechanically stopped so i have to use DC.get_current_consumption() to turn it off. In normal operations DC.get_current_consumption() works fine, but after my program inits DC.get_current_consumption() hangs.

    I am using python language.

    I am using master and DC bricks with 6 connected bricklets.

    I am connecting to master brick via usb.

     

    I know that this is not to much information. I will try to isolate problem, and then put some more info in this topic, but maybe You have some hints ?

  3. Geschrieben

    Is there the possibility to create only one image and switch between Fast- and Featuremode via Brickviewer followed by a reboot?

    That is not easily possible.

    I didn't looked at RED git repo, but if You use DeviceTree in your RED kernel, then it should be quite easy to switch to GPU/nonGPU mode trought fw_setenv-->uboot-->DT-->Kernel

     

    I do like the idea, optimally we would just have some checkboxes in brickv, such as

     

    * [ ] Use GPU

    * [ ] Start X

    * [ ] Start Apache (webserver)

    * [ ] Use splashscreen

    * [ ] ...

     

     

    nice!

  4. Geschrieben

    grhhhh :-/

     

    they worked individually fine ..workED ..I just "bricked" my DC brick :-( ..LED is dead ..i beleve that one of stack connector disconected by accident while under voltage :-/

    I have to order new one..

     

    Thx for that clue!

     

    EDIT:

     

    brick was in "bootloader mode" ..so after upgrading firmware stack working stable !

    ..nice !

  5. Geschrieben

    My topology looks like this

     

    0 - master brick

    0A - SSR

    0B - SSR

    0C - SSR

    1 - DC brick

    1A - 4Relay

    1B - 4Relay

     

    After connecting master brick to my mac (tested with beagle bone black with same results) few magic things can happend:

    1. LEDs on both bricks turning off after few seconds

    2. Bricks are restarting every few seconds

    3. Only Master Brick and it's bricklets are visible

     

     

    I found FAQ section, but non of those worked for me.

     

    Any hints ?

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.